diff --git a/data/curation-review-v1.json b/data/curation-review-v1.json index 901ad5c..08af93e 100644 --- a/data/curation-review-v1.json +++ b/data/curation-review-v1.json @@ -1,12 +1,66 @@ { + "datasetVersion": "purpose-dataset-sol-high-v2", + "humanLabelAndDifficultyReview": { + "decision": "Every supervised target was regenerated with gpt-5.6-sol at high reasoning effort.", + "decisionBasis": "The dataset owner invalidated the original labels and required a complete Sol-high relabel.", + "decisionDate": "2026-08-02", + "generatedArtifact": "ml/purpose-classifier/.artifacts/human-review-v1.csv", + "populationRecords": 12193, + "reviewFields": [ + "purpose", + "secondary", + "difficulty", + "slice", + "review status", + "notes" + ], + "sampleFraction": 0.1, + "sampleRecords": 1219, + "seed": 10558743, + "status": "superseded-by-sol-high-relabel", + "strata": [ + "purpose", + "slice", + "primary language" + ] + }, "schemaVersion": 1, - "datasetVersion": "purpose-dataset-v1", + "semanticDuplicateReview": { + "auditVersion": "purpose-semantic-audit-v1", + "decision": "The prior semantic decisions were tied to the invalidated label population; the reset uses deterministic lexical curation only.", + "excluded": [ + { + "droppedPromptHash": "7348d764d602cfff72dd2b1d369ad0375a96ea52b38174aa0bd6168a548bcc2f", + "matchedPromptHash": "3ad9cfbb664504f0e7ae84b905520937e7812d4e879fa706415782341f2cd400", + "similarity": 0.984897 + }, + { + "droppedPromptHash": "a0c6e7984e92adc11ea6855c39688d733bf7665f5f965939325b15f3ba39e937", + "matchedPromptHash": "17f79a890a323c08770193a94b100dadaa00116405bdb7d14c1b89abc3c3066a", + "similarity": 0.980998 + }, + { + "droppedPromptHash": "bfd7791069fd04c13797f39ba99224ad68ca2deebbc912f08b10815954a7d223", + "matchedPromptHash": "dc48031efb18f25a56a3beddcdd814f26473b23cd496482ce1884ae6f697417a", + "similarity": 0.973329 + } + ], + "excludedCandidates": 3, + "retained": [ + { + "leftPromptHash": "70944e70e0062e947476f73b704ec01ecee19420d06fd174c58a41c04e8112f6", + "rightPromptHash": "cb3e63992cbf5830a222933dc7b44be39933baedcb46e335be02e3c379685517", + "similarity": 0.970376 + } + ], + "retainedCandidates": 1, + "reviewedCandidates": 4, + "status": "superseded-by-sol-high-relabel" + }, "wordTrigramExclusionReview": { - "status": "complete", - "reviewedRecords": 18, "confirmedTemplateDuplicates": 18, - "rejectedExclusions": 0, "decision": "All 18 pairs preserve the same task, requested outcome, and purpose label; differences are generated identifiers, ticket numbers, cosmetic context prefixes, or difficulty/slice metadata. Keep the earliest member and exclude the later template copy.", + "rejectedExclusions": 0, "reviewedDroppedPromptHashes": [ "f29de1d646055017f80346055bb3ac1468c49af7ab0c6249f45f19cf386f9fa7", "dabbcd0a19d2918199b5d0d35fac49fd5413cb17a5164252b789114fc68ec43b", @@ -26,62 +80,8 @@ "fdc04376376dbffcaf9928e9edcef29376203640b49c200c2c117f78891125a1", "432e67ead52d6cd57e4a5034cd8bcde14bd2da13f88cb5532c42fd8fbd8daf05", "24f3759ff4a3fb9fc77bed4c8525f30f9af2479a6cffbb0c4842043f99a7d8f1" - ] - }, - "semanticDuplicateReview": { - "status": "complete", - "auditVersion": "purpose-semantic-audit-v1", - "reviewedCandidates": 4, - "excludedCandidates": 3, - "retainedCandidates": 1, - "decision": "Exclude three same-purpose generated template copies. One pair ('make the screen nicer' / 'Make this screen nicer') remains because it is a deliberate vague-language variant, lives entirely in validation, and does not contaminate the frozen evaluation boundary.", - "excluded": [ - { - "droppedPromptHash": "7348d764d602cfff72dd2b1d369ad0375a96ea52b38174aa0bd6168a548bcc2f", - "matchedPromptHash": "3ad9cfbb664504f0e7ae84b905520937e7812d4e879fa706415782341f2cd400", - "similarity": 0.984897 - }, - { - "droppedPromptHash": "a0c6e7984e92adc11ea6855c39688d733bf7665f5f965939325b15f3ba39e937", - "matchedPromptHash": "17f79a890a323c08770193a94b100dadaa00116405bdb7d14c1b89abc3c3066a", - "similarity": 0.980998 - }, - { - "droppedPromptHash": "bfd7791069fd04c13797f39ba99224ad68ca2deebbc912f08b10815954a7d223", - "matchedPromptHash": "dc48031efb18f25a56a3beddcdd814f26473b23cd496482ce1884ae6f697417a", - "similarity": 0.973329 - } ], - "retained": [ - { - "leftPromptHash": "70944e70e0062e947476f73b704ec01ecee19420d06fd174c58a41c04e8112f6", - "rightPromptHash": "cb3e63992cbf5830a222933dc7b44be39933baedcb46e335be02e3c379685517", - "similarity": 0.970376 - } - ] - }, - "humanLabelAndDifficultyReview": { - "status": "accepted-as-generated", - "populationRecords": 12193, - "sampleFraction": 0.1, - "sampleRecords": 1219, - "seed": 10558743, - "strata": [ - "purpose", - "slice", - "primary language" - ], - "reviewFields": [ - "purpose", - "secondary", - "difficulty", - "slice", - "review status", - "notes" - ], - "generatedArtifact": "ml/purpose-classifier/.artifacts/human-review-v1.csv", - "decisionDate": "2026-07-31", - "decisionBasis": "The dataset owner explicitly directed the project to assume the generated labels, secondary purposes, difficulties, and slices are correct and validated without completing the row-by-row sample.", - "decision": "Accept the curated generated population as-is. No relabel or reject decisions are inferred, and the blank CSV remains an optional future audit artifact rather than a rollout blocker." + "reviewedRecords": 18, + "status": "complete" } } diff --git a/data/dataset-v1-manifest.json b/data/dataset-v1-manifest.json index f016379..69c0e9c 100644 --- a/data/dataset-v1-manifest.json +++ b/data/dataset-v1-manifest.json @@ -1,21 +1,18 @@ { "curation": { "excludedDuplicates": { - "near": 18, - "semantic-reviewed": 3 + "near": 18 }, - "inputRecords": 12214, + "inputRecords": 12007, "nearDuplicateMethod": "word-trigram Jaccard after SimHash LSH candidate search", "nearDuplicateThreshold": 0.92, - "retainedRecords": 12193, - "reviewPath": "ml/purpose-classifier/data/curation-review-v1.json", - "reviewSha256": "1721ab77a0f723a4b03f42b14850b5c351ead2cd8fa72bb2d1fe3f0d2bb568da", + "retainedRecords": 11989, "vagueEvalPolicy": "validation/test only" }, - "datasetVersion": "purpose-dataset-v1", + "datasetVersion": "purpose-dataset-sol-high-v2", "frozenEval": { - "classifiableShippedFixtureRecords": 87, - "excludedGeneralFixtureRecords": 5, + "classifiableShippedFixtureRecords": 89, + "excludedGeneralFixtureRecords": 3, "hardSliceDefinition": [ "boundary", "mixed", @@ -24,9 +21,9 @@ ], "shippedFixtureRecords": 92, "shippedFixturesPath": "Tests/NucleicCoreTests/Fixtures/purpose-prompts.json", - "shippedFixturesSha256": "6c8f0eedce35f9da7a407934009e87737b5e85c7371f6a118982d9fae2ea7aae", + "shippedFixturesSha256": "876068ea26d7109365bcfbd1dc44ba3f1a0400c80dc7fdacf008b3fa07cd92cc", "syntheticPath": "ml/purpose-classifier/data/frozen-test-v1.jsonl", - "syntheticSha256": "5d34c8ac3d39c5b4e2e739c4c9058093beb6f790a42a1397cedefae6271654ab" + "syntheticSha256": "9997dbaa6d305ea56d8c161e39b925368761ab613a706eb8c2ba55d0e58b1906" }, "ratios": { "test": 0.1, @@ -38,113 +35,113 @@ "sources": [ { "path": "ml/purpose-classifier/data/purpose-prompts.jsonl", - "records": 9214, - "sha256": "3c7f8b496ef2014794a50433a78e3125c0dd4a03dc2a7773b52ee25587ac48e7" + "records": 9007, + "sha256": "6fbd08df113ca4c6f9da151222772dc3e25e1b9b19c9c2b7df9f572053af2507" }, { "path": "ml/purpose-classifier/data/purpose-prompts-round2.jsonl", "records": 3000, - "sha256": "0a35eac2549e95b31518cd0eee99b83b03761c26a0fb258f427fe04a632699ed" + "sha256": "a3c5bbede5b7db743c9f31756491990b388edd2aa9b41c8b2b9ec95b7115f4aa" } ], "splits": { "test": { - "classifiableFixtureRecords": 87, + "classifiableFixtureRecords": 89, "distribution": { "language": { - "de": 7, - "en": 1110, - "es": 9, - "fr": 5, - "ja": 3, - "pt": 4, + "de": 6, + "en": 1084, + "es": 7, + "fr": 7, + "ja": 5, + "pt": 7, "zh": 3 }, "purpose": { - "backendImpl": 171, - "debugging": 149, - "frontendImpl": 157, - "planning": 132, - "quickFix": 140, - "refactor": 136, - "review": 127, - "writing": 129 + "backendImpl": 140, + "debugging": 168, + "frontendImpl": 159, + "planning": 120, + "quickFix": 136, + "refactor": 149, + "review": 131, + "writing": 116 }, "slice": { - "boundary": 179, - "core": 507, - "mixed": 80, - "pasted-context": 84, - "vague-eval": 291 + "boundary": 51, + "core": 635, + "mixed": 87, + "pasted-context": 77, + "vague-eval": 269 } }, - "hardSyntheticRecords": 634, - "logicalRecords": 1228, - "sha256": "5d34c8ac3d39c5b4e2e739c4c9058093beb6f790a42a1397cedefae6271654ab", - "syntheticRecords": 1141 + "hardSyntheticRecords": 484, + "logicalRecords": 1208, + "sha256": "9997dbaa6d305ea56d8c161e39b925368761ab613a706eb8c2ba55d0e58b1906", + "syntheticRecords": 1119 }, "train": { "distribution": { "language": { - "de": 100, - "en": 9324, - "es": 100, - "fr": 81, - "ja": 77, - "pt": 70, - "zh": 72 + "de": 84, + "en": 9257, + "es": 82, + "fr": 64, + "ja": 62, + "pt": 56, + "zh": 57 }, "purpose": { - "backendImpl": 1226, - "debugging": 1245, - "frontendImpl": 1234, - "planning": 1223, - "quickFix": 1230, - "refactor": 1223, - "review": 1230, - "writing": 1213 + "backendImpl": 1223, + "debugging": 1355, + "frontendImpl": 1092, + "planning": 1208, + "quickFix": 1184, + "refactor": 1204, + "review": 1203, + "writing": 1193 }, "slice": { - "boundary": 2066, - "core": 5818, - "mixed": 906, - "pasted-context": 1034 + "boundary": 605, + "core": 7175, + "mixed": 987, + "pasted-context": 895 } }, - "records": 9824, - "sha256": "40a5064c2a95d4394d71b3edbad7d03dce7d67b2e5ba9ab9320476e35e3a4953" + "records": 9662, + "sha256": "0e16940308dc7557c73b1b804bf7b715c86d263b613201588ec274169ee01e89" }, "validation": { "distribution": { "language": { - "de": 8, - "en": 1178, - "es": 12, + "de": 10, + "en": 1165, + "es": 10, "fr": 7, - "ja": 8, - "pt": 8, + "ja": 5, + "pt": 4, "zh": 7 }, "purpose": { - "backendImpl": 183, - "debugging": 157, - "frontendImpl": 168, - "planning": 141, - "quickFix": 151, - "refactor": 149, - "review": 140, - "writing": 139 + "backendImpl": 152, + "debugging": 182, + "frontendImpl": 174, + "planning": 128, + "quickFix": 140, + "refactor": 163, + "review": 143, + "writing": 126 }, "slice": { - "boundary": 195, - "core": 541, - "mixed": 83, - "pasted-context": 95, - "vague-eval": 314 + "boundary": 57, + "core": 677, + "mixed": 95, + "pasted-context": 88, + "vague-eval": 291 } }, - "records": 1228, - "sha256": "3d0a3730931db360dd8346cf12d03901ac139acf5be1d9e84975ac591186c588" + "records": 1208, + "sha256": "301cd3d1c69e1bb92b811e857093ad12fb8c5c11bb402ee2993403d5e4467969" } } } diff --git a/data/frozen-test-v1.jsonl b/data/frozen-test-v1.jsonl index 537fa2b..0891e47 100644 --- a/data/frozen-test-v1.jsonl +++ b/data/frozen-test-v1.jsonl @@ -1,1141 +1,1119 @@ -{"prompt":"Investigate why revoked group membership remains active in one regional websocket gateway.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Add a copied state to the client-secret button","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.22,"slice":"core","lang":"en"} -{"prompt":"Define the plan for adopting Iceberg tables in the events lake; implementation will happen in a later project.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"figure out the plan for signing and distributing third party plugins, including a review step we can actually staff","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Add a bounded DovetailBirchMigratorStore export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} +{"prompt":"Investigate why revoked group membership remains active in one regional websocket gateway.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add a copied state to the client-secret button","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Unify the JunctionPrismCacheStore validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-41145: finish the compact AegisAcornWidgetFlow filter experience\n\nRoute: /catalog/search\nSource: projects/aegis/app/src/main/SyncWorker.kt\nFramework: PostgreSQL 17\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Use the UI evidence to complete AegisAcornWidgetFlow'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":"Define the plan for adopting Iceberg tables in the events lake; implementation will happen in a later project.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"figure out the plan for signing and distributing third party plugins, including a review step we can actually staff","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add a bounded DovetailBirchMigratorStore export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Create an operator guide for diagnosing deposits stuck below finality.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"our workflow state lives in a react context, a ref for the canvas positions, and localstorage for the draft, and they desync. one store, same saved output","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Change 'us_east_1' to 'us-east-1' in examples/aws.yaml","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"our postgres connections spike to the max every morning at 9:02 and recover by 9:06. pooler is pgbouncer in transaction mode. what is doing that","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Investigate why the clinician portal briefly shows another patient's name after using browser back.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"TV app ticket:\n\n```text\nScreen: series details\nHero: artwork, title, metadata, actions, current season context\nContinue action resumes latest unfinished episode\nSeason picker preserves focus when changing season\nEpisode rows show progress, download state, availability, and audio-description badge\nLarge artwork loads progressively without shifting layout\nOffline mode shows only playable downloaded episodes\nAccessibility: focus order follows visual layout; synopsis can be expanded; badges have spoken labels\nRemote control: long press opens episode actions\n```\n\nImplement the tvOS screen and UI tests using existing playback models.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"pasted-context","lang":"en"} +{"prompt":"our workflow state lives in a react context, a ref for the canvas positions, and localstorage for the draft, and they desync. one store, same saved output","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Change 'us_east_1' to 'us-east-1' in examples/aws.yaml","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"our postgres connections spike to the max every morning at 9:02 and recover by 9:06. pooler is pgbouncer in transaction mode. what is doing that","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the plugin sends its version in a header we never read","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Investigate why the clinician portal briefly shows another patient's name after using browser back.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"TV app ticket:\n\n```text\nScreen: series details\nHero: artwork, title, metadata, actions, current season context\nContinue action resumes latest unfinished episode\nSeason picker preserves focus when changing season\nEpisode rows show progress, download state, availability, and audio-description badge\nLarge artwork loads progressively without shifting layout\nOffline mode shows only playable downloaded episodes\nAccessibility: focus order follows visual layout; synopsis can be expanded; badges have spoken labels\nRemote control: long press opens episode actions\n```\n\nImplement the tvOS screen and UI tests using existing playback models.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} {"prompt":"sort out the platform direction","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} -{"prompt":"finish the sync thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"compliance-facing doc describing our audit logging: coverage, retention, integrity, and access controls","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"map out how we'd add row level security to the reporting db without breaking the 40-odd existing queries, then do the first table as a proof","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Investigate why UDP flows intermittently bypass the egress policy after a node upgrade.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.76,"slice":"boundary","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.89,"slice":"pasted-context","lang":"en"} +{"prompt":"finish the sync thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"compliance-facing doc describing our audit logging: coverage, retention, integrity, and access controls","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"map out how we'd add row level security to the reporting db without breaking the 40-odd existing queries, then do the first table as a proof","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Investigate why UDP flows intermittently bypass the egress policy after a node upgrade.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","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":"Develop a roadmap for consolidating three observability stacks into one OpenTelemetry platform. Include signal ownership, semantic conventions, sampling, retention, tenant cost attribution, alert migration, training, rollback, and measurable exit criteria for each quarter.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Give the security dashboard a useful empty state","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.32,"slice":"core","lang":"en"} -{"prompt":"Find out why SwiftData occasionally saves two copies of a newly created notebook when iCloud sync resumes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"IsotopeTideWorkerCoordinator: maybe tighten this up","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"vague-eval","lang":"en"} -{"prompt":"make the empty state nicer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Draft a support guide for recovering an interrupted dataset publication.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Build the mobile attendance screen with roster, status, bulk actions, offline capture, and accessible controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Customer release notes source:\n\n```text\nFeature: withdrawal address book\nCustomers may save named addresses per asset and network\nNew addresses require email confirmation before use\nOrganizations can require a 24-hour cooling period\nAddress labels are private to the organization\nRemoving an address prevents new withdrawals but does not affect pending ones\nNetwork and memo/tag fields are part of the saved destination\nUnsupported contract addresses are rejected when detectable\nOld API clients can withdraw to saved or unsaved destinations as before unless policy requires allowlisting\n```\n\nTurn this into release notes and an administrator guide with clear security limits and compatibility behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.46,"slice":"pasted-context","lang":"en"} -{"prompt":"the playground url gets too long for big configs and breaks in slack","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Explain how the content service pins embedded resources when a course version is published.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Add incremental repository-symbol graph updates with delete tombstones and checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","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.83,"slice":"boundary","lang":"en"} -{"prompt":"BorealLumenChartStore returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/boreal/ui/settings/PrivacyPane.tsx and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"boundary","lang":"en"} -{"prompt":"`Matchmakng failed` を `Matchmaking failed` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"ja"} -{"prompt":"GossamerHarborIndexCoordinator: rethink this area","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"vague-eval","lang":"en"} -{"prompt":"Editor UI ticket:\n\nArtists need to inspect navigation regions while placing obstacles. Add a viewport overlay with:\n- translucent region fills keyed by traversal type\n- boundary outlines that remain visible over bright scenes\n- hover label with region ID and cost\n- toolbar toggles for fill, edges, and labels\n- a legend that collapses on narrow editor windows\n- no measurable repaint when the overlay is hidden\n\nThe navigation data already exists in NavDebugModel. Implement the overlay and controls using the editor's current theme and undo-safe selection behavior.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Before touching projects/caldera/crates/index/src/segment.rs, 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.62,"slice":"boundary","lang":"en"} -{"prompt":"just fix the little spacing thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.18,"slice":"vague-eval","lang":"en"} -{"prompt":"Why does BorealLumenChartService's Kafka worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"The JunctionOrbitSyncStore 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.17,"slice":"boundary","lang":"en"} -{"prompt":"Create the desktop fleet-group editor with rules, membership preview, exclusions, scheduling, and validation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Plan and implement the first phase of resumable artifact uploads: define the request lifecycle and storage invariants, then build the create-session and append-chunk endpoints behind upload_v2.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"continue the reward bug","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"Spell EquinoxKiteSchedulerStore's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"boundary","lang":"en"} -{"prompt":"FoxgloveAtlasSearchStore'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.17,"slice":"core","lang":"en"} -{"prompt":"Rename `reciept_url` to `receipt_url` in the unreleased migration.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"boundary","lang":"en"} -{"prompt":"onwards","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"MeridianPrismCacheCoordinator: the docs need something","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"vague-eval","lang":"en"} -{"prompt":"Add zstd support to the trace ingester","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Network architecture notes:\n\n```text\nGoal: private connectivity from customer VPCs to our regional API\nCloud providers: AWS first, Azure next, GCP later\nAWS candidate: PrivateLink with one endpoint service per region\nTenants may have overlapping RFC1918 ranges\nAPI must identify tenant independently of source IP\nDNS should resolve private names only inside enrolled networks\nCustomers need connection-status diagnostics\nBackend deployments must not require endpoint recreation\nAbuse controls and per-tenant quotas still apply\nSupport needs a revocation path that takes effect within five minutes\n```\n\nProduce an implementation-free architecture and rollout plan covering identity, DNS, tenancy, availability, onboarding, observability, revocation, and provider expansion.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"pasted-context","lang":"en"} -{"prompt":"Walk through KeystoneMarbleTokenService's usage.svelte","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"figure out the flaky thing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","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_54124'\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_54124'::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\nFind the source of this NorthstarBirchMigratorFlow 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.96,"slice":"pasted-context","lang":"en"} +{"prompt":"Give the security dashboard a useful empty state","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Find out why SwiftData occasionally saves two copies of a newly created notebook when iCloud sync resumes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"IsotopeTideWorkerCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Draft a support guide for recovering an interrupted dataset publication.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Build the mobile attendance screen with roster, status, bulk actions, offline capture, and accessible controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Customer release notes source:\n\n```text\nFeature: withdrawal address book\nCustomers may save named addresses per asset and network\nNew addresses require email confirmation before use\nOrganizations can require a 24-hour cooling period\nAddress labels are private to the organization\nRemoving an address prevents new withdrawals but does not affect pending ones\nNetwork and memo/tag fields are part of the saved destination\nUnsupported contract addresses are rejected when detectable\nOld API clients can withdraw to saved or unsaved destinations as before unless policy requires allowlisting\n```\n\nTurn this into release notes and an administrator guide with clear security limits and compatibility behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"the playground url gets too long for big configs and breaks in slack","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Explain how the content service pins embedded resources when a course version is published.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Add incremental repository-symbol graph updates with delete tombstones and checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","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":"BorealLumenChartStore returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/boreal/ui/settings/PrivacyPane.tsx and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"`Matchmakng failed` を `Matchmaking failed` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"ja"} +{"prompt":"GossamerHarborIndexCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"IsotopeMapleQueueCoordinator: assess, then document","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Editor UI ticket:\n\nArtists need to inspect navigation regions while placing obstacles. Add a viewport overlay with:\n- translucent region fills keyed by traversal type\n- boundary outlines that remain visible over bright scenes\n- hover label with region ID and cost\n- toolbar toggles for fill, edges, and labels\n- a legend that collapses on narrow editor windows\n- no measurable repaint when the overlay is hidden\n\nThe navigation data already exists in NavDebugModel. Implement the overlay and controls using the editor's current theme and undo-safe selection behavior.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"CalderaJuniperCLICoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Implement robot-health history and write its API documentation. Include signals, state changes, firmware, pagination, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"audit integrity — hash chaining so tampering is detectable, with the verification job","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Before touching projects/caldera/crates/index/src/segment.rs, 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.9,"slice":"core","lang":"en"} +{"prompt":"Why does BorealLumenChartService's Kafka worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"The JunctionOrbitSyncStore 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":"Create the desktop fleet-group editor with rules, membership preview, exclusions, scheduling, and validation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Plan and implement the first phase of resumable artifact uploads: define the request lifecycle and storage invariants, then build the create-session and append-chunk endpoints behind upload_v2.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Responsive layout for CalderaBirchMigratorService","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Spell EquinoxKiteSchedulerStore's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"FoxgloveAtlasSearchStore's metric is misspelled as succesful_total in one declaration. Correct that literal and its exact test expectation, without renaming anything else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename `reciept_url` to `receipt_url` in the unreleased migration.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"MeridianPrismCacheCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Add zstd support to the trace ingester","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Network architecture notes:\n\n```text\nGoal: private connectivity from customer VPCs to our regional API\nCloud providers: AWS first, Azure next, GCP later\nAWS candidate: PrivateLink with one endpoint service per region\nTenants may have overlapping RFC1918 ranges\nAPI must identify tenant independently of source IP\nDNS should resolve private names only inside enrolled networks\nCustomers need connection-status diagnostics\nBackend deployments must not require endpoint recreation\nAbuse controls and per-tenant quotas still apply\nSupport needs a revocation path that takes effect within five minutes\n```\n\nProduce an implementation-free architecture and rollout plan covering identity, DNS, tenancy, availability, onboarding, observability, revocation, and provider expansion.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Walk through KeystoneMarbleTokenService's usage.svelte","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"figure out the flaky thing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"IsotopeOpalRouterCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","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_54124'\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_54124'::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\nFind the source of this NorthstarBirchMigratorFlow symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} {"prompt":"Separate physics integration from entity iteration in the ECS engine while preserving deterministic replay hashes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"SDK consumers are ready for durable continuation tokens, so the remaining work lives in MeridianSummitProxyStore's API, storage, and worker layers. Add signed cursor parsing, bounded pagination, key rotation, tenant checks, and a resumable background path with metrics for lag, retries, and terminal failures.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside MeridianSummitProxyStore\n- do not introduce another runtime dependency\n\nThe relevant code crosses geospatial, Deno, iPadOS. Prefer evidence from the repository and make any assumption explicit.\n\nThe contract notes are context; the requested outcome is the working server path.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"boundary","lang":"en"} -{"prompt":"diff --git a/projects/aegis/crates/index/src/segment.rs b/projects/aegis/crates/index/src/segment.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/aegis/crates/index/src/segment.rs\n+++ b/projects/aegis/crates/index/src/segment.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is AegisAtlasSearchFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"ok next thing please","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Propose an event model for collaborative document cursors. Include ordering guarantees, disconnect cleanup, fan-out limits, multi-region implications, and a staged path from the current single-node WebSocket hub.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"hoist the duplicated auth setup out of all 40 test files into a shared fixture","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Code-review packet from SEC-391:\n\nNew files:\ninternal/plugins/loader.go\ninternal/plugins/manifest.go\ninternal/plugins/sandbox_linux.go\n\nPlugin flow:\n1. Read manifest from user-supplied archive.\n2. Extract to cache directory.\n3. Verify SHA-256 from registry response.\n4. Launch executable with JSON-RPC over stdio.\n5. Pass selected environment variables and workspace path.\n\nReviewer concerns:\n- archive traversal and symlinks\n- digest verification occurs after extraction\n- inherited file descriptors\n- environment allowlist defaults\n- cache replacement races\n- executable permissions\n\nReview the current branch for exploitable paths and sandbox escapes. Report severity, exact code path, attacker prerequisites, and recommended mitigation. Do not make changes; this is an assessment for the security gate.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"clients rejected for capacity retry against the same node forever","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Work out the platform direction","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"Add a loading state to the room controls","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Restructure the feature-generation pipeline and document its transform interface. Preserve outputs while separating reads, joins, transformations, validation, and publication.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","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.92,"slice":"mixed","lang":"en"} +{"prompt":"SDK consumers are ready for durable continuation tokens, so the remaining work lives in MeridianSummitProxyStore's API, storage, and worker layers. Add signed cursor parsing, bounded pagination, key rotation, tenant checks, and a resumable background path with metrics for lag, retries, and terminal failures.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside MeridianSummitProxyStore\n- do not introduce another runtime dependency\n\nThe relevant code crosses geospatial, Deno, iPadOS. Prefer evidence from the repository and make any assumption explicit.\n\nThe contract notes are context; the requested outcome is the working server path.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/aegis/crates/index/src/segment.rs b/projects/aegis/crates/index/src/segment.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/aegis/crates/index/src/segment.rs\n+++ b/projects/aegis/crates/index/src/segment.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is AegisAtlasSearchFlow'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":"Propose an event model for collaborative document cursors. Include ordering guarantees, disconnect cleanup, fan-out limits, multi-region implications, and a staged path from the current single-node WebSocket hub.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"hoist the duplicated auth setup out of all 40 test files into a shared fixture","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Code-review packet from SEC-391:\n\nNew files:\ninternal/plugins/loader.go\ninternal/plugins/manifest.go\ninternal/plugins/sandbox_linux.go\n\nPlugin flow:\n1. Read manifest from user-supplied archive.\n2. Extract to cache directory.\n3. Verify SHA-256 from registry response.\n4. Launch executable with JSON-RPC over stdio.\n5. Pass selected environment variables and workspace path.\n\nReviewer concerns:\n- archive traversal and symlinks\n- digest verification occurs after extraction\n- inherited file descriptors\n- environment allowlist defaults\n- cache replacement races\n- executable permissions\n\nReview the current branch for exploitable paths and sandbox escapes. Report severity, exact code path, attacker prerequisites, and recommended mitigation. Do not make changes; this is an assessment for the security gate.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"clients rejected for capacity retry against the same node forever","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Work out the platform direction","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"vague-eval","lang":"en"} +{"prompt":"Add a loading state to the room controls","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Restructure the feature-generation pipeline and document its transform interface. Preserve outputs while separating reads, joins, transformations, validation, and publication.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","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":"Merge the duplicated OAuth token validation paths in gateway and websocket-auth without altering accepted issuers or error responses.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"sounds good, go","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","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":"loading state for the feed — the cards should reserve their final height so nothing jumps when data lands","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"the preprocessing code exists twice — once in the training pipeline, once in the serving path — and they've diverged. make them literally the same code","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"readme is out of date in like six places and there's a section about a feature we removed. rewrite it top to bottom against what the code actually does now","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Outline a roadmap for making game replays portable across engine upgrades, including versioned state, deterministic validation, compatibility windows, and archival tests.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"core","lang":"en"} -{"prompt":"What is the safest way to split projects/equinox/app/src/main/SyncWorker.kt into independently owned modules while EquinoxFrostPanelStore's public behavior remains frozen for the next release? Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} +{"prompt":"the preprocessing code exists twice — once in the training pipeline, once in the serving path — and they've diverged. make them literally the same code","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"readme is out of date in like six places and there's a section about a feature we removed. rewrite it top to bottom against what the code actually does now","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Outline a roadmap for making game replays portable across engine upgrades, including versioned state, deterministic validation, compatibility windows, and archival tests.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"What is the safest way to split projects/equinox/app/src/main/SyncWorker.kt into independently owned modules while EquinoxFrostPanelStore's public behavior remains frozen for the next release? Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Style the livestream chat composer for compact landscape, safe-area insets, attachment previews, and disabled-send feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"JunctionEchoRegistryCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"vague-eval","lang":"en"} -{"prompt":"ugh whatever, you pick","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Review the subtitle-upload endpoint for parser bombs, unsafe markup, language spoofing, tenant confusion, and partial failures.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"NorthstarOrbitSyncCoordinator: sort out the rough edge","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"vague-eval","lang":"en"} -{"prompt":"GossamerTideWorkerCoordinator: make this less weird","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"vague-eval","lang":"en"} -{"prompt":"Diagnose the duplicate settlement alert","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} +{"prompt":"JunctionEchoRegistryCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Match BorealPineMetricsService's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Polish the creator stats card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Review the subtitle-upload endpoint for parser bombs, unsafe markup, language spoofing, tenant confusion, and partial failures.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why Safari occasionally loops between `/login` and `/callback` after a successful identity-provider response.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"NorthstarOrbitSyncCoordinator: sort out the rough edge","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Diagnose the duplicate settlement alert","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"the graphql resolvers reach into the ORM directly. put a service layer between them, one service per domain, resolvers get thin. no schema changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Pin EquinoxWillowCodecStore's NATS dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"boundary","lang":"en"} -{"prompt":"Move result-highlighting out of `SearchController` while preserving fragments, escaping, and offsets.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Outline a phased architecture for moving transaction history from Postgres to a chain-aware event store, without implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.87,"slice":"boundary","lang":"en"} -{"prompt":"Assess whether navigation/path_planner.cpp can route through a zone that becomes restricted during an active mission.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Why does CalderaOpalRouterStore's Swift 6 worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"i want the design for our multi-region active-active setup. writes in both regions, conflict resolution, and a story for the tables where conflicts are unacceptable (billing, primarily). also what we tell customers about consistency, because right now we'd be lying if we said strong","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"GossamerPineMetricsCoordinator: polish the last piece","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"vague-eval","lang":"en"} -{"prompt":"the monthly uptime number disagrees with our internal slo dashboard by half a percent","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"finish the controller stuff","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"contribution guide for the android repo — module boundaries, the di conventions, and how to add a new screen","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"continue yesterday's architecture","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"Merge the duplicated token-claim normalization paths while retaining claim values, errors, and compatibility with older issuers.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"match quality evaluation harness against a labeled set, reporting precision and recall per match strategy","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Rename `segIdx` to `segmentIndex` in `PlayerState.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"en"} -{"prompt":"HinterlandLedgerGateCoordinator is blocking the next release because lease renewal code copied across three workers. I need two concrete outcomes from a single pass: produce a consumer guide for HinterlandLedgerGateCoordinator, and give the existing implementation a read-only safety pass. Use the existing React 19 conventions in projects/hinterland/cmd/exporter/main.py; avoid a schema migration in this release. Keep the outcomes distinct so reviewers can see which evidence supports the assessment and which files or prose satisfy the requested change.\n\nConstraints:\n- preserve public wire values and tenant boundaries\n- cover cancellation and retry behavior\n- avoid generated code and unrelated cleanup\n- include a rollback trigger that an on-call engineer can measure\n\nThis is a fresh workstream for the release, so derive everything from the repository and the context here.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.61,"slice":"mixed","lang":"en"} -{"prompt":"KeystoneTideWorkerCoordinator: make this less weird","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"vague-eval","lang":"en"} -{"prompt":"what does the memory ordering on that atomic actually buy us? relaxed vs acquire here, i genuinely dont know if the current code is correct","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Move pay-calendar resolution out of the run scheduler without changing dates.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"fix party invites","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} -{"prompt":"NorthstarTideWorkerService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Cloudflare Workers operational envelope\n\nThe relevant code crosses developer tools, Java, WebGL. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Consolidate robot-status formatting across console and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Lay out a two-milestone strategy for eliminating two validators with subtly different error strings in HinterlandBirchMigratorService, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"HinterlandEchoRegistryCoordinator: make this less weird","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"vague-eval","lang":"en"} -{"prompt":"Develop a capacity roadmap for moving build artifacts from 2 PB to 15 PB. Include access patterns, replication, retention, deduplication, cost gates, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"core","lang":"en"} -{"prompt":"review our component library for components that exist in code but not in figma, and vice versa","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Teach KeystoneCinderAuthFlow to verify signed continuation tokens, reject cross-tenant cursors, and rotate keys without invalidating tokens issued during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"Ticket OPS-47146: retire the legacy replay path for GossamerCloudReconcilerFlow\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 GossamerCloudReconcilerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.59,"slice":"pasted-context","lang":"en"} -{"prompt":"The ONNX export produces plausible outputs on CPU but nonsense on TensorRT for batches larger than one. Diagnose which shape assumption is wrong.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Design an authorization architecture for enterprise workspaces with organization roles, project grants, temporary elevation, service accounts, and policy simulation. Cover evaluation semantics, auditability, cache invalidation, emergency access, migration from the current role table, and rollout gates. Deliver an RFC, not implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"core","lang":"en"} -{"prompt":"look through the protocol code","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"Design our shader asset pipeline","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-44130\n\n08:02 deploy DovetailOpalRouterFlow 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 DovetailOpalRouterFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"pasted-context","lang":"en"} -{"prompt":"Test Suite 'OvertureNovaPickerFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[OvertureNovaPickerFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/overture/db/migrations/20260730_events.sql:144: error: -[OvertureNovaPickerFlowTests 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 '-[OvertureNovaPickerFlowTests 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 OvertureNovaPickerFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} +{"prompt":"Pin EquinoxWillowCodecStore's NATS dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Move result-highlighting out of `SearchController` while preserving fragments, escaping, and offsets.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Outline a phased architecture for moving transaction history from Postgres to a chain-aware event store, without implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Assess whether navigation/path_planner.cpp can route through a zone that becomes restricted during an active mission.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Why does CalderaOpalRouterStore's Swift 6 worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"GossamerPineMetricsCoordinator: polish the last piece","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"the monthly uptime number disagrees with our internal slo dashboard by half a percent","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"finish the controller stuff","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"contribution guide for the android repo — module boundaries, the di conventions, and how to add a new screen","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Merge the duplicated token-claim normalization paths while retaining claim values, errors, and compatibility with older issuers.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"match quality evaluation harness against a labeled set, reporting precision and recall per match strategy","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"HinterlandLedgerGateCoordinator is blocking the next release because lease renewal code copied across three workers. I need two concrete outcomes from a single pass: produce a consumer guide for HinterlandLedgerGateCoordinator, and give the existing implementation a read-only safety pass. Use the existing React 19 conventions in projects/hinterland/cmd/exporter/main.py; avoid a schema migration in this release. Keep the outcomes distinct so reviewers can see which evidence supports the assessment and which files or prose satisfy the requested change.\n\nConstraints:\n- preserve public wire values and tenant boundaries\n- cover cancellation and retry behavior\n- avoid generated code and unrelated cleanup\n- include a rollback trigger that an on-call engineer can measure\n\nThis is a fresh workstream for the release, so derive everything from the repository and the context here.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"KeystoneTideWorkerCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"what does the memory ordering on that atomic actually buy us? relaxed vs acquire here, i genuinely dont know if the current code is correct","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Move pay-calendar resolution out of the run scheduler without changing dates.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"fix party invites","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"NorthstarTideWorkerService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Cloudflare Workers operational envelope\n\nThe relevant code crosses developer tools, Java, WebGL. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement assessment-session history and write its API guide. Include timing, accommodations, responses, submission, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Consolidate robot-status formatting across console and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Match EquinoxEchoRegistryService's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating two validators with subtly different error strings in HinterlandBirchMigratorService, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"HinterlandEchoRegistryCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Develop a capacity roadmap for moving build artifacts from 2 PB to 15 PB. Include access patterns, replication, retention, deduplication, cost gates, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"the page size param is capped at 1000 in one endpoint and unbounded in another","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"LongbowLumenChartStore est-il sûr ?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"fr"} +{"prompt":"review our component library for components that exist in code but not in figma, and vice versa","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"# projects/isotope/ml/pipeline/features.py\n[worker.isotopecedarpolicyflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.isotopecedarpolicyflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.isotopecedarpolicyflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.IsotopeCedarPolicyFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-49137\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Align IsotopeCedarPolicyFlow's staging timeout with the shown production value and refresh only the focused config test; nothing else in the paste should move.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Teach KeystoneCinderAuthFlow to verify signed continuation tokens, reject cross-tenant cursors, and rotate keys without invalidating tokens issued during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"The ONNX export produces plausible outputs on CPU but nonsense on TensorRT for batches larger than one. Diagnose which shape assumption is wrong.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Design an authorization architecture for enterprise workspaces with organization roles, project grants, temporary elevation, service accounts, and policy simulation. Cover evaluation semantics, auditability, cache invalidation, emergency access, migration from the current role table, and rollout gates. Deliver an RFC, not implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Design our shader asset pipeline","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-44130\n\n08:02 deploy DovetailOpalRouterFlow 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 DovetailOpalRouterFlow, 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":"Test Suite 'OvertureNovaPickerFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[OvertureNovaPickerFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/overture/db/migrations/20260730_events.sql:144: error: -[OvertureNovaPickerFlowTests 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 '-[OvertureNovaPickerFlowTests 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 OvertureNovaPickerFlow'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":"Crash report from iPhone 18 Pro:\n\nException Type: EXC_BAD_ACCESS (SIGSEGV)\nException Subtype: KERN_INVALID_ADDRESS at 0x0000000000000010\nThread 11 Crashed:\n0 libswiftCore.dylib swift_retain\n1 TrailSync SyncBatch.deinit + 44\n2 TrailSync UploadCoordinator.finish(batch:) + 188\n3 TrailSync closure #2 in UploadCoordinator.start() + 96\n4 libswift_Concurrency completeTaskWithClosure\n\nBreadcrumbs:\n09:17:03 app entered background\n09:17:04 background upload task completed\n09:17:04 account signed out by MDM policy\n09:17:04 pending batch store cleared\n09:17:05 crash\n\nIt reproduces rarely when sign-out and a background URLSession callback overlap. Diagnose the ownership or actor-isolation bug and fix it without retaining user data after sign-out.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"LongbowDriftConsoleCoordinator: sort out the rough edge","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"vague-eval","lang":"en"} -{"prompt":"continue where we stopped","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"LongbowDriftConsoleCoordinator: sort out the rough edge","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"fix privacy","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"Create the desktop merge-conflict viewer with three panes, editable result, navigation, validation, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"next please","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Rename AegisLumenChartStore's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} +{"prompt":"Create the desktop merge-conflict viewer with three panes, editable result, navigation, validation, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"in der nginx.conf client_max_body_size auf 50m setzen, uploads schlagen bei 12mb fehl","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"de"} {"prompt":"sort out the theme tokens","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"hmm, wondering if the right move is to just... ok. plan how we support customer-managed encryption keys. what's encrypted with what, key rotation, and what happens to backups","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"gradle: split the `core` module's build.gradle.kts, it configures 6 things that belong in convention plugins. build outputs identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"KeystoneRainfallDBCoordinator: the docs need something","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"vague-eval","lang":"en"} +{"prompt":"gradle: split the `core` module's build.gradle.kts, it configures 6 things that belong in convention plugins. build outputs identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"KeystoneRainfallDBCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} {"prompt":"Walk through how the current admission webhook handles timeouts and failurePolicy settings across clusters.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Something is busted again","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"Plan a disaster-recovery strategy for learning services, including courses, submissions, grades, assessments, keys, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"core","lang":"en"} -{"prompt":"HinterlandEmberRelayCoordinator: make the api less awkward","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"vague-eval","lang":"en"} -{"prompt":"some rows in the orders table reference customers that don't exist and the app renders 'Unknown' for them","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the keychain accessibility is kSecAttrAccessibleAlways, should be AfterFirstUnlockThisDeviceOnly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Add content-hash deduplication to uploaded travel documents with booking-scoped ownership.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Simulator: # projects/hinterland/ui/settings/PrivacyPane.tsx\n[worker.hinterlandmicaprofileflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandmicaprofileflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandmicaprofileflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandMicaProfileFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48133\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/hinterland/ui/settings/PrivacyPane.tsx. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.41,"slice":"pasted-context","lang":"en"} -{"prompt":"consolidate the four almost-identical Dockerfiles into one with build args. images should come out the same size and contents","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"plugin settings screen using the wp components library instead of our hand-rolled forms, matching core's look","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"figure out the plan for mobile time clock with geofencing, then build the clock-in endpoint","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"IsotopePrismCacheCoordinator: the docs need something","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"the forecast changes when you reload because deals with no close date get today's date","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"podemos continuar","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"pt"} -{"prompt":"Split projects/keystone/app/src/main/SyncWorker.kt by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"Implement deviation-history exports and write the API documentation. Include filters, evidence, signatures, revisions, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} +{"prompt":"Plan a disaster-recovery strategy for learning services, including courses, submissions, grades, assessments, keys, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"HinterlandEmberRelayCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"the keychain accessibility is kSecAttrAccessibleAlways, should be AfterFirstUnlockThisDeviceOnly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Add content-hash deduplication to uploaded travel documents with booking-scoped ownership.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Simulator: # projects/hinterland/ui/settings/PrivacyPane.tsx\n[worker.hinterlandmicaprofileflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandmicaprofileflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandmicaprofileflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandMicaProfileFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48133\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/hinterland/ui/settings/PrivacyPane.tsx. 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":"consolidate the four almost-identical Dockerfiles into one with build args. images should come out the same size and contents","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"plugin settings screen using the wp components library instead of our hand-rolled forms, matching core's look","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"figure out the plan for mobile time clock with geofencing, then build the clock-in endpoint","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"the forecast changes when you reload because deals with no close date get today's date","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Split projects/keystone/app/src/main/SyncWorker.kt by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement deviation-history exports and write the API documentation. Include filters, evidence, signatures, revisions, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"database cleaning between tests uses truncation on 90 tables every test","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"here's the failover test result from last night, and it did not go well:\n\n21:04 killed primary (db-01) with kill -9 on postgres\n21:04 patroni detected leader loss\n21:05 db-02 promoted to leader (11s) ✓\n21:05 app error rate 100% — connections still pointing at db-01\n21:07 pgbouncer still routing to db-01, no reconfiguration happened\n21:09 manually restarted pgbouncer, app recovered\n21:09 total outage: 5m 12s (target: 30s)\n21:14 db-01 restarted, rejoined as replica\n21:14 db-01 has 4 transactions db-02 doesn't (async replica was behind)\n21:15 patroni ran pg_rewind, those 4 transactions are gone\n\nthe 4 lost transactions are the part i can't accept. two were payments.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"sure go","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"DovetailMoonlitSDKCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} -{"prompt":"Tablet design ticket:\n\n```text\nScreen: operator work queue\nCards show work order, product, quantity, due time, line, material readiness, priority\nOperator sees only certified operations\nBlocked cards explain material, tool, quality, or maintenance constraint\nStarting work requires station and equipment confirmation\nOffline mode shows downloaded queue with stale timestamp and prevents unverified reassignment\nAccessibility: priority and block reason are text, not color only\nGlove mode increases targets and removes swipe-only actions\n```\n\nImplement the responsive screen and tests using existing work-order APIs.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"pasted-context","lang":"en"} -{"prompt":"Architect a global live-operations platform with game ownership, versioned configs, targeting, scheduling, compatibility, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"boundary","lang":"en"} +{"prompt":"DovetailMoonlitSDKCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Tablet design ticket:\n\n```text\nScreen: operator work queue\nCards show work order, product, quantity, due time, line, material readiness, priority\nOperator sees only certified operations\nBlocked cards explain material, tool, quality, or maintenance constraint\nStarting work requires station and equipment confirmation\nOffline mode shows downloaded queue with stale timestamp and prevents unverified reassignment\nAccessibility: priority and block reason are text, not color only\nGlove mode increases targets and removes swipe-only actions\n```\n\nImplement the responsive screen and tests using existing work-order APIs.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Architect a global live-operations platform with game ownership, versioned configs, targeting, scheduling, compatibility, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} {"prompt":"Add chunked uploads to the artifact CLI with checksum verification, resume tokens, and concurrent part limits.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"figure out the offline story properly then build the manifest checker","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Schreibe eine verständliche Anleitung zur Rotation von Webhook-Schlüsseln, inklusive Überlappungszeit und Verifikation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"de"} -{"prompt":"NorthstarFernSnapshotCoordinator: untangle the messy bit","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"vague-eval","lang":"en"} -{"prompt":"Find why read replicas occasionally return an older feature vector after the writer confirms commit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.76,"slice":"boundary","lang":"en"} -{"prompt":"# CI job 53112: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: WebGPU\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] MeridianSummitProxyFlowIntegration.replays_after_timeout ... ok\n[test] MeridianSummitProxyFlowIntegration.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 \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\nReconstruct the MeridianSummitProxyFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.92,"slice":"pasted-context","lang":"en"} -{"prompt":"BorealJuniperCLICoordinator needs a paired pass: produce a consumer guide for BorealJuniperCLICoordinator, plus correct the known stale timeout beside it. Use projects/boreal/pkg/cache/lease.rs as the source of truth, preserve the Cloudflare Workers contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.53,"slice":"mixed","lang":"en"} -{"prompt":"KeystoneAtlasSearchCoordinator: diagnose, then assess","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"Investigate why overnight missions use yesterday's restricted-zone schedule, implement the verified cache-key fix, and update operator documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.78,"slice":"mixed","lang":"en"} -{"prompt":"How does HinterlandVelaDrawerStore propagate cancellation through the Redis Streams boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Before touching projects/junction/internal/auth/refresh.go, 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.65,"slice":"core","lang":"en"} -{"prompt":"设计游戏内任务追踪面板，需要折叠分组、距离提示、手柄导航和超宽屏适配。","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"zh"} +{"prompt":"NorthstarFernSnapshotCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Find why read replicas occasionally return an older feature vector after the writer confirms commit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"# CI job 53112: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: WebGPU\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] MeridianSummitProxyFlowIntegration.replays_after_timeout ... ok\n[test] MeridianSummitProxyFlowIntegration.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 \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\nReconstruct the MeridianSummitProxyFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"BorealJuniperCLICoordinator needs a paired pass: produce a consumer guide for BorealJuniperCLICoordinator, plus correct the known stale timeout beside it. Use projects/boreal/pkg/cache/lease.rs as the source of truth, preserve the Cloudflare Workers contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"KeystoneAtlasSearchCoordinator: diagnose, then assess","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"OvertureJuniperCLICoordinator: sequence, then polish","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Investigate why overnight missions use yesterday's restricted-zone schedule, implement the verified cache-key fix, and update operator documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"How does HinterlandVelaDrawerStore propagate cancellation through the Redis Streams boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Before touching projects/junction/internal/auth/refresh.go, 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":"the messaging gateway. three carriers, each with a different api and its own idea of what a delivery receipt means, and our routing is a hardcoded if-chain on country code. i want the plan for proper routing with cost and quality inputs, plus how we handle a carrier being down at 3am without a human","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"and that's it for now","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"continue the review issue","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.54,"slice":"vague-eval","lang":"en"} -{"prompt":"how does our auto-update verify the signature? point me at the code path, i want to confirm we're not just checking the https cert","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"how does our auto-update verify the signature? point me at the code path, i want to confirm we're not just checking the https cert","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Change the dev port to 4174.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"DovetailBirchMigratorCoordinator: rethink this area","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"Could the reasoning behind GossamerSlateEditorStore's OpenTelemetry choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"Change the security banner copy to the approved sentence","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"the backup job hasn't succeeded in 11 days and nothing alerted","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"DovetailBirchMigratorCoordinator: rethink this area","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Could the reasoning behind GossamerSlateEditorStore's OpenTelemetry choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Change the security banner copy to the approved sentence","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"the backup job hasn't succeeded in 11 days and nothing alerted","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"add pagination to GET /v2/orders, cursor based","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"JunctionAmberFilterCoordinator: make this less weird","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"vague-eval","lang":"en"} -{"prompt":"EquinoxWrenExportCoordinator: the docs need something","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"MeridianMicaProfileCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"vague-eval","lang":"en"} -{"prompt":"runtime regressed 20% between two commits that only touched io code","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Give the app a proper onboarding screen","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} +{"prompt":"JunctionAmberFilterCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"EquinoxWrenExportCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"MeridianMicaProfileCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"runtime regressed 20% between two commits that only touched io code","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Give the app a proper onboarding screen","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the license check runs synchronously on every page load and adds 300ms when our api is slow","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"incident management ui for the on-call: create, pick components, post an update from a template, and resolve","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"MeridianRavenSessionStore's staging timeout is already known to be wrong: change the single projects/meridian/Sources/CLI/Commands/Doctor.swift value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"boundary","lang":"en"} -{"prompt":"Exporter: Ticket OPS-49134: retire the legacy replay path for IsotopeLedgerGateFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for IsotopeLedgerGateFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.67,"slice":"pasted-context","lang":"en"} +{"prompt":"MeridianRavenSessionStore's staging timeout is already known to be wrong: change the single projects/meridian/Sources/CLI/Commands/Doctor.swift value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"the row click handler does a synchronous json parse of a 4mb payload","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Exporter: Ticket OPS-49134: retire the legacy replay path for IsotopeLedgerGateFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for IsotopeLedgerGateFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} {"prompt":"our economy values are scattered across 30 scriptableobjects, prefabs and a few hardcoded constants. get them all into one config source, same balance in the test scenarios","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"one service can't reach another after enabling mTLS and the error is just 'connection reset'","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Compare the old and new HinterlandSpruceDaemonStore adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"the api docs already describe GET /v1/segments in full detail but the endpoint doesn't exist. make the code match the docs","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Lay out a two-milestone strategy for eliminating a misleading timeout name used in five packages in JunctionCoralUploadStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"finish it up","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"our build scripts have 40 environment variables that leak into build outputs, which is why nothing caches. make the builds hermetic, same artifacts produced","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Test Suite 'GossamerCopperBridgeFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[GossamerCopperBridgeFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/gossamer/pkg/cache/lease.rs:144: error: -[GossamerCopperBridgeFlowTests 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 '-[GossamerCopperBridgeFlowTests 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\nDetermine why GossamerCopperBridgeFlow 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.96,"slice":"pasted-context","lang":"en"} +{"prompt":"one service can't reach another after enabling mTLS and the error is just 'connection reset'","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Compare the old and new HinterlandSpruceDaemonStore 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":"the api docs already describe GET /v1/segments in full detail but the endpoint doesn't exist. make the code match the docs","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating a misleading timeout name used in five packages in JunctionCoralUploadStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"our build scripts have 40 environment variables that leak into build outputs, which is why nothing caches. make the builds hermetic, same artifacts produced","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'GossamerCopperBridgeFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[GossamerCopperBridgeFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/gossamer/pkg/cache/lease.rs:144: error: -[GossamerCopperBridgeFlowTests 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 '-[GossamerCopperBridgeFlowTests 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\nDetermine why GossamerCopperBridgeFlow 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":"Do the obvious cleanup","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"plan the migration from our stores-everywhere state to runes, incrementally, without a big bang rewrite","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Center the FoxgloveTideWorkerStore modal","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"boundary","lang":"en"} -{"prompt":"the cache is written by every job so the last one wins and the cache is always the wrong branch's","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Two engineers disagree about whether JunctionAtlasSearchService's cache is authoritative. Walk the reads and writes in projects/junction/ui/settings/PrivacyPane.tsx and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"HinterlandWillowCodecCoordinator: smooth out this interaction","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"Opal: What does DovetailOspreyJobService own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"What's causing the README's installation command to produce an unusable binary on Alpine?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Review the supplier-voucher endpoint for tenant confusion, stale authorization, guessed references, unsafe redirects, and cache leakage.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"outline the plan for supporting webhooks with customer-provided mTLS certs, including how we store and rotate them","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"KeystoneDeltaCanvasCoordinator: could this be clearer","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"vague-eval","lang":"en"} -{"prompt":"Investigate why appeal deadlines use the wrong holiday calendar, implement the verified jurisdiction fix, and update clerk documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.78,"slice":"mixed","lang":"en"} -{"prompt":"doc the image url format — the transform params, allowed ranges, what happens on an invalid combo","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Request: Incident timeline — INC-54138\n\n08:02 deploy NorthstarIrisBatchFlow 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 NorthstarIrisBatchFlow rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"pasted-context","lang":"en"} -{"prompt":"make the VR menu less weird","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"MeridianTideWorkerCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"Track down the reconnect crash on macOS 15, add a regression test once understood, and write a short root-cause note for docs/incidents/ble-reconnect.md.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Teach the DNS controller to coalesce duplicate reconciliation keys and apply exponential backoff without starving newly created zones.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Consolidate audience-label formatting across app and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Build the mobile route-preview screen with steps, restrictions, congestion, battery estimate, and accessible summary.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.61,"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":"plan the migration from our stores-everywhere state to runes, incrementally, without a big bang rewrite","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Center the FoxgloveTideWorkerStore modal","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the cache is written by every job so the last one wins and the cache is always the wrong branch's","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Two engineers disagree about whether JunctionAtlasSearchService's cache is authoritative. Walk the reads and writes in projects/junction/ui/settings/PrivacyPane.tsx and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the db user the app connects as is root","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"HinterlandWillowCodecCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Opal: What does DovetailOspreyJobService own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"What's causing the README's installation command to produce an unusable binary on Alpine?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"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_43121'\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_43121'::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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Determine why CalderaBirchMigratorFlow 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":"Review the supplier-voucher endpoint for tenant confusion, stale authorization, guessed references, unsafe redirects, and cache leakage.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"outline the plan for supporting webhooks with customer-provided mTLS certs, including how we store and rotate them","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"KeystoneDeltaCanvasCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Investigate why appeal deadlines use the wrong holiday calendar, implement the verified jurisdiction fix, and update clerk documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"doc the image url format — the transform params, allowed ranges, what happens on an invalid combo","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Request: Incident timeline — INC-54138\n\n08:02 deploy NorthstarIrisBatchFlow 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 NorthstarIrisBatchFlow 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":"make the VR menu less weird","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"MeridianTideWorkerCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"the e-stop topic is best-effort qos","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Teach the DNS controller to coalesce duplicate reconciliation keys and apply exponential backoff without starving newly created zones.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Consolidate audience-label formatting across app and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Build the mobile route-preview screen with steps, restrictions, congestion, battery estimate, and accessible summary.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"A cancellation signal causes some test workers to hang while others exit. Find the descriptor or task preventing shutdown.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Oddly: # projects/overture/apps/console/routes/usage.svelte\n[worker.overturemosaicgridcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.overturemosaicgridcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.overturemosaicgridcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.OvertureMosaicGridCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-55159\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/overture/apps/console/routes/usage.svelte. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.43,"slice":"pasted-context","lang":"en"} -{"prompt":"// projects/caldera/Sources/App/SessionStore.swift\nfinal class CalderaEchoRegistryFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 CalderaEchoRegistryFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"eager load the order page's relations properly and paginate it, same rendered rows","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Explain how `MasteryUpdater` treats skipped, hinted, correct, and partially correct responses. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Rename `ObsConfig` to `ObservabilityConfig` across the monorepo while preserving YAML keys and environment variables.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"plan how we prevent this class of bug — contract tests, or codegen from the spec, or a review checklist. pick something enforceable","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Review how policy cancellation refunds are calculated, then turn the findings into a service-agent guide with examples.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.63,"slice":"mixed","lang":"en"} -{"prompt":"we hit the shopify rate limit during a sync and just fail. plan the proper approach — bulk operations, the leaky bucket, and where we queue","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Evaluate the current keychain access-group setup for accidental credential sharing between the production app and extensions.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write release notes for configurable payout schedules, including eligibility, cutoffs, holidays, and rollback to the default.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"core","lang":"en"} -{"prompt":"Explain how the session cache prevents a revoked account from remaining active until cookie expiry.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} +{"prompt":"Oddly: # projects/overture/apps/console/routes/usage.svelte\n[worker.overturemosaicgridcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.overturemosaicgridcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.overturemosaicgridcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.OvertureMosaicGridCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-55159\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/overture/apps/console/routes/usage.svelte. 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":"// projects/caldera/Sources/App/SessionStore.swift\nfinal class CalderaEchoRegistryFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 CalderaEchoRegistryFlow; 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":"eager load the order page's relations properly and paginate it, same rendered rows","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Explain how `MasteryUpdater` treats skipped, hinted, correct, and partially correct responses. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Rename `ObsConfig` to `ObservabilityConfig` across the monorepo while preserving YAML keys and environment variables.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"plan how we prevent this class of bug — contract tests, or codegen from the spec, or a review checklist. pick something enforceable","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Review how policy cancellation refunds are calculated, then turn the findings into a service-agent guide with examples.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"LongbowMoonlitSDKCoordinator: diagnose, then correct","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"we hit the shopify rate limit during a sync and just fail. plan the proper approach — bulk operations, the leaky bucket, and where we queue","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Evaluate the current keychain access-group setup for accidental credential sharing between the production app and extensions.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Write release notes for configurable payout schedules, including eligibility, cutoffs, holidays, and rollback to the default.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Pin NumPy to `2.3.2`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Explain how the session cache prevents a revoked account from remaining active until cookie expiry.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Make the tiny UI adjustment","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} {"prompt":"Adjust the one value","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"vague-eval","lang":"en"} -{"prompt":"product attribution: which product drove a first order, tracked from the landing page through checkout","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Investigate why the iOS app loses room assignments after restoring a backup.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"Create the responsive workflow-template gallery with filters, versions, inputs, preview, and accessible selection.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Summarize the current batch-release workflow for quality and compliance reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} +{"prompt":"the updater runs as admin and writes to a user-writable temp path first","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"product attribution: which product drove a first order, tracked from the landing page through checkout","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the responsive workflow-template gallery with filters, versions, inputs, preview, and accessible selection.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Summarize the current batch-release workflow for quality and compliance reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} {"prompt":"make the charts feel scientific","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"Pin MathJax to `4.0.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"ok fine","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Schreibe eine kurze Referenz für die bestehenden Antragsstatus und ihre Auswirkungen auf Bearbeitung und Fristen. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"boundary","lang":"de"} -{"prompt":"some traces have a 900ms span called 'unknown' with no attributes and no children. what generates that","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Pin MathJax to `4.0.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"En projects/junction/ml/pipeline/features.py, JunctionQuartzPlayerService tiene un problema intermitente en el flujo de Kotlin coroutines. Separa responsabilidades y elimina duplicación, conservando API, wire values, orden y comportamiento observable.\n\nRestricciones:\n- seguir con Kotlin coroutines\n- conservar compatibilidad y cancelación\n- limitar el cambio a JunctionQuartzPlayerService Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con Kotlin coroutines alrededor de JunctionQuartzPlayerService.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"es"} +{"prompt":"fix the result issue","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Schreibe eine kurze Referenz für die bestehenden Antragsstatus und ihre Auswirkungen auf Bearbeitung und Fristen. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"de"} +{"prompt":"some traces have a 900ms span called 'unknown' with no attributes and no children. what generates that","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"font loading falls back to a web font when the local one is missing","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"break the checkout rewrite into two week chunks","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} {"prompt":"Two engineers disagree about whether HinterlandWrenExportStore's cache is authoritative. Walk the reads and writes in projects/hinterland/packages/api/openapi.yaml and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Dashboard: projects/foxglove/ui/settings/PrivacyPane.tsx has grown through several launches, and FoxgloveSummitProxyService now mixes policy, transport, persistence, and metrics in one place. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- cover the awkward empty and retry states\n- stay compatible with the existing GraphQL deployment\n- keep the work scoped to FoxgloveSummitProxyService and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"ok go on","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Add content-hash deduplication to uploaded signing transcripts.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Why does the party service retain two previous membership snapshots? Explain current reconnect behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.47,"slice":"boundary","lang":"en"} -{"prompt":"trace what happens end to end when someone clicks 'export' — i want every hop, including the lambda i keep forgetting about","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"add a skeleton loader to the analytics cards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"GossamerFrostPanelCoordinator: take care of the warning","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"Projection failure output:\n\n```text\ndataset=d_881 revision=14 publication event offset=99218\ncatalog projection writes status=published and searchable=true\ncheckpoint transaction fails after database failover\nDOI worker observes published state and registers identifier\nprojection restarts from previous offset\nreplays publication against already-published state and rejects duplicate transition\npartition stops; DOI exists but publication event remains uncheckpointed\n```\n\nDetermine how projection, checkpoint, and DOI registration lack one durable boundary and why replay cannot recognize the prior application.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"EquinoxCedarPolicyCoordinator: clean up that old path","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"vague-eval","lang":"en"} -{"prompt":"What does BorealJuniperCLIStore own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"hoist the duplicated pagination logic out of the six list resolvers into one helper. same page sizes, same cursor encoding, don't change the wire format","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Test Suite 'OvertureVelaDrawerCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[OvertureVelaDrawerCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/overture/internal/auth/refresh.go:144: error: -[OvertureVelaDrawerCoordinatorTests 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 '-[OvertureVelaDrawerCoordinatorTests 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 OvertureVelaDrawerCoordinator'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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"JunctionRavenSessionService é seguro?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"pt"} +{"prompt":"Dashboard: projects/foxglove/ui/settings/PrivacyPane.tsx has grown through several launches, and FoxgloveSummitProxyService now mixes policy, transport, persistence, and metrics in one place. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- cover the awkward empty and retry states\n- stay compatible with the existing GraphQL deployment\n- keep the work scoped to FoxgloveSummitProxyService and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add content-hash deduplication to uploaded signing transcripts.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Why does the party service retain two previous membership snapshots? Explain current reconnect behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"trace what happens end to end when someone clicks 'export' — i want every hop, including the lambda i keep forgetting about","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"add a skeleton loader to the analytics cards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"GossamerFrostPanelCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Projection failure output:\n\n```text\ndataset=d_881 revision=14 publication event offset=99218\ncatalog projection writes status=published and searchable=true\ncheckpoint transaction fails after database failover\nDOI worker observes published state and registers identifier\nprojection restarts from previous offset\nreplays publication against already-published state and rejects duplicate transition\npartition stops; DOI exists but publication event remains uncheckpointed\n```\n\nDetermine how projection, checkpoint, and DOI registration lack one durable boundary and why replay cannot recognize the prior application.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"What does BorealJuniperCLIStore own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"hoist the duplicated pagination logic out of the six list resolvers into one helper. same page sizes, same cursor encoding, don't change the wire format","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'OvertureVelaDrawerCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[OvertureVelaDrawerCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/overture/internal/auth/refresh.go:144: error: -[OvertureVelaDrawerCoordinatorTests 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 '-[OvertureVelaDrawerCoordinatorTests 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 OvertureVelaDrawerCoordinator'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":"Design a zero-trust machine-identity architecture for services, CI jobs, developer workstations, and edge robots. Cover enrollment, attestation, short-lived credentials, authorization, revocation, offline operation, audit evidence, and migration from shared certificates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Restructure the transaction indexer and document its chain-adapter interface. Preserve projections while separating fetch, canonicalize, apply, rollback, and checkpoint.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.83,"slice":"mixed","lang":"en"} -{"prompt":"KeystoneCraneWorkspaceCoordinator: smooth out this interaction","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"How does HinterlandEmberRelayStore propagate cancellation through the Terraform boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"JunctionSlateEditorFlow returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/junction/ui/settings/PrivacyPane.tsx and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Incident timeline — INC-50140\n\n08:02 deploy JunctionKiteSchedulerFlow 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 JunctionKiteSchedulerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"pasted-context","lang":"en"} -{"prompt":"the delete key deletes the selected node even when focus is in a text field","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"A previously stable test around DovetailWillowCodecStore now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"that's enough, just finish the small thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Implement idempotent model-output ingestion with run generations and correction support.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"how does our request id propagate from the edge worker through to the db slow query log","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Enforce LongbowEchoRegistryService's idempotency key","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Read projects/caldera/engine/render/atlas.cpp and tell me whether CalderaPineMetricsStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Benenne `MatchCtx` repositoryweit in `MatchContext` um; Protokollfelder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"de"} -{"prompt":"give me a tour of the build pipeline in Makefile + scripts/, i inherited this repo yesterday","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"KeystoneMoonlitSDKCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"vague-eval","lang":"en"} -{"prompt":"next up?","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `ReviewEvt` with `ReviewEvent` across packages while preserving event type names and public aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"the next-run time shown in the ui is an hour off half the year","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Restructure the transaction indexer and document its chain-adapter interface. Preserve projections while separating fetch, canonicalize, apply, rollback, and checkpoint.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"KeystoneCraneWorkspaceCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"日本語でこの Swift package の導入手順を書いて。README の Installation セクションとして使いたい。","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"ja"} +{"prompt":"How does HinterlandEmberRelayStore propagate cancellation through the Terraform boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"AegisSummitProxyCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"the uvicorn worker count is 1 in the container","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"JunctionSlateEditorFlow returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/junction/ui/settings/PrivacyPane.tsx and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-50140\n\n08:02 deploy JunctionKiteSchedulerFlow 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 JunctionKiteSchedulerFlow 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":"Implement idempotent model-output ingestion with run generations and correction support.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"how does our request id propagate from the edge worker through to the db slow query log","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Enforce LongbowEchoRegistryService's idempotency key","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Read projects/caldera/engine/render/atlas.cpp and tell me whether CalderaPineMetricsStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"AegisRavenSessionCoordinator: sequence, then ship","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} +{"prompt":"Benenne `MatchCtx` repositoryweit in `MatchContext` um; Protokollfelder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"de"} +{"prompt":"give me a tour of the build pipeline in Makefile + scripts/, i inherited this repo yesterday","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"KeystoneMoonlitSDKCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `ReviewEvt` with `ReviewEvent` across packages while preserving event type names and public aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the next-run time shown in the ui is an hour off half the year","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"hero section for the landing page: big headline, gradient mesh behind it, two ctas, and it can't jank on scroll","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"cache stats panel in the admin: hit rate per key prefix, memory by prefix, and the top 20 largest keys","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"ok whats left then","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"Fresh release brief for EquinoxFlintTimelineCoordinator:\n- primary outcome: assess ownership and failure handling in projects/equinox/cmd/exporter/main.py\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/equinox/cmd/exporter/main.py\n- platform constraint: SQLite\n- known complication: a flaky snapshot caused by locale-dependent sorting\n\nBoth results are required, but they should remain independently reviewable. Preserve cancellation and back-pressure semantics; 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.84,"slice":"mixed","lang":"en"} -{"prompt":"Sequence EquinoxMosaicGridService's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"the retry decorator doesn't retry on 429, add it to the retryable set","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"the station has no watchdog on the inference loop at all","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Fresh release brief for EquinoxFlintTimelineCoordinator:\n- primary outcome: assess ownership and failure handling in projects/equinox/cmd/exporter/main.py\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/equinox/cmd/exporter/main.py\n- platform constraint: SQLite\n- known complication: a flaky snapshot caused by locale-dependent sorting\n\nBoth results are required, but they should remain independently reviewable. Preserve cancellation and back-pressure semantics; 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":"Sequence EquinoxMosaicGridService's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the retry decorator doesn't retry on 429, add it to the retryable set","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"Rotate the test JWKS fixture expiry date","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"add server side pagination + sorting to the /api/logs endpoint, and a cheap total count that's allowed to be approximate over 10k","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"unwrap the double negative in shouldSkipValidation, it's `!isNotDisabled` and nobody can read it","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"add server side pagination + sorting to the /api/logs endpoint, and a cheap total count that's allowed to be approximate over 10k","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"unwrap the double negative in shouldSkipValidation, it's `!isNotDisabled` and nobody can read it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"Write the usual blurb","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} -{"prompt":"Escribe una guía para integrar formularios electrónicos, con esquemas, validación, firmas, recibos y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} -{"prompt":"Run 1182 failure excerpt:\n\n[ranker-eval] shard 23/64 complete\n[ranker-eval] shard 24/64 complete\n[ranker-eval] waiting for reducer barrier\n[worker-07] heartbeat timeout after 30000ms\n[worker-07] state=RUNNING rss=612MiB cpu=0.0%\n[coordinator] participants=64 arrived=63 generation=91\n[coordinator] retrying worker-07 assignment\n[worker-12] duplicate shard claim: 24\n\nThe job never exits, and cancel leaves the coordinator pod in Terminating until Kubernetes kills it. It happens roughly one run in twenty after enabling speculative execution. Find the protocol failure that strands the barrier and determine whether duplicate shard completion is involved. We need diagnosis first, not a timeout increase.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"The name pendingAck means two different things across HinterlandMarbleTokenStore's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Yarrow: diff --git a/projects/gossamer/crates/index/src/segment.rs b/projects/gossamer/crates/index/src/segment.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/crates/index/src/segment.rs\n+++ b/projects/gossamer/crates/index/src/segment.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nAdd the bounded GossamerQuartzPlayerFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"Forecast publication incident:\n\n```text\nrun=gfs_20260730_00 member=control\noutput valid_times=0..384h\npublication manifest generation=771 references 129 files\nobject-store list was eventually consistent and omitted hour=240\nmanifest validator expected at least 120 files, passed\ncatalog published run complete\nfile hour=240 appeared 14s later but was not in immutable manifest\nusers receive gap at one forecast time\nretry refuses new manifest because run marked published\n```\n\nDetermine why count-based validation and eventual listing produced an incomplete immutable publication and how completeness should have been established.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"walk me through what our vacuum settings actually mean for the events table, autovacuum_vacuum_scale_factor is 0.01 and i don't remember why","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"お願いします。バッチ推論のパイプラインを設計してください。1日3億レコード、GPU は 8 枚、失敗したシャードだけ再実行できるように","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"ja"} -{"prompt":"the config resolution logic exists in the api, the cli and the deploy worker separately. one implementation, and the resolved config must be identical for every existing environment","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the linter wants explicit return types on 40 exported functions, add them","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"seed the random state in the eval script, results move between runs","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"AegisIrisBatchCoordinator: untangle the messy bit","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"vague-eval","lang":"en"} -{"prompt":"The minimum supported Kafka version in projects/foxglove/internal/auth/refresh.go is one patch behind the lockfile. Align that single value and regenerate only the affected metadata.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"core","lang":"en"} -{"prompt":"MeridianNimbusFormCoordinator: smooth out this interaction","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"vague-eval","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new payment provider, including capabilities, sandbox tests, webhooks, reconciliation, and launch gates.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} +{"prompt":"Escribe una guía para integrar formularios electrónicos, con esquemas, validación, firmas, recibos y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"es"} +{"prompt":"Run 1182 failure excerpt:\n\n[ranker-eval] shard 23/64 complete\n[ranker-eval] shard 24/64 complete\n[ranker-eval] waiting for reducer barrier\n[worker-07] heartbeat timeout after 30000ms\n[worker-07] state=RUNNING rss=612MiB cpu=0.0%\n[coordinator] participants=64 arrived=63 generation=91\n[coordinator] retrying worker-07 assignment\n[worker-12] duplicate shard claim: 24\n\nThe job never exits, and cancel leaves the coordinator pod in Terminating until Kubernetes kills it. It happens roughly one run in twenty after enabling speculative execution. Find the protocol failure that strands the barrier and determine whether duplicate shard completion is involved. We need diagnosis first, not a timeout increase.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"The name pendingAck means two different things across HinterlandMarbleTokenStore's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Forecast publication incident:\n\n```text\nrun=gfs_20260730_00 member=control\noutput valid_times=0..384h\npublication manifest generation=771 references 129 files\nobject-store list was eventually consistent and omitted hour=240\nmanifest validator expected at least 120 files, passed\ncatalog published run complete\nfile hour=240 appeared 14s later but was not in immutable manifest\nusers receive gap at one forecast time\nretry refuses new manifest because run marked published\n```\n\nDetermine why count-based validation and eventual listing produced an incomplete immutable publication and how completeness should have been established.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"walk me through what our vacuum settings actually mean for the events table, autovacuum_vacuum_scale_factor is 0.01 and i don't remember why","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"お願いします。バッチ推論のパイプラインを設計してください。1日3億レコード、GPU は 8 枚、失敗したシャードだけ再実行できるように","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"ja"} +{"prompt":"the config resolution logic exists in the api, the cli and the deploy worker separately. one implementation, and the resolved config must be identical for every existing environment","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the linter wants explicit return types on 40 exported functions, add them","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"AegisIrisBatchCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"The minimum supported Kafka version in projects/foxglove/internal/auth/refresh.go 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":"MeridianNimbusFormCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new payment provider, including capabilities, sandbox tests, webhooks, reconciliation, and launch gates.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Set minReplicas to 3.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Polish the portfolio balance card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"Implement a bounded recursive-descent parser for demangling nested generic symbols.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the max.poll.records is 500 with a 3 second per-message handler","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"Build the SwiftUI database-health dashboard and add the diagnostics endpoint that supplies page and WAL statistics.","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Implement idempotent tax-election ingestion with effective dates and correction versions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} +{"prompt":"the max.poll.records is 500 with a 3 second per-message handler","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Build the SwiftUI database-health dashboard and add the diagnostics endpoint that supplies page and WAL statistics.","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Implement idempotent tax-election ingestion with effective dates and correction versions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"messages land in the dlq with no error recorded, so we have no idea why they failed","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"EquinoxJuniperCLICoordinator: sort out the rough edge","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"vague-eval","lang":"en"} -{"prompt":"from the ops channel, please sort out the top two:\n\n> @ravi: heads up, three things piling up\n> 1. the nightly `vacuum_analyze` cron has been failing for 11 days, exit 1, no output captured\n> 2. our terraform state bucket has no versioning on it (found while doing the disaster recovery doc)\n> 3. staging db is a 6 month old dump, people keep testing against unrealistic data\n>\n> also unrelated but the grafana admin password is in the wiki 🙃","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} -{"prompt":"Employee launch notes:\n\n```text\nFeature: preferred-name history\nEmployees may change preferred first and display names\nLegal name remains separate and requires HR verification\nDirectory, chat, and org chart update after synchronization\nHistorical reports retain the name effective at report time when required\nManagers are notified only when configured by organization\nOld mobile clients may show prior name until next full refresh\nChanging preferred name does not alter payroll or tax documents\n```\n\nTurn this into release notes and an employee help article. Clearly distinguish preferred and legal name behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.44,"slice":"pasted-context","lang":"en"} -{"prompt":"Set the docs site port to 4321","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"core","lang":"en"} -{"prompt":"field performance measurement — INP and long task attribution reported per interaction type, so we know which interactions are slow for real users","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"EquinoxJuniperCLICoordinator: sort out the rough edge","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"from the ops channel, please sort out the top two:\n\n> @ravi: heads up, three things piling up\n> 1. the nightly `vacuum_analyze` cron has been failing for 11 days, exit 1, no output captured\n> 2. our terraform state bucket has no versioning on it (found while doing the disaster recovery doc)\n> 3. staging db is a 6 month old dump, people keep testing against unrealistic data\n>\n> also unrelated but the grafana admin password is in the wiki 🙃","purpose":"debugging","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Employee launch notes:\n\n```text\nFeature: preferred-name history\nEmployees may change preferred first and display names\nLegal name remains separate and requires HR verification\nDirectory, chat, and org chart update after synchronization\nHistorical reports retain the name effective at report time when required\nManagers are notified only when configured by organization\nOld mobile clients may show prior name until next full refresh\nChanging preferred name does not alter payroll or tax documents\n```\n\nTurn this into release notes and an employee help article. Clearly distinguish preferred and legal name behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} +{"prompt":"Set the docs site port to 4321","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"field performance measurement — INP and long task attribution reported per interaction type, so we know which interactions are slow for real users","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} {"prompt":"the android release build crashes at startup but debug is fine. proguard i assume but the mapping file isnt telling me much","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"so uh","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"projects/meridian/services/ledger/replay.go has grown through several launches, and MeridianKiteSchedulerService now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- do not introduce another runtime dependency\n- stay compatible with the existing Tokio deployment\n- keep the work scoped to MeridianKiteSchedulerService and its direct tests\n\nThis repository spans geospatial, Deno, iPadOS; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Add a bounded IsotopeCloudReconcilerService export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Create the provenance graph UI and add a short legend for sources, transforms, environments, snapshots, and publications.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} +{"prompt":"projects/meridian/services/ledger/replay.go has grown through several launches, and MeridianKiteSchedulerService now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- do not introduce another runtime dependency\n- stay compatible with the existing Tokio deployment\n- keep the work scoped to MeridianKiteSchedulerService and its direct tests\n\nThis repository spans geospatial, Deno, iPadOS; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add a bounded IsotopeCloudReconcilerService export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the provenance graph UI and add a short legend for sources, transforms, environments, snapshots, and publications.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} {"prompt":"rate limit /login per account and per ip, with a lockout that doesn't let an attacker lock out a victim","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Walk through NorthstarBasilRunnerStore's segment.rs","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"Please resist widening this one: NorthstarHarborIndexService works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarHarborIndexService\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"We expect DovetailAmberFilterService to outgrow its current Terraform arrangement next quarter, but changing everything at once would be risky. 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- make rollback possible without deleting user data\n- stay compatible with the existing Terraform deployment\n- keep the work scoped to DovetailAmberFilterService and its direct tests\n\nThis repository spans game tooling, data pipelines, macOS; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"core","lang":"en"} -{"prompt":"Polish the DovetailCopperBridgeStore toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"boundary","lang":"en"} +{"prompt":"Walk through NorthstarBasilRunnerStore's segment.rs","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Please resist widening this one: NorthstarHarborIndexService works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarHarborIndexService\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"We expect DovetailAmberFilterService to outgrow its current Terraform arrangement next quarter, but changing everything at once would be risky. 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- make rollback possible without deleting user data\n- stay compatible with the existing Terraform deployment\n- keep the work scoped to DovetailAmberFilterService and its direct tests\n\nThis repository spans game tooling, data pipelines, macOS; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Find whatever broke rendering","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"Consolidate the three serializers without output changes and document the new extension point for plugin authors.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.67,"slice":"mixed","lang":"en"} -{"prompt":"Is there a cleaner way to separate OvertureCinderAuthService'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.53,"slice":"core","lang":"en"} -{"prompt":"and now?","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Give the diff minimap clearer contrast","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"make the battle screen cooler","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"vague-eval","lang":"en"} -{"prompt":"plan the sdk story — do we hand write three sdks or generate from openapi. include the maintenance cost and how idiomatic the generated ones would be","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Is there a cleaner way to separate OvertureCinderAuthService'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":"Give the diff minimap clearer contrast","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"make the battle screen cooler","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"plan the sdk story — do we hand write three sdks or generate from openapi. include the maintenance cost and how idiomatic the generated ones would be","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"materialized view for the daily metrics with a concurrent refresh, and a job that refreshes it every 15 min","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"BorealGarnetModalCoordinator: check the suspicious part","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"vague-eval","lang":"en"} -{"prompt":"Enable `STRICT_CSP_REPORTING`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"explain how our netcode handles packet loss right now — is there any redundancy or is it pure reliable-ordered over enet","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Add a clear visual distinction between inherited and explicitly granted permissions.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"Release verification found a single stale BorealKiteSchedulerService value; the cause, desired value, and affected assertion are already agreed. 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- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current GraphQL operational envelope\n\nThe relevant code crosses computer vision, React, PostgreSQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.28,"slice":"core","lang":"en"} -{"prompt":"prism design system: build the Button with variants, sizes, loading state, and icon slots. it needs to work as a link too without duplicating styles","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"PM needs a concise migration note for DovetailIrisBatchFlow, including the user impact, rollback trigger, and the one configuration key operators must change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"boundary","lang":"en"} -{"prompt":"Fix `recomendation` in `features.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} -{"prompt":"Trace DovetailAcornWidgetService's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"take a look at the caching layer and clean up the naming while you're in there","purpose":"review","secondary":"refactor","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} -{"prompt":"The behavior of EquinoxCloudReconcilerService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/equinox/lib/codec/frame.cc. 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- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current PostgreSQL 17 operational envelope\n\nThe relevant code crosses identity, Rust CLI, Vue. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.49,"slice":"core","lang":"en"} -{"prompt":"and stop there","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Two asks around EquinoxMosaicGridCoordinator: (1) produce a consumer guide for EquinoxMosaicGridCoordinator; (2) give the existing implementation a read-only safety pass. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.53,"slice":"mixed","lang":"en"} -{"prompt":"the device hard faults after about 12 hours and the fault handler doesn't give me a useful pc","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"BorealGarnetModalCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Enable `STRICT_CSP_REPORTING`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"explain how our netcode handles packet loss right now — is there any redundancy or is it pure reliable-ordered over enet","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Add a clear visual distinction between inherited and explicitly granted permissions.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Release verification found a single stale BorealKiteSchedulerService value; the cause, desired value, and affected assertion are already agreed. 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- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current GraphQL operational envelope\n\nThe relevant code crosses computer vision, React, PostgreSQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"prism design system: build the Button with variants, sizes, loading state, and icon slots. it needs to work as a link too without duplicating styles","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"PM needs a concise migration note for DovetailIrisBatchFlow, 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":"Fix `recomendation` in `features.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"DovetailLedgerGateCoordinator: polish, then correct","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Rename `ThreadSub` to `ThreadSubscription` across clients while preserving wire fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Trace DovetailAcornWidgetService's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"take a look at the caching layer and clean up the naming while you're in there","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"The behavior of EquinoxCloudReconcilerService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/equinox/lib/codec/frame.cc. 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- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current PostgreSQL 17 operational envelope\n\nThe relevant code crosses identity, Rust CLI, Vue. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Two asks around EquinoxMosaicGridCoordinator: (1) produce a consumer guide for EquinoxMosaicGridCoordinator; (2) give the existing implementation a read-only safety pass. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"the device hard faults after about 12 hours and the fault handler doesn't give me a useful pc","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Polish the Bluetooth permission sheet","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"fix the stock numbers","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"eh, next thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"rate limiter for the public api — tiered by plan, burst allowance, 429 with retry-after, and the counters can't be a single redis hot key","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"consolidate the three request-id header names we accept into one canonical, still accepting the legacy ones on input","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Summarize the current payroll-approval workflow for finance and audit reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"explain the difference between what the gateway rejects and what the service rejects, i want to know where a bad request actually dies","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"alright, stopping after this","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Symptom: The name pendingAck means two different things across HinterlandFrostPanelFlow's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"drift report ui: components with differences, the figma value against the code value, and a link to both","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"rate limiter for the public api — tiered by plan, burst allowance, 429 with retry-after, and the counters can't be a single redis hot key","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"consolidate the three request-id header names we accept into one canonical, still accepting the legacy ones on input","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Summarize the current payroll-approval workflow for finance and audit reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"explain the difference between what the gateway rejects and what the service rejects, i want to know where a bad request actually dies","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Symptom: The name pendingAck means two different things across HinterlandFrostPanelFlow's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"drift report ui: components with differences, the figma value against the code value, and a link to both","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Create a roadmap for cryptographic agility across stored data, network protocols, tokens, firmware signatures, and customer integrations. Include algorithm inventory, negotiation, downgrade prevention, test infrastructure, migration order, emergency replacement, and ownership.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} -{"prompt":"IsotopeCopperBridgeCoordinator: could this be clearer","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"vague-eval","lang":"en"} -{"prompt":"write the docs for the new `--profile` flag including how it interacts with the env vars and the config file, precedence order especially","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"finish the gateway API","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"Decouple GossamerSpruceDaemonService's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Cambia `gridRev` por `gridRevision` solo en `ForecastState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"es"} -{"prompt":"Assess how current API-key prefix matching behaves under collisions and whether full secrets are ever queried unnecessarily.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","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.4,"slice":"mixed","lang":"en"} -{"prompt":"FoxgloveSpruceDaemonCoordinator: could this be clearer","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"JunctionEmberRelayCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"vague-eval","lang":"en"} -{"prompt":"fix pairing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"replace the wp_options cache with the transients api used correctly, or a custom table, and clean up the 12k rows we've left behind","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the dedupe window is 15 minutes, needs to be 6 hours","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"Outline a phased architecture for moving claim documents from shared file storage to object storage, without implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.83,"slice":"boundary","lang":"en"} -{"prompt":"HinterlandKiteSchedulerCoordinator: clean up that old path","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"vague-eval","lang":"en"} -{"prompt":"Move token-hash comparison into a shared constant-time helper without changing supported formats.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Disable `ENABLE_OLD_MATCHMAKER`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"core","lang":"en"} -{"prompt":"eh, next","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"DovetailLumenChartCoordinator: the docs need something","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"vague-eval","lang":"en"} -{"prompt":"make it work like before","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.56,"slice":"vague-eval","lang":"en"} -{"prompt":"Rewrite the local setup for running HAPI FHIR, Orthanc, Kafka, and synthetic patient fixtures.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"Implement review-activity exports and write the integration documentation. Include filters, retention, asynchronous generation, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Why does FoxgloveVelaDrawerStore's Cloudflare Workers worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","lang":"en"} -{"prompt":"HinterlandMosaicGridCoordinator: take care of the warning","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"vague-eval","lang":"en"} -{"prompt":"Design a staged migration from node-local container caches to a regional registry mirror, including eviction, integrity, outage behavior, bandwidth estimates, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"en"} -{"prompt":"Split `AssessmentService` into session, response, timing, scoring, and publication components without changing behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} +{"prompt":"Check IsotopeVelaDrawerService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"IsotopeCopperBridgeCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"write the docs for the new `--profile` flag including how it interacts with the env vars and the config file, precedence order especially","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"finish the gateway API","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Decouple GossamerSpruceDaemonService's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Cambia `gridRev` por `gridRevision` solo en `ForecastState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"es"} +{"prompt":"Assess how current API-key prefix matching behaves under collisions and whether full secrets are ever queried unnecessarily.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","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":"FoxgloveSpruceDaemonCoordinator: could this be clearer","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"JunctionEmberRelayCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"fix pairing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"replace the wp_options cache with the transients api used correctly, or a custom table, and clean up the 12k rows we've left behind","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"the dedupe window is 15 minutes, needs to be 6 hours","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Outline a phased architecture for moving claim documents from shared file storage to object storage, without implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"HinterlandKiteSchedulerCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Move token-hash comparison into a shared constant-time helper without changing supported formats.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Disable `ENABLE_OLD_MATCHMAKER`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"DovetailLumenChartCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"make it work like before","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Rewrite the local setup for running HAPI FHIR, Orthanc, Kafka, and synthetic patient fixtures.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement review-activity exports and write the integration documentation. Include filters, retention, asynchronous generation, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Why does FoxgloveVelaDrawerStore's Cloudflare Workers worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"HinterlandMosaicGridCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Design a staged migration from node-local container caches to a regional registry mirror, including eviction, integrity, outage behavior, bandwidth estimates, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Split `AssessmentService` into session, response, timing, scoring, and publication components without changing behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Polish the review summary panel","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-43153\n\n08:02 deploy CalderaAsterWebhookCoordinator 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Capture the CalderaAsterWebhookCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} {"prompt":"plan our oauth support for the providers that offer it, so people stop needing app passwords","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"estrategia para migrar del monolito Django a servicios, tenemos 8 meses. quiero el orden de extracción y los riesgos, sin código todavía","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"es"} -{"prompt":"that's the last of it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Add reconnect tokens to the match gateway","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Review the current CRDT text implementation and explain how it prevents duplicate insertion after replay.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"back at it","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"After the tracing migration, this test intermittently times out:\n\n```text\nFAIL TestCaptureSpanLinksToAuthorization\nexpected one span link, found zero\ntrace authorization trace_id=0fa1 span_id=11ac sampled=true\nqueue message traceparent=00-0fa1-11ac-01\ncapture worker extracted trace_id=0fa1 parent=11ac\nexporter batch flush interval=5s\ncollector received capture span before authorization span\nquery by trace_id at t+2s returned capture only\nquery at t+7s returned both with link present\n```\n\nDetermine whether context propagation is wrong or the test assumes exporter ordering that is not guaranteed. Explain what evidence distinguishes ingestion delay from a missing link.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.69,"slice":"boundary","lang":"en"} -{"prompt":"picking the payment-flow bug back up. card declines show the generic \"something went wrong\" instead of the issuer message, but only for 3DS cards. i traced it as far as the webhook handler and got lost","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"slo definitions for the 6 tier-1 services, with the error budget policy and what happens when we burn it. i want the doc, not the dashboards","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Add reconnect tokens to the match gateway","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Review the current CRDT text implementation and explain how it prevents duplicate insertion after replay.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"After the tracing migration, this test intermittently times out:\n\n```text\nFAIL TestCaptureSpanLinksToAuthorization\nexpected one span link, found zero\ntrace authorization trace_id=0fa1 span_id=11ac sampled=true\nqueue message traceparent=00-0fa1-11ac-01\ncapture worker extracted trace_id=0fa1 parent=11ac\nexporter batch flush interval=5s\ncollector received capture span before authorization span\nquery by trace_id at t+2s returned capture only\nquery at t+7s returned both with link present\n```\n\nDetermine whether context propagation is wrong or the test assumes exporter ordering that is not guaranteed. Explain what evidence distinguishes ingestion delay from a missing link.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"picking the payment-flow bug back up. card declines show the generic \"something went wrong\" instead of the issuer message, but only for 3DS cards. i traced it as far as the webhook handler and got lost","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"SwiftUI settings screen for the notification prefs — grouped list, three toggles, a picker for quiet hours, matches the rest of the app's styling","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Plan and implement a live-operations configuration service. Begin with a design covering versioned events, segmentation, schedules, time zones, experiments, validation, emergency disable, client compatibility, audit, and rollout. Then add publication APIs, signed bundles, targeting, and conformance tests. Treat compatibility and safe activation as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.96,"slice":"mixed","lang":"en"} -{"prompt":"make the nav sticky","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"untangle yesterday's code","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"vague-eval","lang":"en"} -{"prompt":"Diagnose the duplicated suggestion row","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Investigate why the Android field app assigns a sensor reading to the previously selected sampling site.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"fix the map","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"error output uses ansi colors even when piped to a file","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"One contained cleanup in projects/keystone/workers/thumbnail/consumer.ex: remove the obsolete KeystoneOpalRouterService import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"core","lang":"en"} +{"prompt":"Plan and implement a live-operations configuration service. Begin with a design covering versioned events, segmentation, schedules, time zones, experiments, validation, emergency disable, client compatibility, audit, and rollout. Then add publication APIs, signed bundles, targeting, and conformance tests. Treat compatibility and safe activation as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"our cache eviction is a linear scan of 200k entries on insert","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"envelope encryption for the sensitive columns, kms-backed data keys cached in memory with a short ttl","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} +{"prompt":"make the nav sticky","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"untangle yesterday's code","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Diagnose the duplicated suggestion row","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Investigate why the Android field app assigns a sensor reading to the previously selected sampling site.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"fix the map","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"error output uses ansi colors even when piped to a file","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"One contained cleanup in projects/keystone/workers/thumbnail/consumer.ex: remove the obsolete KeystoneOpalRouterService import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"guide for writing a custom exporter, aimed at people who've never touched our internals","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Draft customer-facing release notes for bank-transfer payments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"NorthstarLedgerGateCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"vague-eval","lang":"en"} -{"prompt":"plan how we get this extension into the pgxn/apt/yum ecosystems so customers stop building from source","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Compare the old and new MeridianSableParserService adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Fix the clipped live badge and extract its repeated offset into the shared player styles.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.36,"slice":"mixed","lang":"en"} -{"prompt":"Add supplier name below the booking title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Renderer: The name pendingAck means two different things across MeridianDeltaCanvasStore's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"FoxgloveVelaDrawerCoordinator: the docs need something","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"vague-eval","lang":"en"} +{"prompt":"Draft customer-facing release notes for bank-transfer payments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"NorthstarSlateEditorCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"NorthstarLedgerGateCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"plan how we get this extension into the pgxn/apt/yum ecosystems so customers stop building from source","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Compare the old and new MeridianSableParserService 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":"Renderer: The name pendingAck means two different things across MeridianDeltaCanvasStore's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"the troubleshooting page needs a section on the 'sync stuck' state, what causes it and the three things a user can try","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Ownership of KeystoneRavenSessionService is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current gRPC operational envelope\n\nThe relevant code crosses collaboration, C++, Next.js. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Linear DATA-884: incremental customer aggregates\n\nThe dbt job recomputes every customer's lifetime totals each hour and now takes 94 minutes. Raw purchases are append-only in BigQuery except that refunds may arrive up to 45 days later. Implement an incremental model with these constraints:\n- output schema must remain analytics.customer_lifetime_value\n- recalculate affected customers when a purchase or refund changes\n- late events may be backfilled by date range\n- preserve currency conversion using the rate valid on transaction day\n- avoid full-table MERGE scans\n- expose counts for inserted, updated, and unchanged customers\n- tests need cases for duplicate events, late refunds, and reruns\n- downstream Looker explores cannot change this quarter\n\nExisting macros for partition pruning are in macros/incremental_windows.sql. Build the model and tests using project conventions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"set `strictNullChecks` true in tsconfig — just the flag, i'll deal with the fallout separately","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.15,"slice":"boundary","lang":"en"} -{"prompt":"LongbowSummitProxyCoordinator: could this be clearer","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"vague-eval","lang":"en"} -{"prompt":"docs for the config api — precedence rules, the reserved key prefixes, and what a null vs empty value means","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","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.64,"slice":"mixed","lang":"en"} -{"prompt":"What sequence would let BorealDeltaCanvasService adopt Cloudflare Workers 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.72,"slice":"core","lang":"en"} -{"prompt":"Why does the deployment agent retain the previous two manifests on disk? Explain the existing recovery behavior and storage tradeoff; no failure is reported.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.42,"slice":"boundary","lang":"en"} +{"prompt":"Ownership of KeystoneRavenSessionService is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current gRPC operational envelope\n\nThe relevant code crosses collaboration, C++, Next.js. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Linear DATA-884: incremental customer aggregates\n\nThe dbt job recomputes every customer's lifetime totals each hour and now takes 94 minutes. Raw purchases are append-only in BigQuery except that refunds may arrive up to 45 days later. Implement an incremental model with these constraints:\n- output schema must remain analytics.customer_lifetime_value\n- recalculate affected customers when a purchase or refund changes\n- late events may be backfilled by date range\n- preserve currency conversion using the rate valid on transaction day\n- avoid full-table MERGE scans\n- expose counts for inserted, updated, and unchanged customers\n- tests need cases for duplicate events, late refunds, and reruns\n- downstream Looker explores cannot change this quarter\n\nExisting macros for partition pruning are in macros/incremental_windows.sql. Build the model and tests using project conventions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"set `strictNullChecks` true in tsconfig — just the flag, i'll deal with the fallout separately","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"LongbowSummitProxyCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"docs for the config api — precedence rules, the reserved key prefixes, and what a null vs empty value means","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"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":"What sequence would let BorealDeltaCanvasService adopt Cloudflare Workers 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.8,"slice":"core","lang":"en"} +{"prompt":"Why does the deployment agent retain the previous two manifests on disk? Explain the existing recovery behavior and storage tradeoff; no failure is reported.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Build the Lit-based log viewer with virtual scrolling, search highlights, wrapping controls, and ANSI color support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Remove the extra dash from the lot label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"core","lang":"en"} -{"prompt":"do the thing we talked about with the queue","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"Implement reserve-revision history and write its API documentation. Include categories, approvals, accounting events, closure, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","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.65,"slice":"mixed","lang":"en"} -{"prompt":"diagnose the grpc UNAVAILABLE thing and then write the postmortem","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"Investigate why the Android barcode scanner sometimes associates a specimen with the previously opened order.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Plan the deprecation of the XML ingestion endpoint, covering usage discovery, customer communication, shadow parsing, parity metrics, and the date-based removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Implement signed match receipts with server generation and result digest.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"gpu memory fragments over a day of serving and eventually a request OOMs even though total usage is under 40%","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"the ISR does a printf. thats obviously bad but before i touch it — what's the actual failure mode here and why hasnt it bitten us yet","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"our #if PG_VERSION_NUM blocks appear in 30 files. collapse behind compat macros in one place, identical behavior per version","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"review what a malicious plugin can do to the host app and the user's machine as things stand","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"continue with search","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"vague-eval","lang":"en"} -{"prompt":"sdk reference docs — every method, params, the error types, and a section on retries and timeouts","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"the generated swift strings file isn't added to the xcode project so new strings silently fall back to the key","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Add GPX route simplification to `tracktool`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Checkout: The KeystoneEmberRelayFlow 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.17,"slice":"boundary","lang":"en"} +{"prompt":"Remove the extra dash from the lot label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Implement reserve-revision history and write its API documentation. Include categories, approvals, accounting events, closure, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Polish the EquinoxVelaDrawerService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"check whether a revoked key can still be used from a warm cache, and for how long","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"diagnose the grpc UNAVAILABLE thing and then write the postmortem","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Investigate why the Android barcode scanner sometimes associates a specimen with the previously opened order.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Plan the deprecation of the XML ingestion endpoint, covering usage discovery, customer communication, shadow parsing, parity metrics, and the date-based removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement signed match receipts with server generation and result digest.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"gpu memory fragments over a day of serving and eventually a request OOMs even though total usage is under 40%","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the ISR does a printf. thats obviously bad but before i touch it — what's the actual failure mode here and why hasnt it bitten us yet","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"our #if PG_VERSION_NUM blocks appear in 30 files. collapse behind compat macros in one place, identical behavior per version","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"review what a malicious plugin can do to the host app and the user's machine as things stand","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"sdk reference docs — every method, params, the error types, and a section on retries and timeouts","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"En projects/northstar/config/staging.toml, NorthstarNovaPickerStore tiene un problema intermitente en el flujo de GraphQL. Propón fases, compatibilidad, métricas, rollback y ownership; detente antes de tocar código.\n\nRestricciones:\n- seguir con GraphQL\n- conservar compatibilidad y cancelación\n- limitar el cambio a NorthstarNovaPickerStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con GraphQL alrededor de NorthstarNovaPickerStore.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"es"} +{"prompt":"the generated swift strings file isn't added to the xcode project so new strings silently fall back to the key","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Add GPX route simplification to `tracktool`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"decouple the pdf renderer from the web request lifecycle — it's currently reaching into flask's g for the tenant and i want it to take an explicit context object","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"# projects/equinox/internal/auth/refresh.go\n[worker.equinoxlumenchartflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.equinoxlumenchartflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.equinoxlumenchartflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.EquinoxLumenChartFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-45116\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/equinox/internal/auth/refresh.go and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.36,"slice":"pasted-context","lang":"en"} -{"prompt":"Add attempt pagination to `/v2/assignments`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Fix `medcation` in `codes.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} +{"prompt":"# projects/equinox/internal/auth/refresh.go\n[worker.equinoxlumenchartflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.equinoxlumenchartflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.equinoxlumenchartflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.EquinoxLumenChartFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-45116\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/equinox/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":"Add attempt pagination to `/v2/assignments`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Fix `medcation` in `codes.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"wasm module for the client-side image decoding, rust, exposed through a tiny js wrapper","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Implement build-action history and write its API documentation. Include inputs, digests, workers, cache status, pagination, retention, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Extract academic-term resolution into one shared module while preserving enrollment behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Merge the two ECS task-definition builders while preserving JSON output, environment ordering, and deployment behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"EquinoxRainfallDBCoordinator: give it a nicer flow","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"vague-eval","lang":"en"} -{"prompt":"DovetailBasilRunnerCoordinator: check the suspicious part","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"vague-eval","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new FHIR profile, including validation, search, examples, compatibility, and conformance tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.47,"slice":"core","lang":"en"} -{"prompt":"Create the desktop payroll-reconciliation workspace with expected payments, provider results, discrepancies, corrections, and export.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"FoxgloveJuniperCLICoordinator: ship, then document","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} +{"prompt":"Implement build-action history and write its API documentation. Include inputs, digests, workers, cache status, pagination, retention, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Extract academic-term resolution into one shared module while preserving enrollment behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the focus ring doesn't show on the icon buttons in the toolbar. keyboard users can't tell where they are","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"what does this regex do","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Merge the two ECS task-definition builders while preserving JSON output, environment ordering, and deployment behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"EquinoxRainfallDBCoordinator: give it a nicer flow","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"DovetailBasilRunnerCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new FHIR profile, including validation, search, examples, compatibility, and conformance tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Create the desktop payroll-reconciliation workspace with expected payments, provider results, discrepancies, corrections, and export.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"FoxgloveJuniperCLICoordinator: ship, then document","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} {"prompt":"the 30 report queries share 5 patterns with slight variations. build them from composable pieces, identical sql output — diff the generated queries to prove it","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"OvertureBirchMigratorCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"vague-eval","lang":"en"} -{"prompt":"thoughts?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"the thing from yesterday","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"summarize the work so far","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.31,"slice":"vague-eval","lang":"en"} -{"prompt":"read the routing code and tell me what happens to an in-flight request during a tenant move","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Any races in OvertureLedgerGateStore?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"AegisMosaicGridCoordinator: take care of the warning","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"the python and ts sdks name the same concepts differently (client vs session, list vs iterate). align the naming across both, keeping the old names as aliases","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Read projects/foxglove/Sources/App/SessionStore.swift and tell me whether FoxgloveWillowCodecService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Goal: Two asks around CalderaEmberRelayCoordinator: (1) change CalderaEmberRelayCoordinator's known staging timeout from 15 to 30 seconds; (2) capture the contract and rollback note for consumers. Do not introduce another runtime dependency, and leave a clear boundary between the resulting artifacts or edits.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.29,"slice":"mixed","lang":"en"} -{"prompt":"Nudge the minimap legend below the safe-area inset","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.14,"slice":"boundary","lang":"en"} -{"prompt":"Today: Incident timeline — INC-44120\n\n08:02 deploy DovetailJuniperCLIFlow 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 DovetailJuniperCLIFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Implement the dataset snapshot endpoint with filtering, signed download URLs, and retention enforcement, then document its request parameters, asynchronous states, examples, and failure responses for SDK authors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"HinterlandHarborIndexCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.45,"slice":"mixed","lang":"en"} -{"prompt":"FoxgloveMicaProfileCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"vague-eval","lang":"en"} -{"prompt":"Document the current refund API behavior, including partial refunds and idempotent retries.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"do the employee page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.39,"slice":"vague-eval","lang":"en"} -{"prompt":"Schreibe eine kurze Referenz für die bestehenden Match-Status und ihre Auswirkungen auf Verbindung, Ergebnis und Belohnung. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"de"} -{"prompt":"Create an operator guide for diagnosing bookings stuck in supplier confirmation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} -{"prompt":"Phrase the rationale for using two-phase deletion as an ADR; the design is already decided.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"boundary","lang":"en"} -{"prompt":"AegisSlateEditorCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"stop after this one","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Set the linker thread count to 8","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"here's the thing that's been driving me nuts:\n\n2026-07-28T14:22:09.114Z INFO [importer] batch 41 start rows=5000\n2026-07-28T14:22:09.882Z INFO [importer] batch 41 upserted=5000 skipped=0\n2026-07-28T14:22:10.004Z INFO [importer] batch 42 start rows=5000\n2026-07-28T14:22:41.229Z WARN [importer] batch 42 slow: 31.2s\n2026-07-28T14:22:41.230Z INFO [importer] batch 42 upserted=4998 skipped=2\n2026-07-28T14:22:41.401Z INFO [importer] batch 43 start rows=5000\n2026-07-28T14:22:42.109Z INFO [importer] batch 43 upserted=5000 skipped=0\n\nevery ~40th batch takes 30+ seconds and skips exactly 2 rows. the rest are sub-second. i've checked for hot keys, nothing obvious. skipped means the on-conflict did nothing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"JunctionBeaconStoreCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"vague-eval","lang":"en"} -{"prompt":"Test Suite 'KeystoneMoonlitSDKFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[KeystoneMoonlitSDKFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/keystone/pkg/cache/lease.rs:144: error: -[KeystoneMoonlitSDKFlowTests 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 '-[KeystoneMoonlitSDKFlowTests 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 KeystoneMoonlitSDKFlow'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.76,"slice":"pasted-context","lang":"en"} -{"prompt":"audit log for every permission change, who granted what to whom, immutable, and queryable by resource","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Implement signed filing receipts with document digests and policy version.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Memory attributed to DovetailDriftConsoleFlow rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Architect a multi-region live-video control plane with ingest ownership, failover, sequence continuity, rights, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"boundary","lang":"en"} -{"prompt":"make the course page inspiring","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.42,"slice":"vague-eval","lang":"en"} -{"prompt":"Architect a multi-region learning platform with institution ownership, course delivery, submissions, grades, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"boundary","lang":"en"} -{"prompt":"IsotopeAsterWebhookCoordinator: take care of the warning","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"vague-eval","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new feed candidate source, including filters, privacy, ranking, fixtures, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"KeystoneRainfallDBService's staging timeout is already known to be wrong: change the single projects/keystone/Sources/App/SessionStore.swift value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"core","lang":"en"} -{"prompt":"Wire a IsotopeFlintTimelineFlow background task in projects/isotope/services/ledger/replay.go that expires abandoned sessions, records an OpenTelemetry span, and yields cleanly when shutdown begins.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} +{"prompt":"OvertureBirchMigratorCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"read the routing code and tell me what happens to an in-flight request during a tenant move","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Any races in OvertureLedgerGateStore?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"j'aimerais un plan pour découper notre service de notifications en deux : l'envoi et les préférences. on a 40 endpoints et pas de tests d'intégration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"fr"} +{"prompt":"AegisMosaicGridCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"the python and ts sdks name the same concepts differently (client vs session, list vs iterate). align the naming across both, keeping the old names as aliases","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Read projects/foxglove/Sources/App/SessionStore.swift and tell me whether FoxgloveWillowCodecService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"MeridianCoralUploadService est-il sûr ?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"fr"} +{"prompt":"Goal: Two asks around CalderaEmberRelayCoordinator: (1) change CalderaEmberRelayCoordinator's known staging timeout from 15 to 30 seconds; (2) capture the contract and rollback note for consumers. Do not introduce another runtime dependency, and leave a clear boundary between the resulting artifacts or edits.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Today: Incident timeline — INC-44120\n\n08:02 deploy DovetailJuniperCLIFlow 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 DovetailJuniperCLIFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"何が原因でこのテストだけ CI で落ちるのか調べてほしい。ローカルでは通る。タイムゾーンかもしれないけど確証がない","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"ja"} +{"prompt":"Implement the dataset snapshot endpoint with filtering, signed download URLs, and retention enforcement, then document its request parameters, asynchronous states, examples, and failure responses for SDK authors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"HinterlandHarborIndexCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"FoxgloveMicaProfileCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Document the current refund API behavior, including partial refunds and idempotent retries.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"do the employee page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Schreibe eine kurze Referenz für die bestehenden Match-Status und ihre Auswirkungen auf Verbindung, Ergebnis und Belohnung. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"de"} +{"prompt":"Create an operator guide for diagnosing bookings stuck in supplier confirmation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Set the linker thread count to 8","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"here's the thing that's been driving me nuts:\n\n2026-07-28T14:22:09.114Z INFO [importer] batch 41 start rows=5000\n2026-07-28T14:22:09.882Z INFO [importer] batch 41 upserted=5000 skipped=0\n2026-07-28T14:22:10.004Z INFO [importer] batch 42 start rows=5000\n2026-07-28T14:22:41.229Z WARN [importer] batch 42 slow: 31.2s\n2026-07-28T14:22:41.230Z INFO [importer] batch 42 upserted=4998 skipped=2\n2026-07-28T14:22:41.401Z INFO [importer] batch 43 start rows=5000\n2026-07-28T14:22:42.109Z INFO [importer] batch 43 upserted=5000 skipped=0\n\nevery ~40th batch takes 30+ seconds and skips exactly 2 rows. the rest are sub-second. i've checked for hot keys, nothing obvious. skipped means the on-conflict did nothing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"JunctionBeaconStoreCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Test Suite 'KeystoneMoonlitSDKFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[KeystoneMoonlitSDKFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/keystone/pkg/cache/lease.rs:144: error: -[KeystoneMoonlitSDKFlowTests 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 '-[KeystoneMoonlitSDKFlowTests 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 KeystoneMoonlitSDKFlow's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"audit log for every permission change, who granted what to whom, immutable, and queryable by resource","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement signed filing receipts with document digests and policy version.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"sketch out how we'd support field selection (sparse fieldsets) without letting someone request a 40-way join","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Polish the shift summary card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Memory attributed to DovetailDriftConsoleFlow rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Architect a multi-region live-video control plane with ingest ownership, failover, sequence continuity, rights, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Prepare an API reference for payout status events","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Document NorthstarSableParserService's cancellation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the health page's upstream list is hardcoded","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"make the course page inspiring","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"quarantined tests stay quarantined forever because nobody looks at the list","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Architect a multi-region learning platform with institution ownership, course delivery, submissions, grades, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"IsotopeAsterWebhookCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"synchronous_commit is 'local' on the primary","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new feed candidate source, including filters, privacy, ranking, fixtures, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"KeystoneRainfallDBService's staging timeout is already known to be wrong: change the single projects/keystone/Sources/App/SessionStore.swift value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"crashes on launch for a handful of users on 18.4, never in the simulator. crashlytics gives me this and i'm lost:\n\nFatal Exception: NSInternalInconsistencyException\nModifying state during view update, this will cause undefined behavior.\n0 SwiftUI 0x1a2 closure #1 in AttributeGraph.withMutation + 412\n1 SwiftUI 0x1a2 StateBox.setValue(_:transaction:) + 88\n2 Kestrel 0x104 LibraryViewModel.reload() + 240 (LibraryViewModel.swift:118)\n3 Kestrel 0x104 closure #2 in LibraryView.body.getter + 96 (LibraryView.swift:64)\n4 SwiftUI 0x1a2 ViewGraph.updateOutputs + 1204\n5 UIKitCore 0x18f _UIUpdateSequenceRun + 84\n6 CoreFoundation 0x180 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 36\n\nLibraryViewModel.reload() is called from .task and from a NotificationCenter observer for .didFinishImport. no idea why only device builds","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Wire a IsotopeFlintTimelineFlow background task in projects/isotope/services/ledger/replay.go that expires abandoned sessions, records an OpenTelemetry span, and yields cleanly when shutdown begins.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"review everywhere our plugin writes to the database and tell me what it costs a site with 50k posts","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"explain the difference between the two ways we can be at 'limit exceeded' — the local token bucket and the global counter. which wins","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain the difference between the two ways we can be at 'limit exceeded' — the local token bucket and the global counter. which wins","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Consolidate three nearly identical iOS sheet coordinators without changing presentation order, dismissal callbacks, or deep-link behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Create the Compose robot-detail screen with mission, battery, pose confidence, alerts, logs, and TalkBack support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"build the reconciliation report: for every order in our db compare against the provider's settlement file, output the mismatches as csv with a reason code","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Introduce a schema migration for nullable warehouse_id on shipments, backfill it from route assignments, then enforce the foreign key.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Turn the current account-deletion behavior into user documentation, then review whether removal and retention claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Review excerpt:\n\n```diff\n async function approveWithdrawal(req) {\n- const simulation = await simulator.run(req.params.id)\n- if (!simulation.safe) throw new Error('unsafe transaction')\n- await approvals.record(req.user.id, simulation.digest)\n+ approvals.record(req.user.id, 'pending').catch(logger.warn)\n+ signer.enqueue(req.params.id)\n return { status: 'accepted' }\n }\n```\n\nThe author says simulation makes approval too slow. Review approval binding, asynchronous failure, transaction mutation, audit, authorization, and what accepted means. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Build a Python API for registering evaluation datasets with immutable versions, checksums, lineage, and role-based access.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"compare our current celery setup against just using postgres SKIP LOCKED for the job queue. we do maybe 200 jobs/min, mostly short","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"forecast methodology doc for the sales leadership: what each number means and the assumptions behind it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"CalderaBasilRunnerCoordinator: polish, then correct","purpose":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.61,"slice":"mixed","lang":"en"} -{"prompt":"Corrige apenas `departue` para `departure` no novo alerta.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"pt"} -{"prompt":"Inspect the payroll-export endpoint for formula injection, excessive scope, stale authorization, sensitive fields, and unbounded jobs.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"onwards, next thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Add transactional material ownership transfer between plants with inventory and genealogy checks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Implement version-aware policy history with endorsements, cancellations, reinstatements, and snapshots.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Refactoring brief copied from ENG-309:\n\nOld names:\nWorkspaceMember\nworkspace_member_id\nworkspace.membership.created\n/workspaces/{id}/members\n\nNew product terminology:\nOrganizationMember\norganization_member_id\norganization.membership.created\n/organizations/{id}/members\n\nCompatibility requirements:\n- existing REST paths remain available for two releases\n- old event names continue to decode\n- database columns are NOT renamed in this change\n- SDK aliases should be deprecated, not removed\n- metrics dashboards still query workspace_* labels\n- behavior and authorization rules stay identical\n\nPerform the terminology restructure across domain types, internal packages, API aliases, generated fixtures, and tests. Keep compatibility adapters explicit and avoid unrelated formatting.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} +{"prompt":"Create the Compose robot-detail screen with mission, battery, pose confidence, alerts, logs, and TalkBack support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"build the reconciliation report: for every order in our db compare against the provider's settlement file, output the mismatches as csv with a reason code","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Introduce a schema migration for nullable warehouse_id on shipments, backfill it from route assignments, then enforce the foreign key.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Turn the current account-deletion behavior into user documentation, then review whether removal and retention claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Review excerpt:\n\n```diff\n async function approveWithdrawal(req) {\n- const simulation = await simulator.run(req.params.id)\n- if (!simulation.safe) throw new Error('unsafe transaction')\n- await approvals.record(req.user.id, simulation.digest)\n+ approvals.record(req.user.id, 'pending').catch(logger.warn)\n+ signer.enqueue(req.params.id)\n return { status: 'accepted' }\n }\n```\n\nThe author says simulation makes approval too slow. Review approval binding, asynchronous failure, transaction mutation, audit, authorization, and what accepted means. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Build a Python API for registering evaluation datasets with immutable versions, checksums, lineage, and role-based access.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"compare our current celery setup against just using postgres SKIP LOCKED for the job queue. we do maybe 200 jobs/min, mostly short","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"BorealSlateEditorCoordinator: sequence, then polish","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"forecast methodology doc for the sales leadership: what each number means and the assumptions behind it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"CalderaBasilRunnerCoordinator: polish, then correct","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Corrige apenas `departue` para `departure` no novo alerta.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"pt"} +{"prompt":"Inspect the payroll-export endpoint for formula injection, excessive scope, stale authorization, sensitive fields, and unbounded jobs.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Remplace `Paiments` par `Payments` uniquement dans le nouveau titre de navigation.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"fr"} +{"prompt":"Before touching projects/overture/Sources/CLI/Commands/Doctor.swift, propose how to retire its legacy format while old clients remain active for ninety days and operators retain a reversible escape hatch. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add transactional material ownership transfer between plants with inventory and genealogy checks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement version-aware policy history with endorsements, cancellations, reinstatements, and snapshots.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Refactoring brief copied from ENG-309:\n\nOld names:\nWorkspaceMember\nworkspace_member_id\nworkspace.membership.created\n/workspaces/{id}/members\n\nNew product terminology:\nOrganizationMember\norganization_member_id\norganization.membership.created\n/organizations/{id}/members\n\nCompatibility requirements:\n- existing REST paths remain available for two releases\n- old event names continue to decode\n- database columns are NOT renamed in this change\n- SDK aliases should be deprecated, not removed\n- metrics dashboards still query workspace_* labels\n- behavior and authorization rules stay identical\n\nPerform the terminology restructure across domain types, internal packages, API aliases, generated fixtures, and tests. Keep compatibility adapters explicit and avoid unrelated formatting.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"the file tree in the sidebar needs multi-select with shift and cmd, and a right click menu that respects the selection","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"JunctionMarbleTokenCoordinator: rethink this area","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"the tool prints progress with \\r which looks broken in xcode's console","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"Before implementing demand-response automation, outline the control design for eligibility, schedules, opt-outs, grid signals, device safety, offline behavior, settlement evidence, and staged rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"boundary","lang":"en"} -{"prompt":"Fresh ticket plus acceptance notes:\n\n```text\nBILL-992 webhook reconciliation\nWhen our provider returns 202, it may deliver `invoice.settled` more than once and out of order with `invoice.updated`.\n\nCurrent tables:\nwebhook_receipts(provider_id unique, received_at, body)\ninvoices(id, account_id, state, amount_due, version)\n\nAcceptance:\n- HTTP handler acknowledges valid signatures within 250 ms\n- processing occurs asynchronously\n- duplicate provider IDs have no effect\n- an older invoice version cannot overwrite a newer one\n- poison events move to `billing-webhooks-dlq` after 8 attempts\n- expose counters for duplicate, stale, applied, and dead-lettered events\n- retain raw receipts for 30 days\n\nExisting entry point: `cmd/billing-api/webhooks.go`\n```\n\nImplement the handler, queue consumer, persistence operations, retry policy, and integration tests against Postgres.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"The CalderaCoralUploadService empty state in projects/caldera/web/components/FilterDrawer.vue needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"AegisBeaconStoreCoordinator: polish the last piece","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"vague-eval","lang":"en"} -{"prompt":"next thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Build the payment-link editor with live preview, expiration controls, branding, and localization-safe layout.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"our batch and streaming jobs compute the same aggregates with duplicated logic. share the transformation, and prove the outputs match on a day of data","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"JunctionKiteSchedulerCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"vague-eval","lang":"en"} -{"prompt":"Create the Compose field-observation form with site, variables, units, quality flags, offline queue, and TalkBack support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"finish the forms API","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"clean up and also make it faster","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"OvertureRavenSessionCoordinator: maybe tighten this up","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"vague-eval","lang":"en"} -{"prompt":"sidebar item spacing feels off, tighten it up a bit","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"Milestones for replacing FoxglovePineMetricsService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Create an operator guide for diagnosing filings stuck in signature validation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} -{"prompt":"Could the reasoning behind EquinoxTideWorkerFlow's WebGPU choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"en"} +{"prompt":"JunctionMarbleTokenCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"the tool prints progress with \\r which looks broken in xcode's console","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Before implementing demand-response automation, outline the control design for eligibility, schedules, opt-outs, grid signals, device safety, offline behavior, settlement evidence, and staged rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Fresh ticket plus acceptance notes:\n\n```text\nBILL-992 webhook reconciliation\nWhen our provider returns 202, it may deliver `invoice.settled` more than once and out of order with `invoice.updated`.\n\nCurrent tables:\nwebhook_receipts(provider_id unique, received_at, body)\ninvoices(id, account_id, state, amount_due, version)\n\nAcceptance:\n- HTTP handler acknowledges valid signatures within 250 ms\n- processing occurs asynchronously\n- duplicate provider IDs have no effect\n- an older invoice version cannot overwrite a newer one\n- poison events move to `billing-webhooks-dlq` after 8 attempts\n- expose counters for duplicate, stale, applied, and dead-lettered events\n- retain raw receipts for 30 days\n\nExisting entry point: `cmd/billing-api/webhooks.go`\n```\n\nImplement the handler, queue consumer, persistence operations, retry policy, and integration tests against Postgres.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"The CalderaCoralUploadService empty state in projects/caldera/web/components/FilterDrawer.vue needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"AegisBeaconStoreCoordinator: polish the last piece","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Build the payment-link editor with live preview, expiration controls, branding, and localization-safe layout.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"our batch and streaming jobs compute the same aggregates with duplicated logic. share the transformation, and prove the outputs match on a day of data","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the Compose field-observation form with site, variables, units, quality flags, offline queue, and TalkBack support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"finish the forms API","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"OvertureRavenSessionCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"sidebar item spacing feels off, tighten it up a bit","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Milestones for replacing FoxglovePineMetricsService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create an operator guide for diagnosing filings stuck in signature validation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Could the reasoning behind EquinoxTideWorkerFlow's WebGPU choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Create the mobile VPN connection screen with region selection, connection progress, failure recovery, and diagnostic export.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"finish the moderation API","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} -{"prompt":"Assess the proposed production-state cache for plant isolation, stale holds, quarantines, maintenance, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"error reference page for the api: code, http status, meaning, and whether retrying will help","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Give the reconnect banner a softer shadow and slide it below the navigation bar.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"Renderer: // projects/hinterland/db/migrations/20260730_events.sql\nfinal class HinterlandJuniperCLIFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandJuniperCLIFlow 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"content model for a page builder: sections with typed props, ordering, and per-section visibility rules","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Flip EquinoxLumenChartService's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"core","lang":"en"} -{"prompt":"the plugin host and the extension host are two implementations of the same sandbox with different capabilities. merge them, and enumerate any capability that changes for existing plugins","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"write the on-disk format spec — header layout, record framing, endianness, version negotiation. someone should be able to write a reader from this doc alone","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"FoxgloveNimbusFormCoordinator: smooth out this interaction","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"vague-eval","lang":"en"} -{"prompt":"Implement snapshot-consistent media catalog exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"meh, do the simple version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"JunctionCraneWorkspaceCoordinator: ship, then assess","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"finish the moderation API","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Assess the proposed production-state cache for plant isolation, stale holds, quarantines, maintenance, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"error reference page for the api: code, http status, meaning, and whether retrying will help","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Give the reconnect banner a softer shadow and slide it below the navigation bar.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Renderer: // projects/hinterland/db/migrations/20260730_events.sql\nfinal class HinterlandJuniperCLIFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandJuniperCLIFlow 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":"content model for a page builder: sections with typed props, ordering, and per-section visibility rules","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"Flip EquinoxLumenChartService's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"the plugin host and the extension host are two implementations of the same sandbox with different capabilities. merge them, and enumerate any capability that changes for existing plugins","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"write the on-disk format spec — header layout, record framing, endianness, version negotiation. someone should be able to write a reader from this doc alone","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"FoxgloveNimbusFormCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Implement snapshot-consistent media catalog exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"browser extension: content script that highlights our resource ids on any page and shows a hover card with the status","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"CalderaDriftConsoleService é seguro?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"pt"} {"prompt":"Assess whether our current S3 multipart cleanup job can delete an upload that is still receiving parts.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"explain the sync state machine and then write it up properly","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Rename `MasterItinerary` to `PrimaryItinerary` across services, events, tests, and dashboards while preserving public fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.64,"slice":"boundary","lang":"en"} -{"prompt":"Read the permission-matching engine and produce a maintainer guide explaining precedence and extension points.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"background sync via wp-cron with a proper lock so two overlapping runs can't both process the same batch","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Untangle the engine bits","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"do the feed page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.39,"slice":"vague-eval","lang":"en"} -{"prompt":"pick up the trust plan","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} -{"prompt":"the update manifest schema isn't documented anywhere and their IT is asking","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"GossamerCedarPolicyCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"vague-eval","lang":"en"} -{"prompt":"chase the robot auth issue","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} -{"prompt":"sync stuff again","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","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.88,"slice":"mixed","lang":"en"} -{"prompt":"segfault on the STM32 build after about 6 hours of uptime, always in the sensor task. stack is only 2k so i suspect overflow but the guard pattern is intact","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"Add bounded result caching with inventory-aware invalidation and request coalescing.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"the lag figure is in bytes and nobody knows whether 4MB is bad","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"Add bounded transaction replay for wallet-balance projections with checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Create the Compose code-review summary with checks, reviewers, change stats, merge controls, and TalkBack order.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Translate the DovetailPrismCacheStore setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"boundary","lang":"en"} -{"prompt":"Replace scattered match booleans with one explicit session lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"finish the compiler command","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.47,"slice":"vague-eval","lang":"en"} -{"prompt":"Before implementing electronic filing, outline the submission model for forms, attachments, validation, signatures, receipts, corrections, deadlines, outages, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"boundary","lang":"en"} -{"prompt":"Add Source RCON packet parsing to `serverctl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Build a responsive secrets-audit page with virtualized results, severity filters, code-location links, and keyboard-friendly triage controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Console: Ticket OPS-48119: retire the legacy replay path for HinterlandCloudReconcilerFlow\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 HinterlandCloudReconcilerFlow 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.67,"slice":"pasted-context","lang":"en"} -{"prompt":"GossamerRainfallDBCoordinator: the docs need something","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"vague-eval","lang":"en"} -{"prompt":"one small tweak","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.13,"slice":"vague-eval","lang":"en"} -{"prompt":"continue the architecture thing","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"vague-eval","lang":"en"} -{"prompt":"FYI: Ticket OPS-41112: retire the legacy replay path for AegisNovaPickerFlow\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 AegisNovaPickerFlow 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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"license key activation in the plugin, tolerant of an offline site, with a clear state when it can't reach us","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"onward then","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Consolidate learner-name formatting across gradebook and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"core","lang":"en"} -{"prompt":"Build the web transaction explorer with saved queries, virtualized rows, expandable ledger entries, and accessible amount formatting.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"typo in the analytics event name, 'chekout_started'. it's already in the warehouse so we need to keep emitting both for a bit","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"same as before pls","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Rename `MasterGateway` to `PrimaryGateway` across firmware, cloud services, metrics, and dashboards while preserving protocol values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"keep at it","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Give the patch notes screen readable typography","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.31,"slice":"core","lang":"en"} -{"prompt":"AegisFernSnapshotCoordinator: smooth out this interaction","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"vague-eval","lang":"en"} -{"prompt":"Set the typing indicator timeout to 5s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Corrige le timeout de NorthstarEmberRelayStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"boundary","lang":"fr"} -{"prompt":"Inspect the bulk-index endpoint for decompression bombs, oversized fields, tenant spoofing, and partial-failure ambiguity. Report only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"AegisQuartzPlayerCoordinator: ship a sensible version","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"vague-eval","lang":"en"} -{"prompt":"finish the streaming endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"Meanwhile: # projects/junction/lib/codec/frame.cc\n[worker.junctioncinderauthflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctioncinderauthflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctioncinderauthflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionCinderAuthFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50130\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 JunctionCinderAuthFlow'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.33,"slice":"pasted-context","lang":"en"} +{"prompt":"explain the sync state machine and then write it up properly","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Rename `MasterItinerary` to `PrimaryItinerary` across services, events, tests, and dashboards while preserving public fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"DovetailGarnetModalCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"background sync via wp-cron with a proper lock so two overlapping runs can't both process the same batch","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"do the feed page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"the update manifest schema isn't documented anywhere and their IT is asking","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"GossamerCedarPolicyCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"chase the robot auth issue","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","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":"segfault on the STM32 build after about 6 hours of uptime, always in the sensor task. stack is only 2k so i suspect overflow but the guard pattern is intact","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add bounded result caching with inventory-aware invalidation and request coalescing.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add bounded transaction replay for wallet-balance projections with checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the Compose code-review summary with checks, reviewers, change stats, merge controls, and TalkBack order.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Translate the DovetailPrismCacheStore setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Replace scattered match booleans with one explicit session lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Before implementing electronic filing, outline the submission model for forms, attachments, validation, signatures, receipts, corrections, deadlines, outages, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add Source RCON packet parsing to `serverctl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Build a responsive secrets-audit page with virtualized results, severity filters, code-location links, and keyboard-friendly triage controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Console: Ticket OPS-48119: retire the legacy replay path for HinterlandCloudReconcilerFlow\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 HinterlandCloudReconcilerFlow 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":"GossamerRainfallDBCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"one small tweak","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"FYI: Ticket OPS-41112: retire the legacy replay path for AegisNovaPickerFlow\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 AegisNovaPickerFlow 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":"license key activation in the plugin, tolerant of an offline site, with a clear state when it can't reach us","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Polish the appointment status card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Consolidate learner-name formatting across gradebook and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Build the web transaction explorer with saved queries, virtualized rows, expandable ledger entries, and accessible amount formatting.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"typo in the analytics event name, 'chekout_started'. it's already in the warehouse so we need to keep emitting both for a bit","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Rename `MasterGateway` to `PrimaryGateway` across firmware, cloud services, metrics, and dashboards while preserving protocol values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Give the patch notes screen readable typography","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"AegisFernSnapshotCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Set the typing indicator timeout to 5s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Inspect the bulk-index endpoint for decompression bombs, oversized fields, tenant spoofing, and partial-failure ambiguity. Report only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"AegisQuartzPlayerCoordinator: ship a sensible version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"finish the streaming endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Produce the architecture and milestone plan for moving mobile feature flags to signed local snapshots.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Meanwhile: # projects/junction/lib/codec/frame.cc\n[worker.junctioncinderauthflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctioncinderauthflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctioncinderauthflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionCinderAuthFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50130\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 JunctionCinderAuthFlow'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":"map out how we'd support ar viewing on top of the configurator, ios and android, and what the model requirements become","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Clean up that subsystem","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"hover state on the table rows is barely visible in dark mode, bump the contrast a notch","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.15,"slice":"boundary","lang":"en"} -{"prompt":"the extension crashes the backend on pg17 during a parallel scan, works fine serially","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Move NorthstarMoonlitSDKService behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Write the on-call guide for failed Argo rollouts","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"hover state on the table rows is barely visible in dark mode, bump the contrast a notch","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"the extension crashes the backend on pg17 during a parallel scan, works fine serially","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Move NorthstarMoonlitSDKService behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Write the on-call guide for failed Argo rollouts","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Build the Flutter Bluetooth pairing flow with scanning, permission education, PIN entry, retry states, and screen-reader support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"plan the api versioning scheme before we have customers, i don't want to be stuck","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Find why incremental type checking reports phantom duplicate symbols after renaming a file twice.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"OvertureMicaProfileCoordinator: polish the last piece","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"vague-eval","lang":"en"} -{"prompt":"check whether our service worker can serve a stale index.html after a deploy. i think it can but the caching code is dense","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Plan the retirement of our shared production Kubernetes cluster. Address workload inventory, dependency mapping, namespace ownership, data-plane migration, ingress cutover, IP allowlists, observability continuity, cost, rollback windows, and final decommission evidence.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Read the cluster drain controller and explain what prevents it from evicting quorum-critical pods.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Plan a disaster-recovery strategy for community services, including graph, content, media, moderation, search, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"DovetailWillowCodecCoordinator: smooth out this interaction","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} -{"prompt":"Download redesign notes:\n\n```text\nCurrent: one fixed 720p rendition, default audio, all captions\nNew need: viewer chooses quality and audio languages\nDownloads must remain playable when rights expire only if policy allows grace\nStorage estimate shown before confirmation\nPartial downloads resume by segment\nChanging device storage location invalidates open file handles\nDownloaded manifests must not expose origin URLs\nAccount logout deletes keys immediately and media later\nOld app versions understand only one audio track\n```\n\nProduce an implementation-free design and migration plan covering selection, rights, storage, resume, keys, logout, manifests, and compatibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"the firmware. we're on a stm32l4 with 256k flash and 64k ram, and we're at 240k flash. the feature list for next year needs another 60k. options: a bigger part (bom cost, and a redesign), compress assets, drop the usb stack, or actually optimize. write me the analysis with real numbers from the current map file","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Implement idempotent repair-estimate ingestion with version ordering and correction support.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Add a loading state to the assignment rows","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} +{"prompt":"plan the api versioning scheme before we have customers, i don't want to be stuck","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why incremental type checking reports phantom duplicate symbols after renaming a file twice.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"OvertureMicaProfileCoordinator: polish the last piece","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Plan the retirement of our shared production Kubernetes cluster. Address workload inventory, dependency mapping, namespace ownership, data-plane migration, ingress cutover, IP allowlists, observability continuity, cost, rollback windows, and final decommission evidence.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Read the cluster drain controller and explain what prevents it from evicting quorum-critical pods.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Plan a disaster-recovery strategy for community services, including graph, content, media, moderation, search, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Download redesign notes:\n\n```text\nCurrent: one fixed 720p rendition, default audio, all captions\nNew need: viewer chooses quality and audio languages\nDownloads must remain playable when rights expire only if policy allows grace\nStorage estimate shown before confirmation\nPartial downloads resume by segment\nChanging device storage location invalidates open file handles\nDownloaded manifests must not expose origin URLs\nAccount logout deletes keys immediately and media later\nOld app versions understand only one audio track\n```\n\nProduce an implementation-free design and migration plan covering selection, rights, storage, resume, keys, logout, manifests, and compatibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"the firmware. we're on a stm32l4 with 256k flash and 64k ram, and we're at 240k flash. the feature list for next year needs another 60k. options: a bigger part (bom cost, and a redesign), compress assets, drop the usb stack, or actually optimize. write me the analysis with real numbers from the current map file","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"Implement idempotent repair-estimate ingestion with version ordering and correction support.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add a loading state to the assignment rows","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Draft a migration guide for payroll partners moving from fixed-width files to the payroll API.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"look at the account linking logic and tell me if an attacker could link their oauth identity to someone else's account","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"make the thermostat app friendlier","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.42,"slice":"vague-eval","lang":"en"} -{"prompt":"audit event capture at the orm layer so no code path can skip it, with the diff stored as a compact json patch","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"reporting page shows a spinner then old data then new data, three states in two seconds. settle it down","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Iris: diff --git a/projects/caldera/db/migrations/20260730_events.sql b/projects/caldera/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/db/migrations/20260730_events.sql\n+++ b/projects/caldera/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure CalderaQuartzPlayerFlow 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Inspect the scenario-upload parser for path traversal, unsafe scripts, huge worlds, tenant confusion, and resource exhaustion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"the imap fetch requests full bodies for the message list","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"onward","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"CalderaOrbitSyncCoordinator: sort out the rough edge","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"vague-eval","lang":"en"} -{"prompt":"我们要把日志系统从 Loki 换成 ClickHouse，先写个方案：成本、查询延迟、迁移期间双写怎么做","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"zh"} -{"prompt":"HinterlandAtlasSearchCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"vague-eval","lang":"en"} -{"prompt":"make the quote page reassuring","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.42,"slice":"vague-eval","lang":"en"} -{"prompt":"does the code in workers/reaper.ts actually handle the case where the row was already deleted by another worker, or is it relying on the delete being idempotent by luck","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} +{"prompt":"look at the account linking logic and tell me if an attacker could link their oauth identity to someone else's account","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"make the thermostat app friendlier","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"audit event capture at the orm layer so no code path can skip it, with the diff stored as a compact json patch","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"reporting page shows a spinner then old data then new data, three states in two seconds. settle it down","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Fresh release brief for FoxgloveLedgerGateCoordinator:\n- primary outcome: produce a consumer guide for FoxgloveLedgerGateCoordinator\n- companion outcome: give the existing implementation a read-only safety pass\n- repository entry point: projects/foxglove/apps/console/routes/usage.svelte\n- platform constraint: Spring Boot\n- known complication: lease renewal code copied across three workers\n\nBoth results are required, but they should remain independently reviewable. Cover the awkward empty and retry states; 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":"writing","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Iris: diff --git a/projects/caldera/db/migrations/20260730_events.sql b/projects/caldera/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/db/migrations/20260730_events.sql\n+++ b/projects/caldera/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure CalderaQuartzPlayerFlow 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":"Polish the benefits summary card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Inspect the scenario-upload parser for path traversal, unsafe scripts, huge worlds, tenant confusion, and resource exhaustion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the imap fetch requests full bodies for the message list","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"CalderaOrbitSyncCoordinator: sort out the rough edge","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"the audit table has no index on the caseworker id","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"我们要把日志系统从 Loki 换成 ClickHouse，先写个方案：成本、查询延迟、迁移期间双写怎么做","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"zh"} +{"prompt":"HinterlandAtlasSearchCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"make the quote page reassuring","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"Build the tablet clip editor with trim handles, frame preview, captions, undo, export, and accessible controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"picking the feature store thing back up","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"BorealRavenSessionCoordinator: make this less weird","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"vague-eval","lang":"en"} -{"prompt":"migration compatibility checks in CI — flag any migration that the previous release's code couldn't tolerate","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"FoxgloveEmberRelayCoordinator: the screen feels unfinished","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"vague-eval","lang":"en"} -{"prompt":"Two deliverables are holding up KeystoneMarbleTokenCoordinator. First, assess ownership and failure handling in projects/keystone/app/src/main/SyncWorker.kt. In the same workstream, capture the contract and rollback note for consumers. The relevant starting point is projects/keystone/app/src/main/SyncWorker.kt, which follows gRPC conventions and currently suffers from out-of-order events after consumer rebalancing. Keep public behavior and serialized data unchanged.\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":"review","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"NorthstarAtlasSearchCoordinator: make the api less awkward","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"vague-eval","lang":"en"} -{"prompt":"IsotopeCloudReconcilerCoordinator: the screen feels unfinished","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"vague-eval","lang":"en"} +{"prompt":"BorealRavenSessionCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"migration compatibility checks in CI — flag any migration that the previous release's code couldn't tolerate","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"FoxgloveEmberRelayCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Two deliverables are holding up KeystoneMarbleTokenCoordinator. First, assess ownership and failure handling in projects/keystone/app/src/main/SyncWorker.kt. In the same workstream, capture the contract and rollback note for consumers. The relevant starting point is projects/keystone/app/src/main/SyncWorker.kt, which follows gRPC conventions and currently suffers from out-of-order events after consumer rebalancing. Keep public behavior and serialized data unchanged.\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":"review","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"NorthstarAtlasSearchCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Correct the IsotopeKiteSchedulerService flag default","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"IsotopeCloudReconcilerCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"Unify duplicated actor-context propagation while preserving tracing and audit fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Add a changelog entry describing the new webhook retry semantics and the one backward-incompatible timeout change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"do the cleanup from yesterday","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.42,"slice":"vague-eval","lang":"en"} -{"prompt":"Before touching projects/overture/crates/index/src/segment.rs, propose how to retire its legacy format while old clients remain active for ninety days and operators retain a reversible escape hatch. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"write a small CLI in rust, `envdiff`, that takes two .env files and prints keys only present in one, keys whose values differ, and exits 1 if there's any drift","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Change the little option","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"vague-eval","lang":"en"} -{"prompt":"continue the nonce bug","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.56,"slice":"vague-eval","lang":"en"} +{"prompt":"Add a changelog entry describing the new webhook retry semantics and the one backward-incompatible timeout change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"GossamerMapleQueueCoordinator: ship, then correct","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Before touching projects/overture/crates/index/src/segment.rs, propose how to retire its legacy format while old clients remain active for ninety days and operators retain a reversible escape hatch. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"write a small CLI in rust, `envdiff`, that takes two .env files and prints keys only present in one, keys whose values differ, and exits 1 if there's any drift","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"the copyright year in the footer is 2024","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Create an RFC for moving device telemetry from MQTT topics to a durable append-only log. Compare options and define migration stages, dual publication, ordering, retention, replay, device compatibility, cost, and operational ownership.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"boundary","lang":"en"} -{"prompt":"Drop JunctionSpruceDaemonService's unused import","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"core","lang":"en"} -{"prompt":"KeystoneSableParserCoordinator: handle the lingering thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"vague-eval","lang":"en"} -{"prompt":"our error messages say things like 'invalid input'. rewrite the user-facing copy for the 20 most common ones to say what to actually do","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"KeystoneGarnetModalCoordinator: take care of the warning","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"deploy view: rollout progress, canary metrics side by side with stable, and a promote/abort","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"The HinterlandCinderAuthStore 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.19,"slice":"boundary","lang":"en"} -{"prompt":"Set the autosave interval to 10s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} +{"prompt":"Polish the MFA method cards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Corrige le timeout de HinterlandDeltaCanvasStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"fr"} +{"prompt":"Create an RFC for moving device telemetry from MQTT topics to a durable append-only log. Compare options and define migration stages, dual publication, ordering, retention, replay, device compatibility, cost, and operational ownership.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Drop JunctionSpruceDaemonService's unused import","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"KeystoneSableParserCoordinator: handle the lingering thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"our error messages say things like 'invalid input'. rewrite the user-facing copy for the 20 most common ones to say what to actually do","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"KeystoneGarnetModalCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"deploy view: rollout progress, canary metrics side by side with stable, and a promote/abort","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"The HinterlandCinderAuthStore 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":"Set the autosave interval to 10s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"fastapi endpoint for bulk tag assignment, accepts up to 1000 ids, partial success reporting per id, all in one transaction per chunk","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"AegisCoralUploadCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"vague-eval","lang":"en"} -{"prompt":"Investigate flaky BLE pairing tests","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Implement the finalized module-resolution algorithm from specs/modules-v2.md.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"BorealSpruceDaemonCoordinator: could this be clearer","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"vague-eval","lang":"en"} -{"prompt":"the push token registration retries forever if the first attempt fails, cap it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"do the season page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.39,"slice":"vague-eval","lang":"en"} -{"prompt":"Add cursor pagination to `/v2/audit-events`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.36,"slice":"core","lang":"en"} -{"prompt":"make the profile more alive","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.41,"slice":"vague-eval","lang":"en"} +{"prompt":"AegisCoralUploadCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Investigate flaky BLE pairing tests","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"BorealSpruceDaemonCoordinator: could this be clearer","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"the push token registration retries forever if the first attempt fails, cap it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"do the season page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Add cursor pagination to `/v2/audit-events`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"make the profile more alive","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"Develop a safety architecture for remote robot commands over unreliable networks. Define authority, command expiry, sequencing, emergency-stop behavior, offline autonomy boundaries, authentication, auditability, simulator validation, degraded modes, rollout stages, and the evidence required before enabling commands outside a test fleet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} {"prompt":"Add a capacity-report command and document its flags, JSON schema, and automation examples.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"prod is being weird","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"vague-eval","lang":"en"} -{"prompt":"Put together the words","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} -{"prompt":"GossamerCraneWorkspaceCoordinator: smooth out this interaction","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"vague-eval","lang":"en"} -{"prompt":"Refactoring request from ledger team:\n\nposting/service.ts validates commands, converts currencies, builds entries, opens transactions, persists entries, updates cached balances, and publishes events. The reconciliation worker duplicates entry construction for imported settlements. Tests rely on exact entry order and error types.\n\nCreate explicit validation, entry-builder, and persistence boundaries; share the builder with reconciliation. Preserve transaction scope, journal ordering, rounding, public service methods, event payloads, balance timing, and every existing error code. This is structural work only—no new ledger states or processor behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"prod is being weird","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"our route handlers set cache headers ad hoc, some with `private` some not. centralize the policy, and list any route whose cacheability changes","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"GossamerCraneWorkspaceCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Refactoring request from ledger team:\n\nposting/service.ts validates commands, converts currencies, builds entries, opens transactions, persists entries, updates cached balances, and publishes events. The reconciliation worker duplicates entry construction for imported settlements. Tests rely on exact entry order and error types.\n\nCreate explicit validation, entry-builder, and persistence boundaries; share the builder with reconciliation. Preserve transaction scope, journal ordering, rounding, public service methods, event payloads, balance timing, and every existing error code. This is structural work only—no new ledger states or processor behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"feedback submissions from the widget lose the screenshot about a third of the time","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"GossamerEmberRelayCoordinator: restructure, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"Turn the existing feature freshness logic into a plain-language operations note with one concrete stale-data example.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why the React app loses its CSRF token after returning from the payment provider in a new tab.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} +{"prompt":"GossamerEmberRelayCoordinator: restructure, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Turn the existing feature freshness logic into a plain-language operations note with one concrete stale-data example.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Polish the HinterlandRavenSessionService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Investigate why the React app loses its CSRF token after returning from the payment provider in a new tab.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"polish the phone screen","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"and then that other thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"LongbowBeaconStoreCoordinator: polish the last piece","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"vague-eval","lang":"en"} -{"prompt":"ok so","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"LongbowBeaconStoreCoordinator: polish the last piece","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"do the auth screen","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"Finish the pipeline piece","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"What is the safest way to split projects/keystone/web/components/FilterDrawer.vue into independently owned modules while KeystoneGarnetModalService's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"just push it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} -{"prompt":"Implement roaring bitmap intersections","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"The data is already available in projects/overture/engine/render/atlas.cpp; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"boundary","lang":"en"} +{"prompt":"Finish the pipeline piece","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"En projects/meridian/ui/settings/PrivacyPane.tsx, MeridianBasilRunnerService tiene un problema intermitente en el flujo de SQLite. La causa ya está clara: cambia solo el timeout de staging de 15 a 30 segundos y ajusta su assertion.\n\nRestricciones:\n- seguir con SQLite\n- conservar compatibilidad y cancelación\n- limitar el cambio a MeridianBasilRunnerService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"es"} +{"prompt":"What is the safest way to split projects/keystone/web/components/FilterDrawer.vue into independently owned modules while KeystoneGarnetModalService's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Implement roaring bitmap intersections","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Replace `TermSvc` with `TerminologyService` across packages while preserving configuration and APIs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"add a ring buffer logger to the firmware that survives a reset and can be dumped over uart on boot. fixed 4KB in a noinit section","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Replace nested conditionals in `resolvePermissions` with named predicates and a flat decision flow. The returned permissions and audit reasons must not change.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.48,"slice":"core","lang":"en"} +{"prompt":"Replace nested conditionals in `resolvePermissions` with named predicates and a flat decision flow. The returned permissions and audit reasons must not change.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"need a design for group calls. currently p2p mesh which dies above 4 people. sfu vs mcu, self hosted vs a vendor, and what our bandwidth and cpu budget is per participant on a laptop. write it up with a recommendation","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Iris: Test Suite 'EquinoxEchoRegistryFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[EquinoxEchoRegistryFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/equinox/crates/index/src/segment.rs:144: error: -[EquinoxEchoRegistryFlowTests 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 '-[EquinoxEchoRegistryFlowTests 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\nFinish the visible EquinoxEchoRegistryFlow 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.73,"slice":"pasted-context","lang":"en"} -{"prompt":"Investigate why the player app briefly displays another account's inventory after profile switching.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} +{"prompt":"Iris: Test Suite 'EquinoxEchoRegistryFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[EquinoxEchoRegistryFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/equinox/crates/index/src/segment.rs:144: error: -[EquinoxEchoRegistryFlowTests 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 '-[EquinoxEchoRegistryFlowTests 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\nFinish the visible EquinoxEchoRegistryFlow 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":"Investigate why the player app briefly displays another account's inventory after profile switching.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Implement invoice PDF generation with deterministic layout inputs and immutable artifact versioning.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"so the thing where the list scrolls to top","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"Investigate why the Android scanner assigns a serial number to the previously selected pallet.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"EquinoxPineMetricsCoordinator: something is off here","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"vague-eval","lang":"en"} -{"prompt":"Figure out why builds are weird","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"add a `--json` output mode to every subcommand. one shared encoder, stable field names, and stderr stays human readable","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Add keyboard navigation to the shader graph editor","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"NorthstarCoralUploadCoordinator: clean up that old path","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"vague-eval","lang":"en"} +{"prompt":"so the thing where the list scrolls to top","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Investigate why the Android scanner assigns a serial number to the previously selected pallet.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"EquinoxPineMetricsCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Figure out why builds are weird","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"add a `--json` output mode to every subcommand. one shared encoder, stable field names, and stderr stays human readable","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add keyboard navigation to the shader graph editor","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create an operator guide for diagnosing claims stuck in coverage review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"NorthstarCoralUploadCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"Separate WAL serialization from file I/O while keeping the on-disk format and fsync ordering identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Responsive layout for AegisFlintTimelineStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"boundary","lang":"en"} +{"prompt":"Responsive layout for AegisFlintTimelineStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"the inference timeout is 2s and the p99 is 2.4s, raise it to 5","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"does our GDPR delete actually delete everything? trace a user id through every store including the analytics warehouse and the s3 exports","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} +{"prompt":"add `--json` to the status command, same data, machine readable","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"does our GDPR delete actually delete everything? trace a user id through every store including the analytics warehouse and the s3 exports","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Implement the editor viewport gizmos for translating spline control points with snapping and undo feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the date format string is MM/DD/YYYY in ExportPanel but everywhere else we use ISO, change it there too","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"add a .nvmrc with 22","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"PR body for the sprite atlas change, mention that artists need to re-export from the tool and link the new naming convention","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"finish that database command","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"rename the Tenant model to Workspace everywhere and update the docs that reference it","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"Consolidate engagement-count formatting across app and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"yesterday's grafana dashboard work — finish wiring the panels","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"PR body for the sprite atlas change, mention that artists need to re-export from the tool and link the new naming convention","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"rename the Tenant model to Workspace everywhere and update the docs that reference it","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Consolidate engagement-count formatting across app and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"yesterday's grafana dashboard work — finish wiring the panels","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"purchase verification against the store receipts so support can confirm a claimed purchase actually happened","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"write the customer-facing docs for rate limits: the numbers per plan, the headers, and the recommended backoff","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"our reconnect logic is implemented separately in the web client, the ios sdk and the android sdk, with different backoff. one specified behavior, implemented consistently","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"write the customer-facing docs for rate limits: the numbers per plan, the headers, and the recommended backoff","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"our reconnect logic is implemented separately in the web client, the ios sdk and the android sdk, with different backoff. one specified behavior, implemented consistently","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"our plan-gating checks are string comparisons against plan names in 60 places. move to a capability check, same gating for every existing plan","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"our ecto queries preload associations inconsistently, some with joins some with separate queries. standardize, and the returned data must be identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"our ecto queries preload associations inconsistently, some with joins some with separate queries. standardize, and the returned data must be identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Build a streaming JSON tokenizer that reports byte offsets and handles tokens split across arbitrary input chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Draft a migration guide for agencies moving from CSV notices to the notices API.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"Describe GossamerAcornWidgetService's error envelope","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"Give MeridianCedarPolicyService a loading skeleton","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Check IsotopeBeaconStoreService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} +{"prompt":"Draft a migration guide for agencies moving from CSV notices to the notices API.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Describe GossamerAcornWidgetService's error envelope","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"the Info.plist is missing NSMicrophoneUsageDescription and the app store rejected us","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Give MeridianCedarPolicyService a loading skeleton","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Check IsotopeBeaconStoreService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"PR description for the branch feat/multi-region-reads, include the migration steps ops needs to run and the rollback","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"IsotopeFrostPanelStore's openapi.yaml needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"one more pass on the importer","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"Design a migration from agency-specific applicant IDs to a federated identity graph, including confidence, privacy, merges, splits, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Corrige apenas `learner progres` para `learner progress` no novo título.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"pt"} -{"prompt":"NorthstarAmberFilterCoordinator: make this less weird","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"vague-eval","lang":"en"} -{"prompt":"Write release notes for parameter-sweep comparisons, including aggregation, missing runs, exports, and limits.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.36,"slice":"core","lang":"en"} -{"prompt":"Teach the settlement worker to checkpoint each provider page and resume safely after a process restart.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"One contained cleanup in projects/isotope/ui/settings/PrivacyPane.tsx: remove the obsolete IsotopeHarborIndexService import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"core","lang":"en"} -{"prompt":"EquinoxCoralUploadCoordinator: deal with the small issue","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"vague-eval","lang":"en"} -{"prompt":"Develop a roadmap for replacing repository webhooks with a durable integration event bus, including compatibility, replay, tenancy, and adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.87,"slice":"core","lang":"en"} -{"prompt":"JunctionMapleQueueCoordinator: polish the last piece","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"synthetic checks hitting our critical flows every minute from 3 regions, alerting only when 2 of 3 fail","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"sure, next","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"`Applicaton status` を `Application status` に直して。新しい英語見出しだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"ja"} -{"prompt":"search ui with the query parsed into visible chips so people can see how we interpreted it, and results that stream in","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"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] = [:]\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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Before implementing IPv6-only clusters, outline the networking design for DNS, service discovery, egress translation, load balancers, observability, developer access, and dual-stack migration.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"boundary","lang":"en"} -{"prompt":"Implement search analytics exports and write the integration guide. Include filters, anonymization, asynchronous generation, retention, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"eso, adelante","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"es"} -{"prompt":"Warum hängt LongbowDeltaCanvasStore?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","lang":"de"} -{"prompt":"Two asks around BorealCedarPolicyCoordinator: (1) find the unknown cause of two validators with subtly different error strings; (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":"debugging","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"please implement the matchmaking queue — mmr buckets that widen the longer you wait, parties up to 4, and a soft cap so a stack of 4 never faces 4 solos","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Why does the index builder sort products by ID before batching? Explain the current determinism and retry rationale.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.43,"slice":"boundary","lang":"en"} -{"prompt":"AegisVelaDrawerCoordinator: give it a nicer flow","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"continue the device cleanup","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} +{"prompt":"IsotopeFrostPanelStore's openapi.yaml needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Design a migration from agency-specific applicant IDs to a federated identity graph, including confidence, privacy, merges, splits, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Corrige apenas `learner progres` para `learner progress` no novo título.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"pt"} +{"prompt":"NorthstarAmberFilterCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Write release notes for parameter-sweep comparisons, including aggregation, missing runs, exports, and limits.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"LongbowMapleQueueCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Teach the settlement worker to checkpoint each provider page and resume safely after a process restart.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"One contained cleanup in projects/isotope/ui/settings/PrivacyPane.tsx: remove the obsolete IsotopeHarborIndexService import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"EquinoxCoralUploadCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Develop a roadmap for replacing repository webhooks with a durable integration event bus, including compatibility, replay, tenancy, and adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"JunctionMapleQueueCoordinator: polish the last piece","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"synthetic checks hitting our critical flows every minute from 3 regions, alerting only when 2 of 3 fail","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"`Applicaton status` を `Application status` に直して。新しい英語見出しだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"ja"} +{"prompt":"search ui with the query parsed into visible chips so people can see how we interpreted it, and results that stream in","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"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] = [:]\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":"Before implementing IPv6-only clusters, outline the networking design for DNS, service discovery, egress translation, load balancers, observability, developer access, and dual-stack migration.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement search analytics exports and write the integration guide. Include filters, anonymization, asynchronous generation, retention, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"IsotopeAtlasSearchService flakes under UTC","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Two asks around BorealCedarPolicyCoordinator: (1) find the unknown cause of two validators with subtly different error strings; (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":"debugging","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"please implement the matchmaking queue — mmr buckets that widen the longer you wait, parties up to 4, and a soft cap so a stack of 4 never faces 4 solos","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Why does the index builder sort products by ID before batching? Explain the current determinism and retry rationale.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"look at our error response shapes across endpoints and tell me how many distinct shapes we actually emit","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"OvertureBasilRunnerCoordinator: check the suspicious part","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"vague-eval","lang":"en"} -{"prompt":"keep going with telemetry","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.47,"slice":"vague-eval","lang":"en"} -{"prompt":"explain how our timezone handling works for aggregation — is a 'day' the store's day or utc","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"ok next","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"OvertureBasilRunnerCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"explain how our timezone handling works for aggregation — is a 'day' the store's day or utc","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Build the TUI test runner with live worker status, failure expansion, rerun shortcuts, and monochrome support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Create the responsive order-history search with filters, grouped results, empty states, and accessible dates.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"webhook receiver that revalidates the affected pages when content changes, with a fallback full rebuild nightly","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the responsive order-history search with filters, grouped results, empty states, and accessible dates.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"webhook receiver that revalidates the affected pages when content changes, with a fallback full rebuild nightly","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"build the ingest bit","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"runner dashboard: queue depth, runners by state, time-to-pickup, and the cost per hour","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Create the SwiftUI party finder with filters, player cards, join requests, blocks, pagination, and VoiceOver support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} +{"prompt":"runner dashboard: queue depth, runners by state, time-to-pickup, and the cost per hour","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Create the SwiftUI party finder with filters, player cards, join requests, blocks, pagination, and VoiceOver support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Change the default log level to info","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Draft the threat-model summary for third-party OAuth applications","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Plan and implement regional failover for the session store, including consistency decisions, rollout, metrics, and integration tests.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.92,"slice":"mixed","lang":"en"} -{"prompt":"Color the selected map marker with the existing accent token.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.16,"slice":"boundary","lang":"en"} -{"prompt":"localization guide for engineers: how to add a string, plural rules, what never to concatenate, and how to test a pseudo-locale","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"plan for handling schema changes in the mobile app's local db when users skip 4 versions","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"IsotopeCraneWorkspaceCoordinator: untangle the messy bit","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"vague-eval","lang":"en"} -{"prompt":"MeridianSableParserCoordinator: rethink this area","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"vague-eval","lang":"en"} -{"prompt":"one sec, actually the other file","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Plan and implement regional failover for the session store, including consistency decisions, rollout, metrics, and integration tests.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Color the selected map marker with the existing accent token.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"localization guide for engineers: how to add a string, plural rules, what never to concatenate, and how to test a pseudo-locale","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"plan for handling schema changes in the mobile app's local db when users skip 4 versions","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"IsotopeCraneWorkspaceCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"MeridianSableParserCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"the rabbit prefetch is unlimited on one consumer","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"our crypto helpers are spread across three modules with two different iv strategies. consolidate onto the correct one and re-encrypt nothing, just handle both on read","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Walk through BorealFernSnapshotStore's atlas.cpp","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"For MeridianSlateEditorCoordinator, lay out a staged migration for MeridianSlateEditorCoordinator; once that is complete, consolidate the duplicated normalization paths without changing behavior. Work from projects/meridian/infra/modules/edge/main.tf, stay with Tokio, and do not introduce another runtime dependency. Keep the two outcomes separately reviewable.","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.82,"slice":"mixed","lang":"en"} -{"prompt":"Write up the API stuff","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Why is HinterlandMicaProfileService stalling?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} +{"prompt":"Walk through BorealFernSnapshotStore's atlas.cpp","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"For MeridianSlateEditorCoordinator, lay out a staged migration for MeridianSlateEditorCoordinator; once that is complete, consolidate the duplicated normalization paths without changing behavior. Work from projects/meridian/infra/modules/edge/main.tf, stay with Tokio, and do not introduce another runtime dependency. Keep the two outcomes separately reviewable.","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Write up the API stuff","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Why is HinterlandMicaProfileService stalling?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"read scripts/deploy.sh line by line and tell me what it does if the health check never passes","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Document the policy-bundle signature envelope and implement its verifier in the edge agent.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"continue the weird crash work","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"$ pnpm test --filter GossamerIrisBatchFlow\n RUN v3.2.4 /workspace/apps/console\n × GossamerIrisBatchFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=47127 phase=resume storedCursor=seg-0183\n session=47127 phase=fetch requestCursor=seg-0183 pageSize=200\n session=47127 phase=commit receivedCursor=seg-0184 itemCount=0\n session=47127 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nReconstruct the GossamerIrisBatchFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.92,"slice":"pasted-context","lang":"en"} -{"prompt":"a tenant move left rows in both databases and the app read from both depending on the request","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"route map view: stops numbered along the path, drag to reorder with the eta updating, and a warning badge on windows we'd miss","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Produce an API reference for the Rust crate's public server types; no implementation changes.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.47,"slice":"boundary","lang":"en"} -{"prompt":"continue the notification cleanup","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.44,"slice":"vague-eval","lang":"en"} -{"prompt":"continue the scheduler cleanup","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.44,"slice":"vague-eval","lang":"en"} -{"prompt":"PM needs a concise migration note for MeridianEmberRelayStore, including the user impact, rollback trigger, and the one configuration key operators must change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Document EquinoxCinderAuthService's cancellation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} +{"prompt":"Document the policy-bundle signature envelope and implement its verifier in the edge agent.","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"$ pnpm test --filter GossamerIrisBatchFlow\n RUN v3.2.4 /workspace/apps/console\n × GossamerIrisBatchFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=47127 phase=resume storedCursor=seg-0183\n session=47127 phase=fetch requestCursor=seg-0183 pageSize=200\n session=47127 phase=commit receivedCursor=seg-0184 itemCount=0\n session=47127 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nReconstruct the GossamerIrisBatchFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"a tenant move left rows in both databases and the app read from both depending on the request","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"route map view: stops numbered along the path, drag to reorder with the eta updating, and a warning badge on windows we'd miss","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Produce an API reference for the Rust crate's public server types; no implementation changes.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"PM needs a concise migration note for MeridianEmberRelayStore, 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":"Document EquinoxCinderAuthService's cancellation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"tooltip should follow the cursor on the chart instead of snapping to the nearest point","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"design the health data model then implement the aggregation service","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"the expression editor is a plain text input with no syntax highlighting or validation","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"BorealOrbitSyncCoordinator is blocking the next release because cancellation being swallowed at the repository boundary. I need two concrete outcomes from a single pass: assess ownership and failure handling in projects/boreal/crates/index/src/segment.rs, and capture the contract and rollback note for consumers. Use the existing Cloudflare Workers conventions in projects/boreal/crates/index/src/segment.rs; 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":"review","secondary":"writing","mixed":true,"difficulty":0.86,"slice":"mixed","lang":"en"} -{"prompt":"CalderaWrenExportCoordinator: give it a nicer flow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"vague-eval","lang":"en"} -{"prompt":"KeystoneOspreyJobCoordinator: clean up that old path","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} -{"prompt":"Failure report from the database fuzz suite:\n\nseed=817400193 operations=22817 page_size=4096\nop[22812] delete range [6f2200, 6f49ff]\nop[22813] checkpoint\nop[22814] crash after wal fsync before manifest rename\nop[22815] reopen\nop[22816] scan [6f0000, 6fffff]\nexpected 184 keys, got 187\nunexpected keys: 6f231a, 6f31cc, 6f4820\n\nThe three keys were covered by the range tombstone before the crash. Point deletes recover correctly. The WAL contains the range-delete record and a valid checksum, but the reopened memtable does not expose the tombstone. Determine which recovery or sequence-boundary rule loses it and fix the bug without changing the persisted WAL format.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"design the health data model then implement the aggregation service","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"the expression editor is a plain text input with no syntax highlighting or validation","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"CalderaWrenExportCoordinator: give it a nicer flow","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"KeystoneOspreyJobCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Failure report from the database fuzz suite:\n\nseed=817400193 operations=22817 page_size=4096\nop[22812] delete range [6f2200, 6f49ff]\nop[22813] checkpoint\nop[22814] crash after wal fsync before manifest rename\nop[22815] reopen\nop[22816] scan [6f0000, 6fffff]\nexpected 184 keys, got 187\nunexpected keys: 6f231a, 6f31cc, 6f4820\n\nThe three keys were covered by the range tombstone before the crash. Point deletes recover correctly. The WAL contains the range-delete record and a valid checksum, but the reopened memtable does not expose the tombstone. Determine which recovery or sequence-boundary rule loses it and fix the bug without changing the persisted WAL format.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"the plugin folder is under Program Files so plugins need admin to install","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"add a compact density option to the data grid — user setting, persists, rows go 44 -> 32 and the font drops a step","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Propose an architecture for claim-event analytics with privacy, late corrections, financial snapshots, model features, retention, and reproducibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"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":"Propose an architecture for claim-event analytics with privacy, late corrections, financial snapshots, model features, retention, and reproducibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Create an operator runbook for draining a NATS JetStream consumer, replaying a dead-letter subject, and confirming that lag has recovered.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Investigate why expired offers remain visible in saved-search results.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.61,"slice":"boundary","lang":"en"} -{"prompt":"Zephyr: Incident timeline — INC-49147\n\n08:02 deploy IsotopeOspreyJobFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current IsotopeOspreyJobFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"review our resolver's handling of a truncated response — do we retry over tcp or return partial results","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"FoxgloveCinderAuthCoordinator: clean up that old path","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"vague-eval","lang":"en"} -{"prompt":"Investigate why site transfers leave robots subscribed to old map updates, implement the verified routing fix, and update operator docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} +{"prompt":"Investigate why expired offers remain visible in saved-search results.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Zephyr: Incident timeline — INC-49147\n\n08:02 deploy IsotopeOspreyJobFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current IsotopeOspreyJobFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"review our resolver's handling of a truncated response — do we retry over tcp or return partial results","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"FoxgloveCinderAuthCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Investigate why site transfers leave robots subscribed to old map updates, implement the verified routing fix, and update operator docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"table has 80M rows and no partitioning. plan the move to monthly partitions with no downtime, including how we handle the existing indexes and the fk from line_items","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"sigue nomás","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"es"} -{"prompt":"BorealPrismCacheCoordinator: the docs need something","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"vague-eval","lang":"en"} -{"prompt":"Propose an architecture for predictive-maintenance data, including sensor ingestion, asset identity, features, models, work orders, explanations, feedback, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"core","lang":"en"} -{"prompt":"把新页面里的 `Permisions` 改成 `Permissions`，不要改 i18n key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"zh"} -{"prompt":"the device stops responding to i2c after a specific sensor error, and only a power cycle recovers it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"some uploads produce a manifest with a 0-duration segment at the end and safari refuses to play it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the device code is 4 digits, that's not enough entropy","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"address autocomplete integration with a fallback to manual entry, and normalize what we store so the shipping label doesn't break","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"language reference for our config format: syntax, the type system, the standard functions, and the evaluation semantics","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Review excerpt:\n\n```diff\n async function getPayslip(req) {\n- const allowed = await payroll.canView(req.user, req.params.employeeId)\n- if (!allowed) throw forbidden()\n- return payslips.load(req.params.id)\n+ const slip = await payslips.load(req.params.id)\n+ payroll.canView(req.user, slip.employeeId).catch(logger.warn)\n+ return slip\n }\n```\n\nThe author says authorization checks slow document downloads. Review guessed IDs, former managers, tenant isolation, audit, caching, and asynchronous denial. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"pasted-context","lang":"en"} -{"prompt":"training loss goes to nan around step 3k, every time, same step give or take 50. lr is 3e-4 with warmup, grad clip at 1.0, bf16. i've tried lowering the lr and it just moves the cliff later","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"LongbowAmberFilterCoordinator: maybe tighten this up","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"vague-eval","lang":"en"} -{"prompt":"Set the plot export DPI to 300","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Test Suite 'HinterlandMapleQueueFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[HinterlandMapleQueueFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/hinterland/workers/thumbnail/consumer.ex:144: error: -[HinterlandMapleQueueFlowTests 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 '-[HinterlandMapleQueueFlowTests 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\nFinish the visible HinterlandMapleQueueFlow 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.76,"slice":"pasted-context","lang":"en"} -{"prompt":"The database recovery test hangs only when the final WAL record exactly fills a block. Locate the loop or boundary error.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Rédige une explication courte de l'API de pagination pour notre guide développeur, avec un exemple curl.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.34,"slice":"boundary","lang":"fr"} -{"prompt":"fix the permission thing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} -{"prompt":"Compare the old and new NorthstarCopperBridgeFlow adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"finish the workflow service","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"Ticket OPS-47118: retire the legacy replay path for GossamerEchoRegistryFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for GossamerEchoRegistryFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.65,"slice":"pasted-context","lang":"en"} -{"prompt":"DovetailSlateEditorCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.48,"slice":"mixed","lang":"en"} -{"prompt":"GossamerCloudReconcilerCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","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.53,"slice":"core","lang":"en"} -{"prompt":"Create the responsive creator analytics view with watch time, retention curves, filters, comparisons, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Add a subcommand that verifies Sigstore bundles offline using a supplied trust root and emits machine-readable results.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} +{"prompt":"the client grants the item locally before the server confirms","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"BorealPrismCacheCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Propose an architecture for predictive-maintenance data, including sensor ingestion, asset identity, features, models, work orders, explanations, feedback, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Match NorthstarMicaProfileService's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"把新页面里的 `Permisions` 改成 `Permissions`，不要改 i18n key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"zh"} +{"prompt":"NorthstarMicaProfileCoordinator: ship, then assess","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"the device stops responding to i2c after a specific sensor error, and only a power cycle recovers it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"some uploads produce a manifest with a 0-duration segment at the end and safari refuses to play it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"address autocomplete integration with a fallback to manual entry, and normalize what we store so the shipping label doesn't break","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Review excerpt:\n\n```diff\n async function getPayslip(req) {\n- const allowed = await payroll.canView(req.user, req.params.employeeId)\n- if (!allowed) throw forbidden()\n- return payslips.load(req.params.id)\n+ const slip = await payslips.load(req.params.id)\n+ payroll.canView(req.user, slip.employeeId).catch(logger.warn)\n+ return slip\n }\n```\n\nThe author says authorization checks slow document downloads. Review guessed IDs, former managers, tenant isolation, audit, caching, and asynchronous denial. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"training loss goes to nan around step 3k, every time, same step give or take 50. lr is 3e-4 with warmup, grad clip at 1.0, bf16. i've tried lowering the lr and it just moves the cliff later","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"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":"Set the plot export DPI to 300","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'HinterlandMapleQueueFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[HinterlandMapleQueueFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/hinterland/workers/thumbnail/consumer.ex:144: error: -[HinterlandMapleQueueFlowTests 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 '-[HinterlandMapleQueueFlowTests 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\nFinish the visible HinterlandMapleQueueFlow 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":"The database recovery test hangs only when the final WAL record exactly fills a block. Locate the loop or boundary error.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"fix the permission thing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Compare the old and new NorthstarCopperBridgeFlow adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"finish the workflow service","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Ticket OPS-47118: retire the legacy replay path for GossamerEchoRegistryFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for GossamerEchoRegistryFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"DovetailSlateEditorCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"GossamerCloudReconcilerCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"flagged frames upload at full resolution over the plant's saturated uplink","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","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":"Create the responsive creator analytics view with watch time, retention curves, filters, comparisons, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add a subcommand that verifies Sigstore bundles offline using a supplied trust root and emits machine-readable results.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the video player controls should auto hide after 3s of no interaction, fade not snap, and stay up while the scrubber is being dragged","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Clarify MeridianPineMetricsService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"Bump AegisLumenChartService's timeout to 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"core","lang":"en"} -{"prompt":"and that's the lot, wrap it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"# projects/aegis/web/components/FilterDrawer.vue\n[worker.aegisfrostpanelflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisfrostpanelflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisfrostpanelflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisFrostPanelFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41147\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/aegis/web/components/FilterDrawer.vue and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.38,"slice":"pasted-context","lang":"en"} -{"prompt":"Implement public-record publication history and write its API documentation. Include revisions, redactions, withdrawals, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Create the responsive creator dashboard with reach, engagement, audience, moderation status, filters, and accessible charts.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Escribe una guía para integrar nóminas, con empleados, tiempo, compensación, deducciones, pagos y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"es"} -{"prompt":"yeah that","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Clarify MeridianPineMetricsService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Bump AegisLumenChartService's timeout to 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"# projects/aegis/web/components/FilterDrawer.vue\n[worker.aegisfrostpanelflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisfrostpanelflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisfrostpanelflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisFrostPanelFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41147\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/aegis/web/components/FilterDrawer.vue and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Implement public-record publication history and write its API documentation. Include revisions, redactions, withdrawals, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Create the responsive creator dashboard with reach, engagement, audience, moderation status, filters, and accessible charts.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"replace the KEYS usage with SCAN wherever it appears, and add a lint rule so it can't come back","purpose":"refactor","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"toast notifications — stack up to 3, auto dismiss at 4s, pause the timer on hover, swipe to dismiss on touch. no libraries, we already have framer motion","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Pin golangci-lint to v2.3.0.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Create an operator guide for diagnosing delayed push notifications across providers and regions.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"continue the policy cleanup","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.44,"slice":"vague-eval","lang":"en"} -{"prompt":"the negative cache ttl comes from the SOA minimum which is 3600 for our zone","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"the pipeline configs use snake_case for column names in some yamls and camelCase in others. normalize on snake everywhere including the dbt models that reference them","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"DovetailNimbusFormCoordinator: untangle the messy bit","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"vague-eval","lang":"en"} -{"prompt":"Add subject-token validation and audience narrowing to the RFC 8693 exchange implementation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"BorealNovaPickerCoordinator: polish the last piece","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"vague-eval","lang":"en"} -{"prompt":"On compact widths, GossamerCloudReconcilerStore'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.46,"slice":"boundary","lang":"en"} -{"prompt":"We need to move HinterlandAcornWidgetFlow from the legacy store to React 19. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"GossamerJuniperCLICoordinator: why is this odd","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"vague-eval","lang":"en"} -{"prompt":"Why does the workflow service retain two previous container images after environment updates? Explain rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.46,"slice":"boundary","lang":"en"} -{"prompt":"HinterlandLumenChartCoordinator: the docs need something","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"vague-eval","lang":"en"} -{"prompt":"anomaly detection over the audit log — a caseworker viewing an unusual number of claims, or claims outside their caseload","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Find why the indexer retries permanent mapping errors forever and blocks its partition.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Create the desktop rights-policy editor with territories, windows, tiers, preview, conflicts, and validation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Find the cause of occasional NaNs in the Metal particle simulation after the app returns from the background.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Extract duplicated money rounding from settlement and invoicing into one decimal utility while preserving every currency-specific result.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"remove the `legacy_checkout` flag, its been 100% off for a year — delete both branches, keeping the off behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Outline a phased architecture for moving fleet telemetry from Cassandra to ClickHouse, without implementing ingestion or queries.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.85,"slice":"boundary","lang":"en"} -{"prompt":"Persist BorealCoralUploadService's replay cursor","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} +{"prompt":"Create an operator guide for diagnosing delayed push notifications across providers and regions.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"code splitting by route with prefetch on hover for the likely next routes","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the pipeline configs use snake_case for column names in some yamls and camelCase in others. normalize on snake everywhere including the dbt models that reference them","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"DovetailNimbusFormCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Add subject-token validation and audience narrowing to the RFC 8693 exchange implementation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"BorealNovaPickerCoordinator: polish the last piece","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"On compact widths, GossamerCloudReconcilerStore'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.6,"slice":"core","lang":"en"} +{"prompt":"We need to move HinterlandAcornWidgetFlow from the legacy store to React 19. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"GossamerJuniperCLICoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Why does the workflow service retain two previous container images after environment updates? Explain rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"HinterlandLumenChartCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"anomaly detection over the audit log — a caseworker viewing an unusual number of claims, or claims outside their caseload","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why the indexer retries permanent mapping errors forever and blocks its partition.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the desktop rights-policy editor with territories, windows, tiers, preview, conflicts, and validation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find the cause of occasional NaNs in the Metal particle simulation after the app returns from the background.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Extract duplicated money rounding from settlement and invoicing into one decimal utility while preserving every currency-specific result.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"HinterlandCopperBridgeCoordinator: sequence, then restructure","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"remove the `legacy_checkout` flag, its been 100% off for a year — delete both branches, keeping the off behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Outline a phased architecture for moving fleet telemetry from Cassandra to ClickHouse, without implementing ingestion or queries.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Persist BorealCoralUploadService's replay cursor","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"do the patient page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"cool cool","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"explain the ownership model in src/session — who's allowed to mutate a Session and when, because i keep getting borrow errors and i think i'm holding it wrong conceptually","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"make the docs decent","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.34,"slice":"vague-eval","lang":"en"} -{"prompt":"make the editor feel smarter","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"NorthstarMosaicGridCoordinator: check the suspicious part","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"vague-eval","lang":"en"} -{"prompt":"Implement workflow-template history and write its API documentation. Include versions, validation, publication, rollback, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Architect secure fleet-to-cloud communication for ten million intermittently connected devices. Cover identity, key rotation, routing, replay protection, protocol versions, revocation distribution, regional failure, manufacturing, observability, and incremental migration.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} -{"prompt":"Replace `PostRef` with `PostReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Move the shield icon 3px right.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"explain the ownership model in src/session — who's allowed to mutate a Session and when, because i keep getting borrow errors and i think i'm holding it wrong conceptually","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"make the editor feel smarter","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"NorthstarMosaicGridCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Implement workflow-template history and write its API documentation. Include versions, validation, publication, rollback, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Architect secure fleet-to-cloud communication for ten million intermittently connected devices. Cover identity, key rotation, routing, replay protection, protocol versions, revocation distribution, regional failure, manufacturing, observability, and incremental migration.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1,"slice":"core","lang":"en"} +{"prompt":"Summarize the current record-correction workflow for compliance reviewers using code and tests as sources.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Replace `PostRef` with `PostReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Move the shield icon 3px right.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Bump the Alpine image from 3.21 to 3.22","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Test Suite 'OvertureLedgerGateFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[OvertureLedgerGateFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/overture/crates/index/src/segment.rs:144: error: -[OvertureLedgerGateFlowTests 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 '-[OvertureLedgerGateFlowTests 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\nReconstruct the OvertureLedgerGateFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.92,"slice":"pasted-context","lang":"en"} -{"prompt":"keep it going","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"make the readme for the eval repo actually usable, right now it says 'run make'","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"GossamerLedgerGateCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"Diagnose why exported energy reports omit corrected intervals, implement the verified snapshot fix, and add a user-facing note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"CI: The NorthstarAmberFilterStore surface in projects/northstar/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.43,"slice":"boundary","lang":"en"} -{"prompt":"Assess the proposal to derive SLOs directly from trace data. Cover sampling bias, missing spans, tail latency, cost, and alert stability.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"why so slow","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Test Suite 'OvertureLedgerGateFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[OvertureLedgerGateFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/overture/crates/index/src/segment.rs:144: error: -[OvertureLedgerGateFlowTests 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 '-[OvertureLedgerGateFlowTests 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\nReconstruct the OvertureLedgerGateFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Polish the dataset summary card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"svelte transitions on the sidebar are janky on low-end android. currently animating width, i assume that's the problem but i want it smooth without changing the layout behavior","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"make the readme for the eval repo actually usable, right now it says 'run make'","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"GossamerLedgerGateCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Diagnose why exported energy reports omit corrected intervals, implement the verified snapshot fix, and add a user-facing note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"CI: The NorthstarAmberFilterStore surface in projects/northstar/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":"Assess the proposal to derive SLOs directly from trace data. Cover sampling bias, missing spans, tail latency, cost, and alert stability.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"why so slow","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"the scrubbing script and the seed script both fake user data with different rules. one faker module, same shapes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"把 `Employe profile` 改成 `Employee profile`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"zh"} +{"prompt":"Por que MeridianJuniperCLIService trava?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"pt"} {"prompt":"Walk me through the current rollback buffer ownership model and why snapshots use intrusive reference counts.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Create the responsive inventory-location view with bins, lots, quantities, holds, filters, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"n+1 queries all over the profile page. bullet is screaming. sort it out","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Web tooling ticket:\n\nThe CI trace viewer currently renders 50,000 spans as DOM rows and freezes Chrome. Replace the main pane with a virtualized timeline. Users need zoom, pan, text search, critical-path highlighting, worker-lane collapse, duration tooltips, and a details drawer. Selection must survive live trace updates. Provide a plain table fallback when reduced motion or assistive technology mode is enabled. The API already returns normalized spans; don't change it.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"the graphql schema has no descriptions on anything. add them, field by field, and be accurate about nullability semantics","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"pouvez-vous auditer notre bundle et me dire ce qui pourrait être supprimé sans rien casser ? juste une analyse","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"fr"} +{"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":"our export code has a hardcoded column list so custom fields never appear in exports","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Create the responsive inventory-location view with bins, lots, quantities, holds, filters, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"n+1 queries all over the profile page. bullet is screaming. sort it out","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the graphql schema has no descriptions on anything. add them, field by field, and be accurate about nullability semantics","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Plan a zero-downtime transition from one shared mobile API to region-specific endpoints. Include endpoint discovery, client-version compatibility, queued offline requests, authentication, data residency, failover, telemetry, staged routing, and rollback for clients that update slowly.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"bundle size tracking per PR with a comment showing the delta per chunk","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Explain why the current webhook verifier accepts two active signing secrets during rotation. Nothing is failing.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"the three.js scene leaks memory when you switch products, about 30mb each time","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"continue the offline strategy","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} -{"prompt":"Add quantity text below the lot title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"BorealMoonlitSDKCoordinator: make the api less awkward","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"vague-eval","lang":"en"} -{"prompt":"empty states across the six main screens with a single clear next action each, replacing the current 'no data' text","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"hero image is a 2.4mb png","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Explain why the current webhook verifier accepts two active signing secrets during rotation. Nothing is failing.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the three.js scene leaks memory when you switch products, about 30mb each time","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add quantity text below the lot title","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"BorealMoonlitSDKCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"empty states across the six main screens with a single clear next action each, replacing the current 'no data' text","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"our connection handling opens a transaction for read-only queries in half the endpoints. clean that up, same results, fewer write locks","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Add atomic capture splitting across multiple fulfillment shipments.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Review the device-log upload endpoint for tenant spoofing, secret leakage, decompression bombs, and unbounded retention.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Bump esbuild to 0.25.5","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"core","lang":"en"} -{"prompt":"The behavior of DovetailWrenExportService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/dovetail/apps/console/routes/usage.svelte. 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- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Playwright operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} +{"prompt":"Add atomic capture splitting across multiple fulfillment shipments.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Review the device-log upload endpoint for tenant spoofing, secret leakage, decompression bombs, and unbounded retention.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Bump esbuild to 0.25.5","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"The behavior of DovetailWrenExportService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/dovetail/apps/console/routes/usage.svelte. 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- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Playwright operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS 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":"second opinion on this hunk before i merge:\n\n@@ -41,15 +41,22 @@ func (s *Store) Claim(ctx context.Context, workerID string) (*Job, error) {\n-\trow := s.db.QueryRowContext(ctx, `\n-\t\tUPDATE jobs SET state='running', worker_id=$1, claimed_at=now()\n-\t\tWHERE id = (SELECT id FROM jobs WHERE state='queued' ORDER BY priority DESC, id LIMIT 1)\n-\t\tRETURNING id, payload`, workerID)\n+\ttx, err := s.db.BeginTx(ctx, nil)\n+\tif err != nil {\n+\t\treturn nil, err\n+\t}\n+\tdefer tx.Rollback()\n+\trow := tx.QueryRowContext(ctx, `\n+\t\tSELECT id, payload FROM jobs\n+\t\tWHERE state='queued' ORDER BY priority DESC, id\n+\t\tLIMIT 1 FOR UPDATE SKIP LOCKED`)\n \tvar j Job\n \tif err := row.Scan(&j.ID, &j.Payload); err != nil {\n \t\treturn nil, err\n \t}\n+\tif _, err := tx.ExecContext(ctx, `UPDATE jobs SET state='running', worker_id=$1, claimed_at=now() WHERE id=$2`, workerID, j.ID); err != nil {\n+\t\treturn nil, err\n+\t}\n+\treturn &j, tx.Commit()\n }","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Responsive layout for IsotopeAcornWidgetStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"boundary","lang":"en"} -{"prompt":"FoxgloveBasilRunnerCoordinator: take care of the warning","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"vague-eval","lang":"en"} -{"prompt":"audit our dependency tree for anything unmaintained or with known CVEs and give me the list ranked by how exposed we actually are, then patch the trivial ones","purpose":"review","secondary":"quickFix","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"docs for the playback api — the manifest urls, token expiry, and the drm handshake steps","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"the thing with the flags","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"Player release notes source:\n\n```text\nFeature: party join requests\nPlayers may request to join a friend's closed party\nParty leader can accept, deny, or ignore\nRequests expire after five minutes\nA player may have one active request per party\nAcceptance still checks party capacity, platform restrictions, and match state\nBlocked players cannot request or appear in the queue\nOld clients receive a standard invitation after acceptance\nRequests do not reserve a party slot\n```\n\nTurn this into release notes and a player help article with clear limits and compatibility behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"pasted-context","lang":"en"} -{"prompt":"nah do it the other way","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Responsive layout for IsotopeAcornWidgetStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"audit our dependency tree for anything unmaintained or with known CVEs and give me the list ranked by how exposed we actually are, then patch the trivial ones","purpose":"review","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"docs for the playback api — the manifest urls, token expiry, and the drm handshake steps","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Player release notes source:\n\n```text\nFeature: party join requests\nPlayers may request to join a friend's closed party\nParty leader can accept, deny, or ignore\nRequests expire after five minutes\nA player may have one active request per party\nAcceptance still checks party capacity, platform restrictions, and match state\nBlocked players cannot request or appear in the queue\nOld clients receive a standard invitation after acceptance\nRequests do not reserve a party slot\n```\n\nTurn this into release notes and a player help article with clear limits and compatibility behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} +{"prompt":"Replace `PatRef` with `PatientReference` across packages while preserving serialized field names and public aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Investigate delayed robot revocation, fix cache propagation, and document the revised consistency window.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new insurance product, including coverage, pricing, claims, documents, fixtures, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.48,"slice":"core","lang":"en"} -{"prompt":"Add bounded event replay for player-progression projections with checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Set the map tile cache to 2 GB","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","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.49,"slice":"boundary","lang":"en"} -{"prompt":"Fix `reservaton` in `events.proto`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} -{"prompt":"Gateway: diff --git a/projects/meridian/db/migrations/20260730_events.sql b/projects/meridian/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/db/migrations/20260730_events.sql\n+++ b/projects/meridian/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit MeridianQuartzPlayerFlow 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"explain how our app decides a plugin is trusted today, and whether the signature is verified or just present","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"MeridianIrisBatchCoordinator is blocking the next release because timestamps rendered one day ahead near UTC midnight. I need two concrete outcomes from a single pass: change MeridianIrisBatchCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing PostgreSQL 17 conventions in projects/meridian/packages/api/openapi.yaml; do not introduce another runtime dependency. 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.35,"slice":"mixed","lang":"en"} -{"prompt":"plan how we handle right-to-left in both apps given the shared layer knows nothing about layout direction","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Add content-hash deduplication to uploaded evidence with case-scoped ownership.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Is there a cleaner way to separate AegisOrbitSyncStore's transport, persistence, and retry policy without changing its API or timing behavior? Go ahead and make that structural change. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Could FoxgloveMarbleTokenFlow show the active Spring Boot sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"boundary","lang":"en"} -{"prompt":"FoxgloveBirchMigratorCoordinator: handle the lingering thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"vague-eval","lang":"en"} -{"prompt":"Could the reasoning behind OvertureMoonlitSDKService's gRPC choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"OvertureCinderAuthCoordinator: deal with the small issue","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"vague-eval","lang":"en"} -{"prompt":"Design the decommissioning process for an identity region. Deliver dependency inventory, session migration, key handling, routing, audit retention, rollback windows, and verification criteria rather than implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Remplace `Authorisation` par `Authorization` uniquement dans le nouveau libellé anglais; ne touche pas aux clés i18n.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"boundary","lang":"fr"} -{"prompt":"make checkout look trustworthy","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"finish the custody service","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"app store connect rejected the build for a privacy manifest thing, i don't understand what it wants:\n\nITMS-91053: Missing API declaration - Your app's code in the \"AcmeNotes\" file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryUserDefaults. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, you must include a NSPrivacyAccessedAPITypes array in your app's privacy manifest.\n\nITMS-91061: Missing privacy manifest - Your app includes \"Frameworks/SentrySwift.framework/SentrySwift\", which is a third-party SDK that requires a privacy manifest.\n\nwe do have a PrivacyInfo.xcprivacy, i added it last release","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} -{"prompt":"DovetailEchoRegistryCoordinator: make this less weird","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"LongbowKiteSchedulerCoordinator: clean up that old path","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"vague-eval","lang":"en"} +{"prompt":"Polish the invoice total section","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new insurance product, including coverage, pricing, claims, documents, fixtures, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add bounded event replay for player-progression projections with checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Set the map tile cache to 2 GB","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","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":"Fix `reservaton` in `events.proto`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Gateway: diff --git a/projects/meridian/db/migrations/20260730_events.sql b/projects/meridian/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/db/migrations/20260730_events.sql\n+++ b/projects/meridian/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit MeridianQuartzPlayerFlow 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":"explain how our app decides a plugin is trusted today, and whether the signature is verified or just present","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"MeridianIrisBatchCoordinator is blocking the next release because timestamps rendered one day ahead near UTC midnight. I need two concrete outcomes from a single pass: change MeridianIrisBatchCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing PostgreSQL 17 conventions in projects/meridian/packages/api/openapi.yaml; do not introduce another runtime dependency. 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":"plan how we handle right-to-left in both apps given the shared layer knows nothing about layout direction","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Em projects/caldera/packages/api/openapi.yaml, o CalderaIrisBatchStore tem um problema intermitente no fluxo de gRPC. Leia o fluxo atual e avalie ownership, cancelamento e ordem; preciso apenas da análise.\n\nRestrições:\n- continuar com gRPC\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao CalderaIrisBatchStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"pt"} +{"prompt":"Add content-hash deduplication to uploaded evidence with case-scoped ownership.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Is there a cleaner way to separate AegisOrbitSyncStore's transport, persistence, and retry policy without changing its API or timing behavior? Go ahead and make that structural change. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Could FoxgloveMarbleTokenFlow show the active Spring Boot sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"FoxgloveBirchMigratorCoordinator: handle the lingering thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Polish the crafting inventory grid","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Could the reasoning behind OvertureMoonlitSDKService's gRPC choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"OvertureCinderAuthCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Find the missing frames","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Design the decommissioning process for an identity region. Deliver dependency inventory, session migration, key handling, routing, audit retention, rollback windows, and verification criteria rather than implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Remplace `Authorisation` par `Authorization` uniquement dans le nouveau libellé anglais; ne touche pas aux clés i18n.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"fr"} +{"prompt":"make checkout look trustworthy","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"finish the custody service","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"vague-eval","lang":"en"} +{"prompt":"app store connect rejected the build for a privacy manifest thing, i don't understand what it wants:\n\nITMS-91053: Missing API declaration - Your app's code in the \"AcmeNotes\" file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryUserDefaults. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, you must include a NSPrivacyAccessedAPITypes array in your app's privacy manifest.\n\nITMS-91061: Missing privacy manifest - Your app includes \"Frameworks/SentrySwift.framework/SentrySwift\", which is a third-party SDK that requires a privacy manifest.\n\nwe do have a PrivacyInfo.xcprivacy, i added it last release","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"DovetailEchoRegistryCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"LongbowKiteSchedulerCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"Implement dataset-version pinning in the training scheduler and document how experiment authors opt in or migrate old runs.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"finish the route service","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} -{"prompt":"IsotopePineMetricsCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"vague-eval","lang":"en"} +{"prompt":"finish the route service","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"IsotopePineMetricsCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","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":"why is the mesh flickering","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"finish the FHIR service","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"EquinoxBeaconStoreCoordinator: polish the last piece","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"vague-eval","lang":"en"} -{"prompt":"Plan the retirement of legacy PDF vouchers, covering supplier requirements, digital documents, offline access, communication, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"en"} -{"prompt":"finish the grade API","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"Add elapsed time beside the live badge","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.24,"slice":"core","lang":"en"} -{"prompt":"Production: Incident timeline — INC-43119\n\n08:02 deploy CalderaCinderAuthFlow 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 CalderaCinderAuthFlow rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"is our retry schedule actually exponential? the numbers in the config look linear to me","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Worker: # projects/hinterland/workers/thumbnail/consumer.ex\n[worker.hinterlandnovapickerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandnovapickerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandnovapickerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandNovaPickerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48123\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 HinterlandNovaPickerFlow'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.41,"slice":"pasted-context","lang":"en"} -{"prompt":"Explain why the current firmware journal writes a commit marker to a separate flash page. Assume recovery works correctly.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Stream BorealFernSnapshotService's audit events","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Raven: // projects/meridian/app/src/main/SyncWorker.kt\nfinal class MeridianOrbitSyncFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianOrbitSyncFlow 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"In projects/aegis/ui/settings/PrivacyPane.tsx hat AegisOpalRouterService ein sporadisches Problem im NATS JetStream-Ablauf. Verfolge Queue, Scheduler und Abbruch, vergleiche Hypothesen und finde die Ursache vor jeder Änderung.\n\nRandbedingungen:\n- NATS JetStream weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf AegisOpalRouterService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um AegisOpalRouterService mit NATS JetStream kompatibel.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"de"} -{"prompt":"wrap up the thing from this morning","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"let's do the next one","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"plugin permission prompts at install time, enforced at runtime, and a way for the user to see what a plugin has accessed","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"A copied hex color in DovetailEmberRelayService lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"core","lang":"en"} -{"prompt":"Symptom: // projects/caldera/infra/modules/edge/main.tf\nfinal class CalderaMoonlitSDKFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 CalderaMoonlitSDKFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"check what our client does on an unexpected disconnect — reconnect backoff, state resync, and whether it can thundering-herd us","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-42112\n\n08:02 deploy BorealIrisBatchFlow 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 BorealIrisBatchFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.62,"slice":"pasted-context","lang":"en"} -{"prompt":"Write release notes for delegated leave approval, including scope, fallback approvers, expiry, and visibility.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.36,"slice":"core","lang":"en"} -{"prompt":"Review the OTA manifest parser for integer overflows, duplicate component names, and signature-verification ordering. Do not implement fixes.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"diff --git a/projects/caldera/lib/codec/frame.cc b/projects/caldera/lib/codec/frame.cc\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/lib/codec/frame.cc\n+++ b/projects/caldera/lib/codec/frame.cc\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure CalderaPineMetricsFlow 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.84,"slice":"pasted-context","lang":"en"} +{"prompt":"finish the FHIR service","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"vague-eval","lang":"en"} +{"prompt":"Plan the retirement of legacy PDF vouchers, covering supplier requirements, digital documents, offline access, communication, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"finish the grade API","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Add elapsed time beside the live badge","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Production: Incident timeline — INC-43119\n\n08:02 deploy CalderaCinderAuthFlow 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 CalderaCinderAuthFlow 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":"is our retry schedule actually exponential? the numbers in the config look linear to me","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Worker: # projects/hinterland/workers/thumbnail/consumer.ex\n[worker.hinterlandnovapickerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandnovapickerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandnovapickerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandNovaPickerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48123\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 HinterlandNovaPickerFlow'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":"Explain why the current firmware journal writes a commit marker to a separate flash page. Assume recovery works correctly.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the recovery job's report goes to a log file nobody reads","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Raven: // projects/meridian/app/src/main/SyncWorker.kt\nfinal class MeridianOrbitSyncFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianOrbitSyncFlow 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":"In projects/aegis/ui/settings/PrivacyPane.tsx hat AegisOpalRouterService ein sporadisches Problem im NATS JetStream-Ablauf. Verfolge Queue, Scheduler und Abbruch, vergleiche Hypothesen und finde die Ursache vor jeder Änderung.\n\nRandbedingungen:\n- NATS JetStream weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf AegisOpalRouterService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um AegisOpalRouterService mit NATS JetStream kompatibel.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} +{"prompt":"multi-threaded accept with SO_REUSEPORT, per-thread event loops, and no shared mutable state on the request path","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} +{"prompt":"plugin permission prompts at install time, enforced at runtime, and a way for the user to see what a plugin has accessed","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"A copied hex color in DovetailEmberRelayService lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Symptom: // projects/caldera/infra/modules/edge/main.tf\nfinal class CalderaMoonlitSDKFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 CalderaMoonlitSDKFlow; 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":"check what our client does on an unexpected disconnect — reconnect backoff, state resync, and whether it can thundering-herd us","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-42112\n\n08:02 deploy BorealIrisBatchFlow 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 BorealIrisBatchFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Write release notes for delegated leave approval, including scope, fallback approvers, expiry, and visibility.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"BorealCopperBridgeService flakes under UTC","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Review the OTA manifest parser for integer overflows, duplicate component names, and signature-verification ordering. Do not implement fixes.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/caldera/lib/codec/frame.cc b/projects/caldera/lib/codec/frame.cc\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/lib/codec/frame.cc\n+++ b/projects/caldera/lib/codec/frame.cc\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure CalderaPineMetricsFlow 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":"NorthstarVelaDrawerCoordinator needs a paired pass: separate NorthstarVelaDrawerCoordinator's policy from transport without behavior changes, plus give the existing implementation a read-only safety pass. Use projects/northstar/app/src/main/SyncWorker.kt as the source of truth, preserve the Kotlin coroutines contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Decouple GossamerMapleQueueStore's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"the async db session is created per request but the background tasks reuse it after the response, which is why we get those closed-session errors. i think. sort it out properly","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Summarize the OvertureCopperBridgeService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"just finish the last bit please","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Decouple GossamerMapleQueueStore's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the async db session is created per request but the background tasks reuse it after the response, which is why we get those closed-session errors. i think. sort it out properly","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Summarize the OvertureCopperBridgeService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Polish the AegisEchoRegistryService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"do the itinerary page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"Symptom: // projects/foxglove/web/components/FilterDrawer.vue\nfinal class FoxglovePineMetricsFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxglovePineMetricsFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Clarify IsotopeMapleQueueService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"We need to move EquinoxBeaconStoreService from the legacy store to Tokio. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Unify the OvertureQuartzPlayerService validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Build the mobile experiment-status screen with stages, resources, logs, outputs, cancellation, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Implement adaptive bitrate selection for the audio streamer using buffer health, throughput samples, and hysteresis.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Our support and SDK teams keep answering the same questions about IsotopeEchoRegistryStore, but the current prose in projects/isotope/lib/codec/frame.cc only describes the happy path. Draft an ADR plus migration note that records the decision, rejected alternatives, compatibility window, observability signals, and the exact action required from consumers.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing Tokio deployment\n- keep the work scoped to IsotopeEchoRegistryStore and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"next one","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Analytics pipeline incident:\n\n```text\njob=course-completion date=2026-07-29\nsource events=441,992\nprojection output completions=18,441\nlate event learner=s_88 lesson=l_12 completed_at=2026-07-28\nwatermark=2026-07-29T00:00Z\nlate event routed to correction topic\ncorrection consumer updates learner progress but not course completion aggregate\nlearner UI shows 100%; institutional report shows 92%\nquality check compares total learners, not cross-projection consistency\n```\n\nDetermine why correction handling updates only one projection and why existing quality checks miss the contradictory completion states.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Fix the clipped late badge and extract its duplicated offset into shared gradebook styles.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.35,"slice":"mixed","lang":"en"} +{"prompt":"Symptom: // projects/foxglove/web/components/FilterDrawer.vue\nfinal class FoxglovePineMetricsFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxglovePineMetricsFlow; 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":"Clarify IsotopeMapleQueueService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"We need to move EquinoxBeaconStoreService from the legacy store to Tokio. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Unify the OvertureQuartzPlayerService validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Build the mobile experiment-status screen with stages, resources, logs, outputs, cancellation, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement adaptive bitrate selection for the audio streamer using buffer health, throughput samples, and hysteresis.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Our support and SDK teams keep answering the same questions about IsotopeEchoRegistryStore, but the current prose in projects/isotope/lib/codec/frame.cc only describes the happy path. Draft an ADR plus migration note that records the decision, rejected alternatives, compatibility window, observability signals, and the exact action required from consumers.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing Tokio deployment\n- keep the work scoped to IsotopeEchoRegistryStore and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Analytics pipeline incident:\n\n```text\njob=course-completion date=2026-07-29\nsource events=441,992\nprojection output completions=18,441\nlate event learner=s_88 lesson=l_12 completed_at=2026-07-28\nwatermark=2026-07-29T00:00Z\nlate event routed to correction topic\ncorrection consumer updates learner progress but not course completion aggregate\nlearner UI shows 100%; institutional report shows 92%\nquality check compares total learners, not cross-projection consistency\n```\n\nDetermine why correction handling updates only one projection and why existing quality checks miss the contradictory completion states.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Fix the clipped late badge and extract its duplicated offset into shared gradebook styles.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} {"prompt":"Change the default output extension to .wasm","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Beacon: The next client release depends on a new JunctionFernSnapshotService capability in projects/junction/internal/auth/refresh.go, with GraphQL already chosen by the platform group. Implement the endpoint and durable cursor, enforce tenant authorization and idempotency, emit useful spans, cap work per request, and include focused tests for retries, cancellation, and malformed cursors.\n\nConstraints:\n- retain the existing CLI flags and exit codes\n- stay compatible with the existing GraphQL deployment\n- keep the work scoped to JunctionFernSnapshotService and its direct tests\n\nThis repository spans logistics, WebAssembly, MySQL; use its existing conventions rather than importing a new abstraction.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"streaming job falls behind by hours overnight then catches up by 9am. the input rate is flat","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Sketch a migration strategy for moving tenant preferences from Redis hashes into Postgres JSONB, including rollout phases, dual-write timing, backfill verification, rollback signals, and how older mobile clients remain compatible. I only need the design and milestone breakdown for now.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"en"} -{"prompt":"Issue UI-1842 context:\n\nCurrent component:\n\n\nQA notes:\n- at 200% browser zoom, clear button overlaps the final two characters\n- Windows high-contrast mode hides the magnify icon\n- focus ring gets clipped inside the data-grid toolbar\n- Escape should clear only when nonempty\n- RTL screenshot has icon and clear button on the wrong sides\n\nExpected snapshots:\nsearch-empty.png\nsearch-value.png\nsearch-focus.png\nsearch-rtl.png\nsearch-high-contrast.png\n\nPlease update packages/ui/src/SearchField.tsx and its CSS to handle these visual and interaction states. Retain the public props and add focused component tests for keyboard clearing and RTL placement.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} -{"prompt":"the actuator health endpoint is exposed on the public port, move it to the management port","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"the disk alert fires and resolves every 20 minutes all night. disk is at 71% and stable","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"AegisAcornWidgetCoordinator: rethink this area","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"Add transaction-level trace correlation to ledger postings without exposing financial data in attributes.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"continue the player cleanup","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.44,"slice":"vague-eval","lang":"en"} -{"prompt":"the fuzzer found a panic on an unterminated block comment","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","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":"boundary","lang":"en"} -{"prompt":"$ pnpm test --filter JunctionGarnetModalFlow\n RUN v3.2.4 /workspace/apps/console\n × JunctionGarnetModalFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=50124 phase=resume storedCursor=seg-0183\n session=50124 phase=fetch requestCursor=seg-0183 pageSize=200\n session=50124 phase=commit receivedCursor=seg-0184 itemCount=0\n session=50124 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nReconstruct the JunctionGarnetModalFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"Draft a support guide for restoring accidentally archived channels without losing thread history.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} -{"prompt":"Ticket copied from the collaboration backlog:\n\n```text\nMSG-3304 — scheduled channel messages\nUsers choose channel, message body, and delivery time\nMaximum horizon 90 days\nEditing creates a new immutable revision\nDeletion before delivery records an audit event\nPermissions are checked at creation and again at send time\nAttachments must still exist and remain accessible at delivery\nDuplicate scheduler claims must not send twice\nWorkspace time zone is display-only; store instants in UTC\nExpose scheduled, delivered, cancelled, failed, and permission-rejected metrics\n```\n\nImplement storage, CRUD commands, scheduler claims, send-time validation, attachment checks, audit events, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"fix the cards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.31,"slice":"vague-eval","lang":"en"} -{"prompt":"Separate firmware manifest parsing from validation while preserving accepted images and errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Merge duplicate lot-status types used by inventory and quality while preserving serialized values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Indexer: # projects/junction/workers/thumbnail/consumer.ex\n[worker.junctionslateeditorcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctionslateeditorcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctionslateeditorcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionSlateEditorCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50155\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/junction/workers/thumbnail/consumer.ex. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"pasted-context","lang":"en"} -{"prompt":"make the player cinematic","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.41,"slice":"vague-eval","lang":"en"} -{"prompt":"EquinoxHarborIndexCoordinator: handle the lingering thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"vague-eval","lang":"en"} -{"prompt":"plan how we detect a carrier silently dropping messages within minutes rather than at the monthly reconciliation","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"This should remain a deliberately small patch: KeystoneMarbleTokenStore has one known configuration mistake in projects/keystone/app/src/main/SyncWorker.kt, not an open-ended failure investigation. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing gRPC deployment\n- keep the work scoped to KeystoneMarbleTokenStore and its direct tests\n\nSeveral teams work in this collaboration, C++, Next.js monorepo, so keep ownership and handoff points understandable in a small review.\n\nThe cause and exact value change are already known, so keep this as a contained correction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.25,"slice":"boundary","lang":"en"} -{"prompt":"Adjust the account switcher so long organization names ellipsize before the chevron rather than pushing it outside the menu.","purpose":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.28,"slice":"mixed","lang":"en"} +{"prompt":"Beacon: The next client release depends on a new JunctionFernSnapshotService capability in projects/junction/internal/auth/refresh.go, with GraphQL already chosen by the platform group. Implement the endpoint and durable cursor, enforce tenant authorization and idempotency, emit useful spans, cap work per request, and include focused tests for retries, cancellation, and malformed cursors.\n\nConstraints:\n- retain the existing CLI flags and exit codes\n- stay compatible with the existing GraphQL deployment\n- keep the work scoped to JunctionFernSnapshotService and its direct tests\n\nThis repository spans logistics, WebAssembly, MySQL; use its existing conventions rather than importing a new abstraction.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"streaming job falls behind by hours overnight then catches up by 9am. the input rate is flat","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Sketch a migration strategy for moving tenant preferences from Redis hashes into Postgres JSONB, including rollout phases, dual-write timing, backfill verification, rollback signals, and how older mobile clients remain compatible. I only need the design and milestone breakdown for now.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Issue UI-1842 context:\n\nCurrent component:\n\n\nQA notes:\n- at 200% browser zoom, clear button overlaps the final two characters\n- Windows high-contrast mode hides the magnify icon\n- focus ring gets clipped inside the data-grid toolbar\n- Escape should clear only when nonempty\n- RTL screenshot has icon and clear button on the wrong sides\n\nExpected snapshots:\nsearch-empty.png\nsearch-value.png\nsearch-focus.png\nsearch-rtl.png\nsearch-high-contrast.png\n\nPlease update packages/ui/src/SearchField.tsx and its CSS to handle these visual and interaction states. Retain the public props and add focused component tests for keyboard clearing and RTL placement.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Set replicas to 3 in staging-values.yaml","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"the actuator health endpoint is exposed on the public port, move it to the management port","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the disk alert fires and resolves every 20 minutes all night. disk is at 71% and stable","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"AegisAcornWidgetCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Add transaction-level trace correlation to ledger postings without exposing financial data in attributes.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the fuzzer found a panic on an unterminated block comment","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","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":"$ pnpm test --filter JunctionGarnetModalFlow\n RUN v3.2.4 /workspace/apps/console\n × JunctionGarnetModalFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=50124 phase=resume storedCursor=seg-0183\n session=50124 phase=fetch requestCursor=seg-0183 pageSize=200\n session=50124 phase=commit receivedCursor=seg-0184 itemCount=0\n session=50124 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nReconstruct the JunctionGarnetModalFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Draft a support guide for restoring accidentally archived channels without losing thread history.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Ticket copied from the collaboration backlog:\n\n```text\nMSG-3304 — scheduled channel messages\nUsers choose channel, message body, and delivery time\nMaximum horizon 90 days\nEditing creates a new immutable revision\nDeletion before delivery records an audit event\nPermissions are checked at creation and again at send time\nAttachments must still exist and remain accessible at delivery\nDuplicate scheduler claims must not send twice\nWorkspace time zone is display-only; store instants in UTC\nExpose scheduled, delivered, cancelled, failed, and permission-rejected metrics\n```\n\nImplement storage, CRUD commands, scheduler claims, send-time validation, attachment checks, audit events, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"fix the cards","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Separate firmware manifest parsing from validation while preserving accepted images and errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Merge duplicate lot-status types used by inventory and quality while preserving serialized values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the import enqueues one job per row","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"make the player cinematic","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"plan how we detect a carrier silently dropping messages within minutes rather than at the monthly reconciliation","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Adjust the account switcher so long organization names ellipsize before the chevron rather than pushing it outside the menu.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"Add immutable provenance chains to calibrated satellite scenes.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Implement an OIDC authorization-code flow in Rust with PKCE, rotating refresh tokens, state validation, and session revocation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement an OIDC authorization-code flow in Rust with PKCE, rotating refresh tokens, state validation, and session revocation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"plan the api v3 surface and then implement the new list endpoints","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"KeystoneNimbusFormCoordinator: untangle the messy bit","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"vague-eval","lang":"en"} -{"prompt":"Rédige les notes de version 3.2 à partir du changelog, avec une section dédiée aux changements incompatibles.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"core","lang":"fr"} -{"prompt":"fix captions","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"our page titles are all 'Acme' — set them per route from the route metadata","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Write the dataset card for product-search-v5","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"handle it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Add a loading state to the mission cards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"the column totals sum the deal value including deals marked lost","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"IsotopeLedgerGateCoordinator: make this less weird","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"Review the migration diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} +{"prompt":"Rédige les notes de version 3.2 à partir du changelog, avec une section dédiée aux changements incompatibles.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"fr"} +{"prompt":"fix captions","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"our page titles are all 'Acme' — set them per route from the route metadata","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Write the dataset card for product-search-v5","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Add a loading state to the mission cards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Resume el flujo actual de alta de dispositivos como una guía para administradores, sin cambiar código.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} +{"prompt":"Bump grpc-go to 1.74.2","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"the column totals sum the deal value including deals marked lost","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"IsotopeLedgerGateCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Review the migration diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"failure notifications per workflow with a per-workflow recipient setting, and a digest rather than one email per failure","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"documents updated in the last few minutes sometimes don't appear in search and sometimes do. the indexer log shows them all as indexed","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"make the forms less governmenty","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.42,"slice":"vague-eval","lang":"en"} -{"prompt":"Fresh release brief for DovetailAcornWidgetCoordinator:\n- primary outcome: assess ownership and failure handling in projects/dovetail/engine/render/atlas.cpp\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/dovetail/engine/render/atlas.cpp\n- platform constraint: Terraform\n- known complication: an empty state that flashes before cached data arrives\n\nBoth results are required, but they should remain independently reviewable. Make rollback possible without deleting user data; 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.86,"slice":"mixed","lang":"en"} -{"prompt":"need docs for it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.32,"slice":"vague-eval","lang":"en"} -{"prompt":"Architecture request from the reliability review:\n\nOur internal package mirror depends on one regional object bucket, one PostgreSQL catalog, and a stateless metadata API. Builds in five regions fetch through local caching proxies. During the last outage, expired proxy entries caused every region to stampede the unavailable origin. Engineers bypassed the mirror, which broke provenance tracking. Security requires malware scanning before a package becomes visible and immediate quarantine when a later scan revokes it. Existing package URLs cannot change for two years.\n\nDesign a highly available mirror architecture and migration roadmap. Cover cache consistency, origin failover, catalog replication, upload sequencing, quarantine propagation, offline build policy, provenance, stampede controls, SLOs, disaster exercises, and phased rollout without changing current client URLs. No code requested.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Rename `MasterDocket` to `PrimaryDocket` across services, schemas, events, and dashboards while preserving public fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"Explain how the editor's semantic-token cache handles partial document updates and overlapping requests.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} +{"prompt":"documents updated in the last few minutes sometimes don't appear in search and sometimes do. the indexer log shows them all as indexed","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"make the forms less governmenty","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Fresh release brief for DovetailAcornWidgetCoordinator:\n- primary outcome: assess ownership and failure handling in projects/dovetail/engine/render/atlas.cpp\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/dovetail/engine/render/atlas.cpp\n- platform constraint: Terraform\n- known complication: an empty state that flashes before cached data arrives\n\nBoth results are required, but they should remain independently reviewable. Make rollback possible without deleting user data; 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.8,"slice":"mixed","lang":"en"} +{"prompt":"Sequence AegisGarnetModalService's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Rename `MasterDocket` to `PrimaryDocket` across services, schemas, events, and dashboards while preserving public fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"# CI job 48121: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: React 19\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] HinterlandTideWorkerFlowIntegration.replays_after_timeout ... ok\n[test] HinterlandTideWorkerFlowIntegration.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 \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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Add the bounded HinterlandTideWorkerFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Explain how the editor's semantic-token cache handles partial document updates and overlapping requests.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"language picker that remembers the choice per account, falls back to the browser preference, and doesn't flash english first","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"just get it working","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"Review the JWT verification path for algorithm confusion, duplicate claims, key selection, critical headers, and token-size limits. Report findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Release engineering needs a BorealFlintTimelineService changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Track down occasional missing serial numbers after pallet aggregation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Cambia `stepRev` por `stepRevision` solo en `BatchState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"es"} +{"prompt":"Review the JWT verification path for algorithm confusion, duplicate claims, key selection, critical headers, and token-size limits. Report findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Release engineering needs a BorealFlintTimelineService 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":"Track down occasional missing serial numbers after pallet aggregation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Build the package graph screen with cycle highlighting, version badges, edge filtering, and SVG export.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"tiny config thing pls","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"vague-eval","lang":"en"} -{"prompt":"Could KeystoneFernSnapshotService migrate incrementally?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Two asks around DovetailCopperBridgeCoordinator: (1) find the unknown cause of stale cursors when a page is resumed; (2) give the existing implementation a read-only safety pass. Make rollback possible without deleting user data, and leave a clear boundary between the resulting artifacts or edits.","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.73,"slice":"mixed","lang":"en"} -{"prompt":"Review how production missions are converted into simulator replays, then turn the findings into a validation guide with examples.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.62,"slice":"mixed","lang":"en"} -{"prompt":"Benenne `LegacyClock` im gesamten Repository in `MonotonicClock` um, einschließlich Swift package products und Tests. Das Verhalten und die öffentliche API abgesehen vom Namen sollen unverändert bleiben.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"de"} -{"prompt":"so what now","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"check how each client stores its token and tell me which one is the weakest","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Two asks around EquinoxVelaDrawerCoordinator: (1) separate EquinoxVelaDrawerCoordinator's policy from transport without behavior changes; (2) correct the known stale timeout beside it. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"que sigue","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"es"} -{"prompt":"make the lobby more epic","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.42,"slice":"vague-eval","lang":"en"} -{"prompt":"profiler says 60% of wall time is in json marshal on the hot path but the payloads are tiny. something's off, help me understand what i'm looking at","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"tiny config thing pls","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"vague-eval","lang":"en"} +{"prompt":"Two asks around DovetailCopperBridgeCoordinator: (1) find the unknown cause of stale cursors when a page is resumed; (2) give the existing implementation a read-only safety pass. Make rollback possible without deleting user data, and leave a clear boundary between the resulting artifacts or edits.","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Review how production missions are converted into simulator replays, then turn the findings into a validation guide with examples.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Benenne `LegacyClock` im gesamten Repository in `MonotonicClock` um, einschließlich Swift package products und Tests. Das Verhalten und die öffentliche API abgesehen vom Namen sollen unverändert bleiben.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} +{"prompt":"check how each client stores its token and tell me which one is the weakest","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Two asks around EquinoxVelaDrawerCoordinator: (1) separate EquinoxVelaDrawerCoordinator's policy from transport without behavior changes; (2) correct the known stale timeout beside it. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"make the lobby more epic","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"profiler says 60% of wall time is in json marshal on the hot path but the payloads are tiny. something's off, help me understand what i'm looking at","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Design a phased migration from self-signed internal certificates to a private ACME service, including bootstrap, renewal, trust rollover, outages, and retirement.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Render model-comparison metrics as an accessible Compose table with sortable columns, sticky experiment names, and clear win/loss coloring.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Render model-comparison metrics as an accessible Compose table with sortable columns, sticky experiment names, and clear win/loss coloring.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"preview envs leak — we have 60 namespaces for 12 open PRs","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"vue 3: the virtual list keeps its scroll position when you filter, so you end up staring at blank space. should reset to top on filter change but keep position on refetch","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"FoxgloveLumenChartCoordinator: give it a nicer flow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"vague-eval","lang":"en"} -{"prompt":"installer doesn't create a start menu shortcut","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"explain how plugin storage isolation works then write the section for the developer docs","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Investigate why terminated employees remain in manager search suggestions.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.61,"slice":"boundary","lang":"en"} +{"prompt":"FoxgloveLumenChartCoordinator: give it a nicer flow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"OvertureFlintTimelineCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"installer doesn't create a start menu shortcut","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"explain how plugin storage isolation works then write the section for the developer docs","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Investigate why terminated employees remain in manager search suggestions.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"customers on the enterprise plan report the export button does nothing. no js errors in their console, works for every account i test with","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"EquinoxFrostPanelCoordinator: check the suspicious part","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"vague-eval","lang":"en"} -{"prompt":"our generated types are checked in and stale. regenerate and wire the generation into the build so it cant drift","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Separate feature extraction from model invocation in `ScoringPipeline` while preserving tensor names, batching, timeouts, metrics, and prediction output exactly.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Rename `MasterPolicy` to `PrimaryPolicy` across services, events, reports, and tests while preserving public fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.64,"slice":"boundary","lang":"en"} -{"prompt":"Production says OvertureKiteSchedulerService is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current gRPC operational envelope\n\nThis repository spans IoT fleet, Ruby, SolidJS; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"off by one in the pagination footer, it says 'showing 1-20 of 20' when there are 21","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"im back, whats the state of things","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"the mute button says 'Mute' when you're already muted","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"half done, take it from here","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"EquinoxEchoRegistryStore leaks tasks on shutdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"boundary","lang":"en"} -{"prompt":"Explain how the policy service chooses coverage when multiple endorsements share an effective date.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} +{"prompt":"EquinoxFrostPanelCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"our generated types are checked in and stale. regenerate and wire the generation into the build so it cant drift","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the confidence threshold for cloud fallback is 0.5, way too low","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Separate feature extraction from model invocation in `ScoringPipeline` while preserving tensor names, batching, timeouts, metrics, and prediction output exactly.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Give the Android media picker a two-column tablet layout, retained selection indicators, and a bottom action bar that respects gesture insets.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Rename `MasterPolicy` to `PrimaryPolicy` across services, events, reports, and tests while preserving public fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Production says OvertureKiteSchedulerService is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current gRPC operational envelope\n\nThis repository spans IoT fleet, Ruby, SolidJS; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"off by one in the pagination footer, it says 'showing 1-20 of 20' when there are 21","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"the mute button says 'Mute' when you're already muted","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"EquinoxEchoRegistryStore leaks tasks on shutdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"Explain how the policy service chooses coverage when multiple endorsements share an effective date.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"users in an sso-enforced org can still log in with a password if they use the old bookmarked url","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"one product's model is 40mb and the others are 3mb, and nobody noticed for two months","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"performance test harness that runs our plugin on a seeded wordpress with 50k posts and reports query counts and timings","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"do the case page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.39,"slice":"vague-eval","lang":"en"} -{"prompt":"Build the mobile evidence-upload flow with category selection, scanning, progress, validation, retry, and receipts.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Move KeystoneAmberFilterService behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Today: // projects/foxglove/db/migrations/20260730_events.sql\nfinal class FoxgloveBirchMigratorFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveBirchMigratorFlow'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.77,"slice":"pasted-context","lang":"en"} +{"prompt":"do the case page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Build the mobile evidence-upload flow with category selection, scanning, progress, validation, retry, and receipts.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Move KeystoneAmberFilterService behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Polish the appliance status tiles","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Today: // projects/foxglove/db/migrations/20260730_events.sql\nfinal class FoxgloveBirchMigratorFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveBirchMigratorFlow'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":"tidy the css into modules per component, we have one 4000 line app.css and specificity wars every time someone touches it. visual output should be pixel identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the traffic light buttons overlap our custom titlebar content at small widths","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the traffic light buttons overlap our custom titlebar content at small widths","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Implement the Grafana-style query editor in React with token completion, inline errors, query history, and keyboard-only operation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"check over the new thing","purpose":"review","secondary":null,"mixed":false,"difficulty":0.46,"slice":"vague-eval","lang":"en"} -{"prompt":"next bit then","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Turn the existing admission-controller behavior into user documentation covering policies, exemptions, dry runs, and rejection messages.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"core","lang":"en"} -{"prompt":"something's off in prod","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"vague-eval","lang":"en"} -{"prompt":"GossamerOpalRouterCoordinator: sort out the rough edge","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"vague-eval","lang":"en"} -{"prompt":"KeystoneSpruceDaemonFlow needs an idempotent replay endpoint backed by OpenTelemetry; accept a cursor, cap each page at 500 items, and return a stable continuation token.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"tiny permission config tweak","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} -{"prompt":"sure keep going","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"CalderaPineMetricsCoordinator: polish the last piece","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"vague-eval","lang":"en"} -{"prompt":"thread 'tokio-runtime-worker' panicked at projects/hinterland/src/sync/reconcile.ts:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: hinterlanddriftconsoleflow::scheduler::LeaseTask::flush\n at ./projects/hinterland/src/sync/reconcile.ts:217:18\n 4: hinterlanddriftconsoleflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nFind the source of this HinterlandDriftConsoleFlow 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.92,"slice":"pasted-context","lang":"en"} -{"prompt":"diff --git a/projects/foxglove/ml/pipeline/features.py b/projects/foxglove/ml/pipeline/features.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/foxglove/ml/pipeline/features.py\n+++ b/projects/foxglove/ml/pipeline/features.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\nRead the artifact above as a skeptical reviewer. Is FoxgloveLumenChartFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"no","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Before changing the login service, outline a migration from session cookies to sender-constrained tokens. Include browser compatibility, key lifecycle, refresh behavior, compromised-device recovery, gradual enrollment, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"boundary","lang":"en"} -{"prompt":"webhook delivery service: at-least-once, exponential backoff to 24h, dead letter after that, per-endpoint concurrency cap so one slow customer can't starve the pool","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"look over the IAM policy attached to the CI role and tell me what it can do that it shouldn't","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"error mapping from the shared layer into idiomatic errors on each platform, so swift gets a typed error not a generic throw","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"check over the new thing","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Turn the existing admission-controller behavior into user documentation covering policies, exemptions, dry runs, and rejection messages.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"something's off in prod","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"GossamerOpalRouterCoordinator: sort out the rough edge","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"KeystoneSpruceDaemonFlow needs an idempotent replay endpoint backed by OpenTelemetry; accept a cursor, cap each page at 500 items, and return a stable continuation token.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"tiny permission config tweak","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"CalderaPineMetricsCoordinator: polish the last piece","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"thread 'tokio-runtime-worker' panicked at projects/hinterland/src/sync/reconcile.ts:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: hinterlanddriftconsoleflow::scheduler::LeaseTask::flush\n at ./projects/hinterland/src/sync/reconcile.ts:217:18\n 4: hinterlanddriftconsoleflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nFind the source of this HinterlandDriftConsoleFlow symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"diff --git a/projects/foxglove/ml/pipeline/features.py b/projects/foxglove/ml/pipeline/features.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/foxglove/ml/pipeline/features.py\n+++ b/projects/foxglove/ml/pipeline/features.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\nRead the artifact above as a skeptical reviewer. Is FoxgloveLumenChartFlow'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":"Before changing the login service, outline a migration from session cookies to sender-constrained tokens. Include browser compatibility, key lifecycle, refresh behavior, compromised-device recovery, gradual enrollment, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"webhook delivery service: at-least-once, exponential backoff to 24h, dead letter after that, per-endpoint concurrency cap so one slow customer can't starve the pool","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"look over the IAM policy attached to the CI role and tell me what it can do that it shouldn't","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"error mapping from the shared layer into idiomatic errors on each platform, so swift gets a typed error not a generic throw","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Document that thing","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} -{"prompt":"We expect KeystoneMicaProfileService to outgrow its current Swift 6 arrangement next quarter, but changing everything at once would be risky. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing Swift 6 deployment\n- keep the work scoped to KeystoneMicaProfileService and its direct tests\n\nSeveral teams work in this collaboration, C++, Next.js monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.83,"slice":"core","lang":"en"} -{"prompt":"Write release notes for review templates, including variables, repository defaults, permissions, and old-client behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"Create the React trace waterfall and explain the new keyboard interactions in docs/accessibility.md.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.66,"slice":"mixed","lang":"en"} -{"prompt":"Draft the incident summary","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"same but for windows","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"JunctionBirchMigratorCoordinator needs a paired pass: assess ownership and failure handling in projects/junction/pkg/cache/lease.rs, plus capture the contract and rollback note for consumers. Use projects/junction/pkg/cache/lease.rs as the source of truth, preserve the Kafka contract, and avoid unrelated cleanup.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"Audit the certificate verifier","purpose":"review","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Build the desktop material-allocation workspace with requirements, available lots, constraints, preview, and undo.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Before anyone writes code, specify how the React dashboard should support user-defined widgets, persistence, drag layout, and versioned widget contracts.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.79,"slice":"boundary","lang":"en"} +{"prompt":"We expect KeystoneMicaProfileService to outgrow its current Swift 6 arrangement next quarter, but changing everything at once would be risky. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing Swift 6 deployment\n- keep the work scoped to KeystoneMicaProfileService and its direct tests\n\nSeveral teams work in this collaboration, C++, Next.js monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the week starts on sunday in three queries and monday in the rest","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Write release notes for review templates, including variables, repository defaults, permissions, and old-client behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Create the React trace waterfall and explain the new keyboard interactions in docs/accessibility.md.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Draft the incident summary","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"JunctionBirchMigratorCoordinator needs a paired pass: assess ownership and failure handling in projects/junction/pkg/cache/lease.rs, plus capture the contract and rollback note for consumers. Use projects/junction/pkg/cache/lease.rs as the source of truth, preserve the Kafka contract, and avoid unrelated cleanup.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Audit the certificate verifier","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"job status polling hammers us — 4 requests per second per client because the ui polls at 250ms","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Build the desktop material-allocation workspace with requirements, available lots, constraints, preview, and undo.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Before anyone writes code, specify how the React dashboard should support user-defined widgets, persistence, drag layout, and versioned widget contracts.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"flatten the inheritance in the exporter classes. BaseExporter -> AbstractFileExporter -> CsvExporter is two levels too many for what it does, composition instead","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"sqlite FTS5 search in the notes CLI — index title and body, prefix matching, snippet with highlights in the terminal output","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"compose ui inside the crm with templates, merge fields, and a preview with the fields resolved","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Documente o contrato de NorthstarEmberRelayService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"pt"} -{"prompt":"Meanwhile: Incident timeline — INC-43159\n\n08:02 deploy CalderaOspreyJobCoordinator 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 CalderaOspreyJobCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.67,"slice":"pasted-context","lang":"en"} -{"prompt":"cursor pagination on the remaining 14 endpoints, opaque cursors, stable ordering, and a hard max page size of 200","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"NorthstarBeaconStoreCoordinator: something is off here","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"Map out a migration from Jenkins-hosted game builds to ephemeral Buildkite agents, covering asset caches, console SDK isolation, signing, capacity spikes, observability, and rollback milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"core","lang":"en"} -{"prompt":"NorthstarIrisBatchCoordinator: smooth out this interaction","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"vague-eval","lang":"en"} -{"prompt":"attribution shows 'direct' for 60% of orders which can't be right","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"FoxgloveDriftConsoleCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"vague-eval","lang":"en"} -{"prompt":"just carry on for now","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Ticket OPS-47138: retire the legacy replay path for GossamerLedgerGateFlow\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 GossamerLedgerGateFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"pasted-context","lang":"en"} -{"prompt":"OvertureAtlasSearchCoordinator is blocking the next release because lost focus when the drawer animation finishes. I need two concrete outcomes from a single pass: lay out a staged migration for OvertureAtlasSearchCoordinator, and consolidate the duplicated normalization paths without changing behavior. Use the existing gRPC conventions in projects/overture/lib/codec/frame.cc; preserve cancellation and back-pressure semantics. 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.88,"slice":"mixed","lang":"en"} +{"prompt":"sqlite FTS5 search in the notes CLI — index title and body, prefix matching, snippet with highlights in the terminal output","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"compose ui inside the crm with templates, merge fields, and a preview with the fields resolved","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Documente o contrato de NorthstarEmberRelayService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"pt"} +{"prompt":"Meanwhile: Incident timeline — INC-43159\n\n08:02 deploy CalderaOspreyJobCoordinator 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 CalderaOspreyJobCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"cursor pagination on the remaining 14 endpoints, opaque cursors, stable ordering, and a hard max page size of 200","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"NorthstarBeaconStoreCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Map out a migration from Jenkins-hosted game builds to ephemeral Buildkite agents, covering asset caches, console SDK isolation, signing, capacity spikes, observability, and rollback milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"NorthstarIrisBatchCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"attribution shows 'direct' for 60% of orders which can't be right","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"FoxgloveDriftConsoleCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Ticket OPS-47138: retire the legacy replay path for GossamerLedgerGateFlow\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 GossamerLedgerGateFlow 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":"OvertureAtlasSearchCoordinator is blocking the next release because lost focus when the drawer animation finishes. I need two concrete outcomes from a single pass: lay out a staged migration for OvertureAtlasSearchCoordinator, and consolidate the duplicated normalization paths without changing behavior. Use the existing gRPC conventions in projects/overture/lib/codec/frame.cc; preserve cancellation and back-pressure semantics. 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":"do the device screen","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"Investigate why revoked personal access tokens continue working through the GraphQL gateway, implement the verified cache fix, and document the propagation window accurately.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.82,"slice":"mixed","lang":"en"} -{"prompt":"two-pane layout on wide screens with the list on the left, and the selection should survive a fold/unfold","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Compare the two existing quantization paths and recommend which is safer for our mobile model, without implementing changes.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"Investigate why revoked personal access tokens continue working through the GraphQL gateway, implement the verified cache fix, and document the propagation window accurately.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"two-pane layout on wide screens with the list on the left, and the selection should survive a fold/unfold","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Database ticket DBENG-933\n\nObserved issue: range scans hold page pins until the iterator is destroyed. Analytics callers sometimes keep iterators alive for minutes, preventing cache eviction and increasing resident memory. We need incremental release without changing scan results.\n\nRequirements:\n- at most three leaf pages pinned per iterator\n- forward and reverse scans remain supported\n- snapshot visibility must remain stable\n- concurrent splits and merges cannot skip or duplicate keys\n- seek and resume tokens retain current encoding\n- iterator errors remain sticky\n- cancellation releases pins promptly\n- benchmarks for 1M-key scans must not regress more than 3%\n- fault tests should cover eviction and structural changes between next() calls\n\nImplement the iterator changes in engine/scan and preserve the public C API.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"alembic's env.py has compare_type=False, flip it on and regenerate nothing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"moving on then","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Restructure the manufacturing SDK into items, inventory, work orders, quality, and genealogy, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Unify the AegisMicaProfileStore validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"write the protocol doc for the sync api — envelope format, the cursor semantics, and how a client recovers from a rejected batch","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"LongbowOrbitSyncCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"support doc for field users whose data isn't syncing: the three things to check, in order","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"internal doc on how the media cache and the download store relate, they're two things and everyone thinks they're one","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"LongbowAcornWidgetCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} -{"prompt":"Investigate the purple frames","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"write up the security disclosure policy for the repo, SECURITY.md, include the response time we're committing to","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"KeystonePrismCacheCoordinator: give it a nicer flow","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"continue the audio issue","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.54,"slice":"vague-eval","lang":"en"} -{"prompt":"drift detection comparing the figma component properties against our code's prop types, reported weekly","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"one nested query takes 12 seconds and the dataloader batching looks like its not kicking in for that path only","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Match LongbowMoonlitSDKStore's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"alembic's env.py has compare_type=False, flip it on and regenerate nothing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Restructure the manufacturing SDK into items, inventory, work orders, quality, and genealogy, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Unify the AegisMicaProfileStore validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"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":"support doc for field users whose data isn't syncing: the three things to check, in order","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Fix the clipped squad names and extract the shared truncation rule used by the lobby and scoreboard. Preserve all other layout behavior.","purpose":"refactor","secondary":"frontendImpl","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"internal doc on how the media cache and the download store relate, they're two things and everyone thinks they're one","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"LongbowAcornWidgetCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Investigate the purple frames","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"write up the security disclosure policy for the repo, SECURITY.md, include the response time we're committing to","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"KeystonePrismCacheCoordinator: give it a nicer flow","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"drift detection comparing the figma component properties against our code's prop types, reported weekly","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"one nested query takes 12 seconds and the dataloader batching looks like its not kicking in for that path only","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"do the fleet page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"Two engineers disagree about whether OvertureGarnetModalStore's cache is authoritative. Walk the reads and writes in projects/overture/app/src/main/SyncWorker.kt and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Propose an architecture for deterministic server-side replays, including input capture, state hashes, versioning, compression, validation, privacy, and production debugging.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Fix the clipped currency code in compact rows and extract the duplicated amount-width rule into the shared table styles.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.38,"slice":"mixed","lang":"en"} -{"prompt":"next up then","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Explain why the current authorization engine evaluates explicit denies before administrator grants. Assume behavior is correct.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Rename DovetailTideWorkerStore's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"that's me done, last bit","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Two engineers disagree about whether OvertureGarnetModalStore's cache is authoritative. Walk the reads and writes in projects/overture/app/src/main/SyncWorker.kt and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Propose an architecture for deterministic server-side replays, including input capture, state hashes, versioning, compression, validation, privacy, and production debugging.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Fix the clipped currency code in compact rows and extract the duplicated amount-width rule into the shared table styles.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Explain why the current authorization engine evaluates explicit denies before administrator grants. Assume behavior is correct.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Rename DovetailTideWorkerStore's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Polish the cart summary card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"persisted queries so the mobile client sends a hash instead of the document, with a build step that extracts them","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"design the retrieval pipeline then build the chunker as the first piece","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"wp-cron never fires on sites with DISABLE_WP_CRON and we don't tell anyone","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Implementation ticket:\n\n```text\nLAB-904 — specimen chain-of-custody events\nEvents: collected, labeled, handed_off, received, aliquoted, disposed\nEach event includes specimen ID, actor, location, device time, server time, and optional note\nRules:\n- events are append-only\n- device time may be offline and out of order\n- a disposed specimen cannot receive later workflow events without supervisor override\n- duplicate scanner submissions are common\n- corrections reference the incorrect event; they never delete it\n- every override requires a reason and audit event\n- expose missing handoff and invalid transition counters\n```\n\nImplement the event model, commands, idempotency, transition checks, override flow, persistence, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.87,"slice":"pasted-context","lang":"en"} -{"prompt":"finish the inventory endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"Restructure the observation pipeline and document its provider interface. Preserve data while separating decode, normalize, quality control, correction, and publication.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"Move yield calculation out of `ProductionController` while preserving values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"FoxgloveWillowCodecCoordinator: untangle the messy bit","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"vague-eval","lang":"en"} +{"prompt":"wp-cron never fires on sites with DISABLE_WP_CRON and we don't tell anyone","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"finish the inventory endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Restructure the observation pipeline and document its provider interface. Preserve data while separating decode, normalize, quality control, correction, and publication.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Move yield calculation out of `ProductionController` while preserving values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"FoxgloveWillowCodecCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"sketch the interaction model for the new inline comment threads (hover affordance, focus states, keyboard nav) and then implement the React side. no backend, the endpoints exist","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Console: diff --git a/projects/keystone/db/migrations/20260730_events.sql b/projects/keystone/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/keystone/db/migrations/20260730_events.sql\n+++ b/projects/keystone/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit KeystoneLedgerGateFlow 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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"release notes for 2.4.0, user-facing tone, group into new / improved / fixed","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"BorealDeltaCanvasCoordinator: ship a sensible version","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"KeystoneOpalRouterCoordinator: sort out the rough edge","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"vague-eval","lang":"en"} -{"prompt":"DovetailEmberRelayCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"vague-eval","lang":"en"} -{"prompt":"sure","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"after we added the partial index the planner switched to a seq scan on the orders join. expected or did we break something","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"implement graceful shutdown properly — stop accepting, drain in flight with a 30s cap, close the db pool last, and log what got dropped","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Explain how the server allocator handles draining nodes with active and pending matches.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} +{"prompt":"Console: diff --git a/projects/keystone/db/migrations/20260730_events.sql b/projects/keystone/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/keystone/db/migrations/20260730_events.sql\n+++ b/projects/keystone/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit KeystoneLedgerGateFlow 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":"release notes for 2.4.0, user-facing tone, group into new / improved / fixed","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Polish the fare summary card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"BorealDeltaCanvasCoordinator: ship a sensible version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"KeystoneOpalRouterCoordinator: sort out the rough edge","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"DovetailEmberRelayCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"after we added the partial index the planner switched to a seq scan on the orders join. expected or did we break something","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"implement graceful shutdown properly — stop accepting, drain in flight with a 30s cap, close the db pool last, and log what got dropped","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Explain how the server allocator handles draining nodes with active and pending matches.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"keyboard shortcut palette, cmd+k, fuzzy filter, recent commands at top, and it has to trap focus properly","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"crm: the pipeline board needs drag between stages with an optimistic move, and the deal value totals per column updating live","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"The OpenAPI contract is approved. Implement PATCH /v2/customers/{id} with ETag preconditions and field-level authorization.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"add cursor pagination to GET /activity. opaque cursor, stable under inserts, include has_more, and don't break the existing page/limit callers","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Where did HinterlandCraneWorkspaceStore's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} +{"prompt":"The OpenAPI contract is approved. Implement PATCH /v2/customers/{id} with ETag preconditions and field-level authorization.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"add cursor pagination to GET /activity. opaque cursor, stable under inserts, include has_more, and don't break the existing page/limit callers","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Where did HinterlandCraneWorkspaceStore's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Flip matchmaking_shadow to true in staging","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Bump OvertureRainfallDBService's timeout to 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"core","lang":"en"} -{"prompt":"implement soft delete on the projects table: deleted_at column, partial unique index on slug where deleted_at is null, and update every query in internal/projects to filter it. also a nightly purge after 30 days","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"code review on the branch — mostly want your eyes on the transaction boundaries in the transfer handler","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","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.88,"slice":"core","lang":"en"} -{"prompt":"Crash and power trace:\n\nDevice: soil-node Rev B, firmware 3.8.1\nReset reason: watchdog\n03:22:18.441 radio IRQ asserted\n03:22:18.442 task radio_rx entered\n03:22:18.443 flash_gc acquiring storage_mutex\n03:22:18.444 radio_rx waiting storage_mutex\n03:22:18.448 flash_gc erasing sector 19\n03:22:21.448 watchdog reset\n\nCurrent watchdog window is 2 seconds. Sector erase normally takes 180 ms but reaches 3.1 seconds below -20°C. The radio receive task also writes its acknowledgement counter to the same flash journal. We cannot simply increase the watchdog window because safety requirements cap it at 2 seconds. Diagnose the blocking design and implement a safe fix that retains acknowledgement durability and cold-temperature operation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"the turn credentials are static and checked into the repo","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"appeals process doc from the system's perspective: what we store, how a decision is reviewed, and what a reversal does to the record","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"set `strict: true` in tsconfig and fix the fallout. there'll be a few hundred errors, work through them without changing runtime behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.75,"slice":"boundary","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new application form, including schema, conditions, validation, accessibility, and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Flip EquinoxAmberFilterService's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"core","lang":"en"} -{"prompt":"GossamerAsterWebhookCoordinator: check the suspicious part","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump OvertureRainfallDBService's timeout to 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"implement soft delete on the projects table: deleted_at column, partial unique index on slug where deleted_at is null, and update every query in internal/projects to filter it. also a nightly purge after 30 days","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"code review on the branch — mostly want your eyes on the transaction boundaries in the transfer handler","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","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":"the texture cache budget is 512mb on every device","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"the turn credentials are static and checked into the repo","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"appeals process doc from the system's perspective: what we store, how a decision is reviewed, and what a reversal does to the record","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"set `strict: true` in tsconfig and fix the fallout. there'll be a few hundred errors, work through them without changing runtime behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new application form, including schema, conditions, validation, accessibility, and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Flip EquinoxAmberFilterService's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"GossamerAsterWebhookCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"Create the passkey management screen and implement credential-renaming support in the API.","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Why does OvertureGarnetModalService's FastAPI worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"schedule editor with a human-readable summary under the cron input ('every weekday at 8am in Europe/Berlin')","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the vscode extension gets logged out whenever the window reloads, but only on windows","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Scheduler: // projects/keystone/cmd/exporter/main.py\nfinal class KeystoneCraneWorkspaceFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 KeystoneCraneWorkspaceFlow 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":"Why does OvertureGarnetModalService's FastAPI worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"schedule editor with a human-readable summary under the cron input ('every weekday at 8am in Europe/Berlin')","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the vscode extension gets logged out whenever the window reloads, but only on windows","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"the rails app's background jobs. sidekiq, 40 job classes, and the queue configuration has grown organically so we have queues called 'default', 'high', 'urgent', 'critical' and 'now', which tells you everything. i want the plan: proper queue design, priorities that mean something, and per-queue capacity","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Inspect the federation inbox for signature confusion, replay, remote deletes, oversized activities, and SSRF through actor URLs.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Why do certificate renewals fail only for robots that were offline during CA rotation? Find the chain-building failure.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Specify an observability model for GPU training jobs spanning Kubernetes scheduling, data loading, checkpointing, and distributed collectives.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.82,"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.86,"slice":"pasted-context","lang":"en"} -{"prompt":"thread 'tokio-runtime-worker' panicked at projects/overture/Sources/CLI/Commands/Doctor.swift:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: overturecopperbridgeflow::scheduler::LeaseTask::flush\n at ./projects/overture/Sources/CLI/Commands/Doctor.swift:217:18\n 4: overturecopperbridgeflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nReconstruct the OvertureCopperBridgeFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.95,"slice":"pasted-context","lang":"en"} -{"prompt":"Staging: The data is already available in projects/caldera/Sources/CLI/Commands/Doctor.swift; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"CalderaMarbleTokenCoordinator needs a paired pass: lay out a staged migration for CalderaMarbleTokenCoordinator, plus consolidate the duplicated normalization paths without changing behavior. Use projects/caldera/ml/pipeline/features.py as the source of truth, preserve the OpenTelemetry contract, and avoid unrelated cleanup.","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.74,"slice":"mixed","lang":"en"} -{"prompt":"Trace the source of nondeterministic particle positions in replay verification after the compiler upgrade.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"Plan and implement a content-rights enforcement service. Begin with a design covering territories, time windows, subscription tiers, device restrictions, downloads, live events, policy versioning, cache invalidation, audit, and failure behavior. Then add the evaluator, policy APIs, signed decisions, metrics, and conformance tests. Treat policy semantics and rollout as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.97,"slice":"mixed","lang":"en"} -{"prompt":"NorthstarQuartzPlayerCoordinator: could this be clearer","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"vague-eval","lang":"en"} -{"prompt":"finish up the ingestion piece","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Inspect the federation inbox for signature confusion, replay, remote deletes, oversized activities, and SSRF through actor URLs.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Why do certificate renewals fail only for robots that were offline during CA rotation? Find the chain-building failure.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Specify an observability model for GPU training jobs spanning Kubernetes scheduling, data loading, checkpointing, and distributed collectives.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"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":"thread 'tokio-runtime-worker' panicked at projects/overture/Sources/CLI/Commands/Doctor.swift:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: overturecopperbridgeflow::scheduler::LeaseTask::flush\n at ./projects/overture/Sources/CLI/Commands/Doctor.swift:217:18\n 4: overturecopperbridgeflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nReconstruct the OvertureCopperBridgeFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Staging: The data is already available in projects/caldera/Sources/CLI/Commands/Doctor.swift; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"CalderaMarbleTokenCoordinator needs a paired pass: lay out a staged migration for CalderaMarbleTokenCoordinator, plus consolidate the duplicated normalization paths without changing behavior. Use projects/caldera/ml/pipeline/features.py as the source of truth, preserve the OpenTelemetry contract, and avoid unrelated cleanup.","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Trace the source of nondeterministic particle positions in replay verification after the compiler upgrade.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Plan and implement a content-rights enforcement service. Begin with a design covering territories, time windows, subscription tiers, device restrictions, downloads, live events, policy versioning, cache invalidation, audit, and failure behavior. Then add the evaluator, policy APIs, signed decisions, metrics, and conformance tests. Treat policy semantics and rollout as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":1,"slice":"mixed","lang":"en"} +{"prompt":"NorthstarQuartzPlayerCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"read the importer and tell me what happens if the process dies at 60% — do we have a half-imported dataset","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"finish up the ingestion piece","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"our token verification is implemented twice, once in the middleware and once in the websocket handler, with different clock skew tolerance. one implementation","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"our alert rules are copy pasted per service with the service name changed. template them, exact same rules firing at the exact same thresholds","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Compare the old and new MeridianDriftConsoleFlow adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Map out a migration from manager-owned spreadsheets to a centralized headcount-planning model, including scenarios, permissions, versions, imports, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"core","lang":"en"} -{"prompt":"que onda con esto","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"es"} -{"prompt":"make the robot map cooler","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.42,"slice":"vague-eval","lang":"en"} +{"prompt":"our alert rules are copy pasted per service with the service name changed. template them, exact same rules firing at the exact same thresholds","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Compare the old and new MeridianDriftConsoleFlow 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":"Map out a migration from manager-owned spreadsheets to a centralized headcount-planning model, including scenarios, permissions, versions, imports, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"que onda con esto","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"es"} +{"prompt":"the retry count is 5 with no backoff","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"make the robot map cooler","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} diff --git a/data/generation-manifest.json b/data/generation-manifest.json index be21c82..e8788a0 100644 --- a/data/generation-manifest.json +++ b/data/generation-manifest.json @@ -1,10 +1,9 @@ { - "schemaVersion": 1, - "dataset": "purpose-classifier-source-v1", "canonicalFiles": [ "purpose-prompts.jsonl", "purpose-prompts-round2.jsonl" ], + "dataset": "purpose-classifier-source-v1", "derivedBatchFiles": [ "round2-01.jsonl", "round2-02.jsonl", @@ -24,34 +23,52 @@ ], "generations": [ { + "date": "2026-07-29", "file": "purpose-prompts.jsonl", "model": "mixed frontier-model runs (legacy sol/opus aliases; exact model IDs were not retained)", - "date": "2026-07-29", + "notes": "The canonical aggregate was curated from the original per-model batches. Three exact overlaps with the shipped eval fixture were removed on 2026-07-30.", "prompt": "../datagen-prompt.md", "topics": [ "web and mobile", "backend and data", "infrastructure and systems", "developer tooling" - ], - "notes": "The canonical aggregate was curated from the original per-model batches. Three exact overlaps with the shipped eval fixture were removed on 2026-07-30." + ] }, { + "date": "2026-07-30", "file": "purpose-prompts-round2.jsonl", "model": "Nucleic frontier-model generator (exact underlying model ID was not retained)", - "date": "2026-07-30", + "notes": "Corrective generation that counterbalances round-one label, slice, length, opener, and language drift.", "prompt": "../datagen-prompt-2.md", "topics": [ "boundary confusion pairs", "pasted context", "mixed intent", "non-English developer prompts" - ], - "notes": "Corrective generation that counterbalances round-one label, slice, length, opener, and language drift." + ] } ], + "labeling": { + "date": "2026-08-02", + "files": { + "purpose-prompts-round2.jsonl": { + "records": 3000, + "sha256": "a3c5bbede5b7db743c9f31756491990b388edd2aa9b41c8b2b9ec95b7115f4aa" + }, + "purpose-prompts.jsonl": { + "records": 9007, + "sha256": "6fbd08df113ca4c6f9da151222772dc3e25e1b9b19c9c2b7df9f572053af2507" + } + }, + "model": "gpt-5.6-sol", + "reasoningEffort": "high", + "schemaVersion": 1, + "scope": "all canonical public prompts; rejected junk removed" + }, "limitations": [ "The exact generator model IDs and sampling parameters were not recorded when the source corpora were created.", "The round2-NN files are retained generation batches and duplicate the round-two canonical aggregate; dataset tooling must read canonicalFiles only." - ] + ], + "schemaVersion": 1 } diff --git a/data/purpose-prompts-round2.jsonl b/data/purpose-prompts-round2.jsonl index 25290c9..b5bb630 100644 --- a/data/purpose-prompts-round2.jsonl +++ b/data/purpose-prompts-round2.jsonl @@ -1,3000 +1,3000 @@ -{"prompt":"AegisQuartzPlayerService 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.55,"slice":"core","lang":"en"} -{"prompt":"Find AegisBirchMigratorStore's duplicate retry source","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} +{"prompt":"AegisQuartzPlayerService 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":"Find AegisBirchMigratorStore's duplicate retry source","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Design handed over a final pass for AegisCraneWorkspaceService, and the basic data flow in projects/aegis/ml/pipeline/features.py already works. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing Tokio deployment\n- keep the work scoped to AegisCraneWorkspaceService and its direct tests\n\nThis repository spans payments, iOS, Kubernetes; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"AegisFlintTimelineCoordinator: ship, then document","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"projects/aegis/lib/codec/frame.cc now contains AegisSummitProxyService'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.55,"slice":"core","lang":"en"} -{"prompt":"The AegisHarborIndexStore surface in projects/aegis/apps/console/routes/usage.svelte 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.33,"slice":"core","lang":"en"} -{"prompt":"Split AegisDriftConsoleStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"AegisGarnetModalCoordinator: diagnose, then correct","purpose":"debugging","secondary":"quickFix","mixed":true,"difficulty":0.78,"slice":"mixed","lang":"en"} -{"prompt":"Please resist widening this one: AegisCraneWorkspaceStore works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside AegisCraneWorkspaceStore\n- keep public behavior and serialized data unchanged\n\nThe relevant code crosses payments, iOS, Kubernetes. Prefer evidence from the repository and make any assumption explicit.\n\nThe cause and exact value change are already known, so keep this as a contained correction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"En projects/aegis/workers/thumbnail/consumer.ex, AegisOpalRouterStore tiene un problema intermitente en el flujo de NATS JetStream. La causa ya está clara: cambia solo el timeout de staging de 15 a 30 segundos y ajusta su assertion.\n\nRestricciones:\n- seguir con NATS JetStream\n- conservar compatibilidad y cancelación\n- limitar el cambio a AegisOpalRouterStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.28,"slice":"boundary","lang":"es"} -{"prompt":"Ticket OPS-41124: retire the legacy replay path for AegisLumenChartFlow\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 AegisLumenChartFlow rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"# projects/aegis/config/staging.toml\n[worker.aegiscinderauthflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegiscinderauthflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegiscinderauthflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisCinderAuthFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41123\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/aegis/config/staging.toml and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.41,"slice":"pasted-context","lang":"en"} -{"prompt":"Apparently: # projects/aegis/workers/thumbnail/consumer.ex\n[worker.aegisflinttimelineflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisflinttimelineflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisflinttimelineflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisFlintTimelineFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41121\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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Align AegisFlintTimelineFlow'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.36,"slice":"pasted-context","lang":"de"} -{"prompt":"Bring AegisIrisBatchStore'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.54,"slice":"boundary","lang":"en"} -{"prompt":"Release verification found a single stale AegisRainfallDBService value; the cause, desired value, and affected assertion are already agreed. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current Tokio operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"AegisPrismCacheStore is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. 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- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current Tokio operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Two asks around AegisEmberRelayCoordinator: (1) assess ownership and failure handling in projects/aegis/crates/index/src/segment.rs; (2) capture the contract and rollback note for consumers. Keep public behavior and serialized data unchanged, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"diff --git a/projects/aegis/Sources/App/SessionStore.swift b/projects/aegis/Sources/App/SessionStore.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/aegis/Sources/App/SessionStore.swift\n+++ b/projects/aegis/Sources/App/SessionStore.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate AegisRainfallDBCoordinator'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.87,"slice":"pasted-context","lang":"en"} -{"prompt":"AegisQuartzPlayerCoordinator: ship a sensible version","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"vague-eval","lang":"en"} -{"prompt":"AegisFrostPanelCoordinator: check the suspicious part","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"vague-eval","lang":"en"} -{"prompt":"Please turn AegisFrostPanelService'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.38,"slice":"core","lang":"en"} -{"prompt":"Describe AegisWillowCodecStore's error envelope","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"boundary","lang":"en"} -{"prompt":"AegisMoonlitSDKCoordinator: sequence, then restructure","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"AegisOrbitSyncCoordinator: why is this odd","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"vague-eval","lang":"en"} -{"prompt":"Lately: // projects/aegis/apps/console/routes/usage.svelte\nfinal class AegisMarbleTokenFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 AegisMarbleTokenFlow 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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Oddly: // projects/aegis/ui/settings/PrivacyPane.tsx\nfinal class AegisDriftConsoleFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 AegisDriftConsoleFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"AegisCoralUploadCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"vague-eval","lang":"en"} -{"prompt":"Summarize the AegisSpruceDaemonService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"Responsive layout for AegisFlintTimelineStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"boundary","lang":"en"} -{"prompt":"For AegisEchoRegistryCoordinator, separate AegisEchoRegistryCoordinator's policy from transport without behavior changes; once that is complete, correct the known stale timeout beside it. Work from projects/aegis/src/sync/reconcile.ts, stay with PostgreSQL 17, and keep public behavior and serialized data unchanged. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.63,"slice":"mixed","lang":"en"} -{"prompt":"Incident timeline — INC-41153\n\n08:02 deploy AegisCedarPolicyCoordinator 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Turn the material above into a concise AegisCedarPolicyCoordinator 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.65,"slice":"pasted-context","lang":"ja"} -{"prompt":"UI ticket DES-41151: finish the compact AegisJuniperCLICoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/aegis/ui/settings/PrivacyPane.tsx\nFramework: NATS JetStream\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 AegisJuniperCLICoordinator's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Currently: projects/aegis/apps/console/routes/usage.svelte 里的 AegisMarbleTokenService 最近在 PostgreSQL 17 流程中出现间歇性问题。 请实现幂等 endpoint，包含持久 cursor、tenant 鉴权、spans 和 retry 测试。\n\n约束：\n- 继续使用 PostgreSQL 17\n- 保持兼容性和取消语义\n- 改动只限于 AegisMarbleTokenService","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"zh"} -{"prompt":"Split projects/aegis/workers/thumbnail/consumer.ex by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current AegisNovaPickerStore design actually guarantees what its callers assume. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside AegisNovaPickerStore\n- keep public behavior and serialized data unchanged\n\nThe relevant code crosses payments, iOS, Kubernetes. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"Release engineering needs a AegisAmberFilterService changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"diff --git a/projects/aegis/Sources/App/SessionStore.swift b/projects/aegis/Sources/App/SessionStore.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/aegis/Sources/App/SessionStore.swift\n+++ b/projects/aegis/Sources/App/SessionStore.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is AegisPrismCacheFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"UI ticket DES-41145: finish the compact AegisAcornWidgetFlow filter experience\n\nRoute: /catalog/search\nSource: projects/aegis/app/src/main/SyncWorker.kt\nFramework: PostgreSQL 17\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Use the UI evidence to complete AegisAcornWidgetFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"pasted-context","lang":"zh"} -{"prompt":"Incident timeline — INC-41115\n\n08:02 deploy AegisSableParserFlow 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 AegisSableParserFlow rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"AegisIrisBatchCoordinator: untangle the messy bit","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"vague-eval","lang":"en"} -{"prompt":"AegisVelaDrawerCoordinator: give it a nicer flow","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"Test Suite 'AegisMicaProfileFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[AegisMicaProfileFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/aegis/infra/modules/edge/main.tf:144: error: -[AegisMicaProfileFlowTests 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 '-[AegisMicaProfileFlowTests 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\nFind the source of this AegisMicaProfileFlow 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.92,"slice":"pasted-context","lang":"en"} -{"prompt":"Test Suite 'AegisEmberRelayFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[AegisEmberRelayFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/aegis/pkg/cache/lease.rs:144: error: -[AegisEmberRelayFlowTests 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 '-[AegisEmberRelayFlowTests 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 AegisEmberRelayFlow'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.76,"slice":"pasted-context","lang":"en"} -{"prompt":"Today: Incident timeline — INC-41119\n\n08:02 deploy AegisNimbusFormFlow 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 AegisNimbusFormFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.67,"slice":"pasted-context","lang":"en"} -{"prompt":"Unifie les validateurs de AegisNimbusFormService","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"fr"} -{"prompt":"Why is AegisMapleQueueService stalling?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Context: # projects/aegis/db/migrations/20260730_events.sql\n[worker.aegisledgergatecoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisledgergatecoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisledgergatecoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisLedgerGateCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41150\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/aegis/db/migrations/20260730_events.sql and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"pasted-context","lang":"en"} -{"prompt":"Move AegisEmberRelayStore behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Ticket OPS-41132: retire the legacy replay path for AegisMapleQueueFlow\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 AegisMapleQueueFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"We need to move AegisQuartzPlayerStore from the legacy store to NATS JetStream. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"Draft AegisSpruceDaemonStore's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"AegisBirchMigratorService's SyncWorker.kt needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"The next client release depends on a new AegisNovaPickerService capability in projects/aegis/internal/auth/refresh.go, with WebGPU already chosen by the platform group. Implement the endpoint and durable cursor, enforce tenant authorization and idempotency, emit useful spans, cap work per request, and include focused tests for retries, cancellation, and malformed cursors.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing WebGPU deployment\n- keep the work scoped to AegisNovaPickerService and its direct tests\n\nThis repository spans payments, iOS, Kubernetes; use its existing conventions rather than importing a new abstraction.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"AegisMarbleTokenCoordinator: handle the lingering thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"vague-eval","lang":"en"} -{"prompt":"Clarify AegisEchoRegistryStore's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"boundary","lang":"en"} -{"prompt":"Where did AegisWillowCodecService's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Background: UI ticket DES-41113: finish the compact AegisOspreyJobFlow filter experience\n\nRoute: /catalog/search\nSource: projects/aegis/packages/api/openapi.yaml\nFramework: SQLite\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\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Bring AegisOspreyJobFlow'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.76,"slice":"pasted-context","lang":"es"} -{"prompt":"AegisNovaPickerCoordinator is blocking the next release because two validators with subtly different error strings. I need two concrete outcomes from a single pass: finish AegisNovaPickerCoordinator's responsive empty and retry states, and capture the contract and rollback note for consumers. Use the existing WebGPU conventions in projects/aegis/infra/modules/edge/main.tf; keep public behavior and serialized data unchanged. 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":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.75,"slice":"mixed","lang":"en"} -{"prompt":"Production says AegisCloudReconcilerStore is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Reconstruct the failing timeline from logs and tests, identify which invariant first breaks, and distinguish causal signals from effects or cleanup noise.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current SQLite operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.87,"slice":"boundary","lang":"en"} -{"prompt":"Two engineers disagree about whether AegisFernSnapshotStore's cache is authoritative. Walk the reads and writes in projects/aegis/cmd/exporter/main.py and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Before we approve AegisSlateEditorStore, assess whether two validators with subtly different error strings is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Fresh release brief for AegisPrismCacheCoordinator:\n- primary outcome: change AegisPrismCacheCoordinator'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/aegis/Sources/CLI/Commands/Doctor.swift\n- platform constraint: Tokio\n- known complication: a misleading timeout name used in five packages\n\nBoth results are required, but they should remain independently reviewable. Keep public behavior and serialized data unchanged; 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.45,"slice":"mixed","lang":"en"} -{"prompt":"Question: diff --git a/projects/aegis/db/migrations/20260730_events.sql b/projects/aegis/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/aegis/db/migrations/20260730_events.sql\n+++ b/projects/aegis/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nWire AegisEchoRegistryFlow'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.81,"slice":"pasted-context","lang":"en"} -{"prompt":"Ticket OPS-41142: retire the legacy replay path for AegisBeaconStoreFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for AegisBeaconStoreFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.62,"slice":"pasted-context","lang":"en"} -{"prompt":"In projects/aegis/ui/settings/PrivacyPane.tsx hat AegisOpalRouterService ein sporadisches Problem im NATS JetStream-Ablauf. Verfolge Queue, Scheduler und Abbruch, vergleiche Hypothesen und finde die Ursache vor jeder Änderung.\n\nRandbedingungen:\n- NATS JetStream weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf AegisOpalRouterService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um AegisOpalRouterService mit NATS JetStream kompatibel.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"de"} -{"prompt":"The API work is done; what remains for AegisSableParserStore is the visible interaction layer across loading, offline, empty, and success cases. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside AegisSableParserStore\n- keep public behavior and serialized data unchanged\n\nThe relevant code crosses payments, iOS, Kubernetes. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"A previously stable test around AegisSummitProxyStore now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"boundary","lang":"en"} -{"prompt":"For AegisBasilRunnerCoordinator, produce a consumer guide for AegisBasilRunnerCoordinator; once that is complete, give the existing implementation a read-only safety pass. Work from projects/aegis/services/ledger/replay.go, stay with WebGPU, and keep public behavior and serialized data unchanged. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.48,"slice":"mixed","lang":"en"} -{"prompt":"Security flagged AegisTideWorkerService for a read-only pass because its PostgreSQL 17 boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current PostgreSQL 17 operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"# projects/aegis/cmd/exporter/main.py\n[worker.aegiscraneworkspacecoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegiscraneworkspacecoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegiscraneworkspacecoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisCraneWorkspaceCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41159\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/aegis/cmd/exporter/main.py and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.43,"slice":"pasted-context","lang":"en"} -{"prompt":"Before we approve AegisLedgerGateStore, assess whether two validators with subtly different error strings is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"projects/aegis/packages/api/openapi.yaml 里的 AegisCoralUploadStore 最近在 SQLite 流程中出现间歇性问题。 请给出阶段、兼容层、指标、rollback 和 ownership，先不要修改代码。\n\n约束：\n- 继续使用 SQLite\n- 保持兼容性和取消语义\n- 改动只限于 AegisCoralUploadStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"zh"} -{"prompt":"Observation: # projects/aegis/lib/codec/frame.cc\n[worker.aegisdeltacanvasflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisdeltacanvasflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisdeltacanvasflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisDeltaCanvasFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41116\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/aegis/lib/codec/frame.cc. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.36,"slice":"pasted-context","lang":"en"} -{"prompt":"Constraint: projects/aegis/pkg/cache/lease.rs now contains AegisCloudReconcilerFlow's normalization branch three times. Consolidate it behind one private helper, keep call ordering identical, and avoid touching generated code. Please preserve behavior. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Two deliverables are holding up AegisTideWorkerCoordinator. First, separate AegisTideWorkerCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/aegis/src/sync/reconcile.ts, which follows PostgreSQL 17 conventions and currently suffers from duplicate retries after a network handoff. Keep public behavior and serialized data unchanged.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"Teach AegisMosaicGridStore to verify signed continuation tokens, reject cross-tenant cursors, and rotate keys without invalidating tokens issued during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"AegisBeaconStoreCoordinator: polish the last piece","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"vague-eval","lang":"en"} -{"prompt":"Why does AegisFrostPanelStore's WebGPU worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"boundary","lang":"en"} -{"prompt":"Request: Ticket OPS-41139: retire the legacy replay path for AegisIrisBatchFlow\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 AegisIrisBatchFlow 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.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Spell AegisDriftConsoleService's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"core","lang":"en"} -{"prompt":"Goal: // projects/aegis/apps/console/routes/usage.svelte\nfinal class AegisHarborIndexCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 AegisHarborIndexCoordinator 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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"AegisDeltaCanvasCoordinator: polish, then correct","purpose":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.56,"slice":"mixed","lang":"en"} -{"prompt":"Memory attributed to AegisPineMetricsStore rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Does AegisCopperBridgeFlow enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"Support wants the behavior in projects/aegis/app/src/main/SyncWorker.kt recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"boundary","lang":"en"} -{"prompt":"Flip AegisMoonlitSDKStore's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"boundary","lang":"en"} -{"prompt":"I inherited AegisOspreyJobStore and need a careful read of projects/aegis/config/staging.toml before I can sign off on the next release. 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- keep public behavior and serialized data unchanged\n- stay compatible with the existing SQLite deployment\n- keep the work scoped to AegisOspreyJobStore and its direct tests\n\nThis repository spans payments, iOS, Kubernetes; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"boundary","lang":"en"} -{"prompt":"Unify the AegisMicaProfileStore validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Symptom: Two engineers disagree about whether AegisIrisBatchService's cache is authoritative. Walk the reads and writes in projects/aegis/cmd/exporter/main.py and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"AegisAtlasSearchCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"vague-eval","lang":"en"} -{"prompt":"Bump AegisLumenChartService's timeout to 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"core","lang":"en"} -{"prompt":"UI ticket DES-41125: finish the compact AegisBirchMigratorFlow filter experience\n\nRoute: /catalog/search\nSource: projects/aegis/app/src/main/SyncWorker.kt\nFramework: PostgreSQL 17\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring AegisBirchMigratorFlow'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.68,"slice":"pasted-context","lang":"en"} -{"prompt":"Read projects/aegis/pkg/cache/lease.rs and tell me whether AegisSlateEditorService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Ist AegisNimbusFormStore sicher?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"de"} -{"prompt":"Headsup: # projects/aegis/workers/thumbnail/consumer.ex\n[worker.aegisorbitsyncflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisorbitsyncflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisorbitsyncflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisOrbitSyncFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41141\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/aegis/workers/thumbnail/consumer.ex and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.36,"slice":"pasted-context","lang":"en"} -{"prompt":"FYI: Ticket OPS-41112: retire the legacy replay path for AegisNovaPickerFlow\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 AegisNovaPickerFlow 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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Is there a cleaner way to separate AegisOrbitSyncStore's transport, persistence, and retry policy without changing its API or timing behavior? Go ahead and make that structural change. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Set AegisRavenSessionStore's port to 8081","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"boundary","lang":"en"} -{"prompt":"A flaky failure around AegisPineMetricsService survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside AegisPineMetricsService\n- keep public behavior and serialized data unchanged\n\nThe relevant code crosses payments, iOS, Kubernetes. Prefer evidence from the repository and make any assumption explicit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.84,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-41111\n\n08:02 deploy AegisOpalRouterFlow 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 AegisOpalRouterFlow 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.59,"slice":"pasted-context","lang":"en"} -{"prompt":"Ticket OPS-41148: retire the legacy replay path for AegisSlateEditorFlow\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 AegisSlateEditorFlow 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"AegisSlateEditorCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"Meanwhile: # projects/aegis/Sources/App/SessionStore.swift\n[worker.aegisveladrawerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisveladrawerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisveladrawerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisVelaDrawerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41134\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/aegis/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.43,"slice":"pasted-context","lang":"en"} -{"prompt":"Sequence AegisGarnetModalService's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current AegisHarborIndexService design actually guarantees what its callers assume. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside AegisHarborIndexService\n- keep public behavior and serialized data unchanged\n\nThe relevant code crosses payments, iOS, Kubernetes. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Locally: Ticket OPS-41144: retire the legacy replay path for AegisWrenExportFlow\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 AegisWrenExportFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"Is there a cleaner way to separate AegisCedarPolicyFlow's transport, persistence, and retry policy without changing its API or timing behavior? Go ahead and make that structural change. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Production: Ticket OPS-41136: retire the legacy replay path for AegisSummitProxyFlow\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 AegisSummitProxyFlow rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"AegisWrenExportCoordinator: the docs need something","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"vague-eval","lang":"en"} -{"prompt":"AegisSummitProxyCoordinator: could this be clearer","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"vague-eval","lang":"en"} -{"prompt":"Staging: projects/aegis/engine/render/atlas.cpp has grown through several launches, and AegisCopperBridgeService now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing NATS JetStream deployment\n- keep the work scoped to AegisCopperBridgeService and its direct tests\n\nThis repository spans payments, iOS, Kubernetes; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Corrija o timeout de AegisBasilRunnerService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"core","lang":"pt"} -{"prompt":"CI: Ticket OPS-41118: retire the legacy replay path for AegisMoonlitSDKFlow\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 AegisMoonlitSDKFlow 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Security flagged AegisAsterWebhookService for a read-only pass because its WebGPU boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current WebGPU operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"The name pendingAck means two different things across AegisCopperBridgeStore's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Describe AegisSableParserService's error envelope","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"Why is AegisDeltaCanvasService stalling?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"A flaky failure around AegisCloudReconcilerService survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside AegisCloudReconcilerService\n- keep public behavior and serialized data unchanged\n\nThe relevant code crosses payments, iOS, Kubernetes. Prefer evidence from the repository and make any assumption explicit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.87,"slice":"core","lang":"en"} -{"prompt":"diff --git a/projects/aegis/crates/index/src/segment.rs b/projects/aegis/crates/index/src/segment.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/aegis/crates/index/src/segment.rs\n+++ b/projects/aegis/crates/index/src/segment.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is AegisAtlasSearchFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"# projects/aegis/web/components/FilterDrawer.vue\n[worker.aegisfrostpanelflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisfrostpanelflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisfrostpanelflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisFrostPanelFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41147\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/aegis/web/components/FilterDrawer.vue and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.38,"slice":"pasted-context","lang":"en"} -{"prompt":"Two asks around AegisBirchMigratorCoordinator: (1) change AegisBirchMigratorCoordinator's known staging timeout from 15 to 30 seconds; (2) give the existing implementation a read-only safety pass. Keep public behavior and serialized data unchanged, and leave a clear boundary between the resulting artifacts or edits.","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.19,"slice":"mixed","lang":"en"} -{"prompt":"Atlas: Is there a cleaner way to separate AegisCraneWorkspaceFlow's transport, persistence, and retry policy without changing its API or timing behavior? Go ahead and make that structural change. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"En projects/aegis/config/staging.toml, AegisCedarPolicyService tiene un problema intermitente en el flujo de SQLite. Añade el endpoint idempotente con cursor durable, autorización tenant, spans y tests de retry.\n\nRestricciones:\n- seguir con SQLite\n- conservar compatibilidad y cancelación\n- limitar el cambio a AegisCedarPolicyService Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con SQLite alrededor de AegisCedarPolicyService.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.81,"slice":"core","lang":"es"} -{"prompt":"Three teams extended AegisJuniperCLIService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current NATS JetStream operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"# projects/aegis/ml/pipeline/features.py\n[worker.aegisfernsnapshotflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisfernsnapshotflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisfernsnapshotflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisFernSnapshotFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41149\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/aegis/ml/pipeline/features.py. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.43,"slice":"pasted-context","lang":"en"} -{"prompt":"Could the reasoning behind AegisWrenExportService's Tokio choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"AegisWrenExportStore has four wrappers that only translate the same error enum. Collapse them into one adapter and preserve every public case, message, and metric label. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"We need to move AegisVelaDrawerStore from the legacy store to Tokio. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"I inherited AegisDeltaCanvasStore and need a careful read of projects/aegis/engine/render/atlas.cpp before I can sign off on the next release. 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- keep public behavior and serialized data unchanged\n- stay compatible with the existing NATS JetStream deployment\n- keep the work scoped to AegisDeltaCanvasStore and its direct tests\n\nThis repository spans payments, iOS, Kubernetes; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.69,"slice":"boundary","lang":"en"} -{"prompt":"Split projects/aegis/web/components/FilterDrawer.vue by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Fresh release brief for AegisOpalRouterCoordinator:\n- primary outcome: separate AegisOpalRouterCoordinator's policy from transport without behavior changes\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/aegis/workers/thumbnail/consumer.ex\n- platform constraint: NATS JetStream\n- known complication: a query plan that changes after statistics refresh\n\nBoth results are required, but they should remain independently reviewable. Keep public behavior and serialized data unchanged; 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":"refactor","secondary":"writing","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"The behavior of AegisGarnetModalStore is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/aegis/web/components/FilterDrawer.vue. 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- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current WebGPU operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.54,"slice":"boundary","lang":"en"} -{"prompt":"AegisRavenSessionCoordinator: sequence, then ship","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"diff --git a/projects/aegis/src/sync/reconcile.ts b/projects/aegis/src/sync/reconcile.ts\nindex 62d71aa..90f3c1e 100644\n--- a/projects/aegis/src/sync/reconcile.ts\n+++ b/projects/aegis/src/sync/reconcile.ts\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 AegisRavenSessionFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"pasted-context","lang":"en"} -{"prompt":"We need to move AegisBeaconStoreService from the legacy store to WebGPU. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"AegisAtlasSearchStore has four wrappers that only translate the same error enum. Collapse them into one adapter and preserve every public case, message, and metric label. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Match AegisMoonlitSDKService's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} -{"prompt":"AegisCinderAuthCoordinator: sequence, then ship","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Design handed over a final pass for AegisLedgerGateService, and the basic data flow in projects/aegis/src/sync/reconcile.ts already works. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing PostgreSQL 17 deployment\n- keep the work scoped to AegisLedgerGateService and its direct tests\n\nThis repository spans payments, iOS, Kubernetes; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Polish the AegisEchoRegistryService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"Beacon: # projects/aegis/db/migrations/20260730_events.sql\n[worker.aegistideworkerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegistideworkerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegistideworkerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisTideWorkerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41110\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/aegis/db/migrations/20260730_events.sql. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"pasted-context","lang":"en"} -{"prompt":"Support wants the behavior in projects/aegis/ui/settings/PrivacyPane.tsx recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"Cinder: We need to move AegisPineMetricsFlow from the legacy store to WebGPU. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Delta: // projects/aegis/services/ledger/replay.go\nfinal class AegisMosaicGridFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Split AegisMosaicGridFlow 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.82,"slice":"pasted-context","lang":"pt"} -{"prompt":"Read projects/aegis/db/migrations/20260730_events.sql and tell me whether AegisAmberFilterStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Make AegisFlintTimelineService keyboard navigable","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"AegisFernSnapshotCoordinator: smooth out this interaction","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"vague-eval","lang":"en"} -{"prompt":"Could the reasoning behind AegisAtlasSearchService's SQLite choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"AegisSpruceDaemonCoordinator needs a paired pass: lay out a staged migration for AegisSpruceDaemonCoordinator, plus then implement the bounded durable-cursor handler. Use projects/aegis/lib/codec/frame.cc as the source of truth, preserve the NATS JetStream contract, and avoid unrelated cleanup.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.74,"slice":"mixed","lang":"en"} -{"prompt":"AegisMapleQueueCoordinator needs a paired pass: lay out a staged migration for AegisMapleQueueCoordinator, plus then implement the bounded durable-cursor handler. Use projects/aegis/infra/modules/edge/main.tf as the source of truth, preserve the WebGPU contract, and avoid unrelated cleanup.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.77,"slice":"mixed","lang":"en"} -{"prompt":"Ember: diff --git a/projects/aegis/services/ledger/replay.go b/projects/aegis/services/ledger/replay.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/aegis/services/ledger/replay.go\n+++ b/projects/aegis/services/ledger/replay.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is AegisGarnetModalFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"AegisRainfallDBStore occasionally exhibits cancellation being swallowed at the repository boundary, but only after a reconnect. Follow the data and cancellation paths in projects/aegis/Sources/App/SessionStore.swift and identify the cause before changing anything.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"UI ticket DES-41133: finish the compact AegisKiteSchedulerFlow filter experience\n\nRoute: /catalog/search\nSource: projects/aegis/packages/api/openapi.yaml\nFramework: SQLite\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 AegisKiteSchedulerFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.76,"slice":"pasted-context","lang":"en"} -{"prompt":"Frost: // projects/aegis/crates/index/src/segment.rs\nfinal class AegisCloudReconcilerCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 AegisCloudReconcilerCoordinator; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Garnet: The AegisMosaicGridService empty state in projects/aegis/services/ledger/replay.go needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"core","lang":"en"} -{"prompt":"Release engineering needs a AegisVelaDrawerService changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"AegisNimbusFormCoordinator: restructure, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.73,"slice":"mixed","lang":"en"} -{"prompt":"AegisEmberRelayService leaks tasks on shutdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Harbor: projects/aegis/config/staging.toml の AegisCoralUploadService で、SQLite の flow に断続的な問題が起きています。 queue、scheduler、cancel 経路を追い、仮説を比較して、変更前に原因を特定してください。\n\n制約:\n- SQLite を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は AegisCoralUploadService のみ","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"ja"} -{"prompt":"Iris: The AegisBeaconStoreStore 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.14,"slice":"boundary","lang":"en"} -{"prompt":"A copied hex color in AegisAcornWidgetStore lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"boundary","lang":"en"} -{"prompt":"Two asks around AegisDriftConsoleCoordinator: (1) assess ownership and failure handling in projects/aegis/workers/thumbnail/consumer.ex; (2) capture the contract and rollback note for consumers. Keep public behavior and serialized data unchanged, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.62,"slice":"mixed","lang":"en"} -{"prompt":"Support wants the behavior in projects/aegis/services/ledger/replay.go recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"Juniper: # projects/aegis/lib/codec/frame.cc\n[worker.aegiscopperbridgecoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegiscopperbridgecoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegiscopperbridgecoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisCopperBridgeCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41156\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/aegis/lib/codec/frame.cc and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.36,"slice":"pasted-context","lang":"en"} -{"prompt":"2026-07-30T08:14:11.409Z level=info service=aegisbasilrunnerflow pod=aegisbasilrunnerflow-7cf8 request_id=41127 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=aegisbasilrunnerflow request_id=41127 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=aegisbasilrunnerflow request_id=41127 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=aegisbasilrunnerflow request_id=41127 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=aegisbasilrunnerflow request_id=41127 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=aegisbasilrunnerflow request_id=41127 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=aegisbasilrunnerflow request_id=41127 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=aegisbasilrunnerflow request_id=41127 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nReconstruct the AegisBasilRunnerFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.92,"slice":"pasted-context","lang":"en"} -{"prompt":"Ticket OPS-41157: retire the legacy replay path for AegisAsterWebhookCoordinator\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 AegisAsterWebhookCoordinator 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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Split AegisCinderAuthStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"For AegisLumenChartCoordinator, lay out a staged migration for AegisLumenChartCoordinator; once that is complete, consolidate the duplicated normalization paths without changing behavior. Work from projects/aegis/Sources/App/SessionStore.swift, stay with Tokio, and keep public behavior and serialized data unchanged. Keep the two outcomes separately reviewable.","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.82,"slice":"mixed","lang":"en"} -{"prompt":"Payments: Support wants the behavior in projects/aegis/app/src/main/SyncWorker.kt recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"AegisMosaicGridCoordinator: take care of the warning","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"Give AegisKiteSchedulerService a loading skeleton","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} -{"prompt":"UI ticket DES-41143: finish the compact AegisCoralUploadFlow filter experience\n\nRoute: /catalog/search\nSource: projects/aegis/config/staging.toml\nFramework: SQLite\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring AegisCoralUploadFlow'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.76,"slice":"pasted-context","lang":"en"} -{"prompt":"Kestrel: Split projects/aegis/packages/api/openapi.yaml by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"AegisWillowCodecCoordinator needs a paired pass: lay out a staged migration for AegisWillowCodecCoordinator, plus then implement the bounded durable-cursor handler. Use projects/aegis/cmd/exporter/main.py as the source of truth, preserve the Tokio contract, and avoid unrelated cleanup.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.82,"slice":"mixed","lang":"en"} -{"prompt":"Ticket OPS-41126: retire the legacy replay path for AegisSpruceDaemonFlow\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\nDeliver the AegisSpruceDaemonFlow 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.83,"slice":"pasted-context","lang":"en"} -{"prompt":"Corrige le timeout de AegisBasilRunnerStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"boundary","lang":"fr"} -{"prompt":"AegisMicaProfileCoordinator: document, then correct","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.48,"slice":"mixed","lang":"en"} -{"prompt":"Two deliverables are holding up AegisOspreyJobCoordinator. First, produce a consumer guide for AegisOspreyJobCoordinator. In the same workstream, correct the known stale timeout beside it. The relevant starting point is projects/aegis/config/staging.toml, which follows SQLite conventions and currently suffers from memory growth during hour-long imports. Keep public behavior and serialized data unchanged.\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":"writing","secondary":"quickFix","mixed":true,"difficulty":0.67,"slice":"mixed","lang":"en"} -{"prompt":"Map AegisRavenSessionService's ownership split","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-41129\n\n08:02 deploy AegisWillowCodecFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Turn the material above into a concise AegisWillowCodecFlow 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.67,"slice":"pasted-context","lang":"fr"} -{"prompt":"AegisSableParserCoordinator is blocking the next release because stale cursors when a page is resumed. I need two concrete outcomes from a single pass: finish AegisSableParserCoordinator's responsive empty and retry states, and capture the contract and rollback note for consumers. Use the existing PostgreSQL 17 conventions in projects/aegis/app/src/main/SyncWorker.kt; keep public behavior and serialized data unchanged. 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":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Lay out a two-milestone strategy for eliminating a deadlock that appears only during shutdown in AegisRainfallDBFlow, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"The AegisFernSnapshotService surface in projects/aegis/ml/pipeline/features.py is stable now; turn its edge cases into API documentation with one successful example and one cancellation example.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Rename AegisLumenChartStore's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"projects/aegis/workers/thumbnail/consumer.ex の AegisJuniperCLIFlow で、NATS JetStream の flow に断続的な問題が起きています。 段階、互換性、metrics、rollback、ownership を提案し、コード変更の前で止めてください。\n\n制約:\n- NATS JetStream を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は AegisJuniperCLIFlow のみ","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"ja"} -{"prompt":"Any races in AegisMicaProfileService?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"projects/aegis/src/sync/reconcile.ts has grown through several launches, and AegisTideWorkerStore now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing PostgreSQL 17 deployment\n- keep the work scoped to AegisTideWorkerStore and its direct tests\n\nThis repository spans payments, iOS, Kubernetes; use its existing conventions rather than importing a new abstraction.\n\nThe individual edits look tiny, but the semantic cleanup spans the repository and must preserve behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.69,"slice":"boundary","lang":"en"} -{"prompt":"AegisAmberFilterCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"vague-eval","lang":"en"} -{"prompt":"For AegisKiteSchedulerCoordinator, ship the idempotent AegisKiteSchedulerCoordinator replay endpoint; once that is complete, capture the contract and rollback note for consumers. Work from projects/aegis/config/staging.toml, stay with SQLite, and keep public behavior and serialized data unchanged. Keep the two outcomes separately reviewable.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.74,"slice":"mixed","lang":"en"} -{"prompt":"Lumen: # projects/aegis/engine/render/atlas.cpp\n[worker.aegisquartzplayerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisquartzplayerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisquartzplayerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisQuartzPlayerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41146\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/aegis/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.36,"slice":"pasted-context","lang":"en"} -{"prompt":"Summarize the AegisMapleQueueStore changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"en"} -{"prompt":"The behavior of AegisOspreyJobService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/aegis/packages/api/openapi.yaml. 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- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current SQLite operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Before touching projects/aegis/src/sync/reconcile.ts, 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.62,"slice":"boundary","lang":"en"} -{"prompt":"Em projects/aegis/app/src/main/SyncWorker.kt, o AegisMarbleTokenStore tem um problema intermitente no fluxo de PostgreSQL 17. Finalize o layout responsivo, estados vazio e retry, foco por teclado, dark mode e reduced motion.\n\nRestrições:\n- continuar com PostgreSQL 17\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao AegisMarbleTokenStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"boundary","lang":"pt"} -{"prompt":"AegisAcornWidgetCoordinator: rethink this area","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"Any races in AegisPrismCacheService?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Queue AegisKiteSchedulerStore's expired sessions","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"Maple: Ticket OPS-41140: retire the legacy replay path for AegisAmberFilterFlow\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 AegisAmberFilterFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"pasted-context","lang":"en"} -{"prompt":"Nimbus: Ticket OPS-41152: retire the legacy replay path for AegisPineMetricsCoordinator\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 AegisPineMetricsCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.62,"slice":"pasted-context","lang":"en"} -{"prompt":"Investigate the AegisCinderAuthService hang","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-42142\n\n08:02 deploy BorealNimbusFormFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current BorealNimbusFormFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"Release engineering needs a BorealFlintTimelineService changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} +{"prompt":"AegisFlintTimelineCoordinator: ship, then document","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"projects/aegis/lib/codec/frame.cc now contains AegisSummitProxyService'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.4,"slice":"core","lang":"en"} +{"prompt":"The AegisHarborIndexStore surface in projects/aegis/apps/console/routes/usage.svelte 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":"Split AegisDriftConsoleStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"AegisGarnetModalCoordinator: diagnose, then correct","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Please resist widening this one: AegisCraneWorkspaceStore works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside AegisCraneWorkspaceStore\n- keep public behavior and serialized data unchanged\n\nThe relevant code crosses payments, iOS, Kubernetes. Prefer evidence from the repository and make any assumption explicit.\n\nThe cause and exact value change are already known, so keep this as a contained correction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"En projects/aegis/workers/thumbnail/consumer.ex, AegisOpalRouterStore tiene un problema intermitente en el flujo de NATS JetStream. La causa ya está clara: cambia solo el timeout de staging de 15 a 30 segundos y ajusta su assertion.\n\nRestricciones:\n- seguir con NATS JetStream\n- conservar compatibilidad y cancelación\n- limitar el cambio a AegisOpalRouterStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"es"} +{"prompt":"Ticket OPS-41124: retire the legacy replay path for AegisLumenChartFlow\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 AegisLumenChartFlow 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":"# projects/aegis/config/staging.toml\n[worker.aegiscinderauthflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegiscinderauthflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegiscinderauthflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisCinderAuthFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41123\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/aegis/config/staging.toml and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Apparently: # projects/aegis/workers/thumbnail/consumer.ex\n[worker.aegisflinttimelineflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisflinttimelineflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisflinttimelineflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisFlintTimelineFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41121\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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Align AegisFlintTimelineFlow'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":"Bring AegisIrisBatchStore'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":"Release verification found a single stale AegisRainfallDBService value; the cause, desired value, and affected assertion are already agreed. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current Tokio operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"AegisPrismCacheStore is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. 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- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current Tokio operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes 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":"Two asks around AegisEmberRelayCoordinator: (1) assess ownership and failure handling in projects/aegis/crates/index/src/segment.rs; (2) capture the contract and rollback note for consumers. Keep public behavior and serialized data unchanged, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"diff --git a/projects/aegis/Sources/App/SessionStore.swift b/projects/aegis/Sources/App/SessionStore.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/aegis/Sources/App/SessionStore.swift\n+++ b/projects/aegis/Sources/App/SessionStore.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate AegisRainfallDBCoordinator'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":"AegisQuartzPlayerCoordinator: ship a sensible version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"AegisFrostPanelCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Please turn AegisFrostPanelService'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":"Describe AegisWillowCodecStore's error envelope","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"AegisMoonlitSDKCoordinator: sequence, then restructure","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"AegisOrbitSyncCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Lately: // projects/aegis/apps/console/routes/usage.svelte\nfinal class AegisMarbleTokenFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 AegisMarbleTokenFlow 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":"Oddly: // projects/aegis/ui/settings/PrivacyPane.tsx\nfinal class AegisDriftConsoleFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 AegisDriftConsoleFlow; 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":"AegisCoralUploadCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Summarize the AegisSpruceDaemonService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Responsive layout for AegisFlintTimelineStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"For AegisEchoRegistryCoordinator, separate AegisEchoRegistryCoordinator's policy from transport without behavior changes; once that is complete, correct the known stale timeout beside it. Work from projects/aegis/src/sync/reconcile.ts, stay with PostgreSQL 17, and keep public behavior and serialized data unchanged. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Incident timeline — INC-41153\n\n08:02 deploy AegisCedarPolicyCoordinator 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Turn the material above into a concise AegisCedarPolicyCoordinator 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":"UI ticket DES-41151: finish the compact AegisJuniperCLICoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/aegis/ui/settings/PrivacyPane.tsx\nFramework: NATS JetStream\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 AegisJuniperCLICoordinator'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":"Currently: projects/aegis/apps/console/routes/usage.svelte 里的 AegisMarbleTokenService 最近在 PostgreSQL 17 流程中出现间歇性问题。 请实现幂等 endpoint，包含持久 cursor、tenant 鉴权、spans 和 retry 测试。\n\n约束：\n- 继续使用 PostgreSQL 17\n- 保持兼容性和取消语义\n- 改动只限于 AegisMarbleTokenService","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"zh"} +{"prompt":"Split projects/aegis/workers/thumbnail/consumer.ex by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current AegisNovaPickerStore design actually guarantees what its callers assume. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside AegisNovaPickerStore\n- keep public behavior and serialized data unchanged\n\nThe relevant code crosses payments, iOS, Kubernetes. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Release engineering needs a AegisAmberFilterService 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":"diff --git a/projects/aegis/Sources/App/SessionStore.swift b/projects/aegis/Sources/App/SessionStore.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/aegis/Sources/App/SessionStore.swift\n+++ b/projects/aegis/Sources/App/SessionStore.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is AegisPrismCacheFlow'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":"UI ticket DES-41145: finish the compact AegisAcornWidgetFlow filter experience\n\nRoute: /catalog/search\nSource: projects/aegis/app/src/main/SyncWorker.kt\nFramework: PostgreSQL 17\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Use the UI evidence to complete AegisAcornWidgetFlow'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":"Incident timeline — INC-41115\n\n08:02 deploy AegisSableParserFlow 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 AegisSableParserFlow 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":"AegisIrisBatchCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"AegisVelaDrawerCoordinator: give it a nicer flow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Test Suite 'AegisMicaProfileFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[AegisMicaProfileFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/aegis/infra/modules/edge/main.tf:144: error: -[AegisMicaProfileFlowTests 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 '-[AegisMicaProfileFlowTests 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\nFind the source of this AegisMicaProfileFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Test Suite 'AegisEmberRelayFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[AegisEmberRelayFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/aegis/pkg/cache/lease.rs:144: error: -[AegisEmberRelayFlowTests 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 '-[AegisEmberRelayFlowTests 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 AegisEmberRelayFlow'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":"Today: Incident timeline — INC-41119\n\n08:02 deploy AegisNimbusFormFlow 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 AegisNimbusFormFlow 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":"Unifie les validateurs de AegisNimbusFormService","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"fr"} +{"prompt":"Why is AegisMapleQueueService stalling?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Context: # projects/aegis/db/migrations/20260730_events.sql\n[worker.aegisledgergatecoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisledgergatecoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisledgergatecoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisLedgerGateCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41150\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/aegis/db/migrations/20260730_events.sql and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Move AegisEmberRelayStore behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-41132: retire the legacy replay path for AegisMapleQueueFlow\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 AegisMapleQueueFlow 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":"We need to move AegisQuartzPlayerStore from the legacy store to NATS JetStream. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Draft AegisSpruceDaemonStore's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"AegisBirchMigratorService's SyncWorker.kt needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"The next client release depends on a new AegisNovaPickerService capability in projects/aegis/internal/auth/refresh.go, with WebGPU already chosen by the platform group. Implement the endpoint and durable cursor, enforce tenant authorization and idempotency, emit useful spans, cap work per request, and include focused tests for retries, cancellation, and malformed cursors.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing WebGPU deployment\n- keep the work scoped to AegisNovaPickerService and its direct tests\n\nThis repository spans payments, iOS, Kubernetes; use its existing conventions rather than importing a new abstraction.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"AegisMarbleTokenCoordinator: handle the lingering thing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Clarify AegisEchoRegistryStore's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Where did AegisWillowCodecService's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Background: UI ticket DES-41113: finish the compact AegisOspreyJobFlow filter experience\n\nRoute: /catalog/search\nSource: projects/aegis/packages/api/openapi.yaml\nFramework: SQLite\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\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Bring AegisOspreyJobFlow'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":"AegisNovaPickerCoordinator is blocking the next release because two validators with subtly different error strings. I need two concrete outcomes from a single pass: finish AegisNovaPickerCoordinator's responsive empty and retry states, and capture the contract and rollback note for consumers. Use the existing WebGPU conventions in projects/aegis/infra/modules/edge/main.tf; keep public behavior and serialized data unchanged. 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":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Production says AegisCloudReconcilerStore is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Reconstruct the failing timeline from logs and tests, identify which invariant first breaks, and distinguish causal signals from effects or cleanup noise.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current SQLite operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Two engineers disagree about whether AegisFernSnapshotStore's cache is authoritative. Walk the reads and writes in projects/aegis/cmd/exporter/main.py and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Before we approve AegisSlateEditorStore, assess whether two validators with subtly different error strings is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Fresh release brief for AegisPrismCacheCoordinator:\n- primary outcome: change AegisPrismCacheCoordinator'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/aegis/Sources/CLI/Commands/Doctor.swift\n- platform constraint: Tokio\n- known complication: a misleading timeout name used in five packages\n\nBoth results are required, but they should remain independently reviewable. Keep public behavior and serialized data unchanged; 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.6,"slice":"mixed","lang":"en"} +{"prompt":"Question: diff --git a/projects/aegis/db/migrations/20260730_events.sql b/projects/aegis/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/aegis/db/migrations/20260730_events.sql\n+++ b/projects/aegis/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nWire AegisEchoRegistryFlow'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.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Ticket OPS-41142: retire the legacy replay path for AegisBeaconStoreFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for AegisBeaconStoreFlow, 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":"In projects/aegis/ui/settings/PrivacyPane.tsx hat AegisOpalRouterService ein sporadisches Problem im NATS JetStream-Ablauf. Verfolge Queue, Scheduler und Abbruch, vergleiche Hypothesen und finde die Ursache vor jeder Änderung.\n\nRandbedingungen:\n- NATS JetStream weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf AegisOpalRouterService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um AegisOpalRouterService mit NATS JetStream kompatibel.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} +{"prompt":"The API work is done; what remains for AegisSableParserStore is the visible interaction layer across loading, offline, empty, and success cases. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside AegisSableParserStore\n- keep public behavior and serialized data unchanged\n\nThe relevant code crosses payments, iOS, Kubernetes. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"A previously stable test around AegisSummitProxyStore 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":"For AegisBasilRunnerCoordinator, produce a consumer guide for AegisBasilRunnerCoordinator; once that is complete, give the existing implementation a read-only safety pass. Work from projects/aegis/services/ledger/replay.go, stay with WebGPU, and keep public behavior and serialized data unchanged. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Security flagged AegisTideWorkerService for a read-only pass because its PostgreSQL 17 boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current PostgreSQL 17 operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes 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":"# projects/aegis/cmd/exporter/main.py\n[worker.aegiscraneworkspacecoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegiscraneworkspacecoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegiscraneworkspacecoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisCraneWorkspaceCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41159\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/aegis/cmd/exporter/main.py and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Before we approve AegisLedgerGateStore, assess whether two validators with subtly different error strings is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"projects/aegis/packages/api/openapi.yaml 里的 AegisCoralUploadStore 最近在 SQLite 流程中出现间歇性问题。 请给出阶段、兼容层、指标、rollback 和 ownership，先不要修改代码。\n\n约束：\n- 继续使用 SQLite\n- 保持兼容性和取消语义\n- 改动只限于 AegisCoralUploadStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"Observation: # projects/aegis/lib/codec/frame.cc\n[worker.aegisdeltacanvasflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisdeltacanvasflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisdeltacanvasflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisDeltaCanvasFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41116\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/aegis/lib/codec/frame.cc. 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":"Constraint: projects/aegis/pkg/cache/lease.rs now contains AegisCloudReconcilerFlow's normalization branch three times. Consolidate it behind one private helper, keep call ordering identical, and avoid touching generated code. Please preserve behavior. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Two deliverables are holding up AegisTideWorkerCoordinator. First, separate AegisTideWorkerCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/aegis/src/sync/reconcile.ts, which follows PostgreSQL 17 conventions and currently suffers from duplicate retries after a network handoff. Keep public behavior and serialized data unchanged.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Teach AegisMosaicGridStore to verify signed continuation tokens, reject cross-tenant cursors, and rotate keys without invalidating tokens issued during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"AegisBeaconStoreCoordinator: polish the last piece","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Why does AegisFrostPanelStore's WebGPU worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Request: Ticket OPS-41139: retire the legacy replay path for AegisIrisBatchFlow\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 AegisIrisBatchFlow 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":"Spell AegisDriftConsoleService's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Goal: // projects/aegis/apps/console/routes/usage.svelte\nfinal class AegisHarborIndexCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 AegisHarborIndexCoordinator 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":"AegisDeltaCanvasCoordinator: polish, then correct","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Memory attributed to AegisPineMetricsStore rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Does AegisCopperBridgeFlow enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Support wants the behavior in projects/aegis/app/src/main/SyncWorker.kt recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Flip AegisMoonlitSDKStore's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"I inherited AegisOspreyJobStore and need a careful read of projects/aegis/config/staging.toml before I can sign off on the next release. 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- keep public behavior and serialized data unchanged\n- stay compatible with the existing SQLite deployment\n- keep the work scoped to AegisOspreyJobStore and its direct tests\n\nThis repository spans payments, iOS, Kubernetes; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Unify the AegisMicaProfileStore validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Symptom: Two engineers disagree about whether AegisIrisBatchService's cache is authoritative. Walk the reads and writes in projects/aegis/cmd/exporter/main.py and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"AegisAtlasSearchCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump AegisLumenChartService's timeout to 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-41125: finish the compact AegisBirchMigratorFlow filter experience\n\nRoute: /catalog/search\nSource: projects/aegis/app/src/main/SyncWorker.kt\nFramework: PostgreSQL 17\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring AegisBirchMigratorFlow'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":"Read projects/aegis/pkg/cache/lease.rs and tell me whether AegisSlateEditorService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Ist AegisNimbusFormStore sicher?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"de"} +{"prompt":"Headsup: # projects/aegis/workers/thumbnail/consumer.ex\n[worker.aegisorbitsyncflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisorbitsyncflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisorbitsyncflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisOrbitSyncFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41141\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/aegis/workers/thumbnail/consumer.ex and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"pasted-context","lang":"en"} +{"prompt":"FYI: Ticket OPS-41112: retire the legacy replay path for AegisNovaPickerFlow\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 AegisNovaPickerFlow 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":"Is there a cleaner way to separate AegisOrbitSyncStore's transport, persistence, and retry policy without changing its API or timing behavior? Go ahead and make that structural change. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Set AegisRavenSessionStore's port to 8081","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"A flaky failure around AegisPineMetricsService survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside AegisPineMetricsService\n- keep public behavior and serialized data unchanged\n\nThe relevant code crosses payments, iOS, Kubernetes. Prefer evidence from the repository and make any assumption explicit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-41111\n\n08:02 deploy AegisOpalRouterFlow 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 AegisOpalRouterFlow 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":"Ticket OPS-41148: retire the legacy replay path for AegisSlateEditorFlow\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 AegisSlateEditorFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"AegisSlateEditorCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Meanwhile: # projects/aegis/Sources/App/SessionStore.swift\n[worker.aegisveladrawerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisveladrawerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisveladrawerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisVelaDrawerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41134\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/aegis/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":"Sequence AegisGarnetModalService's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current AegisHarborIndexService design actually guarantees what its callers assume. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside AegisHarborIndexService\n- keep public behavior and serialized data unchanged\n\nThe relevant code crosses payments, iOS, Kubernetes. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Locally: Ticket OPS-41144: retire the legacy replay path for AegisWrenExportFlow\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 AegisWrenExportFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Is there a cleaner way to separate AegisCedarPolicyFlow's transport, persistence, and retry policy without changing its API or timing behavior? Go ahead and make that structural change. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Production: Ticket OPS-41136: retire the legacy replay path for AegisSummitProxyFlow\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 AegisSummitProxyFlow 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":"AegisWrenExportCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"AegisSummitProxyCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Staging: projects/aegis/engine/render/atlas.cpp has grown through several launches, and AegisCopperBridgeService now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing NATS JetStream deployment\n- keep the work scoped to AegisCopperBridgeService and its direct tests\n\nThis repository spans payments, iOS, Kubernetes; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Corrija o timeout de AegisBasilRunnerService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"pt"} +{"prompt":"CI: Ticket OPS-41118: retire the legacy replay path for AegisMoonlitSDKFlow\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 AegisMoonlitSDKFlow 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":"Security flagged AegisAsterWebhookService for a read-only pass because its WebGPU boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current WebGPU operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes 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 name pendingAck means two different things across AegisCopperBridgeStore's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Describe AegisSableParserService's error envelope","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Why is AegisDeltaCanvasService stalling?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"A flaky failure around AegisCloudReconcilerService survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside AegisCloudReconcilerService\n- keep public behavior and serialized data unchanged\n\nThe relevant code crosses payments, iOS, Kubernetes. Prefer evidence from the repository and make any assumption explicit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/aegis/crates/index/src/segment.rs b/projects/aegis/crates/index/src/segment.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/aegis/crates/index/src/segment.rs\n+++ b/projects/aegis/crates/index/src/segment.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is AegisAtlasSearchFlow'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/aegis/web/components/FilterDrawer.vue\n[worker.aegisfrostpanelflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisfrostpanelflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisfrostpanelflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisFrostPanelFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41147\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/aegis/web/components/FilterDrawer.vue and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Two asks around AegisBirchMigratorCoordinator: (1) change AegisBirchMigratorCoordinator's known staging timeout from 15 to 30 seconds; (2) give the existing implementation a read-only safety pass. Keep public behavior and serialized data unchanged, and leave a clear boundary between the resulting artifacts or edits.","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Atlas: Is there a cleaner way to separate AegisCraneWorkspaceFlow's transport, persistence, and retry policy without changing its API or timing behavior? Go ahead and make that structural change. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"En projects/aegis/config/staging.toml, AegisCedarPolicyService tiene un problema intermitente en el flujo de SQLite. Añade el endpoint idempotente con cursor durable, autorización tenant, spans y tests de retry.\n\nRestricciones:\n- seguir con SQLite\n- conservar compatibilidad y cancelación\n- limitar el cambio a AegisCedarPolicyService Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con SQLite alrededor de AegisCedarPolicyService.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"es"} +{"prompt":"Three teams extended AegisJuniperCLIService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current NATS JetStream operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes 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":"# projects/aegis/ml/pipeline/features.py\n[worker.aegisfernsnapshotflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisfernsnapshotflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisfernsnapshotflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisFernSnapshotFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41149\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/aegis/ml/pipeline/features.py. 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":"Could the reasoning behind AegisWrenExportService's Tokio choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"AegisWrenExportStore has four wrappers that only translate the same error enum. Collapse them into one adapter and preserve every public case, message, and metric label. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"We need to move AegisVelaDrawerStore from the legacy store to Tokio. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"I inherited AegisDeltaCanvasStore and need a careful read of projects/aegis/engine/render/atlas.cpp before I can sign off on the next release. 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- keep public behavior and serialized data unchanged\n- stay compatible with the existing NATS JetStream deployment\n- keep the work scoped to AegisDeltaCanvasStore and its direct tests\n\nThis repository spans payments, iOS, Kubernetes; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Split projects/aegis/web/components/FilterDrawer.vue by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Fresh release brief for AegisOpalRouterCoordinator:\n- primary outcome: separate AegisOpalRouterCoordinator's policy from transport without behavior changes\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/aegis/workers/thumbnail/consumer.ex\n- platform constraint: NATS JetStream\n- known complication: a query plan that changes after statistics refresh\n\nBoth results are required, but they should remain independently reviewable. Keep public behavior and serialized data unchanged; 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":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"The behavior of AegisGarnetModalStore is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/aegis/web/components/FilterDrawer.vue. 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- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current WebGPU operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes 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":"AegisRavenSessionCoordinator: sequence, then ship","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} +{"prompt":"diff --git a/projects/aegis/src/sync/reconcile.ts b/projects/aegis/src/sync/reconcile.ts\nindex 62d71aa..90f3c1e 100644\n--- a/projects/aegis/src/sync/reconcile.ts\n+++ b/projects/aegis/src/sync/reconcile.ts\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 AegisRavenSessionFlow'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":"We need to move AegisBeaconStoreService from the legacy store to WebGPU. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"AegisAtlasSearchStore has four wrappers that only translate the same error enum. Collapse them into one adapter and preserve every public case, message, and metric label. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Match AegisMoonlitSDKService's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"AegisCinderAuthCoordinator: sequence, then ship","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} +{"prompt":"Design handed over a final pass for AegisLedgerGateService, and the basic data flow in projects/aegis/src/sync/reconcile.ts already works. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing PostgreSQL 17 deployment\n- keep the work scoped to AegisLedgerGateService and its direct tests\n\nThis repository spans payments, iOS, Kubernetes; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Polish the AegisEchoRegistryService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Beacon: # projects/aegis/db/migrations/20260730_events.sql\n[worker.aegistideworkerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegistideworkerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegistideworkerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisTideWorkerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41110\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/aegis/db/migrations/20260730_events.sql. 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":"Support wants the behavior in projects/aegis/ui/settings/PrivacyPane.tsx recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Cinder: We need to move AegisPineMetricsFlow from the legacy store to WebGPU. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Delta: // projects/aegis/services/ledger/replay.go\nfinal class AegisMosaicGridFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Split AegisMosaicGridFlow 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":"Read projects/aegis/db/migrations/20260730_events.sql and tell me whether AegisAmberFilterStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Make AegisFlintTimelineService keyboard navigable","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"AegisFernSnapshotCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Could the reasoning behind AegisAtlasSearchService's SQLite choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"AegisSpruceDaemonCoordinator needs a paired pass: lay out a staged migration for AegisSpruceDaemonCoordinator, plus then implement the bounded durable-cursor handler. Use projects/aegis/lib/codec/frame.cc as the source of truth, preserve the NATS JetStream contract, and avoid unrelated cleanup.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"AegisMapleQueueCoordinator needs a paired pass: lay out a staged migration for AegisMapleQueueCoordinator, plus then implement the bounded durable-cursor handler. Use projects/aegis/infra/modules/edge/main.tf as the source of truth, preserve the WebGPU contract, and avoid unrelated cleanup.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Ember: diff --git a/projects/aegis/services/ledger/replay.go b/projects/aegis/services/ledger/replay.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/aegis/services/ledger/replay.go\n+++ b/projects/aegis/services/ledger/replay.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is AegisGarnetModalFlow'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":"AegisRainfallDBStore occasionally exhibits cancellation being swallowed at the repository boundary, but only after a reconnect. Follow the data and cancellation paths in projects/aegis/Sources/App/SessionStore.swift and identify the cause before changing anything.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-41133: finish the compact AegisKiteSchedulerFlow filter experience\n\nRoute: /catalog/search\nSource: projects/aegis/packages/api/openapi.yaml\nFramework: SQLite\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 AegisKiteSchedulerFlow'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":"Frost: // projects/aegis/crates/index/src/segment.rs\nfinal class AegisCloudReconcilerCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 AegisCloudReconcilerCoordinator; 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":"Garnet: The AegisMosaicGridService empty state in projects/aegis/services/ledger/replay.go needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Release engineering needs a AegisVelaDrawerService 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":"AegisNimbusFormCoordinator: restructure, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"AegisEmberRelayService leaks tasks on shutdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Harbor: projects/aegis/config/staging.toml の AegisCoralUploadService で、SQLite の flow に断続的な問題が起きています。 queue、scheduler、cancel 経路を追い、仮説を比較して、変更前に原因を特定してください。\n\n制約:\n- SQLite を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は AegisCoralUploadService のみ","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"} +{"prompt":"Iris: The AegisBeaconStoreStore 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":"A copied hex color in AegisAcornWidgetStore lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Two asks around AegisDriftConsoleCoordinator: (1) assess ownership and failure handling in projects/aegis/workers/thumbnail/consumer.ex; (2) capture the contract and rollback note for consumers. Keep public behavior and serialized data unchanged, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Support wants the behavior in projects/aegis/services/ledger/replay.go recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Juniper: # projects/aegis/lib/codec/frame.cc\n[worker.aegiscopperbridgecoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegiscopperbridgecoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegiscopperbridgecoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisCopperBridgeCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41156\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/aegis/lib/codec/frame.cc and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"2026-07-30T08:14:11.409Z level=info service=aegisbasilrunnerflow pod=aegisbasilrunnerflow-7cf8 request_id=41127 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=aegisbasilrunnerflow request_id=41127 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=aegisbasilrunnerflow request_id=41127 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=aegisbasilrunnerflow request_id=41127 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=aegisbasilrunnerflow request_id=41127 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=aegisbasilrunnerflow request_id=41127 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=aegisbasilrunnerflow request_id=41127 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=aegisbasilrunnerflow request_id=41127 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nReconstruct the AegisBasilRunnerFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Ticket OPS-41157: retire the legacy replay path for AegisAsterWebhookCoordinator\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 AegisAsterWebhookCoordinator 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":"Split AegisCinderAuthStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"For AegisLumenChartCoordinator, lay out a staged migration for AegisLumenChartCoordinator; once that is complete, consolidate the duplicated normalization paths without changing behavior. Work from projects/aegis/Sources/App/SessionStore.swift, stay with Tokio, and keep public behavior and serialized data unchanged. Keep the two outcomes separately reviewable.","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Payments: Support wants the behavior in projects/aegis/app/src/main/SyncWorker.kt recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"AegisMosaicGridCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Give AegisKiteSchedulerService a loading skeleton","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-41143: finish the compact AegisCoralUploadFlow filter experience\n\nRoute: /catalog/search\nSource: projects/aegis/config/staging.toml\nFramework: SQLite\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring AegisCoralUploadFlow's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Kestrel: Split projects/aegis/packages/api/openapi.yaml by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"AegisWillowCodecCoordinator needs a paired pass: lay out a staged migration for AegisWillowCodecCoordinator, plus then implement the bounded durable-cursor handler. Use projects/aegis/cmd/exporter/main.py as the source of truth, preserve the Tokio contract, and avoid unrelated cleanup.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Ticket OPS-41126: retire the legacy replay path for AegisSpruceDaemonFlow\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\nDeliver the AegisSpruceDaemonFlow server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Corrige le timeout de AegisBasilRunnerStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"fr"} +{"prompt":"AegisMicaProfileCoordinator: document, then correct","purpose":"writing","secondary":"debugging","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Two deliverables are holding up AegisOspreyJobCoordinator. First, produce a consumer guide for AegisOspreyJobCoordinator. In the same workstream, correct the known stale timeout beside it. The relevant starting point is projects/aegis/config/staging.toml, which follows SQLite conventions and currently suffers from memory growth during hour-long imports. Keep public behavior and serialized data unchanged.\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":"writing","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Map AegisRavenSessionService's ownership split","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Incident timeline — INC-41129\n\n08:02 deploy AegisWillowCodecFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Turn the material above into a concise AegisWillowCodecFlow 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":"AegisSableParserCoordinator is blocking the next release because stale cursors when a page is resumed. I need two concrete outcomes from a single pass: finish AegisSableParserCoordinator's responsive empty and retry states, and capture the contract and rollback note for consumers. Use the existing PostgreSQL 17 conventions in projects/aegis/app/src/main/SyncWorker.kt; keep public behavior and serialized data unchanged. 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":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating a deadlock that appears only during shutdown in AegisRainfallDBFlow, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"The AegisFernSnapshotService surface in projects/aegis/ml/pipeline/features.py is stable now; turn its edge cases into API documentation with one successful example and one cancellation example.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Rename AegisLumenChartStore's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"projects/aegis/workers/thumbnail/consumer.ex の AegisJuniperCLIFlow で、NATS JetStream の flow に断続的な問題が起きています。 段階、互換性、metrics、rollback、ownership を提案し、コード変更の前で止めてください。\n\n制約:\n- NATS JetStream を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は AegisJuniperCLIFlow のみ","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"} +{"prompt":"Any races in AegisMicaProfileService?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"projects/aegis/src/sync/reconcile.ts has grown through several launches, and AegisTideWorkerStore now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing PostgreSQL 17 deployment\n- keep the work scoped to AegisTideWorkerStore and its direct tests\n\nThis repository spans payments, iOS, Kubernetes; use its existing conventions rather than importing a new abstraction.\n\nThe individual edits look tiny, but the semantic cleanup spans the repository and must preserve behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"AegisAmberFilterCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"For AegisKiteSchedulerCoordinator, ship the idempotent AegisKiteSchedulerCoordinator replay endpoint; once that is complete, capture the contract and rollback note for consumers. Work from projects/aegis/config/staging.toml, stay with SQLite, and keep public behavior and serialized data unchanged. Keep the two outcomes separately reviewable.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Lumen: # projects/aegis/engine/render/atlas.cpp\n[worker.aegisquartzplayerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisquartzplayerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisquartzplayerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisQuartzPlayerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41146\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/aegis/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.1,"slice":"pasted-context","lang":"en"} +{"prompt":"Summarize the AegisMapleQueueStore changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"The behavior of AegisOspreyJobService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/aegis/packages/api/openapi.yaml. 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- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current SQLite operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes 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":"Before touching projects/aegis/src/sync/reconcile.ts, 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":"Em projects/aegis/app/src/main/SyncWorker.kt, o AegisMarbleTokenStore tem um problema intermitente no fluxo de PostgreSQL 17. Finalize o layout responsivo, estados vazio e retry, foco por teclado, dark mode e reduced motion.\n\nRestrições:\n- continuar com PostgreSQL 17\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao AegisMarbleTokenStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"pt"} +{"prompt":"AegisAcornWidgetCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Any races in AegisPrismCacheService?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Queue AegisKiteSchedulerStore's expired sessions","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Maple: Ticket OPS-41140: retire the legacy replay path for AegisAmberFilterFlow\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 AegisAmberFilterFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Nimbus: Ticket OPS-41152: retire the legacy replay path for AegisPineMetricsCoordinator\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 AegisPineMetricsCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Investigate the AegisCinderAuthService hang","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-42142\n\n08:02 deploy BorealNimbusFormFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current BorealNimbusFormFlow 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":"Release engineering needs a BorealFlintTimelineService 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":"Before we approve BorealGarnetModalStore, assess whether lost focus when the drawer animation finishes 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.5,"slice":"boundary","lang":"en"} -{"prompt":"PM needs a concise migration note for BorealOpalRouterService, including the user impact, rollback trigger, and the one configuration key operators must change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"BorealBirchMigratorCoordinator: handle the lingering thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"vague-eval","lang":"en"} -{"prompt":"Set BorealSlateEditorService's port to 8081","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"core","lang":"en"} -{"prompt":"Opal: # projects/boreal/services/ledger/replay.go\n[worker.borealravensessionflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.borealravensessionflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.borealravensessionflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.BorealRavenSessionFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-42143\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/boreal/services/ledger/replay.go and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.41,"slice":"pasted-context","lang":"en"} +{"prompt":"PM needs a concise migration note for BorealOpalRouterService, 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":"BorealBirchMigratorCoordinator: handle the lingering thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Set BorealSlateEditorService's port to 8081","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Opal: # projects/boreal/services/ledger/replay.go\n[worker.borealravensessionflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.borealravensessionflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.borealravensessionflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.BorealRavenSessionFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-42143\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/boreal/services/ledger/replay.go and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} {"prompt":"Release verification found a single stale BorealIrisBatchService value; the cause, desired value, and affected assertion are already agreed. 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- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current Kafka operational envelope\n\nThe relevant code crosses computer vision, React, PostgreSQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Dedupe BorealOrbitSyncService's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Documente le contrat BorealRainfallDBStore","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"fr"} -{"prompt":"Why does BorealLumenChartService's Kafka worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Give BorealCraneWorkspaceService a loading skeleton","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"core","lang":"en"} -{"prompt":"Prism: // projects/boreal/Sources/App/SessionStore.swift\nfinal class BorealFrostPanelFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 BorealFrostPanelFlow'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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"BorealSummitProxyService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current Cloudflare Workers operational envelope\n\nThe relevant code crosses computer vision, React, PostgreSQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Quartz: // projects/boreal/crates/index/src/segment.rs\nfinal class BorealJuniperCLIFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 BorealJuniperCLIFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"BorealFlintTimelineCoordinator: sort out the rough edge","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"vague-eval","lang":"en"} -{"prompt":"Ticket OPS-42115: retire the legacy replay path for BorealBeaconStoreFlow\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 BorealBeaconStoreFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"BorealJuniperCLICoordinator needs a paired pass: produce a consumer guide for BorealJuniperCLICoordinator, plus correct the known stale timeout beside it. Use projects/boreal/pkg/cache/lease.rs as the source of truth, preserve the Cloudflare Workers contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.53,"slice":"mixed","lang":"en"} -{"prompt":"Raven: Incident timeline — INC-42136\n\n08:02 deploy BorealOspreyJobFlow 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 BorealOspreyJobFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.59,"slice":"pasted-context","lang":"en"} -{"prompt":"BorealQuartzPlayerCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"BorealMicaProfileCoordinator: something is off here","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"vague-eval","lang":"en"} -{"prompt":"Sable: Release verification found a single stale BorealAmberFilterStore value; the cause, desired value, and affected assertion are already agreed. 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- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current Kotlin coroutines operational envelope\n\nThe relevant code crosses computer vision, React, PostgreSQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"boundary","lang":"en"} -{"prompt":"Test Suite 'BorealEchoRegistryCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[BorealEchoRegistryCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/boreal/web/components/FilterDrawer.vue:144: error: -[BorealEchoRegistryCoordinatorTests 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 '-[BorealEchoRegistryCoordinatorTests 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 を維持し、根拠と判断を明確にしてください。 Use the UI evidence to complete BorealEchoRegistryCoordinator's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.76,"slice":"pasted-context","lang":"ja"} -{"prompt":"Introduce a durable deduplication key for BorealNimbusFormService events and enforce it in both the database migration and the ingestion path.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Tide: projects/boreal/engine/render/atlas.cpp now contains BorealWillowCodecStore'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.58,"slice":"core","lang":"en"} -{"prompt":"Umbra: Incident timeline — INC-42140\n\n08:02 deploy BorealGarnetModalFlow 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 BorealGarnetModalFlow 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.57,"slice":"pasted-context","lang":"en"} -{"prompt":"Give BorealMoonlitSDKStore'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.46,"slice":"boundary","lang":"en"} -{"prompt":"Test Suite 'BorealKiteSchedulerCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[BorealKiteSchedulerCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/boreal/db/migrations/20260730_events.sql:144: error: -[BorealKiteSchedulerCoordinatorTests 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 '-[BorealKiteSchedulerCoordinatorTests 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\nReconstruct the BorealKiteSchedulerCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Vela: The destination for BorealWrenExportStore is broadly agreed; the missing piece is a reversible route from projects/boreal/workers/thumbnail/consumer.ex to that target. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealWrenExportStore\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.83,"slice":"boundary","lang":"en"} -{"prompt":"Could the reasoning behind BorealDriftConsoleStore's Cloudflare Workers choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Walk through BorealFernSnapshotStore's atlas.cpp","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Compare the old and new BorealSpruceDaemonStore 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.6,"slice":"boundary","lang":"en"} -{"prompt":"Could the reasoning behind BorealCinderAuthStore's GraphQL choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"Ticket OPS-42157: retire the legacy replay path for BorealVelaDrawerCoordinator\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 BorealVelaDrawerCoordinator behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"diff --git a/projects/boreal/ml/pipeline/features.py b/projects/boreal/ml/pipeline/features.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/boreal/ml/pipeline/features.py\n+++ b/projects/boreal/ml/pipeline/features.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 BorealNovaPickerFlow'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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"A previously stable test around BorealBirchMigratorService now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Dokumentiere BorealQuartzPlayerStore kurz","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"boundary","lang":"de"} -{"prompt":"For BorealHarborIndexCoordinator, separate BorealHarborIndexCoordinator's policy from transport without behavior changes; once that is complete, capture the contract and rollback note for consumers. Work from projects/boreal/internal/auth/refresh.go, stay with Kotlin coroutines, and leave generated files and vendored code alone. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Dedupe BorealOrbitSyncService's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Documente le contrat BorealRainfallDBStore","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"fr"} +{"prompt":"Why does BorealLumenChartService's Kafka worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Give BorealCraneWorkspaceService a loading skeleton","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Prism: // projects/boreal/Sources/App/SessionStore.swift\nfinal class BorealFrostPanelFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 BorealFrostPanelFlow'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":"BorealSummitProxyService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current Cloudflare Workers operational envelope\n\nThe relevant code crosses computer vision, React, PostgreSQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Quartz: // projects/boreal/crates/index/src/segment.rs\nfinal class BorealJuniperCLIFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 BorealJuniperCLIFlow; 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":"BorealFlintTimelineCoordinator: sort out the rough edge","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Ticket OPS-42115: retire the legacy replay path for BorealBeaconStoreFlow\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 BorealBeaconStoreFlow 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":"BorealJuniperCLICoordinator needs a paired pass: produce a consumer guide for BorealJuniperCLICoordinator, plus correct the known stale timeout beside it. Use projects/boreal/pkg/cache/lease.rs as the source of truth, preserve the Cloudflare Workers contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Raven: Incident timeline — INC-42136\n\n08:02 deploy BorealOspreyJobFlow 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 BorealOspreyJobFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"BorealQuartzPlayerCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"BorealMicaProfileCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Sable: Release verification found a single stale BorealAmberFilterStore value; the cause, desired value, and affected assertion are already agreed. 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- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current Kotlin coroutines operational envelope\n\nThe relevant code crosses computer vision, React, PostgreSQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'BorealEchoRegistryCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[BorealEchoRegistryCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/boreal/web/components/FilterDrawer.vue:144: error: -[BorealEchoRegistryCoordinatorTests 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 '-[BorealEchoRegistryCoordinatorTests 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 を維持し、根拠と判断を明確にしてください。 Use the UI evidence to complete BorealEchoRegistryCoordinator'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":"Introduce a durable deduplication key for BorealNimbusFormService 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":"Tide: projects/boreal/engine/render/atlas.cpp now contains BorealWillowCodecStore'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.4,"slice":"core","lang":"en"} +{"prompt":"Umbra: Incident timeline — INC-42140\n\n08:02 deploy BorealGarnetModalFlow 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 BorealGarnetModalFlow 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":"Give BorealMoonlitSDKStore'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.5,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'BorealKiteSchedulerCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[BorealKiteSchedulerCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/boreal/db/migrations/20260730_events.sql:144: error: -[BorealKiteSchedulerCoordinatorTests 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 '-[BorealKiteSchedulerCoordinatorTests 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\nReconstruct the BorealKiteSchedulerCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Vela: The destination for BorealWrenExportStore is broadly agreed; the missing piece is a reversible route from projects/boreal/workers/thumbnail/consumer.ex to that target. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealWrenExportStore\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Could the reasoning behind BorealDriftConsoleStore's Cloudflare Workers choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Walk through BorealFernSnapshotStore's atlas.cpp","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Compare the old and new BorealSpruceDaemonStore 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.6,"slice":"core","lang":"en"} +{"prompt":"Could the reasoning behind BorealCinderAuthStore's GraphQL choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-42157: retire the legacy replay path for BorealVelaDrawerCoordinator\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 BorealVelaDrawerCoordinator 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":"diff --git a/projects/boreal/ml/pipeline/features.py b/projects/boreal/ml/pipeline/features.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/boreal/ml/pipeline/features.py\n+++ b/projects/boreal/ml/pipeline/features.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 BorealNovaPickerFlow'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":"A previously stable test around BorealBirchMigratorService now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Dokumentiere BorealQuartzPlayerStore kurz","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"de"} +{"prompt":"For BorealHarborIndexCoordinator, separate BorealHarborIndexCoordinator's policy from transport without behavior changes; once that is complete, capture the contract and rollback note for consumers. Work from projects/boreal/internal/auth/refresh.go, stay with Kotlin coroutines, and leave generated files and vendored code alone. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Is BorealBeaconStoreService safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"On compact widths, BorealBasilRunnerFlow'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.44,"slice":"boundary","lang":"en"} -{"prompt":"Two asks around BorealCedarPolicyCoordinator: (1) find the unknown cause of two validators with subtly different error strings; (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":"debugging","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"BorealSableParserService 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":"projects/boreal/lib/codec/frame.cc has grown through several launches, and BorealIrisBatchStore now mixes policy, transport, persistence, and metrics in one place. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- leave generated files and vendored code alone\n- stay compatible with the existing Kafka deployment\n- keep the work scoped to BorealIrisBatchStore and its direct tests\n\nSeveral teams work in this computer vision, React, PostgreSQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.74,"slice":"boundary","lang":"en"} -{"prompt":"BorealSpruceDaemonCoordinator: could this be clearer","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"vague-eval","lang":"en"} -{"prompt":"BorealSableParserCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","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_42122'\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_42122'::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 BorealFernSnapshotFlow 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.92,"slice":"pasted-context","lang":"en"} -{"prompt":"BorealNimbusFormCoordinator: smooth out this interaction","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"BorealAcornWidgetCoordinator: correct, then assess","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.27,"slice":"mixed","lang":"en"} -{"prompt":"BorealSlateEditorCoordinator: sequence, then polish","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.74,"slice":"mixed","lang":"en"} -{"prompt":"BorealPrismCacheService'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.14,"slice":"core","lang":"en"} -{"prompt":"Move BorealSummitProxyFlow'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.63,"slice":"boundary","lang":"en"} -{"prompt":"Before touching projects/boreal/db/migrations/20260730_events.sql, 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.65,"slice":"core","lang":"en"} -{"prompt":"The BorealDeltaCanvasStore empty state in projects/boreal/config/staging.toml needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"boundary","lang":"en"} -{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current BorealEmberRelayService design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealEmberRelayService\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"On compact widths, BorealCinderAuthService'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.46,"slice":"core","lang":"en"} -{"prompt":"BorealRainfallDBCoordinator needs a paired pass: separate BorealRainfallDBCoordinator's policy from transport without behavior changes, plus give the existing implementation a read-only safety pass. Use projects/boreal/ui/settings/PrivacyPane.tsx as the source of truth, preserve the Kafka contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current BorealDriftConsoleService design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealDriftConsoleService\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"This should remain a deliberately small patch: BorealMarbleTokenService has one known configuration mistake in projects/boreal/infra/modules/edge/main.tf, not an open-ended failure investigation. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- leave generated files and vendored code alone\n- stay compatible with the existing Kotlin coroutines deployment\n- keep the work scoped to BorealMarbleTokenService and its direct tests\n\nSeveral teams work in this computer vision, React, PostgreSQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-42128\n\n08:02 deploy BorealHarborIndexFlow 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 BorealHarborIndexFlow 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.65,"slice":"pasted-context","lang":"en"} -{"prompt":"diff --git a/projects/boreal/cmd/exporter/main.py b/projects/boreal/cmd/exporter/main.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/boreal/cmd/exporter/main.py\n+++ b/projects/boreal/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\nRestructure BorealPineMetricsFlow 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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"In projects/boreal/app/src/main/SyncWorker.kt hat BorealAtlasSearchService ein sporadisches Problem im GraphQL-Ablauf. Vervollständige Responsive Layout, Empty- und Retry-State, Tastaturfokus, Dark Mode und Reduced Motion.\n\nRandbedingungen:\n- GraphQL weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf BorealAtlasSearchService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um BorealAtlasSearchService mit GraphQL kompatibel.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"de"} -{"prompt":"Split BorealAsterWebhookStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"The name pendingAck means two different things across BorealMarbleTokenFlow's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"# projects/boreal/packages/api/openapi.yaml\n[worker.borealquartzplayerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.borealquartzplayerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.borealquartzplayerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.BorealQuartzPlayerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-42119\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/boreal/packages/api/openapi.yaml and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.43,"slice":"pasted-context","lang":"en"} -{"prompt":"Dedupe BorealFrostPanelStore's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"Stream BorealFernSnapshotService's audit events","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Does BorealOspreyJobStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists? I want your judgment and walkthrough, not new documentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"PM needs a concise migration note for BorealFlintTimelineStore, including the user impact, rollback trigger, and the one configuration key operators must change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"boundary","lang":"en"} -{"prompt":"BorealOrbitSyncCoordinator is blocking the next release because cancellation being swallowed at the repository boundary. I need two concrete outcomes from a single pass: assess ownership and failure handling in projects/boreal/crates/index/src/segment.rs, and capture the contract and rollback note for consumers. Use the existing Cloudflare Workers conventions in projects/boreal/crates/index/src/segment.rs; 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":"review","secondary":"writing","mixed":true,"difficulty":0.86,"slice":"mixed","lang":"en"} -{"prompt":"Ticket OPS-42114: retire the legacy replay path for BorealOrbitSyncFlow\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 BorealOrbitSyncFlow 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.84,"slice":"pasted-context","lang":"en"} -{"prompt":"BorealOspreyJobCoordinator: deal with the small issue","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"vague-eval","lang":"en"} -{"prompt":"Compare the old and new BorealVelaDrawerStore adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Remove BorealFrostPanelService's stray comma","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"core","lang":"en"} -{"prompt":"BorealGarnetModalCoordinator: check the suspicious part","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"vague-eval","lang":"en"} -{"prompt":"Willow: The BorealMicaProfileStore surface in projects/boreal/ml/pipeline/features.py is stable now; turn its edge cases into API documentation with one successful example and one cancellation example.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"boundary","lang":"en"} -{"prompt":"Xylem: projects/boreal/web/components/FilterDrawer.vue 里的 BorealRavenSessionStore 最近在 Kotlin coroutines 流程中出现间歇性问题。 请完成 responsive layout、空状态、retry、键盘焦点、dark mode 和 reduced motion。\n\n约束：\n- 继续使用 Kotlin coroutines\n- 保持兼容性和取消语义\n- 改动只限于 BorealRavenSessionStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"zh"} -{"prompt":"Two deliverables are holding up BorealBeaconStoreCoordinator. First, finish BorealBeaconStoreCoordinator's responsive empty and retry states. In the same workstream, correct the known stale timeout beside it. The relevant starting point is projects/boreal/cmd/exporter/main.py, which follows Spring Boot 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":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Yarrow: Two asks around BorealCraneWorkspaceCoordinator: (1) change BorealCraneWorkspaceCoordinator's known staging timeout from 15 to 30 seconds; (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":"quickFix","secondary":"writing","mixed":true,"difficulty":0.24,"slice":"mixed","lang":"en"} -{"prompt":"Zephyr: Ticket OPS-42151: retire the legacy replay path for BorealEmberRelayCoordinator\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 BorealEmberRelayCoordinator behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"Where did BorealHarborIndexService's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"thread 'tokio-runtime-worker' panicked at projects/boreal/infra/modules/edge/main.tf:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: borealbirchmigratorflow::scheduler::LeaseTask::flush\n at ./projects/boreal/infra/modules/edge/main.tf:217:18\n 4: borealbirchmigratorflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nFind the source of this BorealBirchMigratorFlow 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.95,"slice":"pasted-context","lang":"en"} -{"prompt":"Test Suite 'BorealSpruceDaemonFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[BorealSpruceDaemonFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/boreal/config/staging.toml:144: error: -[BorealSpruceDaemonFlowTests 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 '-[BorealSpruceDaemonFlowTests 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\nDetermine why BorealSpruceDaemonFlow 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.96,"slice":"pasted-context","lang":"en"} -{"prompt":"Before touching projects/boreal/engine/render/atlas.cpp, 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.67,"slice":"boundary","lang":"en"} -{"prompt":"# CI job 42147: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: Kafka\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] BorealLumenChartFlowIntegration.replays_after_timeout ... ok\n[test] BorealLumenChartFlowIntegration.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 \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\nWire BorealLumenChartFlow'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.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Checkout: projects/boreal/src/sync/reconcile.ts now contains BorealKiteSchedulerFlow'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.55,"slice":"boundary","lang":"en"} -{"prompt":"Test Suite 'BorealWrenExportFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[BorealWrenExportFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/boreal/ui/settings/PrivacyPane.tsx:144: error: -[BorealWrenExportFlowTests 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 '-[BorealWrenExportFlowTests 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 BorealWrenExportFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"pasted-context","lang":"en"} -{"prompt":"Exporter: # projects/boreal/ui/settings/PrivacyPane.tsx\n[worker.borealprismcacheflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.borealprismcacheflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.borealprismcacheflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.BorealPrismCacheFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-42137\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. The intended correction is already known: change only the stale 15-second setting to 30 seconds in projects/boreal/ui/settings/PrivacyPane.tsx and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.38,"slice":"pasted-context","lang":"pt"} -{"prompt":"Scheduler: // projects/boreal/Sources/CLI/Commands/Doctor.swift\nfinal class BorealAsterWebhookFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 BorealAsterWebhookFlow 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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Incident timeline — INC-42112\n\n08:02 deploy BorealIrisBatchFlow 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 BorealIrisBatchFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.62,"slice":"pasted-context","lang":"en"} -{"prompt":"Ticket OPS-42129: retire the legacy replay path for BorealCopperBridgeFlow\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À partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Turn the artifact into a reversible BorealCopperBridgeFlow rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"fr"} -{"prompt":"Outline a safer BorealCraneWorkspaceStore cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"UI ticket DES-42110: finish the compact BorealMosaicGridFlow filter experience\n\nRoute: /catalog/search\nSource: projects/boreal/Sources/CLI/Commands/Doctor.swift\nFramework: Spring Boot\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 BorealMosaicGridFlow 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.68,"slice":"pasted-context","lang":"en"} -{"prompt":"diff --git a/projects/boreal/web/components/FilterDrawer.vue b/projects/boreal/web/components/FilterDrawer.vue\nindex 62d71aa..90f3c1e 100644\n--- a/projects/boreal/web/components/FilterDrawer.vue\n+++ b/projects/boreal/web/components/FilterDrawer.vue\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit BorealTideWorkerFlow 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.84,"slice":"pasted-context","lang":"en"} -{"prompt":"BorealCinderAuthCoordinator: clean up that old path","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"vague-eval","lang":"en"} -{"prompt":"How should BorealLedgerGateStore be decomposed?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Em projects/boreal/cmd/exporter/main.py, o BorealNovaPickerStore tem um problema intermitente no fluxo de Spring Boot. Proponha fases, compatibilidade, métricas, rollback e ownership; pare antes de alterar código.\n\nRestrições:\n- continuar com Spring Boot\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao BorealNovaPickerStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"pt"} -{"prompt":"Dashboard: Incident timeline — INC-42146\n\n08:02 deploy BorealCinderAuthFlow 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 BorealCinderAuthFlow 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.59,"slice":"pasted-context","lang":"en"} -{"prompt":"A previously stable test around BorealOpalRouterStore now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","lang":"en"} -{"prompt":"Worker: The BorealWillowCodecFlow 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.14,"slice":"boundary","lang":"en"} -{"prompt":"PM is preparing the BorealMosaicGridService rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealMosaicGridService\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.49,"slice":"core","lang":"en"} -{"prompt":"BorealMapleQueueStore returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/boreal/ml/pipeline/features.py and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"BorealAsterWebhookCoordinator needs a paired pass: change BorealAsterWebhookCoordinator's known staging timeout from 15 to 30 seconds, plus give the existing implementation a read-only safety pass. Use projects/boreal/Sources/App/SessionStore.swift as the source of truth, preserve the Spring Boot contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.19,"slice":"mixed","lang":"en"} -{"prompt":"BorealCopperBridgeService flakes under UTC","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"projects/boreal/services/ledger/replay.go の BorealRavenSessionService で、Kotlin coroutines の flow に断続的な問題が起きています。 responsive layout、empty/retry state、keyboard focus、dark mode、reduced motion を仕上げてください。\n\n制約:\n- Kotlin coroutines を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は BorealRavenSessionService のみ","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"ja"} -{"prompt":"Please resist widening this one: BorealMarbleTokenStore works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealMarbleTokenStore\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"boundary","lang":"en"} -{"prompt":"Simulator: // projects/boreal/workers/thumbnail/consumer.ex\nfinal class BorealRainfallDBFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 BorealRainfallDBFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"UI ticket DES-42134: finish the compact BorealOpalRouterFlow filter experience\n\nRoute: /catalog/search\nSource: projects/boreal/pkg/cache/lease.rs\nFramework: Cloudflare Workers\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 BorealOpalRouterFlow 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.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Walk through BorealJuniperCLIService's segment.rs","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"BorealPrismCacheCoordinator: the docs need something","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"vague-eval","lang":"en"} -{"prompt":"BorealDeltaCanvasCoordinator: ship a sensible version","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"Summarize the BorealWrenExportService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"BorealMoonlitSDKCoordinator: make the api less awkward","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"vague-eval","lang":"en"} -{"prompt":"diff --git a/projects/boreal/packages/api/openapi.yaml b/projects/boreal/packages/api/openapi.yaml\nindex 62d71aa..90f3c1e 100644\n--- a/projects/boreal/packages/api/openapi.yaml\n+++ b/projects/boreal/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 BorealDeltaCanvasFlow 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.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Match BorealPineMetricsService's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-42158\n\n08:02 deploy BorealMarbleTokenCoordinator 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 BorealMarbleTokenCoordinator 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.65,"slice":"pasted-context","lang":"en"} -{"prompt":"Release engineering needs a BorealDriftConsoleFlow changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"boundary","lang":"en"} -{"prompt":"Why is BorealLedgerGateService stalling?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"What sequence would let BorealDeltaCanvasService adopt Cloudflare Workers 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.72,"slice":"core","lang":"en"} -{"prompt":"Enforce BorealTideWorkerStore's idempotency key","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"Ownership of BorealCoralUploadStore is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current GraphQL operational envelope\n\nThe relevant code crosses computer vision, React, PostgreSQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.81,"slice":"boundary","lang":"en"} -{"prompt":"Documente o contrato de BorealRainfallDBService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"pt"} -{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current BorealAmberFilterService design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealAmberFilterService\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Extract BorealCedarPolicyService's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Does BorealPineMetricsStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"projects/boreal/cmd/exporter/main.py has grown through several launches, and BorealBeaconStoreStore now mixes policy, transport, persistence, and metrics in one place. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- leave generated files and vendored code alone\n- stay compatible with the existing Spring Boot deployment\n- keep the work scoped to BorealBeaconStoreStore and its direct tests\n\nSeveral teams work in this computer vision, React, PostgreSQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.69,"slice":"boundary","lang":"en"} -{"prompt":"Ticket OPS-42155: retire the legacy replay path for BorealMapleQueueCoordinator\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 BorealMapleQueueCoordinator migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Runbook: diff --git a/projects/boreal/web/components/FilterDrawer.vue b/projects/boreal/web/components/FilterDrawer.vue\nindex 62d71aa..90f3c1e 100644\n--- a/projects/boreal/web/components/FilterDrawer.vue\n+++ b/projects/boreal/web/components/FilterDrawer.vue\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Restructure BorealAmberFilterFlow 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.84,"slice":"pasted-context","lang":"es"} -{"prompt":"BorealSableParserStore's staging timeout is already known to be wrong: change the single projects/boreal/infra/modules/edge/main.tf value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"boundary","lang":"en"} -{"prompt":"Release verification found a single stale BorealKiteSchedulerService value; the cause, desired value, and affected assertion are already agreed. 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- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current GraphQL operational envelope\n\nThe relevant code crosses computer vision, React, PostgreSQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.28,"slice":"core","lang":"en"} -{"prompt":"Trace: Ticket OPS-42150: retire the legacy replay path for BorealBasilRunnerCoordinator\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 BorealBasilRunnerCoordinator 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.74,"slice":"pasted-context","lang":"en"} -{"prompt":"What does BorealJuniperCLIStore own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Outline a safer BorealAcornWidgetService cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Profiler: Incident timeline — INC-42144\n\n08:02 deploy BorealFlintTimelineFlow 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 BorealFlintTimelineFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.67,"slice":"pasted-context","lang":"en"} -{"prompt":"Console: # projects/boreal/internal/auth/refresh.go\n[worker.borealacornwidgetflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.borealacornwidgetflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.borealacornwidgetflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.BorealAcornWidgetFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-42118\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/boreal/internal/auth/refresh.go. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.41,"slice":"pasted-context","lang":"en"} -{"prompt":"Workspace: projects/boreal/apps/console/routes/usage.svelte の BorealEmberRelayFlow で、GraphQL の flow に断続的な問題が起きています。 consumer 向けに contract、error、retry、コピー可能な例を含む文書を書き、handler は変更しないでください。\n\n制約:\n- GraphQL を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は BorealEmberRelayFlow のみ","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"ja"} -{"prompt":"Fresh release brief for BorealMosaicGridCoordinator:\n- primary outcome: finish BorealMosaicGridCoordinator's responsive empty and retry states\n- companion outcome: give the existing implementation a read-only safety pass\n- repository entry point: projects/boreal/Sources/App/SessionStore.swift\n- platform constraint: Spring Boot\n- known complication: two validators with subtly different error strings\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":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"PM is preparing the BorealVelaDrawerService rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealVelaDrawerService\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Repository: Release verification found a single stale BorealMosaicGridStore value; the cause, desired value, and affected assertion are already agreed. 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- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current Spring Boot operational envelope\n\nThe relevant code crosses computer vision, React, PostgreSQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.25,"slice":"boundary","lang":"en"} +{"prompt":"On compact widths, BorealBasilRunnerFlow'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":"Two asks around BorealCedarPolicyCoordinator: (1) find the unknown cause of two validators with subtly different error strings; (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":"debugging","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"BorealSableParserService 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":"projects/boreal/lib/codec/frame.cc has grown through several launches, and BorealIrisBatchStore now mixes policy, transport, persistence, and metrics in one place. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- leave generated files and vendored code alone\n- stay compatible with the existing Kafka deployment\n- keep the work scoped to BorealIrisBatchStore and its direct tests\n\nSeveral teams work in this computer vision, React, PostgreSQL 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":"BorealSpruceDaemonCoordinator: could this be clearer","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"BorealSableParserCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","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_42122'\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_42122'::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 BorealFernSnapshotFlow 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":"BorealNimbusFormCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"BorealAcornWidgetCoordinator: correct, then assess","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"BorealSlateEditorCoordinator: sequence, then polish","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"BorealPrismCacheService's metric is misspelled as succesful_total in one declaration. Correct that literal and its exact test expectation, without renaming anything else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Move BorealSummitProxyFlow'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.5,"slice":"core","lang":"en"} +{"prompt":"Before touching projects/boreal/db/migrations/20260730_events.sql, 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":"The BorealDeltaCanvasStore empty state in projects/boreal/config/staging.toml needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current BorealEmberRelayService design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealEmberRelayService\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"On compact widths, BorealCinderAuthService'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":"BorealRainfallDBCoordinator needs a paired pass: separate BorealRainfallDBCoordinator's policy from transport without behavior changes, plus give the existing implementation a read-only safety pass. Use projects/boreal/ui/settings/PrivacyPane.tsx as the source of truth, preserve the Kafka contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current BorealDriftConsoleService design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealDriftConsoleService\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"This should remain a deliberately small patch: BorealMarbleTokenService has one known configuration mistake in projects/boreal/infra/modules/edge/main.tf, not an open-ended failure investigation. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- leave generated files and vendored code alone\n- stay compatible with the existing Kotlin coroutines deployment\n- keep the work scoped to BorealMarbleTokenService and its direct tests\n\nSeveral teams work in this computer vision, React, PostgreSQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-42128\n\n08:02 deploy BorealHarborIndexFlow 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 BorealHarborIndexFlow 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":"diff --git a/projects/boreal/cmd/exporter/main.py b/projects/boreal/cmd/exporter/main.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/boreal/cmd/exporter/main.py\n+++ b/projects/boreal/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\nRestructure BorealPineMetricsFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"In projects/boreal/app/src/main/SyncWorker.kt hat BorealAtlasSearchService ein sporadisches Problem im GraphQL-Ablauf. Vervollständige Responsive Layout, Empty- und Retry-State, Tastaturfokus, Dark Mode und Reduced Motion.\n\nRandbedingungen:\n- GraphQL weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf BorealAtlasSearchService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um BorealAtlasSearchService mit GraphQL kompatibel.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} +{"prompt":"Split BorealAsterWebhookStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"The name pendingAck means two different things across BorealMarbleTokenFlow's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"# projects/boreal/packages/api/openapi.yaml\n[worker.borealquartzplayerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.borealquartzplayerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.borealquartzplayerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.BorealQuartzPlayerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-42119\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/boreal/packages/api/openapi.yaml and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Dedupe BorealFrostPanelStore's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Stream BorealFernSnapshotService's audit events","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Does BorealOspreyJobStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists? I want your judgment and walkthrough, not new documentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"PM needs a concise migration note for BorealFlintTimelineStore, 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":"BorealOrbitSyncCoordinator is blocking the next release because cancellation being swallowed at the repository boundary. I need two concrete outcomes from a single pass: assess ownership and failure handling in projects/boreal/crates/index/src/segment.rs, and capture the contract and rollback note for consumers. Use the existing Cloudflare Workers conventions in projects/boreal/crates/index/src/segment.rs; 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":"review","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Ticket OPS-42114: retire the legacy replay path for BorealOrbitSyncFlow\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 BorealOrbitSyncFlow 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":"BorealOspreyJobCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Compare the old and new BorealVelaDrawerStore 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":"Remove BorealFrostPanelService's stray comma","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"BorealGarnetModalCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Willow: The BorealMicaProfileStore surface in projects/boreal/ml/pipeline/features.py is stable now; turn its edge cases into API documentation with one successful example and one cancellation example.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Xylem: projects/boreal/web/components/FilterDrawer.vue 里的 BorealRavenSessionStore 最近在 Kotlin coroutines 流程中出现间歇性问题。 请完成 responsive layout、空状态、retry、键盘焦点、dark mode 和 reduced motion。\n\n约束：\n- 继续使用 Kotlin coroutines\n- 保持兼容性和取消语义\n- 改动只限于 BorealRavenSessionStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"Two deliverables are holding up BorealBeaconStoreCoordinator. First, finish BorealBeaconStoreCoordinator's responsive empty and retry states. In the same workstream, correct the known stale timeout beside it. The relevant starting point is projects/boreal/cmd/exporter/main.py, which follows Spring Boot 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":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Yarrow: Two asks around BorealCraneWorkspaceCoordinator: (1) change BorealCraneWorkspaceCoordinator's known staging timeout from 15 to 30 seconds; (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":"quickFix","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Zephyr: Ticket OPS-42151: retire the legacy replay path for BorealEmberRelayCoordinator\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 BorealEmberRelayCoordinator 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":"Where did BorealHarborIndexService's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"thread 'tokio-runtime-worker' panicked at projects/boreal/infra/modules/edge/main.tf:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: borealbirchmigratorflow::scheduler::LeaseTask::flush\n at ./projects/boreal/infra/modules/edge/main.tf:217:18\n 4: borealbirchmigratorflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nFind the source of this BorealBirchMigratorFlow 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":"Test Suite 'BorealSpruceDaemonFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[BorealSpruceDaemonFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/boreal/config/staging.toml:144: error: -[BorealSpruceDaemonFlowTests 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 '-[BorealSpruceDaemonFlowTests 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\nDetermine why BorealSpruceDaemonFlow 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":"Before touching projects/boreal/engine/render/atlas.cpp, 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":"# CI job 42147: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: Kafka\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] BorealLumenChartFlowIntegration.replays_after_timeout ... ok\n[test] BorealLumenChartFlowIntegration.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 \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\nWire BorealLumenChartFlow'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":"Checkout: projects/boreal/src/sync/reconcile.ts now contains BorealKiteSchedulerFlow'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.4,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'BorealWrenExportFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[BorealWrenExportFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/boreal/ui/settings/PrivacyPane.tsx:144: error: -[BorealWrenExportFlowTests 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 '-[BorealWrenExportFlowTests 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 BorealWrenExportFlow'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":"Exporter: # projects/boreal/ui/settings/PrivacyPane.tsx\n[worker.borealprismcacheflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.borealprismcacheflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.borealprismcacheflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.BorealPrismCacheFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-42137\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. The intended correction is already known: change only the stale 15-second setting to 30 seconds in projects/boreal/ui/settings/PrivacyPane.tsx and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Scheduler: // projects/boreal/Sources/CLI/Commands/Doctor.swift\nfinal class BorealAsterWebhookFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 BorealAsterWebhookFlow 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":"Incident timeline — INC-42112\n\n08:02 deploy BorealIrisBatchFlow 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 BorealIrisBatchFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Ticket OPS-42129: retire the legacy replay path for BorealCopperBridgeFlow\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À partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Turn the artifact into a reversible BorealCopperBridgeFlow 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":"Outline a safer BorealCraneWorkspaceStore cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-42110: finish the compact BorealMosaicGridFlow filter experience\n\nRoute: /catalog/search\nSource: projects/boreal/Sources/CLI/Commands/Doctor.swift\nFramework: Spring Boot\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 BorealMosaicGridFlow 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":"diff --git a/projects/boreal/web/components/FilterDrawer.vue b/projects/boreal/web/components/FilterDrawer.vue\nindex 62d71aa..90f3c1e 100644\n--- a/projects/boreal/web/components/FilterDrawer.vue\n+++ b/projects/boreal/web/components/FilterDrawer.vue\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit BorealTideWorkerFlow 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":"BorealCinderAuthCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"How should BorealLedgerGateStore be decomposed?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Em projects/boreal/cmd/exporter/main.py, o BorealNovaPickerStore tem um problema intermitente no fluxo de Spring Boot. Proponha fases, compatibilidade, métricas, rollback e ownership; pare antes de alterar código.\n\nRestrições:\n- continuar com Spring Boot\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao BorealNovaPickerStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"pt"} +{"prompt":"Dashboard: Incident timeline — INC-42146\n\n08:02 deploy BorealCinderAuthFlow 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 BorealCinderAuthFlow 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":"A previously stable test around BorealOpalRouterStore now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Worker: The BorealWillowCodecFlow 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":"PM is preparing the BorealMosaicGridService rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealMosaicGridService\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"BorealMapleQueueStore returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/boreal/ml/pipeline/features.py and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"BorealAsterWebhookCoordinator needs a paired pass: change BorealAsterWebhookCoordinator's known staging timeout from 15 to 30 seconds, plus give the existing implementation a read-only safety pass. Use projects/boreal/Sources/App/SessionStore.swift as the source of truth, preserve the Spring Boot contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"BorealCopperBridgeService flakes under UTC","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"projects/boreal/services/ledger/replay.go の BorealRavenSessionService で、Kotlin coroutines の flow に断続的な問題が起きています。 responsive layout、empty/retry state、keyboard focus、dark mode、reduced motion を仕上げてください。\n\n制約:\n- Kotlin coroutines を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は BorealRavenSessionService のみ","purpose":"frontendImpl","secondary":"debugging","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"ja"} +{"prompt":"Please resist widening this one: BorealMarbleTokenStore works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealMarbleTokenStore\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Simulator: // projects/boreal/workers/thumbnail/consumer.ex\nfinal class BorealRainfallDBFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 BorealRainfallDBFlow; 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":"UI ticket DES-42134: finish the compact BorealOpalRouterFlow filter experience\n\nRoute: /catalog/search\nSource: projects/boreal/pkg/cache/lease.rs\nFramework: Cloudflare Workers\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 BorealOpalRouterFlow 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":"Walk through BorealJuniperCLIService's segment.rs","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"BorealPrismCacheCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"BorealDeltaCanvasCoordinator: ship a sensible version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Summarize the BorealWrenExportService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"BorealMoonlitSDKCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"diff --git a/projects/boreal/packages/api/openapi.yaml b/projects/boreal/packages/api/openapi.yaml\nindex 62d71aa..90f3c1e 100644\n--- a/projects/boreal/packages/api/openapi.yaml\n+++ b/projects/boreal/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 BorealDeltaCanvasFlow 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":"Match BorealPineMetricsService's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Incident timeline — INC-42158\n\n08:02 deploy BorealMarbleTokenCoordinator 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 BorealMarbleTokenCoordinator 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":"Release engineering needs a BorealDriftConsoleFlow 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":"Why is BorealLedgerGateService stalling?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"What sequence would let BorealDeltaCanvasService adopt Cloudflare Workers 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.8,"slice":"core","lang":"en"} +{"prompt":"Enforce BorealTideWorkerStore's idempotency key","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Ownership of BorealCoralUploadStore is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current GraphQL operational envelope\n\nThe relevant code crosses computer vision, React, PostgreSQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Documente o contrato de BorealRainfallDBService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"pt"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current BorealAmberFilterService design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealAmberFilterService\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Extract BorealCedarPolicyService's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Does BorealPineMetricsStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"projects/boreal/cmd/exporter/main.py has grown through several launches, and BorealBeaconStoreStore now mixes policy, transport, persistence, and metrics in one place. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- leave generated files and vendored code alone\n- stay compatible with the existing Spring Boot deployment\n- keep the work scoped to BorealBeaconStoreStore and its direct tests\n\nSeveral teams work in this computer vision, React, PostgreSQL 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":"Ticket OPS-42155: retire the legacy replay path for BorealMapleQueueCoordinator\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 BorealMapleQueueCoordinator 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":"Runbook: diff --git a/projects/boreal/web/components/FilterDrawer.vue b/projects/boreal/web/components/FilterDrawer.vue\nindex 62d71aa..90f3c1e 100644\n--- a/projects/boreal/web/components/FilterDrawer.vue\n+++ b/projects/boreal/web/components/FilterDrawer.vue\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Restructure BorealAmberFilterFlow 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":"BorealSableParserStore's staging timeout is already known to be wrong: change the single projects/boreal/infra/modules/edge/main.tf value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Release verification found a single stale BorealKiteSchedulerService value; the cause, desired value, and affected assertion are already agreed. 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- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current GraphQL operational envelope\n\nThe relevant code crosses computer vision, React, PostgreSQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Trace: Ticket OPS-42150: retire the legacy replay path for BorealBasilRunnerCoordinator\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 BorealBasilRunnerCoordinator 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"What does BorealJuniperCLIStore own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Outline a safer BorealAcornWidgetService cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Profiler: Incident timeline — INC-42144\n\n08:02 deploy BorealFlintTimelineFlow 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 BorealFlintTimelineFlow, 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":"Console: # projects/boreal/internal/auth/refresh.go\n[worker.borealacornwidgetflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.borealacornwidgetflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.borealacornwidgetflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.BorealAcornWidgetFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-42118\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/boreal/internal/auth/refresh.go. 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":"Workspace: projects/boreal/apps/console/routes/usage.svelte の BorealEmberRelayFlow で、GraphQL の flow に断続的な問題が起きています。 consumer 向けに contract、error、retry、コピー可能な例を含む文書を書き、handler は変更しないでください。\n\n制約:\n- GraphQL を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は BorealEmberRelayFlow のみ","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"ja"} +{"prompt":"Fresh release brief for BorealMosaicGridCoordinator:\n- primary outcome: finish BorealMosaicGridCoordinator's responsive empty and retry states\n- companion outcome: give the existing implementation a read-only safety pass\n- repository entry point: projects/boreal/Sources/App/SessionStore.swift\n- platform constraint: Spring Boot\n- known complication: two validators with subtly different error strings\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":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"PM is preparing the BorealVelaDrawerService rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealVelaDrawerService\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Repository: Release verification found a single stale BorealMosaicGridStore value; the cause, desired value, and affected assertion are already agreed. 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- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current Spring Boot operational envelope\n\nThe relevant code crosses computer vision, React, PostgreSQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Read projects/boreal/Sources/App/SessionStore.swift and tell me whether BorealGarnetModalService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Assess the BorealAcornWidgetStore diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"BorealLumenChartStore returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/boreal/ui/settings/PrivacyPane.tsx and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"boundary","lang":"en"} -{"prompt":"Give BorealEchoRegistryFlow'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.52,"slice":"boundary","lang":"en"} -{"prompt":"Split projects/boreal/app/src/main/SyncWorker.kt by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Ownership of BorealBasilRunnerService is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current Spring Boot operational envelope\n\nThe relevant code crosses computer vision, React, PostgreSQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"BorealFrostPanelCoordinator: sequence, then restructure","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Incident timeline — INC-42154\n\n08:02 deploy BorealDriftConsoleCoordinator 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 BorealDriftConsoleCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.67,"slice":"pasted-context","lang":"en"} -{"prompt":"Documente le contrat BorealQuartzPlayerService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"fr"} -{"prompt":"How does BorealEchoRegistryStore propagate cancellation through the Kotlin coroutines boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"$ pnpm test --filter BorealAtlasSearchFlow\n RUN v3.2.4 /workspace/apps/console\n × BorealAtlasSearchFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=42111 phase=resume storedCursor=seg-0183\n session=42111 phase=fetch requestCursor=seg-0183 pageSize=200\n session=42111 phase=commit receivedCursor=seg-0184 itemCount=0\n session=42111 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nReconstruct the BorealAtlasSearchFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Pipeline: What is the safest way to split projects/boreal/apps/console/routes/usage.svelte into independently owned modules while BorealMoonlitSDKService's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Add a bounded BorealBasilRunnerStore export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Two deliverables are holding up BorealIrisBatchCoordinator. First, separate BorealIrisBatchCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/boreal/lib/codec/frame.cc, which follows Kafka conventions and currently suffers from a misleading timeout name used in five packages. 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":"refactor","secondary":"review","mixed":true,"difficulty":0.84,"slice":"mixed","lang":"en"} -{"prompt":"For BorealPineMetricsCoordinator, finish BorealPineMetricsCoordinator's responsive empty and retry states; once that is complete, give the existing implementation a read-only safety pass. Work from projects/boreal/ml/pipeline/features.py, stay with Spring Boot, and leave generated files and vendored code alone. Keep the two outcomes separately reviewable.","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.54,"slice":"mixed","lang":"en"} -{"prompt":"En projects/boreal/apps/console/routes/usage.svelte, BorealAtlasSearchStore tiene un problema intermitente en el flujo de GraphQL. Separa responsabilidades y elimina duplicación, conservando API, wire values, orden y comportamiento observable.\n\nRestricciones:\n- seguir con GraphQL\n- conservar compatibilidad y cancelación\n- limitar el cambio a BorealAtlasSearchStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con GraphQL alrededor de BorealAtlasSearchStore.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"es"} -{"prompt":"BorealLumenChartCoordinator: give it a nicer flow","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"vague-eval","lang":"en"} -{"prompt":"Two asks around BorealCopperBridgeCoordinator: (1) ship the idempotent BorealCopperBridgeCoordinator replay endpoint; (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":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.77,"slice":"mixed","lang":"en"} -{"prompt":"Clarify BorealSlateEditorStore's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"UI ticket DES-42116: finish the compact BorealCoralUploadFlow filter experience\n\nRoute: /catalog/search\nSource: projects/boreal/db/migrations/20260730_events.sql\nFramework: GraphQL\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 BorealCoralUploadFlow 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.7,"slice":"pasted-context","lang":"en"} -{"prompt":"BorealTideWorkerCoordinator needs a paired pass: assess ownership and failure handling in projects/boreal/services/ledger/replay.go, plus capture the contract and rollback note for consumers. Use projects/boreal/services/ledger/replay.go as the source of truth, preserve the Kotlin coroutines contract, and avoid unrelated cleanup.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Clarify BorealCloudReconcilerService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"thread 'tokio-runtime-worker' panicked at projects/boreal/apps/console/routes/usage.svelte:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: borealmoonlitsdkflow::scheduler::LeaseTask::flush\n at ./projects/boreal/apps/console/routes/usage.svelte:217:18\n 4: borealmoonlitsdkflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nReconstruct the BorealMoonlitSDKFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Ticket OPS-42159: retire the legacy replay path for BorealSummitProxyCoordinator\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 BorealSummitProxyCoordinator 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.84,"slice":"pasted-context","lang":"en"} -{"prompt":"BorealOpalRouterCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"BorealSpruceDaemonService'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.19,"slice":"core","lang":"en"} -{"prompt":"Fresh release brief for BorealAmberFilterCoordinator:\n- primary outcome: separate BorealAmberFilterCoordinator's policy from transport without behavior changes\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/boreal/services/ledger/replay.go\n- platform constraint: Kotlin coroutines\n- known complication: stale cursors when a page is resumed\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":"refactor","secondary":"writing","mixed":true,"difficulty":0.86,"slice":"mixed","lang":"en"} -{"prompt":"Compare BorealHarborIndexStore's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"The BorealOspreyJobService 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.12,"slice":"core","lang":"en"} -{"prompt":"BorealNovaPickerCoordinator: polish the last piece","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"vague-eval","lang":"en"} -{"prompt":"For BorealCloudReconcilerCoordinator, finish BorealCloudReconcilerCoordinator's responsive empty and retry states; once that is complete, give the existing implementation a read-only safety pass. Work from projects/boreal/apps/console/routes/usage.svelte, stay with GraphQL, and leave generated files and vendored code alone. Keep the two outcomes separately reviewable.","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.56,"slice":"mixed","lang":"en"} -{"prompt":"The first BorealPrismCacheStore request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"boundary","lang":"en"} -{"prompt":"BorealWrenExportCoordinator: ship, then document","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"diff --git a/projects/boreal/apps/console/routes/usage.svelte b/projects/boreal/apps/console/routes/usage.svelte\nindex 62d71aa..90f3c1e 100644\n--- a/projects/boreal/apps/console/routes/usage.svelte\n+++ b/projects/boreal/apps/console/routes/usage.svelte\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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Split BorealSlateEditorFlow 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.79,"slice":"pasted-context","lang":"de"} -{"prompt":"Gateway: Ticket OPS-42131: retire the legacy replay path for BorealCloudReconcilerFlow\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 BorealCloudReconcilerFlow 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.59,"slice":"pasted-context","lang":"en"} -{"prompt":"BorealLedgerGateCoordinator: restructure, then correct","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"projects/boreal/ml/pipeline/features.py 里的 BorealNovaPickerService 最近在 Spring Boot 流程中出现间歇性问题。 请写一份面向调用方的说明，包含 contract、错误、retry 和可复制示例，不要改 handler。\n\n约束：\n- 继续使用 Spring Boot\n- 保持兼容性和取消语义\n- 改动只限于 BorealNovaPickerService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"zh"} -{"prompt":"Rename BorealTideWorkerService's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Ticket OPS-42145: retire the legacy replay path for BorealMicaProfileFlow\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，并明确说明证据和取舍。 Map a safe route from the current BorealMicaProfileFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"zh"} -{"prompt":"En projects/boreal/services/ledger/replay.go, BorealEchoRegistryService tiene un problema intermitente en el flujo de Kotlin coroutines. Lee el flujo actual y dime si ownership, cancelación y orden son seguros; solo necesito el análisis.\n\nRestricciones:\n- seguir con Kotlin coroutines\n- conservar compatibilidad y cancelación\n- limitar el cambio a BorealEchoRegistryService","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"es"} -{"prompt":"BorealCoralUploadCoordinator: polish, then assess","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.56,"slice":"mixed","lang":"en"} -{"prompt":"Persist BorealCoralUploadService's replay cursor","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"$ pnpm test --filter BorealCraneWorkspaceFlow\n RUN v3.2.4 /workspace/apps/console\n × BorealCraneWorkspaceFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=42132 phase=resume storedCursor=seg-0183\n session=42132 phase=fetch requestCursor=seg-0183 pageSize=200\n session=42132 phase=commit receivedCursor=seg-0184 itemCount=0\n session=42132 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nReconstruct the BorealCraneWorkspaceFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.92,"slice":"pasted-context","lang":"en"} -{"prompt":"Incident timeline — INC-42138\n\n08:02 deploy BorealSableParserFlow 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 BorealSableParserFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.65,"slice":"pasted-context","lang":"en"} -{"prompt":"A copied hex color in BorealMicaProfileService lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"core","lang":"en"} -{"prompt":"Please resist widening this one: BorealOrbitSyncStore works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealOrbitSyncStore\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"BorealAtlasSearchCoordinator is blocking the next release because memory growth during hour-long imports. I need two concrete outcomes from a single pass: change BorealAtlasSearchCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing GraphQL conventions in projects/boreal/apps/console/routes/usage.svelte; 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.38,"slice":"mixed","lang":"en"} -{"prompt":"Summarize the BorealCloudReconcilerStore changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"Does BorealBirchMigratorStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists? I want your judgment and walkthrough, not new documentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"We expect BorealMapleQueueService to outgrow its current Spring Boot arrangement next quarter, but changing everything at once would be risky. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- leave generated files and vendored code alone\n- stay compatible with the existing Spring Boot deployment\n- keep the work scoped to BorealMapleQueueService and its direct tests\n\nSeveral teams work in this computer vision, React, PostgreSQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.78,"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_42126'\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_42126'::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 BorealCedarPolicyFlow'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.83,"slice":"pasted-context","lang":"en"} -{"prompt":"BorealFernSnapshotCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"diff --git a/projects/boreal/engine/render/atlas.cpp b/projects/boreal/engine/render/atlas.cpp\nindex 62d71aa..90f3c1e 100644\n--- a/projects/boreal/engine/render/atlas.cpp\n+++ b/projects/boreal/engine/render/atlas.cpp\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 BorealWillowCodecCoordinator's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"A copied hex color in BorealMapleQueueFlow lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"boundary","lang":"en"} -{"prompt":"Where did BorealCedarPolicyStore's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"boundary","lang":"en"} -{"prompt":"Is there a cleaner way to separate BorealVelaDrawerFlow'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.58,"slice":"boundary","lang":"en"} -{"prompt":"Dedupe BorealAsterWebhookService's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"We expect BorealSummitProxyStore to outgrow its current Cloudflare Workers arrangement next quarter, but changing everything at once would be risky. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- leave generated files and vendored code alone\n- stay compatible with the existing Cloudflare Workers deployment\n- keep the work scoped to BorealSummitProxyStore and its direct tests\n\nSeveral teams work in this computer vision, React, PostgreSQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"boundary","lang":"en"} -{"prompt":"Is BorealCopperBridgeStore safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"Assess the BorealAcornWidgetStore diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"BorealLumenChartStore returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/boreal/ui/settings/PrivacyPane.tsx and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Give BorealEchoRegistryFlow'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":"Split projects/boreal/app/src/main/SyncWorker.kt by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Ownership of BorealBasilRunnerService is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current Spring Boot operational envelope\n\nThe relevant code crosses computer vision, React, PostgreSQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"BorealFrostPanelCoordinator: sequence, then restructure","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-42154\n\n08:02 deploy BorealDriftConsoleCoordinator 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 BorealDriftConsoleCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Documente le contrat BorealQuartzPlayerService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"fr"} +{"prompt":"How does BorealEchoRegistryStore propagate cancellation through the Kotlin coroutines boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"$ pnpm test --filter BorealAtlasSearchFlow\n RUN v3.2.4 /workspace/apps/console\n × BorealAtlasSearchFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=42111 phase=resume storedCursor=seg-0183\n session=42111 phase=fetch requestCursor=seg-0183 pageSize=200\n session=42111 phase=commit receivedCursor=seg-0184 itemCount=0\n session=42111 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nReconstruct the BorealAtlasSearchFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Pipeline: What is the safest way to split projects/boreal/apps/console/routes/usage.svelte into independently owned modules while BorealMoonlitSDKService's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"Add a bounded BorealBasilRunnerStore export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Two deliverables are holding up BorealIrisBatchCoordinator. First, separate BorealIrisBatchCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/boreal/lib/codec/frame.cc, which follows Kafka conventions and currently suffers from a misleading timeout name used in five packages. 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":"refactor","secondary":"review","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"For BorealPineMetricsCoordinator, finish BorealPineMetricsCoordinator's responsive empty and retry states; once that is complete, give the existing implementation a read-only safety pass. Work from projects/boreal/ml/pipeline/features.py, stay with Spring Boot, and leave generated files and vendored code alone. Keep the two outcomes separately reviewable.","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"En projects/boreal/apps/console/routes/usage.svelte, BorealAtlasSearchStore tiene un problema intermitente en el flujo de GraphQL. Separa responsabilidades y elimina duplicación, conservando API, wire values, orden y comportamiento observable.\n\nRestricciones:\n- seguir con GraphQL\n- conservar compatibilidad y cancelación\n- limitar el cambio a BorealAtlasSearchStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con GraphQL alrededor de BorealAtlasSearchStore.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"es"} +{"prompt":"BorealLumenChartCoordinator: give it a nicer flow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Two asks around BorealCopperBridgeCoordinator: (1) ship the idempotent BorealCopperBridgeCoordinator replay endpoint; (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":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Clarify BorealSlateEditorStore's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-42116: finish the compact BorealCoralUploadFlow filter experience\n\nRoute: /catalog/search\nSource: projects/boreal/db/migrations/20260730_events.sql\nFramework: GraphQL\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 BorealCoralUploadFlow 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":"core","lang":"en"} +{"prompt":"BorealTideWorkerCoordinator needs a paired pass: assess ownership and failure handling in projects/boreal/services/ledger/replay.go, plus capture the contract and rollback note for consumers. Use projects/boreal/services/ledger/replay.go as the source of truth, preserve the Kotlin coroutines contract, and avoid unrelated cleanup.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Clarify BorealCloudReconcilerService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"thread 'tokio-runtime-worker' panicked at projects/boreal/apps/console/routes/usage.svelte:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: borealmoonlitsdkflow::scheduler::LeaseTask::flush\n at ./projects/boreal/apps/console/routes/usage.svelte:217:18\n 4: borealmoonlitsdkflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nReconstruct the BorealMoonlitSDKFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Ticket OPS-42159: retire the legacy replay path for BorealSummitProxyCoordinator\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 BorealSummitProxyCoordinator 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":"BorealOpalRouterCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"BorealSpruceDaemonService's metric is misspelled as succesful_total in one declaration. Correct that literal and its exact test expectation, without renaming anything else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fresh release brief for BorealAmberFilterCoordinator:\n- primary outcome: separate BorealAmberFilterCoordinator's policy from transport without behavior changes\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/boreal/services/ledger/replay.go\n- platform constraint: Kotlin coroutines\n- known complication: stale cursors when a page is resumed\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":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Compare BorealHarborIndexStore's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"The BorealOspreyJobService 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":"BorealNovaPickerCoordinator: polish the last piece","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"For BorealCloudReconcilerCoordinator, finish BorealCloudReconcilerCoordinator's responsive empty and retry states; once that is complete, give the existing implementation a read-only safety pass. Work from projects/boreal/apps/console/routes/usage.svelte, stay with GraphQL, and leave generated files and vendored code alone. Keep the two outcomes separately reviewable.","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"The first BorealPrismCacheStore request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"BorealWrenExportCoordinator: ship, then document","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"diff --git a/projects/boreal/apps/console/routes/usage.svelte b/projects/boreal/apps/console/routes/usage.svelte\nindex 62d71aa..90f3c1e 100644\n--- a/projects/boreal/apps/console/routes/usage.svelte\n+++ b/projects/boreal/apps/console/routes/usage.svelte\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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Split BorealSlateEditorFlow 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":"Gateway: Ticket OPS-42131: retire the legacy replay path for BorealCloudReconcilerFlow\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 BorealCloudReconcilerFlow 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":"BorealLedgerGateCoordinator: restructure, then correct","purpose":"refactor","secondary":"backendImpl","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"projects/boreal/ml/pipeline/features.py 里的 BorealNovaPickerService 最近在 Spring Boot 流程中出现间歇性问题。 请写一份面向调用方的说明，包含 contract、错误、retry 和可复制示例，不要改 handler。\n\n约束：\n- 继续使用 Spring Boot\n- 保持兼容性和取消语义\n- 改动只限于 BorealNovaPickerService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"zh"} +{"prompt":"Rename BorealTideWorkerService's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-42145: retire the legacy replay path for BorealMicaProfileFlow\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，并明确说明证据和取舍。 Map a safe route from the current BorealMicaProfileFlow 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":"En projects/boreal/services/ledger/replay.go, BorealEchoRegistryService tiene un problema intermitente en el flujo de Kotlin coroutines. Lee el flujo actual y dime si ownership, cancelación y orden son seguros; solo necesito el análisis.\n\nRestricciones:\n- seguir con Kotlin coroutines\n- conservar compatibilidad y cancelación\n- limitar el cambio a BorealEchoRegistryService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"es"} +{"prompt":"BorealCoralUploadCoordinator: polish, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Persist BorealCoralUploadService's replay cursor","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"$ pnpm test --filter BorealCraneWorkspaceFlow\n RUN v3.2.4 /workspace/apps/console\n × BorealCraneWorkspaceFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=42132 phase=resume storedCursor=seg-0183\n session=42132 phase=fetch requestCursor=seg-0183 pageSize=200\n session=42132 phase=commit receivedCursor=seg-0184 itemCount=0\n session=42132 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nReconstruct the BorealCraneWorkspaceFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Incident timeline — INC-42138\n\n08:02 deploy BorealSableParserFlow 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 BorealSableParserFlow, 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":"A copied hex color in BorealMicaProfileService lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Please resist widening this one: BorealOrbitSyncStore works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealOrbitSyncStore\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"BorealAtlasSearchCoordinator is blocking the next release because memory growth during hour-long imports. I need two concrete outcomes from a single pass: change BorealAtlasSearchCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing GraphQL conventions in projects/boreal/apps/console/routes/usage.svelte; 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.7,"slice":"mixed","lang":"en"} +{"prompt":"Summarize the BorealCloudReconcilerStore changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Does BorealBirchMigratorStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists? I want your judgment and walkthrough, not new documentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"We expect BorealMapleQueueService to outgrow its current Spring Boot arrangement next quarter, but changing everything at once would be risky. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- leave generated files and vendored code alone\n- stay compatible with the existing Spring Boot deployment\n- keep the work scoped to BorealMapleQueueService and its direct tests\n\nSeveral teams work in this computer vision, React, PostgreSQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"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_42126'\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_42126'::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 BorealCedarPolicyFlow'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.8,"slice":"pasted-context","lang":"en"} +{"prompt":"BorealFernSnapshotCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"diff --git a/projects/boreal/engine/render/atlas.cpp b/projects/boreal/engine/render/atlas.cpp\nindex 62d71aa..90f3c1e 100644\n--- a/projects/boreal/engine/render/atlas.cpp\n+++ b/projects/boreal/engine/render/atlas.cpp\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 BorealWillowCodecCoordinator'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":"A copied hex color in BorealMapleQueueFlow lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Where did BorealCedarPolicyStore's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"Is there a cleaner way to separate BorealVelaDrawerFlow'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":"Dedupe BorealAsterWebhookService's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"We expect BorealSummitProxyStore to outgrow its current Cloudflare Workers arrangement next quarter, but changing everything at once would be risky. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- leave generated files and vendored code alone\n- stay compatible with the existing Cloudflare Workers deployment\n- keep the work scoped to BorealSummitProxyStore and its direct tests\n\nSeveral teams work in this computer vision, React, PostgreSQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Is BorealCopperBridgeStore safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"This should remain a deliberately small patch: BorealWillowCodecService has one known configuration mistake in projects/boreal/lib/codec/frame.cc, not an open-ended failure investigation. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- leave generated files and vendored code alone\n- stay compatible with the existing Kafka deployment\n- keep the work scoped to BorealWillowCodecService and its direct tests\n\nSeveral teams work in this computer vision, React, PostgreSQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"BorealRavenSessionCoordinator: make this less weird","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"vague-eval","lang":"en"} -{"prompt":"Test Suite 'BorealLedgerGateFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[BorealLedgerGateFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/boreal/services/ledger/replay.go:144: error: -[BorealLedgerGateFlowTests 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 '-[BorealLedgerGateFlowTests 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 BorealLedgerGateFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.76,"slice":"pasted-context","lang":"en"} -{"prompt":"CalderaKiteSchedulerStore's FilterDrawer.vue needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"boundary","lang":"en"} -{"prompt":"Ist CalderaCinderAuthStore sicher?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"de"} -{"prompt":"What sequence would let CalderaOrbitSyncService adopt Swift 6 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.67,"slice":"core","lang":"en"} -{"prompt":"Two asks around CalderaDriftConsoleCoordinator: (1) separate CalderaDriftConsoleCoordinator's policy from transport without behavior changes; (2) capture the contract and rollback note for consumers. Do not introduce another runtime dependency, and leave a clear boundary between the resulting artifacts or edits.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Renderer: Ticket OPS-43138: retire the legacy replay path for CalderaBeaconStoreFlow\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 CalderaBeaconStoreFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.65,"slice":"pasted-context","lang":"en"} -{"prompt":"CalderaWrenExportCoordinator: give it a nicer flow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"vague-eval","lang":"en"} -{"prompt":"CalderaAmberFilterStore's staging timeout is already known to be wrong: change the single projects/caldera/Sources/App/SessionStore.swift value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"boundary","lang":"en"} -{"prompt":"Indexer: The CalderaCedarPolicyStore empty state in projects/caldera/web/components/FilterDrawer.vue needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"boundary","lang":"en"} -{"prompt":"Incident timeline — INC-43123\n\n08:02 deploy CalderaBasilRunnerFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current CalderaBasilRunnerFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"pasted-context","lang":"en"} -{"prompt":"Architect a gradual ownership transfer for CalderaFernSnapshotStore across two teams, including module seams, temporary interfaces, observability, handoff criteria, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"// projects/caldera/cmd/exporter/main.py\nfinal class CalderaSableParserFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 CalderaSableParserFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Cadre la migration de CalderaDriftConsoleStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"fr"} -{"prompt":"Apparently: diff --git a/projects/caldera/cmd/exporter/main.py b/projects/caldera/cmd/exporter/main.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/cmd/exporter/main.py\n+++ b/projects/caldera/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\nRead the artifact above as a skeptical reviewer. Is CalderaHarborIndexCoordinator's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Fresh release brief for CalderaNimbusFormCoordinator:\n- primary outcome: assess ownership and failure handling in projects/caldera/packages/api/openapi.yaml\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/caldera/packages/api/openapi.yaml\n- platform constraint: gRPC\n- known complication: out-of-order events after consumer rebalancing\n\nBoth results are required, but they should remain independently reviewable. Do not introduce another runtime dependency; 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.76,"slice":"mixed","lang":"en"} -{"prompt":"CalderaBirchMigratorCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.62,"slice":"mixed","lang":"en"} -{"prompt":"Lately: We expect CalderaMoonlitSDKStore to outgrow its current FastAPI 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- do not introduce another runtime dependency\n- stay compatible with the existing FastAPI deployment\n- keep the work scoped to CalderaMoonlitSDKStore and its direct tests\n\nThe relevant code crosses embedded, Go services, Android. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"boundary","lang":"en"} -{"prompt":"I inherited CalderaPrismCacheService and need a careful read of projects/caldera/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- do not introduce another runtime dependency\n- stay compatible with the existing gRPC deployment\n- keep the work scoped to CalderaPrismCacheService and its direct tests\n\nThe relevant code crosses embedded, Go services, Android. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Corrige le timeout de CalderaCinderAuthService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"core","lang":"fr"} -{"prompt":"CalderaBeaconStoreService's staging timeout is already known to be wrong: change the single projects/caldera/engine/render/atlas.cpp value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"core","lang":"en"} -{"prompt":"The destination for CalderaGarnetModalStore is broadly agreed; the missing piece is a reversible route from projects/caldera/ui/settings/PrivacyPane.tsx to that target. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside CalderaGarnetModalStore\n- do not introduce another runtime dependency\n\nSeveral teams work in this embedded, Go services, Android monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"boundary","lang":"en"} -{"prompt":"Support wants the behavior in projects/caldera/ml/pipeline/features.py recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"One contained cleanup in projects/caldera/cmd/exporter/main.py: remove the obsolete CalderaHarborIndexStore import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"core","lang":"en"} -{"prompt":"Please resist widening this one: CalderaRavenSessionStore works, but staging still carries a setting that production corrected last month. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside CalderaRavenSessionStore\n- do not introduce another runtime dependency\n\nSeveral teams work in this embedded, Go services, Android monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.28,"slice":"boundary","lang":"en"} -{"prompt":"UI ticket DES-43155: finish the compact CalderaCraneWorkspaceCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/caldera/config/staging.toml\nFramework: gRPC\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 CalderaCraneWorkspaceCoordinator's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"pasted-context","lang":"en"} -{"prompt":"projects/caldera/config/staging.toml 里的 CalderaIrisBatchService 最近在 gRPC 流程中出现间歇性问题。 请写一份面向调用方的说明，包含 contract、错误、retry 和可复制示例，不要改 handler。\n\n约束：\n- 继续使用 gRPC\n- 保持兼容性和取消语义\n- 改动只限于 CalderaIrisBatchService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"zh"} -{"prompt":"This should remain a deliberately small patch: CalderaHarborIndexService has one known configuration mistake in projects/caldera/ml/pipeline/features.py, not an open-ended failure investigation. Correct the known literal and the test that intentionally mirrors it; the final diff should stay local enough for an on-call engineer to verify at a glance.\n\nConstraints:\n- do not introduce another runtime dependency\n- stay compatible with the existing OpenTelemetry deployment\n- keep the work scoped to CalderaHarborIndexService and its direct tests\n\nThe relevant code crosses embedded, Go services, Android. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.28,"slice":"core","lang":"en"} -{"prompt":"CalderaFernSnapshotCoordinator: untangle the messy bit","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"vague-eval","lang":"en"} -{"prompt":"For CalderaEchoRegistryCoordinator, separate CalderaEchoRegistryCoordinator's policy from transport without behavior changes; once that is complete, give the existing implementation a read-only safety pass. Work from projects/caldera/Sources/CLI/Commands/Doctor.swift, stay with OpenTelemetry, and do not introduce another runtime dependency. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"CalderaSlateEditorCoordinator: the screen feels unfinished","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"CalderaCinderAuthCoordinator: restructure, then correct","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.73,"slice":"mixed","lang":"en"} -{"prompt":"CalderaBeaconStoreCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"vague-eval","lang":"en"} -{"prompt":"CalderaOrbitSyncCoordinator: sort out the rough edge","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"vague-eval","lang":"en"} -{"prompt":"# CI job 43116: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: OpenTelemetry\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] CalderaRavenSessionFlowIntegration.replays_after_timeout ... ok\n[test] CalderaRavenSessionFlowIntegration.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 \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\nWire CalderaRavenSessionFlow'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.83,"slice":"pasted-context","lang":"en"} -{"prompt":"diff --git a/projects/caldera/lib/codec/frame.cc b/projects/caldera/lib/codec/frame.cc\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/lib/codec/frame.cc\n+++ b/projects/caldera/lib/codec/frame.cc\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure CalderaPineMetricsFlow 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.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Split projects/caldera/services/ledger/replay.go by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"The behavior of CalderaCraneWorkspaceService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/caldera/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- do not introduce another runtime dependency\n- retain the current gRPC operational envelope\n\nThis repository spans embedded, Go services, Android; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.49,"slice":"core","lang":"en"} -{"prompt":"En projects/caldera/ui/settings/PrivacyPane.tsx, CalderaAsterWebhookService tiene un problema intermitente en el flujo de Room. La causa ya está clara: cambia solo el timeout de staging de 15 a 30 segundos y ajusta su assertion.\n\nRestricciones:\n- seguir con Room\n- conservar compatibilidad y cancelación\n- limitar el cambio a CalderaAsterWebhookService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"es"} -{"prompt":"Oddly: diff --git a/projects/caldera/packages/api/openapi.yaml b/projects/caldera/packages/api/openapi.yaml\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/packages/api/openapi.yaml\n+++ b/projects/caldera/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\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Read the artifact above as a skeptical reviewer. Is CalderaFernSnapshotFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"pasted-context","lang":"zh"} -{"prompt":"Currently: projects/caldera/ml/pipeline/features.py の CalderaHarborIndexFlow で、OpenTelemetry の flow に断続的な問題が起きています。 responsive layout、empty/retry state、keyboard focus、dark mode、reduced motion を仕上げてください。\n\n制約:\n- OpenTelemetry を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は CalderaHarborIndexFlow のみ","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"boundary","lang":"ja"} -{"prompt":"Test Suite 'CalderaPrismCacheFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[CalderaPrismCacheFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/caldera/crates/index/src/segment.rs:144: error: -[CalderaPrismCacheFlowTests 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 '-[CalderaPrismCacheFlowTests 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 CalderaPrismCacheFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"pasted-context","lang":"en"} +{"prompt":"BorealRavenSessionCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Test Suite 'BorealLedgerGateFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[BorealLedgerGateFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/boreal/services/ledger/replay.go:144: error: -[BorealLedgerGateFlowTests 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 '-[BorealLedgerGateFlowTests 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 BorealLedgerGateFlow'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":"CalderaKiteSchedulerStore's FilterDrawer.vue needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Ist CalderaCinderAuthStore sicher?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"de"} +{"prompt":"What sequence would let CalderaOrbitSyncService adopt Swift 6 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.8,"slice":"core","lang":"en"} +{"prompt":"Two asks around CalderaDriftConsoleCoordinator: (1) separate CalderaDriftConsoleCoordinator's policy from transport without behavior changes; (2) capture the contract and rollback note for consumers. Do not introduce another runtime dependency, 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":"Renderer: Ticket OPS-43138: retire the legacy replay path for CalderaBeaconStoreFlow\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 CalderaBeaconStoreFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"CalderaWrenExportCoordinator: give it a nicer flow","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"CalderaAmberFilterStore's staging timeout is already known to be wrong: change the single projects/caldera/Sources/App/SessionStore.swift value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Indexer: The CalderaCedarPolicyStore empty state in projects/caldera/web/components/FilterDrawer.vue needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-43123\n\n08:02 deploy CalderaBasilRunnerFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current CalderaBasilRunnerFlow 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":"Architect a gradual ownership transfer for CalderaFernSnapshotStore 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":"// projects/caldera/cmd/exporter/main.py\nfinal class CalderaSableParserFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 CalderaSableParserFlow; 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":"Cadre la migration de CalderaDriftConsoleStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"fr"} +{"prompt":"Apparently: diff --git a/projects/caldera/cmd/exporter/main.py b/projects/caldera/cmd/exporter/main.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/cmd/exporter/main.py\n+++ b/projects/caldera/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\nRead the artifact above as a skeptical reviewer. Is CalderaHarborIndexCoordinator'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":"Fresh release brief for CalderaNimbusFormCoordinator:\n- primary outcome: assess ownership and failure handling in projects/caldera/packages/api/openapi.yaml\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/caldera/packages/api/openapi.yaml\n- platform constraint: gRPC\n- known complication: out-of-order events after consumer rebalancing\n\nBoth results are required, but they should remain independently reviewable. Do not introduce another runtime dependency; 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.8,"slice":"mixed","lang":"en"} +{"prompt":"CalderaBirchMigratorCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Lately: We expect CalderaMoonlitSDKStore to outgrow its current FastAPI 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- do not introduce another runtime dependency\n- stay compatible with the existing FastAPI deployment\n- keep the work scoped to CalderaMoonlitSDKStore and its direct tests\n\nThe relevant code crosses embedded, Go services, 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":"I inherited CalderaPrismCacheService and need a careful read of projects/caldera/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- do not introduce another runtime dependency\n- stay compatible with the existing gRPC deployment\n- keep the work scoped to CalderaPrismCacheService and its direct tests\n\nThe relevant code crosses embedded, Go services, Android. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Corrige le timeout de CalderaCinderAuthService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"fr"} +{"prompt":"CalderaBeaconStoreService's staging timeout is already known to be wrong: change the single projects/caldera/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":"The destination for CalderaGarnetModalStore is broadly agreed; the missing piece is a reversible route from projects/caldera/ui/settings/PrivacyPane.tsx to that target. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside CalderaGarnetModalStore\n- do not introduce another runtime dependency\n\nSeveral teams work in this embedded, Go services, Android monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Support wants the behavior in projects/caldera/ml/pipeline/features.py recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"One contained cleanup in projects/caldera/cmd/exporter/main.py: remove the obsolete CalderaHarborIndexStore import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Please resist widening this one: CalderaRavenSessionStore works, but staging still carries a setting that production corrected last month. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside CalderaRavenSessionStore\n- do not introduce another runtime dependency\n\nSeveral teams work in this embedded, Go services, Android monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-43155: finish the compact CalderaCraneWorkspaceCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/caldera/config/staging.toml\nFramework: gRPC\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 CalderaCraneWorkspaceCoordinator'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":"projects/caldera/config/staging.toml 里的 CalderaIrisBatchService 最近在 gRPC 流程中出现间歇性问题。 请写一份面向调用方的说明，包含 contract、错误、retry 和可复制示例，不要改 handler。\n\n约束：\n- 继续使用 gRPC\n- 保持兼容性和取消语义\n- 改动只限于 CalderaIrisBatchService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"zh"} +{"prompt":"This should remain a deliberately small patch: CalderaHarborIndexService has one known configuration mistake in projects/caldera/ml/pipeline/features.py, not an open-ended failure investigation. Correct the known literal and the test that intentionally mirrors it; the final diff should stay local enough for an on-call engineer to verify at a glance.\n\nConstraints:\n- do not introduce another runtime dependency\n- stay compatible with the existing OpenTelemetry deployment\n- keep the work scoped to CalderaHarborIndexService and its direct tests\n\nThe relevant code crosses embedded, Go services, 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":"CalderaFernSnapshotCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"For CalderaEchoRegistryCoordinator, separate CalderaEchoRegistryCoordinator's policy from transport without behavior changes; once that is complete, give the existing implementation a read-only safety pass. Work from projects/caldera/Sources/CLI/Commands/Doctor.swift, stay with OpenTelemetry, and do not introduce another runtime dependency. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"CalderaSlateEditorCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"CalderaCinderAuthCoordinator: restructure, then correct","purpose":"refactor","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"CalderaBeaconStoreCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"CalderaOrbitSyncCoordinator: sort out the rough edge","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"# CI job 43116: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: OpenTelemetry\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] CalderaRavenSessionFlowIntegration.replays_after_timeout ... ok\n[test] CalderaRavenSessionFlowIntegration.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 \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\nWire CalderaRavenSessionFlow'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":"diff --git a/projects/caldera/lib/codec/frame.cc b/projects/caldera/lib/codec/frame.cc\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/lib/codec/frame.cc\n+++ b/projects/caldera/lib/codec/frame.cc\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure CalderaPineMetricsFlow 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":"Split projects/caldera/services/ledger/replay.go by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"The behavior of CalderaCraneWorkspaceService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/caldera/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- do not introduce another runtime dependency\n- retain the current gRPC operational envelope\n\nThis repository spans embedded, Go services, Android; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"En projects/caldera/ui/settings/PrivacyPane.tsx, CalderaAsterWebhookService tiene un problema intermitente en el flujo de Room. La causa ya está clara: cambia solo el timeout de staging de 15 a 30 segundos y ajusta su assertion.\n\nRestricciones:\n- seguir con Room\n- conservar compatibilidad y cancelación\n- limitar el cambio a CalderaAsterWebhookService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"es"} +{"prompt":"Oddly: diff --git a/projects/caldera/packages/api/openapi.yaml b/projects/caldera/packages/api/openapi.yaml\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/packages/api/openapi.yaml\n+++ b/projects/caldera/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\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Read the artifact above as a skeptical reviewer. Is CalderaFernSnapshotFlow'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":"Currently: projects/caldera/ml/pipeline/features.py の CalderaHarborIndexFlow で、OpenTelemetry の flow に断続的な問題が起きています。 responsive layout、empty/retry state、keyboard focus、dark mode、reduced motion を仕上げてください。\n\n制約:\n- OpenTelemetry を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は CalderaHarborIndexFlow のみ","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"} +{"prompt":"Test Suite 'CalderaPrismCacheFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[CalderaPrismCacheFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/caldera/crates/index/src/segment.rs:144: error: -[CalderaPrismCacheFlowTests 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 '-[CalderaPrismCacheFlowTests 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 CalderaPrismCacheFlow'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":"Compare the old and new CalderaCraneWorkspaceStore 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":"CalderaCedarPolicyCoordinator: deal with the small issue","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"vague-eval","lang":"en"} -{"prompt":"Today: Is there a cleaner way to separate CalderaCraneWorkspaceFlow'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.53,"slice":"boundary","lang":"en"} -{"prompt":"Dedupe CalderaKiteSchedulerService's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Support wants the behavior in projects/caldera/apps/console/routes/usage.svelte recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"# CI job 43122: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: Swift 6\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] CalderaSpruceDaemonFlowIntegration.replays_after_timeout ... ok\n[test] CalderaSpruceDaemonFlowIntegration.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 \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\nReconstruct the CalderaSpruceDaemonFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.92,"slice":"pasted-context","lang":"en"} -{"prompt":"Architect a gradual ownership transfer for CalderaOpalRouterFlow across two teams, including module seams, temporary interfaces, observability, handoff criteria, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"CalderaPrismCacheCoordinator is blocking the next release because a misleading timeout name used in five packages. I need two concrete outcomes from a single pass: ship the idempotent CalderaPrismCacheCoordinator replay endpoint, and capture the contract and rollback note for consumers. Use the existing gRPC conventions in projects/caldera/pkg/cache/lease.rs; do not introduce another runtime dependency. 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":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.83,"slice":"mixed","lang":"en"} -{"prompt":"CalderaWillowCodecCoordinator needs a paired pass: produce a consumer guide for CalderaWillowCodecCoordinator, plus give the existing implementation a read-only safety pass. Use projects/caldera/config/staging.toml as the source of truth, preserve the gRPC contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.43,"slice":"mixed","lang":"en"} -{"prompt":"Two deliverables are holding up CalderaSableParserCoordinator. First, separate CalderaSableParserCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/caldera/ml/pipeline/features.py, which follows OpenTelemetry conventions and currently suffers from stale cursors when a page is resumed. Do not introduce another runtime dependency.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"CalderaJuniperCLICoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"PM is preparing the CalderaTideWorkerService 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 CalderaTideWorkerService\n- do not introduce another runtime dependency\n\nSeveral teams work in this embedded, Go services, Android monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} -{"prompt":"Context: The data is already available in projects/caldera/internal/auth/refresh.go; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"boundary","lang":"en"} -{"prompt":"A flaky failure around CalderaDeltaCanvasService survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. Reconstruct the failing timeline from logs and tests, identify which invariant first breaks, and distinguish causal signals from effects or cleanup noise.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside CalderaDeltaCanvasService\n- do not introduce another runtime dependency\n\nSeveral teams work in this embedded, Go services, Android monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.84,"slice":"core","lang":"en"} -{"prompt":"Why does CalderaOpalRouterStore's Swift 6 worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Background: projects/caldera/src/sync/reconcile.ts now contains CalderaQuartzPlayerStore'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.58,"slice":"boundary","lang":"en"} -{"prompt":"Collapse the CalderaMosaicGridStore wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Question: The behavior of CalderaNovaPickerService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/caldera/lib/codec/frame.cc. 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- do not introduce another runtime dependency\n- retain the current Room operational envelope\n\nThis repository spans embedded, Go services, Android; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Design handed over a final pass for CalderaCloudReconcilerService, and the basic data flow in projects/caldera/internal/auth/refresh.go already works. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- do not introduce another runtime dependency\n- stay compatible with the existing FastAPI deployment\n- keep the work scoped to CalderaCloudReconcilerService and its direct tests\n\nThe relevant code crosses embedded, Go services, Android. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Does CalderaEmberRelayStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Before touching projects/caldera/crates/index/src/segment.rs, 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.62,"slice":"boundary","lang":"en"} -{"prompt":"Introduce a durable deduplication key for CalderaBeaconStoreStore events and enforce it in both the database migration and the ingestion path.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"# projects/caldera/src/sync/reconcile.ts\n[worker.calderasummitproxyflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.calderasummitproxyflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.calderasummitproxyflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.CalderaSummitProxyFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-43132\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/caldera/src/sync/reconcile.ts. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.38,"slice":"pasted-context","lang":"en"} -{"prompt":"Observation: The first CalderaAcornWidgetStore request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"boundary","lang":"en"} -{"prompt":"Constraint: # projects/caldera/workers/thumbnail/consumer.ex\n[worker.calderagarnetmodalflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.calderagarnetmodalflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.calderagarnetmodalflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.CalderaGarnetModalFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-43113\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 CalderaGarnetModalFlow'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.41,"slice":"pasted-context","lang":"es"} -{"prompt":"Two asks around CalderaMosaicGridCoordinator: (1) produce a consumer guide for CalderaMosaicGridCoordinator; (2) give the existing implementation a read-only safety pass. Do not introduce another runtime dependency, and leave a clear boundary between the resulting artifacts or edits.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.51,"slice":"mixed","lang":"en"} -{"prompt":"CalderaSpruceDaemonCoordinator: restructure, then correct","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Clarify CalderaSpruceDaemonService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"CalderaFrostPanelCoordinator: take care of the warning","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} -{"prompt":"Ticket OPS-43136: retire the legacy replay path for CalderaAmberFilterFlow\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 CalderaAmberFilterFlow 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.59,"slice":"pasted-context","lang":"en"} -{"prompt":"Request: # projects/caldera/pkg/cache/lease.rs\n[worker.calderawrenexportflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.calderawrenexportflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.calderawrenexportflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.CalderaWrenExportFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-43140\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 CalderaWrenExportFlow'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.33,"slice":"pasted-context","lang":"en"} -{"prompt":"For CalderaSummitProxyCoordinator, ship the idempotent CalderaSummitProxyCoordinator replay endpoint; once that is complete, give the existing implementation a read-only safety pass. Work from projects/caldera/db/migrations/20260730_events.sql, stay with Swift 6, and do not introduce another runtime dependency. Keep the two outcomes separately reviewable.","purpose":"backendImpl","secondary":"review","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"CalderaMarbleTokenCoordinator needs a paired pass: lay out a staged migration for CalderaMarbleTokenCoordinator, plus consolidate the duplicated normalization paths without changing behavior. Use projects/caldera/ml/pipeline/features.py as the source of truth, preserve the OpenTelemetry contract, and avoid unrelated cleanup.","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.74,"slice":"mixed","lang":"en"} -{"prompt":"CalderaRainfallDBStore needs an idempotent replay endpoint backed by gRPC; accept a cursor, cap each page at 500 items, and return a stable continuation token.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"The CalderaCoralUploadService empty state in projects/caldera/web/components/FilterDrawer.vue needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Fresh release brief for CalderaDeltaCanvasCoordinator:\n- primary outcome: separate CalderaDeltaCanvasCoordinator's policy from transport without behavior changes\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/caldera/db/migrations/20260730_events.sql\n- platform constraint: Swift 6\n- known complication: cancellation being swallowed at the repository boundary\n\nBoth results are required, but they should remain independently reviewable. Do not introduce another runtime dependency; 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":"refactor","secondary":"writing","mixed":true,"difficulty":0.84,"slice":"mixed","lang":"en"} -{"prompt":"projects/caldera/workers/thumbnail/consumer.ex 里的 CalderaFrostPanelStore 最近在 Room 流程中出现间歇性问题。 请写一份面向调用方的说明，包含 contract、错误、retry 和可复制示例，不要改 handler。\n\n约束：\n- 继续使用 Room\n- 保持兼容性和取消语义\n- 改动只限于 CalderaFrostPanelStore","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"boundary","lang":"zh"} -{"prompt":"Why is CalderaLumenChartStore stalling?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Outline a safer CalderaFlintTimelineService cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Rename CalderaSummitProxyService's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-43131\n\n08:02 deploy CalderaMarbleTokenFlow 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 CalderaMarbleTokenFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.59,"slice":"pasted-context","lang":"en"} -{"prompt":"Split CalderaBirchMigratorStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Decouple CalderaSummitProxyStore's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Clarify CalderaMapleQueueStore's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"boundary","lang":"en"} -{"prompt":"Give CalderaAsterWebhookStore'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.52,"slice":"core","lang":"en"} -{"prompt":"Release verification found a single stale CalderaNimbusFormStore 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- do not introduce another runtime dependency\n- retain the current gRPC operational envelope\n\nThis repository spans embedded, Go services, Android; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.25,"slice":"boundary","lang":"en"} -{"prompt":"Trace CalderaMarbleTokenService's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"CalderaMapleQueueCoordinator needs a paired pass: finish CalderaMapleQueueCoordinator's responsive empty and retry states, plus capture the contract and rollback note for consumers. Use projects/caldera/engine/render/atlas.cpp as the source of truth, preserve the Room contract, and avoid unrelated cleanup.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.61,"slice":"mixed","lang":"en"} -{"prompt":"Our support and SDK teams keep answering the same questions about CalderaGarnetModalService, but the current prose in projects/caldera/workers/thumbnail/consumer.ex 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- do not introduce another runtime dependency\n- stay compatible with the existing Room deployment\n- keep the work scoped to CalderaGarnetModalService and its direct tests\n\nThe relevant code crosses embedded, Go services, Android. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"We expect CalderaFlintTimelineStore to outgrow its current Swift 6 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- do not introduce another runtime dependency\n- stay compatible with the existing Swift 6 deployment\n- keep the work scoped to CalderaFlintTimelineStore and its direct tests\n\nThe relevant code crosses embedded, Go services, Android. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.83,"slice":"boundary","lang":"en"} -{"prompt":"Pin CalderaBasilRunnerStore's Room dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"boundary","lang":"en"} -{"prompt":"Ticket OPS-43154: retire the legacy replay path for CalderaCloudReconcilerCoordinator\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 CalderaCloudReconcilerCoordinator 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.67,"slice":"pasted-context","lang":"en"} -{"prompt":"Store CalderaMapleQueueService's delivery receipts","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-43115\n\n08:02 deploy CalderaNimbusFormFlow 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 CalderaNimbusFormFlow 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.57,"slice":"pasted-context","lang":"en"} -{"prompt":"Sequence CalderaBasilRunnerService's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Map CalderaEchoRegistryService's ownership split","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Goal: Two asks around CalderaEmberRelayCoordinator: (1) change CalderaEmberRelayCoordinator's known staging timeout from 15 to 30 seconds; (2) capture the contract and rollback note for consumers. Do not introduce another runtime dependency, and leave a clear boundary between the resulting artifacts or edits.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.29,"slice":"mixed","lang":"en"} -{"prompt":"diff --git a/projects/caldera/src/sync/reconcile.ts b/projects/caldera/src/sync/reconcile.ts\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/src/sync/reconcile.ts\n+++ b/projects/caldera/src/sync/reconcile.ts\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure CalderaDeltaCanvasFlow 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Test Suite 'CalderaLumenChartFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[CalderaLumenChartFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/caldera/pkg/cache/lease.rs:144: error: -[CalderaLumenChartFlowTests 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 '-[CalderaLumenChartFlowTests 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 CalderaLumenChartFlow'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.68,"slice":"pasted-context","lang":"en"} -{"prompt":"Does CalderaLedgerGateStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"CalderaAmberFilterCoordinator: make this less weird","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"vague-eval","lang":"en"} -{"prompt":"CalderaQuartzPlayerCoordinator: could this be clearer","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"vague-eval","lang":"en"} -{"prompt":"CalderaPineMetricsCoordinator: polish the last piece","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"vague-eval","lang":"en"} -{"prompt":"Bump CalderaMoonlitSDKService's timeout to 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"core","lang":"en"} -{"prompt":"Symptom: // projects/caldera/infra/modules/edge/main.tf\nfinal class CalderaMoonlitSDKFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 CalderaMoonlitSDKFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Pin CalderaWillowCodecService's gRPC dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"core","lang":"en"} -{"prompt":"Two deliverables are holding up CalderaMoonlitSDKCoordinator. First, change CalderaMoonlitSDKCoordinator's known staging timeout from 15 to 30 seconds. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/caldera/internal/auth/refresh.go, which follows FastAPI conventions and currently suffers from a deadlock that appears only during shutdown. Do not introduce another runtime dependency.\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":"quickFix","secondary":"review","mixed":true,"difficulty":0.45,"slice":"mixed","lang":"en"} -{"prompt":"The first CalderaOspreyJobFlow request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","lang":"en"} -{"prompt":"How should CalderaSpruceDaemonStore be decomposed?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","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_43121'\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_43121'::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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Determine why CalderaBirchMigratorFlow 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.9,"slice":"pasted-context","lang":"de"} -{"prompt":"Give CalderaNimbusFormService a loading skeleton","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"Headsup: Ticket OPS-43158: retire the legacy replay path for CalderaNovaPickerCoordinator\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for CalderaNovaPickerCoordinator, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.65,"slice":"pasted-context","lang":"en"} -{"prompt":"What does CalderaMosaicGridService own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"CalderaLedgerGateCoordinator: maybe tighten this up","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"vague-eval","lang":"en"} -{"prompt":"projects/caldera/apps/console/routes/usage.svelte has grown through several launches, and CalderaOpalRouterService now mixes policy, transport, persistence, and metrics in one place. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- do not introduce another runtime dependency\n- stay compatible with the existing Swift 6 deployment\n- keep the work scoped to CalderaOpalRouterService and its direct tests\n\nThe relevant code crosses embedded, Go services, Android. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Could the reasoning behind CalderaTideWorkerFlow's OpenTelemetry choices be captured as an ADR for engineers joining the project next quarter? The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"Read projects/caldera/engine/render/atlas.cpp and tell me whether CalderaPineMetricsStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","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_43149'\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_43149'::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\nReconstruct the CalderaCedarPolicyFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"Em projects/caldera/packages/api/openapi.yaml, o CalderaIrisBatchStore tem um problema intermitente no fluxo de gRPC. Leia o fluxo atual e avalie ownership, cancelamento e ordem; preciso apenas da análise.\n\nRestrições:\n- continuar com gRPC\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao CalderaIrisBatchStore","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"pt"} -{"prompt":"FYI: # projects/caldera/services/ledger/replay.go\n[worker.calderakiteschedulerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.calderakiteschedulerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.calderakiteschedulerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.CalderaKiteSchedulerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-43129\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Make the one confirmed configuration correction in projects/caldera/services/ledger/replay.go. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.43,"slice":"pasted-context","lang":"fr"} -{"prompt":"In projects/caldera/cmd/exporter/main.py hat CalderaSableParserService ein sporadisches Problem im OpenTelemetry-Ablauf. Trenne Verantwortlichkeiten und entferne Duplikate, ohne API, Wire-Werte, Reihenfolge oder sichtbares Verhalten zu ändern.\n\nRandbedingungen:\n- OpenTelemetry weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf CalderaSableParserService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um CalderaSableParserService mit OpenTelemetry kompatibel.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"de"} -{"prompt":"CalderaAtlasSearchCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"vague-eval","lang":"en"} +{"prompt":"CalderaCedarPolicyCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Today: Is there a cleaner way to separate CalderaCraneWorkspaceFlow'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":"Dedupe CalderaKiteSchedulerService's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Support wants the behavior in projects/caldera/apps/console/routes/usage.svelte recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"# CI job 43122: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: Swift 6\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] CalderaSpruceDaemonFlowIntegration.replays_after_timeout ... ok\n[test] CalderaSpruceDaemonFlowIntegration.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 \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\nReconstruct the CalderaSpruceDaemonFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Architect a gradual ownership transfer for CalderaOpalRouterFlow 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":"CalderaPrismCacheCoordinator is blocking the next release because a misleading timeout name used in five packages. I need two concrete outcomes from a single pass: ship the idempotent CalderaPrismCacheCoordinator replay endpoint, and capture the contract and rollback note for consumers. Use the existing gRPC conventions in projects/caldera/pkg/cache/lease.rs; do not introduce another runtime dependency. 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":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"CalderaWillowCodecCoordinator needs a paired pass: produce a consumer guide for CalderaWillowCodecCoordinator, plus give the existing implementation a read-only safety pass. Use projects/caldera/config/staging.toml as the source of truth, preserve the gRPC contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Two deliverables are holding up CalderaSableParserCoordinator. First, separate CalderaSableParserCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/caldera/ml/pipeline/features.py, which follows OpenTelemetry conventions and currently suffers from stale cursors when a page is resumed. Do not introduce another runtime dependency.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"CalderaJuniperCLICoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"PM is preparing the CalderaTideWorkerService 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 CalderaTideWorkerService\n- do not introduce another runtime dependency\n\nSeveral teams work in this embedded, Go services, 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":"Context: The data is already available in projects/caldera/internal/auth/refresh.go; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"A flaky failure around CalderaDeltaCanvasService survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. Reconstruct the failing timeline from logs and tests, identify which invariant first breaks, and distinguish causal signals from effects or cleanup noise.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside CalderaDeltaCanvasService\n- do not introduce another runtime dependency\n\nSeveral teams work in this embedded, Go services, Android monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Why does CalderaOpalRouterStore's Swift 6 worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Background: projects/caldera/src/sync/reconcile.ts now contains CalderaQuartzPlayerStore'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.4,"slice":"core","lang":"en"} +{"prompt":"Collapse the CalderaMosaicGridStore wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Question: The behavior of CalderaNovaPickerService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/caldera/lib/codec/frame.cc. 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- do not introduce another runtime dependency\n- retain the current Room operational envelope\n\nThis repository spans embedded, Go services, Android; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Design handed over a final pass for CalderaCloudReconcilerService, and the basic data flow in projects/caldera/internal/auth/refresh.go already works. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- do not introduce another runtime dependency\n- stay compatible with the existing FastAPI deployment\n- keep the work scoped to CalderaCloudReconcilerService and its direct tests\n\nThe relevant code crosses embedded, Go services, Android. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Does CalderaEmberRelayStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Before touching projects/caldera/crates/index/src/segment.rs, 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.9,"slice":"core","lang":"en"} +{"prompt":"Introduce a durable deduplication key for CalderaBeaconStoreStore 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":"# projects/caldera/src/sync/reconcile.ts\n[worker.calderasummitproxyflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.calderasummitproxyflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.calderasummitproxyflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.CalderaSummitProxyFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-43132\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/caldera/src/sync/reconcile.ts. 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":"Observation: The first CalderaAcornWidgetStore request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Constraint: # projects/caldera/workers/thumbnail/consumer.ex\n[worker.calderagarnetmodalflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.calderagarnetmodalflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.calderagarnetmodalflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.CalderaGarnetModalFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-43113\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 CalderaGarnetModalFlow'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":"Two asks around CalderaMosaicGridCoordinator: (1) produce a consumer guide for CalderaMosaicGridCoordinator; (2) give the existing implementation a read-only safety pass. Do not introduce another runtime dependency, and leave a clear boundary between the resulting artifacts or edits.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"CalderaSpruceDaemonCoordinator: restructure, then correct","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Clarify CalderaSpruceDaemonService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"CalderaFrostPanelCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Ticket OPS-43136: retire the legacy replay path for CalderaAmberFilterFlow\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 CalderaAmberFilterFlow 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":"Request: # projects/caldera/pkg/cache/lease.rs\n[worker.calderawrenexportflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.calderawrenexportflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.calderawrenexportflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.CalderaWrenExportFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-43140\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 CalderaWrenExportFlow'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":"For CalderaSummitProxyCoordinator, ship the idempotent CalderaSummitProxyCoordinator replay endpoint; once that is complete, give the existing implementation a read-only safety pass. Work from projects/caldera/db/migrations/20260730_events.sql, stay with Swift 6, and do not introduce another runtime dependency. Keep the two outcomes separately reviewable.","purpose":"backendImpl","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"CalderaMarbleTokenCoordinator needs a paired pass: lay out a staged migration for CalderaMarbleTokenCoordinator, plus consolidate the duplicated normalization paths without changing behavior. Use projects/caldera/ml/pipeline/features.py as the source of truth, preserve the OpenTelemetry contract, and avoid unrelated cleanup.","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"CalderaRainfallDBStore needs an idempotent replay endpoint backed by gRPC; accept a cursor, cap each page at 500 items, and return a stable continuation token.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"The CalderaCoralUploadService empty state in projects/caldera/web/components/FilterDrawer.vue needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Fresh release brief for CalderaDeltaCanvasCoordinator:\n- primary outcome: separate CalderaDeltaCanvasCoordinator's policy from transport without behavior changes\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/caldera/db/migrations/20260730_events.sql\n- platform constraint: Swift 6\n- known complication: cancellation being swallowed at the repository boundary\n\nBoth results are required, but they should remain independently reviewable. Do not introduce another runtime dependency; 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":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"projects/caldera/workers/thumbnail/consumer.ex 里的 CalderaFrostPanelStore 最近在 Room 流程中出现间歇性问题。 请写一份面向调用方的说明，包含 contract、错误、retry 和可复制示例，不要改 handler。\n\n约束：\n- 继续使用 Room\n- 保持兼容性和取消语义\n- 改动只限于 CalderaFrostPanelStore","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"zh"} +{"prompt":"Why is CalderaLumenChartStore stalling?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Outline a safer CalderaFlintTimelineService cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Rename CalderaSummitProxyService's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Incident timeline — INC-43131\n\n08:02 deploy CalderaMarbleTokenFlow 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 CalderaMarbleTokenFlow, 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":"Split CalderaBirchMigratorStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Decouple CalderaSummitProxyStore's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Clarify CalderaMapleQueueStore's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Give CalderaAsterWebhookStore'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":"Release verification found a single stale CalderaNimbusFormStore 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- do not introduce another runtime dependency\n- retain the current gRPC operational envelope\n\nThis repository spans embedded, Go services, 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":"Trace CalderaMarbleTokenService's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"CalderaMapleQueueCoordinator needs a paired pass: finish CalderaMapleQueueCoordinator's responsive empty and retry states, plus capture the contract and rollback note for consumers. Use projects/caldera/engine/render/atlas.cpp as the source of truth, preserve the Room contract, and avoid unrelated cleanup.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Our support and SDK teams keep answering the same questions about CalderaGarnetModalService, but the current prose in projects/caldera/workers/thumbnail/consumer.ex 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- do not introduce another runtime dependency\n- stay compatible with the existing Room deployment\n- keep the work scoped to CalderaGarnetModalService and its direct tests\n\nThe relevant code crosses embedded, Go services, 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":"We expect CalderaFlintTimelineStore to outgrow its current Swift 6 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- do not introduce another runtime dependency\n- stay compatible with the existing Swift 6 deployment\n- keep the work scoped to CalderaFlintTimelineStore and its direct tests\n\nThe relevant code crosses embedded, Go services, 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":"Pin CalderaBasilRunnerStore's Room dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-43154: retire the legacy replay path for CalderaCloudReconcilerCoordinator\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 CalderaCloudReconcilerCoordinator 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":"Store CalderaMapleQueueService's delivery receipts","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-43115\n\n08:02 deploy CalderaNimbusFormFlow 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 CalderaNimbusFormFlow 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":"Sequence CalderaBasilRunnerService's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Map CalderaEchoRegistryService's ownership split","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Goal: Two asks around CalderaEmberRelayCoordinator: (1) change CalderaEmberRelayCoordinator's known staging timeout from 15 to 30 seconds; (2) capture the contract and rollback note for consumers. Do not introduce another runtime dependency, and leave a clear boundary between the resulting artifacts or edits.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"diff --git a/projects/caldera/src/sync/reconcile.ts b/projects/caldera/src/sync/reconcile.ts\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/src/sync/reconcile.ts\n+++ b/projects/caldera/src/sync/reconcile.ts\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure CalderaDeltaCanvasFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Test Suite 'CalderaLumenChartFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[CalderaLumenChartFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/caldera/pkg/cache/lease.rs:144: error: -[CalderaLumenChartFlowTests 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 '-[CalderaLumenChartFlowTests 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 CalderaLumenChartFlow'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":"Does CalderaLedgerGateStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"CalderaAmberFilterCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"CalderaQuartzPlayerCoordinator: could this be clearer","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"CalderaPineMetricsCoordinator: polish the last piece","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump CalderaMoonlitSDKService's timeout to 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Symptom: // projects/caldera/infra/modules/edge/main.tf\nfinal class CalderaMoonlitSDKFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 CalderaMoonlitSDKFlow; 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":"Pin CalderaWillowCodecService's gRPC dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Two deliverables are holding up CalderaMoonlitSDKCoordinator. First, change CalderaMoonlitSDKCoordinator's known staging timeout from 15 to 30 seconds. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/caldera/internal/auth/refresh.go, which follows FastAPI conventions and currently suffers from a deadlock that appears only during shutdown. Do not introduce another runtime dependency.\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":"quickFix","secondary":"debugging","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"The first CalderaOspreyJobFlow request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"How should CalderaSpruceDaemonStore be decomposed?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"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_43121'\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_43121'::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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Determine why CalderaBirchMigratorFlow 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":"Give CalderaNimbusFormService a loading skeleton","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Headsup: Ticket OPS-43158: retire the legacy replay path for CalderaNovaPickerCoordinator\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for CalderaNovaPickerCoordinator, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"What does CalderaMosaicGridService own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"CalderaLedgerGateCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"projects/caldera/apps/console/routes/usage.svelte has grown through several launches, and CalderaOpalRouterService now mixes policy, transport, persistence, and metrics in one place. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- do not introduce another runtime dependency\n- stay compatible with the existing Swift 6 deployment\n- keep the work scoped to CalderaOpalRouterService and its direct tests\n\nThe relevant code crosses embedded, Go services, Android. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Could the reasoning behind CalderaTideWorkerFlow's OpenTelemetry choices be captured as an ADR for engineers joining the project next quarter? The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Read projects/caldera/engine/render/atlas.cpp and tell me whether CalderaPineMetricsStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"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_43149'\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_43149'::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\nReconstruct the CalderaCedarPolicyFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Em projects/caldera/packages/api/openapi.yaml, o CalderaIrisBatchStore tem um problema intermitente no fluxo de gRPC. Leia o fluxo atual e avalie ownership, cancelamento e ordem; preciso apenas da análise.\n\nRestrições:\n- continuar com gRPC\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao CalderaIrisBatchStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"pt"} +{"prompt":"FYI: # projects/caldera/services/ledger/replay.go\n[worker.calderakiteschedulerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.calderakiteschedulerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.calderakiteschedulerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.CalderaKiteSchedulerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-43129\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Make the one confirmed configuration correction in projects/caldera/services/ledger/replay.go. 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":"In projects/caldera/cmd/exporter/main.py hat CalderaSableParserService ein sporadisches Problem im OpenTelemetry-Ablauf. Trenne Verantwortlichkeiten und entferne Duplikate, ohne API, Wire-Werte, Reihenfolge oder sichtbares Verhalten zu ändern.\n\nRandbedingungen:\n- OpenTelemetry weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf CalderaSableParserService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um CalderaSableParserService mit OpenTelemetry kompatibel.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} +{"prompt":"CalderaAtlasSearchCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"CalderaPineMetricsService 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":"Match CalderaVelaDrawerStore's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"boundary","lang":"en"} -{"prompt":"# CI job 43143: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: Room\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] CalderaFrostPanelFlowIntegration.replays_after_timeout ... ok\n[test] CalderaFrostPanelFlowIntegration.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 \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\nReconstruct the CalderaFrostPanelFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.95,"slice":"pasted-context","lang":"en"} -{"prompt":"Clarify CalderaVelaDrawerService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"Please turn CalderaJuniperCLIStore's existing tests into a short contract reference, covering pagination, malformed input, authorization, and retry semantics without copying test code. The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"en"} -{"prompt":"CalderaMicaProfileCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Meanwhile: Incident timeline — INC-43159\n\n08:02 deploy CalderaOspreyJobCoordinator 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 CalderaOspreyJobCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.67,"slice":"pasted-context","lang":"en"} -{"prompt":"Ticket OPS-43146: retire the legacy replay path for CalderaLedgerGateFlow\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 CalderaLedgerGateFlow 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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Set CalderaEchoRegistryStore's port to 8081","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"boundary","lang":"en"} -{"prompt":"CalderaDriftConsoleService é seguro?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"pt"} -{"prompt":"Two asks around CalderaVelaDrawerCoordinator: (1) assess ownership and failure handling in projects/caldera/pkg/cache/lease.rs; (2) capture the contract and rollback note for consumers. Do not introduce another runtime dependency, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"Production says CalderaOspreyJobStore is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current FastAPI operational envelope\n\nThis repository spans embedded, Go services, Android; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.89,"slice":"boundary","lang":"en"} -{"prompt":"projects/caldera/engine/render/atlas.cpp has grown through several launches, and CalderaNovaPickerStore now mixes policy, transport, persistence, and metrics in one place. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- do not introduce another runtime dependency\n- stay compatible with the existing Room deployment\n- keep the work scoped to CalderaNovaPickerStore and its direct tests\n\nThe relevant code crosses embedded, Go services, Android. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.77,"slice":"boundary","lang":"en"} -{"prompt":"CalderaLumenChartCoordinator: sequence, then polish","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"CalderaCoralUploadCoordinator: clean up that old path","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"The name pendingAck means two different things across CalderaAtlasSearchService's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Read projects/caldera/Sources/CLI/Commands/Doctor.swift and tell me whether CalderaTideWorkerStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Any races in CalderaMicaProfileStore?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Incident timeline — INC-43125\n\n08:02 deploy CalderaWillowCodecFlow 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 CalderaWillowCodecFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"pasted-context","lang":"en"} -{"prompt":"Bring CalderaAsterWebhookFlow'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.52,"slice":"boundary","lang":"en"} -{"prompt":"Locally: 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_43135'\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_43135'::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\nFind the source of this CalderaIrisBatchFlow 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.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Set CalderaLumenChartService's port to 8081","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-43117\n\n08:02 deploy CalderaFlintTimelineFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current CalderaFlintTimelineFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a bounded CalderaNovaPickerFlow export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"Ticket OPS-43137: retire the legacy replay path for CalderaOrbitSyncFlow\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. Assess CalderaOrbitSyncFlow 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.79,"slice":"pasted-context","lang":"pt"} -{"prompt":"CalderaFlintTimelineCoordinator: correct, then assess","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.24,"slice":"mixed","lang":"en"} -{"prompt":"Production: Incident timeline — INC-43119\n\n08:02 deploy CalderaCinderAuthFlow 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 CalderaCinderAuthFlow rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"Staging: The data is already available in projects/caldera/Sources/CLI/Commands/Doctor.swift; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"CI: Incident timeline — INC-43147\n\n08:02 deploy CalderaJuniperCLIFlow 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 CalderaJuniperCLIFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.62,"slice":"pasted-context","lang":"en"} -{"prompt":"Atlas: Incident timeline — INC-43130\n\n08:02 deploy CalderaVelaDrawerFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nDetermine why CalderaVelaDrawerFlow 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.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Test Suite 'CalderaEmberRelayFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[CalderaEmberRelayFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/caldera/internal/auth/refresh.go:144: error: -[CalderaEmberRelayFlowTests 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 '-[CalderaEmberRelayFlowTests 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\nFinish the visible CalderaEmberRelayFlow 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.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current CalderaOspreyJobService 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 CalderaOspreyJobService\n- do not introduce another runtime dependency\n\nSeveral teams work in this embedded, Go services, Android monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Ownership of CalderaCopperBridgeService 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- do not introduce another runtime dependency\n- retain the current Swift 6 operational envelope\n\nThis repository spans embedded, Go services, Android; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.83,"slice":"core","lang":"en"} -{"prompt":"CalderaCloudReconcilerFlow's staging timeout is already known to be wrong: change the single projects/caldera/internal/auth/refresh.go value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"boundary","lang":"en"} -{"prompt":"CalderaAcornWidgetCoordinator: handle the lingering thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"vague-eval","lang":"en"} +{"prompt":"Match CalderaVelaDrawerStore's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"# CI job 43143: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: Room\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] CalderaFrostPanelFlowIntegration.replays_after_timeout ... ok\n[test] CalderaFrostPanelFlowIntegration.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 \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\nReconstruct the CalderaFrostPanelFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Clarify CalderaVelaDrawerService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Please turn CalderaJuniperCLIStore's existing tests into a short contract reference, covering pagination, malformed input, authorization, and retry semantics without copying test code. The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"CalderaMicaProfileCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Meanwhile: Incident timeline — INC-43159\n\n08:02 deploy CalderaOspreyJobCoordinator 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 CalderaOspreyJobCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Ticket OPS-43146: retire the legacy replay path for CalderaLedgerGateFlow\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 CalderaLedgerGateFlow 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":"Set CalderaEchoRegistryStore's port to 8081","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"CalderaDriftConsoleService é seguro?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"pt"} +{"prompt":"Two asks around CalderaVelaDrawerCoordinator: (1) assess ownership and failure handling in projects/caldera/pkg/cache/lease.rs; (2) capture the contract and rollback note for consumers. Do not introduce another runtime dependency, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Production says CalderaOspreyJobStore is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current FastAPI operational envelope\n\nThis repository spans embedded, Go services, Android; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"projects/caldera/engine/render/atlas.cpp has grown through several launches, and CalderaNovaPickerStore now mixes policy, transport, persistence, and metrics in one place. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- do not introduce another runtime dependency\n- stay compatible with the existing Room deployment\n- keep the work scoped to CalderaNovaPickerStore and its direct tests\n\nThe relevant code crosses embedded, Go services, Android. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"CalderaLumenChartCoordinator: sequence, then polish","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"CalderaCoralUploadCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"The name pendingAck means two different things across CalderaAtlasSearchService's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Read projects/caldera/Sources/CLI/Commands/Doctor.swift and tell me whether CalderaTideWorkerStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Any races in CalderaMicaProfileStore?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-43125\n\n08:02 deploy CalderaWillowCodecFlow 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 CalderaWillowCodecFlow, 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":"Bring CalderaAsterWebhookFlow'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":"Locally: 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_43135'\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_43135'::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\nFind the source of this CalderaIrisBatchFlow symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Set CalderaLumenChartService's port to 8081","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-43117\n\n08:02 deploy CalderaFlintTimelineFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current CalderaFlintTimelineFlow 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":"Add a bounded CalderaNovaPickerFlow export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-43137: retire the legacy replay path for CalderaOrbitSyncFlow\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. Assess CalderaOrbitSyncFlow 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":"CalderaFlintTimelineCoordinator: correct, then assess","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Production: Incident timeline — INC-43119\n\n08:02 deploy CalderaCinderAuthFlow 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 CalderaCinderAuthFlow 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":"Staging: The data is already available in projects/caldera/Sources/CLI/Commands/Doctor.swift; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"CI: Incident timeline — INC-43147\n\n08:02 deploy CalderaJuniperCLIFlow 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 CalderaJuniperCLIFlow 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":"Atlas: Incident timeline — INC-43130\n\n08:02 deploy CalderaVelaDrawerFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nDetermine why CalderaVelaDrawerFlow 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":"Test Suite 'CalderaEmberRelayFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[CalderaEmberRelayFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/caldera/internal/auth/refresh.go:144: error: -[CalderaEmberRelayFlowTests 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 '-[CalderaEmberRelayFlowTests 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\nFinish the visible CalderaEmberRelayFlow 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":"Nobody is asking for code changes yet; we first need to understand whether the current CalderaOspreyJobService 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 CalderaOspreyJobService\n- do not introduce another runtime dependency\n\nSeveral teams work in this embedded, Go services, 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":"Ownership of CalderaCopperBridgeService 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- do not introduce another runtime dependency\n- retain the current Swift 6 operational envelope\n\nThis repository spans embedded, Go services, 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":"CalderaCloudReconcilerFlow's staging timeout is already known to be wrong: change the single projects/caldera/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":"CalderaAcornWidgetCoordinator: handle the lingering thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"How does CalderaFernSnapshotService propagate cancellation through the gRPC boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"The name pendingAck means two different things across CalderaLedgerGateService's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"CalderaBasilRunnerCoordinator: polish, then correct","purpose":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.61,"slice":"mixed","lang":"en"} -{"prompt":"Could CalderaCopperBridgeStore show the active Swift 6 sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"core","lang":"en"} -{"prompt":"Before touching projects/caldera/db/migrations/20260730_events.sql, 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.67,"slice":"boundary","lang":"en"} -{"prompt":"diff --git a/projects/caldera/crates/index/src/segment.rs b/projects/caldera/crates/index/src/segment.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/crates/index/src/segment.rs\n+++ b/projects/caldera/crates/index/src/segment.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit CalderaRainfallDBCoordinator 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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"2026-07-30T08:14:11.409Z level=info service=calderacoraluploadflow pod=calderacoraluploadflow-7cf8 request_id=43139 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=calderacoraluploadflow request_id=43139 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=calderacoraluploadflow request_id=43139 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=calderacoraluploadflow request_id=43139 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=calderacoraluploadflow request_id=43139 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=calderacoraluploadflow request_id=43139 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=calderacoraluploadflow request_id=43139 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=calderacoraluploadflow request_id=43139 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nDetermine why CalderaCoralUploadFlow 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.96,"slice":"pasted-context","lang":"en"} -{"prompt":"CalderaGarnetModalCoordinator is blocking the next release because a feature flag whose default differs between environments. I need two concrete outcomes from a single pass: change CalderaGarnetModalCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing Room conventions in projects/caldera/ui/settings/PrivacyPane.tsx; do not introduce another runtime dependency. 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.43,"slice":"mixed","lang":"en"} -{"prompt":"Three teams extended CalderaDeltaCanvasStore independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current Swift 6 operational envelope\n\nThis repository spans embedded, Go services, Android; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.74,"slice":"boundary","lang":"en"} -{"prompt":"Extract CalderaMarbleTokenStore's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Drop CalderaRavenSessionService's unused import","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"core","lang":"en"} -{"prompt":"Responsive layout for CalderaBirchMigratorService","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"Beacon: Ticket OPS-43134: retire the legacy replay path for CalderaAtlasSearchFlow\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 CalderaAtlasSearchFlow rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"For CalderaKiteSchedulerCoordinator, produce a consumer guide for CalderaKiteSchedulerCoordinator; once that is complete, correct the known stale timeout beside it. Work from projects/caldera/web/components/FilterDrawer.vue, stay with FastAPI, and do not introduce another runtime dependency. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.53,"slice":"mixed","lang":"en"} -{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current CalderaRainfallDBService 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 CalderaRainfallDBService\n- do not introduce another runtime dependency\n\nSeveral teams work in this embedded, Go services, Android monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Draft CalderaMicaProfileService's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"// projects/caldera/Sources/App/SessionStore.swift\nfinal class CalderaEchoRegistryFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 CalderaEchoRegistryFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Support wants the behavior in projects/caldera/services/ledger/replay.go recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary. The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"boundary","lang":"en"} -{"prompt":"Cinder: // projects/caldera/ml/pipeline/features.py\nfinal class CalderaAcornWidgetFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 CalderaAcornWidgetFlow 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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"En projects/caldera/ml/pipeline/features.py, CalderaSableParserStore tiene un problema intermitente en el flujo de OpenTelemetry. Termina el layout responsive, estados vacío y retry, foco por teclado, dark mode y reduced motion.\n\nRestricciones:\n- seguir con OpenTelemetry\n- conservar compatibilidad y cancelación\n- limitar el cambio a CalderaSableParserStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"es"} -{"prompt":"Delta: projects/caldera/ui/settings/PrivacyPane.tsx の CalderaFrostPanelService で、Room の flow に断続的な問題が起きています。 queue、scheduler、cancel 経路を追い、仮説を比較して、変更前に原因を特定してください。\n\n制約:\n- Room を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は CalderaFrostPanelService のみ","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"ja"} -{"prompt":"Ember: The minimum supported FastAPI version in projects/caldera/infra/modules/edge/main.tf is one patch behind the lockfile. Align that single value and regenerate only the affected metadata.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"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_43156'\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_43156'::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\nFind the source of this CalderaTideWorkerCoordinator 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.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Frost: The API work is done; what remains for CalderaPrismCacheStore 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 CalderaPrismCacheStore\n- do not introduce another runtime dependency\n\nSeveral teams work in this embedded, Go services, Android monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Where did CalderaWillowCodecStore's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Read projects/caldera/internal/auth/refresh.go and tell me whether CalderaSlateEditorService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"diff --git a/projects/caldera/engine/render/atlas.cpp b/projects/caldera/engine/render/atlas.cpp\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/engine/render/atlas.cpp\n+++ b/projects/caldera/engine/render/atlas.cpp\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 CalderaMicaProfileFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Garnet: The CalderaRainfallDBFlow 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.09,"slice":"boundary","lang":"en"} -{"prompt":"Harbor: diff --git a/projects/caldera/lib/codec/frame.cc b/projects/caldera/lib/codec/frame.cc\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/lib/codec/frame.cc\n+++ b/projects/caldera/lib/codec/frame.cc\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nWire CalderaMapleQueueFlow'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.89,"slice":"pasted-context","lang":"en"} -{"prompt":"// projects/caldera/internal/auth/refresh.go\nfinal class CalderaSlateEditorFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 CalderaSlateEditorFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Serve CalderaEmberRelayService health checks","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Release engineering needs a CalderaQuartzPlayerService changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"What is the safest way to split projects/caldera/apps/console/routes/usage.svelte into independently owned modules while CalderaOrbitSyncStore's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Iris: diff --git a/projects/caldera/db/migrations/20260730_events.sql b/projects/caldera/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/db/migrations/20260730_events.sql\n+++ b/projects/caldera/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure CalderaQuartzPlayerFlow 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"UI ticket DES-43127: finish the compact CalderaDriftConsoleFlow filter experience\n\nRoute: /catalog/search\nSource: projects/caldera/apps/console/routes/usage.svelte\nFramework: Swift 6\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 CalderaDriftConsoleFlow 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.73,"slice":"pasted-context","lang":"en"} -{"prompt":"CalderaIrisBatchCoordinator: smooth out this interaction","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"vague-eval","lang":"en"} -{"prompt":"Incident timeline — INC-43153\n\n08:02 deploy CalderaAsterWebhookCoordinator 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Capture the CalderaAsterWebhookCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.65,"slice":"pasted-context","lang":"ja"} -{"prompt":"Ticket OPS-43152: retire the legacy replay path for CalderaCopperBridgeCoordinator\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 CalderaCopperBridgeCoordinator rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"Could CalderaWrenExportService show the active gRPC sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"thread 'tokio-runtime-worker' panicked at projects/caldera/workers/thumbnail/consumer.ex:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: calderamosaicgridflow::scheduler::LeaseTask::flush\n at ./projects/caldera/workers/thumbnail/consumer.ex:217:18\n 4: calderamosaicgridflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nDetermine why CalderaMosaicGridFlow 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.95,"slice":"pasted-context","lang":"en"} -{"prompt":"Juniper: // projects/caldera/app/src/main/SyncWorker.kt\nfinal class CalderaOpalRouterCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 CalderaOpalRouterCoordinator 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"CalderaRavenSessionCoordinator: restructure, then correct","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"Before we approve CalderaSlateEditorStore, assess whether two validators with subtly different error strings is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Kestrel: projects/dovetail/apps/console/routes/usage.svelte 里的 DovetailLumenChartStore 最近在 Playwright 流程中出现间歇性问题。 请完成 responsive layout、空状态、retry、键盘焦点、dark mode 和 reduced motion。\n\n约束：\n- 继续使用 Playwright\n- 保持兼容性和取消语义\n- 改动只限于 DovetailLumenChartStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"zh"} -{"prompt":"Does DovetailSableParserService enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Is there a cleaner way to separate DovetailSummitProxyStore'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.53,"slice":"core","lang":"en"} -{"prompt":"Test Suite 'DovetailEmberRelayFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[DovetailEmberRelayFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/dovetail/ml/pipeline/features.py:144: error: -[DovetailEmberRelayFlowTests 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 '-[DovetailEmberRelayFlowTests 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\nFinish the visible DovetailEmberRelayFlow 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.73,"slice":"pasted-context","lang":"en"} -{"prompt":"Lumen: # projects/dovetail/src/sync/reconcile.ts\n[worker.dovetailnimbusformflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetailnimbusformflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetailnimbusformflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailNimbusFormFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44138\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/dovetail/src/sync/reconcile.ts and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.41,"slice":"pasted-context","lang":"en"} -{"prompt":"The behavior of DovetailWrenExportService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/dovetail/apps/console/routes/usage.svelte. 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- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Playwright operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"DovetailFlintTimelineCoordinator: why is this odd","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"vague-eval","lang":"en"} -{"prompt":"Maple: The DovetailVelaDrawerFlow surface in projects/dovetail/app/src/main/SyncWorker.kt 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.41,"slice":"boundary","lang":"en"} -{"prompt":"Security flagged DovetailMarbleTokenService for a read-only pass because its Terraform boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Terraform operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"UI ticket DES-44128: finish the compact DovetailCraneWorkspaceFlow filter experience\n\nRoute: /catalog/search\nSource: projects/dovetail/db/migrations/20260730_events.sql\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\nBring DovetailCraneWorkspaceFlow'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.76,"slice":"pasted-context","lang":"en"} -{"prompt":"How does DovetailAmberFilterFlow propagate cancellation through the Terraform boundary, and are there code paths where ownership becomes ambiguous? Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Em projects/dovetail/web/components/FilterDrawer.vue, o DovetailDeltaCanvasStore tem um problema intermitente no fluxo de Redis Streams. A causa já é conhecida: mude apenas o timeout de staging de 15 para 30 segundos e ajuste a assertion.\n\nRestrições:\n- continuar com Redis Streams\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao DovetailDeltaCanvasStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"boundary","lang":"pt"} -{"prompt":"For DovetailPrismCacheCoordinator, assess ownership and failure handling in projects/dovetail/app/src/main/SyncWorker.kt; once that is complete, capture the contract and rollback note for consumers. Work from projects/dovetail/app/src/main/SyncWorker.kt, stay with Playwright, and make rollback possible without deleting user data. Keep the two outcomes separately reviewable.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Incident timeline — INC-44148\n\n08:02 deploy DovetailWillowCodecFlow 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 DovetailWillowCodecFlow rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"pasted-context","lang":"en"} -{"prompt":"DovetailJuniperCLICoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.43,"slice":"mixed","lang":"en"} -{"prompt":"What is the safest way to split projects/dovetail/cmd/exporter/main.py into independently owned modules while DovetailMoonlitSDKService's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Rename DovetailTideWorkerStore's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Ticket OPS-44133: retire the legacy replay path for DovetailPrismCacheFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for DovetailPrismCacheFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.65,"slice":"pasted-context","lang":"en"} -{"prompt":"thread 'tokio-runtime-worker' panicked at projects/dovetail/web/components/FilterDrawer.vue:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: dovetailcopperbridgeflow::scheduler::LeaseTask::flush\n at ./projects/dovetail/web/components/FilterDrawer.vue:217:18\n 4: dovetailcopperbridgeflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nFind the source of this DovetailCopperBridgeFlow 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.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Does DovetailBasilRunnerService enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"DovetailCedarPolicyCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"Nimbus: Ticket OPS-44111: retire the legacy replay path for DovetailBeaconStoreFlow\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 DovetailBeaconStoreFlow 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.59,"slice":"pasted-context","lang":"en"} -{"prompt":"Opal: What does DovetailOspreyJobService own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Is DovetailTideWorkerService safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Release verification found a single stale DovetailSlateEditorStore value; the cause, desired value, and affected assertion are already agreed. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Core Data operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"Prism: Incident timeline — INC-44116\n\n08:02 deploy DovetailFrostPanelFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current DovetailFrostPanelFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"Could the reasoning behind DovetailDriftConsoleStore's Redis Streams choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"DovetailFlintTimelineService 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.53,"slice":"core","lang":"en"} -{"prompt":"Two asks around DovetailCopperBridgeCoordinator: (1) find the unknown cause of stale cursors when a page is resumed; (2) give the existing implementation a read-only safety pass. Make rollback possible without deleting user data, and leave a clear boundary between the resulting artifacts or edits.","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.73,"slice":"mixed","lang":"en"} -{"prompt":"DovetailPineMetricsCoordinator: ship, then document","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Describe DovetailFernSnapshotStore's error envelope","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"boundary","lang":"en"} -{"prompt":"Quartz: Ticket OPS-44149: retire the legacy replay path for DovetailEchoRegistryFlow\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 DovetailEchoRegistryFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"En projects/dovetail/config/staging.toml, DovetailBeaconStoreStore tiene un problema intermitente en el flujo de React 19. La causa ya está clara: cambia solo el timeout de staging de 15 a 30 segundos y ajusta su assertion.\n\nRestricciones:\n- seguir con React 19\n- conservar compatibilidad y cancelación\n- limitar el cambio a DovetailBeaconStoreStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.28,"slice":"boundary","lang":"es"} -{"prompt":"DovetailRavenSessionService'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.19,"slice":"core","lang":"en"} -{"prompt":"Raven: Incident timeline — INC-44118\n\n08:02 deploy DovetailFernSnapshotFlow 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 DovetailFernSnapshotFlow rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"pasted-context","lang":"en"} -{"prompt":"Fresh release brief for DovetailAcornWidgetCoordinator:\n- primary outcome: assess ownership and failure handling in projects/dovetail/engine/render/atlas.cpp\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/dovetail/engine/render/atlas.cpp\n- platform constraint: Terraform\n- known complication: an empty state that flashes before cached data arrives\n\nBoth results are required, but they should remain independently reviewable. Make rollback possible without deleting user data; 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.86,"slice":"mixed","lang":"en"} -{"prompt":"DovetailCoralUploadCoordinator is blocking the next release because a deadlock that appears only during shutdown. I need two concrete outcomes from a single pass: find the unknown cause of a deadlock that appears only during shutdown, and capture the contract and rollback note for consumers. Use the existing Core Data conventions in projects/dovetail/Sources/CLI/Commands/Doctor.swift; make rollback possible without deleting user data. Keep the outcomes distinct so reviewers can see which evidence supports the assessment and which files or prose satisfy the requested change.\n\nConstraints:\n- preserve public wire values and tenant boundaries\n- cover cancellation and retry behavior\n- avoid generated code and unrelated cleanup\n- include a rollback trigger that an on-call engineer can measure\n\nThis is a fresh workstream for the release, so derive everything from the repository and the context here.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.94,"slice":"mixed","lang":"en"} -{"prompt":"# projects/dovetail/pkg/cache/lease.rs\n[worker.dovetailasterwebhookflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetailasterwebhookflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetailasterwebhookflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailAsterWebhookFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44126\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/dovetail/pkg/cache/lease.rs and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.36,"slice":"pasted-context","lang":"en"} -{"prompt":"On compact widths, DovetailCinderAuthService'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.49,"slice":"core","lang":"en"} -{"prompt":"Sable: Incident timeline — INC-44156\n\n08:02 deploy DovetailMosaicGridCoordinator 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 DovetailMosaicGridCoordinator 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.59,"slice":"pasted-context","lang":"en"} -{"prompt":"Tide: Ticket OPS-44143: retire the legacy replay path for DovetailLumenChartFlow\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 DovetailLumenChartFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.65,"slice":"pasted-context","lang":"en"} -{"prompt":"A previously stable test around DovetailWillowCodecStore now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"diff --git a/projects/dovetail/ui/settings/PrivacyPane.tsx b/projects/dovetail/ui/settings/PrivacyPane.tsx\nindex 62d71aa..90f3c1e 100644\n--- a/projects/dovetail/ui/settings/PrivacyPane.tsx\n+++ b/projects/dovetail/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\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Read the artifact above as a skeptical reviewer. Is DovetailTideWorkerFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"fr"} -{"prompt":"DovetailMicaProfileCoordinator: polish the last piece","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"vague-eval","lang":"en"} -{"prompt":"Support wants the behavior in projects/dovetail/web/components/FilterDrawer.vue recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"boundary","lang":"en"} -{"prompt":"Ticket OPS-44113: retire the legacy replay path for DovetailWrenExportFlow\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\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Add the bounded DovetailWrenExportFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"es"} -{"prompt":"Umbra: Ticket OPS-44136: retire the legacy replay path for DovetailGarnetModalFlow\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 DovetailGarnetModalFlow 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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"DovetailFernSnapshotCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.51,"slice":"mixed","lang":"en"} -{"prompt":"Corrija o timeout de DovetailCloudReconcilerService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"core","lang":"pt"} -{"prompt":"Before we approve DovetailNimbusFormService, assess whether lost focus when the drawer animation finishes is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"DovetailKiteSchedulerFlow needs an idempotent replay endpoint backed by Core Data; accept a cursor, cap each page at 500 items, and return a stable continuation token.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"DovetailSpruceDaemonCoordinator: ship a sensible version","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"vague-eval","lang":"en"} -{"prompt":"The next client release depends on a new DovetailCoralUploadService capability in projects/dovetail/Sources/App/SessionStore.swift, with Core Data already chosen by the platform group. Implement the endpoint and durable cursor, enforce tenant authorization and idempotency, emit useful spans, cap work per request, and include focused tests for retries, cancellation, and malformed cursors.\n\nConstraints:\n- make rollback possible without deleting user data\n- stay compatible with the existing Core Data deployment\n- keep the work scoped to DovetailCoralUploadService and its direct tests\n\nThis repository spans game tooling, data pipelines, macOS; use its existing conventions rather than importing a new abstraction.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Vela: The data is already available in projects/dovetail/pkg/cache/lease.rs; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"boundary","lang":"en"} -{"prompt":"Parse DovetailHarborIndexStore's signed cursor","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Two deliverables are holding up DovetailWrenExportCoordinator. First, find the unknown cause of out-of-order events after consumer rebalancing. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/dovetail/app/src/main/SyncWorker.kt, which follows Playwright conventions and currently suffers from out-of-order events after consumer rebalancing. Make rollback possible without deleting user data.\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.96,"slice":"mixed","lang":"en"} -{"prompt":"DovetailSpruceDaemonService returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/dovetail/web/components/FilterDrawer.vue and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Willow: Ticket OPS-44141: retire the legacy replay path for DovetailMicaProfileFlow\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 DovetailMicaProfileFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"// projects/dovetail/infra/modules/edge/main.tf\nfinal class DovetailFlintTimelineFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 DovetailFlintTimelineFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"pasted-context","lang":"en"} -{"prompt":"DovetailWillowCodecCoordinator: smooth out this interaction","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} -{"prompt":"PM is preparing the DovetailIrisBatchService rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside DovetailIrisBatchService\n- make rollback possible without deleting user data\n\nThe relevant code crosses game tooling, data pipelines, macOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Split DovetailJuniperCLIStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"Incident timeline — INC-44154\n\n08:02 deploy DovetailMarbleTokenCoordinator 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 DovetailMarbleTokenCoordinator, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.67,"slice":"pasted-context","lang":"en"} -{"prompt":"DovetailSlateEditorCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.48,"slice":"mixed","lang":"en"} -{"prompt":"A copied hex color in DovetailEmberRelayService lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"core","lang":"en"} -{"prompt":"DovetailTideWorkerCoordinator needs a paired pass: assess ownership and failure handling in projects/dovetail/workers/thumbnail/consumer.ex, plus capture the contract and rollback note for consumers. Use projects/dovetail/workers/thumbnail/consumer.ex as the source of truth, preserve the Terraform contract, and avoid unrelated cleanup.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Xylem: # projects/dovetail/cmd/exporter/main.py\n[worker.dovetailslateeditorflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetailslateeditorflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetailslateeditorflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailSlateEditorFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44117\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/dovetail/cmd/exporter/main.py and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.38,"slice":"pasted-context","lang":"en"} -{"prompt":"Yarrow: Two asks around DovetailNovaPickerCoordinator: (1) lay out a staged migration for DovetailNovaPickerCoordinator; (2) also add the visible loading and offline states. Make rollback possible without deleting user data, and leave a clear boundary between the resulting artifacts or edits.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.74,"slice":"mixed","lang":"en"} -{"prompt":"In projects/dovetail/packages/api/openapi.yaml hat DovetailBeaconStoreService 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 DovetailBeaconStoreService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um DovetailBeaconStoreService mit React 19 kompatibel.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"de"} -{"prompt":"DovetailFrostPanelCoordinator: correct, then assess","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.22,"slice":"mixed","lang":"en"} -{"prompt":"Outline a safer DovetailCedarPolicyStore cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Incident timeline — INC-44150\n\n08:02 deploy DovetailDriftConsoleCoordinator 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 DovetailDriftConsoleCoordinator 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.57,"slice":"pasted-context","lang":"en"} -{"prompt":"Fresh release brief for DovetailBeaconStoreCoordinator:\n- primary outcome: separate DovetailBeaconStoreCoordinator's policy from transport without behavior changes\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/dovetail/config/staging.toml\n- platform constraint: React 19\n- known complication: a feature flag whose default differs between environments\n\nBoth results are required, but they should remain independently reviewable. Make rollback possible without deleting user data; 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":"refactor","secondary":"writing","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"thread 'tokio-runtime-worker' panicked at projects/dovetail/pkg/cache/lease.rs:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: dovetailbasilrunnerflow::scheduler::LeaseTask::flush\n at ./projects/dovetail/pkg/cache/lease.rs:217:18\n 4: dovetailbasilrunnerflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nFind the source of this DovetailBasilRunnerFlow 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.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Describe DovetailJuniperCLIService's error envelope","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"The DovetailEchoRegistryService empty state in projects/dovetail/ui/settings/PrivacyPane.tsx needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Zephyr: projects/dovetail/internal/auth/refresh.go now contains DovetailFlintTimelineStore'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.53,"slice":"boundary","lang":"en"} +{"prompt":"The name pendingAck means two different things across CalderaLedgerGateService's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"CalderaBasilRunnerCoordinator: polish, then correct","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Could CalderaCopperBridgeStore show the active Swift 6 sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Before touching projects/caldera/db/migrations/20260730_events.sql, 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":"diff --git a/projects/caldera/crates/index/src/segment.rs b/projects/caldera/crates/index/src/segment.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/crates/index/src/segment.rs\n+++ b/projects/caldera/crates/index/src/segment.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit CalderaRainfallDBCoordinator 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":"2026-07-30T08:14:11.409Z level=info service=calderacoraluploadflow pod=calderacoraluploadflow-7cf8 request_id=43139 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=calderacoraluploadflow request_id=43139 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=calderacoraluploadflow request_id=43139 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=calderacoraluploadflow request_id=43139 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=calderacoraluploadflow request_id=43139 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=calderacoraluploadflow request_id=43139 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=calderacoraluploadflow request_id=43139 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=calderacoraluploadflow request_id=43139 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nDetermine why CalderaCoralUploadFlow 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":"CalderaGarnetModalCoordinator is blocking the next release because a feature flag whose default differs between environments. I need two concrete outcomes from a single pass: change CalderaGarnetModalCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing Room conventions in projects/caldera/ui/settings/PrivacyPane.tsx; do not introduce another runtime dependency. 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.5,"slice":"mixed","lang":"en"} +{"prompt":"Three teams extended CalderaDeltaCanvasStore independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current Swift 6 operational envelope\n\nThis repository spans embedded, Go services, Android; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Extract CalderaMarbleTokenStore's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Drop CalderaRavenSessionService's unused import","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Responsive layout for CalderaBirchMigratorService","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Beacon: Ticket OPS-43134: retire the legacy replay path for CalderaAtlasSearchFlow\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 CalderaAtlasSearchFlow 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":"For CalderaKiteSchedulerCoordinator, produce a consumer guide for CalderaKiteSchedulerCoordinator; once that is complete, correct the known stale timeout beside it. Work from projects/caldera/web/components/FilterDrawer.vue, stay with FastAPI, and do not introduce another runtime dependency. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current CalderaRainfallDBService 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 CalderaRainfallDBService\n- do not introduce another runtime dependency\n\nSeveral teams work in this embedded, Go services, 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":"Draft CalderaMicaProfileService's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"// projects/caldera/Sources/App/SessionStore.swift\nfinal class CalderaEchoRegistryFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 CalderaEchoRegistryFlow; 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":"Support wants the behavior in projects/caldera/services/ledger/replay.go recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary. The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Cinder: // projects/caldera/ml/pipeline/features.py\nfinal class CalderaAcornWidgetFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 CalderaAcornWidgetFlow 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":"En projects/caldera/ml/pipeline/features.py, CalderaSableParserStore tiene un problema intermitente en el flujo de OpenTelemetry. Termina el layout responsive, estados vacío y retry, foco por teclado, dark mode y reduced motion.\n\nRestricciones:\n- seguir con OpenTelemetry\n- conservar compatibilidad y cancelación\n- limitar el cambio a CalderaSableParserStore","purpose":"frontendImpl","secondary":"debugging","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"es"} +{"prompt":"Delta: projects/caldera/ui/settings/PrivacyPane.tsx の CalderaFrostPanelService で、Room の flow に断続的な問題が起きています。 queue、scheduler、cancel 経路を追い、仮説を比較して、変更前に原因を特定してください。\n\n制約:\n- Room を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は CalderaFrostPanelService のみ","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"} +{"prompt":"Ember: The minimum supported FastAPI version in projects/caldera/infra/modules/edge/main.tf 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":"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_43156'\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_43156'::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\nFind the source of this CalderaTideWorkerCoordinator symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Frost: The API work is done; what remains for CalderaPrismCacheStore 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 CalderaPrismCacheStore\n- do not introduce another runtime dependency\n\nSeveral teams work in this embedded, Go services, Android monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Where did CalderaWillowCodecStore's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Read projects/caldera/internal/auth/refresh.go and tell me whether CalderaSlateEditorService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/caldera/engine/render/atlas.cpp b/projects/caldera/engine/render/atlas.cpp\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/engine/render/atlas.cpp\n+++ b/projects/caldera/engine/render/atlas.cpp\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 CalderaMicaProfileFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"Garnet: The CalderaRainfallDBFlow 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":"Harbor: diff --git a/projects/caldera/lib/codec/frame.cc b/projects/caldera/lib/codec/frame.cc\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/lib/codec/frame.cc\n+++ b/projects/caldera/lib/codec/frame.cc\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nWire CalderaMapleQueueFlow'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.8,"slice":"pasted-context","lang":"en"} +{"prompt":"// projects/caldera/internal/auth/refresh.go\nfinal class CalderaSlateEditorFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 CalderaSlateEditorFlow; 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":"Serve CalderaEmberRelayService health checks","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Release engineering needs a CalderaQuartzPlayerService 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":"What is the safest way to split projects/caldera/apps/console/routes/usage.svelte into independently owned modules while CalderaOrbitSyncStore's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Iris: diff --git a/projects/caldera/db/migrations/20260730_events.sql b/projects/caldera/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/db/migrations/20260730_events.sql\n+++ b/projects/caldera/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure CalderaQuartzPlayerFlow 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":"UI ticket DES-43127: finish the compact CalderaDriftConsoleFlow filter experience\n\nRoute: /catalog/search\nSource: projects/caldera/apps/console/routes/usage.svelte\nFramework: Swift 6\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 CalderaDriftConsoleFlow 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":"core","lang":"en"} +{"prompt":"CalderaIrisBatchCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-43153\n\n08:02 deploy CalderaAsterWebhookCoordinator 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Capture the CalderaAsterWebhookCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Ticket OPS-43152: retire the legacy replay path for CalderaCopperBridgeCoordinator\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 CalderaCopperBridgeCoordinator rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Could CalderaWrenExportService show the active gRPC 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":"thread 'tokio-runtime-worker' panicked at projects/caldera/workers/thumbnail/consumer.ex:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: calderamosaicgridflow::scheduler::LeaseTask::flush\n at ./projects/caldera/workers/thumbnail/consumer.ex:217:18\n 4: calderamosaicgridflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nDetermine why CalderaMosaicGridFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Juniper: // projects/caldera/app/src/main/SyncWorker.kt\nfinal class CalderaOpalRouterCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 CalderaOpalRouterCoordinator 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":"CalderaRavenSessionCoordinator: restructure, then correct","purpose":"refactor","secondary":"backendImpl","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Before we approve CalderaSlateEditorStore, assess whether two validators with subtly different error strings is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Kestrel: projects/dovetail/apps/console/routes/usage.svelte 里的 DovetailLumenChartStore 最近在 Playwright 流程中出现间歇性问题。 请完成 responsive layout、空状态、retry、键盘焦点、dark mode 和 reduced motion。\n\n约束：\n- 继续使用 Playwright\n- 保持兼容性和取消语义\n- 改动只限于 DovetailLumenChartStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"Does DovetailSableParserService enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Is there a cleaner way to separate DovetailSummitProxyStore'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":"Test Suite 'DovetailEmberRelayFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[DovetailEmberRelayFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/dovetail/ml/pipeline/features.py:144: error: -[DovetailEmberRelayFlowTests 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 '-[DovetailEmberRelayFlowTests 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\nFinish the visible DovetailEmberRelayFlow 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":"Lumen: # projects/dovetail/src/sync/reconcile.ts\n[worker.dovetailnimbusformflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetailnimbusformflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetailnimbusformflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailNimbusFormFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44138\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/dovetail/src/sync/reconcile.ts and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"The behavior of DovetailWrenExportService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/dovetail/apps/console/routes/usage.svelte. 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- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Playwright operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS 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":"DovetailFlintTimelineCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Maple: The DovetailVelaDrawerFlow surface in projects/dovetail/app/src/main/SyncWorker.kt 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":"Security flagged DovetailMarbleTokenService for a read-only pass because its Terraform boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Terraform operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-44128: finish the compact DovetailCraneWorkspaceFlow filter experience\n\nRoute: /catalog/search\nSource: projects/dovetail/db/migrations/20260730_events.sql\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\nBring DovetailCraneWorkspaceFlow'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":"How does DovetailAmberFilterFlow propagate cancellation through the Terraform boundary, and are there code paths where ownership becomes ambiguous? Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Em projects/dovetail/web/components/FilterDrawer.vue, o DovetailDeltaCanvasStore tem um problema intermitente no fluxo de Redis Streams. A causa já é conhecida: mude apenas o timeout de staging de 15 para 30 segundos e ajuste a assertion.\n\nRestrições:\n- continuar com Redis Streams\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao DovetailDeltaCanvasStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"pt"} +{"prompt":"For DovetailPrismCacheCoordinator, assess ownership and failure handling in projects/dovetail/app/src/main/SyncWorker.kt; once that is complete, capture the contract and rollback note for consumers. Work from projects/dovetail/app/src/main/SyncWorker.kt, stay with Playwright, and make rollback possible without deleting user data. Keep the two outcomes separately reviewable.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Incident timeline — INC-44148\n\n08:02 deploy DovetailWillowCodecFlow 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 DovetailWillowCodecFlow 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":"DovetailJuniperCLICoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"What is the safest way to split projects/dovetail/cmd/exporter/main.py into independently owned modules while DovetailMoonlitSDKService's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Rename DovetailTideWorkerStore's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Ticket OPS-44133: retire the legacy replay path for DovetailPrismCacheFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for DovetailPrismCacheFlow, 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":"thread 'tokio-runtime-worker' panicked at projects/dovetail/web/components/FilterDrawer.vue:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: dovetailcopperbridgeflow::scheduler::LeaseTask::flush\n at ./projects/dovetail/web/components/FilterDrawer.vue:217:18\n 4: dovetailcopperbridgeflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nFind the source of this DovetailCopperBridgeFlow 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":"Does DovetailBasilRunnerService enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"DovetailCedarPolicyCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Nimbus: Ticket OPS-44111: retire the legacy replay path for DovetailBeaconStoreFlow\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 DovetailBeaconStoreFlow 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":"Opal: What does DovetailOspreyJobService own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Is DovetailTideWorkerService safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Release verification found a single stale DovetailSlateEditorStore value; the cause, desired value, and affected assertion are already agreed. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Core Data operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Prism: Incident timeline — INC-44116\n\n08:02 deploy DovetailFrostPanelFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current DovetailFrostPanelFlow 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":"Could the reasoning behind DovetailDriftConsoleStore's Redis Streams choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"DovetailFlintTimelineService 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":"Two asks around DovetailCopperBridgeCoordinator: (1) find the unknown cause of stale cursors when a page is resumed; (2) give the existing implementation a read-only safety pass. Make rollback possible without deleting user data, and leave a clear boundary between the resulting artifacts or edits.","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"DovetailPineMetricsCoordinator: ship, then document","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Describe DovetailFernSnapshotStore's error envelope","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Quartz: Ticket OPS-44149: retire the legacy replay path for DovetailEchoRegistryFlow\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 DovetailEchoRegistryFlow 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":"En projects/dovetail/config/staging.toml, DovetailBeaconStoreStore tiene un problema intermitente en el flujo de React 19. La causa ya está clara: cambia solo el timeout de staging de 15 a 30 segundos y ajusta su assertion.\n\nRestricciones:\n- seguir con React 19\n- conservar compatibilidad y cancelación\n- limitar el cambio a DovetailBeaconStoreStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"es"} +{"prompt":"DovetailRavenSessionService's metric is misspelled as succesful_total in one declaration. Correct that literal and its exact test expectation, without renaming anything else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Raven: Incident timeline — INC-44118\n\n08:02 deploy DovetailFernSnapshotFlow 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 DovetailFernSnapshotFlow 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":"Fresh release brief for DovetailAcornWidgetCoordinator:\n- primary outcome: assess ownership and failure handling in projects/dovetail/engine/render/atlas.cpp\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/dovetail/engine/render/atlas.cpp\n- platform constraint: Terraform\n- known complication: an empty state that flashes before cached data arrives\n\nBoth results are required, but they should remain independently reviewable. Make rollback possible without deleting user data; 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.8,"slice":"mixed","lang":"en"} +{"prompt":"DovetailCoralUploadCoordinator is blocking the next release because a deadlock that appears only during shutdown. I need two concrete outcomes from a single pass: find the unknown cause of a deadlock that appears only during shutdown, and capture the contract and rollback note for consumers. Use the existing Core Data conventions in projects/dovetail/Sources/CLI/Commands/Doctor.swift; make rollback possible without deleting user data. Keep the outcomes distinct so reviewers can see which evidence supports the assessment and which files or prose satisfy the requested change.\n\nConstraints:\n- preserve public wire values and tenant boundaries\n- cover cancellation and retry behavior\n- avoid generated code and unrelated cleanup\n- include a rollback trigger that an on-call engineer can measure\n\nThis is a fresh workstream for the release, so derive everything from the repository and the context here.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"# projects/dovetail/pkg/cache/lease.rs\n[worker.dovetailasterwebhookflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetailasterwebhookflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetailasterwebhookflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailAsterWebhookFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44126\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/dovetail/pkg/cache/lease.rs and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"On compact widths, DovetailCinderAuthService'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.4,"slice":"core","lang":"en"} +{"prompt":"Sable: Incident timeline — INC-44156\n\n08:02 deploy DovetailMosaicGridCoordinator 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 DovetailMosaicGridCoordinator 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":"Tide: Ticket OPS-44143: retire the legacy replay path for DovetailLumenChartFlow\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 DovetailLumenChartFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"A previously stable test around DovetailWillowCodecStore 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":"diff --git a/projects/dovetail/ui/settings/PrivacyPane.tsx b/projects/dovetail/ui/settings/PrivacyPane.tsx\nindex 62d71aa..90f3c1e 100644\n--- a/projects/dovetail/ui/settings/PrivacyPane.tsx\n+++ b/projects/dovetail/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\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Read the artifact above as a skeptical reviewer. Is DovetailTideWorkerFlow'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":"DovetailMicaProfileCoordinator: polish the last piece","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Support wants the behavior in projects/dovetail/web/components/FilterDrawer.vue recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Ticket OPS-44113: retire the legacy replay path for DovetailWrenExportFlow\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\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Add the bounded DovetailWrenExportFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Umbra: Ticket OPS-44136: retire the legacy replay path for DovetailGarnetModalFlow\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 DovetailGarnetModalFlow 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":"DovetailFernSnapshotCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Corrija o timeout de DovetailCloudReconcilerService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"pt"} +{"prompt":"Before we approve DovetailNimbusFormService, assess whether lost focus when the drawer animation finishes is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"DovetailKiteSchedulerFlow needs an idempotent replay endpoint backed by Core Data; accept a cursor, cap each page at 500 items, and return a stable continuation token.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"DovetailSpruceDaemonCoordinator: ship a sensible version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"The next client release depends on a new DovetailCoralUploadService capability in projects/dovetail/Sources/App/SessionStore.swift, with Core Data already chosen by the platform group. Implement the endpoint and durable cursor, enforce tenant authorization and idempotency, emit useful spans, cap work per request, and include focused tests for retries, cancellation, and malformed cursors.\n\nConstraints:\n- make rollback possible without deleting user data\n- stay compatible with the existing Core Data deployment\n- keep the work scoped to DovetailCoralUploadService and its direct tests\n\nThis repository spans game tooling, data pipelines, macOS; use its existing conventions rather than importing a new abstraction.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Vela: The data is already available in projects/dovetail/pkg/cache/lease.rs; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Parse DovetailHarborIndexStore's signed cursor","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Two deliverables are holding up DovetailWrenExportCoordinator. First, find the unknown cause of out-of-order events after consumer rebalancing. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/dovetail/app/src/main/SyncWorker.kt, which follows Playwright conventions and currently suffers from out-of-order events after consumer rebalancing. Make rollback possible without deleting user data.\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":"DovetailSpruceDaemonService returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/dovetail/web/components/FilterDrawer.vue and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Willow: Ticket OPS-44141: retire the legacy replay path for DovetailMicaProfileFlow\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 DovetailMicaProfileFlow 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":"// projects/dovetail/infra/modules/edge/main.tf\nfinal class DovetailFlintTimelineFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 DovetailFlintTimelineFlow; 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":"DovetailWillowCodecCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"PM is preparing the DovetailIrisBatchService rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside DovetailIrisBatchService\n- make rollback possible without deleting user data\n\nThe relevant code crosses game tooling, data pipelines, macOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Split DovetailJuniperCLIStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-44154\n\n08:02 deploy DovetailMarbleTokenCoordinator 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 DovetailMarbleTokenCoordinator, 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":"DovetailSlateEditorCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"A copied hex color in DovetailEmberRelayService lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"DovetailTideWorkerCoordinator needs a paired pass: assess ownership and failure handling in projects/dovetail/workers/thumbnail/consumer.ex, plus capture the contract and rollback note for consumers. Use projects/dovetail/workers/thumbnail/consumer.ex as the source of truth, preserve the Terraform contract, and avoid unrelated cleanup.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Xylem: # projects/dovetail/cmd/exporter/main.py\n[worker.dovetailslateeditorflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetailslateeditorflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetailslateeditorflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailSlateEditorFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44117\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/dovetail/cmd/exporter/main.py and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Yarrow: Two asks around DovetailNovaPickerCoordinator: (1) lay out a staged migration for DovetailNovaPickerCoordinator; (2) also add the visible loading and offline states. Make rollback possible without deleting user data, and leave a clear boundary between the resulting artifacts or edits.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"In projects/dovetail/packages/api/openapi.yaml hat DovetailBeaconStoreService 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 DovetailBeaconStoreService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um DovetailBeaconStoreService mit React 19 kompatibel.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"de"} +{"prompt":"DovetailFrostPanelCoordinator: correct, then assess","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Outline a safer DovetailCedarPolicyStore cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-44150\n\n08:02 deploy DovetailDriftConsoleCoordinator 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 DovetailDriftConsoleCoordinator 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":"Fresh release brief for DovetailBeaconStoreCoordinator:\n- primary outcome: separate DovetailBeaconStoreCoordinator's policy from transport without behavior changes\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/dovetail/config/staging.toml\n- platform constraint: React 19\n- known complication: a feature flag whose default differs between environments\n\nBoth results are required, but they should remain independently reviewable. Make rollback possible without deleting user data; 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":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"thread 'tokio-runtime-worker' panicked at projects/dovetail/pkg/cache/lease.rs:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: dovetailbasilrunnerflow::scheduler::LeaseTask::flush\n at ./projects/dovetail/pkg/cache/lease.rs:217:18\n 4: dovetailbasilrunnerflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nFind the source of this DovetailBasilRunnerFlow symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Describe DovetailJuniperCLIService's error envelope","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"The DovetailEchoRegistryService empty state in projects/dovetail/ui/settings/PrivacyPane.tsx needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Zephyr: projects/dovetail/internal/auth/refresh.go now contains DovetailFlintTimelineStore'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":"DovetailRainfallDBCoordinator: restructure, then document","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Release verification found a single stale DovetailOrbitSyncService value; the cause, desired value, and affected assertion are already agreed. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Redis Streams operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.25,"slice":"core","lang":"en"} -{"prompt":"Flip DovetailNovaPickerStore's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"boundary","lang":"en"} -{"prompt":"Please resist widening this one: DovetailCoralUploadStore works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside DovetailCoralUploadStore\n- make rollback possible without deleting user data\n\nThe relevant code crosses game tooling, data pipelines, macOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"DovetailRavenSessionCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"vague-eval","lang":"en"} -{"prompt":"Lay out a two-milestone strategy for eliminating two validators with subtly different error strings in DovetailCinderAuthStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Flip DovetailPrismCacheService's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"core","lang":"en"} -{"prompt":"DovetailEchoRegistryCoordinator: make this less weird","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"Lay out a two-milestone strategy for eliminating two validators with subtly different error strings in DovetailBirchMigratorService, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Add a bounded DovetailBirchMigratorStore export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Test Suite 'DovetailSummitProxyCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[DovetailSummitProxyCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/dovetail/services/ledger/replay.go:144: error: -[DovetailSummitProxyCoordinatorTests 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 '-[DovetailSummitProxyCoordinatorTests 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 DovetailSummitProxyCoordinator'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.68,"slice":"pasted-context","lang":"en"} -{"prompt":"How should DovetailQuartzPlayerService be decomposed?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Ticket OPS-44123: retire the legacy replay path for DovetailRainfallDBFlow\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 DovetailRainfallDBFlow 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.65,"slice":"pasted-context","lang":"en"} -{"prompt":"Checkout: A flaky failure around DovetailAmberFilterStore survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside DovetailAmberFilterStore\n- make rollback possible without deleting user data\n\nThe relevant code crosses game tooling, data pipelines, macOS. Prefer evidence from the repository and make any assumption explicit.\n\nA real symptom is present, so follow evidence to a cause rather than stopping at a walkthrough.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.89,"slice":"boundary","lang":"en"} -{"prompt":"Exporter: Ticket OPS-44151: retire the legacy replay path for DovetailMapleQueueCoordinator\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 DovetailMapleQueueCoordinator rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"Design handed over a final pass for DovetailWrenExportStore, and the basic data flow in projects/dovetail/app/src/main/SyncWorker.kt already works. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- make rollback possible without deleting user data\n- stay compatible with the existing Playwright deployment\n- keep the work scoped to DovetailWrenExportStore and its direct tests\n\nThis repository spans game tooling, data pipelines, macOS; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"boundary","lang":"en"} -{"prompt":"Queue DovetailOpalRouterStore's expired sessions","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"# projects/dovetail/src/sync/reconcile.ts\n[worker.dovetailirisbatchcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetailirisbatchcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetailirisbatchcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailIrisBatchCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44158\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/dovetail/src/sync/reconcile.ts. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.41,"slice":"pasted-context","lang":"en"} -{"prompt":"PM needs a concise migration note for DovetailIrisBatchFlow, including the user impact, rollback trigger, and the one configuration key operators must change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"boundary","lang":"en"} -{"prompt":"Give DovetailEchoRegistryStore'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.54,"slice":"boundary","lang":"en"} -{"prompt":"Scheduler: // projects/dovetail/Sources/App/SessionStore.swift\nfinal class DovetailCoralUploadFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 DovetailCoralUploadFlow'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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Please resist widening this one: DovetailQuartzPlayerStore works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside DovetailQuartzPlayerStore\n- make rollback possible without deleting user data\n\nThe relevant code crosses game tooling, data pipelines, macOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.25,"slice":"boundary","lang":"en"} -{"prompt":"Memory attributed to DovetailDriftConsoleFlow rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"En projects/dovetail/app/src/main/SyncWorker.kt, DovetailVelaDrawerService tiene un problema intermitente en el flujo de Playwright. Separa responsabilidades y elimina duplicación, conservando API, wire values, orden y comportamiento observable.\n\nRestricciones:\n- seguir con Playwright\n- conservar compatibilidad y cancelación\n- limitar el cambio a DovetailVelaDrawerService Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con Playwright alrededor de DovetailVelaDrawerService.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"es"} -{"prompt":"Bring DovetailVelaDrawerStore'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.52,"slice":"core","lang":"en"} -{"prompt":"Three teams extended DovetailMapleQueueService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current React 19 operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Extract DovetailFrostPanelService's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"DovetailMoonlitSDKCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} +{"prompt":"Release verification found a single stale DovetailOrbitSyncService value; the cause, desired value, and affected assertion are already agreed. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Redis Streams operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Flip DovetailNovaPickerStore's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Please resist widening this one: DovetailCoralUploadStore works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside DovetailCoralUploadStore\n- make rollback possible without deleting user data\n\nThe relevant code crosses game tooling, data pipelines, macOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"DovetailRavenSessionCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating two validators with subtly different error strings in DovetailCinderAuthStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Flip DovetailPrismCacheService's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"DovetailEchoRegistryCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating two validators with subtly different error strings in DovetailBirchMigratorService, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add a bounded DovetailBirchMigratorStore export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'DovetailSummitProxyCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[DovetailSummitProxyCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/dovetail/services/ledger/replay.go:144: error: -[DovetailSummitProxyCoordinatorTests 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 '-[DovetailSummitProxyCoordinatorTests 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 DovetailSummitProxyCoordinator's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"How should DovetailQuartzPlayerService be decomposed?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"Ticket OPS-44123: retire the legacy replay path for DovetailRainfallDBFlow\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 DovetailRainfallDBFlow 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":"Checkout: A flaky failure around DovetailAmberFilterStore survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside DovetailAmberFilterStore\n- make rollback possible without deleting user data\n\nThe relevant code crosses game tooling, data pipelines, macOS. Prefer evidence from the repository and make any assumption explicit.\n\nA real symptom is present, so follow evidence to a cause rather than stopping at a walkthrough.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Exporter: Ticket OPS-44151: retire the legacy replay path for DovetailMapleQueueCoordinator\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 DovetailMapleQueueCoordinator 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":"Design handed over a final pass for DovetailWrenExportStore, and the basic data flow in projects/dovetail/app/src/main/SyncWorker.kt already works. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- make rollback possible without deleting user data\n- stay compatible with the existing Playwright deployment\n- keep the work scoped to DovetailWrenExportStore and its direct tests\n\nThis repository spans game tooling, data pipelines, macOS; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Queue DovetailOpalRouterStore's expired sessions","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"# projects/dovetail/src/sync/reconcile.ts\n[worker.dovetailirisbatchcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetailirisbatchcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetailirisbatchcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailIrisBatchCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44158\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/dovetail/src/sync/reconcile.ts. 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":"PM needs a concise migration note for DovetailIrisBatchFlow, 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":"Give DovetailEchoRegistryStore'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.5,"slice":"core","lang":"en"} +{"prompt":"Scheduler: // projects/dovetail/Sources/App/SessionStore.swift\nfinal class DovetailCoralUploadFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 DovetailCoralUploadFlow'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":"Please resist widening this one: DovetailQuartzPlayerStore works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside DovetailQuartzPlayerStore\n- make rollback possible without deleting user data\n\nThe relevant code crosses game tooling, data pipelines, macOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Memory attributed to DovetailDriftConsoleFlow rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"En projects/dovetail/app/src/main/SyncWorker.kt, DovetailVelaDrawerService tiene un problema intermitente en el flujo de Playwright. Separa responsabilidades y elimina duplicación, conservando API, wire values, orden y comportamiento observable.\n\nRestricciones:\n- seguir con Playwright\n- conservar compatibilidad y cancelación\n- limitar el cambio a DovetailVelaDrawerService Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con Playwright alrededor de DovetailVelaDrawerService.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"es"} +{"prompt":"Bring DovetailVelaDrawerStore'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.5,"slice":"core","lang":"en"} +{"prompt":"Three teams extended DovetailMapleQueueService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current React 19 operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Extract DovetailFrostPanelService's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"DovetailMoonlitSDKCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"Dashboard: projects/dovetail/app/src/main/SyncWorker.kt の DovetailLumenChartService で、Playwright の flow に断続的な問題が起きています。 段階、互換性、metrics、rollback、ownership を提案し、コード変更の前で止めてください。\n\n制約:\n- Playwright を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は DovetailLumenChartService のみ","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"} -{"prompt":"DovetailOspreyJobCoordinator needs a paired pass: finish DovetailOspreyJobCoordinator's responsive empty and retry states, plus give the existing implementation a read-only safety pass. Use projects/dovetail/Sources/CLI/Commands/Doctor.swift as the source of truth, preserve the Core Data contract, and avoid unrelated cleanup.","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.59,"slice":"mixed","lang":"en"} -{"prompt":"Two deliverables are holding up DovetailOrbitSyncCoordinator. First, find the unknown cause of cancellation being swallowed at the repository boundary. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/dovetail/infra/modules/edge/main.tf, which follows Redis Streams conventions and currently suffers from cancellation being swallowed at the repository boundary. Make rollback possible without deleting user data.\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.89,"slice":"mixed","lang":"en"} -{"prompt":"For DovetailHarborIndexCoordinator, assess ownership and failure handling in projects/dovetail/lib/codec/frame.cc; once that is complete, capture the contract and rollback note for consumers. Work from projects/dovetail/lib/codec/frame.cc, stay with Terraform, and make rollback possible without deleting user data. Keep the two outcomes separately reviewable.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Worker: Incident timeline — INC-44144\n\n08:02 deploy DovetailBirchMigratorFlow 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 DovetailBirchMigratorFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"Where did DovetailOspreyJobStore's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"boundary","lang":"en"} -{"prompt":"For DovetailCloudReconcilerCoordinator, separate DovetailCloudReconcilerCoordinator's policy from transport without behavior changes; once that is complete, correct the known stale timeout beside it. Work from projects/dovetail/cmd/exporter/main.py, stay with Core Data, and make rollback possible without deleting user data. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"I inherited DovetailFrostPanelStore and need a careful read of projects/dovetail/pkg/cache/lease.rs before I can sign off on the next release. 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- make rollback possible without deleting user data\n- stay compatible with the existing React 19 deployment\n- keep the work scoped to DovetailFrostPanelStore and its direct tests\n\nThis repository spans game tooling, data pipelines, macOS; use its existing conventions rather than importing a new abstraction.\n\nNothing is reported broken, so judge and explain current behavior without inventing a failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.69,"slice":"boundary","lang":"en"} -{"prompt":"Read projects/dovetail/db/migrations/20260730_events.sql and tell me whether DovetailWillowCodecService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Ticket OPS-44131: retire the legacy replay path for DovetailNovaPickerFlow\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 DovetailNovaPickerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.59,"slice":"pasted-context","lang":"en"} -{"prompt":"# projects/dovetail/ml/pipeline/features.py\n[worker.dovetailcloudreconcilerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetailcloudreconcilerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetailcloudreconcilerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailCloudReconcilerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44127\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 DovetailCloudReconcilerFlow'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.38,"slice":"pasted-context","lang":"en"} -{"prompt":"Test Suite 'DovetailLedgerGateFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[DovetailLedgerGateFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/dovetail/workers/thumbnail/consumer.ex:144: error: -[DovetailLedgerGateFlowTests 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 '-[DovetailLedgerGateFlowTests 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\nFind the source of this DovetailLedgerGateFlow 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.96,"slice":"pasted-context","lang":"en"} -{"prompt":"Simulator: Test Suite 'DovetailAmberFilterCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[DovetailAmberFilterCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/dovetail/workers/thumbnail/consumer.ex:144: error: -[DovetailAmberFilterCoordinatorTests 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 '-[DovetailAmberFilterCoordinatorTests 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\nFinish the visible DovetailAmberFilterCoordinator 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.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Summarize the DovetailRainfallDBService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"Runbook: Test Suite 'DovetailVelaDrawerCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[DovetailVelaDrawerCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/dovetail/apps/console/routes/usage.svelte:144: error: -[DovetailVelaDrawerCoordinatorTests 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 '-[DovetailVelaDrawerCoordinatorTests 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 を維持し、根拠と判断を明確にしてください。 Finish the visible DovetailVelaDrawerCoordinator 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.76,"slice":"pasted-context","lang":"ja"} -{"prompt":"Is there a cleaner way to separate DovetailEmberRelayStore'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.58,"slice":"boundary","lang":"en"} -{"prompt":"Style DovetailCopperBridgeService's offline state","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"Security flagged DovetailIrisBatchStore for a read-only pass because its Playwright boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Playwright operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS monorepo, so keep ownership and handoff points understandable in a small review.\n\nNothing is reported broken, so judge and explain current behavior without inventing a failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"boundary","lang":"en"} -{"prompt":"Two asks around DovetailCraneWorkspaceCoordinator: (1) produce a consumer guide for DovetailCraneWorkspaceCoordinator; (2) correct the known stale timeout beside it. Make rollback possible without deleting user data, and leave a clear boundary between the resulting artifacts or edits.","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.51,"slice":"mixed","lang":"en"} -{"prompt":"The destination for DovetailKiteSchedulerService is broadly agreed; the missing piece is a reversible route from projects/dovetail/Sources/CLI/Commands/Doctor.swift to that target. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside DovetailKiteSchedulerService\n- make rollback possible without deleting user data\n\nThe relevant code crosses game tooling, data pipelines, macOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.83,"slice":"core","lang":"en"} -{"prompt":"Support wants the behavior in projects/dovetail/ml/pipeline/features.py recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"en"} -{"prompt":"What sequence would let DovetailMicaProfileService adopt React 19 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.65,"slice":"core","lang":"en"} -{"prompt":"Production says DovetailAcornWidgetStore is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Reconstruct the failing timeline from logs and tests, identify which invariant first breaks, and distinguish causal signals from effects or cleanup noise.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Terraform operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS monorepo, so keep ownership and handoff points understandable in a small review.\n\nA real symptom is present, so follow evidence to a cause rather than stopping at a walkthrough.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.89,"slice":"boundary","lang":"en"} -{"prompt":"DovetailNimbusFormCoordinator: untangle the messy bit","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"vague-eval","lang":"en"} -{"prompt":"Trace: projects/dovetail/config/staging.toml の DovetailMapleQueueFlow で、React 19 の flow に断続的な問題が起きています。 現在の flow を読み、ownership、cancel、順序が安全か評価してください。分析だけで十分です。\n\n制約:\n- React 19 を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は DovetailMapleQueueFlow のみ","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"ja"} -{"prompt":"Move DovetailMapleQueueStore'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.55,"slice":"core","lang":"en"} -{"prompt":"Compare the old and new DovetailAtlasSearchFlow adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Please resist widening this one: DovetailSummitProxyService works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside DovetailSummitProxyService\n- make rollback possible without deleting user data\n\nThe relevant code crosses game tooling, data pipelines, macOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.25,"slice":"core","lang":"en"} -{"prompt":"Diff: projects/dovetail/services/ledger/replay.go 里的 DovetailDeltaCanvasService 最近在 Redis Streams 流程中出现间歇性问题。 请拆分职责并去掉重复，同时保持 API、wire value、顺序和可观察行为不变。\n\n约束：\n- 继续使用 Redis Streams\n- 保持兼容性和取消语义\n- 改动只限于 DovetailDeltaCanvasService","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"zh"} -{"prompt":"Profiler: projects/dovetail/infra/modules/edge/main.tf has grown through several launches, and DovetailOrbitSyncStore now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- make rollback possible without deleting user data\n- stay compatible with the existing Redis Streams deployment\n- keep the work scoped to DovetailOrbitSyncStore and its direct tests\n\nThis repository spans game tooling, data pipelines, macOS; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.69,"slice":"boundary","lang":"en"} -{"prompt":"Where did DovetailAsterWebhookService's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Compare DovetailCraneWorkspaceService's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"How should DovetailNovaPickerService be decomposed?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"UI ticket DES-44124: finish the compact DovetailHarborIndexFlow filter experience\n\nRoute: /catalog/search\nSource: projects/dovetail/engine/render/atlas.cpp\nFramework: Terraform\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 DovetailHarborIndexFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"2026-07-30T08:14:11.409Z level=info service=dovetailsprucedaemonflow pod=dovetailsprucedaemonflow-7cf8 request_id=44145 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=dovetailsprucedaemonflow request_id=44145 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=dovetailsprucedaemonflow request_id=44145 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=dovetailsprucedaemonflow request_id=44145 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=dovetailsprucedaemonflow request_id=44145 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=dovetailsprucedaemonflow request_id=44145 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=dovetailsprucedaemonflow request_id=44145 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=dovetailsprucedaemonflow request_id=44145 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Reconstruct the DovetailSpruceDaemonFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.87,"slice":"pasted-context","lang":"zh"} -{"prompt":"The data is already available in projects/dovetail/db/migrations/20260730_events.sql; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} -{"prompt":"Collapse the DovetailFernSnapshotService wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Console: The name pendingAck means two different things across DovetailMarbleTokenFlow's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Split projects/dovetail/ui/settings/PrivacyPane.tsx by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Read projects/dovetail/crates/index/src/segment.rs and tell me whether DovetailGarnetModalService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Map DovetailRainfallDBStore's ownership split","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"projects/dovetail/crates/index/src/segment.rs now contains DovetailBasilRunnerStore'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.55,"slice":"boundary","lang":"en"} -{"prompt":"Could DovetailMosaicGridStore show the active React 19 sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"diff --git a/projects/dovetail/services/ledger/replay.go b/projects/dovetail/services/ledger/replay.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/dovetail/services/ledger/replay.go\n+++ b/projects/dovetail/services/ledger/replay.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate DovetailQuartzPlayerFlow'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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Split projects/dovetail/services/ledger/replay.go by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"DovetailSableParserCoordinator: handle the lingering thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"vague-eval","lang":"en"} -{"prompt":"DovetailCinderAuthCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"vague-eval","lang":"en"} -{"prompt":"Incident timeline — INC-44130\n\n08:02 deploy DovetailOpalRouterFlow 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 DovetailOpalRouterFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"pasted-context","lang":"en"} -{"prompt":"Could DovetailAsterWebhookStore migrate incrementally?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"Polish the DovetailCopperBridgeStore toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"boundary","lang":"en"} -{"prompt":"DovetailLumenChartCoordinator: the docs need something","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"vague-eval","lang":"en"} -{"prompt":"On compact widths, DovetailSableParserStore'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.54,"slice":"boundary","lang":"en"} -{"prompt":"Workspace: Split DovetailCedarPolicyService without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"thread 'tokio-runtime-worker' panicked at projects/dovetail/workers/thumbnail/consumer.ex:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: dovetailravensessionflow::scheduler::LeaseTask::flush\n at ./projects/dovetail/workers/thumbnail/consumer.ex:217:18\n 4: dovetailravensessionflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nReconstruct the DovetailRavenSessionFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"Extract DovetailHarborIndexService's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Repository: // projects/dovetail/config/staging.toml\nfinal class DovetailPineMetricsFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Wire DovetailPineMetricsFlow'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.83,"slice":"pasted-context","lang":"de"} -{"prompt":"Release verification found a single stale DovetailAtlasSearchService value; the cause, desired value, and affected assertion are already agreed. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Core Data operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Unifie les validateurs de DovetailCloudReconcilerStore","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"fr"} -{"prompt":"DovetailAsterWebhookCoordinator needs a paired pass: produce a consumer guide for DovetailAsterWebhookCoordinator, plus give the existing implementation a read-only safety pass. Use projects/dovetail/crates/index/src/segment.rs as the source of truth, preserve the React 19 contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.45,"slice":"mixed","lang":"en"} -{"prompt":"DovetailQuartzPlayerCoordinator is blocking the next release because a flaky snapshot caused by locale-dependent sorting. I need two concrete outcomes from a single pass: finish DovetailQuartzPlayerCoordinator's responsive empty and retry states, and capture the contract and rollback note for consumers. Use the existing Redis Streams conventions in projects/dovetail/web/components/FilterDrawer.vue; make rollback possible without deleting user data. 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":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"DovetailDeltaCanvasCoordinator: could this be clearer","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"vague-eval","lang":"en"} -{"prompt":"Incident timeline — INC-44134\n\n08:02 deploy DovetailSableParserFlow 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 DovetailSableParserFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.67,"slice":"pasted-context","lang":"en"} -{"prompt":"Does DovetailSlateEditorService preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"# projects/dovetail/lib/codec/frame.cc\n[worker.dovetailacornwidgetflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetailacornwidgetflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetailacornwidgetflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailAcornWidgetFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44114\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/dovetail/lib/codec/frame.cc and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.43,"slice":"pasted-context","lang":"en"} -{"prompt":"DovetailBasilRunnerCoordinator: check the suspicious part","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"vague-eval","lang":"en"} -{"prompt":"DovetailBirchMigratorCoordinator: rethink this area","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"Before we approve DovetailGarnetModalStore, assess whether lost focus when the drawer animation finishes is an actual correctness risk or merely confusing structure. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"Our support and SDK teams keep answering the same questions about DovetailMosaicGridService, but the current prose in projects/dovetail/pkg/cache/lease.rs only describes the happy path. 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- make rollback possible without deleting user data\n- stay compatible with the existing React 19 deployment\n- keep the work scoped to DovetailMosaicGridService and its direct tests\n\nThis repository spans game tooling, data pipelines, macOS; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} -{"prompt":"DovetailLedgerGateCoordinator: polish, then correct","purpose":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.64,"slice":"mixed","lang":"en"} -{"prompt":"Is there a cleaner way to separate DovetailMicaProfileStore'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.55,"slice":"boundary","lang":"en"} -{"prompt":"Pipeline: diff --git a/projects/dovetail/cmd/exporter/main.py b/projects/dovetail/cmd/exporter/main.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/dovetail/cmd/exporter/main.py\n+++ b/projects/dovetail/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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Add the bounded DovetailMoonlitSDKFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"pt"} -{"prompt":"This should remain a deliberately small patch: DovetailDriftConsoleService has one known configuration mistake in projects/dovetail/infra/modules/edge/main.tf, not an open-ended failure investigation. 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- make rollback possible without deleting user data\n- stay compatible with the existing Redis Streams deployment\n- keep the work scoped to DovetailDriftConsoleService and its direct tests\n\nThis repository spans game tooling, data pipelines, macOS; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.25,"slice":"core","lang":"en"} -{"prompt":"For DovetailOpalRouterCoordinator, change DovetailOpalRouterCoordinator's known staging timeout from 15 to 30 seconds; once that is complete, capture the contract and rollback note for consumers. Work from projects/dovetail/infra/modules/edge/main.tf, stay with Redis Streams, and make rollback possible without deleting user data. Keep the two outcomes separately reviewable.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.19,"slice":"mixed","lang":"en"} -{"prompt":"Gateway: projects/dovetail/lib/codec/frame.cc now contains DovetailMarbleTokenStore'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.63,"slice":"core","lang":"en"} -{"prompt":"DovetailGarnetModalCoordinator: take care of the warning","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"vague-eval","lang":"en"} -{"prompt":"Renderer: # projects/dovetail/Sources/CLI/Commands/Doctor.swift\n[worker.dovetailcinderauthflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetailcinderauthflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetailcinderauthflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailCinderAuthFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44142\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 DovetailCinderAuthFlow'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.38,"slice":"pasted-context","lang":"en"} -{"prompt":"Indexer: Split DovetailOpalRouterService without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Documente le contrat DovetailLedgerGateService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"fr"} -{"prompt":"diff --git a/projects/dovetail/Sources/App/SessionStore.swift b/projects/dovetail/Sources/App/SessionStore.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/dovetail/Sources/App/SessionStore.swift\n+++ b/projects/dovetail/Sources/App/SessionStore.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is DovetailOspreyJobFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Apparently: Incident timeline — INC-44157\n\n08:02 deploy DovetailAtlasSearchCoordinator 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nReconstruct the DovetailAtlasSearchCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.92,"slice":"pasted-context","lang":"en"} -{"prompt":"Lately: # projects/dovetail/services/ledger/replay.go\n[worker.dovetaildeltacanvasflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetaildeltacanvasflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetaildeltacanvasflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailDeltaCanvasFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44135\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/dovetail/services/ledger/replay.go and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"pasted-context","lang":"en"} -{"prompt":"The data is already available in projects/dovetail/Sources/App/SessionStore.swift; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"core","lang":"en"} -{"prompt":"Walk through DovetailCraneWorkspaceStore's reconcile.ts","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Trace DovetailAcornWidgetService's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Oddly: Incident timeline — INC-44110\n\n08:02 deploy DovetailOrbitSyncFlow 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 DovetailOrbitSyncFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"pasted-context","lang":"en"} -{"prompt":"Currently: // projects/dovetail/Sources/App/SessionStore.swift\nfinal class DovetailKiteSchedulerCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 DovetailKiteSchedulerCoordinator 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Sketch the DovetailPineMetricsService migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Drop DovetailPineMetricsStore's unused import","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"boundary","lang":"en"} -{"prompt":"Today: Incident timeline — INC-44120\n\n08:02 deploy DovetailJuniperCLIFlow 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 DovetailJuniperCLIFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Translate the DovetailPrismCacheStore setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"boundary","lang":"en"} -{"prompt":"Context: Incident timeline — INC-44122\n\n08:02 deploy DovetailCedarPolicyFlow 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 DovetailCedarPolicyFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.62,"slice":"pasted-context","lang":"en"} -{"prompt":"Two engineers disagree about whether DovetailAtlasSearchStore's cache is authoritative. Walk the reads and writes in projects/dovetail/cmd/exporter/main.py and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"We expect DovetailAmberFilterService to outgrow its current Terraform arrangement next quarter, but changing everything at once would be risky. 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- make rollback possible without deleting user data\n- stay compatible with the existing Terraform deployment\n- keep the work scoped to DovetailAmberFilterService and its direct tests\n\nThis repository spans game tooling, data pipelines, macOS; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"core","lang":"en"} -{"prompt":"DovetailEmberRelayCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"vague-eval","lang":"en"} -{"prompt":"Ist DovetailLedgerGateStore sicher?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"de"} -{"prompt":"Corrige le timeout de EquinoxBasilRunnerService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"core","lang":"fr"} -{"prompt":"// projects/equinox/cmd/exporter/main.py\nfinal class EquinoxDriftConsoleFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 EquinoxDriftConsoleFlow'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.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Ticket OPS-45111: retire the legacy replay path for EquinoxNimbusFormFlow\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 EquinoxNimbusFormFlow 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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"A copied hex color in EquinoxAcornWidgetStore lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"boundary","lang":"en"} -{"prompt":"Two deliverables are holding up EquinoxCinderAuthCoordinator. First, assess ownership and failure handling in projects/equinox/workers/thumbnail/consumer.ex. In the same workstream, capture the contract and rollback note for consumers. The relevant starting point is projects/equinox/workers/thumbnail/consumer.ex, which follows PostgreSQL 17 conventions and currently suffers from timestamps rendered one day ahead near UTC midnight. Preserve cancellation and back-pressure semantics.\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":"review","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Incident timeline — INC-45115\n\n08:02 deploy EquinoxCinderAuthFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current EquinoxCinderAuthFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Background: # projects/equinox/pkg/cache/lease.rs\n[worker.equinoxravensessionflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.equinoxravensessionflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.equinoxravensessionflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.EquinoxRavenSessionFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-45112\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/equinox/pkg/cache/lease.rs. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.38,"slice":"pasted-context","lang":"en"} -{"prompt":"EquinoxCedarPolicyCoordinator: clean up that old path","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"vague-eval","lang":"en"} -{"prompt":"Does EquinoxWrenExportStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"EquinoxBeaconStoreCoordinator: polish the last piece","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"vague-eval","lang":"en"} -{"prompt":"Question: Incident timeline — INC-45119\n\n08:02 deploy EquinoxBasilRunnerFlow 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 EquinoxBasilRunnerFlow 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.67,"slice":"pasted-context","lang":"en"} -{"prompt":"Design handed over a final pass for EquinoxCinderAuthStore, and the basic data flow in projects/equinox/workers/thumbnail/consumer.ex already works. 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- preserve cancellation and back-pressure semantics\n- stay compatible with the existing PostgreSQL 17 deployment\n- keep the work scoped to EquinoxCinderAuthStore and its direct tests\n\nSeveral teams work in this identity, Rust CLI, Vue monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"A flaky failure around EquinoxMoonlitSDKService survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxMoonlitSDKService\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Em projects/equinox/workers/thumbnail/consumer.ex, o EquinoxCoralUploadStore tem um problema intermitente no fluxo de PostgreSQL 17. Separe responsabilidades e remova duplicação sem mudar API, wire values, ordem ou comportamento observável.\n\nRestrições:\n- continuar com PostgreSQL 17\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao EquinoxCoralUploadStore","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"pt"} -{"prompt":"Please resist widening this one: EquinoxCraneWorkspaceService works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxCraneWorkspaceService\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.28,"slice":"core","lang":"en"} -{"prompt":"Observation: Two deliverables are holding up EquinoxRavenSessionCoordinator. First, assess ownership and failure handling in projects/equinox/crates/index/src/segment.rs. In the same workstream, capture the contract and rollback note for consumers. The relevant starting point is projects/equinox/crates/index/src/segment.rs, which follows WebGPU conventions and currently suffers from an empty state that flashes before cached data arrives. Preserve cancellation and back-pressure semantics.\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":"review","secondary":"writing","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"EquinoxNovaPickerFlow 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.63,"slice":"boundary","lang":"en"} -{"prompt":"On compact widths, EquinoxSlateEditorService'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.44,"slice":"core","lang":"en"} -{"prompt":"Ticket OPS-45130: retire the legacy replay path for EquinoxAtlasSearchFlow\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 EquinoxAtlasSearchFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"pasted-context","lang":"en"} -{"prompt":"Extract EquinoxIrisBatchService's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Check EquinoxEmberRelayStore's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"projects/equinox/infra/modules/edge/main.tf now contains EquinoxPrismCacheFlow'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.55,"slice":"boundary","lang":"en"} -{"prompt":"Constraint: Ticket OPS-45144: retire the legacy replay path for EquinoxPineMetricsFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for EquinoxPineMetricsFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.67,"slice":"pasted-context","lang":"en"} -{"prompt":"Pin EquinoxDriftConsoleService's SQLite dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"core","lang":"en"} -{"prompt":"EquinoxFernSnapshotCoordinator: smooth out this interaction","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"vague-eval","lang":"en"} -{"prompt":"EquinoxEchoRegistryStore leaks tasks on shutdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"boundary","lang":"en"} -{"prompt":"Compare the old and new EquinoxCedarPolicyService 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":"$ pnpm test --filter EquinoxJuniperCLIFlow\n RUN v3.2.4 /workspace/apps/console\n × EquinoxJuniperCLIFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=45143 phase=resume storedCursor=seg-0183\n session=45143 phase=fetch requestCursor=seg-0183 pageSize=200\n session=45143 phase=commit receivedCursor=seg-0184 itemCount=0\n session=45143 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nDetermine why EquinoxJuniperCLIFlow 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.95,"slice":"pasted-context","lang":"en"} -{"prompt":"Ownership of EquinoxPrismCacheService is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current NATS JetStream operational envelope\n\nThe relevant code crosses identity, Rust CLI, Vue. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.81,"slice":"core","lang":"en"} -{"prompt":"EquinoxAcornWidgetCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"vague-eval","lang":"en"} -{"prompt":"EquinoxWillowCodecCoordinator: document, then correct","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.45,"slice":"mixed","lang":"en"} -{"prompt":"Request: projects/equinox/services/ledger/replay.go の EquinoxCraneWorkspaceFlow で、NATS JetStream の flow に断続的な問題が起きています。 consumer 向けに contract、error、retry、コピー可能な例を含む文書を書き、handler は変更しないでください。\n\n制約:\n- NATS JetStream を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は EquinoxCraneWorkspaceFlow のみ","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"ja"} -{"prompt":"Goal: A flaky failure around EquinoxBirchMigratorStore survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxBirchMigratorStore\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.84,"slice":"boundary","lang":"en"} -{"prompt":"Symptom: // projects/equinox/ml/pipeline/features.py\nfinal class EquinoxFlintTimelineFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Restructure EquinoxFlintTimelineFlow 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.84,"slice":"pasted-context","lang":"es"} -{"prompt":"EquinoxRainfallDBService's staging timeout is already known to be wrong: change the single projects/equinox/infra/modules/edge/main.tf value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"core","lang":"en"} +{"prompt":"DovetailOspreyJobCoordinator needs a paired pass: finish DovetailOspreyJobCoordinator's responsive empty and retry states, plus give the existing implementation a read-only safety pass. Use projects/dovetail/Sources/CLI/Commands/Doctor.swift as the source of truth, preserve the Core Data contract, and avoid unrelated cleanup.","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Two deliverables are holding up DovetailOrbitSyncCoordinator. First, find the unknown cause of cancellation being swallowed at the repository boundary. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/dovetail/infra/modules/edge/main.tf, which follows Redis Streams conventions and currently suffers from cancellation being swallowed at the repository boundary. Make rollback possible without deleting user data.\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":"For DovetailHarborIndexCoordinator, assess ownership and failure handling in projects/dovetail/lib/codec/frame.cc; once that is complete, capture the contract and rollback note for consumers. Work from projects/dovetail/lib/codec/frame.cc, stay with Terraform, and make rollback possible without deleting user data. Keep the two outcomes separately reviewable.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Worker: Incident timeline — INC-44144\n\n08:02 deploy DovetailBirchMigratorFlow 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 DovetailBirchMigratorFlow 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":"Where did DovetailOspreyJobStore's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"For DovetailCloudReconcilerCoordinator, separate DovetailCloudReconcilerCoordinator's policy from transport without behavior changes; once that is complete, correct the known stale timeout beside it. Work from projects/dovetail/cmd/exporter/main.py, stay with Core Data, and make rollback possible without deleting user data. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"I inherited DovetailFrostPanelStore and need a careful read of projects/dovetail/pkg/cache/lease.rs before I can sign off on the next release. 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- make rollback possible without deleting user data\n- stay compatible with the existing React 19 deployment\n- keep the work scoped to DovetailFrostPanelStore and its direct tests\n\nThis repository spans game tooling, data pipelines, macOS; use its existing conventions rather than importing a new abstraction.\n\nNothing is reported broken, so judge and explain current behavior without inventing a failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Read projects/dovetail/db/migrations/20260730_events.sql and tell me whether DovetailWillowCodecService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-44131: retire the legacy replay path for DovetailNovaPickerFlow\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 DovetailNovaPickerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"# projects/dovetail/ml/pipeline/features.py\n[worker.dovetailcloudreconcilerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetailcloudreconcilerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetailcloudreconcilerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailCloudReconcilerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44127\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 DovetailCloudReconcilerFlow'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":"Test Suite 'DovetailLedgerGateFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[DovetailLedgerGateFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/dovetail/workers/thumbnail/consumer.ex:144: error: -[DovetailLedgerGateFlowTests 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 '-[DovetailLedgerGateFlowTests 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\nFind the source of this DovetailLedgerGateFlow 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":"Simulator: Test Suite 'DovetailAmberFilterCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[DovetailAmberFilterCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/dovetail/workers/thumbnail/consumer.ex:144: error: -[DovetailAmberFilterCoordinatorTests 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 '-[DovetailAmberFilterCoordinatorTests 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\nFinish the visible DovetailAmberFilterCoordinator 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Summarize the DovetailRainfallDBService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Runbook: Test Suite 'DovetailVelaDrawerCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[DovetailVelaDrawerCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/dovetail/apps/console/routes/usage.svelte:144: error: -[DovetailVelaDrawerCoordinatorTests 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 '-[DovetailVelaDrawerCoordinatorTests 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 を維持し、根拠と判断を明確にしてください。 Finish the visible DovetailVelaDrawerCoordinator 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":"Is there a cleaner way to separate DovetailEmberRelayStore'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":"Style DovetailCopperBridgeService's offline state","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Security flagged DovetailIrisBatchStore for a read-only pass because its Playwright boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Playwright operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS monorepo, so keep ownership and handoff points understandable in a small review.\n\nNothing is reported broken, so judge and explain current behavior without inventing a failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Two asks around DovetailCraneWorkspaceCoordinator: (1) produce a consumer guide for DovetailCraneWorkspaceCoordinator; (2) correct the known stale timeout beside it. Make rollback possible without deleting user data, and leave a clear boundary between the resulting artifacts or edits.","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"The destination for DovetailKiteSchedulerService is broadly agreed; the missing piece is a reversible route from projects/dovetail/Sources/CLI/Commands/Doctor.swift to that target. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside DovetailKiteSchedulerService\n- make rollback possible without deleting user data\n\nThe relevant code crosses game tooling, data pipelines, macOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Support wants the behavior in projects/dovetail/ml/pipeline/features.py recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"What sequence would let DovetailMicaProfileService adopt React 19 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":"Production says DovetailAcornWidgetStore is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Reconstruct the failing timeline from logs and tests, identify which invariant first breaks, and distinguish causal signals from effects or cleanup noise.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Terraform operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS monorepo, so keep ownership and handoff points understandable in a small review.\n\nA real symptom is present, so follow evidence to a cause rather than stopping at a walkthrough.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"DovetailNimbusFormCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Trace: projects/dovetail/config/staging.toml の DovetailMapleQueueFlow で、React 19 の flow に断続的な問題が起きています。 現在の flow を読み、ownership、cancel、順序が安全か評価してください。分析だけで十分です。\n\n制約:\n- React 19 を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は DovetailMapleQueueFlow のみ","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"ja"} +{"prompt":"Move DovetailMapleQueueStore'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":"Compare the old and new DovetailAtlasSearchFlow adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Please resist widening this one: DovetailSummitProxyService works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside DovetailSummitProxyService\n- make rollback possible without deleting user data\n\nThe relevant code crosses game tooling, data pipelines, macOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Diff: projects/dovetail/services/ledger/replay.go 里的 DovetailDeltaCanvasService 最近在 Redis Streams 流程中出现间歇性问题。 请拆分职责并去掉重复，同时保持 API、wire value、顺序和可观察行为不变。\n\n约束：\n- 继续使用 Redis Streams\n- 保持兼容性和取消语义\n- 改动只限于 DovetailDeltaCanvasService","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"Profiler: projects/dovetail/infra/modules/edge/main.tf has grown through several launches, and DovetailOrbitSyncStore now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- make rollback possible without deleting user data\n- stay compatible with the existing Redis Streams deployment\n- keep the work scoped to DovetailOrbitSyncStore and its direct tests\n\nThis repository spans game tooling, data pipelines, macOS; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Where did DovetailAsterWebhookService's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Compare DovetailCraneWorkspaceService's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"How should DovetailNovaPickerService be decomposed?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-44124: finish the compact DovetailHarborIndexFlow filter experience\n\nRoute: /catalog/search\nSource: projects/dovetail/engine/render/atlas.cpp\nFramework: Terraform\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 DovetailHarborIndexFlow'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":"2026-07-30T08:14:11.409Z level=info service=dovetailsprucedaemonflow pod=dovetailsprucedaemonflow-7cf8 request_id=44145 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=dovetailsprucedaemonflow request_id=44145 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=dovetailsprucedaemonflow request_id=44145 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=dovetailsprucedaemonflow request_id=44145 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=dovetailsprucedaemonflow request_id=44145 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=dovetailsprucedaemonflow request_id=44145 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=dovetailsprucedaemonflow request_id=44145 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=dovetailsprucedaemonflow request_id=44145 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Reconstruct the DovetailSpruceDaemonFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"The data is already available in projects/dovetail/db/migrations/20260730_events.sql; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Collapse the DovetailFernSnapshotService wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Console: The name pendingAck means two different things across DovetailMarbleTokenFlow's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Split projects/dovetail/ui/settings/PrivacyPane.tsx by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Read projects/dovetail/crates/index/src/segment.rs and tell me whether DovetailGarnetModalService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Map DovetailRainfallDBStore's ownership split","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"projects/dovetail/crates/index/src/segment.rs now contains DovetailBasilRunnerStore'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":"Could DovetailMosaicGridStore show the active React 19 sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/dovetail/services/ledger/replay.go b/projects/dovetail/services/ledger/replay.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/dovetail/services/ledger/replay.go\n+++ b/projects/dovetail/services/ledger/replay.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate DovetailQuartzPlayerFlow'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":"Split projects/dovetail/services/ledger/replay.go by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"DovetailSableParserCoordinator: handle the lingering thing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"DovetailCinderAuthCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-44130\n\n08:02 deploy DovetailOpalRouterFlow 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 DovetailOpalRouterFlow, 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":"Could DovetailAsterWebhookStore migrate incrementally?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} +{"prompt":"Polish the DovetailCopperBridgeStore toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"DovetailLumenChartCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"On compact widths, DovetailSableParserStore'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":"Workspace: Split DovetailCedarPolicyService without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"thread 'tokio-runtime-worker' panicked at projects/dovetail/workers/thumbnail/consumer.ex:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: dovetailravensessionflow::scheduler::LeaseTask::flush\n at ./projects/dovetail/workers/thumbnail/consumer.ex:217:18\n 4: dovetailravensessionflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nReconstruct the DovetailRavenSessionFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Extract DovetailHarborIndexService's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Repository: // projects/dovetail/config/staging.toml\nfinal class DovetailPineMetricsFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Wire DovetailPineMetricsFlow'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":"Release verification found a single stale DovetailAtlasSearchService value; the cause, desired value, and affected assertion are already agreed. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Core Data operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Unifie les validateurs de DovetailCloudReconcilerStore","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"fr"} +{"prompt":"DovetailAsterWebhookCoordinator needs a paired pass: produce a consumer guide for DovetailAsterWebhookCoordinator, plus give the existing implementation a read-only safety pass. Use projects/dovetail/crates/index/src/segment.rs as the source of truth, preserve the React 19 contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"DovetailQuartzPlayerCoordinator is blocking the next release because a flaky snapshot caused by locale-dependent sorting. I need two concrete outcomes from a single pass: finish DovetailQuartzPlayerCoordinator's responsive empty and retry states, and capture the contract and rollback note for consumers. Use the existing Redis Streams conventions in projects/dovetail/web/components/FilterDrawer.vue; make rollback possible without deleting user data. 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":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"DovetailDeltaCanvasCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-44134\n\n08:02 deploy DovetailSableParserFlow 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 DovetailSableParserFlow 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":"Does DovetailSlateEditorService preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"# projects/dovetail/lib/codec/frame.cc\n[worker.dovetailacornwidgetflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetailacornwidgetflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetailacornwidgetflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailAcornWidgetFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44114\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/dovetail/lib/codec/frame.cc and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"DovetailBasilRunnerCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"DovetailBirchMigratorCoordinator: rethink this area","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Before we approve DovetailGarnetModalStore, assess whether lost focus when the drawer animation finishes is an actual correctness risk or merely confusing structure. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Our support and SDK teams keep answering the same questions about DovetailMosaicGridService, but the current prose in projects/dovetail/pkg/cache/lease.rs only describes the happy path. 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- make rollback possible without deleting user data\n- stay compatible with the existing React 19 deployment\n- keep the work scoped to DovetailMosaicGridService and its direct tests\n\nThis repository spans game tooling, data pipelines, macOS; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"DovetailLedgerGateCoordinator: polish, then correct","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Is there a cleaner way to separate DovetailMicaProfileStore'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":"Pipeline: diff --git a/projects/dovetail/cmd/exporter/main.py b/projects/dovetail/cmd/exporter/main.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/dovetail/cmd/exporter/main.py\n+++ b/projects/dovetail/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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Add the bounded DovetailMoonlitSDKFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"This should remain a deliberately small patch: DovetailDriftConsoleService has one known configuration mistake in projects/dovetail/infra/modules/edge/main.tf, not an open-ended failure investigation. 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- make rollback possible without deleting user data\n- stay compatible with the existing Redis Streams deployment\n- keep the work scoped to DovetailDriftConsoleService and its direct tests\n\nThis repository spans game tooling, data pipelines, macOS; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"For DovetailOpalRouterCoordinator, change DovetailOpalRouterCoordinator's known staging timeout from 15 to 30 seconds; once that is complete, capture the contract and rollback note for consumers. Work from projects/dovetail/infra/modules/edge/main.tf, stay with Redis Streams, and make rollback possible without deleting user data. Keep the two outcomes separately reviewable.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Gateway: projects/dovetail/lib/codec/frame.cc now contains DovetailMarbleTokenStore'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.4,"slice":"core","lang":"en"} +{"prompt":"DovetailGarnetModalCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Renderer: # projects/dovetail/Sources/CLI/Commands/Doctor.swift\n[worker.dovetailcinderauthflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetailcinderauthflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetailcinderauthflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailCinderAuthFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44142\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 DovetailCinderAuthFlow'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":"Indexer: Split DovetailOpalRouterService without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Documente le contrat DovetailLedgerGateService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"fr"} +{"prompt":"diff --git a/projects/dovetail/Sources/App/SessionStore.swift b/projects/dovetail/Sources/App/SessionStore.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/dovetail/Sources/App/SessionStore.swift\n+++ b/projects/dovetail/Sources/App/SessionStore.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is DovetailOspreyJobFlow'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":"Apparently: Incident timeline — INC-44157\n\n08:02 deploy DovetailAtlasSearchCoordinator 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nReconstruct the DovetailAtlasSearchCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Lately: # projects/dovetail/services/ledger/replay.go\n[worker.dovetaildeltacanvasflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetaildeltacanvasflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetaildeltacanvasflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailDeltaCanvasFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44135\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/dovetail/services/ledger/replay.go and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"The data is already available in projects/dovetail/Sources/App/SessionStore.swift; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Walk through DovetailCraneWorkspaceStore's reconcile.ts","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Trace DovetailAcornWidgetService's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Oddly: Incident timeline — INC-44110\n\n08:02 deploy DovetailOrbitSyncFlow 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 DovetailOrbitSyncFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Currently: // projects/dovetail/Sources/App/SessionStore.swift\nfinal class DovetailKiteSchedulerCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 DovetailKiteSchedulerCoordinator 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":"Sketch the DovetailPineMetricsService migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Drop DovetailPineMetricsStore's unused import","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Today: Incident timeline — INC-44120\n\n08:02 deploy DovetailJuniperCLIFlow 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 DovetailJuniperCLIFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Translate the DovetailPrismCacheStore setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Context: Incident timeline — INC-44122\n\n08:02 deploy DovetailCedarPolicyFlow 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 DovetailCedarPolicyFlow 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":"Two engineers disagree about whether DovetailAtlasSearchStore's cache is authoritative. Walk the reads and writes in projects/dovetail/cmd/exporter/main.py and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"We expect DovetailAmberFilterService to outgrow its current Terraform arrangement next quarter, but changing everything at once would be risky. 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- make rollback possible without deleting user data\n- stay compatible with the existing Terraform deployment\n- keep the work scoped to DovetailAmberFilterService and its direct tests\n\nThis repository spans game tooling, data pipelines, macOS; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"DovetailEmberRelayCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Ist DovetailLedgerGateStore sicher?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"de"} +{"prompt":"Corrige le timeout de EquinoxBasilRunnerService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"fr"} +{"prompt":"// projects/equinox/cmd/exporter/main.py\nfinal class EquinoxDriftConsoleFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 EquinoxDriftConsoleFlow'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":"Ticket OPS-45111: retire the legacy replay path for EquinoxNimbusFormFlow\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 EquinoxNimbusFormFlow for durability, tenant isolation, races, and misleading observability. Separate blockers from questions and do not produce a patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"A copied hex color in EquinoxAcornWidgetStore lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Two deliverables are holding up EquinoxCinderAuthCoordinator. First, assess ownership and failure handling in projects/equinox/workers/thumbnail/consumer.ex. In the same workstream, capture the contract and rollback note for consumers. The relevant starting point is projects/equinox/workers/thumbnail/consumer.ex, which follows PostgreSQL 17 conventions and currently suffers from timestamps rendered one day ahead near UTC midnight. Preserve cancellation and back-pressure semantics.\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":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Incident timeline — INC-45115\n\n08:02 deploy EquinoxCinderAuthFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current EquinoxCinderAuthFlow 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":"Background: # projects/equinox/pkg/cache/lease.rs\n[worker.equinoxravensessionflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.equinoxravensessionflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.equinoxravensessionflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.EquinoxRavenSessionFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-45112\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/equinox/pkg/cache/lease.rs. 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":"EquinoxCedarPolicyCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Does EquinoxWrenExportStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"EquinoxBeaconStoreCoordinator: polish the last piece","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Question: Incident timeline — INC-45119\n\n08:02 deploy EquinoxBasilRunnerFlow 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 EquinoxBasilRunnerFlow release note and operator runbook section. State impact, detection, rollback, and the client-visible contract; do not modify code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} +{"prompt":"Design handed over a final pass for EquinoxCinderAuthStore, and the basic data flow in projects/equinox/workers/thumbnail/consumer.ex already works. 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- preserve cancellation and back-pressure semantics\n- stay compatible with the existing PostgreSQL 17 deployment\n- keep the work scoped to EquinoxCinderAuthStore and its direct tests\n\nSeveral teams work in this identity, Rust CLI, Vue 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":"A flaky failure around EquinoxMoonlitSDKService survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxMoonlitSDKService\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Em projects/equinox/workers/thumbnail/consumer.ex, o EquinoxCoralUploadStore tem um problema intermitente no fluxo de PostgreSQL 17. Separe responsabilidades e remova duplicação sem mudar API, wire values, ordem ou comportamento observável.\n\nRestrições:\n- continuar com PostgreSQL 17\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao EquinoxCoralUploadStore","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"pt"} +{"prompt":"Please resist widening this one: EquinoxCraneWorkspaceService works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxCraneWorkspaceService\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Observation: Two deliverables are holding up EquinoxRavenSessionCoordinator. First, assess ownership and failure handling in projects/equinox/crates/index/src/segment.rs. In the same workstream, capture the contract and rollback note for consumers. The relevant starting point is projects/equinox/crates/index/src/segment.rs, which follows WebGPU conventions and currently suffers from an empty state that flashes before cached data arrives. Preserve cancellation and back-pressure semantics.\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":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"EquinoxNovaPickerFlow 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.4,"slice":"core","lang":"en"} +{"prompt":"On compact widths, EquinoxSlateEditorService'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.4,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-45130: retire the legacy replay path for EquinoxAtlasSearchFlow\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 EquinoxAtlasSearchFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Extract EquinoxIrisBatchService's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Check EquinoxEmberRelayStore's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"projects/equinox/infra/modules/edge/main.tf now contains EquinoxPrismCacheFlow'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":"Constraint: Ticket OPS-45144: retire the legacy replay path for EquinoxPineMetricsFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for EquinoxPineMetricsFlow, 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":"Pin EquinoxDriftConsoleService's SQLite dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"EquinoxFernSnapshotCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"EquinoxEchoRegistryStore leaks tasks on shutdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"Compare the old and new EquinoxCedarPolicyService adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"$ pnpm test --filter EquinoxJuniperCLIFlow\n RUN v3.2.4 /workspace/apps/console\n × EquinoxJuniperCLIFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=45143 phase=resume storedCursor=seg-0183\n session=45143 phase=fetch requestCursor=seg-0183 pageSize=200\n session=45143 phase=commit receivedCursor=seg-0184 itemCount=0\n session=45143 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nDetermine why EquinoxJuniperCLIFlow 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":"Ownership of EquinoxPrismCacheService is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current NATS JetStream operational envelope\n\nThe relevant code crosses identity, Rust CLI, Vue. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"EquinoxAcornWidgetCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"EquinoxWillowCodecCoordinator: document, then correct","purpose":"writing","secondary":"debugging","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Request: projects/equinox/services/ledger/replay.go の EquinoxCraneWorkspaceFlow で、NATS JetStream の flow に断続的な問題が起きています。 consumer 向けに contract、error、retry、コピー可能な例を含む文書を書き、handler は変更しないでください。\n\n制約:\n- NATS JetStream を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は EquinoxCraneWorkspaceFlow のみ","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"ja"} +{"prompt":"Goal: A flaky failure around EquinoxBirchMigratorStore survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxBirchMigratorStore\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Symptom: // projects/equinox/ml/pipeline/features.py\nfinal class EquinoxFlintTimelineFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Restructure EquinoxFlintTimelineFlow 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":"EquinoxRainfallDBService's staging timeout is already known to be wrong: change the single projects/equinox/infra/modules/edge/main.tf value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Milestones for replacing EquinoxSpruceDaemonService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"EquinoxMapleQueueCoordinator needs a paired pass: lay out a staged migration for EquinoxMapleQueueCoordinator, plus also add the visible loading and offline states. Use projects/equinox/db/migrations/20260730_events.sql as the source of truth, preserve the Tokio contract, and avoid unrelated cleanup.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.82,"slice":"mixed","lang":"en"} -{"prompt":"Headsup: // projects/equinox/db/migrations/20260730_events.sql\nfinal class EquinoxNovaPickerCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 EquinoxNovaPickerCoordinator; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Incident timeline — INC-45121\n\n08:02 deploy EquinoxWillowCodecFlow 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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Find the source of this EquinoxWillowCodecFlow 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.9,"slice":"pasted-context","lang":"de"} -{"prompt":"Before we approve EquinoxBeaconStoreStore, assess whether lost focus when the drawer animation finishes is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"EquinoxDriftConsoleCoordinator: correct, then document","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.27,"slice":"mixed","lang":"en"} -{"prompt":"FYI: // projects/equinox/src/sync/reconcile.ts\nfinal class EquinoxMapleQueueFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 EquinoxMapleQueueFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"The behavior of EquinoxGarnetModalService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/equinox/app/src/main/SyncWorker.kt. 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- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current Tokio operational envelope\n\nThe relevant code crosses identity, Rust CLI, Vue. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"EquinoxSlateEditorCoordinator: make the api less awkward","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"vague-eval","lang":"en"} -{"prompt":"Test Suite 'EquinoxTideWorkerCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[EquinoxTideWorkerCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/equinox/pkg/cache/lease.rs:144: error: -[EquinoxTideWorkerCoordinatorTests 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 '-[EquinoxTideWorkerCoordinatorTests 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\nFinish the visible EquinoxTideWorkerCoordinator 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.73,"slice":"pasted-context","lang":"en"} -{"prompt":"Document EquinoxCinderAuthService's cancellation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"Two asks around EquinoxAmberFilterCoordinator: (1) finish EquinoxAmberFilterCoordinator's responsive empty and retry states; (2) capture the contract and rollback note for consumers. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.59,"slice":"mixed","lang":"en"} -{"prompt":"diff --git a/projects/equinox/infra/modules/edge/main.tf b/projects/equinox/infra/modules/edge/main.tf\nindex 62d71aa..90f3c1e 100644\n--- a/projects/equinox/infra/modules/edge/main.tf\n+++ b/projects/equinox/infra/modules/edge/main.tf\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure EquinoxRainfallDBFlow 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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Meanwhile: Two engineers disagree about whether EquinoxHarborIndexStore's cache is authoritative. Walk the reads and writes in projects/equinox/packages/api/openapi.yaml and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"EquinoxQuartzPlayerCoordinator: ship a sensible version","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"vague-eval","lang":"en"} -{"prompt":"Locally: // projects/equinox/web/components/FilterDrawer.vue\nfinal class EquinoxCraneWorkspaceCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 EquinoxCraneWorkspaceCoordinator 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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"EquinoxPineMetricsCoordinator: something is off here","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"vague-eval","lang":"en"} -{"prompt":"Document EquinoxMosaicGridStore's cancellation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"boundary","lang":"en"} -{"prompt":"Rename EquinoxSummitProxyStore's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"EquinoxNimbusFormCoordinator is blocking the next release because out-of-order events after consumer rebalancing. I need two concrete outcomes from a single pass: finish EquinoxNimbusFormCoordinator's responsive empty and retry states, and capture the contract and rollback note for consumers. Use the existing NATS JetStream conventions in projects/equinox/services/ledger/replay.go; preserve cancellation and back-pressure semantics. 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":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"EquinoxAcornWidgetService'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.14,"slice":"core","lang":"en"} -{"prompt":"Architect a gradual ownership transfer for EquinoxOpalRouterFlow across two teams, including module seams, temporary interfaces, observability, handoff criteria, and rollback responsibility. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Collapse the EquinoxBirchMigratorService wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"# projects/equinox/internal/auth/refresh.go\n[worker.equinoxlumenchartflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.equinoxlumenchartflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.equinoxlumenchartflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.EquinoxLumenChartFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-45116\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/equinox/internal/auth/refresh.go and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.36,"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_45140'\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_45140'::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 EquinoxSlateEditorFlow 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.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Ticket OPS-45136: retire the legacy replay path for EquinoxWrenExportFlow\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 EquinoxWrenExportFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.59,"slice":"pasted-context","lang":"en"} -{"prompt":"Set EquinoxMapleQueueStore's port to 8081","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"boundary","lang":"en"} -{"prompt":"Production: Ticket OPS-45128: retire the legacy replay path for EquinoxSummitProxyFlow\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 EquinoxSummitProxyFlow 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.65,"slice":"pasted-context","lang":"en"} -{"prompt":"Production says EquinoxRavenSessionService is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. 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- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current WebGPU operational envelope\n\nThe relevant code crosses identity, Rust CLI, Vue. Prefer evidence from the repository and make any assumption explicit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.84,"slice":"core","lang":"en"} -{"prompt":"Move EquinoxGarnetModalFlow'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.63,"slice":"boundary","lang":"en"} -{"prompt":"Security flagged EquinoxLumenChartStore for a read-only pass because its NATS JetStream boundary mixes tenant data, retries, and cancellation in subtle ways. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current NATS JetStream operational envelope\n\nThe relevant code crosses identity, Rust CLI, Vue. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.69,"slice":"boundary","lang":"en"} +{"prompt":"EquinoxMapleQueueCoordinator needs a paired pass: lay out a staged migration for EquinoxMapleQueueCoordinator, plus also add the visible loading and offline states. Use projects/equinox/db/migrations/20260730_events.sql as the source of truth, preserve the Tokio contract, and avoid unrelated cleanup.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Headsup: // projects/equinox/db/migrations/20260730_events.sql\nfinal class EquinoxNovaPickerCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 EquinoxNovaPickerCoordinator; 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":"Incident timeline — INC-45121\n\n08:02 deploy EquinoxWillowCodecFlow 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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Find the source of this EquinoxWillowCodecFlow symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Before we approve EquinoxBeaconStoreStore, assess whether lost focus when the drawer animation finishes is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"EquinoxDriftConsoleCoordinator: correct, then document","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"FYI: // projects/equinox/src/sync/reconcile.ts\nfinal class EquinoxMapleQueueFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 EquinoxMapleQueueFlow; 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":"The behavior of EquinoxGarnetModalService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/equinox/app/src/main/SyncWorker.kt. 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- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current Tokio operational envelope\n\nThe relevant code crosses identity, Rust CLI, Vue. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"EquinoxSlateEditorCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Test Suite 'EquinoxTideWorkerCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[EquinoxTideWorkerCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/equinox/pkg/cache/lease.rs:144: error: -[EquinoxTideWorkerCoordinatorTests 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 '-[EquinoxTideWorkerCoordinatorTests 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\nFinish the visible EquinoxTideWorkerCoordinator 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":"Document EquinoxCinderAuthService's cancellation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Two asks around EquinoxAmberFilterCoordinator: (1) finish EquinoxAmberFilterCoordinator's responsive empty and retry states; (2) capture the contract and rollback note for consumers. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"diff --git a/projects/equinox/infra/modules/edge/main.tf b/projects/equinox/infra/modules/edge/main.tf\nindex 62d71aa..90f3c1e 100644\n--- a/projects/equinox/infra/modules/edge/main.tf\n+++ b/projects/equinox/infra/modules/edge/main.tf\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure EquinoxRainfallDBFlow 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":"Meanwhile: Two engineers disagree about whether EquinoxHarborIndexStore's cache is authoritative. Walk the reads and writes in projects/equinox/packages/api/openapi.yaml and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"EquinoxQuartzPlayerCoordinator: ship a sensible version","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Locally: // projects/equinox/web/components/FilterDrawer.vue\nfinal class EquinoxCraneWorkspaceCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 EquinoxCraneWorkspaceCoordinator 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":"EquinoxPineMetricsCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Document EquinoxMosaicGridStore's cancellation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Rename EquinoxSummitProxyStore's staleLease state","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"EquinoxNimbusFormCoordinator is blocking the next release because out-of-order events after consumer rebalancing. I need two concrete outcomes from a single pass: finish EquinoxNimbusFormCoordinator's responsive empty and retry states, and capture the contract and rollback note for consumers. Use the existing NATS JetStream conventions in projects/equinox/services/ledger/replay.go; preserve cancellation and back-pressure semantics. 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":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"EquinoxAcornWidgetService's metric is misspelled as succesful_total in one declaration. Correct that literal and its exact test expectation, without renaming anything else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Architect a gradual ownership transfer for EquinoxOpalRouterFlow across two teams, including module seams, temporary interfaces, observability, handoff criteria, and rollback responsibility. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Collapse the EquinoxBirchMigratorService wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"# projects/equinox/internal/auth/refresh.go\n[worker.equinoxlumenchartflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.equinoxlumenchartflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.equinoxlumenchartflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.EquinoxLumenChartFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-45116\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/equinox/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":"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_45140'\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_45140'::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 EquinoxSlateEditorFlow 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":"Ticket OPS-45136: retire the legacy replay path for EquinoxWrenExportFlow\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 EquinoxWrenExportFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Set EquinoxMapleQueueStore's port to 8081","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Production: Ticket OPS-45128: retire the legacy replay path for EquinoxSummitProxyFlow\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 EquinoxSummitProxyFlow 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":"Production says EquinoxRavenSessionService is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. 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- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current WebGPU operational envelope\n\nThe relevant code crosses identity, Rust CLI, Vue. Prefer evidence from the repository and make any assumption explicit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Move EquinoxGarnetModalFlow'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.5,"slice":"core","lang":"en"} +{"prompt":"Security flagged EquinoxLumenChartStore for a read-only pass because its NATS JetStream boundary mixes tenant data, retries, and cancellation in subtle ways. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current NATS JetStream operational envelope\n\nThe relevant code crosses identity, Rust CLI, Vue. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"For EquinoxKiteSchedulerCoordinator, assess ownership and failure handling in projects/equinox/ui/settings/PrivacyPane.tsx; once that is complete, capture the contract and rollback note for consumers. Work from projects/equinox/ui/settings/PrivacyPane.tsx, stay with PostgreSQL 17, and preserve cancellation and back-pressure semantics. Keep the two outcomes separately reviewable.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"The next client release depends on a new EquinoxGarnetModalStore capability in projects/equinox/apps/console/routes/usage.svelte, with Tokio already chosen by the platform group. Wire the schema, repository, handler, and worker so duplicate deliveries return the original result and shutdown never acknowledges uncommitted work.\n\nConstraints:\n- preserve cancellation and back-pressure semantics\n- stay compatible with the existing Tokio deployment\n- keep the work scoped to EquinoxGarnetModalStore and its direct tests\n\nSeveral teams work in this identity, Rust CLI, Vue monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.83,"slice":"boundary","lang":"en"} -{"prompt":"Two asks around EquinoxMosaicGridCoordinator: (1) produce a consumer guide for EquinoxMosaicGridCoordinator; (2) give the existing implementation a read-only safety pass. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.53,"slice":"mixed","lang":"en"} -{"prompt":"Pin EquinoxWillowCodecStore's NATS dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"boundary","lang":"en"} -{"prompt":"Staging: // projects/equinox/packages/api/openapi.yaml\nfinal class EquinoxSableParserCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 EquinoxSableParserCoordinator; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"CI: The API work is done; what remains for EquinoxSableParserService is the visible interaction layer across loading, offline, empty, and success cases. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxSableParserService\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Set EquinoxAmberFilterStore's port to 8081","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"boundary","lang":"en"} -{"prompt":"PM is preparing the EquinoxDeltaCanvasStore rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxDeltaCanvasStore\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"# projects/equinox/pkg/cache/lease.rs\n[worker.equinoxamberfilterflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.equinoxamberfilterflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.equinoxamberfilterflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.EquinoxAmberFilterFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-45132\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 EquinoxAmberFilterFlow'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.38,"slice":"pasted-context","lang":"en"} -{"prompt":"Please resist widening this one: EquinoxNovaPickerService works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxNovaPickerService\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"In projects/equinox/web/components/FilterDrawer.vue hat EquinoxNimbusFormService ein sporadisches Problem im NATS JetStream-Ablauf. Die Ursache ist klar: Ändere nur das Staging-Timeout von 15 auf 30 Sekunden und passe die Assertion an.\n\nRandbedingungen:\n- NATS JetStream weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf EquinoxNimbusFormService begrenzen","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.28,"slice":"core","lang":"de"} -{"prompt":"Atlas: The public surface of EquinoxFlintTimelineService is frozen, but its internal ownership in projects/equinox/ml/pipeline/features.py is difficult to test and even harder to change safely. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxFlintTimelineService\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"UI ticket DES-45129: finish the compact EquinoxMosaicGridFlow filter experience\n\nRoute: /catalog/search\nSource: projects/equinox/app/src/main/SyncWorker.kt\nFramework: Tokio\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Use the UI evidence to complete EquinoxMosaicGridFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"fr"} -{"prompt":"thread 'tokio-runtime-worker' panicked at projects/equinox/apps/console/routes/usage.svelte:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: equinoxgarnetmodalcoordinator::scheduler::LeaseTask::flush\n at ./projects/equinox/apps/console/routes/usage.svelte:217:18\n 4: equinoxgarnetmodalcoordinator::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nReconstruct the EquinoxGarnetModalCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"Match EquinoxEchoRegistryService's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"core","lang":"en"} -{"prompt":"Bring EquinoxFrostPanelService'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.54,"slice":"core","lang":"en"} -{"prompt":"Could EquinoxSlateEditorStore show the active PostgreSQL 17 sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"boundary","lang":"en"} -{"prompt":"Why is EquinoxSummitProxyService stalling?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"EquinoxAtlasSearchStore leaks tasks on shutdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Ownership of EquinoxMoonlitSDKStore is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current PostgreSQL 17 operational envelope\n\nThe relevant code crosses identity, Rust CLI, Vue. Prefer evidence from the repository and make any assumption explicit.\n\nReturn the restructuring sequence and decision points, not the edits themselves.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.78,"slice":"boundary","lang":"en"} -{"prompt":"Ticket OPS-45150: retire the legacy replay path for EquinoxCloudReconcilerCoordinator\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for EquinoxCloudReconcilerCoordinator, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"pasted-context","lang":"en"} -{"prompt":"Decouple EquinoxMapleQueueService's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"diff --git a/projects/equinox/internal/auth/refresh.go b/projects/equinox/internal/auth/refresh.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/equinox/internal/auth/refresh.go\n+++ b/projects/equinox/internal/auth/refresh.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate EquinoxPrismCacheCoordinator'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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"A previously stable test around EquinoxNovaPickerStore now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"A previously stable test around EquinoxWrenExportService now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"EquinoxLumenChartCoordinator: diagnose, then correct","purpose":"debugging","secondary":"quickFix","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Beacon: Ticket OPS-45134: retire the legacy replay path for EquinoxBeaconStoreFlow\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 EquinoxBeaconStoreFlow 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.67,"slice":"pasted-context","lang":"en"} -{"prompt":"How does EquinoxCedarPolicyStore propagate cancellation through the PostgreSQL 17 boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"The next client release depends on a new EquinoxGarnetModalStore capability in projects/equinox/apps/console/routes/usage.svelte, with Tokio already chosen by the platform group. Wire the schema, repository, handler, and worker so duplicate deliveries return the original result and shutdown never acknowledges uncommitted work.\n\nConstraints:\n- preserve cancellation and back-pressure semantics\n- stay compatible with the existing Tokio deployment\n- keep the work scoped to EquinoxGarnetModalStore and its direct tests\n\nSeveral teams work in this identity, Rust CLI, Vue monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Two asks around EquinoxMosaicGridCoordinator: (1) produce a consumer guide for EquinoxMosaicGridCoordinator; (2) give the existing implementation a read-only safety pass. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Pin EquinoxWillowCodecStore's NATS dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Staging: // projects/equinox/packages/api/openapi.yaml\nfinal class EquinoxSableParserCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 EquinoxSableParserCoordinator; 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":"CI: The API work is done; what remains for EquinoxSableParserService is the visible interaction layer across loading, offline, empty, and success cases. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxSableParserService\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Set EquinoxAmberFilterStore's port to 8081","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"PM is preparing the EquinoxDeltaCanvasStore rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxDeltaCanvasStore\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"# projects/equinox/pkg/cache/lease.rs\n[worker.equinoxamberfilterflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.equinoxamberfilterflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.equinoxamberfilterflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.EquinoxAmberFilterFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-45132\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 EquinoxAmberFilterFlow'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":"Please resist widening this one: EquinoxNovaPickerService works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxNovaPickerService\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"In projects/equinox/web/components/FilterDrawer.vue hat EquinoxNimbusFormService ein sporadisches Problem im NATS JetStream-Ablauf. Die Ursache ist klar: Ändere nur das Staging-Timeout von 15 auf 30 Sekunden und passe die Assertion an.\n\nRandbedingungen:\n- NATS JetStream weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf EquinoxNimbusFormService begrenzen","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"de"} +{"prompt":"Atlas: The public surface of EquinoxFlintTimelineService is frozen, but its internal ownership in projects/equinox/ml/pipeline/features.py is difficult to test and even harder to change safely. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxFlintTimelineService\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-45129: finish the compact EquinoxMosaicGridFlow filter experience\n\nRoute: /catalog/search\nSource: projects/equinox/app/src/main/SyncWorker.kt\nFramework: Tokio\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Use the UI evidence to complete EquinoxMosaicGridFlow'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":"thread 'tokio-runtime-worker' panicked at projects/equinox/apps/console/routes/usage.svelte:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: equinoxgarnetmodalcoordinator::scheduler::LeaseTask::flush\n at ./projects/equinox/apps/console/routes/usage.svelte:217:18\n 4: equinoxgarnetmodalcoordinator::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nReconstruct the EquinoxGarnetModalCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Match EquinoxEchoRegistryService's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Bring EquinoxFrostPanelService'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.5,"slice":"core","lang":"en"} +{"prompt":"Could EquinoxSlateEditorStore show the active PostgreSQL 17 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":"Why is EquinoxSummitProxyService stalling?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"EquinoxAtlasSearchStore leaks tasks on shutdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Ownership of EquinoxMoonlitSDKStore is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current PostgreSQL 17 operational envelope\n\nThe relevant code crosses identity, Rust CLI, Vue. Prefer evidence from the repository and make any assumption explicit.\n\nReturn the restructuring sequence and decision points, not the edits themselves.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-45150: retire the legacy replay path for EquinoxCloudReconcilerCoordinator\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for EquinoxCloudReconcilerCoordinator, 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":"Decouple EquinoxMapleQueueService's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/equinox/internal/auth/refresh.go b/projects/equinox/internal/auth/refresh.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/equinox/internal/auth/refresh.go\n+++ b/projects/equinox/internal/auth/refresh.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate EquinoxPrismCacheCoordinator'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":"A previously stable test around EquinoxNovaPickerStore now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"A previously stable test around EquinoxWrenExportService now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"EquinoxLumenChartCoordinator: diagnose, then correct","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Beacon: Ticket OPS-45134: retire the legacy replay path for EquinoxBeaconStoreFlow\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 EquinoxBeaconStoreFlow 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":"How does EquinoxCedarPolicyStore propagate cancellation through the PostgreSQL 17 boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Is EquinoxEmberRelayService safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"For EquinoxIrisBatchCoordinator, ship the idempotent EquinoxIrisBatchCoordinator replay endpoint; once that is complete, correct the known stale timeout beside it. Work from projects/equinox/services/ledger/replay.go, stay with NATS JetStream, and preserve cancellation and back-pressure semantics. Keep the two outcomes separately reviewable.","purpose":"backendImpl","secondary":"quickFix","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Could the reasoning behind EquinoxRainfallDBStore's NATS JetStream choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"diff --git a/projects/equinox/Sources/App/SessionStore.swift b/projects/equinox/Sources/App/SessionStore.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/equinox/Sources/App/SessionStore.swift\n+++ b/projects/equinox/Sources/App/SessionStore.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit EquinoxSpruceDaemonFlow 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.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Split EquinoxWillowCodecService without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current EquinoxMicaProfileStore design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxMicaProfileStore\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"boundary","lang":"en"} -{"prompt":"EquinoxCoralUploadCoordinator: deal with the small issue","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"vague-eval","lang":"en"} -{"prompt":"Rename EquinoxMicaProfileService's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Unifie les validateurs de EquinoxMarbleTokenStore","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"fr"} -{"prompt":"EquinoxOrbitSyncCoordinator needs a paired pass: find the unknown cause of lease renewal code copied across three workers, plus give the existing implementation a read-only safety pass. Use projects/equinox/cmd/exporter/main.py as the source of truth, preserve the SQLite contract, and avoid unrelated cleanup.","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"The name pendingAck means two different things across EquinoxLedgerGateService's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"EquinoxBasilRunnerCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.53,"slice":"mixed","lang":"en"} -{"prompt":"Skizziere die EquinoxBasilRunnerStore-Migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"de"} -{"prompt":"What is the safest way to split projects/equinox/app/src/main/SyncWorker.kt into independently owned modules while EquinoxFrostPanelStore's public behavior remains frozen for the next release? Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"Cinder: Ticket OPS-45153: retire the legacy replay path for EquinoxOpalRouterCoordinator\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 を維持し、根拠と判断を明確にしてください。 Assess EquinoxOpalRouterCoordinator 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.82,"slice":"pasted-context","lang":"ja"} -{"prompt":"EquinoxMicaProfileCoordinator is blocking the next release because lost focus when the drawer animation finishes. I need two concrete outcomes from a single pass: lay out a staged migration for EquinoxMicaProfileCoordinator, and consolidate the duplicated normalization paths without changing behavior. Use the existing Tokio conventions in projects/equinox/src/sync/reconcile.ts; preserve cancellation and back-pressure semantics. 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.96,"slice":"mixed","lang":"en"} -{"prompt":"We need to move EquinoxBeaconStoreService from the legacy store to Tokio. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"// projects/equinox/config/staging.toml\nfinal class EquinoxMarbleTokenFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 EquinoxMarbleTokenFlow 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Delta: A copied hex color in EquinoxOspreyJobFlow lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"boundary","lang":"en"} -{"prompt":"Incident timeline — INC-45114\n\n08:02 deploy EquinoxMicaProfileFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nReconstruct the EquinoxMicaProfileFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"Ember: A copied hex color in EquinoxSableParserStore lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"core","lang":"en"} -{"prompt":"Test Suite 'EquinoxQuartzPlayerFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[EquinoxQuartzPlayerFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/equinox/Sources/App/SessionStore.swift:144: error: -[EquinoxQuartzPlayerFlowTests 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 '-[EquinoxQuartzPlayerFlowTests 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 EquinoxQuartzPlayerFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.76,"slice":"pasted-context","lang":"en"} -{"prompt":"EquinoxWrenExportCoordinator: the docs need something","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"Ticket OPS-45135: retire the legacy replay path for EquinoxCoralUploadFlow\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 EquinoxCoralUploadFlow 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.74,"slice":"pasted-context","lang":"en"} -{"prompt":"Center the EquinoxSpruceDaemonStore modal","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} -{"prompt":"Frost: diff --git a/projects/equinox/packages/api/openapi.yaml b/projects/equinox/packages/api/openapi.yaml\nindex 62d71aa..90f3c1e 100644\n--- a/projects/equinox/packages/api/openapi.yaml\n+++ b/projects/equinox/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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Read the artifact above as a skeptical reviewer. Is EquinoxAcornWidgetFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"pt"} -{"prompt":"EquinoxFrostPanelCoordinator: check the suspicious part","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"vague-eval","lang":"en"} -{"prompt":"EquinoxQuartzPlayerService 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":"Garnet: projects/equinox/db/migrations/20260730_events.sql now contains EquinoxPineMetricsStore'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.63,"slice":"boundary","lang":"en"} -{"prompt":"Harbor: projects/equinox/crates/index/src/segment.rs has grown through several launches, and EquinoxTideWorkerService now mixes policy, transport, persistence, and metrics in one place. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- preserve cancellation and back-pressure semantics\n- stay compatible with the existing WebGPU deployment\n- keep the work scoped to EquinoxTideWorkerService and its direct tests\n\nSeveral teams work in this identity, Rust CLI, Vue monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Does EquinoxPrismCacheStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Spell EquinoxKiteSchedulerStore's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"boundary","lang":"en"} -{"prompt":"EquinoxJuniperCLICoordinator: sort out the rough edge","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"vague-eval","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_45148'\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_45148'::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\nAdd the bounded EquinoxCopperBridgeFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a bounded EquinoxCloudReconcilerStore export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Since the last release, EquinoxOspreyJobService has shown timestamps rendered one day ahead near UTC midnight; nobody on the team can reproduce it reliably on a laptop. Reconstruct the failing timeline from logs and tests, identify which invariant first breaks, and distinguish causal signals from effects or cleanup noise.\n\nConstraints:\n- preserve cancellation and back-pressure semantics\n- stay compatible with the existing PostgreSQL 17 deployment\n- keep the work scoped to EquinoxOspreyJobService and its direct tests\n\nSeveral teams work in this identity, Rust CLI, Vue monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Release engineering needs a EquinoxCopperBridgeStore changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"boundary","lang":"en"} -{"prompt":"En projects/equinox/cmd/exporter/main.py, EquinoxOpalRouterService tiene un problema intermitente en el flujo de SQLite. Termina el layout responsive, estados vacío y retry, foco por teclado, dark mode y reduced motion.\n\nRestricciones:\n- seguir con SQLite\n- conservar compatibilidad y cancelación\n- limitar el cambio a EquinoxOpalRouterService","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"es"} -{"prompt":"Give EquinoxOspreyJobStore'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.44,"slice":"core","lang":"en"} -{"prompt":"The next client release depends on a new EquinoxRavenSessionStore capability in projects/equinox/crates/index/src/segment.rs, with WebGPU already chosen by the platform group. Wire the schema, repository, handler, and worker so duplicate deliveries return the original result and shutdown never acknowledges uncommitted work.\n\nConstraints:\n- preserve cancellation and back-pressure semantics\n- stay compatible with the existing WebGPU deployment\n- keep the work scoped to EquinoxRavenSessionStore and its direct tests\n\nSeveral teams work in this identity, Rust CLI, Vue monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"boundary","lang":"en"} -{"prompt":"Support wants the behavior in projects/equinox/web/components/FilterDrawer.vue recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"Test Suite 'EquinoxEmberRelayFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[EquinoxEmberRelayFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/equinox/lib/codec/frame.cc:144: error: -[EquinoxEmberRelayFlowTests 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 '-[EquinoxEmberRelayFlowTests 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 EquinoxEmberRelayFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"pasted-context","lang":"en"} -{"prompt":"Iris: Test Suite 'EquinoxEchoRegistryFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[EquinoxEchoRegistryFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/equinox/crates/index/src/segment.rs:144: error: -[EquinoxEchoRegistryFlowTests 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 '-[EquinoxEchoRegistryFlowTests 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\nFinish the visible EquinoxEchoRegistryFlow 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.73,"slice":"pasted-context","lang":"en"} -{"prompt":"Design the EquinoxOrbitSyncService rollback","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"EquinoxEmberRelayCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"# projects/equinox/services/ledger/replay.go\n[worker.equinoxfernsnapshotflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.equinoxfernsnapshotflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.equinoxfernsnapshotflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.EquinoxFernSnapshotFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-45141\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 EquinoxFernSnapshotFlow'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.36,"slice":"pasted-context","lang":"en"} -{"prompt":"Could the reasoning behind EquinoxDeltaCanvasFlow's SQLite choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"boundary","lang":"en"} -{"prompt":"Flip EquinoxLumenChartService's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"core","lang":"en"} -{"prompt":"Ownership of EquinoxFlintTimelineStore is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current SQLite operational envelope\n\nThe relevant code crosses identity, Rust CLI, Vue. Prefer evidence from the repository and make any assumption explicit.\n\nReturn the restructuring sequence and decision points, not the edits themselves.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"boundary","lang":"en"} -{"prompt":"Add a bounded EquinoxLedgerGateStore export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"Polish the EquinoxVelaDrawerService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"How does EquinoxFernSnapshotService propagate cancellation through the NATS JetStream boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Collapse the EquinoxIrisBatchStore wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"We expect EquinoxDeltaCanvasService to outgrow its current SQLite arrangement next quarter, but changing everything at once would be risky. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- preserve cancellation and back-pressure semantics\n- stay compatible with the existing SQLite deployment\n- keep the work scoped to EquinoxDeltaCanvasService and its direct tests\n\nSeveral teams work in this identity, Rust CLI, Vue monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"core","lang":"en"} -{"prompt":"Juniper: # projects/equinox/crates/index/src/segment.rs\n[worker.equinoxledgergateflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.equinoxledgergateflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.equinoxledgergateflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.EquinoxLedgerGateFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-45142\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/equinox/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.38,"slice":"pasted-context","lang":"en"} -{"prompt":"Kestrel: We need to move EquinoxTideWorkerStore from the legacy store to WebGPU. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Responsive layout for EquinoxOrbitSyncStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} -{"prompt":"Incident timeline — INC-45149\n\n08:02 deploy EquinoxAsterWebhookFlow 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 EquinoxAsterWebhookFlow 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.67,"slice":"pasted-context","lang":"en"} -{"prompt":"EquinoxMarbleTokenCoordinator needs a paired pass: produce a consumer guide for EquinoxMarbleTokenCoordinator, plus correct the known stale timeout beside it. Use projects/equinox/packages/api/openapi.yaml as the source of truth, preserve the WebGPU contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.48,"slice":"mixed","lang":"en"} -{"prompt":"Lumen: Incident timeline — INC-45155\n\n08:02 deploy EquinoxOspreyJobCoordinator 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 EquinoxOspreyJobCoordinator migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Wire a EquinoxOpalRouterStore background task in projects/equinox/ml/pipeline/features.py that expires abandoned sessions, records an OpenTelemetry span, and yields cleanly when shutdown begins.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Read projects/equinox/lib/codec/frame.cc and tell me whether EquinoxCloudReconcilerFlow can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"EquinoxAtlasSearchCoordinator needs a paired pass: separate EquinoxAtlasSearchCoordinator's policy from transport without behavior changes, plus give the existing implementation a read-only safety pass. Use projects/equinox/lib/codec/frame.cc as the source of truth, preserve the PostgreSQL 17 contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.63,"slice":"mixed","lang":"en"} -{"prompt":"Maple: Incident timeline — INC-45133\n\n08:02 deploy EquinoxOrbitSyncFlow 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 EquinoxOrbitSyncFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.65,"slice":"pasted-context","lang":"en"} -{"prompt":"EquinoxRainfallDBCoordinator: give it a nicer flow","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"vague-eval","lang":"en"} -{"prompt":"Nimbus: projects/equinox/cmd/exporter/main.py の EquinoxJuniperCLIService で、SQLite の flow に断続的な問題が起きています。 原因は判明済みです。staging timeout だけを 15 秒から 30 秒へ変え、対応する assertion を直してください。\n\n制約:\n- SQLite を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は EquinoxJuniperCLIService のみ","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"core","lang":"ja"} -{"prompt":"UI ticket DES-45139: finish the compact EquinoxFrostPanelFlow filter experience\n\nRoute: /catalog/search\nSource: projects/equinox/apps/console/routes/usage.svelte\nFramework: Tokio\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring EquinoxFrostPanelFlow'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.78,"slice":"pasted-context","lang":"en"} -{"prompt":"For EquinoxSummitProxyCoordinator, separate EquinoxSummitProxyCoordinator's policy from transport without behavior changes; once that is complete, capture the contract and rollback note for consumers. Work from projects/equinox/Sources/App/SessionStore.swift, stay with SQLite, and preserve cancellation and back-pressure semantics. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"EquinoxHarborIndexCoordinator: handle the lingering thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"vague-eval","lang":"en"} -{"prompt":"diff --git a/projects/equinox/Sources/App/SessionStore.swift b/projects/equinox/Sources/App/SessionStore.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/equinox/Sources/App/SessionStore.swift\n+++ b/projects/equinox/Sources/App/SessionStore.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is EquinoxDeltaCanvasCoordinator's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"EquinoxAsterWebhookCoordinator: take care of the warning","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"// projects/equinox/web/components/FilterDrawer.vue\nfinal class EquinoxIrisBatchFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 EquinoxIrisBatchFlow 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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"How should EquinoxAtlasSearchService be decomposed?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Fresh release brief for EquinoxMoonlitSDKCoordinator:\n- primary outcome: lay out a staged migration for EquinoxMoonlitSDKCoordinator\n- companion outcome: then implement the bounded durable-cursor handler\n- repository entry point: projects/equinox/lib/codec/frame.cc\n- platform constraint: PostgreSQL 17\n- known complication: a deadlock that appears only during shutdown\n\nBoth results are required, but they should remain independently reviewable. Preserve cancellation and back-pressure semantics; retain serialization and authorization boundaries; cover cancellation, idempotent retries, and rollback; and avoid drive-by cleanup. Use the code as the source of truth, call out assumptions, and state how an on-call engineer can tell that either part is unsafe to ship.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.88,"slice":"mixed","lang":"en"} -{"prompt":"Fresh release brief for EquinoxFlintTimelineCoordinator:\n- primary outcome: assess ownership and failure handling in projects/equinox/cmd/exporter/main.py\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/equinox/cmd/exporter/main.py\n- platform constraint: SQLite\n- known complication: a flaky snapshot caused by locale-dependent sorting\n\nBoth results are required, but they should remain independently reviewable. Preserve cancellation and back-pressure semantics; 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.84,"slice":"mixed","lang":"en"} -{"prompt":"EquinoxBirchMigratorCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.48,"slice":"mixed","lang":"en"} -{"prompt":"EquinoxCopperBridgeCoordinator: could this be clearer","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"vague-eval","lang":"en"} -{"prompt":"On compact widths, EquinoxQuartzPlayerStore'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.52,"slice":"boundary","lang":"en"} -{"prompt":"Memory attributed to EquinoxPineMetricsService rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Could the reasoning behind EquinoxTideWorkerFlow's WebGPU choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"en"} -{"prompt":"EquinoxSpruceDaemonCoordinator: document, then correct","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.51,"slice":"mixed","lang":"en"} -{"prompt":"Ticket OPS-45117: retire the legacy replay path for EquinoxBirchMigratorFlow\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 EquinoxBirchMigratorFlow 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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"EquinoxEchoRegistryCoordinator: sequence, then ship","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.77,"slice":"mixed","lang":"en"} -{"prompt":"diff --git a/projects/equinox/infra/modules/edge/main.tf b/projects/equinox/infra/modules/edge/main.tf\nindex 62d71aa..90f3c1e 100644\n--- a/projects/equinox/infra/modules/edge/main.tf\n+++ b/projects/equinox/infra/modules/edge/main.tf\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate EquinoxVelaDrawerFlow'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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"The behavior of EquinoxCloudReconcilerService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/equinox/lib/codec/frame.cc. 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- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current PostgreSQL 17 operational envelope\n\nThe relevant code crosses identity, Rust CLI, Vue. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.49,"slice":"core","lang":"en"} -{"prompt":"Ticket OPS-45110: retire the legacy replay path for EquinoxMoonlitSDKFlow\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 EquinoxMoonlitSDKFlow 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.57,"slice":"pasted-context","lang":"en"} -{"prompt":"Compare the old and new EquinoxAsterWebhookStore adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"En projects/equinox/services/ledger/replay.go, EquinoxNimbusFormStore tiene un problema intermitente en el flujo de NATS JetStream. Propón fases, compatibilidad, métricas, rollback y ownership; detente antes de tocar código.\n\nRestricciones:\n- seguir con NATS JetStream\n- conservar compatibilidad y cancelación\n- limitar el cambio a EquinoxNimbusFormStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con NATS JetStream alrededor de EquinoxNimbusFormStore.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.81,"slice":"boundary","lang":"es"} -{"prompt":"Sketch the EquinoxVelaDrawerStore migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"Bring EquinoxCraneWorkspaceStore'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.46,"slice":"core","lang":"en"} -{"prompt":"EquinoxAsterWebhookService returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/equinox/app/src/main/SyncWorker.kt and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"The EquinoxCopperBridgeService 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.17,"slice":"core","lang":"en"} -{"prompt":"Sequence EquinoxMosaicGridService's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-45147\n\n08:02 deploy EquinoxHarborIndexFlow 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 EquinoxHarborIndexFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.62,"slice":"pasted-context","lang":"en"} -{"prompt":"EquinoxLedgerGateCoordinator: make this less weird","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} -{"prompt":"Flip EquinoxAmberFilterService's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"core","lang":"en"} -{"prompt":"Make EquinoxDriftConsoleStore keyboard navigable","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} -{"prompt":"projects/equinox/ml/pipeline/features.py 里的 EquinoxJuniperCLIStore 最近在 SQLite 流程中出现间歇性问题。 请实现幂等 endpoint，包含持久 cursor、tenant 鉴权、spans 和 retry 测试。\n\n约束：\n- 继续使用 SQLite\n- 保持兼容性和取消语义\n- 改动只限于 EquinoxJuniperCLIStore","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"zh"} -{"prompt":"Documente o contrato de EquinoxMarbleTokenService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"pt"} -{"prompt":"Opal: projects/equinox/ui/settings/PrivacyPane.tsx 里的 EquinoxCoralUploadService 最近在 PostgreSQL 17 流程中出现间歇性问题。 请阅读现有流程，判断 ownership、取消和顺序是否安全，只需要分析。\n\n约束：\n- 继续使用 PostgreSQL 17\n- 保持兼容性和取消语义\n- 改动只限于 EquinoxCoralUploadService","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"zh"} -{"prompt":"Remove EquinoxKiteSchedulerService's stray comma","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"core","lang":"en"} -{"prompt":"Two asks around EquinoxVelaDrawerCoordinator: (1) separate EquinoxVelaDrawerCoordinator's policy from transport without behavior changes; (2) correct the known stale timeout beside it. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"Prism: The EquinoxHarborIndexService surface in projects/equinox/config/staging.toml 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.38,"slice":"core","lang":"en"} -{"prompt":"Quartz: // projects/equinox/workers/thumbnail/consumer.ex\nfinal class EquinoxKiteSchedulerFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nDeliver the EquinoxKiteSchedulerFlow 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.81,"slice":"pasted-context","lang":"en"} -{"prompt":"Raven: Incident timeline — INC-45145\n\n08:02 deploy EquinoxCedarPolicyFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Map a safe route from the current EquinoxCedarPolicyFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"zh"} -{"prompt":"How does EquinoxSableParserFlow propagate cancellation through the WebGPU boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"I inherited FoxglovePineMetricsStore and need a careful read of projects/foxglove/services/ledger/replay.go 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- cover the awkward empty and retry states\n- stay compatible with the existing Kafka deployment\n- keep the work scoped to FoxglovePineMetricsStore and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"FoxgloveLumenChartStore returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/foxglove/cmd/exporter/main.py and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","lang":"en"} -{"prompt":"FoxgloveNimbusFormCoordinator: smooth out this interaction","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"vague-eval","lang":"en"} -{"prompt":"Two asks around FoxgloveSableParserCoordinator: (1) assess ownership and failure handling in projects/foxglove/db/migrations/20260730_events.sql; (2) capture the contract and rollback note for consumers. Cover the awkward empty and retry states, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"What does FoxgloveHarborIndexStore own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Sable: Two deliverables are holding up FoxgloveFernSnapshotCoordinator. First, assess ownership and failure handling in projects/foxglove/Sources/App/SessionStore.swift. In the same workstream, capture the contract and rollback note for consumers. The relevant starting point is projects/foxglove/Sources/App/SessionStore.swift, which follows Cloudflare Workers conventions and currently suffers from an accessibility label that reads the internal enum. Cover the awkward empty and retry states.\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":"review","secondary":"writing","mixed":true,"difficulty":0.86,"slice":"mixed","lang":"en"} -{"prompt":"Tide: projects/foxglove/ui/settings/PrivacyPane.tsx の FoxgloveSummitProxyFlow で、GraphQL の flow に断続的な問題が起きています。 現在の flow を読み、ownership、cancel、順序が安全か評価してください。分析だけで十分です。\n\n制約:\n- GraphQL を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は FoxgloveSummitProxyFlow のみ","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"ja"} -{"prompt":"Release engineering needs a FoxgloveKiteSchedulerService changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"For FoxgloveGarnetModalCoordinator, change FoxgloveGarnetModalCoordinator's known staging timeout from 15 to 30 seconds; once that is complete, give the existing implementation a read-only safety pass. Work from projects/foxglove/internal/auth/refresh.go, stay with Kafka, and cover the awkward empty and retry states. Keep the two outcomes separately reviewable.","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.24,"slice":"mixed","lang":"en"} -{"prompt":"Incident timeline — INC-46118\n\n08:02 deploy FoxgloveCedarPolicyFlow 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 FoxgloveCedarPolicyFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"pasted-context","lang":"en"} -{"prompt":"FoxgloveAcornWidgetCoordinator is blocking the next release because an empty state that flashes before cached data arrives. I need two concrete outcomes from a single pass: change FoxgloveAcornWidgetCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing Spring Boot conventions in projects/foxglove/db/migrations/20260730_events.sql; cover the awkward empty and retry states. 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.35,"slice":"mixed","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_46157'\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_46157'::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\nDeliver the FoxgloveBeaconStoreCoordinator 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.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Pin FoxgloveAsterWebhookService's Kafka dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"core","lang":"en"} -{"prompt":"Umbra: Ticket OPS-46155: retire the legacy replay path for FoxgloveAmberFilterCoordinator\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 FoxgloveAmberFilterCoordinator rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Split FoxgloveCedarPolicyStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"FoxgloveBasilRunnerCoordinator: take care of the warning","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"vague-eval","lang":"en"} -{"prompt":"Bring FoxgloveMapleQueueStore'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.49,"slice":"boundary","lang":"en"} -{"prompt":"Vela: Two deliverables are holding up FoxgloveQuartzPlayerCoordinator. First, separate FoxgloveQuartzPlayerCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/foxglove/ui/settings/PrivacyPane.tsx, which follows GraphQL conventions and currently suffers from a flaky snapshot caused by locale-dependent sorting. Cover the awkward empty and retry states.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"FoxgloveBirchMigratorCoordinator: handle the lingering thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"vague-eval","lang":"en"} -{"prompt":"Test Suite 'FoxglovePrismCacheFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[FoxglovePrismCacheFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/foxglove/cmd/exporter/main.py:144: error: -[FoxglovePrismCacheFlowTests 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 '-[FoxglovePrismCacheFlowTests 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 FoxglovePrismCacheFlow'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.78,"slice":"pasted-context","lang":"fr"} -{"prompt":"Willow: The first FoxgloveAtlasSearchFlow request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"FoxgloveVelaDrawerCoordinator: the docs need something","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"vague-eval","lang":"en"} -{"prompt":"Xylem: Ticket OPS-46141: retire the legacy replay path for FoxgloveSpruceDaemonFlow\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 FoxgloveSpruceDaemonFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"Three teams extended FoxgloveAmberFilterService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- cover the awkward empty and retry states\n- retain the current Spring Boot operational envelope\n\nThis repository spans observability, SwiftUI, Redis; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"FoxgloveHarborIndexCoordinator: restructure, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.63,"slice":"mixed","lang":"en"} -{"prompt":"Yarrow: The API work is done; what remains for FoxgloveAcornWidgetStore 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 FoxgloveAcornWidgetStore\n- cover the awkward empty and retry states\n\nSeveral teams work in this observability, SwiftUI, Redis monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Zephyr: Two asks around FoxgloveMoonlitSDKCoordinator: (1) finish FoxgloveMoonlitSDKCoordinator's responsive empty and retry states; (2) give the existing implementation a read-only safety pass. Cover the awkward empty and retry states, and leave a clear boundary between the resulting artifacts or edits.","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.61,"slice":"mixed","lang":"en"} -{"prompt":"A previously stable test around FoxgloveOrbitSyncFlow now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"boundary","lang":"en"} -{"prompt":"FoxgloveRainfallDBCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.53,"slice":"mixed","lang":"en"} -{"prompt":"Checkout: Incident timeline — INC-46130\n\n08:02 deploy FoxgloveSableParserFlow 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 FoxgloveSableParserFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"For FoxglovePrismCacheCoordinator, finish FoxglovePrismCacheCoordinator's responsive empty and retry states; once that is complete, correct the known stale timeout beside it. Work from projects/foxglove/ml/pipeline/features.py, stay with Cloudflare Workers, and cover the awkward empty and retry states. Keep the two outcomes separately reviewable.","purpose":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.64,"slice":"mixed","lang":"en"} -{"prompt":"Does FoxgloveCoralUploadFlow enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"// projects/foxglove/pkg/cache/lease.rs\nfinal class FoxgloveCinderAuthFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveCinderAuthFlow 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.84,"slice":"pasted-context","lang":"en"} -{"prompt":"FoxgloveBeaconStoreFlow returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/foxglove/services/ledger/replay.go and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"boundary","lang":"en"} -{"prompt":"Exporter: Incident timeline — INC-46150\n\n08:02 deploy FoxgloveMarbleTokenCoordinator 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 FoxgloveMarbleTokenCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"pasted-context","lang":"en"} -{"prompt":"Why does FoxgloveBeaconStoreStore's Kafka worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Scheduler: Incident timeline — INC-46124\n\n08:02 deploy FoxgloveCraneWorkspaceFlow 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 FoxgloveCraneWorkspaceFlow 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.67,"slice":"pasted-context","lang":"en"} -{"prompt":"Extract FoxgloveFernSnapshotService's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"A copied hex color in FoxgloveWrenExportFlow lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"boundary","lang":"en"} -{"prompt":"Fresh release brief for FoxgloveLedgerGateCoordinator:\n- primary outcome: produce a consumer guide for FoxgloveLedgerGateCoordinator\n- companion outcome: give the existing implementation a read-only safety pass\n- repository entry point: projects/foxglove/apps/console/routes/usage.svelte\n- platform constraint: Spring Boot\n- known complication: lease renewal code copied across three workers\n\nBoth results are required, but they should remain independently reviewable. Cover the awkward empty and retry states; 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":"writing","secondary":"review","mixed":true,"difficulty":0.59,"slice":"mixed","lang":"en"} -{"prompt":"Spell FoxgloveGarnetModalStore's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"boundary","lang":"en"} -{"prompt":"FoxgloveDriftConsoleCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"vague-eval","lang":"en"} -{"prompt":"FoxgloveTideWorkerCoordinator needs a paired pass: produce a consumer guide for FoxgloveTideWorkerCoordinator, plus give the existing implementation a read-only safety pass. Use projects/foxglove/app/src/main/SyncWorker.kt as the source of truth, preserve the Spring Boot contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.43,"slice":"mixed","lang":"en"} -{"prompt":"The FoxgloveMicaProfileStore surface in projects/foxglove/services/ledger/replay.go 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.38,"slice":"boundary","lang":"en"} -{"prompt":"Why does FoxgloveVelaDrawerStore's Cloudflare Workers worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","lang":"en"} -{"prompt":"# projects/foxglove/ui/settings/PrivacyPane.tsx\n[worker.foxglovecopperbridgeflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.foxglovecopperbridgeflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.foxglovecopperbridgeflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.FoxgloveCopperBridgeFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-46121\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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. The intended correction is already known: change only the stale 15-second setting to 30 seconds in projects/foxglove/ui/settings/PrivacyPane.tsx and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.36,"slice":"pasted-context","lang":"de"} -{"prompt":"We need to move FoxgloveFlintTimelineStore from the legacy store to GraphQL. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"FoxgloveCloudReconcilerCoordinator: polish, then correct","purpose":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.61,"slice":"mixed","lang":"en"} -{"prompt":"Give FoxgloveAsterWebhookStore a README example","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"en"} -{"prompt":"Release engineering needs a FoxgloveBirchMigratorStore changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"boundary","lang":"en"} -{"prompt":"We need to move FoxgloveMarbleTokenStore from the legacy store to Spring Boot. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"What sequence would let FoxgloveSpruceDaemonStore adopt GraphQL 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.65,"slice":"boundary","lang":"en"} -{"prompt":"Could the reasoning behind FoxgloveBirchMigratorService's Spring Boot choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"PM is preparing the FoxgloveFrostPanelService 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 FoxgloveFrostPanelService\n- cover the awkward empty and retry states\n\nSeveral teams work in this observability, SwiftUI, Redis monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Dashboard: projects/foxglove/ui/settings/PrivacyPane.tsx has grown through several launches, and FoxgloveSummitProxyService now mixes policy, transport, persistence, and metrics in one place. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- cover the awkward empty and retry states\n- stay compatible with the existing GraphQL deployment\n- keep the work scoped to FoxgloveSummitProxyService and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"diff --git a/projects/foxglove/internal/auth/refresh.go b/projects/foxglove/internal/auth/refresh.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/foxglove/internal/auth/refresh.go\n+++ b/projects/foxglove/internal/auth/refresh.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is FoxgloveBasilRunnerFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Worker: // projects/foxglove/config/staging.toml\nfinal class FoxgloveAtlasSearchCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Walk through what the artifact proves about FoxgloveAtlasSearchCoordinator; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"ja"} -{"prompt":"FoxgloveSpruceDaemonCoordinator: could this be clearer","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"Ticket OPS-46137: retire the legacy replay path for FoxgloveMicaProfileFlow\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 FoxgloveMicaProfileFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.62,"slice":"pasted-context","lang":"pt"} -{"prompt":"Simulator: // projects/foxglove/infra/modules/edge/main.tf\nfinal class FoxgloveFrostPanelFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveFrostPanelFlow 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"FoxgloveLumenChartCoordinator: give it a nicer flow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"vague-eval","lang":"en"} -{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current FoxgloveJuniperCLIStore 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 FoxgloveJuniperCLIStore\n- cover the awkward empty and retry states\n\nSeveral teams work in this observability, SwiftUI, Redis monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.69,"slice":"boundary","lang":"en"} -{"prompt":"FoxgloveEmberRelayCoordinator: the screen feels unfinished","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"vague-eval","lang":"en"} -{"prompt":"Incident timeline — INC-46152\n\n08:02 deploy FoxgloveMosaicGridCoordinator 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 FoxgloveMosaicGridCoordinator, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.62,"slice":"pasted-context","lang":"en"} -{"prompt":"Style FoxgloveLedgerGateService's offline state","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"FoxgloveDeltaCanvasCoordinator needs a paired pass: ship the idempotent FoxgloveDeltaCanvasCoordinator replay endpoint, plus capture the contract and rollback note for consumers. Use projects/foxglove/ui/settings/PrivacyPane.tsx as the source of truth, preserve the GraphQL contract, and avoid unrelated cleanup.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Serve FoxglovePrismCacheService health checks","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Ticket OPS-46122: retire the legacy replay path for FoxgloveAsterWebhookFlow\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 FoxgloveAsterWebhookFlow 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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Runbook: projects/foxglove/infra/modules/edge/main.tf now contains FoxgloveBasilRunnerStore's normalization branch three times. Consolidate it behind one private helper, keep call ordering identical, and avoid touching generated code. Please preserve behavior. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"FoxgloveFlintTimelineCoordinator: sort out the rough edge","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"vague-eval","lang":"en"} +{"prompt":"For EquinoxIrisBatchCoordinator, ship the idempotent EquinoxIrisBatchCoordinator replay endpoint; once that is complete, correct the known stale timeout beside it. Work from projects/equinox/services/ledger/replay.go, stay with NATS JetStream, and preserve cancellation and back-pressure semantics. Keep the two outcomes separately reviewable.","purpose":"backendImpl","secondary":"quickFix","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Could the reasoning behind EquinoxRainfallDBStore's NATS JetStream choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/equinox/Sources/App/SessionStore.swift b/projects/equinox/Sources/App/SessionStore.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/equinox/Sources/App/SessionStore.swift\n+++ b/projects/equinox/Sources/App/SessionStore.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit EquinoxSpruceDaemonFlow 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":"Split EquinoxWillowCodecService without behavior changes","purpose":"refactor","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 EquinoxMicaProfileStore design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxMicaProfileStore\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"EquinoxCoralUploadCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Rename EquinoxMicaProfileService's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Unifie les validateurs de EquinoxMarbleTokenStore","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"fr"} +{"prompt":"EquinoxOrbitSyncCoordinator needs a paired pass: find the unknown cause of lease renewal code copied across three workers, plus give the existing implementation a read-only safety pass. Use projects/equinox/cmd/exporter/main.py as the source of truth, preserve the SQLite contract, and avoid unrelated cleanup.","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"The name pendingAck means two different things across EquinoxLedgerGateService's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"EquinoxBasilRunnerCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Skizziere die EquinoxBasilRunnerStore-Migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"de"} +{"prompt":"What is the safest way to split projects/equinox/app/src/main/SyncWorker.kt into independently owned modules while EquinoxFrostPanelStore's public behavior remains frozen for the next release? Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Cinder: Ticket OPS-45153: retire the legacy replay path for EquinoxOpalRouterCoordinator\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 を維持し、根拠と判断を明確にしてください。 Assess EquinoxOpalRouterCoordinator 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":"EquinoxMicaProfileCoordinator is blocking the next release because lost focus when the drawer animation finishes. I need two concrete outcomes from a single pass: lay out a staged migration for EquinoxMicaProfileCoordinator, and consolidate the duplicated normalization paths without changing behavior. Use the existing Tokio conventions in projects/equinox/src/sync/reconcile.ts; preserve cancellation and back-pressure semantics. 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.9,"slice":"mixed","lang":"en"} +{"prompt":"We need to move EquinoxBeaconStoreService from the legacy store to Tokio. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"// projects/equinox/config/staging.toml\nfinal class EquinoxMarbleTokenFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 EquinoxMarbleTokenFlow 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":"Delta: A copied hex color in EquinoxOspreyJobFlow lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-45114\n\n08:02 deploy EquinoxMicaProfileFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nReconstruct the EquinoxMicaProfileFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Ember: A copied hex color in EquinoxSableParserStore lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'EquinoxQuartzPlayerFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[EquinoxQuartzPlayerFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/equinox/Sources/App/SessionStore.swift:144: error: -[EquinoxQuartzPlayerFlowTests 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 '-[EquinoxQuartzPlayerFlowTests 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 EquinoxQuartzPlayerFlow'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":"EquinoxWrenExportCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Ticket OPS-45135: retire the legacy replay path for EquinoxCoralUploadFlow\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 EquinoxCoralUploadFlow 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":"Center the EquinoxSpruceDaemonStore modal","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Frost: diff --git a/projects/equinox/packages/api/openapi.yaml b/projects/equinox/packages/api/openapi.yaml\nindex 62d71aa..90f3c1e 100644\n--- a/projects/equinox/packages/api/openapi.yaml\n+++ b/projects/equinox/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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Read the artifact above as a skeptical reviewer. Is EquinoxAcornWidgetFlow'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":"EquinoxFrostPanelCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"EquinoxQuartzPlayerService 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":"Garnet: projects/equinox/db/migrations/20260730_events.sql now contains EquinoxPineMetricsStore'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":"Harbor: projects/equinox/crates/index/src/segment.rs has grown through several launches, and EquinoxTideWorkerService now mixes policy, transport, persistence, and metrics in one place. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- preserve cancellation and back-pressure semantics\n- stay compatible with the existing WebGPU deployment\n- keep the work scoped to EquinoxTideWorkerService and its direct tests\n\nSeveral teams work in this identity, Rust CLI, Vue 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":"Does EquinoxPrismCacheStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Spell EquinoxKiteSchedulerStore's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"EquinoxJuniperCLICoordinator: sort out the rough edge","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","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_45148'\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_45148'::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\nAdd the bounded EquinoxCopperBridgeFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add a bounded EquinoxCloudReconcilerStore export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Since the last release, EquinoxOspreyJobService has shown timestamps rendered one day ahead near UTC midnight; nobody on the team can reproduce it reliably on a laptop. Reconstruct the failing timeline from logs and tests, identify which invariant first breaks, and distinguish causal signals from effects or cleanup noise.\n\nConstraints:\n- preserve cancellation and back-pressure semantics\n- stay compatible with the existing PostgreSQL 17 deployment\n- keep the work scoped to EquinoxOspreyJobService and its direct tests\n\nSeveral teams work in this identity, Rust CLI, Vue monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Release engineering needs a EquinoxCopperBridgeStore 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":"En projects/equinox/cmd/exporter/main.py, EquinoxOpalRouterService tiene un problema intermitente en el flujo de SQLite. Termina el layout responsive, estados vacío y retry, foco por teclado, dark mode y reduced motion.\n\nRestricciones:\n- seguir con SQLite\n- conservar compatibilidad y cancelación\n- limitar el cambio a EquinoxOpalRouterService","purpose":"frontendImpl","secondary":"debugging","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"es"} +{"prompt":"Give EquinoxOspreyJobStore'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.5,"slice":"core","lang":"en"} +{"prompt":"The next client release depends on a new EquinoxRavenSessionStore capability in projects/equinox/crates/index/src/segment.rs, with WebGPU already chosen by the platform group. Wire the schema, repository, handler, and worker so duplicate deliveries return the original result and shutdown never acknowledges uncommitted work.\n\nConstraints:\n- preserve cancellation and back-pressure semantics\n- stay compatible with the existing WebGPU deployment\n- keep the work scoped to EquinoxRavenSessionStore and its direct tests\n\nSeveral teams work in this identity, Rust CLI, Vue monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Support wants the behavior in projects/equinox/web/components/FilterDrawer.vue recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Test Suite 'EquinoxEmberRelayFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[EquinoxEmberRelayFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/equinox/lib/codec/frame.cc:144: error: -[EquinoxEmberRelayFlowTests 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 '-[EquinoxEmberRelayFlowTests 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 EquinoxEmberRelayFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":"debugging","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Iris: Test Suite 'EquinoxEchoRegistryFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[EquinoxEchoRegistryFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/equinox/crates/index/src/segment.rs:144: error: -[EquinoxEchoRegistryFlowTests 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 '-[EquinoxEchoRegistryFlowTests 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\nFinish the visible EquinoxEchoRegistryFlow 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":"Design the EquinoxOrbitSyncService rollback","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"EquinoxEmberRelayCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"# projects/equinox/services/ledger/replay.go\n[worker.equinoxfernsnapshotflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.equinoxfernsnapshotflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.equinoxfernsnapshotflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.EquinoxFernSnapshotFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-45141\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 EquinoxFernSnapshotFlow'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":"Could the reasoning behind EquinoxDeltaCanvasFlow's SQLite choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Flip EquinoxLumenChartService's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Ownership of EquinoxFlintTimelineStore is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current SQLite operational envelope\n\nThe relevant code crosses identity, Rust CLI, Vue. Prefer evidence from the repository and make any assumption explicit.\n\nReturn the restructuring sequence and decision points, not the edits themselves.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add a bounded EquinoxLedgerGateStore export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Polish the EquinoxVelaDrawerService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"How does EquinoxFernSnapshotService propagate cancellation through the NATS JetStream boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Collapse the EquinoxIrisBatchStore wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"We expect EquinoxDeltaCanvasService to outgrow its current SQLite arrangement next quarter, but changing everything at once would be risky. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- preserve cancellation and back-pressure semantics\n- stay compatible with the existing SQLite deployment\n- keep the work scoped to EquinoxDeltaCanvasService and its direct tests\n\nSeveral teams work in this identity, Rust CLI, Vue monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Juniper: # projects/equinox/crates/index/src/segment.rs\n[worker.equinoxledgergateflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.equinoxledgergateflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.equinoxledgergateflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.EquinoxLedgerGateFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-45142\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/equinox/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":"Kestrel: We need to move EquinoxTideWorkerStore from the legacy store to WebGPU. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Responsive layout for EquinoxOrbitSyncStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-45149\n\n08:02 deploy EquinoxAsterWebhookFlow 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 EquinoxAsterWebhookFlow 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":"EquinoxMarbleTokenCoordinator needs a paired pass: produce a consumer guide for EquinoxMarbleTokenCoordinator, plus correct the known stale timeout beside it. Use projects/equinox/packages/api/openapi.yaml as the source of truth, preserve the WebGPU contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Lumen: Incident timeline — INC-45155\n\n08:02 deploy EquinoxOspreyJobCoordinator 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 EquinoxOspreyJobCoordinator migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Wire a EquinoxOpalRouterStore background task in projects/equinox/ml/pipeline/features.py that expires abandoned sessions, records an OpenTelemetry span, and yields cleanly when shutdown begins.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Read projects/equinox/lib/codec/frame.cc and tell me whether EquinoxCloudReconcilerFlow can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"EquinoxAtlasSearchCoordinator needs a paired pass: separate EquinoxAtlasSearchCoordinator's policy from transport without behavior changes, plus give the existing implementation a read-only safety pass. Use projects/equinox/lib/codec/frame.cc as the source of truth, preserve the PostgreSQL 17 contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Maple: Incident timeline — INC-45133\n\n08:02 deploy EquinoxOrbitSyncFlow 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 EquinoxOrbitSyncFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"EquinoxRainfallDBCoordinator: give it a nicer flow","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Nimbus: projects/equinox/cmd/exporter/main.py の EquinoxJuniperCLIService で、SQLite の flow に断続的な問題が起きています。 原因は判明済みです。staging timeout だけを 15 秒から 30 秒へ変え、対応する assertion を直してください。\n\n制約:\n- SQLite を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は EquinoxJuniperCLIService のみ","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"ja"} +{"prompt":"UI ticket DES-45139: finish the compact EquinoxFrostPanelFlow filter experience\n\nRoute: /catalog/search\nSource: projects/equinox/apps/console/routes/usage.svelte\nFramework: Tokio\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring EquinoxFrostPanelFlow'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":"For EquinoxSummitProxyCoordinator, separate EquinoxSummitProxyCoordinator's policy from transport without behavior changes; once that is complete, capture the contract and rollback note for consumers. Work from projects/equinox/Sources/App/SessionStore.swift, stay with SQLite, and preserve cancellation and back-pressure semantics. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"EquinoxHarborIndexCoordinator: handle the lingering thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"diff --git a/projects/equinox/Sources/App/SessionStore.swift b/projects/equinox/Sources/App/SessionStore.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/equinox/Sources/App/SessionStore.swift\n+++ b/projects/equinox/Sources/App/SessionStore.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is EquinoxDeltaCanvasCoordinator'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":"EquinoxAsterWebhookCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"// projects/equinox/web/components/FilterDrawer.vue\nfinal class EquinoxIrisBatchFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 EquinoxIrisBatchFlow 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":"How should EquinoxAtlasSearchService be decomposed?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Fresh release brief for EquinoxMoonlitSDKCoordinator:\n- primary outcome: lay out a staged migration for EquinoxMoonlitSDKCoordinator\n- companion outcome: then implement the bounded durable-cursor handler\n- repository entry point: projects/equinox/lib/codec/frame.cc\n- platform constraint: PostgreSQL 17\n- known complication: a deadlock that appears only during shutdown\n\nBoth results are required, but they should remain independently reviewable. Preserve cancellation and back-pressure semantics; retain serialization and authorization boundaries; cover cancellation, idempotent retries, and rollback; and avoid drive-by cleanup. Use the code as the source of truth, call out assumptions, and state how an on-call engineer can tell that either part is unsafe to ship.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Fresh release brief for EquinoxFlintTimelineCoordinator:\n- primary outcome: assess ownership and failure handling in projects/equinox/cmd/exporter/main.py\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/equinox/cmd/exporter/main.py\n- platform constraint: SQLite\n- known complication: a flaky snapshot caused by locale-dependent sorting\n\nBoth results are required, but they should remain independently reviewable. Preserve cancellation and back-pressure semantics; 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":"EquinoxBirchMigratorCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"EquinoxCopperBridgeCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"On compact widths, EquinoxQuartzPlayerStore'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":"Memory attributed to EquinoxPineMetricsService rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Could the reasoning behind EquinoxTideWorkerFlow's WebGPU choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"EquinoxSpruceDaemonCoordinator: document, then correct","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Ticket OPS-45117: retire the legacy replay path for EquinoxBirchMigratorFlow\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 EquinoxBirchMigratorFlow 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":"EquinoxEchoRegistryCoordinator: sequence, then ship","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"diff --git a/projects/equinox/infra/modules/edge/main.tf b/projects/equinox/infra/modules/edge/main.tf\nindex 62d71aa..90f3c1e 100644\n--- a/projects/equinox/infra/modules/edge/main.tf\n+++ b/projects/equinox/infra/modules/edge/main.tf\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate EquinoxVelaDrawerFlow'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":"The behavior of EquinoxCloudReconcilerService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/equinox/lib/codec/frame.cc. 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- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current PostgreSQL 17 operational envelope\n\nThe relevant code crosses identity, Rust CLI, Vue. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Ticket OPS-45110: retire the legacy replay path for EquinoxMoonlitSDKFlow\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 EquinoxMoonlitSDKFlow 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":"Compare the old and new EquinoxAsterWebhookStore 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":"En projects/equinox/services/ledger/replay.go, EquinoxNimbusFormStore tiene un problema intermitente en el flujo de NATS JetStream. Propón fases, compatibilidad, métricas, rollback y ownership; detente antes de tocar código.\n\nRestricciones:\n- seguir con NATS JetStream\n- conservar compatibilidad y cancelación\n- limitar el cambio a EquinoxNimbusFormStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con NATS JetStream alrededor de EquinoxNimbusFormStore.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"es"} +{"prompt":"Sketch the EquinoxVelaDrawerStore migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Bring EquinoxCraneWorkspaceStore'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":"EquinoxAsterWebhookService returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/equinox/app/src/main/SyncWorker.kt and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"The EquinoxCopperBridgeService 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":"Sequence EquinoxMosaicGridService's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-45147\n\n08:02 deploy EquinoxHarborIndexFlow 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 EquinoxHarborIndexFlow, 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":"EquinoxLedgerGateCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Flip EquinoxAmberFilterService's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Make EquinoxDriftConsoleStore keyboard navigable","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"projects/equinox/ml/pipeline/features.py 里的 EquinoxJuniperCLIStore 最近在 SQLite 流程中出现间歇性问题。 请实现幂等 endpoint，包含持久 cursor、tenant 鉴权、spans 和 retry 测试。\n\n约束：\n- 继续使用 SQLite\n- 保持兼容性和取消语义\n- 改动只限于 EquinoxJuniperCLIStore","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"zh"} +{"prompt":"Documente o contrato de EquinoxMarbleTokenService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"pt"} +{"prompt":"Opal: projects/equinox/ui/settings/PrivacyPane.tsx 里的 EquinoxCoralUploadService 最近在 PostgreSQL 17 流程中出现间歇性问题。 请阅读现有流程，判断 ownership、取消和顺序是否安全，只需要分析。\n\n约束：\n- 继续使用 PostgreSQL 17\n- 保持兼容性和取消语义\n- 改动只限于 EquinoxCoralUploadService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"zh"} +{"prompt":"Remove EquinoxKiteSchedulerService's stray comma","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Two asks around EquinoxVelaDrawerCoordinator: (1) separate EquinoxVelaDrawerCoordinator's policy from transport without behavior changes; (2) correct the known stale timeout beside it. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Prism: The EquinoxHarborIndexService surface in projects/equinox/config/staging.toml 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":"Quartz: // projects/equinox/workers/thumbnail/consumer.ex\nfinal class EquinoxKiteSchedulerFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nDeliver the EquinoxKiteSchedulerFlow server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Raven: Incident timeline — INC-45145\n\n08:02 deploy EquinoxCedarPolicyFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Map a safe route from the current EquinoxCedarPolicyFlow 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":"How does EquinoxSableParserFlow propagate cancellation through the WebGPU boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"I inherited FoxglovePineMetricsStore and need a careful read of projects/foxglove/services/ledger/replay.go 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- cover the awkward empty and retry states\n- stay compatible with the existing Kafka deployment\n- keep the work scoped to FoxglovePineMetricsStore and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"FoxgloveLumenChartStore returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/foxglove/cmd/exporter/main.py and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"FoxgloveNimbusFormCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Two asks around FoxgloveSableParserCoordinator: (1) assess ownership and failure handling in projects/foxglove/db/migrations/20260730_events.sql; (2) capture the contract and rollback note for consumers. Cover the awkward empty and retry states, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"What does FoxgloveHarborIndexStore own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Sable: Two deliverables are holding up FoxgloveFernSnapshotCoordinator. First, assess ownership and failure handling in projects/foxglove/Sources/App/SessionStore.swift. In the same workstream, capture the contract and rollback note for consumers. The relevant starting point is projects/foxglove/Sources/App/SessionStore.swift, which follows Cloudflare Workers conventions and currently suffers from an accessibility label that reads the internal enum. Cover the awkward empty and retry states.\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":"review","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Tide: projects/foxglove/ui/settings/PrivacyPane.tsx の FoxgloveSummitProxyFlow で、GraphQL の flow に断続的な問題が起きています。 現在の flow を読み、ownership、cancel、順序が安全か評価してください。分析だけで十分です。\n\n制約:\n- GraphQL を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は FoxgloveSummitProxyFlow のみ","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"ja"} +{"prompt":"Release engineering needs a FoxgloveKiteSchedulerService 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":"For FoxgloveGarnetModalCoordinator, change FoxgloveGarnetModalCoordinator's known staging timeout from 15 to 30 seconds; once that is complete, give the existing implementation a read-only safety pass. Work from projects/foxglove/internal/auth/refresh.go, stay with Kafka, and cover the awkward empty and retry states. Keep the two outcomes separately reviewable.","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Incident timeline — INC-46118\n\n08:02 deploy FoxgloveCedarPolicyFlow 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 FoxgloveCedarPolicyFlow 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":"FoxgloveAcornWidgetCoordinator is blocking the next release because an empty state that flashes before cached data arrives. I need two concrete outcomes from a single pass: change FoxgloveAcornWidgetCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing Spring Boot conventions in projects/foxglove/db/migrations/20260730_events.sql; cover the awkward empty and retry states. 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.5,"slice":"mixed","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_46157'\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_46157'::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\nDeliver the FoxgloveBeaconStoreCoordinator server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Pin FoxgloveAsterWebhookService's Kafka dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Umbra: Ticket OPS-46155: retire the legacy replay path for FoxgloveAmberFilterCoordinator\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 FoxgloveAmberFilterCoordinator 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":"Split FoxgloveCedarPolicyStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"FoxgloveBasilRunnerCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Bring FoxgloveMapleQueueStore'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":"Vela: Two deliverables are holding up FoxgloveQuartzPlayerCoordinator. First, separate FoxgloveQuartzPlayerCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/foxglove/ui/settings/PrivacyPane.tsx, which follows GraphQL conventions and currently suffers from a flaky snapshot caused by locale-dependent sorting. Cover the awkward empty and retry states.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"FoxgloveBirchMigratorCoordinator: handle the lingering thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Test Suite 'FoxglovePrismCacheFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[FoxglovePrismCacheFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/foxglove/cmd/exporter/main.py:144: error: -[FoxglovePrismCacheFlowTests 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 '-[FoxglovePrismCacheFlowTests 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 FoxglovePrismCacheFlow'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":"debugging","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Willow: The first FoxgloveAtlasSearchFlow request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"FoxgloveVelaDrawerCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Xylem: Ticket OPS-46141: retire the legacy replay path for FoxgloveSpruceDaemonFlow\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 FoxgloveSpruceDaemonFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Three teams extended FoxgloveAmberFilterService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- cover the awkward empty and retry states\n- retain the current Spring Boot operational envelope\n\nThis repository spans observability, SwiftUI, Redis; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"FoxgloveHarborIndexCoordinator: restructure, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Yarrow: The API work is done; what remains for FoxgloveAcornWidgetStore 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 FoxgloveAcornWidgetStore\n- cover the awkward empty and retry states\n\nSeveral teams work in this observability, SwiftUI, Redis monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Zephyr: Two asks around FoxgloveMoonlitSDKCoordinator: (1) finish FoxgloveMoonlitSDKCoordinator's responsive empty and retry states; (2) give the existing implementation a read-only safety pass. Cover the awkward empty and retry states, and leave a clear boundary between the resulting artifacts or edits.","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"A previously stable test around FoxgloveOrbitSyncFlow now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"FoxgloveRainfallDBCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Checkout: Incident timeline — INC-46130\n\n08:02 deploy FoxgloveSableParserFlow 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 FoxgloveSableParserFlow 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":"For FoxglovePrismCacheCoordinator, finish FoxglovePrismCacheCoordinator's responsive empty and retry states; once that is complete, correct the known stale timeout beside it. Work from projects/foxglove/ml/pipeline/features.py, stay with Cloudflare Workers, and cover the awkward empty and retry states. Keep the two outcomes separately reviewable.","purpose":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Does FoxgloveCoralUploadFlow enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"// projects/foxglove/pkg/cache/lease.rs\nfinal class FoxgloveCinderAuthFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveCinderAuthFlow 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":"FoxgloveBeaconStoreFlow returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/foxglove/services/ledger/replay.go and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Exporter: Incident timeline — INC-46150\n\n08:02 deploy FoxgloveMarbleTokenCoordinator 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 FoxgloveMarbleTokenCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Why does FoxgloveBeaconStoreStore's Kafka worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Scheduler: Incident timeline — INC-46124\n\n08:02 deploy FoxgloveCraneWorkspaceFlow 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 FoxgloveCraneWorkspaceFlow 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":"Extract FoxgloveFernSnapshotService's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"A copied hex color in FoxgloveWrenExportFlow lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fresh release brief for FoxgloveLedgerGateCoordinator:\n- primary outcome: produce a consumer guide for FoxgloveLedgerGateCoordinator\n- companion outcome: give the existing implementation a read-only safety pass\n- repository entry point: projects/foxglove/apps/console/routes/usage.svelte\n- platform constraint: Spring Boot\n- known complication: lease renewal code copied across three workers\n\nBoth results are required, but they should remain independently reviewable. Cover the awkward empty and retry states; 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":"writing","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Spell FoxgloveGarnetModalStore's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"FoxgloveDriftConsoleCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"FoxgloveTideWorkerCoordinator needs a paired pass: produce a consumer guide for FoxgloveTideWorkerCoordinator, plus give the existing implementation a read-only safety pass. Use projects/foxglove/app/src/main/SyncWorker.kt as the source of truth, preserve the Spring Boot contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"The FoxgloveMicaProfileStore surface in projects/foxglove/services/ledger/replay.go 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":"Why does FoxgloveVelaDrawerStore's Cloudflare Workers worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"# projects/foxglove/ui/settings/PrivacyPane.tsx\n[worker.foxglovecopperbridgeflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.foxglovecopperbridgeflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.foxglovecopperbridgeflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.FoxgloveCopperBridgeFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-46121\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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. The intended correction is already known: change only the stale 15-second setting to 30 seconds in projects/foxglove/ui/settings/PrivacyPane.tsx and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"We need to move FoxgloveFlintTimelineStore from the legacy store to GraphQL. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"FoxgloveCloudReconcilerCoordinator: polish, then correct","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Give FoxgloveAsterWebhookStore a README example","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Release engineering needs a FoxgloveBirchMigratorStore 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":"We need to move FoxgloveMarbleTokenStore from the legacy store to Spring Boot. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"What sequence would let FoxgloveSpruceDaemonStore adopt GraphQL 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.8,"slice":"core","lang":"en"} +{"prompt":"Could the reasoning behind FoxgloveBirchMigratorService's Spring Boot choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"PM is preparing the FoxgloveFrostPanelService 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 FoxgloveFrostPanelService\n- cover the awkward empty and retry states\n\nSeveral teams work in this observability, SwiftUI, Redis monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Dashboard: projects/foxglove/ui/settings/PrivacyPane.tsx has grown through several launches, and FoxgloveSummitProxyService now mixes policy, transport, persistence, and metrics in one place. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- cover the awkward empty and retry states\n- stay compatible with the existing GraphQL deployment\n- keep the work scoped to FoxgloveSummitProxyService and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/foxglove/internal/auth/refresh.go b/projects/foxglove/internal/auth/refresh.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/foxglove/internal/auth/refresh.go\n+++ b/projects/foxglove/internal/auth/refresh.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is FoxgloveBasilRunnerFlow'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":"Worker: // projects/foxglove/config/staging.toml\nfinal class FoxgloveAtlasSearchCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Walk through what the artifact proves about FoxgloveAtlasSearchCoordinator; 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":"FoxgloveSpruceDaemonCoordinator: could this be clearer","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Ticket OPS-46137: retire the legacy replay path for FoxgloveMicaProfileFlow\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 FoxgloveMicaProfileFlow, 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":"Simulator: // projects/foxglove/infra/modules/edge/main.tf\nfinal class FoxgloveFrostPanelFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveFrostPanelFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"FoxgloveLumenChartCoordinator: give it a nicer flow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current FoxgloveJuniperCLIStore 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 FoxgloveJuniperCLIStore\n- cover the awkward empty and retry states\n\nSeveral teams work in this observability, SwiftUI, Redis 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":"FoxgloveEmberRelayCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-46152\n\n08:02 deploy FoxgloveMosaicGridCoordinator 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 FoxgloveMosaicGridCoordinator, 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":"Style FoxgloveLedgerGateService's offline state","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"FoxgloveDeltaCanvasCoordinator needs a paired pass: ship the idempotent FoxgloveDeltaCanvasCoordinator replay endpoint, plus capture the contract and rollback note for consumers. Use projects/foxglove/ui/settings/PrivacyPane.tsx as the source of truth, preserve the GraphQL contract, and avoid unrelated cleanup.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Serve FoxglovePrismCacheService health checks","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-46122: retire the legacy replay path for FoxgloveAsterWebhookFlow\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 FoxgloveAsterWebhookFlow 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":"Runbook: projects/foxglove/infra/modules/edge/main.tf now contains FoxgloveBasilRunnerStore's normalization branch three times. Consolidate it behind one private helper, keep call ordering identical, and avoid touching generated code. Please preserve behavior. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"FoxgloveFlintTimelineCoordinator: sort out the rough edge","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"Compare the old and new FoxgloveAmberFilterStore 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":"Since the last release, FoxgloveSlateEditorService 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- cover the awkward empty and retry states\n- stay compatible with the existing Kotlin coroutines deployment\n- keep the work scoped to FoxgloveSlateEditorService and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.87,"slice":"core","lang":"en"} -{"prompt":"Trace: projects/foxglove/app/src/main/SyncWorker.kt 里的 FoxgloveRavenSessionService 最近在 Spring Boot 流程中出现间歇性问题。 请写一份面向调用方的说明，包含 contract、错误、retry 和可复制示例，不要改 handler。\n\n约束：\n- 继续使用 Spring Boot\n- 保持兼容性和取消语义\n- 改动只限于 FoxgloveRavenSessionService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"zh"} -{"prompt":"FoxgloveAsterWebhookCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.48,"slice":"mixed","lang":"en"} -{"prompt":"Diff: projects/foxglove/services/ledger/replay.go has grown through several launches, and FoxgloveBeaconStoreService now mixes policy, transport, persistence, and metrics in one place. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- cover the awkward empty and retry states\n- stay compatible with the existing Kafka deployment\n- keep the work scoped to FoxgloveBeaconStoreService and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Before we approve FoxgloveCinderAuthStore, assess whether two validators with subtly different error strings is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"The FoxgloveAmberFilterFlow surface in projects/foxglove/apps/console/routes/usage.svelte 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.33,"slice":"boundary","lang":"en"} -{"prompt":"FoxgloveCedarPolicyCoordinator: diagnose, then correct","purpose":"debugging","secondary":"quickFix","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"Profiler: The FoxgloveLumenChartService empty state in projects/foxglove/ml/pipeline/features.py needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Lay out a two-milestone strategy for eliminating an accessibility label that reads the internal enum in FoxgloveMosaicGridStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Does FoxgloveCloudReconcilerService preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Extract FoxgloveOspreyJobStore's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"FoxgloveAtlasSearchStore'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.17,"slice":"core","lang":"en"} -{"prompt":"// projects/foxglove/engine/render/atlas.cpp\nfinal class FoxgloveFlintTimelineFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveFlintTimelineFlow 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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Introduce a durable deduplication key for FoxgloveDriftConsoleService events and enforce it in both the database migration and the ingestion path.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"FoxgloveSlateEditorCoordinator is blocking the next release because timestamps rendered one day ahead near UTC midnight. I need two concrete outcomes from a single pass: assess ownership and failure handling in projects/foxglove/packages/api/openapi.yaml, and capture the contract and rollback note for consumers. Use the existing Kotlin coroutines conventions in projects/foxglove/packages/api/openapi.yaml; cover the awkward empty and retry states. 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":"review","secondary":"writing","mixed":true,"difficulty":0.84,"slice":"mixed","lang":"en"} -{"prompt":"FoxgloveCopperBridgeCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.45,"slice":"mixed","lang":"en"} -{"prompt":"Make FoxgloveJuniperCLIService keyboard navigable","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"Console: # projects/foxglove/ml/pipeline/features.py\n[worker.foxglovewrenexportcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.foxglovewrenexportcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.foxglovewrenexportcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.FoxgloveWrenExportCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-46159\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/foxglove/ml/pipeline/features.py. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.43,"slice":"pasted-context","lang":"en"} -{"prompt":"FoxgloveCinderAuthCoordinator: clean up that old path","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"vague-eval","lang":"en"} -{"prompt":"FoxglovePineMetricsCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"Give FoxgloveEchoRegistryStore'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.44,"slice":"boundary","lang":"en"} -{"prompt":"Decouple FoxgloveDeltaCanvasService's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Summarize the FoxgloveCopperBridgeService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"The behavior of FoxgloveLedgerGateStore is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/foxglove/apps/console/routes/usage.svelte. 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- cover the awkward empty and retry states\n- retain the current Spring Boot operational envelope\n\nThis repository spans observability, SwiftUI, Redis; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.49,"slice":"boundary","lang":"en"} -{"prompt":"Describe FoxgloveOpalRouterService's error envelope","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"// projects/foxglove/engine/render/atlas.cpp\nfinal class FoxgloveJuniperCLIFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveJuniperCLIFlow'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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Workspace: Ticket OPS-46131: retire the legacy replay path for FoxgloveDeltaCanvasFlow\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 FoxgloveDeltaCanvasFlow 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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Por que FoxgloveNovaPickerService trava?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"pt"} -{"prompt":"FoxgloveKiteSchedulerCoordinator: deal with the small issue","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"vague-eval","lang":"en"} -{"prompt":"Store FoxgloveCloudReconcilerStore's delivery receipts","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"FoxgloveRavenSessionCoordinator: make this less weird","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"vague-eval","lang":"en"} -{"prompt":"Repository: // projects/foxglove/infra/modules/edge/main.tf\nfinal class FoxgloveGarnetModalFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveGarnetModalFlow 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Release engineering needs a FoxgloveMosaicGridFlow changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"en"} -{"prompt":"Pipeline: # projects/foxglove/src/sync/reconcile.ts\n[worker.foxgloveacornwidgetflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.foxgloveacornwidgetflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.foxgloveacornwidgetflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.FoxgloveAcornWidgetFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-46110\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 FoxgloveAcornWidgetFlow'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.33,"slice":"pasted-context","lang":"en"} -{"prompt":"En projects/foxglove/ui/settings/PrivacyPane.tsx, FoxgloveQuartzPlayerStore tiene un problema intermitente en el flujo de GraphQL. Propón fases, compatibilidad, métricas, rollback y ownership; detente antes de tocar código.\n\nRestricciones:\n- seguir con GraphQL\n- conservar compatibilidad y cancelación\n- limitar el cambio a FoxgloveQuartzPlayerStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con GraphQL alrededor de FoxgloveQuartzPlayerStore.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.81,"slice":"boundary","lang":"es"} -{"prompt":"Gateway: Ticket OPS-46135: retire the legacy replay path for FoxgloveRavenSessionFlow\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 FoxgloveRavenSessionFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Renderer: The name pendingAck means two different things across FoxgloveNimbusFormService's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"For FoxgloveOpalRouterCoordinator, assess ownership and failure handling in projects/foxglove/engine/render/atlas.cpp; once that is complete, capture the contract and rollback note for consumers. Work from projects/foxglove/engine/render/atlas.cpp, stay with GraphQL, and cover the awkward empty and retry states. Keep the two outcomes separately reviewable.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.62,"slice":"mixed","lang":"en"} -{"prompt":"FoxgloveEchoRegistryCoordinator: maybe tighten this up","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"vague-eval","lang":"en"} -{"prompt":"Compare the old and new FoxgloveVelaDrawerService adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Read projects/foxglove/Sources/App/SessionStore.swift and tell me whether FoxgloveWillowCodecService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Could FoxgloveMarbleTokenFlow show the active Spring Boot sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"boundary","lang":"en"} -{"prompt":"Since the last release, FoxgloveCoralUploadStore has shown a misleading timeout name used in five packages; 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- cover the awkward empty and retry states\n- stay compatible with the existing Kotlin coroutines deployment\n- keep the work scoped to FoxgloveCoralUploadStore and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.87,"slice":"boundary","lang":"en"} -{"prompt":"Center the FoxgloveTideWorkerStore modal","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"boundary","lang":"en"} -{"prompt":"Spell FoxgloveCraneWorkspaceStore's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"boundary","lang":"en"} -{"prompt":"Ticket OPS-46123: retire the legacy replay path for FoxgloveCloudReconcilerFlow\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 FoxgloveCloudReconcilerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.65,"slice":"pasted-context","lang":"en"} -{"prompt":"FoxgloveJuniperCLICoordinator: ship, then document","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Two asks around FoxgloveNovaPickerCoordinator: (1) change FoxgloveNovaPickerCoordinator's known staging timeout from 15 to 30 seconds; (2) capture the contract and rollback note for consumers. Cover the awkward empty and retry states, and leave a clear boundary between the resulting artifacts or edits.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.24,"slice":"mixed","lang":"en"} -{"prompt":"FoxgloveKiteSchedulerStore's staging timeout is already known to be wrong: change the single projects/foxglove/pkg/cache/lease.rs value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"boundary","lang":"en"} -{"prompt":"Trace FoxgloveHarborIndexService's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current FoxgloveWrenExportService 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 FoxgloveWrenExportService\n- cover the awkward empty and retry states\n\nSeveral teams work in this observability, SwiftUI, Redis monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Two asks around FoxgloveCraneWorkspaceCoordinator: (1) find the unknown cause of a deadlock that appears only during shutdown; (2) correct the known stale timeout beside it. Cover the awkward empty and retry states, and leave a clear boundary between the resulting artifacts or edits.","purpose":"debugging","secondary":"quickFix","mixed":true,"difficulty":0.83,"slice":"mixed","lang":"en"} -{"prompt":"UI ticket DES-46154: finish the compact FoxgloveIrisBatchCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/foxglove/Sources/CLI/Commands/Doctor.swift\nFramework: Cloudflare Workers\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 FoxgloveIrisBatchCoordinator 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.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Indexer: // projects/foxglove/Sources/CLI/Commands/Doctor.swift\nfinal class FoxgloveFernSnapshotFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nAdd the bounded FoxgloveFernSnapshotFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"diff --git a/projects/foxglove/ml/pipeline/features.py b/projects/foxglove/ml/pipeline/features.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/foxglove/ml/pipeline/features.py\n+++ b/projects/foxglove/ml/pipeline/features.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\nRead the artifact above as a skeptical reviewer. Is FoxgloveLumenChartFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Incident timeline — INC-46126\n\n08:02 deploy FoxgloveOpalRouterFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current FoxgloveOpalRouterFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"The data is already available in projects/foxglove/Sources/CLI/Commands/Doctor.swift; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} +{"prompt":"Since the last release, FoxgloveSlateEditorService 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- cover the awkward empty and retry states\n- stay compatible with the existing Kotlin coroutines deployment\n- keep the work scoped to FoxgloveSlateEditorService and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Trace: projects/foxglove/app/src/main/SyncWorker.kt 里的 FoxgloveRavenSessionService 最近在 Spring Boot 流程中出现间歇性问题。 请写一份面向调用方的说明，包含 contract、错误、retry 和可复制示例，不要改 handler。\n\n约束：\n- 继续使用 Spring Boot\n- 保持兼容性和取消语义\n- 改动只限于 FoxgloveRavenSessionService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"zh"} +{"prompt":"FoxgloveAsterWebhookCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Diff: projects/foxglove/services/ledger/replay.go has grown through several launches, and FoxgloveBeaconStoreService now mixes policy, transport, persistence, and metrics in one place. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- cover the awkward empty and retry states\n- stay compatible with the existing Kafka deployment\n- keep the work scoped to FoxgloveBeaconStoreService and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Before we approve FoxgloveCinderAuthStore, assess whether two validators with subtly different error strings is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"The FoxgloveAmberFilterFlow surface in projects/foxglove/apps/console/routes/usage.svelte 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":"FoxgloveCedarPolicyCoordinator: diagnose, then correct","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Profiler: The FoxgloveLumenChartService empty state in projects/foxglove/ml/pipeline/features.py needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating an accessibility label that reads the internal enum in FoxgloveMosaicGridStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Does FoxgloveCloudReconcilerService preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Extract FoxgloveOspreyJobStore's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"FoxgloveAtlasSearchStore's metric is misspelled as succesful_total in one declaration. Correct that literal and its exact test expectation, without renaming anything else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"// projects/foxglove/engine/render/atlas.cpp\nfinal class FoxgloveFlintTimelineFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveFlintTimelineFlow 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":"Introduce a durable deduplication key for FoxgloveDriftConsoleService 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":"FoxgloveSlateEditorCoordinator is blocking the next release because timestamps rendered one day ahead near UTC midnight. I need two concrete outcomes from a single pass: assess ownership and failure handling in projects/foxglove/packages/api/openapi.yaml, and capture the contract and rollback note for consumers. Use the existing Kotlin coroutines conventions in projects/foxglove/packages/api/openapi.yaml; cover the awkward empty and retry states. 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":"review","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"FoxgloveCopperBridgeCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Make FoxgloveJuniperCLIService keyboard navigable","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Console: # projects/foxglove/ml/pipeline/features.py\n[worker.foxglovewrenexportcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.foxglovewrenexportcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.foxglovewrenexportcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.FoxgloveWrenExportCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-46159\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/foxglove/ml/pipeline/features.py. 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":"FoxgloveCinderAuthCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"FoxglovePineMetricsCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Give FoxgloveEchoRegistryStore'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":"Decouple FoxgloveDeltaCanvasService's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Summarize the FoxgloveCopperBridgeService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"The behavior of FoxgloveLedgerGateStore is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/foxglove/apps/console/routes/usage.svelte. 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- cover the awkward empty and retry states\n- retain the current Spring Boot operational envelope\n\nThis repository spans observability, SwiftUI, Redis; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Describe FoxgloveOpalRouterService's error envelope","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"// projects/foxglove/engine/render/atlas.cpp\nfinal class FoxgloveJuniperCLIFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveJuniperCLIFlow'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":"Workspace: Ticket OPS-46131: retire the legacy replay path for FoxgloveDeltaCanvasFlow\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 FoxgloveDeltaCanvasFlow 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":"Por que FoxgloveNovaPickerService trava?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"pt"} +{"prompt":"FoxgloveKiteSchedulerCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Store FoxgloveCloudReconcilerStore's delivery receipts","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"FoxgloveRavenSessionCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Repository: // projects/foxglove/infra/modules/edge/main.tf\nfinal class FoxgloveGarnetModalFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveGarnetModalFlow 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":"Release engineering needs a FoxgloveMosaicGridFlow 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":"Pipeline: # projects/foxglove/src/sync/reconcile.ts\n[worker.foxgloveacornwidgetflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.foxgloveacornwidgetflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.foxgloveacornwidgetflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.FoxgloveAcornWidgetFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-46110\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 FoxgloveAcornWidgetFlow'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":"En projects/foxglove/ui/settings/PrivacyPane.tsx, FoxgloveQuartzPlayerStore tiene un problema intermitente en el flujo de GraphQL. Propón fases, compatibilidad, métricas, rollback y ownership; detente antes de tocar código.\n\nRestricciones:\n- seguir con GraphQL\n- conservar compatibilidad y cancelación\n- limitar el cambio a FoxgloveQuartzPlayerStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con GraphQL alrededor de FoxgloveQuartzPlayerStore.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"es"} +{"prompt":"Gateway: Ticket OPS-46135: retire the legacy replay path for FoxgloveRavenSessionFlow\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 FoxgloveRavenSessionFlow 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":"Renderer: The name pendingAck means two different things across FoxgloveNimbusFormService's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"For FoxgloveOpalRouterCoordinator, assess ownership and failure handling in projects/foxglove/engine/render/atlas.cpp; once that is complete, capture the contract and rollback note for consumers. Work from projects/foxglove/engine/render/atlas.cpp, stay with GraphQL, and cover the awkward empty and retry states. Keep the two outcomes separately reviewable.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"FoxgloveEchoRegistryCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Compare the old and new FoxgloveVelaDrawerService 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":"Read projects/foxglove/Sources/App/SessionStore.swift and tell me whether FoxgloveWillowCodecService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Could FoxgloveMarbleTokenFlow show the active Spring Boot sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Since the last release, FoxgloveCoralUploadStore has shown a misleading timeout name used in five packages; 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- cover the awkward empty and retry states\n- stay compatible with the existing Kotlin coroutines deployment\n- keep the work scoped to FoxgloveCoralUploadStore and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Center the FoxgloveTideWorkerStore modal","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Spell FoxgloveCraneWorkspaceStore's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-46123: retire the legacy replay path for FoxgloveCloudReconcilerFlow\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 FoxgloveCloudReconcilerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"FoxgloveJuniperCLICoordinator: ship, then document","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Two asks around FoxgloveNovaPickerCoordinator: (1) change FoxgloveNovaPickerCoordinator's known staging timeout from 15 to 30 seconds; (2) capture the contract and rollback note for consumers. Cover the awkward empty and retry states, and leave a clear boundary between the resulting artifacts or edits.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"FoxgloveKiteSchedulerStore's staging timeout is already known to be wrong: change the single projects/foxglove/pkg/cache/lease.rs value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Trace FoxgloveHarborIndexService's memory growth","purpose":"debugging","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 FoxgloveWrenExportService 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 FoxgloveWrenExportService\n- cover the awkward empty and retry states\n\nSeveral teams work in this observability, SwiftUI, Redis 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":"Two asks around FoxgloveCraneWorkspaceCoordinator: (1) find the unknown cause of a deadlock that appears only during shutdown; (2) correct the known stale timeout beside it. Cover the awkward empty and retry states, 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":"UI ticket DES-46154: finish the compact FoxgloveIrisBatchCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/foxglove/Sources/CLI/Commands/Doctor.swift\nFramework: Cloudflare Workers\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 FoxgloveIrisBatchCoordinator 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":"Indexer: // projects/foxglove/Sources/CLI/Commands/Doctor.swift\nfinal class FoxgloveFernSnapshotFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nAdd the bounded FoxgloveFernSnapshotFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"diff --git a/projects/foxglove/ml/pipeline/features.py b/projects/foxglove/ml/pipeline/features.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/foxglove/ml/pipeline/features.py\n+++ b/projects/foxglove/ml/pipeline/features.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\nRead the artifact above as a skeptical reviewer. Is FoxgloveLumenChartFlow'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":"Incident timeline — INC-46126\n\n08:02 deploy FoxgloveOpalRouterFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current FoxgloveOpalRouterFlow 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":"The data is already available in projects/foxglove/Sources/CLI/Commands/Doctor.swift; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Split FoxgloveOspreyJobService without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"FoxgloveMapleQueueCoordinator: polish the last piece","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} -{"prompt":"Apparently: # projects/foxglove/apps/console/routes/usage.svelte\n[worker.foxgloveechoregistryflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.foxgloveechoregistryflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.foxgloveechoregistryflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.FoxgloveEchoRegistryFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-46145\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 The intended correction is already known: change only the stale 15-second setting to 30 seconds in projects/foxglove/apps/console/routes/usage.svelte and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"pasted-context","lang":"zh"} -{"prompt":"Milestones for replacing FoxglovePineMetricsService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Does FoxglovePrismCacheStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"This should remain a deliberately small patch: FoxgloveAcornWidgetService has one known configuration mistake in projects/foxglove/src/sync/reconcile.ts, 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- cover the awkward empty and retry states\n- stay compatible with the existing Spring Boot deployment\n- keep the work scoped to FoxgloveAcornWidgetService and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.25,"slice":"core","lang":"en"} -{"prompt":"// projects/foxglove/Sources/App/SessionStore.swift\nfinal class FoxgloveWillowCodecFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveWillowCodecFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Fresh release brief for FoxgloveFrostPanelCoordinator:\n- primary outcome: change FoxgloveFrostPanelCoordinator'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/foxglove/internal/auth/refresh.go\n- platform constraint: Kafka\n- known complication: lost focus when the drawer animation finishes\n\nBoth results are required, but they should remain independently reviewable. Cover the awkward empty and retry states; 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.4,"slice":"mixed","lang":"en"} -{"prompt":"Ticket OPS-46143: retire the legacy replay path for FoxgloveEmberRelayFlow\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 FoxgloveEmberRelayFlow rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"pasted-context","lang":"en"} -{"prompt":"diff --git a/projects/foxglove/ml/pipeline/features.py b/projects/foxglove/ml/pipeline/features.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/foxglove/ml/pipeline/features.py\n+++ b/projects/foxglove/ml/pipeline/features.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 FoxgloveRainfallDBFlow'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.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Release engineering needs a FoxgloveNimbusFormStore changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"boundary","lang":"en"} -{"prompt":"FoxgloveMicaProfileCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"vague-eval","lang":"en"} -{"prompt":"Give FoxgloveMapleQueueService'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.49,"slice":"core","lang":"en"} -{"prompt":"Warum hängt FoxgloveRainfallDBStore?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","lang":"de"} -{"prompt":"Lately: // projects/foxglove/engine/render/atlas.cpp\nfinal class FoxgloveOrbitSyncCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveOrbitSyncCoordinator 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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Oddly: diff --git a/projects/foxglove/app/src/main/SyncWorker.kt b/projects/foxglove/app/src/main/SyncWorker.kt\nindex 62d71aa..90f3c1e 100644\n--- a/projects/foxglove/app/src/main/SyncWorker.kt\n+++ b/projects/foxglove/app/src/main/SyncWorker.kt\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure FoxgloveLedgerGateFlow 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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Map FoxgloveCopperBridgeStore's ownership split","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"Dedupe FoxgloveCedarPolicyService's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"On compact widths, FoxgloveIrisBatchFlow'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.54,"slice":"boundary","lang":"en"} -{"prompt":"The minimum supported GraphQL version in projects/foxglove/engine/render/atlas.cpp is one patch behind the lockfile. Align that single value and regenerate only the affected metadata.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"boundary","lang":"en"} -{"prompt":"Incident timeline — INC-46134\n\n08:02 deploy FoxgloveNimbusFormFlow 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 FoxgloveNimbusFormFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.67,"slice":"pasted-context","lang":"en"} -{"prompt":"Design the FoxgloveGarnetModalService rollback","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Corrige le timeout de FoxgloveNovaPickerStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"boundary","lang":"fr"} -{"prompt":"Move FoxgloveSpruceDaemonService'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.55,"slice":"core","lang":"en"} -{"prompt":"Store FoxgloveTideWorkerService's delivery receipts","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Pin FoxgloveSableParserService's Spring dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"core","lang":"en"} -{"prompt":"projects/foxglove/packages/api/openapi.yaml の FoxgloveEmberRelayService で、Kotlin coroutines の flow に断続的な問題が起きています。 段階、互換性、metrics、rollback、ownership を提案し、コード変更の前で止めてください。\n\n制約:\n- Kotlin coroutines を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は FoxgloveEmberRelayService のみ","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"} -{"prompt":"Please resist widening this one: FoxgloveSlateEditorStore works, but staging still carries a setting that production corrected last month. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside FoxgloveSlateEditorStore\n- cover the awkward empty and retry states\n\nSeveral teams work in this observability, SwiftUI, Redis monorepo, so keep ownership and handoff points understandable in a small review.\n\nThe cause and exact value change are already known, so keep this as a contained correction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"boundary","lang":"en"} -{"prompt":"UI ticket DES-46128: finish the compact FoxgloveOspreyJobFlow filter experience\n\nRoute: /catalog/search\nSource: projects/foxglove/crates/index/src/segment.rs\nFramework: Kotlin coroutines\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 FoxgloveOspreyJobFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.76,"slice":"pasted-context","lang":"en"} -{"prompt":"Why does FoxgloveSummitProxyStore's GraphQL worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Test Suite 'FoxgloveVelaDrawerFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[FoxgloveVelaDrawerFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/foxglove/cmd/exporter/main.py:144: error: -[FoxgloveVelaDrawerFlowTests 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 '-[FoxgloveVelaDrawerFlowTests 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 FoxgloveVelaDrawerFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Currently: diff --git a/projects/foxglove/workers/thumbnail/consumer.ex b/projects/foxglove/workers/thumbnail/consumer.ex\nindex 62d71aa..90f3c1e 100644\n--- a/projects/foxglove/workers/thumbnail/consumer.ex\n+++ b/projects/foxglove/workers/thumbnail/consumer.ex\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 FoxgloveQuartzPlayerFlow 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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Today: // projects/foxglove/db/migrations/20260730_events.sql\nfinal class FoxgloveBirchMigratorFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveBirchMigratorFlow'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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"FoxgloveOspreyJobCoordinator needs a paired pass: produce a consumer guide for FoxgloveOspreyJobCoordinator, plus give the existing implementation a read-only safety pass. Use projects/foxglove/pkg/cache/lease.rs as the source of truth, preserve the Kotlin coroutines contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.51,"slice":"mixed","lang":"en"} -{"prompt":"Context: # projects/foxglove/workers/thumbnail/consumer.ex\n[worker.foxglovesummitproxycoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.foxglovesummitproxycoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.foxglovesummitproxycoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.FoxgloveSummitProxyCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-46151\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/foxglove/workers/thumbnail/consumer.ex and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.36,"slice":"pasted-context","lang":"en"} -{"prompt":"Background: projects/foxglove/config/staging.toml 里的 FoxgloveEmberRelayStore 最近在 Kotlin coroutines 流程中出现间歇性问题。 请给出阶段、兼容层、指标、rollback 和 ownership，先不要修改代码。\n\n约束：\n- 继续使用 Kotlin coroutines\n- 保持兼容性和取消语义\n- 改动只限于 FoxgloveEmberRelayStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"zh"} -{"prompt":"FoxgloveMosaicGridService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- cover the awkward empty and retry states\n- retain the current Kafka operational envelope\n\nThis repository spans observability, SwiftUI, Redis; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Question: diff --git a/projects/foxglove/config/staging.toml b/projects/foxglove/config/staging.toml\nindex 62d71aa..90f3c1e 100644\n--- a/projects/foxglove/config/staging.toml\n+++ b/projects/foxglove/config/staging.toml\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure FoxgloveMoonlitSDKFlow 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.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Observation: Incident timeline — INC-46120\n\n08:02 deploy FoxgloveHarborIndexFlow 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\nFind the source of this FoxgloveHarborIndexFlow 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.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Constraint: The public surface of FoxgloveMarbleTokenService is frozen, but its internal ownership in projects/foxglove/db/migrations/20260730_events.sql 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 FoxgloveMarbleTokenService\n- cover the awkward empty and retry states\n\nSeveral teams work in this observability, SwiftUI, Redis monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Before touching projects/foxglove/engine/render/atlas.cpp, 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.65,"slice":"core","lang":"en"} -{"prompt":"Request: The public surface of FoxgloveOrbitSyncService is frozen, but its internal ownership in projects/foxglove/lib/codec/frame.cc 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 FoxgloveOrbitSyncService\n- cover the awkward empty and retry states\n\nSeveral teams work in this observability, SwiftUI, Redis monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Goal: # projects/foxglove/apps/console/routes/usage.svelte\n[worker.foxglovetideworkerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.foxglovetideworkerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.foxglovetideworkerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.FoxgloveTideWorkerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-46125\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 FoxgloveTideWorkerFlow'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.33,"slice":"pasted-context","lang":"en"} -{"prompt":"Symptom: // projects/foxglove/web/components/FilterDrawer.vue\nfinal class FoxglovePineMetricsFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxglovePineMetricsFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"FoxgloveWillowCodecCoordinator: untangle the messy bit","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"vague-eval","lang":"en"} -{"prompt":"Headsup: Incident timeline — INC-46146\n\n08:02 deploy FoxgloveDriftConsoleFlow 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 FoxgloveDriftConsoleFlow rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"FYI: Incident timeline — INC-46113\n\n08:02 deploy FoxgloveSlateEditorFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Reconstruct the FoxgloveSlateEditorFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.95,"slice":"pasted-context","lang":"es"} -{"prompt":"Meanwhile: Incident timeline — INC-46148\n\n08:02 deploy FoxgloveKiteSchedulerFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nDetermine why FoxgloveKiteSchedulerFlow 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.95,"slice":"pasted-context","lang":"en"} -{"prompt":"Incident timeline — INC-46158\n\n08:02 deploy FoxgloveCoralUploadCoordinator 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 FoxgloveCoralUploadCoordinator, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.65,"slice":"pasted-context","lang":"en"} -{"prompt":"Split FoxgloveOpalRouterStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Design the FoxgloveSableParserStore rollback","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"Locally: projects/foxglove/pkg/cache/lease.rs now contains FoxgloveCinderAuthService'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.6,"slice":"core","lang":"en"} -{"prompt":"Polish the FoxgloveDeltaCanvasStore toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"boundary","lang":"en"} -{"prompt":"FoxgloveCoralUploadService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- cover the awkward empty and retry states\n- retain the current Kotlin coroutines operational envelope\n\nThis repository spans observability, SwiftUI, Redis; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"The minimum supported Kafka version in projects/foxglove/internal/auth/refresh.go is one patch behind the lockfile. Align that single value and regenerate only the affected metadata.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"core","lang":"en"} -{"prompt":"Production: The FoxgloveEchoRegistryService surface in projects/foxglove/apps/console/routes/usage.svelte 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.33,"slice":"core","lang":"en"} -{"prompt":"Em projects/foxglove/apps/console/routes/usage.svelte, o FoxgloveRavenSessionStore tem um problema intermitente no fluxo de Spring Boot. Leia o fluxo atual e avalie ownership, cancelamento e ordem; preciso apenas da análise.\n\nRestrições:\n- continuar com Spring Boot\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao FoxgloveRavenSessionStore","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"pt"} -{"prompt":"A copied hex color in FoxgloveMicaProfileService lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"core","lang":"en"} -{"prompt":"En projects/foxglove/packages/api/openapi.yaml, FoxgloveAtlasSearchService tiene un problema intermitente en el flujo de Kotlin coroutines. Lee el flujo actual y dime si ownership, cancelación y orden son seguros; solo necesito el análisis.\n\nRestricciones:\n- seguir con Kotlin coroutines\n- conservar compatibilidad y cancelación\n- limitar el cambio a FoxgloveAtlasSearchService","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"es"} -{"prompt":"Any races in FoxgloveMoonlitSDKService?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Ownership of FoxgloveWrenExportStore 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- cover the awkward empty and retry states\n- retain the current Cloudflare Workers operational envelope\n\nThis repository spans observability, SwiftUI, Redis; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"boundary","lang":"en"} -{"prompt":"In projects/foxglove/workers/thumbnail/consumer.ex hat FoxgloveQuartzPlayerService ein sporadisches Problem im GraphQL-Ablauf. Lies den aktuellen Ablauf und bewerte Ownership, Abbruch und Reihenfolge; ich brauche nur die Analyse.\n\nRandbedingungen:\n- GraphQL weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf FoxgloveQuartzPlayerService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um FoxgloveQuartzPlayerService mit GraphQL kompatibel.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"de"} -{"prompt":"Read projects/foxglove/engine/render/atlas.cpp and tell me whether FoxgloveOrbitSyncStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Clarify FoxgloveMoonlitSDKStore's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"boundary","lang":"en"} -{"prompt":"FoxgloveFrostPanelStore needs a production server path for replaying tenant events; the public envelope is agreed but persistence and retry handling are not wired. Implement the endpoint and durable cursor, enforce tenant authorization and idempotency, emit useful spans, cap work per request, and include focused tests for retries, cancellation, and malformed cursors.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- cover the awkward empty and retry states\n- retain the current Kafka operational envelope\n\nThis repository spans observability, SwiftUI, Redis; use its existing conventions rather than importing a new abstraction.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"boundary","lang":"en"} -{"prompt":"Ticket OPS-46147: retire the legacy replay path for FoxgloveMapleQueueFlow\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 FoxgloveMapleQueueFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.62,"slice":"pasted-context","lang":"en"} -{"prompt":"Cadre la migration de FoxgloveRainfallDBService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"fr"} -{"prompt":"Make FoxgloveCraneWorkspaceService keyboard navigable","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Our support and SDK teams keep answering the same questions about FoxgloveFernSnapshotStore, but the current prose in projects/foxglove/Sources/App/SessionStore.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- cover the awkward empty and retry states\n- stay compatible with the existing Cloudflare Workers deployment\n- keep the work scoped to FoxgloveFernSnapshotStore and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"This should remain a deliberately small patch: FoxgloveIrisBatchService has one known configuration mistake in projects/foxglove/Sources/App/SessionStore.swift, 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- cover the awkward empty and retry states\n- stay compatible with the existing Cloudflare Workers deployment\n- keep the work scoped to FoxgloveIrisBatchService and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"The FoxgloveWillowCodecStore 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.19,"slice":"boundary","lang":"en"} -{"prompt":"Incident timeline — INC-46127\n\n08:02 deploy FoxgloveNovaPickerFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nDetermine why FoxgloveNovaPickerFlow 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.92,"slice":"pasted-context","lang":"en"} -{"prompt":"Staging: Incident timeline — INC-47119\n\n08:02 deploy GossamerDriftConsoleFlow 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 GossamerDriftConsoleFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.67,"slice":"pasted-context","lang":"en"} -{"prompt":"Ticket OPS-47132: retire the legacy replay path for GossamerWrenExportFlow\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 GossamerWrenExportFlow 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.62,"slice":"pasted-context","lang":"en"} -{"prompt":"Two deliverables are holding up GossamerBirchMigratorCoordinator. First, lay out a staged migration for GossamerBirchMigratorCoordinator. In the same workstream, also add the visible loading and offline states. The relevant starting point is projects/gossamer/web/components/FilterDrawer.vue, which follows Room conventions and currently suffers from lease renewal code copied across three workers. Keep voiceover and keyboard navigation working.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.96,"slice":"mixed","lang":"en"} -{"prompt":"Move GossamerEmberRelayService behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Milestones for replacing GossamerBeaconStoreStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"GossamerOspreyJobService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. 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- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current OpenTelemetry operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"GossamerAsterWebhookCoordinator: check the suspicious part","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"vague-eval","lang":"en"} -{"prompt":"On compact widths, GossamerRainfallDBService'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.49,"slice":"core","lang":"en"} -{"prompt":"Bring GossamerAsterWebhookStore'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.44,"slice":"boundary","lang":"en"} -{"prompt":"// projects/gossamer/web/components/FilterDrawer.vue\nfinal class GossamerMarbleTokenFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 GossamerMarbleTokenFlow 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.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Read projects/gossamer/Sources/App/SessionStore.swift and tell me whether GossamerPineMetricsStore 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":"boundary","lang":"en"} -{"prompt":"GossamerQuartzPlayerService 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.63,"slice":"core","lang":"en"} -{"prompt":"GossamerCraneWorkspaceCoordinator: smooth out this interaction","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"vague-eval","lang":"en"} -{"prompt":"CI: Ticket OPS-47154: retire the legacy replay path for GossamerDeltaCanvasCoordinator\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 GossamerDeltaCanvasCoordinator 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.84,"slice":"pasted-context","lang":"en"} -{"prompt":"// projects/gossamer/services/ledger/replay.go\nfinal class GossamerSableParserCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Restructure GossamerSableParserCoordinator 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.84,"slice":"pasted-context","lang":"ja"} -{"prompt":"Atlas: projects/gossamer/cmd/exporter/main.py 里的 GossamerFrostPanelService 最近在 gRPC 流程中出现间歇性问题。 请阅读现有流程，判断 ownership、取消和顺序是否安全，只需要分析。\n\n约束：\n- 继续使用 gRPC\n- 保持兼容性和取消语义\n- 改动只限于 GossamerFrostPanelService","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"zh"} -{"prompt":"GossamerMarbleTokenCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Beacon: # projects/gossamer/Sources/App/SessionStore.swift\n[worker.gossamernovapickercoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossamernovapickercoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossamernovapickercoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerNovaPickerCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47150\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/gossamer/Sources/App/SessionStore.swift and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"pasted-context","lang":"en"} -{"prompt":"Cinder: Incident timeline — INC-47129\n\n08:02 deploy GossamerOrbitSyncFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Turn the material above into a concise GossamerOrbitSyncFlow 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.67,"slice":"pasted-context","lang":"fr"} -{"prompt":"Delta: // projects/gossamer/cmd/exporter/main.py\nfinal class GossamerBasilRunnerFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 GossamerBasilRunnerFlow'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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"GossamerPrismCacheFlow needs an idempotent replay endpoint backed by Swift 6; accept a cursor, cap each page at 500 items, and return a stable continuation token.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"GossamerSlateEditorService occasionally exhibits duplicate retries after a network handoff, but only after a reconnect. Follow the data and cancellation paths in projects/gossamer/src/sync/reconcile.ts and identify the cause before changing anything.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Could GossamerDeltaCanvasFlow show the active FastAPI sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"boundary","lang":"en"} -{"prompt":"Does GossamerCloudReconcilerService enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Test Suite 'GossamerBeaconStoreFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[GossamerBeaconStoreFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/gossamer/Sources/App/SessionStore.swift:144: error: -[GossamerBeaconStoreFlowTests 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 '-[GossamerBeaconStoreFlowTests 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\nReconstruct the GossamerBeaconStoreFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Does GossamerLedgerGateStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists? I want your judgment and walkthrough, not new documentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Draft GossamerBeaconStoreService's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"Ember: The data is already available in projects/gossamer/Sources/CLI/Commands/Doctor.swift; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"boundary","lang":"en"} -{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current GossamerGarnetModalService design actually guarantees what its callers assume. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside GossamerGarnetModalService\n- keep VoiceOver and keyboard navigation working\n\nThe relevant code crosses healthcare, Svelte, Kafka. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Could GossamerLedgerGateService show the active Room sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} -{"prompt":"Frost: projects/gossamer/services/ledger/replay.go 里的 GossamerHarborIndexStore 最近在 Room 流程中出现间歇性问题。 请给出阶段、兼容层、指标、rollback 和 ownership，先不要修改代码。\n\n约束：\n- 继续使用 Room\n- 保持兼容性和取消语义\n- 改动只限于 GossamerHarborIndexStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"zh"} -{"prompt":"Incident timeline — INC-47139\n\n08:02 deploy GossamerJuniperCLIFlow 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 GossamerJuniperCLIFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.67,"slice":"pasted-context","lang":"en"} -{"prompt":"Garnet: Ticket OPS-47124: retire the legacy replay path for GossamerSummitProxyFlow\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 GossamerSummitProxyFlow 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.84,"slice":"pasted-context","lang":"en"} -{"prompt":"How does GossamerCraneWorkspaceStore propagate cancellation through the Swift 6 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.55,"slice":"boundary","lang":"en"} -{"prompt":"On compact widths, GossamerCloudReconcilerStore'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.46,"slice":"boundary","lang":"en"} -{"prompt":"$ pnpm test --filter GossamerIrisBatchFlow\n RUN v3.2.4 /workspace/apps/console\n × GossamerIrisBatchFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=47127 phase=resume storedCursor=seg-0183\n session=47127 phase=fetch requestCursor=seg-0183 pageSize=200\n session=47127 phase=commit receivedCursor=seg-0184 itemCount=0\n session=47127 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nReconstruct the GossamerIrisBatchFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.92,"slice":"pasted-context","lang":"en"} -{"prompt":"GossamerLedgerGateCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"One contained cleanup in projects/gossamer/web/components/FilterDrawer.vue: remove the obsolete GossamerSableParserFlow import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"boundary","lang":"en"} -{"prompt":"For GossamerSummitProxyCoordinator, separate GossamerSummitProxyCoordinator's policy from transport without behavior changes; once that is complete, correct the known stale timeout beside it. Work from projects/gossamer/crates/index/src/segment.rs, stay with FastAPI, and keep VoiceOver and keyboard navigation working. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.73,"slice":"mixed","lang":"en"} -{"prompt":"Harbor: # projects/gossamer/internal/auth/refresh.go\n[worker.gossameramberfilterflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossameramberfilterflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossameramberfilterflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerAmberFilterFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47128\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/gossamer/internal/auth/refresh.go. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.41,"slice":"pasted-context","lang":"en"} -{"prompt":"The next client release depends on a new GossamerNovaPickerService capability in projects/gossamer/Sources/CLI/Commands/Doctor.swift, with gRPC already chosen by the platform group. Implement the endpoint and durable cursor, enforce tenant authorization and idempotency, emit useful spans, cap work per request, and include focused tests for retries, cancellation, and malformed cursors.\n\nConstraints:\n- keep VoiceOver and keyboard navigation working\n- stay compatible with the existing gRPC deployment\n- keep the work scoped to GossamerNovaPickerService and its direct tests\n\nThis repository spans healthcare, Svelte, Kafka; use its existing conventions rather than importing a new abstraction.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Lay out a two-milestone strategy for eliminating a deadlock that appears only during shutdown in GossamerRainfallDBStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Iris: The first GossamerSableParserStore request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current GossamerBasilRunnerStore design actually guarantees what its callers assume. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside GossamerBasilRunnerStore\n- keep VoiceOver and keyboard navigation working\n\nThe relevant code crosses healthcare, Svelte, Kafka. 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.66,"slice":"boundary","lang":"en"} -{"prompt":"Assess the GossamerCoralUploadService diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Summarize the GossamerAmberFilterService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"Juniper: Could GossamerTideWorkerStore show the active Room sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} -{"prompt":"Kestrel: // projects/gossamer/web/components/FilterDrawer.vue\nfinal class GossamerHarborIndexFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nAdd the bounded GossamerHarborIndexFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"Lumen: // projects/gossamer/workers/thumbnail/consumer.ex\nfinal class GossamerFernSnapshotFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Split GossamerFernSnapshotFlow 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.82,"slice":"pasted-context","lang":"pt"} -{"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_47121'\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_47121'::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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Wire GossamerKiteSchedulerFlow'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.83,"slice":"pasted-context","lang":"de"} -{"prompt":"GossamerRavenSessionFlow's staging timeout is already known to be wrong: change the single projects/gossamer/internal/auth/refresh.go value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"boundary","lang":"en"} -{"prompt":"GossamerWillowCodecCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"GossamerCopperBridgeCoordinator: ship a sensible version","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"vague-eval","lang":"en"} -{"prompt":"GossamerJuniperCLICoordinator: why is this odd","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"vague-eval","lang":"en"} -{"prompt":"The destination for GossamerRavenSessionService is broadly agreed; the missing piece is a reversible route from projects/gossamer/internal/auth/refresh.go to that target. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside GossamerRavenSessionService\n- keep VoiceOver and keyboard navigation working\n\nThe relevant code crosses healthcare, Svelte, Kafka. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"core","lang":"en"} -{"prompt":"Centre la modale GossamerDriftConsoleService","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"fr"} -{"prompt":"diff --git a/projects/gossamer/Sources/CLI/Commands/Doctor.swift b/projects/gossamer/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/gossamer/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is GossamerMapleQueueFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"pasted-context","lang":"en"} -{"prompt":"Maple: # projects/gossamer/Sources/App/SessionStore.swift\n[worker.gossamermicaprofileflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossamermicaprofileflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossamermicaprofileflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerMicaProfileFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47110\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/gossamer/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.33,"slice":"pasted-context","lang":"en"} -{"prompt":"Vereinheitliche die GossamerDriftConsoleStore-Validatoren","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"de"} -{"prompt":"Translate the GossamerSummitProxyService setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"diff --git a/projects/gossamer/Sources/CLI/Commands/Doctor.swift b/projects/gossamer/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/gossamer/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit GossamerPineMetricsFlow 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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Translate the GossamerWrenExportService setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"# projects/gossamer/ui/settings/PrivacyPane.tsx\n[worker.gossamercraneworkspaceflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossamercraneworkspaceflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossamercraneworkspaceflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerCraneWorkspaceFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47147\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/gossamer/ui/settings/PrivacyPane.tsx and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.38,"slice":"pasted-context","lang":"en"} -{"prompt":"GossamerBasilRunnerCoordinator is blocking the next release because a query plan that changes after statistics refresh. I need two concrete outcomes from a single pass: finish GossamerBasilRunnerCoordinator's responsive empty and retry states, and capture the contract and rollback note for consumers. Use the existing gRPC conventions in projects/gossamer/ml/pipeline/features.py; keep VoiceOver and keyboard navigation working. 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":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"PM needs a concise migration note for GossamerDeltaCanvasStore, including the user impact, rollback trigger, and the one configuration key operators must change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"For GossamerBeaconStoreCoordinator, produce a consumer guide for GossamerBeaconStoreCoordinator; once that is complete, give the existing implementation a read-only safety pass. Work from projects/gossamer/Sources/CLI/Commands/Doctor.swift, stay with gRPC, and keep VoiceOver and keyboard navigation working. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.43,"slice":"mixed","lang":"en"} -{"prompt":"Give GossamerOrbitSyncStore a README example","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"boundary","lang":"en"} -{"prompt":"What sequence would let GossamerNimbusFormFlow adopt Swift 6 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.67,"slice":"boundary","lang":"en"} +{"prompt":"FoxgloveMapleQueueCoordinator: polish the last piece","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Apparently: # projects/foxglove/apps/console/routes/usage.svelte\n[worker.foxgloveechoregistryflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.foxgloveechoregistryflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.foxgloveechoregistryflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.FoxgloveEchoRegistryFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-46145\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 The intended correction is already known: change only the stale 15-second setting to 30 seconds in projects/foxglove/apps/console/routes/usage.svelte and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Milestones for replacing FoxglovePineMetricsService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Does FoxglovePrismCacheStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"This should remain a deliberately small patch: FoxgloveAcornWidgetService has one known configuration mistake in projects/foxglove/src/sync/reconcile.ts, 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- cover the awkward empty and retry states\n- stay compatible with the existing Spring Boot deployment\n- keep the work scoped to FoxgloveAcornWidgetService and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"// projects/foxglove/Sources/App/SessionStore.swift\nfinal class FoxgloveWillowCodecFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveWillowCodecFlow; 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":"Fresh release brief for FoxgloveFrostPanelCoordinator:\n- primary outcome: change FoxgloveFrostPanelCoordinator'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/foxglove/internal/auth/refresh.go\n- platform constraint: Kafka\n- known complication: lost focus when the drawer animation finishes\n\nBoth results are required, but they should remain independently reviewable. Cover the awkward empty and retry states; 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.6,"slice":"mixed","lang":"en"} +{"prompt":"Ticket OPS-46143: retire the legacy replay path for FoxgloveEmberRelayFlow\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 FoxgloveEmberRelayFlow 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":"diff --git a/projects/foxglove/ml/pipeline/features.py b/projects/foxglove/ml/pipeline/features.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/foxglove/ml/pipeline/features.py\n+++ b/projects/foxglove/ml/pipeline/features.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 FoxgloveRainfallDBFlow'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":"Release engineering needs a FoxgloveNimbusFormStore 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":"FoxgloveMicaProfileCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Give FoxgloveMapleQueueService'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":"Warum hängt FoxgloveRainfallDBStore?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"de"} +{"prompt":"Lately: // projects/foxglove/engine/render/atlas.cpp\nfinal class FoxgloveOrbitSyncCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveOrbitSyncCoordinator 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":"Oddly: diff --git a/projects/foxglove/app/src/main/SyncWorker.kt b/projects/foxglove/app/src/main/SyncWorker.kt\nindex 62d71aa..90f3c1e 100644\n--- a/projects/foxglove/app/src/main/SyncWorker.kt\n+++ b/projects/foxglove/app/src/main/SyncWorker.kt\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure FoxgloveLedgerGateFlow 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":"Map FoxgloveCopperBridgeStore's ownership split","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Dedupe FoxgloveCedarPolicyService's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"On compact widths, FoxgloveIrisBatchFlow'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":"The minimum supported GraphQL version in projects/foxglove/engine/render/atlas.cpp 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":"Incident timeline — INC-46134\n\n08:02 deploy FoxgloveNimbusFormFlow 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 FoxgloveNimbusFormFlow, 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":"Design the FoxgloveGarnetModalService rollback","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Corrige le timeout de FoxgloveNovaPickerStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"fr"} +{"prompt":"Move FoxgloveSpruceDaemonService'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":"Store FoxgloveTideWorkerService's delivery receipts","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Pin FoxgloveSableParserService's Spring dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"projects/foxglove/packages/api/openapi.yaml の FoxgloveEmberRelayService で、Kotlin coroutines の flow に断続的な問題が起きています。 段階、互換性、metrics、rollback、ownership を提案し、コード変更の前で止めてください。\n\n制約:\n- Kotlin coroutines を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は FoxgloveEmberRelayService のみ","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"ja"} +{"prompt":"Please resist widening this one: FoxgloveSlateEditorStore works, but staging still carries a setting that production corrected last month. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside FoxgloveSlateEditorStore\n- cover the awkward empty and retry states\n\nSeveral teams work in this observability, SwiftUI, Redis monorepo, so keep ownership and handoff points understandable in a small review.\n\nThe cause and exact value change are already known, so keep this as a contained correction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-46128: finish the compact FoxgloveOspreyJobFlow filter experience\n\nRoute: /catalog/search\nSource: projects/foxglove/crates/index/src/segment.rs\nFramework: Kotlin coroutines\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 FoxgloveOspreyJobFlow'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":"core","lang":"en"} +{"prompt":"Why does FoxgloveSummitProxyStore's GraphQL worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'FoxgloveVelaDrawerFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[FoxgloveVelaDrawerFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/foxglove/cmd/exporter/main.py:144: error: -[FoxgloveVelaDrawerFlowTests 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 '-[FoxgloveVelaDrawerFlowTests 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 FoxgloveVelaDrawerFlow'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":"Currently: diff --git a/projects/foxglove/workers/thumbnail/consumer.ex b/projects/foxglove/workers/thumbnail/consumer.ex\nindex 62d71aa..90f3c1e 100644\n--- a/projects/foxglove/workers/thumbnail/consumer.ex\n+++ b/projects/foxglove/workers/thumbnail/consumer.ex\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 FoxgloveQuartzPlayerFlow 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":"Today: // projects/foxglove/db/migrations/20260730_events.sql\nfinal class FoxgloveBirchMigratorFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveBirchMigratorFlow'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":"FoxgloveOspreyJobCoordinator needs a paired pass: produce a consumer guide for FoxgloveOspreyJobCoordinator, plus give the existing implementation a read-only safety pass. Use projects/foxglove/pkg/cache/lease.rs as the source of truth, preserve the Kotlin coroutines contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Context: # projects/foxglove/workers/thumbnail/consumer.ex\n[worker.foxglovesummitproxycoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.foxglovesummitproxycoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.foxglovesummitproxycoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.FoxgloveSummitProxyCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-46151\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/foxglove/workers/thumbnail/consumer.ex and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Background: projects/foxglove/config/staging.toml 里的 FoxgloveEmberRelayStore 最近在 Kotlin coroutines 流程中出现间歇性问题。 请给出阶段、兼容层、指标、rollback 和 ownership，先不要修改代码。\n\n约束：\n- 继续使用 Kotlin coroutines\n- 保持兼容性和取消语义\n- 改动只限于 FoxgloveEmberRelayStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"FoxgloveMosaicGridService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- cover the awkward empty and retry states\n- retain the current Kafka operational envelope\n\nThis repository spans observability, SwiftUI, Redis; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Question: diff --git a/projects/foxglove/config/staging.toml b/projects/foxglove/config/staging.toml\nindex 62d71aa..90f3c1e 100644\n--- a/projects/foxglove/config/staging.toml\n+++ b/projects/foxglove/config/staging.toml\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure FoxgloveMoonlitSDKFlow 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":"Observation: Incident timeline — INC-46120\n\n08:02 deploy FoxgloveHarborIndexFlow 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\nFind the source of this FoxgloveHarborIndexFlow symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Constraint: The public surface of FoxgloveMarbleTokenService is frozen, but its internal ownership in projects/foxglove/db/migrations/20260730_events.sql 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 FoxgloveMarbleTokenService\n- cover the awkward empty and retry states\n\nSeveral teams work in this observability, SwiftUI, Redis 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":"Before touching projects/foxglove/engine/render/atlas.cpp, 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":"Request: The public surface of FoxgloveOrbitSyncService is frozen, but its internal ownership in projects/foxglove/lib/codec/frame.cc 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 FoxgloveOrbitSyncService\n- cover the awkward empty and retry states\n\nSeveral teams work in this observability, SwiftUI, Redis 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":"Goal: # projects/foxglove/apps/console/routes/usage.svelte\n[worker.foxglovetideworkerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.foxglovetideworkerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.foxglovetideworkerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.FoxgloveTideWorkerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-46125\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 FoxgloveTideWorkerFlow'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":"Symptom: // projects/foxglove/web/components/FilterDrawer.vue\nfinal class FoxglovePineMetricsFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxglovePineMetricsFlow; 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":"FoxgloveWillowCodecCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Headsup: Incident timeline — INC-46146\n\n08:02 deploy FoxgloveDriftConsoleFlow 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 FoxgloveDriftConsoleFlow 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":"FYI: Incident timeline — INC-46113\n\n08:02 deploy FoxgloveSlateEditorFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Reconstruct the FoxgloveSlateEditorFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Meanwhile: Incident timeline — INC-46148\n\n08:02 deploy FoxgloveKiteSchedulerFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nDetermine why FoxgloveKiteSchedulerFlow 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":"Incident timeline — INC-46158\n\n08:02 deploy FoxgloveCoralUploadCoordinator 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 FoxgloveCoralUploadCoordinator, 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":"Split FoxgloveOpalRouterStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Design the FoxgloveSableParserStore rollback","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Locally: projects/foxglove/pkg/cache/lease.rs now contains FoxgloveCinderAuthService'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.4,"slice":"core","lang":"en"} +{"prompt":"Polish the FoxgloveDeltaCanvasStore toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"FoxgloveCoralUploadService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- cover the awkward empty and retry states\n- retain the current Kotlin coroutines operational envelope\n\nThis repository spans observability, SwiftUI, Redis; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"The minimum supported Kafka version in projects/foxglove/internal/auth/refresh.go 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":"Production: The FoxgloveEchoRegistryService surface in projects/foxglove/apps/console/routes/usage.svelte 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":"Em projects/foxglove/apps/console/routes/usage.svelte, o FoxgloveRavenSessionStore tem um problema intermitente no fluxo de Spring Boot. Leia o fluxo atual e avalie ownership, cancelamento e ordem; preciso apenas da análise.\n\nRestrições:\n- continuar com Spring Boot\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao FoxgloveRavenSessionStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"pt"} +{"prompt":"A copied hex color in FoxgloveMicaProfileService lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"En projects/foxglove/packages/api/openapi.yaml, FoxgloveAtlasSearchService tiene un problema intermitente en el flujo de Kotlin coroutines. Lee el flujo actual y dime si ownership, cancelación y orden son seguros; solo necesito el análisis.\n\nRestricciones:\n- seguir con Kotlin coroutines\n- conservar compatibilidad y cancelación\n- limitar el cambio a FoxgloveAtlasSearchService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"es"} +{"prompt":"Any races in FoxgloveMoonlitSDKService?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Ownership of FoxgloveWrenExportStore 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- cover the awkward empty and retry states\n- retain the current Cloudflare Workers operational envelope\n\nThis repository spans observability, SwiftUI, Redis; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"In projects/foxglove/workers/thumbnail/consumer.ex hat FoxgloveQuartzPlayerService ein sporadisches Problem im GraphQL-Ablauf. Lies den aktuellen Ablauf und bewerte Ownership, Abbruch und Reihenfolge; ich brauche nur die Analyse.\n\nRandbedingungen:\n- GraphQL weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf FoxgloveQuartzPlayerService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um FoxgloveQuartzPlayerService mit GraphQL kompatibel.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"de"} +{"prompt":"Read projects/foxglove/engine/render/atlas.cpp and tell me whether FoxgloveOrbitSyncStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Clarify FoxgloveMoonlitSDKStore's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"FoxgloveFrostPanelStore needs a production server path for replaying tenant events; the public envelope is agreed but persistence and retry handling are not wired. Implement the endpoint and durable cursor, enforce tenant authorization and idempotency, emit useful spans, cap work per request, and include focused tests for retries, cancellation, and malformed cursors.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- cover the awkward empty and retry states\n- retain the current Kafka operational envelope\n\nThis repository spans observability, SwiftUI, Redis; use its existing conventions rather than importing a new abstraction.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-46147: retire the legacy replay path for FoxgloveMapleQueueFlow\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 FoxgloveMapleQueueFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Cadre la migration de FoxgloveRainfallDBService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"fr"} +{"prompt":"Make FoxgloveCraneWorkspaceService keyboard navigable","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Our support and SDK teams keep answering the same questions about FoxgloveFernSnapshotStore, but the current prose in projects/foxglove/Sources/App/SessionStore.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- cover the awkward empty and retry states\n- stay compatible with the existing Cloudflare Workers deployment\n- keep the work scoped to FoxgloveFernSnapshotStore and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"This should remain a deliberately small patch: FoxgloveIrisBatchService has one known configuration mistake in projects/foxglove/Sources/App/SessionStore.swift, 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- cover the awkward empty and retry states\n- stay compatible with the existing Cloudflare Workers deployment\n- keep the work scoped to FoxgloveIrisBatchService and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"The FoxgloveWillowCodecStore 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":"Incident timeline — INC-46127\n\n08:02 deploy FoxgloveNovaPickerFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nDetermine why FoxgloveNovaPickerFlow 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":"Staging: Incident timeline — INC-47119\n\n08:02 deploy GossamerDriftConsoleFlow 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 GossamerDriftConsoleFlow 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":"Ticket OPS-47132: retire the legacy replay path for GossamerWrenExportFlow\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 GossamerWrenExportFlow 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":"Two deliverables are holding up GossamerBirchMigratorCoordinator. First, lay out a staged migration for GossamerBirchMigratorCoordinator. In the same workstream, also add the visible loading and offline states. The relevant starting point is projects/gossamer/web/components/FilterDrawer.vue, which follows Room conventions and currently suffers from lease renewal code copied across three workers. Keep voiceover and keyboard navigation working.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Move GossamerEmberRelayService behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Milestones for replacing GossamerBeaconStoreStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"GossamerOspreyJobService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. 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- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current OpenTelemetry operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka 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":"GossamerAsterWebhookCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"On compact widths, GossamerRainfallDBService'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":"Bring GossamerAsterWebhookStore'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":"// projects/gossamer/web/components/FilterDrawer.vue\nfinal class GossamerMarbleTokenFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 GossamerMarbleTokenFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Read projects/gossamer/Sources/App/SessionStore.swift and tell me whether GossamerPineMetricsStore 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":"GossamerQuartzPlayerService 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":"GossamerCraneWorkspaceCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"CI: Ticket OPS-47154: retire the legacy replay path for GossamerDeltaCanvasCoordinator\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 GossamerDeltaCanvasCoordinator 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/gossamer/services/ledger/replay.go\nfinal class GossamerSableParserCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Restructure GossamerSableParserCoordinator 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":"Atlas: projects/gossamer/cmd/exporter/main.py 里的 GossamerFrostPanelService 最近在 gRPC 流程中出现间歇性问题。 请阅读现有流程，判断 ownership、取消和顺序是否安全，只需要分析。\n\n约束：\n- 继续使用 gRPC\n- 保持兼容性和取消语义\n- 改动只限于 GossamerFrostPanelService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"zh"} +{"prompt":"GossamerMarbleTokenCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Beacon: # projects/gossamer/Sources/App/SessionStore.swift\n[worker.gossamernovapickercoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossamernovapickercoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossamernovapickercoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerNovaPickerCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47150\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/gossamer/Sources/App/SessionStore.swift and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Cinder: Incident timeline — INC-47129\n\n08:02 deploy GossamerOrbitSyncFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Turn the material above into a concise GossamerOrbitSyncFlow 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":"Delta: // projects/gossamer/cmd/exporter/main.py\nfinal class GossamerBasilRunnerFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 GossamerBasilRunnerFlow'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":"GossamerPrismCacheFlow needs an idempotent replay endpoint backed by Swift 6; accept a cursor, cap each page at 500 items, and return a stable continuation token.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"GossamerSlateEditorService occasionally exhibits duplicate retries after a network handoff, but only after a reconnect. Follow the data and cancellation paths in projects/gossamer/src/sync/reconcile.ts and identify the cause before changing anything.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Could GossamerDeltaCanvasFlow show the active FastAPI sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Does GossamerCloudReconcilerService enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'GossamerBeaconStoreFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[GossamerBeaconStoreFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/gossamer/Sources/App/SessionStore.swift:144: error: -[GossamerBeaconStoreFlowTests 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 '-[GossamerBeaconStoreFlowTests 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\nReconstruct the GossamerBeaconStoreFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Does GossamerLedgerGateStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists? I want your judgment and walkthrough, not new documentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft GossamerBeaconStoreService's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Ember: The data is already available in projects/gossamer/Sources/CLI/Commands/Doctor.swift; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current GossamerGarnetModalService design actually guarantees what its callers assume. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside GossamerGarnetModalService\n- keep VoiceOver and keyboard navigation working\n\nThe relevant code crosses healthcare, Svelte, Kafka. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Could GossamerLedgerGateService show the active Room 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":"Frost: projects/gossamer/services/ledger/replay.go 里的 GossamerHarborIndexStore 最近在 Room 流程中出现间歇性问题。 请给出阶段、兼容层、指标、rollback 和 ownership，先不要修改代码。\n\n约束：\n- 继续使用 Room\n- 保持兼容性和取消语义\n- 改动只限于 GossamerHarborIndexStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"zh"} +{"prompt":"Incident timeline — INC-47139\n\n08:02 deploy GossamerJuniperCLIFlow 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 GossamerJuniperCLIFlow, 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":"Garnet: Ticket OPS-47124: retire the legacy replay path for GossamerSummitProxyFlow\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 GossamerSummitProxyFlow 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":"How does GossamerCraneWorkspaceStore propagate cancellation through the Swift 6 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":"On compact widths, GossamerCloudReconcilerStore'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.6,"slice":"core","lang":"en"} +{"prompt":"$ pnpm test --filter GossamerIrisBatchFlow\n RUN v3.2.4 /workspace/apps/console\n × GossamerIrisBatchFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=47127 phase=resume storedCursor=seg-0183\n session=47127 phase=fetch requestCursor=seg-0183 pageSize=200\n session=47127 phase=commit receivedCursor=seg-0184 itemCount=0\n session=47127 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nReconstruct the GossamerIrisBatchFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"GossamerLedgerGateCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"One contained cleanup in projects/gossamer/web/components/FilterDrawer.vue: remove the obsolete GossamerSableParserFlow import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"For GossamerSummitProxyCoordinator, separate GossamerSummitProxyCoordinator's policy from transport without behavior changes; once that is complete, correct the known stale timeout beside it. Work from projects/gossamer/crates/index/src/segment.rs, stay with FastAPI, and keep VoiceOver and keyboard navigation working. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Harbor: # projects/gossamer/internal/auth/refresh.go\n[worker.gossameramberfilterflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossameramberfilterflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossameramberfilterflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerAmberFilterFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47128\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/gossamer/internal/auth/refresh.go. 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":"The next client release depends on a new GossamerNovaPickerService capability in projects/gossamer/Sources/CLI/Commands/Doctor.swift, with gRPC already chosen by the platform group. Implement the endpoint and durable cursor, enforce tenant authorization and idempotency, emit useful spans, cap work per request, and include focused tests for retries, cancellation, and malformed cursors.\n\nConstraints:\n- keep VoiceOver and keyboard navigation working\n- stay compatible with the existing gRPC deployment\n- keep the work scoped to GossamerNovaPickerService and its direct tests\n\nThis repository spans healthcare, Svelte, Kafka; use its existing conventions rather than importing a new abstraction.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating a deadlock that appears only during shutdown in GossamerRainfallDBStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Iris: The first GossamerSableParserStore request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current GossamerBasilRunnerStore design actually guarantees what its callers assume. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside GossamerBasilRunnerStore\n- keep VoiceOver and keyboard navigation working\n\nThe relevant code crosses healthcare, Svelte, Kafka. 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":"Assess the GossamerCoralUploadService diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Summarize the GossamerAmberFilterService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Juniper: Could GossamerTideWorkerStore show the active Room 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":"Kestrel: // projects/gossamer/web/components/FilterDrawer.vue\nfinal class GossamerHarborIndexFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nAdd the bounded GossamerHarborIndexFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Lumen: // projects/gossamer/workers/thumbnail/consumer.ex\nfinal class GossamerFernSnapshotFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Split GossamerFernSnapshotFlow 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":"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_47121'\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_47121'::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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Wire GossamerKiteSchedulerFlow'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":"GossamerRavenSessionFlow's staging timeout is already known to be wrong: change the single projects/gossamer/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":"GossamerWillowCodecCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"GossamerCopperBridgeCoordinator: ship a sensible version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"GossamerJuniperCLICoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"The destination for GossamerRavenSessionService is broadly agreed; the missing piece is a reversible route from projects/gossamer/internal/auth/refresh.go to that target. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside GossamerRavenSessionService\n- keep VoiceOver and keyboard navigation working\n\nThe relevant code crosses healthcare, Svelte, Kafka. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Centre la modale GossamerDriftConsoleService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"fr"} +{"prompt":"diff --git a/projects/gossamer/Sources/CLI/Commands/Doctor.swift b/projects/gossamer/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/gossamer/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is GossamerMapleQueueFlow'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":"Maple: # projects/gossamer/Sources/App/SessionStore.swift\n[worker.gossamermicaprofileflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossamermicaprofileflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossamermicaprofileflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerMicaProfileFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47110\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/gossamer/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":"Vereinheitliche die GossamerDriftConsoleStore-Validatoren","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"de"} +{"prompt":"Translate the GossamerSummitProxyService setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/gossamer/Sources/CLI/Commands/Doctor.swift b/projects/gossamer/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/gossamer/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit GossamerPineMetricsFlow 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":"Translate the GossamerWrenExportService setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"# projects/gossamer/ui/settings/PrivacyPane.tsx\n[worker.gossamercraneworkspaceflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossamercraneworkspaceflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossamercraneworkspaceflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerCraneWorkspaceFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47147\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/gossamer/ui/settings/PrivacyPane.tsx and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"GossamerBasilRunnerCoordinator is blocking the next release because a query plan that changes after statistics refresh. I need two concrete outcomes from a single pass: finish GossamerBasilRunnerCoordinator's responsive empty and retry states, and capture the contract and rollback note for consumers. Use the existing gRPC conventions in projects/gossamer/ml/pipeline/features.py; keep VoiceOver and keyboard navigation working. 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":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"PM needs a concise migration note for GossamerDeltaCanvasStore, 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":"For GossamerBeaconStoreCoordinator, produce a consumer guide for GossamerBeaconStoreCoordinator; once that is complete, give the existing implementation a read-only safety pass. Work from projects/gossamer/Sources/CLI/Commands/Doctor.swift, stay with gRPC, and keep VoiceOver and keyboard navigation working. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Give GossamerOrbitSyncStore a README example","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"What sequence would let GossamerNimbusFormFlow adopt Swift 6 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.8,"slice":"core","lang":"en"} {"prompt":"Two engineers disagree about whether GossamerAsterWebhookService's cache is authoritative. Walk the reads and writes in projects/gossamer/ml/pipeline/features.py and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"This should remain a deliberately small patch: GossamerLumenChartService has one known configuration mistake in projects/gossamer/lib/codec/frame.cc, not an open-ended failure investigation. 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- keep VoiceOver and keyboard navigation working\n- stay compatible with the existing Swift 6 deployment\n- keep the work scoped to GossamerLumenChartService and its direct tests\n\nThis repository spans healthcare, Svelte, Kafka; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Three teams extended GossamerBirchMigratorService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current Room operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"# projects/gossamer/cmd/exporter/main.py\n[worker.gossamerfrostpanelflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossamerfrostpanelflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossamerfrostpanelflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerFrostPanelFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47135\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/gossamer/cmd/exporter/main.py and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"pasted-context","lang":"en"} -{"prompt":"Fresh release brief for GossamerSpruceDaemonCoordinator:\n- primary outcome: produce a consumer guide for GossamerSpruceDaemonCoordinator\n- companion outcome: give the existing implementation a read-only safety pass\n- repository entry point: projects/gossamer/pkg/cache/lease.rs\n- platform constraint: FastAPI\n- known complication: duplicate retries after a network handoff\n\nBoth results are required, but they should remain independently reviewable. Keep voiceover and keyboard navigation working; 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":"writing","secondary":"review","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"GossamerVelaDrawerCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"GossamerCedarPolicyCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"vague-eval","lang":"en"} -{"prompt":"GossamerRainfallDBCoordinator: the docs need something","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"vague-eval","lang":"en"} -{"prompt":"En projects/gossamer/web/components/FilterDrawer.vue, GossamerSableParserService tiene un problema intermitente en el flujo de Room. Termina el layout responsive, estados vacío y retry, foco por teclado, dark mode y reduced motion.\n\nRestricciones:\n- seguir con Room\n- conservar compatibilidad y cancelación\n- limitar el cambio a GossamerSableParserService","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"es"} -{"prompt":"Why does GossamerCedarPolicyStore's OpenTelemetry worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"boundary","lang":"en"} -{"prompt":"Trace GossamerMosaicGridStore's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current GossamerPrismCacheService design actually guarantees what its callers assume. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside GossamerPrismCacheService\n- keep VoiceOver and keyboard navigation working\n\nThe relevant code crosses healthcare, Svelte, Kafka. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Ticket OPS-47146: retire the legacy replay path for GossamerCloudReconcilerFlow\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 GossamerCloudReconcilerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.59,"slice":"pasted-context","lang":"en"} -{"prompt":"GossamerMapleQueueCoordinator: ship, then correct","purpose":"backendImpl","secondary":"quickFix","mixed":true,"difficulty":0.67,"slice":"mixed","lang":"en"} -{"prompt":"GossamerFrostPanelCoordinator: take care of the warning","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"UI ticket DES-47145: finish the compact GossamerAsterWebhookFlow filter experience\n\nRoute: /catalog/search\nSource: projects/gossamer/ml/pipeline/features.py\nFramework: gRPC\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\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Use the UI evidence to complete GossamerAsterWebhookFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"pasted-context","lang":"zh"} -{"prompt":"Before touching projects/gossamer/Sources/CLI/Commands/Doctor.swift, 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.62,"slice":"core","lang":"en"} -{"prompt":"GossamerOrbitSyncCoordinator needs a paired pass: change GossamerOrbitSyncCoordinator's known staging timeout from 15 to 30 seconds, plus capture the contract and rollback note for consumers. Use projects/gossamer/config/staging.toml as the source of truth, preserve the FastAPI contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.29,"slice":"mixed","lang":"en"} -{"prompt":"GossamerAcornWidgetStore's FilterDrawer.vue needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"boundary","lang":"en"} -{"prompt":"GossamerEmberRelayCoordinator: restructure, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"Unify the GossamerWrenExportStore validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Nimbus: # projects/gossamer/engine/render/atlas.cpp\n[worker.gossamerrainfalldbflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossamerrainfalldbflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossamerrainfalldbflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerRainfallDBFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47142\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 GossamerRainfallDBFlow'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.38,"slice":"pasted-context","lang":"en"} -{"prompt":"Collapse the GossamerMarbleTokenService wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Opal: diff --git a/projects/gossamer/src/sync/reconcile.ts b/projects/gossamer/src/sync/reconcile.ts\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/src/sync/reconcile.ts\n+++ b/projects/gossamer/src/sync/reconcile.ts\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure GossamerMoonlitSDKCoordinator 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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"What is the safest way to split projects/gossamer/packages/api/openapi.yaml into independently owned modules while GossamerFlintTimelineFlow's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"Clarify GossamerAtlasSearchService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"Release verification found a single stale GossamerSpruceDaemonStore value; the cause, desired value, and affected assertion are already agreed. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current FastAPI operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"Prism: // projects/gossamer/services/ledger/replay.go\nfinal class GossamerBirchMigratorFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Split GossamerBirchMigratorFlow 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.84,"slice":"pasted-context","lang":"es"} -{"prompt":"Production says GossamerNimbusFormService is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Reconstruct the failing timeline from logs and tests, identify which invariant first breaks, and distinguish causal signals from effects or cleanup noise.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current Swift 6 operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.84,"slice":"core","lang":"en"} -{"prompt":"Move GossamerVelaDrawerStore behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Could GossamerNovaPickerStore show the active gRPC sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"Security flagged GossamerWillowCodecStore for a read-only pass because its Swift 6 boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current Swift 6 operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka 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.71,"slice":"boundary","lang":"en"} -{"prompt":"Quartz: What is the safest way to split projects/gossamer/workers/thumbnail/consumer.ex into independently owned modules while GossamerFernSnapshotService's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Our support and SDK teams keep answering the same questions about GossamerBirchMigratorStore, but the current prose in projects/gossamer/web/components/FilterDrawer.vue only describes the happy path. 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- keep VoiceOver and keyboard navigation working\n- stay compatible with the existing Room deployment\n- keep the work scoped to GossamerBirchMigratorStore and its direct tests\n\nThis repository spans healthcare, Svelte, Kafka; 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.57,"slice":"boundary","lang":"en"} -{"prompt":"UI ticket DES-47131: finish the compact GossamerCoralUploadFlow filter experience\n\nRoute: /catalog/search\nSource: projects/gossamer/apps/console/routes/usage.svelte\nFramework: OpenTelemetry\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring GossamerCoralUploadFlow'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.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Remove GossamerBasilRunnerService's stray comma","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"core","lang":"en"} -{"prompt":"The first GossamerCraneWorkspaceService request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Raven: projects/gossamer/app/src/main/SyncWorker.kt の GossamerOspreyJobFlow で、OpenTelemetry の flow に断続的な問題が起きています。 consumer 向けに contract、error、retry、コピー可能な例を含む文書を書き、handler は変更しないでください。\n\n制約:\n- OpenTelemetry を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は GossamerOspreyJobFlow のみ","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"ja"} -{"prompt":"Ticket OPS-47122: retire the legacy replay path for GossamerVelaDrawerFlow\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 GossamerVelaDrawerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.62,"slice":"pasted-context","lang":"en"} -{"prompt":"Summarize the GossamerAtlasSearchStore changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"GossamerWrenExportCoordinator needs a paired pass: change GossamerWrenExportCoordinator's known staging timeout from 15 to 30 seconds, plus capture the contract and rollback note for consumers. Use projects/gossamer/engine/render/atlas.cpp as the source of truth, preserve the Swift 6 contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.24,"slice":"mixed","lang":"en"} -{"prompt":"Incident timeline — INC-47125\n\n08:02 deploy GossamerMosaicGridFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current GossamerMosaicGridFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Two engineers disagree about whether GossamerOpalRouterStore's cache is authoritative. Walk the reads and writes in projects/gossamer/config/staging.toml and settle that question from the code. I want your judgment and walkthrough, not new documentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"GossamerHarborIndexCoordinator: rethink this area","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"vague-eval","lang":"en"} -{"prompt":"Memory attributed to GossamerPrismCacheStore rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Why does GossamerGarnetModalStore's gRPC worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Decouple GossamerMapleQueueStore's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"Spell GossamerWillowCodecService's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"core","lang":"en"} -{"prompt":"Describe GossamerAcornWidgetService's error envelope","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"Read projects/gossamer/internal/auth/refresh.go and tell me whether GossamerTideWorkerService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"GossamerDriftConsoleCoordinator: restructure, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.73,"slice":"mixed","lang":"en"} -{"prompt":"GossamerAtlasSearchCoordinator needs a paired pass: finish GossamerAtlasSearchCoordinator's responsive empty and retry states, plus give the existing implementation a read-only safety pass. Use projects/gossamer/src/sync/reconcile.ts as the source of truth, preserve the OpenTelemetry contract, and avoid unrelated cleanup.","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.56,"slice":"mixed","lang":"en"} -{"prompt":"Em projects/gossamer/ml/pipeline/features.py, o GossamerFrostPanelStore tem um problema intermitente no fluxo de gRPC. Finalize o layout responsivo, estados vazio e retry, foco por teclado, dark mode e reduced motion.\n\nRestrições:\n- continuar com gRPC\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao GossamerFrostPanelStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"boundary","lang":"pt"} -{"prompt":"projects/gossamer/web/components/FilterDrawer.vue の GossamerHarborIndexService で、Room の flow に断続的な問題が起きています。 原因は判明済みです。staging timeout だけを 15 秒から 30 秒へ変え、対応する assertion を直してください。\n\n制約:\n- Room を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は GossamerHarborIndexService のみ","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"core","lang":"ja"} -{"prompt":"projects/gossamer/db/migrations/20260730_events.sql has grown through several launches, and GossamerMoonlitSDKService now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- keep VoiceOver and keyboard navigation working\n- stay compatible with the existing OpenTelemetry deployment\n- keep the work scoped to GossamerMoonlitSDKService and its direct tests\n\nThis repository spans healthcare, Svelte, Kafka; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"GossamerEchoRegistryStore crashes after reconnect","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"diff --git a/projects/gossamer/lib/codec/frame.cc b/projects/gossamer/lib/codec/frame.cc\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/lib/codec/frame.cc\n+++ b/projects/gossamer/lib/codec/frame.cc\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 GossamerPrismCacheCoordinator 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Bring GossamerCedarPolicyService'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.46,"slice":"core","lang":"en"} -{"prompt":"GossamerFernSnapshotStore returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/gossamer/ui/settings/PrivacyPane.tsx and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"boundary","lang":"en"} -{"prompt":"Sable: Ticket OPS-47116: retire the legacy replay path for GossamerEmberRelayFlow\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 GossamerEmberRelayFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"Incident timeline — INC-47155\n\n08:02 deploy GossamerGarnetModalCoordinator 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current GossamerGarnetModalCoordinator behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Tide: Ticket OPS-47126: retire the legacy replay path for GossamerAtlasSearchFlow\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 GossamerAtlasSearchFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"GossamerPineMetricsCoordinator: polish the last piece","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"vague-eval","lang":"en"} -{"prompt":"Draft GossamerVelaDrawerService's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} +{"prompt":"Three teams extended GossamerBirchMigratorService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current Room operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka 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":"# projects/gossamer/cmd/exporter/main.py\n[worker.gossamerfrostpanelflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossamerfrostpanelflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossamerfrostpanelflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerFrostPanelFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47135\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/gossamer/cmd/exporter/main.py and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Fresh release brief for GossamerSpruceDaemonCoordinator:\n- primary outcome: produce a consumer guide for GossamerSpruceDaemonCoordinator\n- companion outcome: give the existing implementation a read-only safety pass\n- repository entry point: projects/gossamer/pkg/cache/lease.rs\n- platform constraint: FastAPI\n- known complication: duplicate retries after a network handoff\n\nBoth results are required, but they should remain independently reviewable. Keep voiceover and keyboard navigation working; 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":"writing","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"GossamerVelaDrawerCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"GossamerCedarPolicyCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"GossamerRainfallDBCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"En projects/gossamer/web/components/FilterDrawer.vue, GossamerSableParserService tiene un problema intermitente en el flujo de Room. Termina el layout responsive, estados vacío y retry, foco por teclado, dark mode y reduced motion.\n\nRestricciones:\n- seguir con Room\n- conservar compatibilidad y cancelación\n- limitar el cambio a GossamerSableParserService","purpose":"frontendImpl","secondary":"debugging","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"es"} +{"prompt":"Why does GossamerCedarPolicyStore's OpenTelemetry worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Trace GossamerMosaicGridStore's memory growth","purpose":"debugging","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 GossamerPrismCacheService design actually guarantees what its callers assume. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside GossamerPrismCacheService\n- keep VoiceOver and keyboard navigation working\n\nThe relevant code crosses healthcare, Svelte, Kafka. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-47146: retire the legacy replay path for GossamerCloudReconcilerFlow\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 GossamerCloudReconcilerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"boundary","lang":"en"} +{"prompt":"GossamerMapleQueueCoordinator: ship, then correct","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"GossamerFrostPanelCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"UI ticket DES-47145: finish the compact GossamerAsterWebhookFlow filter experience\n\nRoute: /catalog/search\nSource: projects/gossamer/ml/pipeline/features.py\nFramework: gRPC\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\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Use the UI evidence to complete GossamerAsterWebhookFlow'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":"Before touching projects/gossamer/Sources/CLI/Commands/Doctor.swift, 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":"GossamerOrbitSyncCoordinator needs a paired pass: change GossamerOrbitSyncCoordinator's known staging timeout from 15 to 30 seconds, plus capture the contract and rollback note for consumers. Use projects/gossamer/config/staging.toml as the source of truth, preserve the FastAPI contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"GossamerAcornWidgetStore's FilterDrawer.vue needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"GossamerEmberRelayCoordinator: restructure, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Unify the GossamerWrenExportStore validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Nimbus: # projects/gossamer/engine/render/atlas.cpp\n[worker.gossamerrainfalldbflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossamerrainfalldbflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossamerrainfalldbflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerRainfallDBFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47142\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 GossamerRainfallDBFlow'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":"Collapse the GossamerMarbleTokenService wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Opal: diff --git a/projects/gossamer/src/sync/reconcile.ts b/projects/gossamer/src/sync/reconcile.ts\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/src/sync/reconcile.ts\n+++ b/projects/gossamer/src/sync/reconcile.ts\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure GossamerMoonlitSDKCoordinator 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":"What is the safest way to split projects/gossamer/packages/api/openapi.yaml into independently owned modules while GossamerFlintTimelineFlow's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Clarify GossamerAtlasSearchService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Release verification found a single stale GossamerSpruceDaemonStore value; the cause, desired value, and affected assertion are already agreed. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current FastAPI operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Prism: // projects/gossamer/services/ledger/replay.go\nfinal class GossamerBirchMigratorFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Split GossamerBirchMigratorFlow 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":"Production says GossamerNimbusFormService is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Reconstruct the failing timeline from logs and tests, identify which invariant first breaks, and distinguish causal signals from effects or cleanup noise.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current Swift 6 operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Move GossamerVelaDrawerStore behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Could GossamerNovaPickerStore show the active gRPC 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":"Security flagged GossamerWillowCodecStore for a read-only pass because its Swift 6 boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current Swift 6 operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka 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":"Quartz: What is the safest way to split projects/gossamer/workers/thumbnail/consumer.ex into independently owned modules while GossamerFernSnapshotService's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Our support and SDK teams keep answering the same questions about GossamerBirchMigratorStore, but the current prose in projects/gossamer/web/components/FilterDrawer.vue only describes the happy path. 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- keep VoiceOver and keyboard navigation working\n- stay compatible with the existing Room deployment\n- keep the work scoped to GossamerBirchMigratorStore and its direct tests\n\nThis repository spans healthcare, Svelte, Kafka; 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.5,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-47131: finish the compact GossamerCoralUploadFlow filter experience\n\nRoute: /catalog/search\nSource: projects/gossamer/apps/console/routes/usage.svelte\nFramework: OpenTelemetry\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring GossamerCoralUploadFlow'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":"Remove GossamerBasilRunnerService's stray comma","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"The first GossamerCraneWorkspaceService request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Raven: projects/gossamer/app/src/main/SyncWorker.kt の GossamerOspreyJobFlow で、OpenTelemetry の flow に断続的な問題が起きています。 consumer 向けに contract、error、retry、コピー可能な例を含む文書を書き、handler は変更しないでください。\n\n制約:\n- OpenTelemetry を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は GossamerOspreyJobFlow のみ","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"ja"} +{"prompt":"Ticket OPS-47122: retire the legacy replay path for GossamerVelaDrawerFlow\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 GossamerVelaDrawerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Summarize the GossamerAtlasSearchStore changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"GossamerWrenExportCoordinator needs a paired pass: change GossamerWrenExportCoordinator's known staging timeout from 15 to 30 seconds, plus capture the contract and rollback note for consumers. Use projects/gossamer/engine/render/atlas.cpp as the source of truth, preserve the Swift 6 contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Incident timeline — INC-47125\n\n08:02 deploy GossamerMosaicGridFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current GossamerMosaicGridFlow 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":"Two engineers disagree about whether GossamerOpalRouterStore's cache is authoritative. Walk the reads and writes in projects/gossamer/config/staging.toml and settle that question from the code. I want your judgment and walkthrough, not new documentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"GossamerHarborIndexCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Memory attributed to GossamerPrismCacheStore rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Why does GossamerGarnetModalStore's gRPC worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Decouple GossamerMapleQueueStore's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Spell GossamerWillowCodecService's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Describe GossamerAcornWidgetService's error envelope","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Read projects/gossamer/internal/auth/refresh.go and tell me whether GossamerTideWorkerService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"GossamerDriftConsoleCoordinator: restructure, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"GossamerAtlasSearchCoordinator needs a paired pass: finish GossamerAtlasSearchCoordinator's responsive empty and retry states, plus give the existing implementation a read-only safety pass. Use projects/gossamer/src/sync/reconcile.ts as the source of truth, preserve the OpenTelemetry contract, and avoid unrelated cleanup.","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Em projects/gossamer/ml/pipeline/features.py, o GossamerFrostPanelStore tem um problema intermitente no fluxo de gRPC. Finalize o layout responsivo, estados vazio e retry, foco por teclado, dark mode e reduced motion.\n\nRestrições:\n- continuar com gRPC\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao GossamerFrostPanelStore","purpose":"frontendImpl","secondary":"debugging","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"pt"} +{"prompt":"projects/gossamer/web/components/FilterDrawer.vue の GossamerHarborIndexService で、Room の flow に断続的な問題が起きています。 原因は判明済みです。staging timeout だけを 15 秒から 30 秒へ変え、対応する assertion を直してください。\n\n制約:\n- Room を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は GossamerHarborIndexService のみ","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"ja"} +{"prompt":"projects/gossamer/db/migrations/20260730_events.sql has grown through several launches, and GossamerMoonlitSDKService now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- keep VoiceOver and keyboard navigation working\n- stay compatible with the existing OpenTelemetry deployment\n- keep the work scoped to GossamerMoonlitSDKService and its direct tests\n\nThis repository spans healthcare, Svelte, Kafka; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"GossamerEchoRegistryStore crashes after reconnect","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/gossamer/lib/codec/frame.cc b/projects/gossamer/lib/codec/frame.cc\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/lib/codec/frame.cc\n+++ b/projects/gossamer/lib/codec/frame.cc\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 GossamerPrismCacheCoordinator 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":"Bring GossamerCedarPolicyService'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":"GossamerFernSnapshotStore returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/gossamer/ui/settings/PrivacyPane.tsx and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Sable: Ticket OPS-47116: retire the legacy replay path for GossamerEmberRelayFlow\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 GossamerEmberRelayFlow 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":"Incident timeline — INC-47155\n\n08:02 deploy GossamerGarnetModalCoordinator 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current GossamerGarnetModalCoordinator 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":"Tide: Ticket OPS-47126: retire the legacy replay path for GossamerAtlasSearchFlow\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 GossamerAtlasSearchFlow 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":"GossamerPineMetricsCoordinator: polish the last piece","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Draft GossamerVelaDrawerService's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"For GossamerAcornWidgetCoordinator, separate GossamerAcornWidgetCoordinator's policy from transport without behavior changes; once that is complete, correct the known stale timeout beside it. Work from projects/gossamer/web/components/FilterDrawer.vue, stay with Room, and keep VoiceOver and keyboard navigation working. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Could GossamerCopperBridgeService show the active FastAPI sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Does GossamerMoonlitSDKFlow enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists? I want your judgment and walkthrough, not new documentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"The behavior of GossamerRavenSessionStore is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/gossamer/infra/modules/edge/main.tf. 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- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current Room operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka monorepo, so keep ownership and handoff points understandable in a small review.\n\nProduce durable prose rather than a code assessment or implementation change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"GossamerLumenChartCoordinator is blocking the next release because an accessibility label that reads the internal enum. I need two concrete outcomes from a single pass: finish GossamerLumenChartCoordinator's responsive empty and retry states, and capture the contract and rollback note for consumers. Use the existing Swift 6 conventions in projects/gossamer/engine/render/atlas.cpp; keep VoiceOver and keyboard navigation working. 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":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.75,"slice":"mixed","lang":"en"} +{"prompt":"Could GossamerCopperBridgeService show the active FastAPI sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Does GossamerMoonlitSDKFlow enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists? I want your judgment and walkthrough, not new documentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"The behavior of GossamerRavenSessionStore is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/gossamer/infra/modules/edge/main.tf. 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- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current Room operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka monorepo, so keep ownership and handoff points understandable in a small review.\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":"GossamerLumenChartCoordinator is blocking the next release because an accessibility label that reads the internal enum. I need two concrete outcomes from a single pass: finish GossamerLumenChartCoordinator's responsive empty and retry states, and capture the contract and rollback note for consumers. Use the existing Swift 6 conventions in projects/gossamer/engine/render/atlas.cpp; keep VoiceOver and keyboard navigation working. 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":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Sketch the GossamerEchoRegistryService migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"thread 'tokio-runtime-worker' panicked at projects/gossamer/src/sync/reconcile.ts:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: gossamerslateeditorflow::scheduler::LeaseTask::flush\n at ./projects/gossamer/src/sync/reconcile.ts:217:18\n 4: gossamerslateeditorflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nReconstruct the GossamerSlateEditorFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Two deliverables are holding up GossamerMicaProfileCoordinator. First, assess ownership and failure handling in projects/gossamer/Sources/CLI/Commands/Doctor.swift. In the same workstream, capture the contract and rollback note for consumers. The relevant starting point is projects/gossamer/Sources/CLI/Commands/Doctor.swift, which follows gRPC conventions and currently suffers from lost focus when the drawer animation finishes. Keep voiceover and keyboard navigation working.\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":"review","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"GossamerEchoRegistryCoordinator: diagnose, then document","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"Umbra: # projects/gossamer/infra/modules/edge/main.tf\n[worker.gossamerravensessioncoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossamerravensessioncoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossamerravensessioncoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerRavenSessionCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47158\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/gossamer/infra/modules/edge/main.tf. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.41,"slice":"pasted-context","lang":"en"} -{"prompt":"Ticket OPS-47118: retire the legacy replay path for GossamerEchoRegistryFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for GossamerEchoRegistryFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.65,"slice":"pasted-context","lang":"en"} -{"prompt":"Vela: // projects/gossamer/apps/console/routes/usage.svelte\nfinal class GossamerCinderAuthFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 GossamerCinderAuthFlow 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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"GossamerCloudReconcilerCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"In projects/gossamer/apps/console/routes/usage.svelte hat GossamerCinderAuthService ein sporadisches Problem im OpenTelemetry-Ablauf. Verfolge Queue, Scheduler und Abbruch, vergleiche Hypothesen und finde die Ursache vor jeder Änderung.\n\nRandbedingungen:\n- OpenTelemetry weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf GossamerCinderAuthService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um GossamerCinderAuthService mit OpenTelemetry kompatibel.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"de"} -{"prompt":"UI ticket DES-47151: finish the compact GossamerOspreyJobCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/gossamer/apps/console/routes/usage.svelte\nFramework: OpenTelemetry\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 GossamerOspreyJobCoordinator's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Pin GossamerOrbitSyncService's FastAPI dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"core","lang":"en"} -{"prompt":"Exponha retryAfter em GossamerIrisBatchService","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"pt"} -{"prompt":"GossamerQuartzPlayerCoordinator: could this be clearer","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"vague-eval","lang":"en"} -{"prompt":"Willow: Incident timeline — INC-47141\n\n08:02 deploy GossamerCedarPolicyFlow 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 GossamerCedarPolicyFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"GossamerSlateEditorCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"vague-eval","lang":"en"} -{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current GossamerFlintTimelineStore design actually guarantees what its callers assume. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside GossamerFlintTimelineStore\n- keep VoiceOver and keyboard navigation working\n\nThe relevant code crosses healthcare, Svelte, Kafka. 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.76,"slice":"boundary","lang":"en"} -{"prompt":"Xylem: Incident timeline — INC-47157\n\n08:02 deploy GossamerNimbusFormCoordinator 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 GossamerNimbusFormCoordinator, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.62,"slice":"pasted-context","lang":"en"} -{"prompt":"diff --git a/projects/gossamer/workers/thumbnail/consumer.ex b/projects/gossamer/workers/thumbnail/consumer.ex\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/workers/thumbnail/consumer.ex\n+++ b/projects/gossamer/workers/thumbnail/consumer.ex\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 GossamerWillowCodecFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"GossamerJuniperCLIService'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.19,"slice":"core","lang":"en"} -{"prompt":"Spell GossamerCoralUploadStore's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"boundary","lang":"en"} -{"prompt":"On compact widths, GossamerQuartzPlayerStore'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.54,"slice":"boundary","lang":"en"} -{"prompt":"Assess the GossamerKiteSchedulerStore diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"Lay out a two-milestone strategy for eliminating a misleading timeout name used in five packages in GossamerMoonlitSDKStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Yarrow: diff --git a/projects/gossamer/crates/index/src/segment.rs b/projects/gossamer/crates/index/src/segment.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/crates/index/src/segment.rs\n+++ b/projects/gossamer/crates/index/src/segment.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nAdd the bounded GossamerQuartzPlayerFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"Two asks around GossamerCoralUploadCoordinator: (1) separate GossamerCoralUploadCoordinator's policy from transport without behavior changes; (2) give the existing implementation a read-only safety pass. Keep voiceover and keyboard navigation working, and leave a clear boundary between the resulting artifacts or edits.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"Fresh release brief for GossamerCinderAuthCoordinator:\n- primary outcome: lay out a staged migration for GossamerCinderAuthCoordinator\n- companion outcome: then implement the bounded durable-cursor handler\n- repository entry point: projects/gossamer/app/src/main/SyncWorker.kt\n- platform constraint: OpenTelemetry\n- known complication: timestamps rendered one day ahead near UTC midnight\n\nBoth results are required, but they should remain independently reviewable. Keep voiceover and keyboard navigation working; retain serialization and authorization boundaries; cover cancellation, idempotent retries, and rollback; and avoid drive-by cleanup. Use the code as the source of truth, call out assumptions, and state how an on-call engineer can tell that either part is unsafe to ship.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.91,"slice":"mixed","lang":"en"} -{"prompt":"GossamerOspreyJobStore'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.12,"slice":"core","lang":"en"} -{"prompt":"Zephyr: Two asks around GossamerAmberFilterCoordinator: (1) assess ownership and failure handling in projects/gossamer/infra/modules/edge/main.tf; (2) capture the contract and rollback note for consumers. Keep voiceover and keyboard navigation working, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"En projects/gossamer/app/src/main/SyncWorker.kt, GossamerCinderAuthStore tiene un problema intermitente en el flujo de OpenTelemetry. Separa responsabilidades y elimina duplicación, conservando API, wire values, orden y comportamiento observable.\n\nRestricciones:\n- seguir con OpenTelemetry\n- conservar compatibilidad y cancelación\n- limitar el cambio a GossamerCinderAuthStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con OpenTelemetry alrededor de GossamerCinderAuthStore.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"es"} -{"prompt":"GossamerFernSnapshotCoordinator: untangle the messy bit","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"vague-eval","lang":"en"} -{"prompt":"What sequence would let GossamerJuniperCLIStore adopt FastAPI 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.72,"slice":"boundary","lang":"en"} -{"prompt":"Checkout: # projects/gossamer/crates/index/src/segment.rs\n[worker.gossamersprucedaemonflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossamersprucedaemonflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossamersprucedaemonflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerSpruceDaemonFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47114\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/gossamer/crates/index/src/segment.rs and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.43,"slice":"pasted-context","lang":"en"} -{"prompt":"We expect GossamerEmberRelayStore to outgrow its current OpenTelemetry arrangement next quarter, but changing everything at once would be risky. 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- keep VoiceOver and keyboard navigation working\n- stay compatible with the existing OpenTelemetry deployment\n- keep the work scoped to GossamerEmberRelayStore and its direct tests\n\nThis repository spans healthcare, Svelte, Kafka; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.81,"slice":"boundary","lang":"en"} -{"prompt":"Test Suite 'GossamerCopperBridgeFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[GossamerCopperBridgeFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/gossamer/pkg/cache/lease.rs:144: error: -[GossamerCopperBridgeFlowTests 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 '-[GossamerCopperBridgeFlowTests 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\nDetermine why GossamerCopperBridgeFlow 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.96,"slice":"pasted-context","lang":"en"} -{"prompt":"PM is preparing the GossamerLumenChartStore rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside GossamerLumenChartStore\n- keep VoiceOver and keyboard navigation working\n\nThe relevant code crosses healthcare, Svelte, Kafka. Prefer evidence from the repository and make any assumption explicit.\n\nProduce durable prose rather than a code assessment or implementation change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.54,"slice":"boundary","lang":"en"} -{"prompt":"Corrige le timeout de GossamerIrisBatchStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"boundary","lang":"fr"} -{"prompt":"Sketch the GossamerSummitProxyStore migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"UI ticket DES-47159: finish the compact GossamerFlintTimelineCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/gossamer/config/staging.toml\nFramework: FastAPI\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 GossamerFlintTimelineCoordinator 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.78,"slice":"pasted-context","lang":"en"} -{"prompt":"diff --git a/projects/gossamer/internal/auth/refresh.go b/projects/gossamer/internal/auth/refresh.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/internal/auth/refresh.go\n+++ b/projects/gossamer/internal/auth/refresh.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate GossamerTideWorkerFlow'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.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Support wants the behavior in projects/gossamer/workers/thumbnail/consumer.ex recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"Ticket OPS-47138: retire the legacy replay path for GossamerLedgerGateFlow\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 GossamerLedgerGateFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"pasted-context","lang":"en"} -{"prompt":"GossamerTideWorkerCoordinator: make this less weird","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"vague-eval","lang":"en"} -{"prompt":"Our support and SDK teams keep answering the same questions about GossamerFlintTimelineService, but the current prose in projects/gossamer/packages/api/openapi.yaml only describes the happy path. 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- keep VoiceOver and keyboard navigation working\n- stay compatible with the existing FastAPI deployment\n- keep the work scoped to GossamerFlintTimelineService and its direct tests\n\nThis repository spans healthcare, Svelte, Kafka; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Compare GossamerMarbleTokenStore's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Security flagged GossamerMicaProfileService for a read-only pass because its gRPC boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current gRPC operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"This should remain a deliberately small patch: GossamerMicaProfileStore has one known configuration mistake in projects/gossamer/Sources/CLI/Commands/Doctor.swift, not an open-ended failure investigation. 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- keep VoiceOver and keyboard navigation working\n- stay compatible with the existing gRPC deployment\n- keep the work scoped to GossamerMicaProfileStore and its direct tests\n\nThis repository spans healthcare, Svelte, Kafka; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.25,"slice":"boundary","lang":"en"} -{"prompt":"Outline a safer GossamerKiteSchedulerService cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"The GossamerOpalRouterService surface in projects/gossamer/packages/api/openapi.yaml 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.43,"slice":"core","lang":"en"} -{"prompt":"Exporter: Two asks around GossamerMosaicGridCoordinator: (1) ship the idempotent GossamerMosaicGridCoordinator replay endpoint; (2) give the existing implementation a read-only safety pass. Keep voiceover and keyboard navigation working, and leave a clear boundary between the resulting artifacts or edits.","purpose":"backendImpl","secondary":"review","mixed":true,"difficulty":0.67,"slice":"mixed","lang":"en"} -{"prompt":"# projects/gossamer/packages/api/openapi.yaml\n[worker.gossameropalrouterflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossameropalrouterflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossameropalrouterflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerOpalRouterFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47149\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/gossamer/packages/api/openapi.yaml. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.43,"slice":"pasted-context","lang":"en"} -{"prompt":"# projects/gossamer/services/ledger/replay.go\n[worker.gossameracornwidgetflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossameracornwidgetflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossameracornwidgetflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerAcornWidgetFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47133\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 GossamerAcornWidgetFlow'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.41,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a bounded GossamerCopperBridgeStore export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"For GossamerIrisBatchCoordinator, produce a consumer guide for GossamerIrisBatchCoordinator; once that is complete, give the existing implementation a read-only safety pass. Work from projects/gossamer/workers/thumbnail/consumer.ex, stay with Swift 6, and keep VoiceOver and keyboard navigation working. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.48,"slice":"mixed","lang":"en"} +{"prompt":"thread 'tokio-runtime-worker' panicked at projects/gossamer/src/sync/reconcile.ts:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: gossamerslateeditorflow::scheduler::LeaseTask::flush\n at ./projects/gossamer/src/sync/reconcile.ts:217:18\n 4: gossamerslateeditorflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nReconstruct the GossamerSlateEditorFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Two deliverables are holding up GossamerMicaProfileCoordinator. First, assess ownership and failure handling in projects/gossamer/Sources/CLI/Commands/Doctor.swift. In the same workstream, capture the contract and rollback note for consumers. The relevant starting point is projects/gossamer/Sources/CLI/Commands/Doctor.swift, which follows gRPC conventions and currently suffers from lost focus when the drawer animation finishes. Keep voiceover and keyboard navigation working.\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":"review","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"GossamerEchoRegistryCoordinator: diagnose, then document","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Umbra: # projects/gossamer/infra/modules/edge/main.tf\n[worker.gossamerravensessioncoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossamerravensessioncoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossamerravensessioncoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerRavenSessionCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47158\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/gossamer/infra/modules/edge/main.tf. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-47118: retire the legacy replay path for GossamerEchoRegistryFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for GossamerEchoRegistryFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"Vela: // projects/gossamer/apps/console/routes/usage.svelte\nfinal class GossamerCinderAuthFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 GossamerCinderAuthFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"GossamerCloudReconcilerCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"In projects/gossamer/apps/console/routes/usage.svelte hat GossamerCinderAuthService ein sporadisches Problem im OpenTelemetry-Ablauf. Verfolge Queue, Scheduler und Abbruch, vergleiche Hypothesen und finde die Ursache vor jeder Änderung.\n\nRandbedingungen:\n- OpenTelemetry weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf GossamerCinderAuthService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um GossamerCinderAuthService mit OpenTelemetry kompatibel.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} +{"prompt":"UI ticket DES-47151: finish the compact GossamerOspreyJobCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/gossamer/apps/console/routes/usage.svelte\nFramework: OpenTelemetry\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 GossamerOspreyJobCoordinator'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":"Pin GossamerOrbitSyncService's FastAPI dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Exponha retryAfter em GossamerIrisBatchService","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"pt"} +{"prompt":"GossamerQuartzPlayerCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Willow: Incident timeline — INC-47141\n\n08:02 deploy GossamerCedarPolicyFlow 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 GossamerCedarPolicyFlow 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":"GossamerSlateEditorCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current GossamerFlintTimelineStore design actually guarantees what its callers assume. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside GossamerFlintTimelineStore\n- keep VoiceOver and keyboard navigation working\n\nThe relevant code crosses healthcare, Svelte, Kafka. 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":"Xylem: Incident timeline — INC-47157\n\n08:02 deploy GossamerNimbusFormCoordinator 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 GossamerNimbusFormCoordinator, 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":"diff --git a/projects/gossamer/workers/thumbnail/consumer.ex b/projects/gossamer/workers/thumbnail/consumer.ex\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/workers/thumbnail/consumer.ex\n+++ b/projects/gossamer/workers/thumbnail/consumer.ex\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 GossamerWillowCodecFlow'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":"GossamerJuniperCLIService'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":"Spell GossamerCoralUploadStore's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"On compact widths, GossamerQuartzPlayerStore'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.6,"slice":"core","lang":"en"} +{"prompt":"Assess the GossamerKiteSchedulerStore diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating a misleading timeout name used in five packages in GossamerMoonlitSDKStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Yarrow: diff --git a/projects/gossamer/crates/index/src/segment.rs b/projects/gossamer/crates/index/src/segment.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/crates/index/src/segment.rs\n+++ b/projects/gossamer/crates/index/src/segment.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nAdd the bounded GossamerQuartzPlayerFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Two asks around GossamerCoralUploadCoordinator: (1) separate GossamerCoralUploadCoordinator's policy from transport without behavior changes; (2) give the existing implementation a read-only safety pass. Keep voiceover and keyboard navigation working, and leave a clear boundary between the resulting artifacts or edits.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Fresh release brief for GossamerCinderAuthCoordinator:\n- primary outcome: lay out a staged migration for GossamerCinderAuthCoordinator\n- companion outcome: then implement the bounded durable-cursor handler\n- repository entry point: projects/gossamer/app/src/main/SyncWorker.kt\n- platform constraint: OpenTelemetry\n- known complication: timestamps rendered one day ahead near UTC midnight\n\nBoth results are required, but they should remain independently reviewable. Keep voiceover and keyboard navigation working; retain serialization and authorization boundaries; cover cancellation, idempotent retries, and rollback; and avoid drive-by cleanup. Use the code as the source of truth, call out assumptions, and state how an on-call engineer can tell that either part is unsafe to ship.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"GossamerOspreyJobStore's metric is misspelled as succesful_total in one declaration. Correct that literal and its exact test expectation, without renaming anything else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Zephyr: Two asks around GossamerAmberFilterCoordinator: (1) assess ownership and failure handling in projects/gossamer/infra/modules/edge/main.tf; (2) capture the contract and rollback note for consumers. Keep voiceover and keyboard navigation working, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"En projects/gossamer/app/src/main/SyncWorker.kt, GossamerCinderAuthStore tiene un problema intermitente en el flujo de OpenTelemetry. Separa responsabilidades y elimina duplicación, conservando API, wire values, orden y comportamiento observable.\n\nRestricciones:\n- seguir con OpenTelemetry\n- conservar compatibilidad y cancelación\n- limitar el cambio a GossamerCinderAuthStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con OpenTelemetry alrededor de GossamerCinderAuthStore.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"es"} +{"prompt":"GossamerFernSnapshotCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"What sequence would let GossamerJuniperCLIStore adopt FastAPI 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.8,"slice":"core","lang":"en"} +{"prompt":"Checkout: # projects/gossamer/crates/index/src/segment.rs\n[worker.gossamersprucedaemonflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossamersprucedaemonflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossamersprucedaemonflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerSpruceDaemonFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47114\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/gossamer/crates/index/src/segment.rs and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"We expect GossamerEmberRelayStore to outgrow its current OpenTelemetry arrangement next quarter, but changing everything at once would be risky. 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- keep VoiceOver and keyboard navigation working\n- stay compatible with the existing OpenTelemetry deployment\n- keep the work scoped to GossamerEmberRelayStore and its direct tests\n\nThis repository spans healthcare, Svelte, Kafka; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'GossamerCopperBridgeFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[GossamerCopperBridgeFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/gossamer/pkg/cache/lease.rs:144: error: -[GossamerCopperBridgeFlowTests 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 '-[GossamerCopperBridgeFlowTests 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\nDetermine why GossamerCopperBridgeFlow 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":"PM is preparing the GossamerLumenChartStore rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside GossamerLumenChartStore\n- keep VoiceOver and keyboard navigation working\n\nThe relevant code crosses healthcare, Svelte, Kafka. Prefer evidence from the repository and make any assumption explicit.\n\nProduce durable prose rather than a code assessment or implementation change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Corrige le timeout de GossamerIrisBatchStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"fr"} +{"prompt":"Sketch the GossamerSummitProxyStore migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-47159: finish the compact GossamerFlintTimelineCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/gossamer/config/staging.toml\nFramework: FastAPI\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 GossamerFlintTimelineCoordinator 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":"diff --git a/projects/gossamer/internal/auth/refresh.go b/projects/gossamer/internal/auth/refresh.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/internal/auth/refresh.go\n+++ b/projects/gossamer/internal/auth/refresh.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate GossamerTideWorkerFlow'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":"Support wants the behavior in projects/gossamer/workers/thumbnail/consumer.ex recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-47138: retire the legacy replay path for GossamerLedgerGateFlow\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 GossamerLedgerGateFlow 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":"GossamerTideWorkerCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Our support and SDK teams keep answering the same questions about GossamerFlintTimelineService, but the current prose in projects/gossamer/packages/api/openapi.yaml only describes the happy path. 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- keep VoiceOver and keyboard navigation working\n- stay compatible with the existing FastAPI deployment\n- keep the work scoped to GossamerFlintTimelineService and its direct tests\n\nThis repository spans healthcare, Svelte, Kafka; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Compare GossamerMarbleTokenStore's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Security flagged GossamerMicaProfileService for a read-only pass because its gRPC boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current gRPC operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka 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":"This should remain a deliberately small patch: GossamerMicaProfileStore has one known configuration mistake in projects/gossamer/Sources/CLI/Commands/Doctor.swift, not an open-ended failure investigation. 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- keep VoiceOver and keyboard navigation working\n- stay compatible with the existing gRPC deployment\n- keep the work scoped to GossamerMicaProfileStore and its direct tests\n\nThis repository spans healthcare, Svelte, Kafka; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Outline a safer GossamerKiteSchedulerService cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"The GossamerOpalRouterService surface in projects/gossamer/packages/api/openapi.yaml 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":"Exporter: Two asks around GossamerMosaicGridCoordinator: (1) ship the idempotent GossamerMosaicGridCoordinator replay endpoint; (2) give the existing implementation a read-only safety pass. Keep voiceover and keyboard navigation working, and leave a clear boundary between the resulting artifacts or edits.","purpose":"backendImpl","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"# projects/gossamer/packages/api/openapi.yaml\n[worker.gossameropalrouterflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossameropalrouterflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossameropalrouterflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerOpalRouterFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47149\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/gossamer/packages/api/openapi.yaml. 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":"# projects/gossamer/services/ledger/replay.go\n[worker.gossameracornwidgetflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossameracornwidgetflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossameracornwidgetflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerAcornWidgetFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47133\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 GossamerAcornWidgetFlow'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":"Add a bounded GossamerCopperBridgeStore export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"For GossamerIrisBatchCoordinator, produce a consumer guide for GossamerIrisBatchCoordinator; once that is complete, give the existing implementation a read-only safety pass. Work from projects/gossamer/workers/thumbnail/consumer.ex, stay with Swift 6, and keep VoiceOver and keyboard navigation working. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Check GossamerMapleQueueService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"GossamerKiteSchedulerCoordinator: restructure, then correct","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"GossamerGarnetModalFlow returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/gossamer/ml/pipeline/features.py and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Decouple GossamerSpruceDaemonService's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"GossamerOpalRouterCoordinator: sort out the rough edge","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"vague-eval","lang":"en"} -{"prompt":"Three teams extended GossamerDeltaCanvasService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current FastAPI operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Scheduler: diff --git a/projects/gossamer/lib/codec/frame.cc b/projects/gossamer/lib/codec/frame.cc\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/lib/codec/frame.cc\n+++ b/projects/gossamer/lib/codec/frame.cc\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 GossamerLumenChartFlow'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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Investigate the GossamerMosaicGridService hang","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Could the reasoning behind GossamerSlateEditorStore's OpenTelemetry choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"Does GossamerAmberFilterStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"HinterlandMicaProfileCoordinator needs a paired pass: assess ownership and failure handling in projects/hinterland/workers/thumbnail/consumer.ex, plus capture the contract and rollback note for consumers. Use projects/hinterland/workers/thumbnail/consumer.ex as the source of truth, preserve the Playwright contract, and avoid unrelated cleanup.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Ticket OPS-48127: retire the legacy replay path for HinterlandDeltaCanvasFlow\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 HinterlandDeltaCanvasFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"thread 'tokio-runtime-worker' panicked at projects/hinterland/src/sync/reconcile.ts:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: hinterlanddriftconsoleflow::scheduler::LeaseTask::flush\n at ./projects/hinterland/src/sync/reconcile.ts:217:18\n 4: hinterlanddriftconsoleflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nFind the source of this HinterlandDriftConsoleFlow 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.92,"slice":"pasted-context","lang":"en"} -{"prompt":"Clarify HinterlandPrismCacheService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"Dashboard: # projects/hinterland/crates/index/src/segment.rs\n[worker.hinterlandwillowcodecflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandwillowcodecflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandwillowcodecflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandWillowCodecFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48140\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/hinterland/crates/index/src/segment.rs and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"pasted-context","lang":"en"} -{"prompt":"Corrige le timeout de HinterlandDeltaCanvasStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"boundary","lang":"fr"} -{"prompt":"En projects/hinterland/workers/thumbnail/consumer.ex, HinterlandBeaconStoreService tiene un problema intermitente en el flujo de Playwright. Redacta una guía para consumidores con contrato, errores, retry y un ejemplo copiable; no cambies el handler.\n\nRestricciones:\n- seguir con Playwright\n- conservar compatibilidad y cancelación\n- limitar el cambio a HinterlandBeaconStoreService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"es"} -{"prompt":"Worker: # projects/hinterland/workers/thumbnail/consumer.ex\n[worker.hinterlandnovapickerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandnovapickerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandnovapickerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandNovaPickerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48123\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 HinterlandNovaPickerFlow'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.41,"slice":"pasted-context","lang":"en"} -{"prompt":"Simulator: # projects/hinterland/ui/settings/PrivacyPane.tsx\n[worker.hinterlandmicaprofileflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandmicaprofileflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandmicaprofileflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandMicaProfileFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48133\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/hinterland/ui/settings/PrivacyPane.tsx. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.41,"slice":"pasted-context","lang":"en"} -{"prompt":"Runbook: projects/hinterland/packages/api/openapi.yaml 里的 HinterlandLumenChartService 最近在 Redis Streams 流程中出现间歇性问题。 请给出阶段、兼容层、指标、rollback 和 ownership，先不要修改代码。\n\n约束：\n- 继续使用 Redis Streams\n- 保持兼容性和取消语义\n- 改动只限于 HinterlandLumenChartService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"zh"} -{"prompt":"The minimum supported React 19 version in projects/hinterland/Sources/CLI/Commands/Doctor.swift is one patch behind the lockfile. Align that single value and regenerate only the affected metadata.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"boundary","lang":"en"} -{"prompt":"Wire a HinterlandQuartzPlayerFlow background task in projects/hinterland/app/src/main/SyncWorker.kt that expires abandoned sessions, records an OpenTelemetry span, and yields cleanly when shutdown begins.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"Two asks around HinterlandSableParserCoordinator: (1) assess ownership and failure handling in projects/hinterland/Sources/App/SessionStore.swift; (2) capture the contract and rollback note for consumers. Avoid a schema migration in this release, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.62,"slice":"mixed","lang":"en"} -{"prompt":"HinterlandEchoRegistryCoordinator: make this less weird","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"vague-eval","lang":"en"} -{"prompt":"HinterlandWillowCodecCoordinator: smooth out this interaction","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"HinterlandCinderAuthCoordinator: deal with the small issue","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"vague-eval","lang":"en"} -{"prompt":"Could HinterlandFlintTimelineService migrate incrementally?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Sketch the HinterlandCopperBridgeService migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Design handed over a final pass for HinterlandWrenExportService, and the basic data flow in projects/hinterland/config/staging.toml already works. 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- avoid a schema migration in this release\n- stay compatible with the existing Redis Streams deployment\n- keep the work scoped to HinterlandWrenExportService and its direct tests\n\nSeveral teams work in this search, Terraform, Flutter monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Test Suite 'HinterlandSlateEditorCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[HinterlandSlateEditorCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/hinterland/services/ledger/replay.go:144: error: -[HinterlandSlateEditorCoordinatorTests 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 '-[HinterlandSlateEditorCoordinatorTests 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 HinterlandSlateEditorCoordinator's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Support wants the behavior in projects/hinterland/apps/console/routes/usage.svelte recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary. The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"en"} -{"prompt":"Is HinterlandRavenSessionStore safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"HinterlandLedgerGateCoordinator is blocking the next release because lease renewal code copied across three workers. I need two concrete outcomes from a single pass: produce a consumer guide for HinterlandLedgerGateCoordinator, and give the existing implementation a read-only safety pass. Use the existing React 19 conventions in projects/hinterland/cmd/exporter/main.py; avoid a schema migration in this release. Keep the outcomes distinct so reviewers can see which evidence supports the assessment and which files or prose satisfy the requested change.\n\nConstraints:\n- preserve public wire values and tenant boundaries\n- cover cancellation and retry behavior\n- avoid generated code and unrelated cleanup\n- include a rollback trigger that an on-call engineer can measure\n\nThis is a fresh workstream for the release, so derive everything from the repository and the context here.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.61,"slice":"mixed","lang":"en"} -{"prompt":"Trace: # projects/hinterland/db/migrations/20260730_events.sql\n[worker.hinterlandflinttimelineflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandflinttimelineflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandflinttimelineflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandFlintTimelineFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48132\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 HinterlandFlintTimelineFlow'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.38,"slice":"pasted-context","lang":"en"} -{"prompt":"Responsive layout for HinterlandNimbusFormStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"boundary","lang":"en"} -{"prompt":"For HinterlandPrismCacheCoordinator, lay out a staged migration for HinterlandPrismCacheCoordinator; once that is complete, then implement the bounded durable-cursor handler. Work from projects/hinterland/packages/api/openapi.yaml, stay with Redis Streams, and avoid a schema migration in this release. Keep the two outcomes separately reviewable.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Extract HinterlandAsterWebhookStore's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"GossamerKiteSchedulerCoordinator: restructure, then correct","purpose":"refactor","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"GossamerGarnetModalFlow returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/gossamer/ml/pipeline/features.py and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Decouple GossamerSpruceDaemonService's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"GossamerOpalRouterCoordinator: sort out the rough edge","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Three teams extended GossamerDeltaCanvasService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current FastAPI operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka 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":"Scheduler: diff --git a/projects/gossamer/lib/codec/frame.cc b/projects/gossamer/lib/codec/frame.cc\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/lib/codec/frame.cc\n+++ b/projects/gossamer/lib/codec/frame.cc\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 GossamerLumenChartFlow'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":"Investigate the GossamerMosaicGridService hang","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Could the reasoning behind GossamerSlateEditorStore's OpenTelemetry choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Does GossamerAmberFilterStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"HinterlandMicaProfileCoordinator needs a paired pass: assess ownership and failure handling in projects/hinterland/workers/thumbnail/consumer.ex, plus capture the contract and rollback note for consumers. Use projects/hinterland/workers/thumbnail/consumer.ex as the source of truth, preserve the Playwright contract, and avoid unrelated cleanup.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Ticket OPS-48127: retire the legacy replay path for HinterlandDeltaCanvasFlow\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 HinterlandDeltaCanvasFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"thread 'tokio-runtime-worker' panicked at projects/hinterland/src/sync/reconcile.ts:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: hinterlanddriftconsoleflow::scheduler::LeaseTask::flush\n at ./projects/hinterland/src/sync/reconcile.ts:217:18\n 4: hinterlanddriftconsoleflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nFind the source of this HinterlandDriftConsoleFlow symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Clarify HinterlandPrismCacheService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Dashboard: # projects/hinterland/crates/index/src/segment.rs\n[worker.hinterlandwillowcodecflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandwillowcodecflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandwillowcodecflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandWillowCodecFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48140\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/hinterland/crates/index/src/segment.rs and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Corrige le timeout de HinterlandDeltaCanvasStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"fr"} +{"prompt":"En projects/hinterland/workers/thumbnail/consumer.ex, HinterlandBeaconStoreService tiene un problema intermitente en el flujo de Playwright. Redacta una guía para consumidores con contrato, errores, retry y un ejemplo copiable; no cambies el handler.\n\nRestricciones:\n- seguir con Playwright\n- conservar compatibilidad y cancelación\n- limitar el cambio a HinterlandBeaconStoreService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} +{"prompt":"Worker: # projects/hinterland/workers/thumbnail/consumer.ex\n[worker.hinterlandnovapickerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandnovapickerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandnovapickerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandNovaPickerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48123\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 HinterlandNovaPickerFlow'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":"Simulator: # projects/hinterland/ui/settings/PrivacyPane.tsx\n[worker.hinterlandmicaprofileflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandmicaprofileflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandmicaprofileflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandMicaProfileFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48133\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/hinterland/ui/settings/PrivacyPane.tsx. 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":"Runbook: projects/hinterland/packages/api/openapi.yaml 里的 HinterlandLumenChartService 最近在 Redis Streams 流程中出现间歇性问题。 请给出阶段、兼容层、指标、rollback 和 ownership，先不要修改代码。\n\n约束：\n- 继续使用 Redis Streams\n- 保持兼容性和取消语义\n- 改动只限于 HinterlandLumenChartService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"The minimum supported React 19 version in projects/hinterland/Sources/CLI/Commands/Doctor.swift is one patch behind the lockfile. Align that single value and regenerate only the affected metadata.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Wire a HinterlandQuartzPlayerFlow background task in projects/hinterland/app/src/main/SyncWorker.kt that expires abandoned sessions, records an OpenTelemetry span, and yields cleanly when shutdown begins.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Two asks around HinterlandSableParserCoordinator: (1) assess ownership and failure handling in projects/hinterland/Sources/App/SessionStore.swift; (2) capture the contract and rollback note for consumers. Avoid a schema migration in this release, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"HinterlandEchoRegistryCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"HinterlandWillowCodecCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"HinterlandCinderAuthCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Could HinterlandFlintTimelineService migrate incrementally?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"Sketch the HinterlandCopperBridgeService migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Design handed over a final pass for HinterlandWrenExportService, and the basic data flow in projects/hinterland/config/staging.toml already works. 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- avoid a schema migration in this release\n- stay compatible with the existing Redis Streams deployment\n- keep the work scoped to HinterlandWrenExportService and its direct tests\n\nSeveral teams work in this search, Terraform, Flutter 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":"Test Suite 'HinterlandSlateEditorCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[HinterlandSlateEditorCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/hinterland/services/ledger/replay.go:144: error: -[HinterlandSlateEditorCoordinatorTests 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 '-[HinterlandSlateEditorCoordinatorTests 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 HinterlandSlateEditorCoordinator's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Support wants the behavior in projects/hinterland/apps/console/routes/usage.svelte recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary. The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Is HinterlandRavenSessionStore safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"HinterlandLedgerGateCoordinator is blocking the next release because lease renewal code copied across three workers. I need two concrete outcomes from a single pass: produce a consumer guide for HinterlandLedgerGateCoordinator, and give the existing implementation a read-only safety pass. Use the existing React 19 conventions in projects/hinterland/cmd/exporter/main.py; avoid a schema migration in this release. Keep the outcomes distinct so reviewers can see which evidence supports the assessment and which files or prose satisfy the requested change.\n\nConstraints:\n- preserve public wire values and tenant boundaries\n- cover cancellation and retry behavior\n- avoid generated code and unrelated cleanup\n- include a rollback trigger that an on-call engineer can measure\n\nThis is a fresh workstream for the release, so derive everything from the repository and the context here.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Trace: # projects/hinterland/db/migrations/20260730_events.sql\n[worker.hinterlandflinttimelineflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandflinttimelineflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandflinttimelineflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandFlintTimelineFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48132\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 HinterlandFlintTimelineFlow'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":"Responsive layout for HinterlandNimbusFormStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"For HinterlandPrismCacheCoordinator, lay out a staged migration for HinterlandPrismCacheCoordinator; once that is complete, then implement the bounded durable-cursor handler. Work from projects/hinterland/packages/api/openapi.yaml, stay with Redis Streams, and avoid a schema migration in this release. Keep the two outcomes separately reviewable.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Extract HinterlandAsterWebhookStore's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Outline a safer HinterlandGarnetModalService cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"HinterlandSlateEditorService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- avoid a schema migration in this release\n- retain the current Terraform operational envelope\n\nThe relevant code crosses search, Terraform, Flutter. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Does HinterlandIrisBatchStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"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_48135'\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_48135'::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 HinterlandLumenChartFlow'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.81,"slice":"pasted-context","lang":"en"} -{"prompt":"Lay out a two-milestone strategy for eliminating two validators with subtly different error strings in HinterlandBirchMigratorService, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Give HinterlandFlintTimelineStore a loading skeleton","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"boundary","lang":"en"} -{"prompt":"Style HinterlandMoonlitSDKService's offline state","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"diff --git a/projects/hinterland/ui/settings/PrivacyPane.tsx b/projects/hinterland/ui/settings/PrivacyPane.tsx\nindex 62d71aa..90f3c1e 100644\n--- a/projects/hinterland/ui/settings/PrivacyPane.tsx\n+++ b/projects/hinterland/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\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Read the artifact above as a skeptical reviewer. Is HinterlandPineMetricsFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"es"} +{"prompt":"HinterlandSlateEditorService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- avoid a schema migration in this release\n- retain the current Terraform operational envelope\n\nThe relevant code crosses search, Terraform, Flutter. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Does HinterlandIrisBatchStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"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_48135'\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_48135'::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 HinterlandLumenChartFlow'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.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating two validators with subtly different error strings in HinterlandBirchMigratorService, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Give HinterlandFlintTimelineStore a loading skeleton","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Style HinterlandMoonlitSDKService's offline state","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/hinterland/ui/settings/PrivacyPane.tsx b/projects/hinterland/ui/settings/PrivacyPane.tsx\nindex 62d71aa..90f3c1e 100644\n--- a/projects/hinterland/ui/settings/PrivacyPane.tsx\n+++ b/projects/hinterland/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\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Read the artifact above as a skeptical reviewer. Is HinterlandPineMetricsFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} {"prompt":"Two engineers disagree about whether HinterlandWrenExportStore's cache is authoritative. Walk the reads and writes in projects/hinterland/packages/api/openapi.yaml and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"We need to move HinterlandWillowCodecService from the legacy store to Redis Streams. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Why is HinterlandMicaProfileService stalling?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"HinterlandNovaPickerCoordinator: polish, then document","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.61,"slice":"mixed","lang":"en"} -{"prompt":"// projects/hinterland/services/ledger/replay.go\nfinal class HinterlandEmberRelayFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandEmberRelayFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"projects/hinterland/Sources/CLI/Commands/Doctor.swift now contains HinterlandMarbleTokenService'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.55,"slice":"core","lang":"en"} -{"prompt":"The destination for HinterlandFernSnapshotService is broadly agreed; the missing piece is a reversible route from projects/hinterland/pkg/cache/lease.rs to that target. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandFernSnapshotService\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Ticket OPS-48125: retire the legacy replay path for HinterlandPrismCacheFlow\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 HinterlandPrismCacheFlow 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.57,"slice":"pasted-context","lang":"en"} -{"prompt":"HinterlandSableParserService's Doctor.swift needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"Diff: The public surface of HinterlandPineMetricsService is frozen, but its internal ownership in projects/hinterland/ui/settings/PrivacyPane.tsx is difficult to test and even harder to change safely. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandPineMetricsService\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"HinterlandBirchMigratorCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"vague-eval","lang":"en"} -{"prompt":"Ownership of HinterlandIrisBatchService is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- avoid a schema migration in this release\n- retain the current Redis Streams operational envelope\n\nThe relevant code crosses search, Terraform, Flutter. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Profiler: // projects/hinterland/Sources/App/SessionStore.swift\nfinal class HinterlandBirchMigratorFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandBirchMigratorFlow 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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Could the reasoning behind HinterlandDriftConsoleService's Core Data choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"Console: Ticket OPS-48119: retire the legacy replay path for HinterlandCloudReconcilerFlow\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 HinterlandCloudReconcilerFlow 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.67,"slice":"pasted-context","lang":"en"} -{"prompt":"Workspace: diff --git a/projects/hinterland/ui/settings/PrivacyPane.tsx b/projects/hinterland/ui/settings/PrivacyPane.tsx\nindex 62d71aa..90f3c1e 100644\n--- a/projects/hinterland/ui/settings/PrivacyPane.tsx\n+++ b/projects/hinterland/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\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Wire HinterlandBeaconStoreCoordinator'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.89,"slice":"pasted-context","lang":"ja"} -{"prompt":"HinterlandHarborIndexStore is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- avoid a schema migration in this release\n- retain the current React 19 operational envelope\n\nThe relevant code crosses search, Terraform, Flutter. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"Repository: Could the reasoning behind HinterlandWillowCodecStore's Redis Streams choices be captured as an ADR for engineers joining the project next quarter? The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"boundary","lang":"en"} -{"prompt":"Assess the HinterlandCedarPolicyService diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"We need to move HinterlandAcornWidgetFlow from the legacy store to React 19. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"Move HinterlandEchoRegistryStore'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.55,"slice":"boundary","lang":"en"} -{"prompt":"Pipeline: // projects/hinterland/Sources/App/SessionStore.swift\nfinal class HinterlandHarborIndexFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandHarborIndexFlow 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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"HinterlandMapleQueueCoordinator: something is off here","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"PM is preparing the HinterlandCedarPolicyStore rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandCedarPolicyStore\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.\n\nThe server contract is the subject, but the requested output is documentation rather than handler code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Find HinterlandCraneWorkspaceService's duplicate retry source","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Gateway: diff --git a/projects/hinterland/ml/pipeline/features.py b/projects/hinterland/ml/pipeline/features.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/hinterland/ml/pipeline/features.py\n+++ b/projects/hinterland/ml/pipeline/features.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\nRead the artifact above as a skeptical reviewer. Is HinterlandRavenSessionFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"HinterlandVelaDrawerCoordinator: give it a nicer flow","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"vague-eval","lang":"en"} -{"prompt":"I inherited HinterlandRainfallDBStore and need a careful read of projects/hinterland/config/staging.toml before I can sign off on the next release. 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- avoid a schema migration in this release\n- stay compatible with the existing Redis Streams deployment\n- keep the work scoped to HinterlandRainfallDBStore and its direct tests\n\nSeveral teams work in this search, Terraform, Flutter monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.66,"slice":"boundary","lang":"en"} -{"prompt":"HinterlandAtlasSearchService'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.19,"slice":"core","lang":"en"} +{"prompt":"We need to move HinterlandWillowCodecService from the legacy store to Redis Streams. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Why is HinterlandMicaProfileService stalling?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"HinterlandNovaPickerCoordinator: polish, then document","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"// projects/hinterland/services/ledger/replay.go\nfinal class HinterlandEmberRelayFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandEmberRelayFlow; 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":"projects/hinterland/Sources/CLI/Commands/Doctor.swift now contains HinterlandMarbleTokenService'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.4,"slice":"core","lang":"en"} +{"prompt":"The destination for HinterlandFernSnapshotService is broadly agreed; the missing piece is a reversible route from projects/hinterland/pkg/cache/lease.rs to that target. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandFernSnapshotService\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-48125: retire the legacy replay path for HinterlandPrismCacheFlow\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 HinterlandPrismCacheFlow 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":"HinterlandSableParserService's Doctor.swift needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Diff: The public surface of HinterlandPineMetricsService is frozen, but its internal ownership in projects/hinterland/ui/settings/PrivacyPane.tsx is difficult to test and even harder to change safely. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandPineMetricsService\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"HinterlandBirchMigratorCoordinator: rethink this area","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Ownership of HinterlandIrisBatchService is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- avoid a schema migration in this release\n- retain the current Redis Streams operational envelope\n\nThe relevant code crosses search, Terraform, Flutter. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Profiler: // projects/hinterland/Sources/App/SessionStore.swift\nfinal class HinterlandBirchMigratorFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandBirchMigratorFlow 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":"Could the reasoning behind HinterlandDriftConsoleService's Core Data choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Console: Ticket OPS-48119: retire the legacy replay path for HinterlandCloudReconcilerFlow\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 HinterlandCloudReconcilerFlow 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":"Workspace: diff --git a/projects/hinterland/ui/settings/PrivacyPane.tsx b/projects/hinterland/ui/settings/PrivacyPane.tsx\nindex 62d71aa..90f3c1e 100644\n--- a/projects/hinterland/ui/settings/PrivacyPane.tsx\n+++ b/projects/hinterland/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\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Wire HinterlandBeaconStoreCoordinator'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":"HinterlandHarborIndexStore is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- avoid a schema migration in this release\n- retain the current React 19 operational envelope\n\nThe relevant code crosses search, Terraform, Flutter. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Repository: Could the reasoning behind HinterlandWillowCodecStore's Redis Streams choices be captured as an ADR for engineers joining the project next quarter? The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Assess the HinterlandCedarPolicyService diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"We need to move HinterlandAcornWidgetFlow from the legacy store to React 19. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Move HinterlandEchoRegistryStore'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":"Pipeline: // projects/hinterland/Sources/App/SessionStore.swift\nfinal class HinterlandHarborIndexFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandHarborIndexFlow 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":"HinterlandMapleQueueCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"PM is preparing the HinterlandCedarPolicyStore rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandCedarPolicyStore\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.\n\nThe server contract is the subject, but the requested output is documentation rather than handler code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Find HinterlandCraneWorkspaceService's duplicate retry source","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Gateway: diff --git a/projects/hinterland/ml/pipeline/features.py b/projects/hinterland/ml/pipeline/features.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/hinterland/ml/pipeline/features.py\n+++ b/projects/hinterland/ml/pipeline/features.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\nRead the artifact above as a skeptical reviewer. Is HinterlandRavenSessionFlow'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":"HinterlandVelaDrawerCoordinator: give it a nicer flow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"I inherited HinterlandRainfallDBStore and need a careful read of projects/hinterland/config/staging.toml before I can sign off on the next release. 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- avoid a schema migration in this release\n- stay compatible with the existing Redis Streams deployment\n- keep the work scoped to HinterlandRainfallDBStore and its direct tests\n\nSeveral teams work in this search, Terraform, Flutter 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":"HinterlandAtlasSearchService'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":"Split HinterlandAsterWebhookService without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Renderer: // projects/hinterland/db/migrations/20260730_events.sql\nfinal class HinterlandJuniperCLIFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandJuniperCLIFlow 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Since the last release, HinterlandOrbitSyncService has shown duplicate retries after a network handoff; nobody on the team can reproduce it reliably on a laptop. Reconstruct the failing timeline from logs and tests, identify which invariant first breaks, and distinguish causal signals from effects or cleanup noise.\n\nConstraints:\n- avoid a schema migration in this release\n- stay compatible with the existing Core Data deployment\n- keep the work scoped to HinterlandOrbitSyncService and its direct tests\n\nSeveral teams work in this search, Terraform, Flutter monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.84,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-48138\n\n08:02 deploy HinterlandBasilRunnerFlow 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 HinterlandBasilRunnerFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.65,"slice":"pasted-context","lang":"en"} -{"prompt":"Indexer: diff --git a/projects/hinterland/apps/console/routes/usage.svelte b/projects/hinterland/apps/console/routes/usage.svelte\nindex 62d71aa..90f3c1e 100644\n--- a/projects/hinterland/apps/console/routes/usage.svelte\n+++ b/projects/hinterland/apps/console/routes/usage.svelte\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 HinterlandCopperBridgeFlow'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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"HinterlandBasilRunnerCoordinator: check the suspicious part","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"vague-eval","lang":"en"} -{"prompt":"HinterlandOspreyJobCoordinator needs a paired pass: separate HinterlandOspreyJobCoordinator's policy from transport without behavior changes, plus give the existing implementation a read-only safety pass. Use projects/hinterland/internal/auth/refresh.go as the source of truth, preserve the Terraform contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.73,"slice":"mixed","lang":"en"} -{"prompt":"Release engineering needs a HinterlandDriftConsoleStore changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition. The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","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_48151'\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_48151'::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\nFind the source of this HinterlandAmberFilterCoordinator 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.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Sequence HinterlandOspreyJobStore's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"Investigate the HinterlandOspreyJobService hang","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Apparently: projects/hinterland/workers/thumbnail/consumer.ex の HinterlandMapleQueueService で、Playwright の flow に断続的な問題が起きています。 現在の flow を読み、ownership、cancel、順序が安全か評価してください。分析だけで十分です。\n\n制約:\n- Playwright を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は HinterlandMapleQueueService のみ","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"ja"} -{"prompt":"HinterlandAsterWebhookCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"HinterlandMarbleTokenCoordinator: handle the lingering thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"vague-eval","lang":"en"} -{"prompt":"Incident timeline — INC-48118\n\n08:02 deploy HinterlandAsterWebhookFlow 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 HinterlandAsterWebhookFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.65,"slice":"pasted-context","lang":"en"} -{"prompt":"Lately: Incident timeline — INC-48154\n\n08:02 deploy HinterlandCoralUploadCoordinator 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 HinterlandCoralUploadCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.67,"slice":"pasted-context","lang":"en"} -{"prompt":"HinterlandLumenChartCoordinator: the docs need something","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"vague-eval","lang":"en"} -{"prompt":"How does HinterlandEmberRelayStore propagate cancellation through the Terraform boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Oddly: Incident timeline — INC-48146\n\n08:02 deploy HinterlandMarbleTokenFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nDetermine why HinterlandMarbleTokenFlow 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.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Translate the HinterlandMoonlitSDKStore setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"boundary","lang":"en"} -{"prompt":"For HinterlandRavenSessionCoordinator, separate HinterlandRavenSessionCoordinator's policy from transport without behavior changes; once that is complete, capture the contract and rollback note for consumers. Work from projects/hinterland/cmd/exporter/main.py, stay with React 19, and avoid a schema migration in this release. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"HinterlandKiteSchedulerCoordinator: clean up that old path","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"vague-eval","lang":"en"} -{"prompt":"Currently: projects/hinterland/ui/settings/PrivacyPane.tsx 里的 HinterlandMapleQueueStore 最近在 Playwright 流程中出现间歇性问题。 请追踪 queue、scheduler 和取消路径，对比假设，先定位原因再提修改。\n\n约束：\n- 继续使用 Playwright\n- 保持兼容性和取消语义\n- 改动只限于 HinterlandMapleQueueStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"zh"} -{"prompt":"Today: // projects/hinterland/apps/console/routes/usage.svelte\nfinal class HinterlandQuartzPlayerCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandQuartzPlayerCoordinator; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Context: # projects/hinterland/Sources/CLI/Commands/Doctor.swift\n[worker.hinterlandsableparserflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandsableparserflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandsableparserflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandSableParserFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48126\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 HinterlandSableParserFlow'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.36,"slice":"pasted-context","lang":"en"} -{"prompt":"projects/hinterland/crates/index/src/segment.rs now contains HinterlandIrisBatchFlow'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.53,"slice":"boundary","lang":"en"} -{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current HinterlandAmberFilterService design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandAmberFilterService\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"The data is already available in projects/hinterland/lib/codec/frame.cc; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} -{"prompt":"Background: Incident timeline — INC-48122\n\n08:02 deploy HinterlandOpalRouterFlow 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 HinterlandOpalRouterFlow 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.62,"slice":"pasted-context","lang":"en"} -{"prompt":"How does HinterlandVelaDrawerStore propagate cancellation through the Redis Streams boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"I inherited HinterlandFrostPanelService and need a careful read of projects/hinterland/engine/render/atlas.cpp before I can sign off on the next release. 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- avoid a schema migration in this release\n- stay compatible with the existing Playwright deployment\n- keep the work scoped to HinterlandFrostPanelService and its direct tests\n\nSeveral teams work in this search, Terraform, Flutter monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Move HinterlandSpruceDaemonService'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.58,"slice":"core","lang":"en"} -{"prompt":"Could HinterlandCoralUploadStore show the active Terraform sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"HinterlandSpruceDaemonCoordinator: ship a sensible version","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"vague-eval","lang":"en"} -{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current HinterlandCopperBridgeStore design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandCopperBridgeStore\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"# projects/hinterland/ml/pipeline/features.py\n[worker.hinterlandledgergateflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandledgergateflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandledgergateflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandLedgerGateFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48111\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 HinterlandLedgerGateFlow'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.36,"slice":"pasted-context","lang":"en"} -{"prompt":"Read projects/hinterland/engine/render/atlas.cpp and tell me whether HinterlandBasilRunnerStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"UI ticket DES-48124: finish the compact HinterlandOspreyJobFlow filter experience\n\nRoute: /catalog/search\nSource: projects/hinterland/infra/modules/edge/main.tf\nFramework: Terraform\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring HinterlandOspreyJobFlow'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.78,"slice":"pasted-context","lang":"en"} -{"prompt":"HinterlandMosaicGridCoordinator: take care of the warning","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"vague-eval","lang":"en"} -{"prompt":"Compare the old and new HinterlandSpruceDaemonStore adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Center the HinterlandNovaPickerStore modal","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} +{"prompt":"Renderer: // projects/hinterland/db/migrations/20260730_events.sql\nfinal class HinterlandJuniperCLIFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandJuniperCLIFlow 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":"Since the last release, HinterlandOrbitSyncService has shown duplicate retries after a network handoff; nobody on the team can reproduce it reliably on a laptop. Reconstruct the failing timeline from logs and tests, identify which invariant first breaks, and distinguish causal signals from effects or cleanup noise.\n\nConstraints:\n- avoid a schema migration in this release\n- stay compatible with the existing Core Data deployment\n- keep the work scoped to HinterlandOrbitSyncService and its direct tests\n\nSeveral teams work in this search, Terraform, Flutter monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-48138\n\n08:02 deploy HinterlandBasilRunnerFlow 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 HinterlandBasilRunnerFlow, 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":"Indexer: diff --git a/projects/hinterland/apps/console/routes/usage.svelte b/projects/hinterland/apps/console/routes/usage.svelte\nindex 62d71aa..90f3c1e 100644\n--- a/projects/hinterland/apps/console/routes/usage.svelte\n+++ b/projects/hinterland/apps/console/routes/usage.svelte\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 HinterlandCopperBridgeFlow'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":"HinterlandBasilRunnerCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"HinterlandOspreyJobCoordinator needs a paired pass: separate HinterlandOspreyJobCoordinator's policy from transport without behavior changes, plus give the existing implementation a read-only safety pass. Use projects/hinterland/internal/auth/refresh.go as the source of truth, preserve the Terraform contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Release engineering needs a HinterlandDriftConsoleStore changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition. The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"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_48151'\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_48151'::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\nFind the source of this HinterlandAmberFilterCoordinator symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Sequence HinterlandOspreyJobStore's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate the HinterlandOspreyJobService hang","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Apparently: projects/hinterland/workers/thumbnail/consumer.ex の HinterlandMapleQueueService で、Playwright の flow に断続的な問題が起きています。 現在の flow を読み、ownership、cancel、順序が安全か評価してください。分析だけで十分です。\n\n制約:\n- Playwright を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は HinterlandMapleQueueService のみ","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"ja"} +{"prompt":"HinterlandAsterWebhookCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"HinterlandMarbleTokenCoordinator: handle the lingering thing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-48118\n\n08:02 deploy HinterlandAsterWebhookFlow 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 HinterlandAsterWebhookFlow 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":"Lately: Incident timeline — INC-48154\n\n08:02 deploy HinterlandCoralUploadCoordinator 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 HinterlandCoralUploadCoordinator 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":"HinterlandLumenChartCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"How does HinterlandEmberRelayStore propagate cancellation through the Terraform boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Oddly: Incident timeline — INC-48146\n\n08:02 deploy HinterlandMarbleTokenFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nDetermine why HinterlandMarbleTokenFlow 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":"Translate the HinterlandMoonlitSDKStore setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"For HinterlandRavenSessionCoordinator, separate HinterlandRavenSessionCoordinator's policy from transport without behavior changes; once that is complete, capture the contract and rollback note for consumers. Work from projects/hinterland/cmd/exporter/main.py, stay with React 19, and avoid a schema migration in this release. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"HinterlandKiteSchedulerCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Currently: projects/hinterland/ui/settings/PrivacyPane.tsx 里的 HinterlandMapleQueueStore 最近在 Playwright 流程中出现间歇性问题。 请追踪 queue、scheduler 和取消路径，对比假设，先定位原因再提修改。\n\n约束：\n- 继续使用 Playwright\n- 保持兼容性和取消语义\n- 改动只限于 HinterlandMapleQueueStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"Today: // projects/hinterland/apps/console/routes/usage.svelte\nfinal class HinterlandQuartzPlayerCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandQuartzPlayerCoordinator; 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":"Context: # projects/hinterland/Sources/CLI/Commands/Doctor.swift\n[worker.hinterlandsableparserflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandsableparserflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandsableparserflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandSableParserFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48126\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 HinterlandSableParserFlow'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":"projects/hinterland/crates/index/src/segment.rs now contains HinterlandIrisBatchFlow'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.4,"slice":"core","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current HinterlandAmberFilterService design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandAmberFilterService\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"The data is already available in projects/hinterland/lib/codec/frame.cc; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Background: Incident timeline — INC-48122\n\n08:02 deploy HinterlandOpalRouterFlow 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 HinterlandOpalRouterFlow 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":"How does HinterlandVelaDrawerStore propagate cancellation through the Redis Streams boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"I inherited HinterlandFrostPanelService and need a careful read of projects/hinterland/engine/render/atlas.cpp before I can sign off on the next release. 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- avoid a schema migration in this release\n- stay compatible with the existing Playwright deployment\n- keep the work scoped to HinterlandFrostPanelService and its direct tests\n\nSeveral teams work in this search, Terraform, Flutter 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":"Move HinterlandSpruceDaemonService'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.5,"slice":"core","lang":"en"} +{"prompt":"Could HinterlandCoralUploadStore show the active Terraform 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":"HinterlandSpruceDaemonCoordinator: ship a sensible version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current HinterlandCopperBridgeStore design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandCopperBridgeStore\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"# projects/hinterland/ml/pipeline/features.py\n[worker.hinterlandledgergateflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandledgergateflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandledgergateflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandLedgerGateFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48111\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 HinterlandLedgerGateFlow'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":"Read projects/hinterland/engine/render/atlas.cpp and tell me whether HinterlandBasilRunnerStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-48124: finish the compact HinterlandOspreyJobFlow filter experience\n\nRoute: /catalog/search\nSource: projects/hinterland/infra/modules/edge/main.tf\nFramework: Terraform\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring HinterlandOspreyJobFlow'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":"HinterlandMosaicGridCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Compare the old and new HinterlandSpruceDaemonStore 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":"Center the HinterlandNovaPickerStore modal","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"For HinterlandGarnetModalCoordinator, separate HinterlandGarnetModalCoordinator's policy from transport without behavior changes; once that is complete, capture the contract and rollback note for consumers. Work from projects/hinterland/lib/codec/frame.cc, stay with Playwright, and avoid a schema migration in this release. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"HinterlandCopperBridgeCoordinator: sequence, then restructure","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.77,"slice":"mixed","lang":"en"} -{"prompt":"Two deliverables are holding up HinterlandJuniperCLICoordinator. First, finish HinterlandJuniperCLICoordinator's responsive empty and retry states. In the same workstream, correct the known stale timeout beside it. The relevant starting point is projects/hinterland/src/sync/reconcile.ts, which follows Core Data conventions and currently suffers from duplicate retries after a network handoff. Avoid a schema migration in this release.\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.75,"slice":"mixed","lang":"en"} -{"prompt":"# CI job 48121: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: React 19\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] HinterlandTideWorkerFlowIntegration.replays_after_timeout ... ok\n[test] HinterlandTideWorkerFlowIntegration.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 \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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Add the bounded HinterlandTideWorkerFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.83,"slice":"pasted-context","lang":"de"} -{"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_48137'\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_48137'::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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Determine why HinterlandSpruceDaemonFlow 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.92,"slice":"pasted-context","lang":"pt"} -{"prompt":"Collapse the HinterlandOpalRouterService wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Describe HinterlandOpalRouterStore's error envelope","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"en"} -{"prompt":"Fresh release brief for HinterlandFernSnapshotCoordinator:\n- primary outcome: finish HinterlandFernSnapshotCoordinator's responsive empty and retry states\n- companion outcome: give the existing implementation a read-only safety pass\n- repository entry point: projects/hinterland/crates/index/src/segment.rs\n- platform constraint: Redis Streams\n- known complication: an accessibility label that reads the internal enum\n\nBoth results are required, but they should remain independently reviewable. Avoid a schema migration in this release; 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":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"A copied hex color in HinterlandWrenExportFlow lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"boundary","lang":"en"} -{"prompt":"HinterlandAcornWidgetService needs a production server path for replaying tenant events; the public envelope is agreed but persistence and retry handling are not wired. Add signed cursor parsing, bounded pagination, key rotation, tenant checks, and a resumable background path with metrics for lag, retries, and terminal failures.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- avoid a schema migration in this release\n- retain the current React 19 operational envelope\n\nThe relevant code crosses search, Terraform, Flutter. Prefer evidence from the repository and make any assumption explicit.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Ticket OPS-48144: retire the legacy replay path for HinterlandKiteSchedulerFlow\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 HinterlandKiteSchedulerFlow 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.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Does HinterlandBasilRunnerService enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"The minimum supported Terraform version in projects/hinterland/infra/modules/edge/main.tf is one patch behind the lockfile. Align that single value and regenerate only the affected metadata.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"boundary","lang":"en"} -{"prompt":"Flip HinterlandTideWorkerService's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"core","lang":"en"} -{"prompt":"A copied hex color in HinterlandEmberRelayService lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"core","lang":"en"} -{"prompt":"Cadre la migration de HinterlandCloudReconcilerService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"fr"} -{"prompt":"Ticket OPS-48129: retire the legacy replay path for HinterlandMoonlitSDKFlow\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À partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. From this evidence, draft consumer-facing migration guidance for HinterlandMoonlitSDKFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.67,"slice":"pasted-context","lang":"fr"} -{"prompt":"HinterlandAtlasSearchCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"vague-eval","lang":"en"} -{"prompt":"Test Suite 'HinterlandWrenExportCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[HinterlandWrenExportCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/hinterland/packages/api/openapi.yaml:144: error: -[HinterlandWrenExportCoordinatorTests 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 '-[HinterlandWrenExportCoordinatorTests 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\nFinish the visible HinterlandWrenExportCoordinator 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.68,"slice":"pasted-context","lang":"en"} -{"prompt":"Question: The next client release depends on a new HinterlandSlateEditorStore capability in projects/hinterland/services/ledger/replay.go, with Terraform already chosen by the platform group. Wire the schema, repository, handler, and worker so duplicate deliveries return the original result and shutdown never acknowledges uncommitted work.\n\nConstraints:\n- avoid a schema migration in this release\n- stay compatible with the existing Terraform deployment\n- keep the work scoped to HinterlandSlateEditorStore and its direct tests\n\nSeveral teams work in this search, Terraform, Flutter monorepo, so keep ownership and handoff points understandable in a small review.\n\nThe contract notes are context; the requested outcome is the working server path.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.83,"slice":"boundary","lang":"en"} -{"prompt":"HinterlandEmberRelayCoordinator: make the api less awkward","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"vague-eval","lang":"en"} -{"prompt":"This should remain a deliberately small patch: HinterlandJuniperCLIStore has one known configuration mistake in projects/hinterland/src/sync/reconcile.ts, not an open-ended failure investigation. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- avoid a schema migration in this release\n- stay compatible with the existing Core Data deployment\n- keep the work scoped to HinterlandJuniperCLIStore and its direct tests\n\nSeveral teams work in this search, Terraform, Flutter monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"Collapse the HinterlandNimbusFormService wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Release engineering needs a HinterlandAcornWidgetStore changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"Move HinterlandBeaconStoreFlow'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":"boundary","lang":"en"} -{"prompt":"Observation: Move HinterlandTideWorkerStore behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Two asks around HinterlandFlintTimelineCoordinator: (1) assess ownership and failure handling in projects/hinterland/src/sync/reconcile.ts; (2) capture the contract and rollback note for consumers. Avoid a schema migration in this release, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"Constraint: // projects/hinterland/db/migrations/20260730_events.sql\nfinal class HinterlandOrbitSyncCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nDeliver the HinterlandOrbitSyncCoordinator 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.86,"slice":"pasted-context","lang":"en"} -{"prompt":"HinterlandCloudReconcilerCoordinator: sequence, then ship","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.82,"slice":"mixed","lang":"en"} -{"prompt":"HinterlandOpalRouterCoordinator: ship, then correct","purpose":"backendImpl","secondary":"quickFix","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Remove HinterlandGarnetModalStore's stray comma","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"boundary","lang":"en"} -{"prompt":"Request: # projects/hinterland/Sources/App/SessionStore.swift\n[worker.hinterlandacornwidgetcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandacornwidgetcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandacornwidgetcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandAcornWidgetCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48156\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 HinterlandAcornWidgetCoordinator'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.36,"slice":"pasted-context","lang":"en"} -{"prompt":"Split projects/hinterland/apps/console/routes/usage.svelte by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Vereinheitliche die HinterlandCloudReconcilerStore-Validatoren","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"de"} -{"prompt":"# projects/hinterland/engine/render/atlas.cpp\n[worker.hinterlandgarnetmodalflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandgarnetmodalflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandgarnetmodalflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandGarnetModalFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48128\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/hinterland/engine/render/atlas.cpp and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.41,"slice":"pasted-context","lang":"en"} -{"prompt":"HinterlandNimbusFormCoordinator needs a paired pass: separate HinterlandNimbusFormCoordinator's policy from transport without behavior changes, plus give the existing implementation a read-only safety pass. Use projects/hinterland/crates/index/src/segment.rs as the source of truth, preserve the Redis Streams contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.63,"slice":"mixed","lang":"en"} -{"prompt":"$ pnpm test --filter HinterlandSummitProxyFlow\n RUN v3.2.4 /workspace/apps/console\n × HinterlandSummitProxyFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=48147 phase=resume storedCursor=seg-0183\n session=48147 phase=fetch requestCursor=seg-0183 pageSize=200\n session=48147 phase=commit receivedCursor=seg-0184 itemCount=0\n session=48147 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nReconstruct the HinterlandSummitProxyFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.92,"slice":"pasted-context","lang":"en"} -{"prompt":"Find HinterlandSableParserStore's duplicate retry source","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"boundary","lang":"en"} -{"prompt":"HinterlandSummitProxyCoordinator: could this be clearer","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"vague-eval","lang":"en"} -{"prompt":"Fresh release brief for HinterlandPineMetricsCoordinator:\n- primary outcome: produce a consumer guide for HinterlandPineMetricsCoordinator\n- companion outcome: give the existing implementation a read-only safety pass\n- repository entry point: projects/hinterland/workers/thumbnail/consumer.ex\n- platform constraint: Playwright\n- known complication: a query plan that changes after statistics refresh\n\nBoth results are required, but they should remain independently reviewable. Avoid a schema migration in this release; 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":"writing","secondary":"review","mixed":true,"difficulty":0.67,"slice":"mixed","lang":"en"} -{"prompt":"Please turn HinterlandAmberFilterStore'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.35,"slice":"core","lang":"en"} -{"prompt":"The data is already available in projects/hinterland/infra/modules/edge/main.tf; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Polish the HinterlandNovaPickerService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} -{"prompt":"Lay out a two-milestone strategy for eliminating a misleading timeout name used in five packages in HinterlandOrbitSyncFlow, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Goal: Ticket OPS-48149: retire the legacy replay path for HinterlandAtlasSearchFlow\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 HinterlandAtlasSearchFlow 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.67,"slice":"pasted-context","lang":"en"} -{"prompt":"HinterlandHarborIndexCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.45,"slice":"mixed","lang":"en"} -{"prompt":"Symptom: The name pendingAck means two different things across HinterlandFrostPanelFlow's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Where did HinterlandCraneWorkspaceStore's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current HinterlandQuartzPlayerService design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandQuartzPlayerService\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Persist HinterlandAtlasSearchStore delivery attempts in projects/hinterland/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.67,"slice":"boundary","lang":"en"} -{"prompt":"// projects/hinterland/crates/index/src/segment.rs\nfinal class HinterlandCraneWorkspaceFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandCraneWorkspaceFlow'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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Polish the HinterlandRavenSessionService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"Headsup: A flaky failure around HinterlandCoralUploadService survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandCoralUploadService\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.89,"slice":"core","lang":"en"} -{"prompt":"FYI: // projects/hinterland/internal/auth/refresh.go\nfinal class HinterlandCinderAuthFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandCinderAuthFlow 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.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Meanwhile: A copied hex color in HinterlandVelaDrawerService lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"core","lang":"en"} -{"prompt":"HinterlandRainfallDBService flakes under UTC","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Describe HinterlandHarborIndexService's error envelope","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"HinterlandCinderAuthService's staging timeout is already known to be wrong: change the single projects/hinterland/internal/auth/refresh.go value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"core","lang":"en"} -{"prompt":"Move HinterlandSlateEditorFlow'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.63,"slice":"boundary","lang":"en"} -{"prompt":"2026-07-30T08:14:11.409Z level=info service=hinterlandmosaicgridflow pod=hinterlandmosaicgridflow-7cf8 request_id=48148 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=hinterlandmosaicgridflow request_id=48148 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=hinterlandmosaicgridflow request_id=48148 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=hinterlandmosaicgridflow request_id=48148 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=hinterlandmosaicgridflow request_id=48148 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=hinterlandmosaicgridflow request_id=48148 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=hinterlandmosaicgridflow request_id=48148 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=hinterlandmosaicgridflow request_id=48148 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nFind the source of this HinterlandMosaicGridFlow 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.95,"slice":"pasted-context","lang":"en"} -{"prompt":"How should HinterlandPrismCacheStore be decomposed?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"HinterlandCraneWorkspaceCoordinator: sequence, then restructure","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Locally: # projects/hinterland/internal/auth/refresh.go\n[worker.hinterlandcedarpolicyflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandcedarpolicyflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandcedarpolicyflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandCedarPolicyFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48114\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 HinterlandCedarPolicyFlow'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.43,"slice":"pasted-context","lang":"en"} -{"prompt":"Read projects/hinterland/internal/auth/refresh.go and tell me whether HinterlandKiteSchedulerStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"HinterlandTideWorkerCoordinator: sequence, then polish","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.74,"slice":"mixed","lang":"en"} -{"prompt":"Incident timeline — INC-48110\n\n08:02 deploy HinterlandFernSnapshotFlow 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 HinterlandFernSnapshotFlow 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.57,"slice":"pasted-context","lang":"en"} -{"prompt":"Test Suite 'HinterlandMapleQueueFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[HinterlandMapleQueueFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/hinterland/workers/thumbnail/consumer.ex:144: error: -[HinterlandMapleQueueFlowTests 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 '-[HinterlandMapleQueueFlowTests 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\nFinish the visible HinterlandMapleQueueFlow 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.76,"slice":"pasted-context","lang":"en"} -{"prompt":"One contained cleanup in projects/hinterland/cmd/exporter/main.py: remove the obsolete HinterlandEchoRegistryService import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"core","lang":"en"} -{"prompt":"What is the safest way to split projects/hinterland/app/src/main/SyncWorker.kt into independently owned modules while HinterlandSummitProxyService's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Test Suite 'HinterlandEchoRegistryFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[HinterlandEchoRegistryFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/hinterland/cmd/exporter/main.py:144: error: -[HinterlandEchoRegistryFlowTests 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 '-[HinterlandEchoRegistryFlowTests 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 HinterlandEchoRegistryFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"The HinterlandCinderAuthStore 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.19,"slice":"boundary","lang":"en"} -{"prompt":"Could HinterlandMosaicGridService show the active Playwright sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} -{"prompt":"Is there a cleaner way to separate HinterlandBeaconStoreStore'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":"En projects/hinterland/cmd/exporter/main.py, HinterlandLedgerGateStore tiene un problema intermitente en el flujo de React 19. Separa responsabilidades y elimina duplicación, conservando API, wire values, orden y comportamiento observable.\n\nRestricciones:\n- seguir con React 19\n- conservar compatibilidad y cancelación\n- limitar el cambio a HinterlandLedgerGateStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con React 19 alrededor de HinterlandLedgerGateStore.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"es"} -{"prompt":"Three teams extended HinterlandPineMetricsStore independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- avoid a schema migration in this release\n- retain the current Playwright operational envelope\n\nThe relevant code crosses search, Terraform, Flutter. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.77,"slice":"boundary","lang":"en"} -{"prompt":"HinterlandCedarPolicyCoordinator is blocking the next release because two validators with subtly different error strings. I need two concrete outcomes from a single pass: lay out a staged migration for HinterlandCedarPolicyCoordinator, and consolidate the duplicated normalization paths without changing behavior. Use the existing Terraform conventions in projects/hinterland/infra/modules/edge/main.tf; avoid a schema migration in this release. 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.96,"slice":"mixed","lang":"en"} -{"prompt":"Two deliverables are holding up HinterlandRainfallDBCoordinator. First, produce a consumer guide for HinterlandRainfallDBCoordinator. In the same workstream, correct the known stale timeout beside it. The relevant starting point is projects/hinterland/config/staging.toml, which follows Redis Streams conventions and currently suffers from memory growth during hour-long imports. Avoid a schema migration in this release.\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":"writing","secondary":"quickFix","mixed":true,"difficulty":0.59,"slice":"mixed","lang":"en"} -{"prompt":"Em projects/hinterland/config/staging.toml, o HinterlandLumenChartStore tem um problema intermitente no fluxo de Redis Streams. Siga queue, scheduler e cancelamento, compare hipóteses e encontre a causa antes de mudar código.\n\nRestrições:\n- continuar com Redis Streams\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao HinterlandLumenChartStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"pt"} -{"prompt":"Two asks around HinterlandMoonlitSDKCoordinator: (1) assess ownership and failure handling in projects/hinterland/services/ledger/replay.go; (2) capture the contract and rollback note for consumers. Avoid a schema migration in this release, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Drop HinterlandMicaProfileStore's unused import","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"boundary","lang":"en"} -{"prompt":"Incident timeline — INC-48130\n\n08:02 deploy HinterlandNimbusFormFlow 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 HinterlandNimbusFormFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"pasted-context","lang":"en"} -{"prompt":"HinterlandDriftConsoleCoordinator: sort out the rough edge","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"vague-eval","lang":"en"} -{"prompt":"Production: // projects/hinterland/packages/api/openapi.yaml\nfinal class HinterlandRainfallDBFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandRainfallDBFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"pasted-context","lang":"en"} -{"prompt":"Staging: # projects/hinterland/lib/codec/frame.cc\n[worker.hinterlandfrostpanelcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandfrostpanelcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandfrostpanelcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandFrostPanelCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48158\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/hinterland/lib/codec/frame.cc and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.41,"slice":"pasted-context","lang":"en"} -{"prompt":"HinterlandFernSnapshotStore is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- avoid a schema migration in this release\n- retain the current Redis Streams operational envelope\n\nThe relevant code crosses search, Terraform, Flutter. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"// projects/hinterland/config/staging.toml\nfinal class HinterlandVelaDrawerFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Walk through what the artifact proves about HinterlandVelaDrawerFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"pasted-context","lang":"zh"} -{"prompt":"HinterlandDeltaCanvasCoordinator needs a paired pass: change HinterlandDeltaCanvasCoordinator's known staging timeout from 15 to 30 seconds, plus give the existing implementation a read-only safety pass. Use projects/hinterland/apps/console/routes/usage.svelte as the source of truth, preserve the Core Data contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.24,"slice":"mixed","lang":"en"} -{"prompt":"CI: The behavior of HinterlandJuniperCLIService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/hinterland/db/migrations/20260730_events.sql. 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- touch generated artifacts only through their checked-in generator\n- avoid a schema migration in this release\n- retain the current Core Data operational envelope\n\nThe relevant code crosses search, Terraform, Flutter. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"PM needs a concise migration note for HinterlandOrbitSyncStore, including the user impact, rollback trigger, and the one configuration key operators must change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current HinterlandFrostPanelStore design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandFrostPanelStore\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"boundary","lang":"en"} -{"prompt":"Documente o contrato de HinterlandDeltaCanvasService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"pt"} -{"prompt":"The name pendingAck means two different things across HinterlandMarbleTokenStore's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Atlas: projects/hinterland/cmd/exporter/main.py の HinterlandAmberFilterFlow で、React 19 の flow に断続的な問題が起きています。 queue、scheduler、cancel 経路を追い、仮説を比較して、変更前に原因を特定してください。\n\n制約:\n- React 19 を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は HinterlandAmberFilterFlow のみ","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"boundary","lang":"ja"} -{"prompt":"In projects/hinterland/ml/pipeline/features.py hat HinterlandLedgerGateService ein sporadisches Problem im React 19-Ablauf. Verfolge Queue, Scheduler und Abbruch, vergleiche Hypothesen und finde die Ursache vor jeder Änderung.\n\nRandbedingungen:\n- React 19 weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf HinterlandLedgerGateService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um HinterlandLedgerGateService mit React 19 kompatibel.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"de"} -{"prompt":"Beacon: Incident timeline — INC-48150\n\n08:02 deploy HinterlandIrisBatchCoordinator 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 HinterlandIrisBatchCoordinator rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Split projects/isotope/ml/pipeline/features.py by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"UI ticket DES-49139: finish the compact IsotopeHarborIndexFlow filter experience\n\nRoute: /catalog/search\nSource: projects/isotope/ui/settings/PrivacyPane.tsx\nFramework: Tokio\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nFinish the visible IsotopeHarborIndexFlow state described above: responsive layout, correct selection restoration, keyboard focus, accessible labels, dark mode, and reduced-motion behavior.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"IsotopeSummitProxyCoordinator: restructure, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.63,"slice":"mixed","lang":"en"} -{"prompt":"Center the IsotopeAmberFilterService modal","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Walk through IsotopeIrisBatchStore's SyncWorker.kt","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"diff --git a/projects/isotope/Sources/App/SessionStore.swift b/projects/isotope/Sources/App/SessionStore.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/Sources/App/SessionStore.swift\n+++ b/projects/isotope/Sources/App/SessionStore.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure IsotopeCloudReconcilerFlow so duplicated normalization and shutdown ownership have one home. Preserve public behavior, wire values, logging fields, and ordering; extend characterization coverage first.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Wire a IsotopeFlintTimelineFlow background task in projects/isotope/services/ledger/replay.go that expires abandoned sessions, records an OpenTelemetry span, and yields cleanly when shutdown begins.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"Production says IsotopeFlintTimelineService is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current PostgreSQL 17 operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Cinder: The IsotopeLedgerGateService feature flag default should be false in test, exactly like production; correct that config entry and nothing else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"core","lang":"en"} -{"prompt":"IsotopeSableParserCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"vague-eval","lang":"en"} -{"prompt":"Teach IsotopeOpalRouterStore to verify signed continuation tokens, reject cross-tenant cursors, and rotate keys without invalidating tokens issued during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"// projects/isotope/crates/index/src/segment.rs\nfinal class IsotopeBeaconStoreFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nWalk through what the artifact proves about IsotopeBeaconStoreFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Could IsotopeNovaPickerService show the active NATS JetStream sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"IsotopeKiteSchedulerCoordinator: correct, then assess","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.24,"slice":"mixed","lang":"en"} -{"prompt":"Delta: projects/isotope/packages/api/openapi.yaml の IsotopeGarnetModalFlow で、NATS JetStream の flow に断続的な問題が起きています。 責務を分離して重複をなくし、API、wire value、順序、観測可能な動作は変えないでください。\n\n制約:\n- NATS JetStream を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は IsotopeGarnetModalFlow のみ","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"ja"} -{"prompt":"Ember: Incident timeline — INC-49124\n\n08:02 deploy IsotopeAmberFilterFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nDetermine why IsotopeAmberFilterFlow produces this result. Trace ordering, cancellation, shared state, and scheduler behavior; identify the root cause before suggesting a patch.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"diff --git a/projects/isotope/Sources/CLI/Commands/Doctor.swift b/projects/isotope/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/isotope/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit IsotopeSlateEditorFlow by responsibility and make cancellation ownership explicit. Characterize the current sequence before moving code and keep callers unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"PM needs a concise migration note for IsotopeCloudReconcilerStore, including the user impact, rollback trigger, and the one configuration key operators must change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"en"} -{"prompt":"IsotopeWrenExportCoordinator needs a paired pass: produce a consumer guide for IsotopeWrenExportCoordinator, plus give the existing implementation a read-only safety pass. Use projects/isotope/db/migrations/20260730_events.sql as the source of truth, preserve the SQLite contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.51,"slice":"mixed","lang":"en"} -{"prompt":"Frost: The first IsotopeBirchMigratorFlow request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","lang":"en"} -{"prompt":"Garnet: Two asks around IsotopeAmberFilterCoordinator: (1) separate IsotopeAmberFilterCoordinator's policy from transport without behavior changes; (2) capture the contract and rollback note for consumers. Keep the patch readable for a small on-call review, and leave a clear boundary between the resulting artifacts or edits.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.73,"slice":"mixed","lang":"en"} -{"prompt":"A previously stable test around IsotopeDeltaCanvasFlow now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"IsotopeMosaicGridCoordinator: polish, then assess","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.56,"slice":"mixed","lang":"en"} -{"prompt":"Harbor: Two asks around IsotopeFernSnapshotCoordinator: (1) assess ownership and failure handling in projects/isotope/apps/console/routes/usage.svelte; (2) capture the contract and rollback note for consumers. Keep the patch readable for a small on-call review, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Ticket OPS-49148: retire the legacy replay path for IsotopePrismCacheFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nTurn the material above into a concise IsotopePrismCacheFlow release note and operator runbook section. State impact, detection, rollback, and the client-visible contract; do not modify code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.65,"slice":"pasted-context","lang":"en"} -{"prompt":"Split IsotopeOrbitSyncService without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Clarify IsotopeMapleQueueService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"Compare IsotopeMosaicGridStore's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"Translate the IsotopeEchoRegistryService setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"The minimum supported WebGPU version in projects/isotope/Sources/App/SessionStore.swift is one patch behind the lockfile. Align that single value and regenerate only the affected metadata.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"boundary","lang":"en"} -{"prompt":"Fresh release brief for IsotopeDriftConsoleCoordinator:\n- primary outcome: find the unknown cause of stale cursors when a page is resumed\n- companion outcome: correct the known stale timeout beside it\n- repository entry point: projects/isotope/services/ledger/replay.go\n- platform constraint: PostgreSQL 17\n- known complication: stale cursors when a page is resumed\n\nBoth results are required, but they should remain independently reviewable. Keep the patch readable for a small on-call review; retain serialization and authorization boundaries; cover cancellation, idempotent retries, and rollback; and avoid drive-by cleanup. Use the code as the source of truth, call out assumptions, and state how an on-call engineer can tell that either part is unsafe to ship.","purpose":"debugging","secondary":"quickFix","mixed":true,"difficulty":0.89,"slice":"mixed","lang":"en"} -{"prompt":"UI ticket DES-49159: finish the compact IsotopeBirchMigratorCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/isotope/ui/settings/PrivacyPane.tsx\nFramework: Tokio\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring IsotopeBirchMigratorCoordinator's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"IsotopeRavenSessionStore has four wrappers that only translate the same error enum. Collapse them into one adapter and preserve every public case, message, and metric label.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Two engineers disagree about whether IsotopeCinderAuthFlow's cache is authoritative. Walk the reads and writes in projects/isotope/cmd/exporter/main.py and settle that question from the code. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Iris: Split projects/isotope/config/staging.toml by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Juniper: The public surface of IsotopeMapleQueueStore is frozen, but its internal ownership in projects/isotope/crates/index/src/segment.rs is difficult to test and even harder to change safely. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeMapleQueueStore\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"Two asks around IsotopeQuartzPlayerCoordinator: (1) lay out a staged migration for IsotopeQuartzPlayerCoordinator; (2) then implement the bounded durable-cursor handler. Keep the patch readable for a small on-call review, and leave a clear boundary between the resulting artifacts or edits.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Does IsotopeCopperBridgeStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists? Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"We need to move IsotopeTideWorkerService from the legacy store to Tokio. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Responsive layout for IsotopeAcornWidgetStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"boundary","lang":"en"} -{"prompt":"IsotopeLedgerGateCoordinator: make this less weird","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"IsotopeSpruceDaemonCoordinator is blocking the next release because duplicate retries after a network handoff. I need two concrete outcomes from a single pass: find the unknown cause of duplicate retries after a network handoff, and capture the contract and rollback note for consumers. Use the existing PostgreSQL 17 conventions in projects/isotope/internal/auth/refresh.go; keep the patch readable for a small on-call review. Keep the outcomes distinct so reviewers can see which evidence supports the assessment and which files or prose satisfy the requested change.\n\nConstraints:\n- preserve public wire values and tenant boundaries\n- cover cancellation and retry behavior\n- avoid generated code and unrelated cleanup\n- include a rollback trigger that an on-call engineer can measure\n\nThis is a fresh workstream for the release, so derive everything from the repository and the context here.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.89,"slice":"mixed","lang":"en"} -{"prompt":"Incident timeline — INC-49113\n\n08:02 deploy IsotopeWillowCodecFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. From this evidence, draft consumer-facing migration guidance for IsotopeWillowCodecFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.65,"slice":"pasted-context","lang":"es"} -{"prompt":"IsotopeCraneWorkspaceCoordinator: untangle the messy bit","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"vague-eval","lang":"en"} -{"prompt":"Add a bounded IsotopeCloudReconcilerService export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Add a bounded IsotopePineMetricsService export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Compare IsotopeIrisBatchService's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Test Suite 'IsotopeWrenExportFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[IsotopeWrenExportFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/isotope/src/sync/reconcile.ts:144: error: -[IsotopeWrenExportFlowTests testRestoresSelectionAfterBackgrounding] : XCTAssertEqual failed: (\"Optional(4)\") is not equal to (\"Optional(3)\")\nAccessibility hierarchy at failure:\n Application, 0x104c, pid: 812\n Window, identifier: \"main\"\n NavigationStack, identifier: \"catalog\"\n Button, label: \"Filters\", value: \"2 active\"\n CollectionView, identifier: \"results-grid\", rows: 24\n Sheet, identifier: \"filter-sheet\"\n TextField, label: \"Search filters\", value: \"\"\n Switch, label: \"Available offline\", value: \"1\"\n Button, label: \"Apply\", enabled: true\nTest Case '-[IsotopeWrenExportFlowTests testRestoresSelectionAfterBackgrounding]' failed (4.812 seconds).\n\nSimulator: iPhone 17 Pro, iOS 27.0, en_US, content size XXXL, Reduce Motion enabled. The screenshot looks correct. The mismatch is the internal selected-segment index after the scene becomes active; tapping Apply a second time makes it three again.\n\nUse the UI evidence to complete IsotopeWrenExportFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.76,"slice":"pasted-context","lang":"en"} -{"prompt":"The IsotopeCedarPolicyStore surface in projects/isotope/cmd/exporter/main.py is stable now; turn its edge cases into API documentation with one successful example and one cancellation example.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"en"} -{"prompt":"Cadre la migration de IsotopeMarbleTokenService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"fr"} -{"prompt":"Test Suite 'IsotopeAtlasSearchFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[IsotopeAtlasSearchFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/isotope/Sources/App/SessionStore.swift:144: error: -[IsotopeAtlasSearchFlowTests testRestoresSelectionAfterBackgrounding] : XCTAssertEqual failed: (\"Optional(4)\") is not equal to (\"Optional(3)\")\nAccessibility hierarchy at failure:\n Application, 0x104c, pid: 812\n Window, identifier: \"main\"\n NavigationStack, identifier: \"catalog\"\n Button, label: \"Filters\", value: \"2 active\"\n CollectionView, identifier: \"results-grid\", rows: 24\n Sheet, identifier: \"filter-sheet\"\n TextField, label: \"Search filters\", value: \"\"\n Switch, label: \"Available offline\", value: \"1\"\n Button, label: \"Apply\", enabled: true\nTest Case '-[IsotopeAtlasSearchFlowTests testRestoresSelectionAfterBackgrounding]' failed (4.812 seconds).\n\nSimulator: iPhone 17 Pro, iOS 27.0, en_US, content size XXXL, Reduce Motion enabled. The screenshot looks correct. The mismatch is the internal selected-segment index after the scene becomes active; tapping Apply a second time makes it three again.\n\nUse the UI evidence to complete IsotopeAtlasSearchFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"pasted-context","lang":"en"} -{"prompt":"Release verification found a single stale IsotopeDriftConsoleStore value; the cause, desired value, and affected assertion are already agreed. Change the staging timeout from 15 seconds to 30, adjust the adjacent assertion that encodes that value, and avoid unrelated formatting, renames, dependency bumps, or cleanup.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current PostgreSQL 17 operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.25,"slice":"boundary","lang":"en"} +{"prompt":"HinterlandCopperBridgeCoordinator: sequence, then restructure","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Two deliverables are holding up HinterlandJuniperCLICoordinator. First, finish HinterlandJuniperCLICoordinator's responsive empty and retry states. In the same workstream, correct the known stale timeout beside it. The relevant starting point is projects/hinterland/src/sync/reconcile.ts, which follows Core Data conventions and currently suffers from duplicate retries after a network handoff. Avoid a schema migration in this release.\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":"# CI job 48121: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: React 19\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] HinterlandTideWorkerFlowIntegration.replays_after_timeout ... ok\n[test] HinterlandTideWorkerFlowIntegration.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 \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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Add the bounded HinterlandTideWorkerFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","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_48137'\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_48137'::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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Determine why HinterlandSpruceDaemonFlow 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":"Collapse the HinterlandOpalRouterService wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Describe HinterlandOpalRouterStore's error envelope","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Fresh release brief for HinterlandFernSnapshotCoordinator:\n- primary outcome: finish HinterlandFernSnapshotCoordinator's responsive empty and retry states\n- companion outcome: give the existing implementation a read-only safety pass\n- repository entry point: projects/hinterland/crates/index/src/segment.rs\n- platform constraint: Redis Streams\n- known complication: an accessibility label that reads the internal enum\n\nBoth results are required, but they should remain independently reviewable. Avoid a schema migration in this release; 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":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"A copied hex color in HinterlandWrenExportFlow lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"HinterlandAcornWidgetService needs a production server path for replaying tenant events; the public envelope is agreed but persistence and retry handling are not wired. Add signed cursor parsing, bounded pagination, key rotation, tenant checks, and a resumable background path with metrics for lag, retries, and terminal failures.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- avoid a schema migration in this release\n- retain the current React 19 operational envelope\n\nThe relevant code crosses search, Terraform, Flutter. Prefer evidence from the repository and make any assumption explicit.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-48144: retire the legacy replay path for HinterlandKiteSchedulerFlow\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 HinterlandKiteSchedulerFlow 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":"Does HinterlandBasilRunnerService enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"The minimum supported Terraform version in projects/hinterland/infra/modules/edge/main.tf 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":"Flip HinterlandTideWorkerService's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"A copied hex color in HinterlandEmberRelayService lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Cadre la migration de HinterlandCloudReconcilerService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"fr"} +{"prompt":"Ticket OPS-48129: retire the legacy replay path for HinterlandMoonlitSDKFlow\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À partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. From this evidence, draft consumer-facing migration guidance for HinterlandMoonlitSDKFlow, 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":"HinterlandAtlasSearchCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Test Suite 'HinterlandWrenExportCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[HinterlandWrenExportCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/hinterland/packages/api/openapi.yaml:144: error: -[HinterlandWrenExportCoordinatorTests 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 '-[HinterlandWrenExportCoordinatorTests 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\nFinish the visible HinterlandWrenExportCoordinator 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":"Question: The next client release depends on a new HinterlandSlateEditorStore capability in projects/hinterland/services/ledger/replay.go, with Terraform already chosen by the platform group. Wire the schema, repository, handler, and worker so duplicate deliveries return the original result and shutdown never acknowledges uncommitted work.\n\nConstraints:\n- avoid a schema migration in this release\n- stay compatible with the existing Terraform deployment\n- keep the work scoped to HinterlandSlateEditorStore and its direct tests\n\nSeveral teams work in this search, Terraform, Flutter monorepo, so keep ownership and handoff points understandable in a small review.\n\nThe contract notes are context; the requested outcome is the working server path.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"HinterlandEmberRelayCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"This should remain a deliberately small patch: HinterlandJuniperCLIStore has one known configuration mistake in projects/hinterland/src/sync/reconcile.ts, not an open-ended failure investigation. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- avoid a schema migration in this release\n- stay compatible with the existing Core Data deployment\n- keep the work scoped to HinterlandJuniperCLIStore and its direct tests\n\nSeveral teams work in this search, Terraform, Flutter monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Collapse the HinterlandNimbusFormService wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Release engineering needs a HinterlandAcornWidgetStore 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 HinterlandBeaconStoreFlow'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.5,"slice":"core","lang":"en"} +{"prompt":"Observation: Move HinterlandTideWorkerStore behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Two asks around HinterlandFlintTimelineCoordinator: (1) assess ownership and failure handling in projects/hinterland/src/sync/reconcile.ts; (2) capture the contract and rollback note for consumers. Avoid a schema migration in this release, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Constraint: // projects/hinterland/db/migrations/20260730_events.sql\nfinal class HinterlandOrbitSyncCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nDeliver the HinterlandOrbitSyncCoordinator server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"HinterlandCloudReconcilerCoordinator: sequence, then ship","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"HinterlandOpalRouterCoordinator: ship, then correct","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} +{"prompt":"Remove HinterlandGarnetModalStore's stray comma","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Request: # projects/hinterland/Sources/App/SessionStore.swift\n[worker.hinterlandacornwidgetcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandacornwidgetcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandacornwidgetcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandAcornWidgetCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48156\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 HinterlandAcornWidgetCoordinator'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":"Split projects/hinterland/apps/console/routes/usage.svelte by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Vereinheitliche die HinterlandCloudReconcilerStore-Validatoren","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"de"} +{"prompt":"# projects/hinterland/engine/render/atlas.cpp\n[worker.hinterlandgarnetmodalflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandgarnetmodalflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandgarnetmodalflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandGarnetModalFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48128\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/hinterland/engine/render/atlas.cpp and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"HinterlandNimbusFormCoordinator needs a paired pass: separate HinterlandNimbusFormCoordinator's policy from transport without behavior changes, plus give the existing implementation a read-only safety pass. Use projects/hinterland/crates/index/src/segment.rs as the source of truth, preserve the Redis Streams contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"$ pnpm test --filter HinterlandSummitProxyFlow\n RUN v3.2.4 /workspace/apps/console\n × HinterlandSummitProxyFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=48147 phase=resume storedCursor=seg-0183\n session=48147 phase=fetch requestCursor=seg-0183 pageSize=200\n session=48147 phase=commit receivedCursor=seg-0184 itemCount=0\n session=48147 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nReconstruct the HinterlandSummitProxyFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Find HinterlandSableParserStore's duplicate retry source","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"HinterlandSummitProxyCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Fresh release brief for HinterlandPineMetricsCoordinator:\n- primary outcome: produce a consumer guide for HinterlandPineMetricsCoordinator\n- companion outcome: give the existing implementation a read-only safety pass\n- repository entry point: projects/hinterland/workers/thumbnail/consumer.ex\n- platform constraint: Playwright\n- known complication: a query plan that changes after statistics refresh\n\nBoth results are required, but they should remain independently reviewable. Avoid a schema migration in this release; 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":"writing","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Please turn HinterlandAmberFilterStore'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":"The data is already available in projects/hinterland/infra/modules/edge/main.tf; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Polish the HinterlandNovaPickerService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating a misleading timeout name used in five packages in HinterlandOrbitSyncFlow, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Goal: Ticket OPS-48149: retire the legacy replay path for HinterlandAtlasSearchFlow\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 HinterlandAtlasSearchFlow 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":"HinterlandHarborIndexCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Symptom: The name pendingAck means two different things across HinterlandFrostPanelFlow's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Where did HinterlandCraneWorkspaceStore's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current HinterlandQuartzPlayerService design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandQuartzPlayerService\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Persist HinterlandAtlasSearchStore delivery attempts in projects/hinterland/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":"// projects/hinterland/crates/index/src/segment.rs\nfinal class HinterlandCraneWorkspaceFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandCraneWorkspaceFlow'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":"Polish the HinterlandRavenSessionService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Headsup: A flaky failure around HinterlandCoralUploadService survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandCoralUploadService\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"FYI: // projects/hinterland/internal/auth/refresh.go\nfinal class HinterlandCinderAuthFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandCinderAuthFlow 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":"Meanwhile: A copied hex color in HinterlandVelaDrawerService lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"HinterlandRainfallDBService flakes under UTC","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Describe HinterlandHarborIndexService's error envelope","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"HinterlandCinderAuthService's staging timeout is already known to be wrong: change the single projects/hinterland/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":"Move HinterlandSlateEditorFlow'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":"2026-07-30T08:14:11.409Z level=info service=hinterlandmosaicgridflow pod=hinterlandmosaicgridflow-7cf8 request_id=48148 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=hinterlandmosaicgridflow request_id=48148 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=hinterlandmosaicgridflow request_id=48148 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=hinterlandmosaicgridflow request_id=48148 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=hinterlandmosaicgridflow request_id=48148 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=hinterlandmosaicgridflow request_id=48148 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=hinterlandmosaicgridflow request_id=48148 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=hinterlandmosaicgridflow request_id=48148 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nFind the source of this HinterlandMosaicGridFlow symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"How should HinterlandPrismCacheStore be decomposed?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"HinterlandCraneWorkspaceCoordinator: sequence, then restructure","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Locally: # projects/hinterland/internal/auth/refresh.go\n[worker.hinterlandcedarpolicyflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandcedarpolicyflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandcedarpolicyflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandCedarPolicyFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48114\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 HinterlandCedarPolicyFlow'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":"Read projects/hinterland/internal/auth/refresh.go and tell me whether HinterlandKiteSchedulerStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"HinterlandTideWorkerCoordinator: sequence, then polish","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-48110\n\n08:02 deploy HinterlandFernSnapshotFlow 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 HinterlandFernSnapshotFlow 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":"Test Suite 'HinterlandMapleQueueFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[HinterlandMapleQueueFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/hinterland/workers/thumbnail/consumer.ex:144: error: -[HinterlandMapleQueueFlowTests 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 '-[HinterlandMapleQueueFlowTests 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\nFinish the visible HinterlandMapleQueueFlow 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":"One contained cleanup in projects/hinterland/cmd/exporter/main.py: remove the obsolete HinterlandEchoRegistryService import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"What is the safest way to split projects/hinterland/app/src/main/SyncWorker.kt into independently owned modules while HinterlandSummitProxyService's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"Test Suite 'HinterlandEchoRegistryFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[HinterlandEchoRegistryFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/hinterland/cmd/exporter/main.py:144: error: -[HinterlandEchoRegistryFlowTests 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 '-[HinterlandEchoRegistryFlowTests 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 HinterlandEchoRegistryFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"The HinterlandCinderAuthStore 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":"Could HinterlandMosaicGridService show the active Playwright 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":"Is there a cleaner way to separate HinterlandBeaconStoreStore'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":"En projects/hinterland/cmd/exporter/main.py, HinterlandLedgerGateStore tiene un problema intermitente en el flujo de React 19. Separa responsabilidades y elimina duplicación, conservando API, wire values, orden y comportamiento observable.\n\nRestricciones:\n- seguir con React 19\n- conservar compatibilidad y cancelación\n- limitar el cambio a HinterlandLedgerGateStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con React 19 alrededor de HinterlandLedgerGateStore.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"es"} +{"prompt":"Three teams extended HinterlandPineMetricsStore independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- avoid a schema migration in this release\n- retain the current Playwright operational envelope\n\nThe relevant code crosses search, Terraform, Flutter. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"HinterlandCedarPolicyCoordinator is blocking the next release because two validators with subtly different error strings. I need two concrete outcomes from a single pass: lay out a staged migration for HinterlandCedarPolicyCoordinator, and consolidate the duplicated normalization paths without changing behavior. Use the existing Terraform conventions in projects/hinterland/infra/modules/edge/main.tf; avoid a schema migration in this release. 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.9,"slice":"mixed","lang":"en"} +{"prompt":"Two deliverables are holding up HinterlandRainfallDBCoordinator. First, produce a consumer guide for HinterlandRainfallDBCoordinator. In the same workstream, correct the known stale timeout beside it. The relevant starting point is projects/hinterland/config/staging.toml, which follows Redis Streams conventions and currently suffers from memory growth during hour-long imports. Avoid a schema migration in this release.\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":"writing","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Em projects/hinterland/config/staging.toml, o HinterlandLumenChartStore tem um problema intermitente no fluxo de Redis Streams. Siga queue, scheduler e cancelamento, compare hipóteses e encontre a causa antes de mudar código.\n\nRestrições:\n- continuar com Redis Streams\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao HinterlandLumenChartStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"pt"} +{"prompt":"Two asks around HinterlandMoonlitSDKCoordinator: (1) assess ownership and failure handling in projects/hinterland/services/ledger/replay.go; (2) capture the contract and rollback note for consumers. Avoid a schema migration in this release, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Drop HinterlandMicaProfileStore's unused import","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-48130\n\n08:02 deploy HinterlandNimbusFormFlow 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 HinterlandNimbusFormFlow 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":"HinterlandDriftConsoleCoordinator: sort out the rough edge","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Production: // projects/hinterland/packages/api/openapi.yaml\nfinal class HinterlandRainfallDBFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandRainfallDBFlow; 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":"Staging: # projects/hinterland/lib/codec/frame.cc\n[worker.hinterlandfrostpanelcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandfrostpanelcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandfrostpanelcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandFrostPanelCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48158\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/hinterland/lib/codec/frame.cc and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"HinterlandFernSnapshotStore is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- avoid a schema migration in this release\n- retain the current Redis Streams operational envelope\n\nThe relevant code crosses search, Terraform, Flutter. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"// projects/hinterland/config/staging.toml\nfinal class HinterlandVelaDrawerFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Walk through what the artifact proves about HinterlandVelaDrawerFlow; 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":"HinterlandDeltaCanvasCoordinator needs a paired pass: change HinterlandDeltaCanvasCoordinator's known staging timeout from 15 to 30 seconds, plus give the existing implementation a read-only safety pass. Use projects/hinterland/apps/console/routes/usage.svelte as the source of truth, preserve the Core Data contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"CI: The behavior of HinterlandJuniperCLIService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/hinterland/db/migrations/20260730_events.sql. 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- touch generated artifacts only through their checked-in generator\n- avoid a schema migration in this release\n- retain the current Core Data operational envelope\n\nThe relevant code crosses search, Terraform, Flutter. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"PM needs a concise migration note for HinterlandOrbitSyncStore, 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":"Nobody is asking for code changes yet; we first need to understand whether the current HinterlandFrostPanelStore design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandFrostPanelStore\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Documente o contrato de HinterlandDeltaCanvasService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"pt"} +{"prompt":"The name pendingAck means two different things across HinterlandMarbleTokenStore's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Atlas: projects/hinterland/cmd/exporter/main.py の HinterlandAmberFilterFlow で、React 19 の flow に断続的な問題が起きています。 queue、scheduler、cancel 経路を追い、仮説を比較して、変更前に原因を特定してください。\n\n制約:\n- React 19 を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は HinterlandAmberFilterFlow のみ","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"} +{"prompt":"In projects/hinterland/ml/pipeline/features.py hat HinterlandLedgerGateService ein sporadisches Problem im React 19-Ablauf. Verfolge Queue, Scheduler und Abbruch, vergleiche Hypothesen und finde die Ursache vor jeder Änderung.\n\nRandbedingungen:\n- React 19 weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf HinterlandLedgerGateService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um HinterlandLedgerGateService mit React 19 kompatibel.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} +{"prompt":"Beacon: Incident timeline — INC-48150\n\n08:02 deploy HinterlandIrisBatchCoordinator 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 HinterlandIrisBatchCoordinator 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":"Split projects/isotope/ml/pipeline/features.py by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-49139: finish the compact IsotopeHarborIndexFlow filter experience\n\nRoute: /catalog/search\nSource: projects/isotope/ui/settings/PrivacyPane.tsx\nFramework: Tokio\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nFinish the visible IsotopeHarborIndexFlow state described above: responsive layout, correct selection restoration, keyboard focus, accessible labels, dark mode, and reduced-motion behavior.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"IsotopeSummitProxyCoordinator: restructure, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Center the IsotopeAmberFilterService modal","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Walk through IsotopeIrisBatchStore's SyncWorker.kt","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/isotope/Sources/App/SessionStore.swift b/projects/isotope/Sources/App/SessionStore.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/Sources/App/SessionStore.swift\n+++ b/projects/isotope/Sources/App/SessionStore.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure IsotopeCloudReconcilerFlow so duplicated normalization and shutdown ownership have one home. Preserve public behavior, wire values, logging fields, and ordering; extend characterization coverage first.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Wire a IsotopeFlintTimelineFlow background task in projects/isotope/services/ledger/replay.go that expires abandoned sessions, records an OpenTelemetry span, and yields cleanly when shutdown begins.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Production says IsotopeFlintTimelineService is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current PostgreSQL 17 operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Cinder: The IsotopeLedgerGateService feature flag default should be false in test, exactly like production; correct that config entry and nothing else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"IsotopeSableParserCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Teach IsotopeOpalRouterStore to verify signed continuation tokens, reject cross-tenant cursors, and rotate keys without invalidating tokens issued during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"// projects/isotope/crates/index/src/segment.rs\nfinal class IsotopeBeaconStoreFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nWalk through what the artifact proves about IsotopeBeaconStoreFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Could IsotopeNovaPickerService show the active NATS JetStream sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"IsotopeKiteSchedulerCoordinator: correct, then assess","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Delta: projects/isotope/packages/api/openapi.yaml の IsotopeGarnetModalFlow で、NATS JetStream の flow に断続的な問題が起きています。 責務を分離して重複をなくし、API、wire value、順序、観測可能な動作は変えないでください。\n\n制約:\n- NATS JetStream を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は IsotopeGarnetModalFlow のみ","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"ja"} +{"prompt":"Ember: Incident timeline — INC-49124\n\n08:02 deploy IsotopeAmberFilterFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nDetermine why IsotopeAmberFilterFlow produces this result. Trace ordering, cancellation, shared state, and scheduler behavior; identify the root cause before suggesting a patch.","purpose":"debugging","secondary":"planning","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"diff --git a/projects/isotope/Sources/CLI/Commands/Doctor.swift b/projects/isotope/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/isotope/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit IsotopeSlateEditorFlow by responsibility and make cancellation ownership explicit. Characterize the current sequence before moving code and keep callers unchanged.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"PM needs a concise migration note for IsotopeCloudReconcilerStore, including the user impact, rollback trigger, and the one configuration key operators must change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"IsotopeWrenExportCoordinator needs a paired pass: produce a consumer guide for IsotopeWrenExportCoordinator, plus give the existing implementation a read-only safety pass. Use projects/isotope/db/migrations/20260730_events.sql as the source of truth, preserve the SQLite contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Frost: The first IsotopeBirchMigratorFlow request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Garnet: Two asks around IsotopeAmberFilterCoordinator: (1) separate IsotopeAmberFilterCoordinator's policy from transport without behavior changes; (2) capture the contract and rollback note for consumers. Keep the patch readable for a small on-call review, and leave a clear boundary between the resulting artifacts or edits.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"A previously stable test around IsotopeDeltaCanvasFlow now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"IsotopeMosaicGridCoordinator: polish, then assess","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Harbor: Two asks around IsotopeFernSnapshotCoordinator: (1) assess ownership and failure handling in projects/isotope/apps/console/routes/usage.svelte; (2) capture the contract and rollback note for consumers. Keep the patch readable for a small on-call review, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Ticket OPS-49148: retire the legacy replay path for IsotopePrismCacheFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nTurn the material above into a concise IsotopePrismCacheFlow release note and operator runbook section. State impact, detection, rollback, and the client-visible contract; do not modify code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"Split IsotopeOrbitSyncService without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Clarify IsotopeMapleQueueService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Compare IsotopeMosaicGridStore's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Translate the IsotopeEchoRegistryService setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"The minimum supported WebGPU version in projects/isotope/Sources/App/SessionStore.swift is one patch behind the lockfile. Align that single value and regenerate only the affected metadata.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Fresh release brief for IsotopeDriftConsoleCoordinator:\n- primary outcome: find the unknown cause of stale cursors when a page is resumed\n- companion outcome: correct the known stale timeout beside it\n- repository entry point: projects/isotope/services/ledger/replay.go\n- platform constraint: PostgreSQL 17\n- known complication: stale cursors when a page is resumed\n\nBoth results are required, but they should remain independently reviewable. Keep the patch readable for a small on-call review; retain serialization and authorization boundaries; cover cancellation, idempotent retries, and rollback; and avoid drive-by cleanup. Use the code as the source of truth, call out assumptions, and state how an on-call engineer can tell that either part is unsafe to ship.","purpose":"debugging","secondary":"quickFix","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"UI ticket DES-49159: finish the compact IsotopeBirchMigratorCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/isotope/ui/settings/PrivacyPane.tsx\nFramework: Tokio\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring IsotopeBirchMigratorCoordinator's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"IsotopeRavenSessionStore has four wrappers that only translate the same error enum. Collapse them into one adapter and preserve every public case, message, and metric label.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Two engineers disagree about whether IsotopeCinderAuthFlow's cache is authoritative. Walk the reads and writes in projects/isotope/cmd/exporter/main.py and settle that question from the code. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Iris: Split projects/isotope/config/staging.toml by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Juniper: The public surface of IsotopeMapleQueueStore is frozen, but its internal ownership in projects/isotope/crates/index/src/segment.rs is difficult to test and even harder to change safely. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeMapleQueueStore\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Two asks around IsotopeQuartzPlayerCoordinator: (1) lay out a staged migration for IsotopeQuartzPlayerCoordinator; (2) then implement the bounded durable-cursor handler. Keep the patch readable for a small on-call review, and leave a clear boundary between the resulting artifacts or edits.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Does IsotopeCopperBridgeStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists? Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"We need to move IsotopeTideWorkerService from the legacy store to Tokio. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Responsive layout for IsotopeAcornWidgetStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"IsotopeLedgerGateCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"IsotopeSpruceDaemonCoordinator is blocking the next release because duplicate retries after a network handoff. I need two concrete outcomes from a single pass: find the unknown cause of duplicate retries after a network handoff, and capture the contract and rollback note for consumers. Use the existing PostgreSQL 17 conventions in projects/isotope/internal/auth/refresh.go; keep the patch readable for a small on-call review. Keep the outcomes distinct so reviewers can see which evidence supports the assessment and which files or prose satisfy the requested change.\n\nConstraints:\n- preserve public wire values and tenant boundaries\n- cover cancellation and retry behavior\n- avoid generated code and unrelated cleanup\n- include a rollback trigger that an on-call engineer can measure\n\nThis is a fresh workstream for the release, so derive everything from the repository and the context here.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Incident timeline — INC-49113\n\n08:02 deploy IsotopeWillowCodecFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. From this evidence, draft consumer-facing migration guidance for IsotopeWillowCodecFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"IsotopeCraneWorkspaceCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Add a bounded IsotopeCloudReconcilerService export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add a bounded IsotopePineMetricsService export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Compare IsotopeIrisBatchService's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'IsotopeWrenExportFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[IsotopeWrenExportFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/isotope/src/sync/reconcile.ts:144: error: -[IsotopeWrenExportFlowTests testRestoresSelectionAfterBackgrounding] : XCTAssertEqual failed: (\"Optional(4)\") is not equal to (\"Optional(3)\")\nAccessibility hierarchy at failure:\n Application, 0x104c, pid: 812\n Window, identifier: \"main\"\n NavigationStack, identifier: \"catalog\"\n Button, label: \"Filters\", value: \"2 active\"\n CollectionView, identifier: \"results-grid\", rows: 24\n Sheet, identifier: \"filter-sheet\"\n TextField, label: \"Search filters\", value: \"\"\n Switch, label: \"Available offline\", value: \"1\"\n Button, label: \"Apply\", enabled: true\nTest Case '-[IsotopeWrenExportFlowTests testRestoresSelectionAfterBackgrounding]' failed (4.812 seconds).\n\nSimulator: iPhone 17 Pro, iOS 27.0, en_US, content size XXXL, Reduce Motion enabled. The screenshot looks correct. The mismatch is the internal selected-segment index after the scene becomes active; tapping Apply a second time makes it three again.\n\nUse the UI evidence to complete IsotopeWrenExportFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"The IsotopeCedarPolicyStore surface in projects/isotope/cmd/exporter/main.py is stable now; turn its edge cases into API documentation with one successful example and one cancellation example.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Cadre la migration de IsotopeMarbleTokenService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"fr"} +{"prompt":"Test Suite 'IsotopeAtlasSearchFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[IsotopeAtlasSearchFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/isotope/Sources/App/SessionStore.swift:144: error: -[IsotopeAtlasSearchFlowTests testRestoresSelectionAfterBackgrounding] : XCTAssertEqual failed: (\"Optional(4)\") is not equal to (\"Optional(3)\")\nAccessibility hierarchy at failure:\n Application, 0x104c, pid: 812\n Window, identifier: \"main\"\n NavigationStack, identifier: \"catalog\"\n Button, label: \"Filters\", value: \"2 active\"\n CollectionView, identifier: \"results-grid\", rows: 24\n Sheet, identifier: \"filter-sheet\"\n TextField, label: \"Search filters\", value: \"\"\n Switch, label: \"Available offline\", value: \"1\"\n Button, label: \"Apply\", enabled: true\nTest Case '-[IsotopeAtlasSearchFlowTests testRestoresSelectionAfterBackgrounding]' failed (4.812 seconds).\n\nSimulator: iPhone 17 Pro, iOS 27.0, en_US, content size XXXL, Reduce Motion enabled. The screenshot looks correct. The mismatch is the internal selected-segment index after the scene becomes active; tapping Apply a second time makes it three again.\n\nUse the UI evidence to complete IsotopeAtlasSearchFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Release verification found a single stale IsotopeDriftConsoleStore value; the cause, desired value, and affected assertion are already agreed. Change the staging timeout from 15 seconds to 30, adjust the adjacent assertion that encodes that value, and avoid unrelated formatting, renames, dependency bumps, or cleanup.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current PostgreSQL 17 operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Please resist widening this one: IsotopeEmberRelayService works, but staging still carries a setting that production corrected last month. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeEmberRelayService\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Ticket OPS-49158: retire the legacy replay path for IsotopeLumenChartCoordinator\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nAssess IsotopeLumenChartCoordinator for durability, tenant isolation, races, and misleading observability. Separate blockers from questions and do not produce a patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"En projects/isotope/packages/api/openapi.yaml, IsotopeBasilRunnerStore tiene un problema intermitente en el flujo de NATS JetStream. Propón fases, compatibilidad, métricas, rollback y ownership; detente antes de tocar código.\n\nRestricciones:\n- seguir con NATS JetStream\n- conservar compatibilidad y cancelación\n- limitar el cambio a IsotopeBasilRunnerStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con NATS JetStream alrededor de IsotopeBasilRunnerStore.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.81,"slice":"boundary","lang":"es"} -{"prompt":"Summarize the IsotopeSlateEditorStore changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"en"} -{"prompt":"IsotopeAtlasSearchService flakes under UTC","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Find IsotopeFernSnapshotStore's duplicate retry source","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"Kestrel: Test Suite 'IsotopeTideWorkerFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[IsotopeTideWorkerFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/isotope/lib/codec/frame.cc:144: error: -[IsotopeTideWorkerFlowTests testRestoresSelectionAfterBackgrounding] : XCTAssertEqual failed: (\"Optional(4)\") is not equal to (\"Optional(3)\")\nAccessibility hierarchy at failure:\n Application, 0x104c, pid: 812\n Window, identifier: \"main\"\n NavigationStack, identifier: \"catalog\"\n Button, label: \"Filters\", value: \"2 active\"\n CollectionView, identifier: \"results-grid\", rows: 24\n Sheet, identifier: \"filter-sheet\"\n TextField, label: \"Search filters\", value: \"\"\n Switch, label: \"Available offline\", value: \"1\"\n Button, label: \"Apply\", enabled: true\nTest Case '-[IsotopeTideWorkerFlowTests testRestoresSelectionAfterBackgrounding]' failed (4.812 seconds).\n\nSimulator: iPhone 17 Pro, iOS 27.0, en_US, content size XXXL, Reduce Motion enabled. The screenshot looks correct. The mismatch is the internal selected-segment index after the scene becomes active; tapping Apply a second time makes it three again.\n\nBring IsotopeTideWorkerFlow's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"diff --git a/projects/isotope/app/src/main/SyncWorker.kt b/projects/isotope/app/src/main/SyncWorker.kt\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/app/src/main/SyncWorker.kt\n+++ b/projects/isotope/app/src/main/SyncWorker.kt\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is IsotopeFernSnapshotFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Assess the IsotopeMosaicGridService diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Teach IsotopeOspreyJobService to verify signed continuation tokens, reject cross-tenant cursors, and rotate keys without invalidating tokens issued during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Lumen: diff --git a/projects/isotope/crates/index/src/segment.rs b/projects/isotope/crates/index/src/segment.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/crates/index/src/segment.rs\n+++ b/projects/isotope/crates/index/src/segment.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate IsotopeNovaPickerFlow's parallel adapters behind a single internal boundary, with no changes to API, timing, serialization, metrics, or error text.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Maple: Ticket OPS-49112: retire the legacy replay path for IsotopeEmberRelayFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nTurn the material above into a concise IsotopeEmberRelayFlow release note and operator runbook section. State impact, detection, rollback, and the client-visible contract; do not modify code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.62,"slice":"pasted-context","lang":"en"} -{"prompt":"Our support and SDK teams keep answering the same questions about IsotopeLumenChartStore, but the current prose in projects/isotope/db/migrations/20260730_events.sql only describes the happy path. Draft an ADR plus migration note that records the decision, rejected alternatives, compatibility window, observability signals, and the exact action required from consumers.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing SQLite deployment\n- keep the work scoped to IsotopeLumenChartStore and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"projects/isotope/app/src/main/SyncWorker.kt 里的 IsotopeCraneWorkspaceStore 最近在 SQLite 流程中出现间歇性问题。 请阅读现有流程，判断 ownership、取消和顺序是否安全，只需要分析。\n\n约束：\n- 继续使用 SQLite\n- 保持兼容性和取消语义\n- 改动只限于 IsotopeCraneWorkspaceStore","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"zh"} -{"prompt":"Release engineering needs a IsotopeNovaPickerStore changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"Flip IsotopeWrenExportService's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"core","lang":"en"} -{"prompt":"IsotopeHarborIndexCoordinator: handle the lingering thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"vague-eval","lang":"en"} -{"prompt":"IsotopeTideWorkerCoordinator: maybe tighten this up","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"vague-eval","lang":"en"} -{"prompt":"Korrigiere den IsotopeMarbleTokenStore-Timeout","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"boundary","lang":"de"} +{"prompt":"Ticket OPS-49158: retire the legacy replay path for IsotopeLumenChartCoordinator\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nAssess IsotopeLumenChartCoordinator for durability, tenant isolation, races, and misleading observability. Separate blockers from questions and do not produce a patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"En projects/isotope/packages/api/openapi.yaml, IsotopeBasilRunnerStore tiene un problema intermitente en el flujo de NATS JetStream. Propón fases, compatibilidad, métricas, rollback y ownership; detente antes de tocar código.\n\nRestricciones:\n- seguir con NATS JetStream\n- conservar compatibilidad y cancelación\n- limitar el cambio a IsotopeBasilRunnerStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con NATS JetStream alrededor de IsotopeBasilRunnerStore.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"es"} +{"prompt":"Summarize the IsotopeSlateEditorStore changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"IsotopeAtlasSearchService flakes under UTC","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Find IsotopeFernSnapshotStore's duplicate retry source","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Kestrel: Test Suite 'IsotopeTideWorkerFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[IsotopeTideWorkerFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/isotope/lib/codec/frame.cc:144: error: -[IsotopeTideWorkerFlowTests testRestoresSelectionAfterBackgrounding] : XCTAssertEqual failed: (\"Optional(4)\") is not equal to (\"Optional(3)\")\nAccessibility hierarchy at failure:\n Application, 0x104c, pid: 812\n Window, identifier: \"main\"\n NavigationStack, identifier: \"catalog\"\n Button, label: \"Filters\", value: \"2 active\"\n CollectionView, identifier: \"results-grid\", rows: 24\n Sheet, identifier: \"filter-sheet\"\n TextField, label: \"Search filters\", value: \"\"\n Switch, label: \"Available offline\", value: \"1\"\n Button, label: \"Apply\", enabled: true\nTest Case '-[IsotopeTideWorkerFlowTests testRestoresSelectionAfterBackgrounding]' failed (4.812 seconds).\n\nSimulator: iPhone 17 Pro, iOS 27.0, en_US, content size XXXL, Reduce Motion enabled. The screenshot looks correct. The mismatch is the internal selected-segment index after the scene becomes active; tapping Apply a second time makes it three again.\n\nBring IsotopeTideWorkerFlow's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"diff --git a/projects/isotope/app/src/main/SyncWorker.kt b/projects/isotope/app/src/main/SyncWorker.kt\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/app/src/main/SyncWorker.kt\n+++ b/projects/isotope/app/src/main/SyncWorker.kt\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is IsotopeFernSnapshotFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Assess the IsotopeMosaicGridService diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Teach IsotopeOspreyJobService to verify signed continuation tokens, reject cross-tenant cursors, and rotate keys without invalidating tokens issued during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Lumen: diff --git a/projects/isotope/crates/index/src/segment.rs b/projects/isotope/crates/index/src/segment.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/crates/index/src/segment.rs\n+++ b/projects/isotope/crates/index/src/segment.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate IsotopeNovaPickerFlow's parallel adapters behind a single internal boundary, with no changes to API, timing, serialization, metrics, or error text.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Maple: Ticket OPS-49112: retire the legacy replay path for IsotopeEmberRelayFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nTurn the material above into a concise IsotopeEmberRelayFlow release note and operator runbook section. State impact, detection, rollback, and the client-visible contract; do not modify code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"Our support and SDK teams keep answering the same questions about IsotopeLumenChartStore, but the current prose in projects/isotope/db/migrations/20260730_events.sql only describes the happy path. Draft an ADR plus migration note that records the decision, rejected alternatives, compatibility window, observability signals, and the exact action required from consumers.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing SQLite deployment\n- keep the work scoped to IsotopeLumenChartStore and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"projects/isotope/app/src/main/SyncWorker.kt 里的 IsotopeCraneWorkspaceStore 最近在 SQLite 流程中出现间歇性问题。 请阅读现有流程，判断 ownership、取消和顺序是否安全，只需要分析。\n\n约束：\n- 继续使用 SQLite\n- 保持兼容性和取消语义\n- 改动只限于 IsotopeCraneWorkspaceStore","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"zh"} +{"prompt":"Release engineering needs a IsotopeNovaPickerStore changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Flip IsotopeWrenExportService's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"IsotopeHarborIndexCoordinator: handle the lingering thing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"IsotopeTideWorkerCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Korrigiere den IsotopeMarbleTokenStore-Timeout","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"de"} {"prompt":"This should remain a deliberately small patch: IsotopeCinderAuthService has one known configuration mistake in projects/isotope/cmd/exporter/main.py, not an open-ended failure investigation. Correct the known literal and the test that intentionally mirrors it; the final diff should stay local enough for an on-call engineer to verify at a glance.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing WebGPU deployment\n- keep the work scoped to IsotopeCinderAuthService and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Nimbus: The destination for IsotopeDeltaCanvasService is broadly agreed; the missing piece is a reversible route from projects/isotope/internal/auth/refresh.go to that target. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeDeltaCanvasService\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Any races in IsotopeSummitProxyStore?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Sketch the IsotopeQuartzPlayerStore migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"Opal: Test Suite 'IsotopeRainfallDBFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[IsotopeRainfallDBFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/isotope/db/migrations/20260730_events.sql:144: error: -[IsotopeRainfallDBFlowTests testRestoresSelectionAfterBackgrounding] : XCTAssertEqual failed: (\"Optional(4)\") is not equal to (\"Optional(3)\")\nAccessibility hierarchy at failure:\n Application, 0x104c, pid: 812\n Window, identifier: \"main\"\n NavigationStack, identifier: \"catalog\"\n Button, label: \"Filters\", value: \"2 active\"\n CollectionView, identifier: \"results-grid\", rows: 24\n Sheet, identifier: \"filter-sheet\"\n TextField, label: \"Search filters\", value: \"\"\n Switch, label: \"Available offline\", value: \"1\"\n Button, label: \"Apply\", enabled: true\nTest Case '-[IsotopeRainfallDBFlowTests testRestoresSelectionAfterBackgrounding]' failed (4.812 seconds).\n\nSimulator: iPhone 17 Pro, iOS 27.0, en_US, content size XXXL, Reduce Motion enabled. The screenshot looks correct. The mismatch is the internal selected-segment index after the scene becomes active; tapping Apply a second time makes it three again.\n\nBring IsotopeRainfallDBFlow's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.76,"slice":"pasted-context","lang":"en"} -{"prompt":"diff --git a/projects/isotope/db/migrations/20260730_events.sql b/projects/isotope/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/db/migrations/20260730_events.sql\n+++ b/projects/isotope/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is IsotopeVelaDrawerFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"# projects/isotope/ml/pipeline/features.py\n[worker.isotopecinderauthcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.isotopecinderauthcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.isotopecinderauthcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.IsotopeCinderAuthCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-49157\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nThe intended correction is already known: change only the stale 15-second setting to 30 seconds in projects/isotope/ml/pipeline/features.py and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.38,"slice":"pasted-context","lang":"en"} -{"prompt":"IsotopeOspreyJobCoordinator: deal with the small issue","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"vague-eval","lang":"en"} -{"prompt":"IsotopeIrisBatchCoordinator: diagnose, then assess","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"What sequence would let IsotopeFlintTimelineStore adopt PostgreSQL 17 with dual reads but no dual writes? Include data validation, canary scope, and the decision that ends compatibility mode.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Prism: Two asks around IsotopeCoralUploadCoordinator: (1) lay out a staged migration for IsotopeCoralUploadCoordinator; (2) then implement the bounded durable-cursor handler. Keep the patch readable for a small on-call review, and leave a clear boundary between the resulting artifacts or edits.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.77,"slice":"mixed","lang":"en"} -{"prompt":"Quartz: # projects/isotope/workers/thumbnail/consumer.ex\n[worker.isotopeacornwidgetflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.isotopeacornwidgetflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.isotopeacornwidgetflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.IsotopeAcornWidgetFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-49129\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Make the one confirmed configuration correction in projects/isotope/workers/thumbnail/consumer.ex. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.43,"slice":"pasted-context","lang":"fr"} -{"prompt":"Sketch the IsotopeAtlasSearchStore migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Dedupe IsotopeDriftConsoleService's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-49111\n\n08:02 deploy IsotopeBasilRunnerFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCapture the IsotopeBasilRunnerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.59,"slice":"pasted-context","lang":"en"} -{"prompt":"Two deliverables are holding up IsotopeEchoRegistryCoordinator. First, lay out a staged migration for IsotopeEchoRegistryCoordinator. In the same workstream, also add the visible loading and offline states. The relevant starting point is projects/isotope/lib/codec/frame.cc, which follows Tokio conventions and currently suffers from a misleading timeout name used in five packages. Keep the patch readable for a small on-call review.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.96,"slice":"mixed","lang":"en"} -{"prompt":"IsotopeFrostPanelStore's openapi.yaml needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"$ pnpm test --filter IsotopeNimbusFormCoordinator\n RUN v3.2.4 /workspace/apps/console\n × IsotopeNimbusFormCoordinator > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=49153 phase=resume storedCursor=seg-0183\n session=49153 phase=fetch requestCursor=seg-0183 pageSize=200\n session=49153 phase=commit receivedCursor=seg-0184 itemCount=0\n session=49153 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Find the source of this IsotopeNimbusFormCoordinator symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.95,"slice":"pasted-context","lang":"ja"} -{"prompt":"We need to move IsotopeRavenSessionFlow from the legacy store to Tokio. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"IsotopeRainfallDBCoordinator: give it a nicer flow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"vague-eval","lang":"en"} -{"prompt":"Raven: Incident timeline — INC-49125\n\n08:02 deploy IsotopeOrbitSyncFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nFrom this evidence, draft consumer-facing migration guidance for IsotopeOrbitSyncFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"pasted-context","lang":"en"} -{"prompt":"Give IsotopeNimbusFormStore's detail pane a sticky action bar, fluid type at narrow widths, and a keyboard-safe scroll region that still works at 200% zoom.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} -{"prompt":"IsotopeHarborIndexStore's metric is misspelled as succesful_total in one declaration. Correct that literal and its exact test expectation, without renaming anything else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"boundary","lang":"en"} -{"prompt":"Sable: projects/isotope/apps/console/routes/usage.svelte の IsotopeCraneWorkspaceService で、SQLite の flow に断続的な問題が起きています。 責務を分離して重複をなくし、API、wire value、順序、観測可能な動作は変えないでください。\n\n制約:\n- SQLite を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は IsotopeCraneWorkspaceService のみ","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"ja"} -{"prompt":"Correct the IsotopeKiteSchedulerService flag default","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"core","lang":"en"} -{"prompt":"Bump IsotopeSlateEditorService's timeout to 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"core","lang":"en"} -{"prompt":"Lay out a two-milestone strategy for eliminating a deadlock that appears only during shutdown in IsotopeRainfallDBStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Read projects/isotope/db/migrations/20260730_events.sql and tell me whether IsotopeRainfallDBService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"IsotopeOpalRouterCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"Fresh release brief for IsotopeEmberRelayCoordinator:\n- primary outcome: lay out a staged migration for IsotopeEmberRelayCoordinator\n- companion outcome: then implement the bounded durable-cursor handler\n- repository entry point: projects/isotope/Sources/App/SessionStore.swift\n- platform constraint: WebGPU\n- known complication: two validators with subtly different error strings\n\nBoth results are required, but they should remain independently reviewable. Keep the patch readable for a small on-call review; retain serialization and authorization boundaries; cover cancellation, idempotent retries, and rollback; and avoid drive-by cleanup. Use the code as the source of truth, call out assumptions, and state how an on-call engineer can tell that either part is unsafe to ship.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.93,"slice":"mixed","lang":"en"} -{"prompt":"Check IsotopeBeaconStoreService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"IsotopeCloudReconcilerCoordinator: the screen feels unfinished","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"vague-eval","lang":"en"} -{"prompt":"Incident timeline — INC-49117\n\n08:02 deploy IsotopeKiteSchedulerFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCapture the IsotopeKiteSchedulerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.62,"slice":"pasted-context","lang":"en"} -{"prompt":"The public surface of IsotopeWillowCodecStore is frozen, but its internal ownership in projects/isotope/apps/console/routes/usage.svelte is difficult to test and even harder to change safely. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeWillowCodecStore\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.77,"slice":"boundary","lang":"en"} -{"prompt":"IsotopePineMetricsCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"vague-eval","lang":"en"} -{"prompt":"In projects/isotope/config/staging.toml hat IsotopeBasilRunnerService ein sporadisches Problem im NATS JetStream-Ablauf. Verfasse eine Consumer-Doku mit Vertrag, Fehlern, Retry und einem kopierbaren Beispiel; ändere keinen Handler.\n\nRandbedingungen:\n- NATS JetStream weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf IsotopeBasilRunnerService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um IsotopeBasilRunnerService mit NATS JetStream kompatibel.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"de"} -{"prompt":"Tide: // projects/isotope/apps/console/routes/usage.svelte\nfinal class IsotopeIrisBatchFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nSplit IsotopeIrisBatchFlow by responsibility and make cancellation ownership explicit. Characterize the current sequence before moving code and keep callers unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"I inherited IsotopeKiteSchedulerStore and need a careful read of projects/isotope/cmd/exporter/main.py before I can sign off on the next release. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing WebGPU deployment\n- keep the work scoped to IsotopeKiteSchedulerStore and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.\n\nNothing is reported broken, so judge and explain current behavior without inventing a failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"The first IsotopeOspreyJobStore request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"boundary","lang":"en"} -{"prompt":"IsotopeNovaPickerCoordinator: polish the last piece","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"vague-eval","lang":"en"} -{"prompt":"diff --git a/projects/isotope/infra/modules/edge/main.tf b/projects/isotope/infra/modules/edge/main.tf\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/infra/modules/edge/main.tf\n+++ b/projects/isotope/infra/modules/edge/main.tf\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit IsotopeDeltaCanvasCoordinator by responsibility and make cancellation ownership explicit. Characterize the current sequence before moving code and keep callers unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"IsotopeJuniperCLICoordinator: sort out the rough edge","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"vague-eval","lang":"en"} -{"prompt":"Ownership of IsotopeEmberRelayStore is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Give me a staged design with ownership boundaries, compatibility seams, migration order, telemetry, failure drills, rollback criteria, and explicit decisions we can defer; stop before implementation.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current WebGPU operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.83,"slice":"boundary","lang":"en"} -{"prompt":"Umbra: Incident timeline — INC-49141\n\n08:02 deploy IsotopeAsterWebhookFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current IsotopeAsterWebhookFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"Our support and SDK teams keep answering the same questions about IsotopeEchoRegistryStore, but the current prose in projects/isotope/lib/codec/frame.cc only describes the happy path. Draft an ADR plus migration note that records the decision, rejected alternatives, compatibility window, observability signals, and the exact action required from consumers.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing Tokio deployment\n- keep the work scoped to IsotopeEchoRegistryStore and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"En projects/isotope/apps/console/routes/usage.svelte, IsotopeNimbusFormService tiene un problema intermitente en el flujo de SQLite. Sigue queue, scheduler y cancelación, compara hipótesis y encuentra la causa antes de proponer cambios.\n\nRestricciones:\n- seguir con SQLite\n- conservar compatibilidad y cancelación\n- limitar el cambio a IsotopeNimbusFormService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.87,"slice":"core","lang":"es"} -{"prompt":"projects/isotope/web/components/FilterDrawer.vue 里的 IsotopeJuniperCLIService 最近在 PostgreSQL 17 流程中出现间歇性问题。 请完成 responsive layout、空状态、retry、键盘焦点、dark mode 和 reduced motion。\n\n约束：\n- 继续使用 PostgreSQL 17\n- 保持兼容性和取消语义\n- 改动只限于 IsotopeJuniperCLIService","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"zh"} -{"prompt":"Milestones for replacing IsotopeWrenExportStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Flip IsotopeVelaDrawerStore's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"boundary","lang":"en"} -{"prompt":"Security flagged IsotopeBirchMigratorStore for a read-only pass because its Tokio boundary mixes tenant data, retries, and cancellation in subtle ways. Trace ownership, ordering, error propagation, and cancellation; call out concrete risks with file references, but do not edit the implementation or turn the answer into a replacement design.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current Tokio operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.\n\nNothing is reported broken, so judge and explain current behavior without inventing a failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"boundary","lang":"en"} -{"prompt":"IsotopePrismCacheCoordinator: the docs need something","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"# CI job 49130: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: PostgreSQL 17\n\n[setup] restoring cache key deps-a2f91c ... hit\n[setup] starting postgres:17 ... healthy after 4.2s\n[setup] starting redis:8 ... healthy after 0.8s\n[test] shard 3/8 selected 412 tests\n[test] IsotopeQuartzPlayerFlowIntegration.replays_after_timeout ... ok\n[test] IsotopeQuartzPlayerFlowIntegration.cancels_orphaned_batch ... FAILED\n\nExpected:\n pending_jobs{queue=\"replay\"} 0\nActual:\n pending_jobs{queue=\"replay\"} 1\n\nCaptured spans:\n batch.receive 2.1ms status=ok\n storage.transaction 44.8ms status=cancelled\n batch.nack \n\nteardown warning: resource still in use: redis connection pool (1 borrower)\nretry 1/2 with identical seed ... passed\nretry 2/2 with identical seed ... passed\n\nThe failure began after the test suite was sharded, but it sometimes appears on an unsharded nightly run. There are no wall-clock sleeps in this test; it advances the fake scheduler until idle.\n\nDeliver the IsotopeQuartzPlayerFlow server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.81,"slice":"pasted-context","lang":"en"} -{"prompt":"Vela: // projects/isotope/engine/render/atlas.cpp\nfinal class IsotopeEchoRegistryFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nWalk through what the artifact proves about IsotopeEchoRegistryFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Willow: diff --git a/projects/isotope/Sources/CLI/Commands/Doctor.swift b/projects/isotope/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/isotope/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nWire IsotopeMoonlitSDKCoordinator's schema, storage, handler, and worker path so continuation is signed, duplicate delivery is stable, and shutdown cannot acknowledge uncommitted work.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Our support and SDK teams keep answering the same questions about IsotopeGarnetModalService, but the current prose in projects/isotope/packages/api/openapi.yaml only describes the happy path. Draft an ADR plus migration note that records the decision, rejected alternatives, compatibility window, observability signals, and the exact action required from consumers.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing NATS JetStream deployment\n- keep the work scoped to IsotopeGarnetModalService and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} -{"prompt":"Xylem: # projects/isotope/engine/render/atlas.cpp\n[worker.isotoperavensessioncoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.isotoperavensessioncoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.isotoperavensessioncoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.IsotopeRavenSessionCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-49154\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nThe intended correction is already known: change only the stale 15-second setting to 30 seconds in projects/isotope/engine/render/atlas.cpp and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.43,"slice":"pasted-context","lang":"en"} -{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current IsotopeMicaProfileService design actually guarantees what its callers assume. Follow one successful request and each early exit through the code, then rank findings by impact and state which apparent hazards are already ruled out by invariants.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeMicaProfileService\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"IsotopeMapleQueueCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.62,"slice":"mixed","lang":"en"} -{"prompt":"PM needs a concise migration note for IsotopeMicaProfileStore, including the user impact, rollback trigger, and the one configuration key operators must change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"IsotopeFrostPanelCoordinator needs a paired pass: find the unknown cause of stale cursors when a page is resumed, plus capture the contract and rollback note for consumers. Use projects/isotope/packages/api/openapi.yaml as the source of truth, preserve the NATS JetStream contract, and avoid unrelated cleanup.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Yarrow: The IsotopeGarnetModalStore empty state in projects/isotope/config/staging.toml needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"Zephyr: Incident timeline — INC-49147\n\n08:02 deploy IsotopeOspreyJobFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current IsotopeOspreyJobFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"Sequence IsotopeFernSnapshotService's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Release verification found a single stale IsotopeLumenChartService value; the cause, desired value, and affected assertion are already agreed. Change the staging timeout from 15 seconds to 30, adjust the adjacent assertion that encodes that value, and avoid unrelated formatting, renames, dependency bumps, or cleanup.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current SQLite operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"Memory attributed to IsotopeLedgerGateStore rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","lang":"en"} -{"prompt":"IsotopeCopperBridgeCoordinator: could this be clearer","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"vague-eval","lang":"en"} -{"prompt":"PM is preparing the IsotopeBirchMigratorService rollout and needs prose that works for both application developers and the operators who will carry the pager. Turn the repository behavior into a compact reference with prerequisites, request and response examples, failure semantics, a rollback note, and links to the authoritative config keys.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeBirchMigratorService\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"IsotopeVelaDrawerCoordinator: polish, then assess","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.61,"slice":"mixed","lang":"en"} -{"prompt":"Polish the IsotopeQuartzPlayerService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"One contained cleanup in projects/isotope/ui/settings/PrivacyPane.tsx: remove the obsolete IsotopeHarborIndexService import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"core","lang":"en"} -{"prompt":"Security flagged IsotopeMoonlitSDKService for a read-only pass because its WebGPU boundary mixes tenant data, retries, and cancellation in subtle ways. Trace ownership, ordering, error propagation, and cancellation; call out concrete risks with file references, but do not edit the implementation or turn the answer into a replacement design.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current WebGPU operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} +{"prompt":"Nimbus: The destination for IsotopeDeltaCanvasService is broadly agreed; the missing piece is a reversible route from projects/isotope/internal/auth/refresh.go to that target. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeDeltaCanvasService\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Any races in IsotopeSummitProxyStore?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Sketch the IsotopeQuartzPlayerStore migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Opal: Test Suite 'IsotopeRainfallDBFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[IsotopeRainfallDBFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/isotope/db/migrations/20260730_events.sql:144: error: -[IsotopeRainfallDBFlowTests testRestoresSelectionAfterBackgrounding] : XCTAssertEqual failed: (\"Optional(4)\") is not equal to (\"Optional(3)\")\nAccessibility hierarchy at failure:\n Application, 0x104c, pid: 812\n Window, identifier: \"main\"\n NavigationStack, identifier: \"catalog\"\n Button, label: \"Filters\", value: \"2 active\"\n CollectionView, identifier: \"results-grid\", rows: 24\n Sheet, identifier: \"filter-sheet\"\n TextField, label: \"Search filters\", value: \"\"\n Switch, label: \"Available offline\", value: \"1\"\n Button, label: \"Apply\", enabled: true\nTest Case '-[IsotopeRainfallDBFlowTests testRestoresSelectionAfterBackgrounding]' failed (4.812 seconds).\n\nSimulator: iPhone 17 Pro, iOS 27.0, en_US, content size XXXL, Reduce Motion enabled. The screenshot looks correct. The mismatch is the internal selected-segment index after the scene becomes active; tapping Apply a second time makes it three again.\n\nBring IsotopeRainfallDBFlow's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"diff --git a/projects/isotope/db/migrations/20260730_events.sql b/projects/isotope/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/db/migrations/20260730_events.sql\n+++ b/projects/isotope/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is IsotopeVelaDrawerFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"# projects/isotope/ml/pipeline/features.py\n[worker.isotopecinderauthcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.isotopecinderauthcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.isotopecinderauthcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.IsotopeCinderAuthCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-49157\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nThe intended correction is already known: change only the stale 15-second setting to 30 seconds in projects/isotope/ml/pipeline/features.py and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"IsotopeOspreyJobCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"IsotopeIrisBatchCoordinator: diagnose, then assess","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"What sequence would let IsotopeFlintTimelineStore adopt PostgreSQL 17 with dual reads but no dual writes? Include data validation, canary scope, and the decision that ends compatibility mode.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Prism: Two asks around IsotopeCoralUploadCoordinator: (1) lay out a staged migration for IsotopeCoralUploadCoordinator; (2) then implement the bounded durable-cursor handler. Keep the patch readable for a small on-call review, and leave a clear boundary between the resulting artifacts or edits.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Quartz: # projects/isotope/workers/thumbnail/consumer.ex\n[worker.isotopeacornwidgetflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.isotopeacornwidgetflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.isotopeacornwidgetflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.IsotopeAcornWidgetFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-49129\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Make the one confirmed configuration correction in projects/isotope/workers/thumbnail/consumer.ex. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"pasted-context","lang":"en"} +{"prompt":"Sketch the IsotopeAtlasSearchStore migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Dedupe IsotopeDriftConsoleService's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-49111\n\n08:02 deploy IsotopeBasilRunnerFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCapture the IsotopeBasilRunnerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Two deliverables are holding up IsotopeEchoRegistryCoordinator. First, lay out a staged migration for IsotopeEchoRegistryCoordinator. In the same workstream, also add the visible loading and offline states. The relevant starting point is projects/isotope/lib/codec/frame.cc, which follows Tokio conventions and currently suffers from a misleading timeout name used in five packages. Keep the patch readable for a small on-call review.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"IsotopeFrostPanelStore's openapi.yaml needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"$ pnpm test --filter IsotopeNimbusFormCoordinator\n RUN v3.2.4 /workspace/apps/console\n × IsotopeNimbusFormCoordinator > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=49153 phase=resume storedCursor=seg-0183\n session=49153 phase=fetch requestCursor=seg-0183 pageSize=200\n session=49153 phase=commit receivedCursor=seg-0184 itemCount=0\n session=49153 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Find the source of this IsotopeNimbusFormCoordinator symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"We need to move IsotopeRavenSessionFlow from the legacy store to Tokio. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"IsotopeRainfallDBCoordinator: give it a nicer flow","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Raven: Incident timeline — INC-49125\n\n08:02 deploy IsotopeOrbitSyncFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nFrom this evidence, draft consumer-facing migration guidance for IsotopeOrbitSyncFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Give IsotopeNimbusFormStore's detail pane a sticky action bar, fluid type at narrow widths, and a keyboard-safe scroll region that still works at 200% zoom.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"IsotopeHarborIndexStore's metric is misspelled as succesful_total in one declaration. Correct that literal and its exact test expectation, without renaming anything else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Sable: projects/isotope/apps/console/routes/usage.svelte の IsotopeCraneWorkspaceService で、SQLite の flow に断続的な問題が起きています。 責務を分離して重複をなくし、API、wire value、順序、観測可能な動作は変えないでください。\n\n制約:\n- SQLite を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は IsotopeCraneWorkspaceService のみ","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"} +{"prompt":"Correct the IsotopeKiteSchedulerService flag default","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump IsotopeSlateEditorService's timeout to 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating a deadlock that appears only during shutdown in IsotopeRainfallDBStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Read projects/isotope/db/migrations/20260730_events.sql and tell me whether IsotopeRainfallDBService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"IsotopeOpalRouterCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Fresh release brief for IsotopeEmberRelayCoordinator:\n- primary outcome: lay out a staged migration for IsotopeEmberRelayCoordinator\n- companion outcome: then implement the bounded durable-cursor handler\n- repository entry point: projects/isotope/Sources/App/SessionStore.swift\n- platform constraint: WebGPU\n- known complication: two validators with subtly different error strings\n\nBoth results are required, but they should remain independently reviewable. Keep the patch readable for a small on-call review; retain serialization and authorization boundaries; cover cancellation, idempotent retries, and rollback; and avoid drive-by cleanup. Use the code as the source of truth, call out assumptions, and state how an on-call engineer can tell that either part is unsafe to ship.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Check IsotopeBeaconStoreService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"IsotopeCloudReconcilerCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-49117\n\n08:02 deploy IsotopeKiteSchedulerFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCapture the IsotopeKiteSchedulerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"The public surface of IsotopeWillowCodecStore is frozen, but its internal ownership in projects/isotope/apps/console/routes/usage.svelte is difficult to test and even harder to change safely. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeWillowCodecStore\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"IsotopePineMetricsCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"In projects/isotope/config/staging.toml hat IsotopeBasilRunnerService ein sporadisches Problem im NATS JetStream-Ablauf. Verfasse eine Consumer-Doku mit Vertrag, Fehlern, Retry und einem kopierbaren Beispiel; ändere keinen Handler.\n\nRandbedingungen:\n- NATS JetStream weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf IsotopeBasilRunnerService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um IsotopeBasilRunnerService mit NATS JetStream kompatibel.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"de"} +{"prompt":"Tide: // projects/isotope/apps/console/routes/usage.svelte\nfinal class IsotopeIrisBatchFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nSplit IsotopeIrisBatchFlow by responsibility and make cancellation ownership explicit. Characterize the current sequence before moving code and keep callers unchanged.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"I inherited IsotopeKiteSchedulerStore and need a careful read of projects/isotope/cmd/exporter/main.py before I can sign off on the next release. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing WebGPU deployment\n- keep the work scoped to IsotopeKiteSchedulerStore and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.\n\nNothing is reported broken, so judge and explain current behavior without inventing a failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"The first IsotopeOspreyJobStore request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"IsotopeNovaPickerCoordinator: polish the last piece","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"diff --git a/projects/isotope/infra/modules/edge/main.tf b/projects/isotope/infra/modules/edge/main.tf\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/infra/modules/edge/main.tf\n+++ b/projects/isotope/infra/modules/edge/main.tf\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit IsotopeDeltaCanvasCoordinator by responsibility and make cancellation ownership explicit. Characterize the current sequence before moving code and keep callers unchanged.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"IsotopeJuniperCLICoordinator: sort out the rough edge","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Ownership of IsotopeEmberRelayStore is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Give me a staged design with ownership boundaries, compatibility seams, migration order, telemetry, failure drills, rollback criteria, and explicit decisions we can defer; stop before implementation.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current WebGPU operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Umbra: Incident timeline — INC-49141\n\n08:02 deploy IsotopeAsterWebhookFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current IsotopeAsterWebhookFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Our support and SDK teams keep answering the same questions about IsotopeEchoRegistryStore, but the current prose in projects/isotope/lib/codec/frame.cc only describes the happy path. Draft an ADR plus migration note that records the decision, rejected alternatives, compatibility window, observability signals, and the exact action required from consumers.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing Tokio deployment\n- keep the work scoped to IsotopeEchoRegistryStore and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"En projects/isotope/apps/console/routes/usage.svelte, IsotopeNimbusFormService tiene un problema intermitente en el flujo de SQLite. Sigue queue, scheduler y cancelación, compara hipótesis y encuentra la causa antes de proponer cambios.\n\nRestricciones:\n- seguir con SQLite\n- conservar compatibilidad y cancelación\n- limitar el cambio a IsotopeNimbusFormService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"es"} +{"prompt":"projects/isotope/web/components/FilterDrawer.vue 里的 IsotopeJuniperCLIService 最近在 PostgreSQL 17 流程中出现间歇性问题。 请完成 responsive layout、空状态、retry、键盘焦点、dark mode 和 reduced motion。\n\n约束：\n- 继续使用 PostgreSQL 17\n- 保持兼容性和取消语义\n- 改动只限于 IsotopeJuniperCLIService","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"zh"} +{"prompt":"Milestones for replacing IsotopeWrenExportStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Flip IsotopeVelaDrawerStore's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Security flagged IsotopeBirchMigratorStore for a read-only pass because its Tokio boundary mixes tenant data, retries, and cancellation in subtle ways. Trace ownership, ordering, error propagation, and cancellation; call out concrete risks with file references, but do not edit the implementation or turn the answer into a replacement design.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current Tokio operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.\n\nNothing is reported broken, so judge and explain current behavior without inventing a failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"IsotopePrismCacheCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"# CI job 49130: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: PostgreSQL 17\n\n[setup] restoring cache key deps-a2f91c ... hit\n[setup] starting postgres:17 ... healthy after 4.2s\n[setup] starting redis:8 ... healthy after 0.8s\n[test] shard 3/8 selected 412 tests\n[test] IsotopeQuartzPlayerFlowIntegration.replays_after_timeout ... ok\n[test] IsotopeQuartzPlayerFlowIntegration.cancels_orphaned_batch ... FAILED\n\nExpected:\n pending_jobs{queue=\"replay\"} 0\nActual:\n pending_jobs{queue=\"replay\"} 1\n\nCaptured spans:\n batch.receive 2.1ms status=ok\n storage.transaction 44.8ms status=cancelled\n batch.nack \n\nteardown warning: resource still in use: redis connection pool (1 borrower)\nretry 1/2 with identical seed ... passed\nretry 2/2 with identical seed ... passed\n\nThe failure began after the test suite was sharded, but it sometimes appears on an unsharded nightly run. There are no wall-clock sleeps in this test; it advances the fake scheduler until idle.\n\nDeliver the IsotopeQuartzPlayerFlow server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Vela: // projects/isotope/engine/render/atlas.cpp\nfinal class IsotopeEchoRegistryFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nWalk through what the artifact proves about IsotopeEchoRegistryFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Willow: diff --git a/projects/isotope/Sources/CLI/Commands/Doctor.swift b/projects/isotope/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/isotope/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nWire IsotopeMoonlitSDKCoordinator's schema, storage, handler, and worker path so continuation is signed, duplicate delivery is stable, and shutdown cannot acknowledge uncommitted work.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Our support and SDK teams keep answering the same questions about IsotopeGarnetModalService, but the current prose in projects/isotope/packages/api/openapi.yaml only describes the happy path. Draft an ADR plus migration note that records the decision, rejected alternatives, compatibility window, observability signals, and the exact action required from consumers.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing NATS JetStream deployment\n- keep the work scoped to IsotopeGarnetModalService and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Xylem: # projects/isotope/engine/render/atlas.cpp\n[worker.isotoperavensessioncoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.isotoperavensessioncoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.isotoperavensessioncoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.IsotopeRavenSessionCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-49154\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nThe intended correction is already known: change only the stale 15-second setting to 30 seconds in projects/isotope/engine/render/atlas.cpp and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current IsotopeMicaProfileService design actually guarantees what its callers assume. Follow one successful request and each early exit through the code, then rank findings by impact and state which apparent hazards are already ruled out by invariants.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeMicaProfileService\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"IsotopeMapleQueueCoordinator: assess, then document","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"PM needs a concise migration note for IsotopeMicaProfileStore, including the user impact, rollback trigger, and the one configuration key operators must change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"IsotopeFrostPanelCoordinator needs a paired pass: find the unknown cause of stale cursors when a page is resumed, plus capture the contract and rollback note for consumers. Use projects/isotope/packages/api/openapi.yaml as the source of truth, preserve the NATS JetStream contract, and avoid unrelated cleanup.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Yarrow: The IsotopeGarnetModalStore empty state in projects/isotope/config/staging.toml needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Zephyr: Incident timeline — INC-49147\n\n08:02 deploy IsotopeOspreyJobFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current IsotopeOspreyJobFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Sequence IsotopeFernSnapshotService's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Release verification found a single stale IsotopeLumenChartService value; the cause, desired value, and affected assertion are already agreed. Change the staging timeout from 15 seconds to 30, adjust the adjacent assertion that encodes that value, and avoid unrelated formatting, renames, dependency bumps, or cleanup.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current SQLite operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Memory attributed to IsotopeLedgerGateStore rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"IsotopeCopperBridgeCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"PM is preparing the IsotopeBirchMigratorService rollout and needs prose that works for both application developers and the operators who will carry the pager. Turn the repository behavior into a compact reference with prerequisites, request and response examples, failure semantics, a rollback note, and links to the authoritative config keys.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeBirchMigratorService\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"IsotopeVelaDrawerCoordinator: polish, then assess","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Polish the IsotopeQuartzPlayerService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"One contained cleanup in projects/isotope/ui/settings/PrivacyPane.tsx: remove the obsolete IsotopeHarborIndexService import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Security flagged IsotopeMoonlitSDKService for a read-only pass because its WebGPU boundary mixes tenant data, retries, and cancellation in subtle ways. Trace ownership, ordering, error propagation, and cancellation; call out concrete risks with file references, but do not edit the implementation or turn the answer into a replacement design.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current WebGPU operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"How does IsotopeOpalRouterService propagate cancellation through the PostgreSQL 17 boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-49110\n\n08:02 deploy IsotopeSpruceDaemonFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nReconstruct the IsotopeSpruceDaemonFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Before we approve IsotopeTideWorkerStore, assess whether an accessibility label that reads the internal enum is an actual correctness risk or merely confusing structure. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Em projects/isotope/services/ledger/replay.go, o IsotopeJuniperCLIStore tem um problema intermitente no fluxo de PostgreSQL 17. Siga queue, scheduler e cancelamento, compare hipóteses e encontre a causa antes de mudar código.\n\nRestrições:\n- continuar com PostgreSQL 17\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao IsotopeJuniperCLIStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"pt"} -{"prompt":"diff --git a/projects/isotope/pkg/cache/lease.rs b/projects/isotope/pkg/cache/lease.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/pkg/cache/lease.rs\n+++ b/projects/isotope/pkg/cache/lease.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate IsotopeMapleQueueFlow's parallel adapters behind a single internal boundary, with no changes to API, timing, serialization, metrics, or error text.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Design handed over a final pass for IsotopeSpruceDaemonService, and the basic data flow in projects/isotope/infra/modules/edge/main.tf already works. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing PostgreSQL 17 deployment\n- keep the work scoped to IsotopeSpruceDaemonService and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"For IsotopeAcornWidgetCoordinator, assess ownership and failure handling in projects/isotope/ui/settings/PrivacyPane.tsx; once that is complete, capture the contract and rollback note for consumers. Work from projects/isotope/ui/settings/PrivacyPane.tsx, stay with Tokio, and keep the patch readable for a small on-call review. Keep the two outcomes separately reviewable.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Checkout: Incident timeline — INC-49131\n\n08:02 deploy IsotopeFrostPanelFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nTurn the artifact into a reversible IsotopeFrostPanelFlow rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"IsotopeDeltaCanvasStore's staging timeout is already known to be wrong: change the single projects/isotope/infra/modules/edge/main.tf value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"core","lang":"en"} -{"prompt":"UI ticket DES-49135: finish the compact IsotopeJuniperCLIFlow filter experience\n\nRoute: /catalog/search\nSource: projects/isotope/web/components/FilterDrawer.vue\nFramework: PostgreSQL 17\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring IsotopeJuniperCLIFlow's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"pasted-context","lang":"en"} -{"prompt":"IsotopeWillowCodecCoordinator is blocking the next release because memory growth during hour-long imports. I need two concrete outcomes from a single pass: produce a consumer guide for IsotopeWillowCodecCoordinator, and give the existing implementation a read-only safety pass. Use the existing SQLite conventions in projects/isotope/apps/console/routes/usage.svelte; keep the patch readable for a small on-call review. Keep the outcomes distinct so reviewers can see which evidence supports the assessment and which files or prose satisfy the requested change.\n\nConstraints:\n- preserve public wire values and tenant boundaries\n- cover cancellation and retry behavior\n- avoid generated code and unrelated cleanup\n- include a rollback trigger that an on-call engineer can measure\n\nThis is a fresh workstream for the release, so derive everything from the repository and the context here.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.67,"slice":"mixed","lang":"en"} -{"prompt":"For IsotopeBeaconStoreCoordinator, separate IsotopeBeaconStoreCoordinator's policy from transport without behavior changes; once that is complete, give the existing implementation a read-only safety pass. Work from projects/isotope/pkg/cache/lease.rs, stay with NATS JetStream, and keep the patch readable for a small on-call review. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"# projects/isotope/ml/pipeline/features.py\n[worker.isotopecedarpolicyflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.isotopecedarpolicyflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.isotopecedarpolicyflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.IsotopeCedarPolicyFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-49137\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Align IsotopeCedarPolicyFlow's staging timeout with the shown production value and refresh only the focused config test; nothing else in the paste should move.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.38,"slice":"pasted-context","lang":"pt"} -{"prompt":"IsotopePrismCacheStore's staging timeout is already known to be wrong: change the single projects/isotope/db/migrations/20260730_events.sql value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"boundary","lang":"en"} -{"prompt":"Style IsotopeSummitProxyService's offline state","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"Drop IsotopeAmberFilterStore's unused import","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"boundary","lang":"en"} -{"prompt":"Give IsotopeAcornWidgetService a README example","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Ticket OPS-49136: retire the legacy replay path for IsotopePineMetricsFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nUsing this as the starting evidence, propose a staged IsotopePineMetricsFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"This should remain a deliberately small patch: IsotopeRavenSessionService has one known configuration mistake in projects/isotope/lib/codec/frame.cc, not an open-ended failure investigation. Correct the known literal and the test that intentionally mirrors it; the final diff should stay local enough for an on-call engineer to verify at a glance.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing Tokio deployment\n- keep the work scoped to IsotopeRavenSessionService and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-49127\n\n08:02 deploy IsotopeCoralUploadFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nTurn the material above into a concise IsotopeCoralUploadFlow release note and operator runbook section. State impact, detection, rollback, and the client-visible contract; do not modify code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.62,"slice":"pasted-context","lang":"en"} -{"prompt":"IsotopePrismCacheService has four wrappers that only translate the same error enum. Collapse them into one adapter and preserve every public case, message, and metric label.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Ticket OPS-49143: retire the legacy replay path for IsotopeCraneWorkspaceFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nAssess IsotopeCraneWorkspaceFlow for durability, tenant isolation, races, and misleading observability. Separate blockers from questions and do not produce a patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Flip IsotopeBeaconStoreStore's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"boundary","lang":"en"} -{"prompt":"The IsotopeCinderAuthStore empty state in projects/isotope/ml/pipeline/features.py needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"core","lang":"en"} -{"prompt":"IsotopeAtlasSearchCoordinator: restructure, then correct","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"diff --git a/projects/isotope/internal/auth/refresh.go b/projects/isotope/internal/auth/refresh.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/internal/auth/refresh.go\n+++ b/projects/isotope/internal/auth/refresh.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate IsotopeCopperBridgeFlow's parallel adapters behind a single internal boundary, with no changes to API, timing, serialization, metrics, or error text.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Exporter: Ticket OPS-49134: retire the legacy replay path for IsotopeLedgerGateFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for IsotopeLedgerGateFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.67,"slice":"pasted-context","lang":"en"} -{"prompt":"UI ticket DES-49149: finish the compact IsotopeSableParserFlow filter experience\n\nRoute: /catalog/search\nSource: projects/isotope/workers/thumbnail/consumer.ex\nFramework: Tokio\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nUse the UI evidence to complete IsotopeSableParserFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Scheduler: Ticket OPS-49120: retire the legacy replay path for IsotopeSummitProxyFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nCapture the IsotopeSummitProxyFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"pasted-context","lang":"en"} -{"prompt":"Is there a cleaner way to separate IsotopeSableParserStore's transport, persistence, and retry policy without changing its API or timing behavior? Go ahead and make that structural change.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Check IsotopeVelaDrawerService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Dashboard: For IsotopeSlateEditorCoordinator, change IsotopeSlateEditorCoordinator's known staging timeout from 15 to 30 seconds; once that is complete, give the existing implementation a read-only safety pass. Work from projects/isotope/Sources/App/SessionStore.swift, stay with WebGPU, and keep the patch readable for a small on-call review. Keep the two outcomes separately reviewable.","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.24,"slice":"mixed","lang":"en"} -{"prompt":"Worker: diff --git a/projects/isotope/pkg/cache/lease.rs b/projects/isotope/pkg/cache/lease.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/pkg/cache/lease.rs\n+++ b/projects/isotope/pkg/cache/lease.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit IsotopeMicaProfileCoordinator by responsibility and make cancellation ownership explicit. Characterize the current sequence before moving code and keep callers unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Our support and SDK teams keep answering the same questions about IsotopeWillowCodecService, but the current prose in projects/isotope/app/src/main/SyncWorker.kt only describes the happy path. Draft an ADR plus migration note that records the decision, rejected alternatives, compatibility window, observability signals, and the exact action required from consumers.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing SQLite deployment\n- keep the work scoped to IsotopeWillowCodecService and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"IsotopeOrbitSyncCoordinator needs a paired pass: produce a consumer guide for IsotopeOrbitSyncCoordinator, plus give the existing implementation a read-only safety pass. Use projects/isotope/web/components/FilterDrawer.vue as the source of truth, preserve the PostgreSQL 17 contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.43,"slice":"mixed","lang":"en"} -{"prompt":"Simulator: PM is preparing the IsotopeSpruceDaemonStore rollout and needs prose that works for both application developers and the operators who will carry the pager. Turn the repository behavior into a compact reference with prerequisites, request and response examples, failure semantics, a rollback note, and links to the authoritative config keys.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeSpruceDaemonStore\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.49,"slice":"boundary","lang":"en"} -{"prompt":"Responsive layout for IsotopeFrostPanelService","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"Could IsotopeCopperBridgeService show the active PostgreSQL 17 sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"Runbook: diff --git a/projects/isotope/web/components/FilterDrawer.vue b/projects/isotope/web/components/FilterDrawer.vue\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/web/components/FilterDrawer.vue\n+++ b/projects/isotope/web/components/FilterDrawer.vue\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is IsotopeDriftConsoleFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"pasted-context","lang":"en"} -{"prompt":"IsotopeMarbleTokenCoordinator: sequence, then restructure","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.82,"slice":"mixed","lang":"en"} -{"prompt":"// projects/isotope/packages/api/openapi.yaml\nfinal class IsotopeMosaicGridFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Deliver the IsotopeMosaicGridFlow server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.83,"slice":"pasted-context","lang":"de"} -{"prompt":"Trace: Ticket OPS-49119: retire the legacy replay path for IsotopeMarbleTokenFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nAssess IsotopeMarbleTokenFlow for durability, tenant isolation, races, and misleading observability. Separate blockers from questions and do not produce a patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"A copied hex color in IsotopeNimbusFormFlow lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"boundary","lang":"en"} -{"prompt":"Two deliverables are holding up IsotopeBasilRunnerCoordinator. First, separate IsotopeBasilRunnerCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/isotope/packages/api/openapi.yaml, which follows NATS JetStream conventions and currently suffers from a query plan that changes after statistics refresh. Keep the patch readable for a small on-call review.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"Profiler: Incident timeline — INC-49145\n\n08:02 deploy IsotopeOpalRouterFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Using this as the starting evidence, propose a staged IsotopeOpalRouterFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"zh"} -{"prompt":"IsotopeAsterWebhookCoordinator: take care of the warning","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"vague-eval","lang":"en"} -{"prompt":"IsotopeLumenChartFlow has four wrappers that only translate the same error enum. Collapse them into one adapter and preserve every public case, message, and metric label.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"IsotopeCoralUploadService é seguro?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"pt"} -{"prompt":"Console: // projects/isotope/config/staging.toml\nfinal class IsotopeGarnetModalCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nRestructure IsotopeGarnetModalCoordinator so duplicated normalization and shutdown ownership have one home. Preserve public behavior, wire values, logging fields, and ordering; extend characterization coverage first.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"A previously stable test around IsotopeMicaProfileFlow now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"boundary","lang":"en"} -{"prompt":"Teach IsotopeAsterWebhookService to verify signed continuation tokens, reject cross-tenant cursors, and rotate keys without invalidating tokens issued during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Workspace: projects/isotope/crates/index/src/segment.rs now contains IsotopePineMetricsStore's normalization branch three times. Consolidate it behind one private helper, keep call ordering identical, and avoid touching generated code. Please preserve behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Document IsotopeOrbitSyncStore's cancellation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"boundary","lang":"en"} -{"prompt":"Documente le contrat IsotopeCoralUploadStore","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"fr"} -{"prompt":"The first IsotopeSableParserService request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"IsotopeCedarPolicyCoordinator: clean up that old path","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"Repository: The name pendingAck means two different things across IsotopeMoonlitSDKStore's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Pipeline: // projects/isotope/web/components/FilterDrawer.vue\nfinal class IsotopeFlintTimelineCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nConsolidate IsotopeFlintTimelineCoordinator's parallel adapters behind a single internal boundary, with no changes to API, timing, serialization, metrics, or error text.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Gateway: Ticket OPS-50147: retire the legacy replay path for JunctionAmberFilterFlow\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 JunctionAmberFilterFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"Test Suite 'JunctionEchoRegistryFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[JunctionEchoRegistryFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/junction/config/staging.toml:144: error: -[JunctionEchoRegistryFlowTests 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 '-[JunctionEchoRegistryFlowTests 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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Bring JunctionEchoRegistryFlow'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.73,"slice":"pasted-context","lang":"pt"} -{"prompt":"Renderer: # projects/junction/ml/pipeline/features.py\n[worker.junctionsummitproxyflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctionsummitproxyflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctionsummitproxyflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionSummitProxyFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50143\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/junction/ml/pipeline/features.py. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.41,"slice":"pasted-context","lang":"en"} -{"prompt":"Make JunctionOpalRouterStore keyboard navigable","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} -{"prompt":"Test Suite 'JunctionCopperBridgeFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[JunctionCopperBridgeFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/junction/cmd/exporter/main.py:144: error: -[JunctionCopperBridgeFlowTests 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 '-[JunctionCopperBridgeFlowTests 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\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Bring JunctionCopperBridgeFlow'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.76,"slice":"pasted-context","lang":"es"} -{"prompt":"JunctionDriftConsoleCoordinator: why is this odd","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} -{"prompt":"# CI job 50144: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: Cloudflare Workers\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] JunctionMosaicGridFlowIntegration.replays_after_timeout ... ok\n[test] JunctionMosaicGridFlowIntegration.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 \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 JunctionMosaicGridFlow 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.91,"slice":"pasted-context","lang":"en"} -{"prompt":"Collapse the JunctionFlintTimelineService wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"JunctionMosaicGridCoordinator: check the suspicious part","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"vague-eval","lang":"en"} -{"prompt":"diff --git a/projects/junction/web/components/FilterDrawer.vue b/projects/junction/web/components/FilterDrawer.vue\nindex 62d71aa..90f3c1e 100644\n--- a/projects/junction/web/components/FilterDrawer.vue\n+++ b/projects/junction/web/components/FilterDrawer.vue\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Consolidate JunctionPrismCacheFlow'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.79,"slice":"pasted-context","lang":"de"} -{"prompt":"Summarize the JunctionTideWorkerService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"Support wants the behavior in projects/junction/services/ledger/replay.go recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"JunctionOrbitSyncCoordinator: sort out the rough edge","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"vague-eval","lang":"en"} -{"prompt":"Outline a safer JunctionOpalRouterService cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-50120\n\n08:02 deploy JunctionOspreyJobFlow 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 JunctionOspreyJobFlow 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.57,"slice":"pasted-context","lang":"en"} -{"prompt":"projects/junction/workers/thumbnail/consumer.ex 里的 JunctionEmberRelayService 最近在 Spring Boot 流程中出现间歇性问题。 请追踪 queue、scheduler 和取消路径，对比假设，先定位原因再提修改。\n\n约束：\n- 继续使用 Spring Boot\n- 保持兼容性和取消语义\n- 改动只限于 JunctionEmberRelayService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"zh"} -{"prompt":"Our support and SDK teams keep answering the same questions about JunctionHarborIndexService, but the current prose in projects/junction/crates/index/src/segment.rs only describes the happy path. 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- retain the existing CLI flags and exit codes\n- stay compatible with the existing Kafka deployment\n- keep the work scoped to JunctionHarborIndexService and its direct tests\n\nThis repository spans logistics, WebAssembly, MySQL; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Em projects/junction/ui/settings/PrivacyPane.tsx, o JunctionEmberRelayStore tem um problema intermitente no fluxo de Spring Boot. Finalize o layout responsivo, estados vazio e retry, foco por teclado, dark mode e reduced motion.\n\nRestrições:\n- continuar com Spring Boot\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao JunctionEmberRelayStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"boundary","lang":"pt"} -{"prompt":"Indexer: # projects/junction/workers/thumbnail/consumer.ex\n[worker.junctionslateeditorcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctionslateeditorcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctionslateeditorcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionSlateEditorCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50155\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/junction/workers/thumbnail/consumer.ex. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"pasted-context","lang":"en"} -{"prompt":"diff --git a/projects/junction/Sources/CLI/Commands/Doctor.swift b/projects/junction/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/junction/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/junction/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is JunctionDriftConsoleFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Apparently: A copied hex color in JunctionAtlasSearchStore lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"boundary","lang":"en"} -{"prompt":"The JunctionMosaicGridService 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.19,"slice":"core","lang":"en"} -{"prompt":"Lately: projects/junction/cmd/exporter/main.py 里的 JunctionSummitProxyStore 最近在 Kotlin coroutines 流程中出现间歇性问题。 请完成 responsive layout、空状态、retry、键盘焦点、dark mode 和 reduced motion。\n\n约束：\n- 继续使用 Kotlin coroutines\n- 保持兼容性和取消语义\n- 改动只限于 JunctionSummitProxyStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"zh"} -{"prompt":"JunctionTideWorkerCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.48,"slice":"mixed","lang":"en"} -{"prompt":"Ticket OPS-50125: retire the legacy replay path for JunctionMoonlitSDKFlow\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 JunctionMoonlitSDKFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"pasted-context","lang":"en"} -{"prompt":"JunctionJuniperCLIFlow's staging timeout is already known to be wrong: change the single projects/junction/Sources/App/SessionStore.swift value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"boundary","lang":"en"} -{"prompt":"Centre la modale JunctionNovaPickerService","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"fr"} -{"prompt":"Oddly: Test Suite 'JunctionVelaDrawerFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[JunctionVelaDrawerFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/junction/web/components/FilterDrawer.vue:144: error: -[JunctionVelaDrawerFlowTests 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 '-[JunctionVelaDrawerFlowTests 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\nFinish the visible JunctionVelaDrawerFlow 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.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Fresh release brief for JunctionRainfallDBCoordinator:\n- primary outcome: change JunctionRainfallDBCoordinator'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/junction/web/components/FilterDrawer.vue\n- platform constraint: GraphQL\n- known complication: memory growth during hour-long imports\n\nBoth results are required, but they should remain independently reviewable. Retain the existing cli flags and exit codes; 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.38,"slice":"mixed","lang":"en"} -{"prompt":"Sequence JunctionGarnetModalService's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"JunctionVelaDrawerCoordinator: the docs need something","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"vague-eval","lang":"en"} -{"prompt":"Currently: The JunctionEchoRegistryService surface in projects/junction/config/staging.toml 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.38,"slice":"core","lang":"en"} -{"prompt":"Production says JunctionCopperBridgeService is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Reconstruct the failing timeline from logs and tests, identify which invariant first breaks, and distinguish causal signals from effects or cleanup noise.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current Kotlin coroutines operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.87,"slice":"core","lang":"en"} -{"prompt":"Please turn JunctionAmberFilterService'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.38,"slice":"core","lang":"en"} -{"prompt":"JunctionAmberFilterCoordinator: make this less weird","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"vague-eval","lang":"en"} -{"prompt":"JunctionKiteSchedulerCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"vague-eval","lang":"en"} -{"prompt":"JunctionFrostPanelStore's staging timeout is already known to be wrong: change the single projects/junction/src/sync/reconcile.ts value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-49110\n\n08:02 deploy IsotopeSpruceDaemonFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nReconstruct the IsotopeSpruceDaemonFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Before we approve IsotopeTideWorkerStore, assess whether an accessibility label that reads the internal enum is an actual correctness risk or merely confusing structure. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Em projects/isotope/services/ledger/replay.go, o IsotopeJuniperCLIStore tem um problema intermitente no fluxo de PostgreSQL 17. Siga queue, scheduler e cancelamento, compare hipóteses e encontre a causa antes de mudar código.\n\nRestrições:\n- continuar com PostgreSQL 17\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao IsotopeJuniperCLIStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"pt"} +{"prompt":"diff --git a/projects/isotope/pkg/cache/lease.rs b/projects/isotope/pkg/cache/lease.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/pkg/cache/lease.rs\n+++ b/projects/isotope/pkg/cache/lease.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate IsotopeMapleQueueFlow's parallel adapters behind a single internal boundary, with no changes to API, timing, serialization, metrics, or error text.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Design handed over a final pass for IsotopeSpruceDaemonService, and the basic data flow in projects/isotope/infra/modules/edge/main.tf already works. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing PostgreSQL 17 deployment\n- keep the work scoped to IsotopeSpruceDaemonService and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"For IsotopeAcornWidgetCoordinator, assess ownership and failure handling in projects/isotope/ui/settings/PrivacyPane.tsx; once that is complete, capture the contract and rollback note for consumers. Work from projects/isotope/ui/settings/PrivacyPane.tsx, stay with Tokio, and keep the patch readable for a small on-call review. Keep the two outcomes separately reviewable.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Checkout: Incident timeline — INC-49131\n\n08:02 deploy IsotopeFrostPanelFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nTurn the artifact into a reversible IsotopeFrostPanelFlow rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"IsotopeDeltaCanvasStore's staging timeout is already known to be wrong: change the single projects/isotope/infra/modules/edge/main.tf value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-49135: finish the compact IsotopeJuniperCLIFlow filter experience\n\nRoute: /catalog/search\nSource: projects/isotope/web/components/FilterDrawer.vue\nFramework: PostgreSQL 17\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring IsotopeJuniperCLIFlow's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"IsotopeWillowCodecCoordinator is blocking the next release because memory growth during hour-long imports. I need two concrete outcomes from a single pass: produce a consumer guide for IsotopeWillowCodecCoordinator, and give the existing implementation a read-only safety pass. Use the existing SQLite conventions in projects/isotope/apps/console/routes/usage.svelte; keep the patch readable for a small on-call review. Keep the outcomes distinct so reviewers can see which evidence supports the assessment and which files or prose satisfy the requested change.\n\nConstraints:\n- preserve public wire values and tenant boundaries\n- cover cancellation and retry behavior\n- avoid generated code and unrelated cleanup\n- include a rollback trigger that an on-call engineer can measure\n\nThis is a fresh workstream for the release, so derive everything from the repository and the context here.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"For IsotopeBeaconStoreCoordinator, separate IsotopeBeaconStoreCoordinator's policy from transport without behavior changes; once that is complete, give the existing implementation a read-only safety pass. Work from projects/isotope/pkg/cache/lease.rs, stay with NATS JetStream, and keep the patch readable for a small on-call review. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"# projects/isotope/ml/pipeline/features.py\n[worker.isotopecedarpolicyflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.isotopecedarpolicyflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.isotopecedarpolicyflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.IsotopeCedarPolicyFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-49137\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Align IsotopeCedarPolicyFlow's staging timeout with the shown production value and refresh only the focused config test; nothing else in the paste should move.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"IsotopePrismCacheStore's staging timeout is already known to be wrong: change the single projects/isotope/db/migrations/20260730_events.sql value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Style IsotopeSummitProxyService's offline state","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Drop IsotopeAmberFilterStore's unused import","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Give IsotopeAcornWidgetService a README example","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-49136: retire the legacy replay path for IsotopePineMetricsFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nUsing this as the starting evidence, propose a staged IsotopePineMetricsFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"This should remain a deliberately small patch: IsotopeRavenSessionService has one known configuration mistake in projects/isotope/lib/codec/frame.cc, not an open-ended failure investigation. Correct the known literal and the test that intentionally mirrors it; the final diff should stay local enough for an on-call engineer to verify at a glance.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing Tokio deployment\n- keep the work scoped to IsotopeRavenSessionService and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-49127\n\n08:02 deploy IsotopeCoralUploadFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nTurn the material above into a concise IsotopeCoralUploadFlow release note and operator runbook section. State impact, detection, rollback, and the client-visible contract; do not modify code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} +{"prompt":"IsotopePrismCacheService has four wrappers that only translate the same error enum. Collapse them into one adapter and preserve every public case, message, and metric label.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-49143: retire the legacy replay path for IsotopeCraneWorkspaceFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nAssess IsotopeCraneWorkspaceFlow for durability, tenant isolation, races, and misleading observability. Separate blockers from questions and do not produce a patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Flip IsotopeBeaconStoreStore's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"The IsotopeCinderAuthStore empty state in projects/isotope/ml/pipeline/features.py needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"IsotopeAtlasSearchCoordinator: restructure, then correct","purpose":"refactor","secondary":"debugging","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"diff --git a/projects/isotope/internal/auth/refresh.go b/projects/isotope/internal/auth/refresh.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/internal/auth/refresh.go\n+++ b/projects/isotope/internal/auth/refresh.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate IsotopeCopperBridgeFlow's parallel adapters behind a single internal boundary, with no changes to API, timing, serialization, metrics, or error text.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Exporter: Ticket OPS-49134: retire the legacy replay path for IsotopeLedgerGateFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for IsotopeLedgerGateFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"UI ticket DES-49149: finish the compact IsotopeSableParserFlow filter experience\n\nRoute: /catalog/search\nSource: projects/isotope/workers/thumbnail/consumer.ex\nFramework: Tokio\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nUse the UI evidence to complete IsotopeSableParserFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":"debugging","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Scheduler: Ticket OPS-49120: retire the legacy replay path for IsotopeSummitProxyFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nCapture the IsotopeSummitProxyFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Is there a cleaner way to separate IsotopeSableParserStore's transport, persistence, and retry policy without changing its API or timing behavior? Go ahead and make that structural change.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Check IsotopeVelaDrawerService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Dashboard: For IsotopeSlateEditorCoordinator, change IsotopeSlateEditorCoordinator's known staging timeout from 15 to 30 seconds; once that is complete, give the existing implementation a read-only safety pass. Work from projects/isotope/Sources/App/SessionStore.swift, stay with WebGPU, and keep the patch readable for a small on-call review. Keep the two outcomes separately reviewable.","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Worker: diff --git a/projects/isotope/pkg/cache/lease.rs b/projects/isotope/pkg/cache/lease.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/pkg/cache/lease.rs\n+++ b/projects/isotope/pkg/cache/lease.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit IsotopeMicaProfileCoordinator by responsibility and make cancellation ownership explicit. Characterize the current sequence before moving code and keep callers unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Our support and SDK teams keep answering the same questions about IsotopeWillowCodecService, but the current prose in projects/isotope/app/src/main/SyncWorker.kt only describes the happy path. Draft an ADR plus migration note that records the decision, rejected alternatives, compatibility window, observability signals, and the exact action required from consumers.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing SQLite deployment\n- keep the work scoped to IsotopeWillowCodecService and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"IsotopeOrbitSyncCoordinator needs a paired pass: produce a consumer guide for IsotopeOrbitSyncCoordinator, plus give the existing implementation a read-only safety pass. Use projects/isotope/web/components/FilterDrawer.vue as the source of truth, preserve the PostgreSQL 17 contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Simulator: PM is preparing the IsotopeSpruceDaemonStore rollout and needs prose that works for both application developers and the operators who will carry the pager. Turn the repository behavior into a compact reference with prerequisites, request and response examples, failure semantics, a rollback note, and links to the authoritative config keys.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeSpruceDaemonStore\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Responsive layout for IsotopeFrostPanelService","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Could IsotopeCopperBridgeService show the active PostgreSQL 17 sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Runbook: diff --git a/projects/isotope/web/components/FilterDrawer.vue b/projects/isotope/web/components/FilterDrawer.vue\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/web/components/FilterDrawer.vue\n+++ b/projects/isotope/web/components/FilterDrawer.vue\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is IsotopeDriftConsoleFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"IsotopeMarbleTokenCoordinator: sequence, then restructure","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"// projects/isotope/packages/api/openapi.yaml\nfinal class IsotopeMosaicGridFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Deliver the IsotopeMosaicGridFlow server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Trace: Ticket OPS-49119: retire the legacy replay path for IsotopeMarbleTokenFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nAssess IsotopeMarbleTokenFlow for durability, tenant isolation, races, and misleading observability. Separate blockers from questions and do not produce a patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"A copied hex color in IsotopeNimbusFormFlow lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Two deliverables are holding up IsotopeBasilRunnerCoordinator. First, separate IsotopeBasilRunnerCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/isotope/packages/api/openapi.yaml, which follows NATS JetStream conventions and currently suffers from a query plan that changes after statistics refresh. Keep the patch readable for a small on-call review.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Profiler: Incident timeline — INC-49145\n\n08:02 deploy IsotopeOpalRouterFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Using this as the starting evidence, propose a staged IsotopeOpalRouterFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"IsotopeAsterWebhookCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"IsotopeLumenChartFlow has four wrappers that only translate the same error enum. Collapse them into one adapter and preserve every public case, message, and metric label.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"IsotopeCoralUploadService é seguro?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"pt"} +{"prompt":"Console: // projects/isotope/config/staging.toml\nfinal class IsotopeGarnetModalCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nRestructure IsotopeGarnetModalCoordinator so duplicated normalization and shutdown ownership have one home. Preserve public behavior, wire values, logging fields, and ordering; extend characterization coverage first.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"A previously stable test around IsotopeMicaProfileFlow now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Teach IsotopeAsterWebhookService to verify signed continuation tokens, reject cross-tenant cursors, and rotate keys without invalidating tokens issued during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Workspace: projects/isotope/crates/index/src/segment.rs now contains IsotopePineMetricsStore's normalization branch three times. Consolidate it behind one private helper, keep call ordering identical, and avoid touching generated code. Please preserve behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Document IsotopeOrbitSyncStore's cancellation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Documente le contrat IsotopeCoralUploadStore","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"fr"} +{"prompt":"The first IsotopeSableParserService request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"IsotopeCedarPolicyCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Repository: The name pendingAck means two different things across IsotopeMoonlitSDKStore's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Pipeline: // projects/isotope/web/components/FilterDrawer.vue\nfinal class IsotopeFlintTimelineCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nConsolidate IsotopeFlintTimelineCoordinator's parallel adapters behind a single internal boundary, with no changes to API, timing, serialization, metrics, or error text.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Gateway: Ticket OPS-50147: retire the legacy replay path for JunctionAmberFilterFlow\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 JunctionAmberFilterFlow 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":"Test Suite 'JunctionEchoRegistryFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[JunctionEchoRegistryFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/junction/config/staging.toml:144: error: -[JunctionEchoRegistryFlowTests 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 '-[JunctionEchoRegistryFlowTests 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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Bring JunctionEchoRegistryFlow'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":"debugging","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Renderer: # projects/junction/ml/pipeline/features.py\n[worker.junctionsummitproxyflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctionsummitproxyflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctionsummitproxyflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionSummitProxyFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50143\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/junction/ml/pipeline/features.py. 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":"Make JunctionOpalRouterStore keyboard navigable","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'JunctionCopperBridgeFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[JunctionCopperBridgeFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/junction/cmd/exporter/main.py:144: error: -[JunctionCopperBridgeFlowTests 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 '-[JunctionCopperBridgeFlowTests 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\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Bring JunctionCopperBridgeFlow'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":"JunctionDriftConsoleCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"# CI job 50144: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: Cloudflare Workers\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] JunctionMosaicGridFlowIntegration.replays_after_timeout ... ok\n[test] JunctionMosaicGridFlowIntegration.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 \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 JunctionMosaicGridFlow server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Collapse the JunctionFlintTimelineService wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"JunctionMosaicGridCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"diff --git a/projects/junction/web/components/FilterDrawer.vue b/projects/junction/web/components/FilterDrawer.vue\nindex 62d71aa..90f3c1e 100644\n--- a/projects/junction/web/components/FilterDrawer.vue\n+++ b/projects/junction/web/components/FilterDrawer.vue\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Consolidate JunctionPrismCacheFlow'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":"Summarize the JunctionTideWorkerService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Support wants the behavior in projects/junction/services/ledger/replay.go recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"JunctionOrbitSyncCoordinator: sort out the rough edge","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Outline a safer JunctionOpalRouterService cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-50120\n\n08:02 deploy JunctionOspreyJobFlow 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 JunctionOspreyJobFlow 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":"projects/junction/workers/thumbnail/consumer.ex 里的 JunctionEmberRelayService 最近在 Spring Boot 流程中出现间歇性问题。 请追踪 queue、scheduler 和取消路径，对比假设，先定位原因再提修改。\n\n约束：\n- 继续使用 Spring Boot\n- 保持兼容性和取消语义\n- 改动只限于 JunctionEmberRelayService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"Our support and SDK teams keep answering the same questions about JunctionHarborIndexService, but the current prose in projects/junction/crates/index/src/segment.rs only describes the happy path. 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- retain the existing CLI flags and exit codes\n- stay compatible with the existing Kafka deployment\n- keep the work scoped to JunctionHarborIndexService and its direct tests\n\nThis repository spans logistics, WebAssembly, MySQL; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Em projects/junction/ui/settings/PrivacyPane.tsx, o JunctionEmberRelayStore tem um problema intermitente no fluxo de Spring Boot. Finalize o layout responsivo, estados vazio e retry, foco por teclado, dark mode e reduced motion.\n\nRestrições:\n- continuar com Spring Boot\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao JunctionEmberRelayStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"pt"} +{"prompt":"Indexer: # projects/junction/workers/thumbnail/consumer.ex\n[worker.junctionslateeditorcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctionslateeditorcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctionslateeditorcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionSlateEditorCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50155\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/junction/workers/thumbnail/consumer.ex. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"pasted-context","lang":"en"} +{"prompt":"diff --git a/projects/junction/Sources/CLI/Commands/Doctor.swift b/projects/junction/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/junction/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/junction/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is JunctionDriftConsoleFlow'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":"Apparently: A copied hex color in JunctionAtlasSearchStore lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"The JunctionMosaicGridService 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":"Lately: projects/junction/cmd/exporter/main.py 里的 JunctionSummitProxyStore 最近在 Kotlin coroutines 流程中出现间歇性问题。 请完成 responsive layout、空状态、retry、键盘焦点、dark mode 和 reduced motion。\n\n约束：\n- 继续使用 Kotlin coroutines\n- 保持兼容性和取消语义\n- 改动只限于 JunctionSummitProxyStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"zh"} +{"prompt":"JunctionTideWorkerCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Ticket OPS-50125: retire the legacy replay path for JunctionMoonlitSDKFlow\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 JunctionMoonlitSDKFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"JunctionJuniperCLIFlow's staging timeout is already known to be wrong: change the single projects/junction/Sources/App/SessionStore.swift value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Centre la modale JunctionNovaPickerService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"fr"} +{"prompt":"Oddly: Test Suite 'JunctionVelaDrawerFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[JunctionVelaDrawerFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/junction/web/components/FilterDrawer.vue:144: error: -[JunctionVelaDrawerFlowTests 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 '-[JunctionVelaDrawerFlowTests 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\nFinish the visible JunctionVelaDrawerFlow 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":"Fresh release brief for JunctionRainfallDBCoordinator:\n- primary outcome: change JunctionRainfallDBCoordinator'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/junction/web/components/FilterDrawer.vue\n- platform constraint: GraphQL\n- known complication: memory growth during hour-long imports\n\nBoth results are required, but they should remain independently reviewable. Retain the existing cli flags and exit codes; 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.6,"slice":"mixed","lang":"en"} +{"prompt":"Sequence JunctionGarnetModalService's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"JunctionVelaDrawerCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Currently: The JunctionEchoRegistryService surface in projects/junction/config/staging.toml 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":"Production says JunctionCopperBridgeService is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Reconstruct the failing timeline from logs and tests, identify which invariant first breaks, and distinguish causal signals from effects or cleanup noise.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current Kotlin coroutines operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Please turn JunctionAmberFilterService'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":"JunctionAmberFilterCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"JunctionKiteSchedulerCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"JunctionFrostPanelStore's staging timeout is already known to be wrong: change the single projects/junction/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":"Check JunctionMoonlitSDKService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-50154\n\n08:02 deploy JunctionFrostPanelCoordinator 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 JunctionFrostPanelCoordinator rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"Ist JunctionNovaPickerStore sicher?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"de"} -{"prompt":"Today: The behavior of JunctionWrenExportService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/junction/web/components/FilterDrawer.vue. 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- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current GraphQL operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} -{"prompt":"$ pnpm test --filter JunctionGarnetModalFlow\n RUN v3.2.4 /workspace/apps/console\n × JunctionGarnetModalFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=50124 phase=resume storedCursor=seg-0183\n session=50124 phase=fetch requestCursor=seg-0183 pageSize=200\n session=50124 phase=commit receivedCursor=seg-0184 itemCount=0\n session=50124 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nReconstruct the JunctionGarnetModalFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"# projects/junction/Sources/CLI/Commands/Doctor.swift\n[worker.junctionjuniperclicoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctionjuniperclicoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctionjuniperclicoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionJuniperCLICoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50158\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/junction/Sources/CLI/Commands/Doctor.swift. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.41,"slice":"pasted-context","lang":"en"} -{"prompt":"Ticket OPS-50129: retire the legacy replay path for JunctionMicaProfileFlow\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À partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Turn the material above into a concise JunctionMicaProfileFlow 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.67,"slice":"pasted-context","lang":"fr"} -{"prompt":"Read projects/junction/db/migrations/20260730_events.sql and tell me whether JunctionBasilRunnerStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"JunctionOpalRouterCoordinator: ship, then document","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.74,"slice":"mixed","lang":"en"} -{"prompt":"UI ticket DES-50146: finish the compact JunctionIrisBatchFlow filter experience\n\nRoute: /catalog/search\nSource: projects/junction/internal/auth/refresh.go\nFramework: GraphQL\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring JunctionIrisBatchFlow'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.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Context: diff --git a/projects/junction/services/ledger/replay.go b/projects/junction/services/ledger/replay.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/junction/services/ledger/replay.go\n+++ b/projects/junction/services/ledger/replay.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit JunctionLumenChartFlow 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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"JunctionMarbleTokenCoordinator: rethink this area","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"Describe JunctionOspreyJobStore's error envelope","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"boundary","lang":"en"} -{"prompt":"The behavior of JunctionTideWorkerStore is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/junction/packages/api/openapi.yaml. 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- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current Kafka operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.54,"slice":"boundary","lang":"en"} -{"prompt":"Stream JunctionSableParserService's audit events","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"JunctionEmberRelayCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"vague-eval","lang":"en"} -{"prompt":"Is there a cleaner way to separate JunctionBeaconStoreService'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.63,"slice":"core","lang":"en"} -{"prompt":"JunctionBirchMigratorCoordinator needs a paired pass: assess ownership and failure handling in projects/junction/pkg/cache/lease.rs, plus capture the contract and rollback note for consumers. Use projects/junction/pkg/cache/lease.rs as the source of truth, preserve the Kafka contract, and avoid unrelated cleanup.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"Dedupe JunctionFlintTimelineStore's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"JunctionRavenSessionService é seguro?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"pt"} -{"prompt":"JunctionEchoRegistryCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"vague-eval","lang":"en"} -{"prompt":"Test Suite 'JunctionMapleQueueFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[JunctionMapleQueueFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/junction/app/src/main/SyncWorker.kt:144: error: -[JunctionMapleQueueFlowTests 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 '-[JunctionMapleQueueFlowTests 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 JunctionMapleQueueFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"$ pnpm test --filter JunctionTideWorkerFlow\n RUN v3.2.4 /workspace/apps/console\n × JunctionTideWorkerFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=50117 phase=resume storedCursor=seg-0183\n session=50117 phase=fetch requestCursor=seg-0183 pageSize=200\n session=50117 phase=commit receivedCursor=seg-0184 itemCount=0\n session=50117 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nDetermine why JunctionTideWorkerFlow 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.92,"slice":"pasted-context","lang":"en"} -{"prompt":"Background: Incident timeline — INC-50114\n\n08:02 deploy JunctionAsterWebhookFlow 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 JunctionAsterWebhookFlow 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.67,"slice":"pasted-context","lang":"en"} -{"prompt":"Question: Ticket OPS-50159: retire the legacy replay path for JunctionPineMetricsCoordinator\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 JunctionPineMetricsCoordinator migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"Observation: projects/junction/ml/pipeline/features.py の JunctionSummitProxyService で、Kotlin coroutines の flow に断続的な問題が起きています。 consumer 向けに contract、error、retry、コピー可能な例を含む文書を書き、handler は変更しないでください。\n\n制約:\n- Kotlin coroutines を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は JunctionSummitProxyService のみ","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"ja"} -{"prompt":"Move JunctionEchoRegistryStore'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.58,"slice":"boundary","lang":"en"} -{"prompt":"Two asks around JunctionMoonlitSDKCoordinator: (1) finish JunctionMoonlitSDKCoordinator's responsive empty and retry states; (2) correct the known stale timeout beside it. Retain the existing cli flags and exit codes, and leave a clear boundary between the resulting artifacts or edits.","purpose":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.54,"slice":"mixed","lang":"en"} -{"prompt":"Fresh release brief for JunctionAsterWebhookCoordinator:\n- primary outcome: separate JunctionAsterWebhookCoordinator's policy from transport without behavior changes\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/junction/db/migrations/20260730_events.sql\n- platform constraint: Cloudflare Workers\n- known complication: cancellation being swallowed at the repository boundary\n\nBoth results are required, but they should remain independently reviewable. Retain the existing cli flags and exit codes; 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":"refactor","secondary":"writing","mixed":true,"difficulty":0.89,"slice":"mixed","lang":"en"} -{"prompt":"Check JunctionLumenChartStore's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"Unifie les validateurs de JunctionRavenSessionStore","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"fr"} -{"prompt":"Ownership of JunctionFrostPanelService is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current Cloudflare Workers operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"core","lang":"en"} -{"prompt":"What does JunctionBirchMigratorStore own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Milestones for replacing JunctionMicaProfileService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Two deliverables are holding up JunctionCedarPolicyCoordinator. First, separate JunctionCedarPolicyCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/junction/engine/render/atlas.cpp, which follows Spring Boot conventions and currently suffers from two validators with subtly different error strings. Retain the existing cli flags and exit codes.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"JunctionSummitProxyCoordinator: ship a sensible version","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"vague-eval","lang":"en"} -{"prompt":"JunctionFernSnapshotFlow 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.55,"slice":"boundary","lang":"en"} -{"prompt":"Release verification found a single stale JunctionCedarPolicyService value; the cause, desired value, and affected assertion are already agreed. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current Spring Boot operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.25,"slice":"core","lang":"en"} -{"prompt":"The JunctionQuartzPlayerFlow surface in projects/junction/ml/pipeline/features.py is stable now; turn its edge cases into API documentation with one successful example and one cancellation example.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"boundary","lang":"en"} -{"prompt":"Constraint: Two deliverables are holding up JunctionCopperBridgeCoordinator. First, separate JunctionCopperBridgeCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/junction/ml/pipeline/features.py, which follows Kotlin coroutines conventions and currently suffers from stale cursors when a page is resumed. Retain the existing cli flags and exit codes.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.86,"slice":"mixed","lang":"en"} -{"prompt":"JunctionDeltaCanvasStore crashes after reconnect","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"JunctionDeltaCanvasCoordinator: sequence, then ship","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Decouple JunctionMoonlitSDKStore's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} +{"prompt":"Incident timeline — INC-50154\n\n08:02 deploy JunctionFrostPanelCoordinator 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 JunctionFrostPanelCoordinator 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":"Ist JunctionNovaPickerStore sicher?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"de"} +{"prompt":"Today: The behavior of JunctionWrenExportService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/junction/web/components/FilterDrawer.vue. 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- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current GraphQL operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"$ pnpm test --filter JunctionGarnetModalFlow\n RUN v3.2.4 /workspace/apps/console\n × JunctionGarnetModalFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=50124 phase=resume storedCursor=seg-0183\n session=50124 phase=fetch requestCursor=seg-0183 pageSize=200\n session=50124 phase=commit receivedCursor=seg-0184 itemCount=0\n session=50124 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nReconstruct the JunctionGarnetModalFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"# projects/junction/Sources/CLI/Commands/Doctor.swift\n[worker.junctionjuniperclicoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctionjuniperclicoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctionjuniperclicoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionJuniperCLICoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50158\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/junction/Sources/CLI/Commands/Doctor.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":"Ticket OPS-50129: retire the legacy replay path for JunctionMicaProfileFlow\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À partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Turn the material above into a concise JunctionMicaProfileFlow 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":"Read projects/junction/db/migrations/20260730_events.sql and tell me whether JunctionBasilRunnerStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"JunctionOpalRouterCoordinator: ship, then document","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"UI ticket DES-50146: finish the compact JunctionIrisBatchFlow filter experience\n\nRoute: /catalog/search\nSource: projects/junction/internal/auth/refresh.go\nFramework: GraphQL\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring JunctionIrisBatchFlow'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":"Context: diff --git a/projects/junction/services/ledger/replay.go b/projects/junction/services/ledger/replay.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/junction/services/ledger/replay.go\n+++ b/projects/junction/services/ledger/replay.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit JunctionLumenChartFlow 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":"JunctionMarbleTokenCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Describe JunctionOspreyJobStore's error envelope","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"The behavior of JunctionTideWorkerStore is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/junction/packages/api/openapi.yaml. 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- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current Kafka operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Stream JunctionSableParserService's audit events","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"JunctionEmberRelayCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Is there a cleaner way to separate JunctionBeaconStoreService'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":"JunctionBirchMigratorCoordinator needs a paired pass: assess ownership and failure handling in projects/junction/pkg/cache/lease.rs, plus capture the contract and rollback note for consumers. Use projects/junction/pkg/cache/lease.rs as the source of truth, preserve the Kafka contract, and avoid unrelated cleanup.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Dedupe JunctionFlintTimelineStore's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"JunctionRavenSessionService é seguro?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"pt"} +{"prompt":"JunctionEchoRegistryCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Test Suite 'JunctionMapleQueueFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[JunctionMapleQueueFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/junction/app/src/main/SyncWorker.kt:144: error: -[JunctionMapleQueueFlowTests 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 '-[JunctionMapleQueueFlowTests 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 JunctionMapleQueueFlow'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":"$ pnpm test --filter JunctionTideWorkerFlow\n RUN v3.2.4 /workspace/apps/console\n × JunctionTideWorkerFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=50117 phase=resume storedCursor=seg-0183\n session=50117 phase=fetch requestCursor=seg-0183 pageSize=200\n session=50117 phase=commit receivedCursor=seg-0184 itemCount=0\n session=50117 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nDetermine why JunctionTideWorkerFlow 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":"Background: Incident timeline — INC-50114\n\n08:02 deploy JunctionAsterWebhookFlow 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 JunctionAsterWebhookFlow 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":"Question: Ticket OPS-50159: retire the legacy replay path for JunctionPineMetricsCoordinator\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 JunctionPineMetricsCoordinator 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":"Observation: projects/junction/ml/pipeline/features.py の JunctionSummitProxyService で、Kotlin coroutines の flow に断続的な問題が起きています。 consumer 向けに contract、error、retry、コピー可能な例を含む文書を書き、handler は変更しないでください。\n\n制約:\n- Kotlin coroutines を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は JunctionSummitProxyService のみ","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"ja"} +{"prompt":"Move JunctionEchoRegistryStore'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.5,"slice":"core","lang":"en"} +{"prompt":"Two asks around JunctionMoonlitSDKCoordinator: (1) finish JunctionMoonlitSDKCoordinator's responsive empty and retry states; (2) correct the known stale timeout beside it. Retain the existing cli flags and exit codes, and leave a clear boundary between the resulting artifacts or edits.","purpose":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Fresh release brief for JunctionAsterWebhookCoordinator:\n- primary outcome: separate JunctionAsterWebhookCoordinator's policy from transport without behavior changes\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/junction/db/migrations/20260730_events.sql\n- platform constraint: Cloudflare Workers\n- known complication: cancellation being swallowed at the repository boundary\n\nBoth results are required, but they should remain independently reviewable. Retain the existing cli flags and exit codes; 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":"refactor","secondary":"writing","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Check JunctionLumenChartStore's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Unifie les validateurs de JunctionRavenSessionStore","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"fr"} +{"prompt":"Ownership of JunctionFrostPanelService is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current Cloudflare Workers operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"What does JunctionBirchMigratorStore own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Milestones for replacing JunctionMicaProfileService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Two deliverables are holding up JunctionCedarPolicyCoordinator. First, separate JunctionCedarPolicyCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/junction/engine/render/atlas.cpp, which follows Spring Boot conventions and currently suffers from two validators with subtly different error strings. Retain the existing cli flags and exit codes.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"JunctionSummitProxyCoordinator: ship a sensible version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"JunctionFernSnapshotFlow 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":"Release verification found a single stale JunctionCedarPolicyService value; the cause, desired value, and affected assertion are already agreed. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current Spring Boot operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"The JunctionQuartzPlayerFlow surface in projects/junction/ml/pipeline/features.py is stable now; turn its edge cases into API documentation with one successful example and one cancellation example.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Constraint: Two deliverables are holding up JunctionCopperBridgeCoordinator. First, separate JunctionCopperBridgeCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/junction/ml/pipeline/features.py, which follows Kotlin coroutines conventions and currently suffers from stale cursors when a page is resumed. Retain the existing cli flags and exit codes.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"JunctionDeltaCanvasStore crashes after reconnect","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"JunctionDeltaCanvasCoordinator: sequence, then ship","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Decouple JunctionMoonlitSDKStore's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Lay out a two-milestone strategy for eliminating a deadlock that appears only during shutdown in JunctionDriftConsoleService, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Ticket OPS-50151: retire the legacy replay path for JunctionWrenExportCoordinator\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for JunctionWrenExportCoordinator, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.59,"slice":"pasted-context","lang":"en"} -{"prompt":"Request: Two asks around JunctionLumenChartCoordinator: (1) change JunctionLumenChartCoordinator's known staging timeout from 15 to 30 seconds; (2) give the existing implementation a read-only safety pass. Retain the existing cli flags and exit codes, and leave a clear boundary between the resulting artifacts or edits.","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.22,"slice":"mixed","lang":"en"} -{"prompt":"PM needs a concise migration note for JunctionIrisBatchStore, including the user impact, rollback trigger, and the one configuration key operators must change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"Is there a cleaner way to separate JunctionPineMetricsFlow'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.63,"slice":"boundary","lang":"en"} -{"prompt":"JunctionHarborIndexCoordinator is blocking the next release because a misleading timeout name used in five packages. I need two concrete outcomes from a single pass: assess ownership and failure handling in projects/junction/pkg/cache/lease.rs, and capture the contract and rollback note for consumers. Use the existing Kafka conventions in projects/junction/pkg/cache/lease.rs; retain the existing CLI flags and exit codes. 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":"review","secondary":"writing","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"Goal: The data is already available in projects/junction/engine/render/atlas.cpp; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"boundary","lang":"en"} -{"prompt":"Symptom: The public surface of JunctionJuniperCLIService is frozen, but its internal ownership in projects/junction/Sources/App/SessionStore.swift is difficult to test and even harder to change safely. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside JunctionJuniperCLIService\n- retain the existing CLI flags and exit codes\n\nThe relevant code crosses logistics, WebAssembly, MySQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"JunctionWillowCodecCoordinator: untangle the messy bit","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"vague-eval","lang":"en"} -{"prompt":"Memory attributed to JunctionKiteSchedulerService rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"For JunctionRavenSessionCoordinator, finish JunctionRavenSessionCoordinator's responsive empty and retry states; once that is complete, capture the contract and rollback note for consumers. Work from projects/junction/config/staging.toml, stay with Kafka, and retain the existing CLI flags and exit codes. Keep the two outcomes separately reviewable.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.59,"slice":"mixed","lang":"en"} -{"prompt":"JunctionMicaProfileCoordinator needs a paired pass: change JunctionMicaProfileCoordinator's known staging timeout from 15 to 30 seconds, plus capture the contract and rollback note for consumers. Use projects/junction/app/src/main/SyncWorker.kt as the source of truth, preserve the Cloudflare Workers contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.29,"slice":"mixed","lang":"en"} -{"prompt":"Give JunctionLedgerGateStore'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.49,"slice":"core","lang":"en"} -{"prompt":"JunctionCloudReconcilerCoordinator is blocking the next release because a feature flag whose default differs between environments. I need two concrete outcomes from a single pass: find the unknown cause of a feature flag whose default differs between environments, and capture the contract and rollback note for consumers. Use the existing Spring Boot conventions in projects/junction/ui/settings/PrivacyPane.tsx; retain the existing CLI flags and exit codes. Keep the outcomes distinct so reviewers can see which evidence supports the assessment and which files or prose satisfy the requested change.\n\nConstraints:\n- preserve public wire values and tenant boundaries\n- cover cancellation and retry behavior\n- avoid generated code and unrelated cleanup\n- include a rollback trigger that an on-call engineer can measure\n\nThis is a fresh workstream for the release, so derive everything from the repository and the context here.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.89,"slice":"mixed","lang":"en"} -{"prompt":"Introduce a durable deduplication key for JunctionFernSnapshotStore events and enforce it in both the database migration and the ingestion path.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"JunctionOspreyJobCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"# projects/junction/Sources/App/SessionStore.swift\n[worker.junctionorbitsyncflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctionorbitsyncflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctionorbitsyncflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionOrbitSyncFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50148\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 JunctionOrbitSyncFlow'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.41,"slice":"pasted-context","lang":"en"} -{"prompt":"En projects/junction/web/components/FilterDrawer.vue, JunctionRainfallDBStore tiene un problema intermitente en el flujo de GraphQL. Lee el flujo actual y dime si ownership, cancelación y orden son seguros; solo necesito el análisis.\n\nRestricciones:\n- seguir con GraphQL\n- conservar compatibilidad y cancelación\n- limitar el cambio a JunctionRainfallDBStore","purpose":"review","secondary":null,"mixed":false,"difficulty":0.69,"slice":"boundary","lang":"es"} -{"prompt":"Why is JunctionDeltaCanvasService stalling?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Lay out a two-milestone strategy for eliminating a misleading timeout name used in five packages in JunctionCoralUploadStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-50151: retire the legacy replay path for JunctionWrenExportCoordinator\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for JunctionWrenExportCoordinator, 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":"Request: Two asks around JunctionLumenChartCoordinator: (1) change JunctionLumenChartCoordinator's known staging timeout from 15 to 30 seconds; (2) give the existing implementation a read-only safety pass. Retain the existing cli flags and exit codes, and leave a clear boundary between the resulting artifacts or edits.","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"PM needs a concise migration note for JunctionIrisBatchStore, 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":"Is there a cleaner way to separate JunctionPineMetricsFlow'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":"JunctionHarborIndexCoordinator is blocking the next release because a misleading timeout name used in five packages. I need two concrete outcomes from a single pass: assess ownership and failure handling in projects/junction/pkg/cache/lease.rs, and capture the contract and rollback note for consumers. Use the existing Kafka conventions in projects/junction/pkg/cache/lease.rs; retain the existing CLI flags and exit codes. 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":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Goal: The data is already available in projects/junction/engine/render/atlas.cpp; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Symptom: The public surface of JunctionJuniperCLIService is frozen, but its internal ownership in projects/junction/Sources/App/SessionStore.swift is difficult to test and even harder to change safely. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside JunctionJuniperCLIService\n- retain the existing CLI flags and exit codes\n\nThe relevant code crosses logistics, WebAssembly, MySQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"JunctionWillowCodecCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Memory attributed to JunctionKiteSchedulerService rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"For JunctionRavenSessionCoordinator, finish JunctionRavenSessionCoordinator's responsive empty and retry states; once that is complete, capture the contract and rollback note for consumers. Work from projects/junction/config/staging.toml, stay with Kafka, and retain the existing CLI flags and exit codes. Keep the two outcomes separately reviewable.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"JunctionMicaProfileCoordinator needs a paired pass: change JunctionMicaProfileCoordinator's known staging timeout from 15 to 30 seconds, plus capture the contract and rollback note for consumers. Use projects/junction/app/src/main/SyncWorker.kt as the source of truth, preserve the Cloudflare Workers contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.3,"slice":"mixed","lang":"en"} +{"prompt":"Give JunctionLedgerGateStore'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.5,"slice":"core","lang":"en"} +{"prompt":"JunctionCloudReconcilerCoordinator is blocking the next release because a feature flag whose default differs between environments. I need two concrete outcomes from a single pass: find the unknown cause of a feature flag whose default differs between environments, and capture the contract and rollback note for consumers. Use the existing Spring Boot conventions in projects/junction/ui/settings/PrivacyPane.tsx; retain the existing CLI flags and exit codes. Keep the outcomes distinct so reviewers can see which evidence supports the assessment and which files or prose satisfy the requested change.\n\nConstraints:\n- preserve public wire values and tenant boundaries\n- cover cancellation and retry behavior\n- avoid generated code and unrelated cleanup\n- include a rollback trigger that an on-call engineer can measure\n\nThis is a fresh workstream for the release, so derive everything from the repository and the context here.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Introduce a durable deduplication key for JunctionFernSnapshotStore 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":"JunctionOspreyJobCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"# projects/junction/Sources/App/SessionStore.swift\n[worker.junctionorbitsyncflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctionorbitsyncflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctionorbitsyncflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionOrbitSyncFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50148\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 JunctionOrbitSyncFlow'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":"En projects/junction/web/components/FilterDrawer.vue, JunctionRainfallDBStore tiene un problema intermitente en el flujo de GraphQL. Lee el flujo actual y dime si ownership, cancelación y orden son seguros; solo necesito el análisis.\n\nRestricciones:\n- seguir con GraphQL\n- conservar compatibilidad y cancelación\n- limitar el cambio a JunctionRainfallDBStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"es"} +{"prompt":"Why is JunctionDeltaCanvasService stalling?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating a misleading timeout name used in five packages in JunctionCoralUploadStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Headsup: Two asks around JunctionFlintTimelineCoordinator: (1) lay out a staged migration for JunctionFlintTimelineCoordinator; (2) also add the visible loading and offline states. Retain the existing cli flags and exit codes, and leave a clear boundary between the resulting artifacts or edits.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Ticket OPS-50157: retire the legacy replay path for JunctionLedgerGateCoordinator\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for JunctionLedgerGateCoordinator, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.62,"slice":"pasted-context","lang":"en"} -{"prompt":"Since the last release, JunctionCraneWorkspaceStore has shown a misleading timeout name used in five packages; nobody on the team can reproduce it reliably on a laptop. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- retain the existing CLI flags and exit codes\n- stay compatible with the existing GraphQL deployment\n- keep the work scoped to JunctionCraneWorkspaceStore and its direct tests\n\nThis repository spans logistics, WebAssembly, MySQL; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"boundary","lang":"en"} -{"prompt":"Trace JunctionBirchMigratorService's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"JunctionAtlasSearchCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"vague-eval","lang":"en"} -{"prompt":"JunctionAcornWidgetStore 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.58,"slice":"core","lang":"en"} -{"prompt":"# projects/junction/crates/index/src/segment.rs\n[worker.junctionharborindexflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctionharborindexflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctionharborindexflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionHarborIndexFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50112\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 JunctionHarborIndexFlow'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.38,"slice":"pasted-context","lang":"en"} -{"prompt":"FYI: projects/junction/engine/render/atlas.cpp has grown through several launches, and JunctionCoralUploadService now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- retain the existing CLI flags and exit codes\n- stay compatible with the existing Spring Boot deployment\n- keep the work scoped to JunctionCoralUploadService and its direct tests\n\nThis repository spans logistics, WebAssembly, MySQL; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Meanwhile: # projects/junction/lib/codec/frame.cc\n[worker.junctioncinderauthflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctioncinderauthflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctioncinderauthflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionCinderAuthFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50130\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 JunctionCinderAuthFlow'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.33,"slice":"pasted-context","lang":"en"} -{"prompt":"How does JunctionVelaDrawerStore propagate cancellation through the GraphQL boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"JunctionBasilRunnerCoordinator: take care of the warning","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"JunctionSableParserCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"A flaky failure around JunctionCloudReconcilerStore survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside JunctionCloudReconcilerStore\n- retain the existing CLI flags and exit codes\n\nThe relevant code crosses logistics, WebAssembly, MySQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.79,"slice":"boundary","lang":"en"} -{"prompt":"Drop JunctionSpruceDaemonService's unused import","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"core","lang":"en"} -{"prompt":"JunctionNimbusFormCoordinator needs a paired pass: change JunctionNimbusFormCoordinator's known staging timeout from 15 to 30 seconds, plus capture the contract and rollback note for consumers. Use projects/junction/infra/modules/edge/main.tf as the source of truth, preserve the GraphQL contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.22,"slice":"mixed","lang":"en"} -{"prompt":"Architect a gradual ownership transfer for JunctionBeaconStoreStore across two teams, including module seams, temporary interfaces, observability, handoff criteria, and rollback responsibility. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"Unify the JunctionCloudReconcilerService validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Locally: Ticket OPS-50127: retire the legacy replay path for JunctionRavenSessionFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for JunctionRavenSessionFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.62,"slice":"pasted-context","lang":"en"} -{"prompt":"Compare the old and new JunctionMapleQueueStore adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"For JunctionCinderAuthCoordinator, change JunctionCinderAuthCoordinator's known staging timeout from 15 to 30 seconds; once that is complete, capture the contract and rollback note for consumers. Work from projects/junction/engine/render/atlas.cpp, stay with Spring Boot, and retain the existing CLI flags and exit codes. Keep the two outcomes separately reviewable.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.19,"slice":"mixed","lang":"en"} -{"prompt":"The public surface of JunctionSlateEditorService is frozen, but its internal ownership in projects/junction/ui/settings/PrivacyPane.tsx is difficult to test and even harder to change safely. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside JunctionSlateEditorService\n- retain the existing CLI flags and exit codes\n\nThe relevant code crosses logistics, WebAssembly, MySQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"What does JunctionGarnetModalStore own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"JunctionMarbleTokenService needs an idempotent replay endpoint backed by Kafka; accept a cursor, cap each page at 500 items, and return a stable continuation token.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"PM is preparing the JunctionHarborIndexStore rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside JunctionHarborIndexStore\n- retain the existing CLI flags and exit codes\n\nThe relevant code crosses logistics, WebAssembly, MySQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.54,"slice":"boundary","lang":"en"} -{"prompt":"Sketch the JunctionMicaProfileStore migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"The JunctionOrbitSyncStore 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.17,"slice":"boundary","lang":"en"} -{"prompt":"Production: projects/junction/web/components/FilterDrawer.vue の JunctionWrenExportFlow で、GraphQL の flow に断続的な問題が起きています。 段階、互換性、metrics、rollback、ownership を提案し、コード変更の前で止めてください。\n\n制約:\n- GraphQL を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は JunctionWrenExportFlow のみ","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"ja"} -{"prompt":"Staging: The destination for JunctionAcornWidgetService is broadly agreed; the missing piece is a reversible route from projects/junction/pkg/cache/lease.rs to that target. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside JunctionAcornWidgetService\n- retain the existing CLI flags and exit codes\n\nThe relevant code crosses logistics, WebAssembly, MySQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.83,"slice":"core","lang":"en"} -{"prompt":"JunctionAcornWidgetFlow's staging timeout is already known to be wrong: change the single projects/junction/pkg/cache/lease.rs value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"boundary","lang":"en"} -{"prompt":"CI: For JunctionGarnetModalCoordinator, assess ownership and failure handling in projects/junction/src/sync/reconcile.ts; once that is complete, capture the contract and rollback note for consumers. Work from projects/junction/src/sync/reconcile.ts, stay with Cloudflare Workers, and retain the existing CLI flags and exit codes. Keep the two outcomes separately reviewable.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Incident timeline — INC-50150\n\n08:02 deploy JunctionCoralUploadCoordinator 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 JunctionCoralUploadCoordinator 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.57,"slice":"pasted-context","lang":"en"} -{"prompt":"diff --git a/projects/junction/cmd/exporter/main.py b/projects/junction/cmd/exporter/main.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/junction/cmd/exporter/main.py\n+++ b/projects/junction/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\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Restructure JunctionQuartzPlayerCoordinator 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.84,"slice":"pasted-context","lang":"ja"} -{"prompt":"JunctionNovaPickerCoordinator: polish, then correct","purpose":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.64,"slice":"mixed","lang":"en"} -{"prompt":"diff --git a/projects/junction/workers/thumbnail/consumer.ex b/projects/junction/workers/thumbnail/consumer.ex\nindex 62d71aa..90f3c1e 100644\n--- a/projects/junction/workers/thumbnail/consumer.ex\n+++ b/projects/junction/workers/thumbnail/consumer.ex\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 JunctionEmberRelayFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"pasted-context","lang":"en"} -{"prompt":"Ticket OPS-50111: retire the legacy replay path for JunctionRainfallDBFlow\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 JunctionRainfallDBFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"Give JunctionNimbusFormStore a README example","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} +{"prompt":"Ticket OPS-50157: retire the legacy replay path for JunctionLedgerGateCoordinator\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for JunctionLedgerGateCoordinator, 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":"Since the last release, JunctionCraneWorkspaceStore has shown a misleading timeout name used in five packages; nobody on the team can reproduce it reliably on a laptop. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- retain the existing CLI flags and exit codes\n- stay compatible with the existing GraphQL deployment\n- keep the work scoped to JunctionCraneWorkspaceStore and its direct tests\n\nThis repository spans logistics, WebAssembly, MySQL; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Trace JunctionBirchMigratorService's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"JunctionAtlasSearchCoordinator: make the api less awkward","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"JunctionAcornWidgetStore 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":"# projects/junction/crates/index/src/segment.rs\n[worker.junctionharborindexflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctionharborindexflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctionharborindexflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionHarborIndexFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50112\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 JunctionHarborIndexFlow'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":"FYI: projects/junction/engine/render/atlas.cpp has grown through several launches, and JunctionCoralUploadService now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- retain the existing CLI flags and exit codes\n- stay compatible with the existing Spring Boot deployment\n- keep the work scoped to JunctionCoralUploadService and its direct tests\n\nThis repository spans logistics, WebAssembly, MySQL; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Meanwhile: # projects/junction/lib/codec/frame.cc\n[worker.junctioncinderauthflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctioncinderauthflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctioncinderauthflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionCinderAuthFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50130\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 JunctionCinderAuthFlow'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":"How does JunctionVelaDrawerStore propagate cancellation through the GraphQL boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"JunctionBasilRunnerCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"JunctionSableParserCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"A flaky failure around JunctionCloudReconcilerStore survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside JunctionCloudReconcilerStore\n- retain the existing CLI flags and exit codes\n\nThe relevant code crosses logistics, WebAssembly, MySQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Drop JunctionSpruceDaemonService's unused import","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"JunctionNimbusFormCoordinator needs a paired pass: change JunctionNimbusFormCoordinator's known staging timeout from 15 to 30 seconds, plus capture the contract and rollback note for consumers. Use projects/junction/infra/modules/edge/main.tf as the source of truth, preserve the GraphQL contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Architect a gradual ownership transfer for JunctionBeaconStoreStore across two teams, including module seams, temporary interfaces, observability, handoff criteria, and rollback responsibility. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Unify the JunctionCloudReconcilerService validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Locally: Ticket OPS-50127: retire the legacy replay path for JunctionRavenSessionFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for JunctionRavenSessionFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"Compare the old and new JunctionMapleQueueStore 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":"For JunctionCinderAuthCoordinator, change JunctionCinderAuthCoordinator's known staging timeout from 15 to 30 seconds; once that is complete, capture the contract and rollback note for consumers. Work from projects/junction/engine/render/atlas.cpp, stay with Spring Boot, and retain the existing CLI flags and exit codes. Keep the two outcomes separately reviewable.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"The public surface of JunctionSlateEditorService is frozen, but its internal ownership in projects/junction/ui/settings/PrivacyPane.tsx is difficult to test and even harder to change safely. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside JunctionSlateEditorService\n- retain the existing CLI flags and exit codes\n\nThe relevant code crosses logistics, WebAssembly, MySQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"What does JunctionGarnetModalStore own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"JunctionMarbleTokenService needs an idempotent replay endpoint backed by Kafka; accept a cursor, cap each page at 500 items, and return a stable continuation token.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"PM is preparing the JunctionHarborIndexStore rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside JunctionHarborIndexStore\n- retain the existing CLI flags and exit codes\n\nThe relevant code crosses logistics, WebAssembly, MySQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Sketch the JunctionMicaProfileStore migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"The JunctionOrbitSyncStore 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":"Production: projects/junction/web/components/FilterDrawer.vue の JunctionWrenExportFlow で、GraphQL の flow に断続的な問題が起きています。 段階、互換性、metrics、rollback、ownership を提案し、コード変更の前で止めてください。\n\n制約:\n- GraphQL を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は JunctionWrenExportFlow のみ","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"ja"} +{"prompt":"Staging: The destination for JunctionAcornWidgetService is broadly agreed; the missing piece is a reversible route from projects/junction/pkg/cache/lease.rs to that target. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside JunctionAcornWidgetService\n- retain the existing CLI flags and exit codes\n\nThe relevant code crosses logistics, WebAssembly, MySQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"JunctionAcornWidgetFlow's staging timeout is already known to be wrong: change the single projects/junction/pkg/cache/lease.rs value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"CI: For JunctionGarnetModalCoordinator, assess ownership and failure handling in projects/junction/src/sync/reconcile.ts; once that is complete, capture the contract and rollback note for consumers. Work from projects/junction/src/sync/reconcile.ts, stay with Cloudflare Workers, and retain the existing CLI flags and exit codes. Keep the two outcomes separately reviewable.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Incident timeline — INC-50150\n\n08:02 deploy JunctionCoralUploadCoordinator 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 JunctionCoralUploadCoordinator 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":"diff --git a/projects/junction/cmd/exporter/main.py b/projects/junction/cmd/exporter/main.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/junction/cmd/exporter/main.py\n+++ b/projects/junction/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\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Restructure JunctionQuartzPlayerCoordinator 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":"JunctionNovaPickerCoordinator: polish, then correct","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"diff --git a/projects/junction/workers/thumbnail/consumer.ex b/projects/junction/workers/thumbnail/consumer.ex\nindex 62d71aa..90f3c1e 100644\n--- a/projects/junction/workers/thumbnail/consumer.ex\n+++ b/projects/junction/workers/thumbnail/consumer.ex\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 JunctionEmberRelayFlow'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":"Ticket OPS-50111: retire the legacy replay path for JunctionRainfallDBFlow\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 JunctionRainfallDBFlow 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":"Give JunctionNimbusFormStore a README example","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"Atlas: For JunctionSpruceDaemonCoordinator, separate JunctionSpruceDaemonCoordinator's policy from transport without behavior changes; once that is complete, correct the known stale timeout beside it. Work from projects/junction/ml/pipeline/features.py, stay with Kotlin coroutines, and retain the existing CLI flags and exit codes. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"En projects/junction/ml/pipeline/features.py, JunctionQuartzPlayerService tiene un problema intermitente en el flujo de Kotlin coroutines. Separa responsabilidades y elimina duplicación, conservando API, wire values, orden y comportamiento observable.\n\nRestricciones:\n- seguir con Kotlin coroutines\n- conservar compatibilidad y cancelación\n- limitar el cambio a JunctionQuartzPlayerService Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con Kotlin coroutines alrededor de JunctionQuartzPlayerService.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"es"} -{"prompt":"# CI job 50122: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: Kafka\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] JunctionSableParserFlowIntegration.replays_after_timeout ... ok\n[test] JunctionSableParserFlowIntegration.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 \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\nFind the source of this JunctionSableParserFlow 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.92,"slice":"pasted-context","lang":"en"} -{"prompt":"Split projects/junction/web/components/FilterDrawer.vue by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Does JunctionSpruceDaemonStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Dedupe JunctionAsterWebhookService's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Unify the JunctionPrismCacheStore validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Beacon: The next client release depends on a new JunctionFernSnapshotService capability in projects/junction/internal/auth/refresh.go, with GraphQL already chosen by the platform group. Implement the endpoint and durable cursor, enforce tenant authorization and idempotency, emit useful spans, cap work per request, and include focused tests for retries, cancellation, and malformed cursors.\n\nConstraints:\n- retain the existing CLI flags and exit codes\n- stay compatible with the existing GraphQL deployment\n- keep the work scoped to JunctionFernSnapshotService and its direct tests\n\nThis repository spans logistics, WebAssembly, MySQL; use its existing conventions rather than importing a new abstraction.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"JunctionPrismCacheCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.45,"slice":"mixed","lang":"en"} -{"prompt":"thread 'tokio-runtime-worker' panicked at projects/junction/app/src/main/SyncWorker.kt:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: junctionnovapickerflow::scheduler::LeaseTask::flush\n at ./projects/junction/app/src/main/SyncWorker.kt:217:18\n 4: junctionnovapickerflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nFind the source of this JunctionNovaPickerFlow 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.96,"slice":"pasted-context","lang":"en"} -{"prompt":"Cinder: Unify the JunctionLumenChartService validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Correct the JunctionCraneWorkspaceService flag default","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"core","lang":"en"} -{"prompt":"Introduce a durable deduplication key for JunctionWillowCodecStore events and enforce it in both the database migration and the ingestion path.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"projects/junction/ml/pipeline/features.py has grown through several launches, and JunctionCopperBridgeStore now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- retain the existing CLI flags and exit codes\n- stay compatible with the existing Kotlin coroutines deployment\n- keep the work scoped to JunctionCopperBridgeStore and its direct tests\n\nThis repository spans logistics, WebAssembly, MySQL; use its existing conventions rather than importing a new abstraction.\n\nThe target structure is settled; carry out the behavior-preserving edits rather than writing another strategy.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.77,"slice":"boundary","lang":"en"} -{"prompt":"Test Suite 'JunctionAtlasSearchFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[JunctionAtlasSearchFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/junction/ui/settings/PrivacyPane.tsx:144: error: -[JunctionAtlasSearchFlowTests 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 '-[JunctionAtlasSearchFlowTests 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，并明确说明证据和取舍。 Use the UI evidence to complete JunctionAtlasSearchFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"pasted-context","lang":"zh"} -{"prompt":"Please resist widening this one: JunctionPineMetricsStore works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside JunctionPineMetricsStore\n- retain the existing CLI flags and exit codes\n\nThe relevant code crosses logistics, WebAssembly, MySQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"On compact widths, JunctionKiteSchedulerStore'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.44,"slice":"boundary","lang":"en"} -{"prompt":"JunctionSlateEditorFlow returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/junction/ui/settings/PrivacyPane.tsx and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"How does JunctionAmberFilterStore propagate cancellation through the Kafka boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Compare JunctionCinderAuthService's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Animate the JunctionNimbusFormService drawer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-50116\n\n08:02 deploy JunctionCraneWorkspaceFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current JunctionCraneWorkspaceFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"UI ticket DES-50142: finish the compact JunctionMarbleTokenFlow filter experience\n\nRoute: /catalog/search\nSource: projects/junction/pkg/cache/lease.rs\nFramework: Kafka\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 JunctionMarbleTokenFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"pasted-context","lang":"en"} -{"prompt":"Delta: diff --git a/projects/junction/infra/modules/edge/main.tf b/projects/junction/infra/modules/edge/main.tf\nindex 62d71aa..90f3c1e 100644\n--- a/projects/junction/infra/modules/edge/main.tf\n+++ b/projects/junction/infra/modules/edge/main.tf\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is JunctionFernSnapshotCoordinator's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"// projects/junction/crates/index/src/segment.rs\nfinal class JunctionAcornWidgetCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 JunctionAcornWidgetCoordinator; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Before touching projects/junction/internal/auth/refresh.go, 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.65,"slice":"core","lang":"en"} -{"prompt":"JunctionBeaconStoreCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"vague-eval","lang":"en"} -{"prompt":"This should remain a deliberately small patch: JunctionCedarPolicyStore has one known configuration mistake in projects/junction/engine/render/atlas.cpp, not an open-ended failure investigation. 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- retain the existing CLI flags and exit codes\n- stay compatible with the existing Spring Boot deployment\n- keep the work scoped to JunctionCedarPolicyStore and its direct tests\n\nThis repository spans logistics, WebAssembly, MySQL; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.25,"slice":"boundary","lang":"en"} -{"prompt":"Security flagged JunctionAsterWebhookStore for a read-only pass because its Cloudflare Workers boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current Cloudflare Workers operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"boundary","lang":"en"} -{"prompt":"JunctionMapleQueueCoordinator: polish the last piece","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"Read projects/junction/infra/modules/edge/main.tf and tell me whether JunctionWillowCodecService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} +{"prompt":"En projects/junction/ml/pipeline/features.py, JunctionQuartzPlayerService tiene un problema intermitente en el flujo de Kotlin coroutines. Separa responsabilidades y elimina duplicación, conservando API, wire values, orden y comportamiento observable.\n\nRestricciones:\n- seguir con Kotlin coroutines\n- conservar compatibilidad y cancelación\n- limitar el cambio a JunctionQuartzPlayerService Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con Kotlin coroutines alrededor de JunctionQuartzPlayerService.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"es"} +{"prompt":"# CI job 50122: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: Kafka\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] JunctionSableParserFlowIntegration.replays_after_timeout ... ok\n[test] JunctionSableParserFlowIntegration.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 \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\nFind the source of this JunctionSableParserFlow 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":"Split projects/junction/web/components/FilterDrawer.vue by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Does JunctionSpruceDaemonStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Dedupe JunctionAsterWebhookService's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Unify the JunctionPrismCacheStore validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Beacon: The next client release depends on a new JunctionFernSnapshotService capability in projects/junction/internal/auth/refresh.go, with GraphQL already chosen by the platform group. Implement the endpoint and durable cursor, enforce tenant authorization and idempotency, emit useful spans, cap work per request, and include focused tests for retries, cancellation, and malformed cursors.\n\nConstraints:\n- retain the existing CLI flags and exit codes\n- stay compatible with the existing GraphQL deployment\n- keep the work scoped to JunctionFernSnapshotService and its direct tests\n\nThis repository spans logistics, WebAssembly, MySQL; use its existing conventions rather than importing a new abstraction.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"JunctionPrismCacheCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"thread 'tokio-runtime-worker' panicked at projects/junction/app/src/main/SyncWorker.kt:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: junctionnovapickerflow::scheduler::LeaseTask::flush\n at ./projects/junction/app/src/main/SyncWorker.kt:217:18\n 4: junctionnovapickerflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nFind the source of this JunctionNovaPickerFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Cinder: Unify the JunctionLumenChartService validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Correct the JunctionCraneWorkspaceService flag default","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Introduce a durable deduplication key for JunctionWillowCodecStore 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":"projects/junction/ml/pipeline/features.py has grown through several launches, and JunctionCopperBridgeStore now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- retain the existing CLI flags and exit codes\n- stay compatible with the existing Kotlin coroutines deployment\n- keep the work scoped to JunctionCopperBridgeStore and its direct tests\n\nThis repository spans logistics, WebAssembly, MySQL; use its existing conventions rather than importing a new abstraction.\n\nThe target structure is settled; carry out the behavior-preserving edits rather than writing another strategy.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'JunctionAtlasSearchFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[JunctionAtlasSearchFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/junction/ui/settings/PrivacyPane.tsx:144: error: -[JunctionAtlasSearchFlowTests 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 '-[JunctionAtlasSearchFlowTests 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，并明确说明证据和取舍。 Use the UI evidence to complete JunctionAtlasSearchFlow'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":"Please resist widening this one: JunctionPineMetricsStore works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside JunctionPineMetricsStore\n- retain the existing CLI flags and exit codes\n\nThe relevant code crosses logistics, WebAssembly, MySQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"On compact widths, JunctionKiteSchedulerStore'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.4,"slice":"core","lang":"en"} +{"prompt":"JunctionSlateEditorFlow returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/junction/ui/settings/PrivacyPane.tsx and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"How does JunctionAmberFilterStore propagate cancellation through the Kafka boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Compare JunctionCinderAuthService's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Animate the JunctionNimbusFormService drawer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-50116\n\n08:02 deploy JunctionCraneWorkspaceFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current JunctionCraneWorkspaceFlow 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":"UI ticket DES-50142: finish the compact JunctionMarbleTokenFlow filter experience\n\nRoute: /catalog/search\nSource: projects/junction/pkg/cache/lease.rs\nFramework: Kafka\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 JunctionMarbleTokenFlow'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":"Delta: diff --git a/projects/junction/infra/modules/edge/main.tf b/projects/junction/infra/modules/edge/main.tf\nindex 62d71aa..90f3c1e 100644\n--- a/projects/junction/infra/modules/edge/main.tf\n+++ b/projects/junction/infra/modules/edge/main.tf\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is JunctionFernSnapshotCoordinator'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/junction/crates/index/src/segment.rs\nfinal class JunctionAcornWidgetCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 JunctionAcornWidgetCoordinator; 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":"Before touching projects/junction/internal/auth/refresh.go, 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":"JunctionBeaconStoreCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"This should remain a deliberately small patch: JunctionCedarPolicyStore has one known configuration mistake in projects/junction/engine/render/atlas.cpp, not an open-ended failure investigation. 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- retain the existing CLI flags and exit codes\n- stay compatible with the existing Spring Boot deployment\n- keep the work scoped to JunctionCedarPolicyStore and its direct tests\n\nThis repository spans logistics, WebAssembly, MySQL; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Security flagged JunctionAsterWebhookStore for a read-only pass because its Cloudflare Workers boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current Cloudflare Workers operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL 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":"JunctionMapleQueueCoordinator: polish the last piece","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Read projects/junction/infra/modules/edge/main.tf and tell me whether JunctionWillowCodecService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"How does JunctionSlateEditorStore propagate cancellation through the Spring Boot boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Test Suite 'JunctionBeaconStoreFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[JunctionBeaconStoreFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/junction/apps/console/routes/usage.svelte:144: error: -[JunctionBeaconStoreFlowTests 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 '-[JunctionBeaconStoreFlowTests 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 JunctionBeaconStoreFlow'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.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Where did JunctionOspreyJobService's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Ember: Incident timeline — INC-50132\n\n08:02 deploy JunctionBirchMigratorFlow 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 JunctionBirchMigratorFlow 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.62,"slice":"pasted-context","lang":"en"} -{"prompt":"UI ticket DES-50134: finish the compact JunctionBasilRunnerFlow filter experience\n\nRoute: /catalog/search\nSource: projects/junction/src/sync/reconcile.ts\nFramework: Cloudflare Workers\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring JunctionBasilRunnerFlow'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.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Ticket OPS-50133: retire the legacy replay path for JunctionSpruceDaemonFlow\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 JunctionSpruceDaemonFlow 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Architect a gradual ownership transfer for JunctionMapleQueueService across two teams, including module seams, temporary interfaces, observability, handoff criteria, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Translate the JunctionPrismCacheService setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"Could the reasoning behind JunctionFrostPanelFlow's Cloudflare Workers choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"boundary","lang":"en"} -{"prompt":"Three teams extended JunctionJuniperCLIStore independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current Kotlin coroutines operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL monorepo, so keep ownership and handoff points understandable in a small review.\n\nThe target structure is settled; carry out the behavior-preserving edits rather than writing another strategy.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.77,"slice":"boundary","lang":"en"} -{"prompt":"$ pnpm test --filter JunctionCedarPolicyFlow\n RUN v3.2.4 /workspace/apps/console\n × JunctionCedarPolicyFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=50110 phase=resume storedCursor=seg-0183\n session=50110 phase=fetch requestCursor=seg-0183 pageSize=200\n session=50110 phase=commit receivedCursor=seg-0184 itemCount=0\n session=50110 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nFind the source of this JunctionCedarPolicyFlow 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.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Trace JunctionCinderAuthStore's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"The JunctionMarbleTokenStore 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.14,"slice":"boundary","lang":"en"} -{"prompt":"Release engineering needs a JunctionDriftConsoleStore changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"boundary","lang":"en"} -{"prompt":"thread 'tokio-runtime-worker' panicked at projects/junction/internal/auth/refresh.go:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: junctionnimbusformflow::scheduler::LeaseTask::flush\n at ./projects/junction/internal/auth/refresh.go:217:18\n 4: junctionnimbusformflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nDetermine why JunctionNimbusFormFlow 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.9,"slice":"pasted-context","lang":"en"} -{"prompt":"The behavior of JunctionLedgerGateService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/junction/packages/api/openapi.yaml. 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- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current Kafka operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-50140\n\n08:02 deploy JunctionKiteSchedulerFlow 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 JunctionKiteSchedulerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"pasted-context","lang":"en"} -{"prompt":"In projects/junction/services/ledger/replay.go hat JunctionRainfallDBService ein sporadisches Problem im GraphQL-Ablauf. Vervollständige Responsive Layout, Empty- und Retry-State, Tastaturfokus, Dark Mode und Reduced Motion.\n\nRandbedingungen:\n- GraphQL weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf JunctionRainfallDBService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um JunctionRainfallDBService mit GraphQL kompatibel.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"de"} -{"prompt":"JunctionCraneWorkspaceCoordinator: ship, then assess","purpose":"backendImpl","secondary":"review","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Release engineering needs a JunctionMosaicGridStore changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"boundary","lang":"en"} -{"prompt":"We need to move JunctionOrbitSyncService from the legacy store to Kotlin coroutines. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Frost: UI ticket DES-50128: finish the compact JunctionFlintTimelineFlow filter experience\n\nRoute: /catalog/search\nSource: projects/junction/Sources/App/SessionStore.swift\nFramework: Kotlin coroutines\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring JunctionFlintTimelineFlow'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.76,"slice":"pasted-context","lang":"en"} -{"prompt":"Garnet: Incident timeline — INC-50118\n\n08:02 deploy JunctionOpalRouterFlow 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 JunctionOpalRouterFlow rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"pasted-context","lang":"en"} -{"prompt":"JunctionIrisBatchCoordinator: smooth out this interaction","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"vague-eval","lang":"en"} -{"prompt":"Harbor: # projects/junction/ml/pipeline/features.py\n[worker.junctiondeltacanvasflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctiondeltacanvasflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctiondeltacanvasflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionDeltaCanvasFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50123\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/junction/ml/pipeline/features.py and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.41,"slice":"pasted-context","lang":"en"} -{"prompt":"Iris: projects/junction/apps/console/routes/usage.svelte has grown through several launches, and JunctionPineMetricsService now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- retain the existing CLI flags and exit codes\n- stay compatible with the existing Cloudflare Workers deployment\n- keep the work scoped to JunctionPineMetricsService and its direct tests\n\nThis repository spans logistics, WebAssembly, MySQL; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Compare the old and new JunctionQuartzPlayerStore adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"What sequence would let JunctionLedgerGateFlow adopt Kafka with dual reads but no dual writes? Include data validation, canary scope, and the decision that ends compatibility mode. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Two engineers disagree about whether JunctionAtlasSearchService's cache is authoritative. Walk the reads and writes in projects/junction/ui/settings/PrivacyPane.tsx and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Ticket OPS-50115: retire the legacy replay path for JunctionCloudReconcilerFlow\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 JunctionCloudReconcilerFlow 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.74,"slice":"pasted-context","lang":"en"} -{"prompt":"Split JunctionSableParserStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Juniper: The minimum supported Cloudflare Workers version in projects/junction/src/sync/reconcile.ts is one patch behind the lockfile. Align that single value and regenerate only the affected metadata.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"core","lang":"en"} -{"prompt":"diff --git a/projects/junction/infra/modules/edge/main.tf b/projects/junction/infra/modules/edge/main.tf\nindex 62d71aa..90f3c1e 100644\n--- a/projects/junction/infra/modules/edge/main.tf\n+++ b/projects/junction/infra/modules/edge/main.tf\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nWire JunctionWillowCodecFlow'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.83,"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_51155'\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_51155'::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 KeystoneBirchMigratorCoordinator 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.87,"slice":"pasted-context","lang":"en"} -{"prompt":"KeystoneSummitProxyCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.62,"slice":"mixed","lang":"en"} -{"prompt":"Read projects/keystone/engine/render/atlas.cpp and tell me whether KeystoneDeltaCanvasService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Lay out a two-milestone strategy for eliminating an empty state that flashes before cached data arrives in KeystoneLumenChartStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"// projects/keystone/ui/settings/PrivacyPane.tsx\nfinal class KeystoneFlintTimelineCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 KeystoneFlintTimelineCoordinator; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"KeystoneOspreyJobCoordinator: clean up that old path","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} -{"prompt":"KeystoneAsterWebhookCoordinator: check the suspicious part","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"vague-eval","lang":"en"} -{"prompt":"A flaky failure around KeystoneBasilRunnerService survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneBasilRunnerService\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.84,"slice":"core","lang":"en"} -{"prompt":"PM needs a concise migration note for KeystonePrismCacheStore, including the user impact, rollback trigger, and the one configuration key operators must change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"boundary","lang":"en"} -{"prompt":"KeystoneDeltaCanvasCoordinator: could this be clearer","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"vague-eval","lang":"en"} -{"prompt":"Our support and SDK teams keep answering the same questions about KeystoneBirchMigratorService, but the current prose in projects/keystone/app/src/main/SyncWorker.kt only describes the happy path. 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- keep public behavior and serialized data unchanged\n- stay compatible with the existing gRPC deployment\n- keep the work scoped to KeystoneBirchMigratorService and its direct tests\n\nSeveral teams work in this collaboration, C++, Next.js monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.49,"slice":"core","lang":"en"} -{"prompt":"Move KeystoneAmberFilterService behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"UI ticket DES-51159: finish the compact KeystoneWillowCodecCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/keystone/cmd/exporter/main.py\nFramework: FastAPI\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 KeystoneWillowCodecCoordinator's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"KeystoneBirchMigratorStore returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/keystone/apps/console/routes/usage.svelte and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Could KeystoneFernSnapshotService migrate incrementally?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"projects/keystone/pkg/cache/lease.rs has grown through several launches, and KeystoneEmberRelayService now mixes policy, transport, persistence, and metrics in one place. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing Room deployment\n- keep the work scoped to KeystoneEmberRelayService and its direct tests\n\nSeveral teams work in this collaboration, C++, Next.js monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"Two deliverables are holding up KeystoneMarbleTokenCoordinator. First, assess ownership and failure handling in projects/keystone/app/src/main/SyncWorker.kt. In the same workstream, capture the contract and rollback note for consumers. The relevant starting point is projects/keystone/app/src/main/SyncWorker.kt, which follows gRPC conventions and currently suffers from out-of-order events after consumer rebalancing. Keep public behavior and serialized data unchanged.\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":"review","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Stream KeystoneOrbitSyncService's audit events","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Extract KeystoneAcornWidgetService's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Kestrel: # projects/keystone/workers/thumbnail/consumer.ex\n[worker.keystoneorbitsyncflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystoneorbitsyncflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystoneorbitsyncflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneOrbitSyncFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51121\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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Make the one confirmed configuration correction in projects/keystone/workers/thumbnail/consumer.ex. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.36,"slice":"pasted-context","lang":"de"} -{"prompt":"Lumen: # projects/keystone/crates/index/src/segment.rs\n[worker.keystonecloudreconcilerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystonecloudreconcilerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystonecloudreconcilerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneCloudReconcilerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51138\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 KeystoneCloudReconcilerFlow'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.41,"slice":"pasted-context","lang":"en"} -{"prompt":"Please resist widening this one: KeystoneKiteSchedulerService works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneKiteSchedulerService\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"Before we approve KeystoneCopperBridgeService, assess whether a deadlock that appears only during shutdown is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"How does KeystoneCinderAuthStore propagate cancellation through the Room boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Walk through KeystoneMarbleTokenService's usage.svelte","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Sequence KeystoneJuniperCLIService's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Document KeystoneCoralUploadStore's cancellation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"boundary","lang":"en"} -{"prompt":"Maple: Two asks around KeystoneQuartzPlayerCoordinator: (1) separate KeystoneQuartzPlayerCoordinator's policy from transport without behavior changes; (2) correct the known stale timeout beside it. Keep public behavior and serialized data unchanged, and leave a clear boundary between the resulting artifacts or edits.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"Nimbus: The public surface of KeystoneFlintTimelineService is frozen, but its internal ownership in projects/keystone/workers/thumbnail/consumer.ex is difficult to test and even harder to change safely. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneFlintTimelineService\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Fresh release brief for KeystoneKiteSchedulerCoordinator:\n- primary outcome: produce a consumer guide for KeystoneKiteSchedulerCoordinator\n- companion outcome: give the existing implementation a read-only safety pass\n- repository entry point: projects/keystone/config/staging.toml\n- platform constraint: Room\n- known complication: a feature flag whose default differs between environments\n\nBoth results are required, but they should remain independently reviewable. Keep public behavior and serialized data unchanged; 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":"writing","secondary":"review","mixed":true,"difficulty":0.67,"slice":"mixed","lang":"en"} -{"prompt":"Summarize the KeystoneBeaconStoreStore changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"en"} -{"prompt":"For KeystoneAcornWidgetCoordinator, change KeystoneAcornWidgetCoordinator's known staging timeout from 15 to 30 seconds; once that is complete, capture the contract and rollback note for consumers. Work from projects/keystone/apps/console/routes/usage.svelte, stay with gRPC, and keep public behavior and serialized data unchanged. Keep the two outcomes separately reviewable.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.19,"slice":"mixed","lang":"en"} -{"prompt":"KeystoneOpalRouterCoordinator: sort out the rough edge","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"vague-eval","lang":"en"} -{"prompt":"Lay out a two-milestone strategy for eliminating a deadlock that appears only during shutdown in KeystoneRainfallDBStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"KeystoneBeaconStoreCoordinator: diagnose, then correct","purpose":"debugging","secondary":"quickFix","mixed":true,"difficulty":0.78,"slice":"mixed","lang":"en"} -{"prompt":"Sketch the KeystoneLedgerGateService migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Opal: # projects/keystone/internal/auth/refresh.go\n[worker.keystonepinemetricsflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystonepinemetricsflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystonepinemetricsflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystonePineMetricsFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51132\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 KeystonePineMetricsFlow'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.38,"slice":"pasted-context","lang":"en"} -{"prompt":"Prism: projects/keystone/apps/console/routes/usage.svelte 里的 KeystoneHarborIndexService 最近在 gRPC 流程中出现间歇性问题。 原因已经明确：只把 staging timeout 从 15 秒改成 30 秒，并调整对应 assertion。\n\n约束：\n- 继续使用 gRPC\n- 保持兼容性和取消语义\n- 改动只限于 KeystoneHarborIndexService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"core","lang":"zh"} -{"prompt":"What is the safest way to split projects/keystone/web/components/FilterDrawer.vue into independently owned modules while KeystoneGarnetModalService's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Milestones for replacing KeystoneAtlasSearchStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"KeystoneIrisBatchCoordinator: polish, then assess","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.64,"slice":"mixed","lang":"en"} -{"prompt":"Ticket OPS-51120: retire the legacy replay path for KeystoneAmberFilterFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for KeystoneAmberFilterFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"pasted-context","lang":"en"} -{"prompt":"For KeystoneSlateEditorCoordinator, produce a consumer guide for KeystoneSlateEditorCoordinator; once that is complete, give the existing implementation a read-only safety pass. Work from projects/keystone/crates/index/src/segment.rs, stay with Room, and keep public behavior and serialized data unchanged. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.51,"slice":"mixed","lang":"en"} -{"prompt":"Sketch the KeystoneVelaDrawerService migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Add a bounded KeystoneRavenSessionStore export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"UI ticket DES-51143: finish the compact KeystoneOspreyJobFlow filter experience\n\nRoute: /catalog/search\nSource: projects/keystone/config/staging.toml\nFramework: Room\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 KeystoneOspreyJobFlow 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.76,"slice":"pasted-context","lang":"en"} -{"prompt":"Before touching projects/keystone/Sources/CLI/Commands/Doctor.swift, 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.72,"slice":"core","lang":"en"} -{"prompt":"Ticket OPS-51110: retire the legacy replay path for KeystoneEchoRegistryFlow\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 KeystoneEchoRegistryFlow 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.57,"slice":"pasted-context","lang":"en"} -{"prompt":"Animate the KeystoneCedarPolicyService drawer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} -{"prompt":"KeystoneFrostPanelCoordinator needs a paired pass: assess ownership and failure handling in projects/keystone/services/ledger/replay.go, plus capture the contract and rollback note for consumers. Use projects/keystone/services/ledger/replay.go as the source of truth, preserve the Swift 6 contract, and avoid unrelated cleanup.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"Memory attributed to KeystoneCopperBridgeStore rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"boundary","lang":"en"} -{"prompt":"Incident timeline — INC-51131\n\n08:02 deploy KeystoneJuniperCLIFlow 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 KeystoneJuniperCLIFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"Quartz: // projects/keystone/internal/auth/refresh.go\nfinal class KeystoneMapleQueueFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 KeystoneMapleQueueFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"KeystoneCoralUploadCoordinator: restructure, then correct","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Security flagged KeystoneKiteSchedulerStore for a read-only pass because its Room boundary mixes tenant data, retries, and cancellation in subtle ways. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current Room operational envelope\n\nThe relevant code crosses collaboration, C++, Next.js. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"boundary","lang":"en"} -{"prompt":"KeystoneAtlasSearchService leaks tasks on shutdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Split projects/keystone/cmd/exporter/main.py by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Is KeystoneAmberFilterStore safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"KeystoneMoonlitSDKCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"vague-eval","lang":"en"} -{"prompt":"# projects/keystone/internal/auth/refresh.go\n[worker.keystonemicaprofilecoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystonemicaprofilecoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystonemicaprofilecoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneMicaProfileCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51152\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/keystone/internal/auth/refresh.go and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.38,"slice":"pasted-context","lang":"en"} -{"prompt":"Raven: Ticket OPS-51116: retire the legacy replay path for KeystoneSummitProxyFlow\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 KeystoneSummitProxyFlow 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.59,"slice":"pasted-context","lang":"en"} -{"prompt":"KeystoneWillowCodecFlow returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/keystone/ml/pipeline/features.py and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","lang":"en"} -{"prompt":"On compact widths, KeystoneMicaProfileStore'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.49,"slice":"core","lang":"en"} -{"prompt":"Sable: Ticket OPS-51156: retire the legacy replay path for KeystoneSpruceDaemonCoordinator\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\nWire KeystoneSpruceDaemonCoordinator'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.83,"slice":"pasted-context","lang":"en"} -{"prompt":"One contained cleanup in projects/keystone/workers/thumbnail/consumer.ex: remove the obsolete KeystoneOpalRouterService import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"core","lang":"en"} -{"prompt":"UI ticket DES-51135: finish the compact KeystoneHarborIndexFlow filter experience\n\nRoute: /catalog/search\nSource: projects/keystone/apps/console/routes/usage.svelte\nFramework: gRPC\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 KeystoneHarborIndexFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"pasted-context","lang":"en"} -{"prompt":"Move KeystoneGarnetModalStore's clock and ID generation behind the existing environment type so tests no longer reach global state; outputs and scheduling order must stay identical. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"diff --git a/projects/keystone/engine/render/atlas.cpp b/projects/keystone/engine/render/atlas.cpp\nindex 62d71aa..90f3c1e 100644\n--- a/projects/keystone/engine/render/atlas.cpp\n+++ b/projects/keystone/engine/render/atlas.cpp\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure KeystoneDeltaCanvasFlow 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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"The behavior of KeystoneWillowCodecService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/keystone/ml/pipeline/features.py. 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- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current FastAPI operational envelope\n\nThe relevant code crosses collaboration, C++, Next.js. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Bring KeystoneFlintTimelineStore'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.46,"slice":"core","lang":"en"} -{"prompt":"The destination for KeystoneLumenChartService is broadly agreed; the missing piece is a reversible route from projects/keystone/Sources/CLI/Commands/Doctor.swift to that target. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneLumenChartService\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"core","lang":"en"} -{"prompt":"KeystoneCopperBridgeCoordinator: ship a sensible version","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"vague-eval","lang":"en"} -{"prompt":"KeystoneSableParserCoordinator: handle the lingering thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"vague-eval","lang":"en"} -{"prompt":"Tide: The destination for KeystoneEmberRelayStore is broadly agreed; the missing piece is a reversible route from projects/keystone/crates/index/src/segment.rs to that target. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneEmberRelayStore\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"boundary","lang":"en"} -{"prompt":"Two asks around KeystonePineMetricsCoordinator: (1) finish KeystonePineMetricsCoordinator's responsive empty and retry states; (2) capture the contract and rollback note for consumers. Keep public behavior and serialized data unchanged, and leave a clear boundary between the resulting artifacts or edits.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.59,"slice":"mixed","lang":"en"} -{"prompt":"Test Suite 'KeystoneMoonlitSDKFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[KeystoneMoonlitSDKFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/keystone/pkg/cache/lease.rs:144: error: -[KeystoneMoonlitSDKFlowTests 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 '-[KeystoneMoonlitSDKFlowTests 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 KeystoneMoonlitSDKFlow'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.76,"slice":"pasted-context","lang":"en"} -{"prompt":"Documente le contrat KeystoneFrostPanelStore","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"fr"} -{"prompt":"What sequence would let KeystoneSableParserService adopt gRPC 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.62,"slice":"core","lang":"en"} -{"prompt":"Walk through KeystoneFernSnapshotStore's main.py","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Does KeystoneQuartzPlayerService preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Teach KeystoneCinderAuthFlow to verify signed continuation tokens, reject cross-tenant cursors, and rotate keys without invalidating tokens issued during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"Memory attributed to KeystoneLumenChartFlow rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","lang":"en"} -{"prompt":"// projects/keystone/web/components/FilterDrawer.vue\nfinal class KeystoneFrostPanelFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 KeystoneFrostPanelFlow 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Three teams extended KeystoneEchoRegistryStore independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current gRPC operational envelope\n\nThe relevant code crosses collaboration, C++, Next.js. Prefer evidence from the repository and make any assumption explicit.\n\nThe individual edits look tiny, but the semantic cleanup spans the repository and must preserve behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.69,"slice":"boundary","lang":"en"} -{"prompt":"Three teams extended KeystoneSpruceDaemonService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current OpenTelemetry operational envelope\n\nThe relevant code crosses collaboration, C++, Next.js. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"KeystoneRainfallDBService's staging timeout is already known to be wrong: change the single projects/keystone/Sources/App/SessionStore.swift value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"core","lang":"en"} -{"prompt":"KeystoneSlateEditorService flakes under UTC","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"2026-07-30T08:14:11.409Z level=info service=keystonemosaicgridflow pod=keystonemosaicgridflow-7cf8 request_id=51117 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=keystonemosaicgridflow request_id=51117 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=keystonemosaicgridflow request_id=51117 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=keystonemosaicgridflow request_id=51117 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=keystonemosaicgridflow request_id=51117 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=keystonemosaicgridflow request_id=51117 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=keystonemosaicgridflow request_id=51117 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=keystonemosaicgridflow request_id=51117 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nReconstruct the KeystoneMosaicGridFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.92,"slice":"pasted-context","lang":"en"} -{"prompt":"KeystoneNovaPickerCoordinator: something is off here","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"vague-eval","lang":"en"} -{"prompt":"Incident timeline — INC-51119\n\n08:02 deploy KeystoneIrisBatchFlow 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 KeystoneIrisBatchFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"Umbra: // projects/keystone/ui/settings/PrivacyPane.tsx\nfinal class KeystoneDriftConsoleFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 KeystoneDriftConsoleFlow'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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Zentriere das KeystoneIrisBatchStore-Modal","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"boundary","lang":"de"} -{"prompt":"KeystonePrismCacheCoordinator: give it a nicer flow","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"Vela: # projects/keystone/services/ledger/replay.go\n[worker.keystonebasilrunnercoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystonebasilrunnercoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystonebasilrunnercoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneBasilRunnerCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51157\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/keystone/services/ledger/replay.go. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.38,"slice":"pasted-context","lang":"en"} -{"prompt":"Willow: # projects/keystone/app/src/main/SyncWorker.kt\n[worker.keystoneacornwidgetflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystoneacornwidgetflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystoneacornwidgetflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneAcornWidgetFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51125\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/keystone/app/src/main/SyncWorker.kt and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"pasted-context","lang":"en"} -{"prompt":"KeystoneAtlasSearchCoordinator: diagnose, then assess","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"Fresh release brief for KeystoneEchoRegistryCoordinator:\n- primary outcome: separate KeystoneEchoRegistryCoordinator's policy from transport without behavior changes\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/keystone/src/sync/reconcile.ts\n- platform constraint: gRPC\n- known complication: a misleading timeout name used in five packages\n\nBoth results are required, but they should remain independently reviewable. Keep public behavior and serialized data unchanged; 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":"refactor","secondary":"writing","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"UI ticket DES-51149: finish the compact KeystoneNimbusFormFlow filter experience\n\nRoute: /catalog/search\nSource: projects/keystone/ml/pipeline/features.py\nFramework: FastAPI\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 KeystoneNimbusFormFlow 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.78,"slice":"pasted-context","lang":"en"} -{"prompt":"How does KeystoneSableParserStore propagate cancellation through the gRPC boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Two asks around KeystoneFernSnapshotCoordinator: (1) find the unknown cause of a feature flag whose default differs between environments; (2) capture the contract and rollback note for consumers. Keep public behavior and serialized data unchanged, and leave a clear boundary between the resulting artifacts or edits.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.83,"slice":"mixed","lang":"en"} -{"prompt":"A flaky failure around KeystoneVelaDrawerStore survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneVelaDrawerStore\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.89,"slice":"boundary","lang":"en"} -{"prompt":"Add a bounded KeystoneCloudReconcilerService export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Ownership of KeystoneRavenSessionService is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current gRPC operational envelope\n\nThe relevant code crosses collaboration, C++, Next.js. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Support wants the behavior in projects/keystone/ml/pipeline/features.py recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Style KeystonePineMetricsStore's offline state","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"boundary","lang":"en"} -{"prompt":"Documente o contrato de KeystoneFrostPanelService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"pt"} -{"prompt":"Ticket OPS-51154: retire the legacy replay path for KeystoneLumenChartCoordinator\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 KeystoneLumenChartCoordinator behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"Xylem: UI ticket DES-51133: finish the compact KeystoneCedarPolicyFlow filter experience\n\nRoute: /catalog/search\nSource: projects/keystone/packages/api/openapi.yaml\nFramework: Room\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring KeystoneCedarPolicyFlow'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.76,"slice":"pasted-context","lang":"en"} -{"prompt":"KeystoneNovaPickerStore has four wrappers that only translate the same error enum. Collapse them into one adapter and preserve every public case, message, and metric label. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} +{"prompt":"Test Suite 'JunctionBeaconStoreFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[JunctionBeaconStoreFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/junction/apps/console/routes/usage.svelte:144: error: -[JunctionBeaconStoreFlowTests 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 '-[JunctionBeaconStoreFlowTests 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 JunctionBeaconStoreFlow'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":"Where did JunctionOspreyJobService's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Ember: Incident timeline — INC-50132\n\n08:02 deploy JunctionBirchMigratorFlow 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 JunctionBirchMigratorFlow 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":"UI ticket DES-50134: finish the compact JunctionBasilRunnerFlow filter experience\n\nRoute: /catalog/search\nSource: projects/junction/src/sync/reconcile.ts\nFramework: Cloudflare Workers\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring JunctionBasilRunnerFlow'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":"Ticket OPS-50133: retire the legacy replay path for JunctionSpruceDaemonFlow\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 JunctionSpruceDaemonFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Architect a gradual ownership transfer for JunctionMapleQueueService 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":"Translate the JunctionPrismCacheService setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Could the reasoning behind JunctionFrostPanelFlow's Cloudflare Workers choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Three teams extended JunctionJuniperCLIStore independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current Kotlin coroutines operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL monorepo, so keep ownership and handoff points understandable in a small review.\n\nThe target structure is settled; carry out the behavior-preserving edits rather than writing another strategy.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"$ pnpm test --filter JunctionCedarPolicyFlow\n RUN v3.2.4 /workspace/apps/console\n × JunctionCedarPolicyFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=50110 phase=resume storedCursor=seg-0183\n session=50110 phase=fetch requestCursor=seg-0183 pageSize=200\n session=50110 phase=commit receivedCursor=seg-0184 itemCount=0\n session=50110 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nFind the source of this JunctionCedarPolicyFlow 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":"Trace JunctionCinderAuthStore's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"The JunctionMarbleTokenStore 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":"Release engineering needs a JunctionDriftConsoleStore 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":"thread 'tokio-runtime-worker' panicked at projects/junction/internal/auth/refresh.go:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: junctionnimbusformflow::scheduler::LeaseTask::flush\n at ./projects/junction/internal/auth/refresh.go:217:18\n 4: junctionnimbusformflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nDetermine why JunctionNimbusFormFlow 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":"The behavior of JunctionLedgerGateService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/junction/packages/api/openapi.yaml. 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- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current Kafka operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-50140\n\n08:02 deploy JunctionKiteSchedulerFlow 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 JunctionKiteSchedulerFlow 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":"In projects/junction/services/ledger/replay.go hat JunctionRainfallDBService ein sporadisches Problem im GraphQL-Ablauf. Vervollständige Responsive Layout, Empty- und Retry-State, Tastaturfokus, Dark Mode und Reduced Motion.\n\nRandbedingungen:\n- GraphQL weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf JunctionRainfallDBService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um JunctionRainfallDBService mit GraphQL kompatibel.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"de"} +{"prompt":"JunctionCraneWorkspaceCoordinator: ship, then assess","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Release engineering needs a JunctionMosaicGridStore 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":"We need to move JunctionOrbitSyncService from the legacy store to Kotlin coroutines. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Frost: UI ticket DES-50128: finish the compact JunctionFlintTimelineFlow filter experience\n\nRoute: /catalog/search\nSource: projects/junction/Sources/App/SessionStore.swift\nFramework: Kotlin coroutines\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring JunctionFlintTimelineFlow'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":"Garnet: Incident timeline — INC-50118\n\n08:02 deploy JunctionOpalRouterFlow 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 JunctionOpalRouterFlow 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":"JunctionIrisBatchCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Harbor: # projects/junction/ml/pipeline/features.py\n[worker.junctiondeltacanvasflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctiondeltacanvasflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctiondeltacanvasflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionDeltaCanvasFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50123\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/junction/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":"Iris: projects/junction/apps/console/routes/usage.svelte has grown through several launches, and JunctionPineMetricsService now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- retain the existing CLI flags and exit codes\n- stay compatible with the existing Cloudflare Workers deployment\n- keep the work scoped to JunctionPineMetricsService and its direct tests\n\nThis repository spans logistics, WebAssembly, MySQL; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Compare the old and new JunctionQuartzPlayerStore 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":"What sequence would let JunctionLedgerGateFlow adopt Kafka with dual reads but no dual writes? Include data validation, canary scope, and the decision that ends compatibility mode. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Two engineers disagree about whether JunctionAtlasSearchService's cache is authoritative. Walk the reads and writes in projects/junction/ui/settings/PrivacyPane.tsx and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-50115: retire the legacy replay path for JunctionCloudReconcilerFlow\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 JunctionCloudReconcilerFlow 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":"Split JunctionSableParserStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Juniper: The minimum supported Cloudflare Workers version in projects/junction/src/sync/reconcile.ts 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":"diff --git a/projects/junction/infra/modules/edge/main.tf b/projects/junction/infra/modules/edge/main.tf\nindex 62d71aa..90f3c1e 100644\n--- a/projects/junction/infra/modules/edge/main.tf\n+++ b/projects/junction/infra/modules/edge/main.tf\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nWire JunctionWillowCodecFlow'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.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_51155'\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_51155'::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 KeystoneBirchMigratorCoordinator 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":"KeystoneSummitProxyCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Read projects/keystone/engine/render/atlas.cpp and tell me whether KeystoneDeltaCanvasService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating an empty state that flashes before cached data arrives in KeystoneLumenChartStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"// projects/keystone/ui/settings/PrivacyPane.tsx\nfinal class KeystoneFlintTimelineCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 KeystoneFlintTimelineCoordinator; 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":"KeystoneOspreyJobCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"KeystoneAsterWebhookCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"A flaky failure around KeystoneBasilRunnerService survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneBasilRunnerService\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":"planning","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"PM needs a concise migration note for KeystonePrismCacheStore, 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":"KeystoneDeltaCanvasCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Our support and SDK teams keep answering the same questions about KeystoneBirchMigratorService, but the current prose in projects/keystone/app/src/main/SyncWorker.kt only describes the happy path. 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- keep public behavior and serialized data unchanged\n- stay compatible with the existing gRPC deployment\n- keep the work scoped to KeystoneBirchMigratorService and its direct tests\n\nSeveral teams work in this collaboration, C++, Next.js monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Move KeystoneAmberFilterService behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"UI ticket DES-51159: finish the compact KeystoneWillowCodecCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/keystone/cmd/exporter/main.py\nFramework: FastAPI\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 KeystoneWillowCodecCoordinator'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":"KeystoneBirchMigratorStore returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/keystone/apps/console/routes/usage.svelte and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Could KeystoneFernSnapshotService migrate incrementally?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"projects/keystone/pkg/cache/lease.rs has grown through several launches, and KeystoneEmberRelayService now mixes policy, transport, persistence, and metrics in one place. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing Room deployment\n- keep the work scoped to KeystoneEmberRelayService and its direct tests\n\nSeveral teams work in this collaboration, C++, Next.js monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Two deliverables are holding up KeystoneMarbleTokenCoordinator. First, assess ownership and failure handling in projects/keystone/app/src/main/SyncWorker.kt. In the same workstream, capture the contract and rollback note for consumers. The relevant starting point is projects/keystone/app/src/main/SyncWorker.kt, which follows gRPC conventions and currently suffers from out-of-order events after consumer rebalancing. Keep public behavior and serialized data unchanged.\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":"review","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Stream KeystoneOrbitSyncService's audit events","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Extract KeystoneAcornWidgetService's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Kestrel: # projects/keystone/workers/thumbnail/consumer.ex\n[worker.keystoneorbitsyncflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystoneorbitsyncflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystoneorbitsyncflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneOrbitSyncFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51121\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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Make the one confirmed configuration correction in projects/keystone/workers/thumbnail/consumer.ex. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Lumen: # projects/keystone/crates/index/src/segment.rs\n[worker.keystonecloudreconcilerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystonecloudreconcilerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystonecloudreconcilerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneCloudReconcilerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51138\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 KeystoneCloudReconcilerFlow'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":"Please resist widening this one: KeystoneKiteSchedulerService works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneKiteSchedulerService\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Before we approve KeystoneCopperBridgeService, assess whether a deadlock that appears only during shutdown is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"How does KeystoneCinderAuthStore propagate cancellation through the Room boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Walk through KeystoneMarbleTokenService's usage.svelte","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Sequence KeystoneJuniperCLIService's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Document KeystoneCoralUploadStore's cancellation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Maple: Two asks around KeystoneQuartzPlayerCoordinator: (1) separate KeystoneQuartzPlayerCoordinator's policy from transport without behavior changes; (2) correct the known stale timeout beside it. Keep public behavior and serialized data unchanged, and leave a clear boundary between the resulting artifacts or edits.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Nimbus: The public surface of KeystoneFlintTimelineService is frozen, but its internal ownership in projects/keystone/workers/thumbnail/consumer.ex is difficult to test and even harder to change safely. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneFlintTimelineService\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Fresh release brief for KeystoneKiteSchedulerCoordinator:\n- primary outcome: produce a consumer guide for KeystoneKiteSchedulerCoordinator\n- companion outcome: give the existing implementation a read-only safety pass\n- repository entry point: projects/keystone/config/staging.toml\n- platform constraint: Room\n- known complication: a feature flag whose default differs between environments\n\nBoth results are required, but they should remain independently reviewable. Keep public behavior and serialized data unchanged; 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":"writing","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Summarize the KeystoneBeaconStoreStore changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"For KeystoneAcornWidgetCoordinator, change KeystoneAcornWidgetCoordinator's known staging timeout from 15 to 30 seconds; once that is complete, capture the contract and rollback note for consumers. Work from projects/keystone/apps/console/routes/usage.svelte, stay with gRPC, and keep public behavior and serialized data unchanged. Keep the two outcomes separately reviewable.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"KeystoneOpalRouterCoordinator: sort out the rough edge","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating a deadlock that appears only during shutdown in KeystoneRainfallDBStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"KeystoneBeaconStoreCoordinator: diagnose, then correct","purpose":"debugging","secondary":"quickFix","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Sketch the KeystoneLedgerGateService migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Opal: # projects/keystone/internal/auth/refresh.go\n[worker.keystonepinemetricsflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystonepinemetricsflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystonepinemetricsflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystonePineMetricsFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51132\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 KeystonePineMetricsFlow'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":"Prism: projects/keystone/apps/console/routes/usage.svelte 里的 KeystoneHarborIndexService 最近在 gRPC 流程中出现间歇性问题。 原因已经明确：只把 staging timeout 从 15 秒改成 30 秒，并调整对应 assertion。\n\n约束：\n- 继续使用 gRPC\n- 保持兼容性和取消语义\n- 改动只限于 KeystoneHarborIndexService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"zh"} +{"prompt":"What is the safest way to split projects/keystone/web/components/FilterDrawer.vue into independently owned modules while KeystoneGarnetModalService's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Milestones for replacing KeystoneAtlasSearchStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"KeystoneIrisBatchCoordinator: polish, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Ticket OPS-51120: retire the legacy replay path for KeystoneAmberFilterFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for KeystoneAmberFilterFlow, 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":"For KeystoneSlateEditorCoordinator, produce a consumer guide for KeystoneSlateEditorCoordinator; once that is complete, give the existing implementation a read-only safety pass. Work from projects/keystone/crates/index/src/segment.rs, stay with Room, and keep public behavior and serialized data unchanged. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Sketch the KeystoneVelaDrawerService migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add a bounded KeystoneRavenSessionStore export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-51143: finish the compact KeystoneOspreyJobFlow filter experience\n\nRoute: /catalog/search\nSource: projects/keystone/config/staging.toml\nFramework: Room\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 KeystoneOspreyJobFlow 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":"Before touching projects/keystone/Sources/CLI/Commands/Doctor.swift, 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":"Ticket OPS-51110: retire the legacy replay path for KeystoneEchoRegistryFlow\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 KeystoneEchoRegistryFlow 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":"Animate the KeystoneCedarPolicyService drawer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"KeystoneFrostPanelCoordinator needs a paired pass: assess ownership and failure handling in projects/keystone/services/ledger/replay.go, plus capture the contract and rollback note for consumers. Use projects/keystone/services/ledger/replay.go as the source of truth, preserve the Swift 6 contract, and avoid unrelated cleanup.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Memory attributed to KeystoneCopperBridgeStore rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-51131\n\n08:02 deploy KeystoneJuniperCLIFlow 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 KeystoneJuniperCLIFlow 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":"Quartz: // projects/keystone/internal/auth/refresh.go\nfinal class KeystoneMapleQueueFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 KeystoneMapleQueueFlow; 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":"KeystoneCoralUploadCoordinator: restructure, then correct","purpose":"refactor","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Security flagged KeystoneKiteSchedulerStore for a read-only pass because its Room boundary mixes tenant data, retries, and cancellation in subtle ways. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current Room operational envelope\n\nThe relevant code crosses collaboration, C++, Next.js. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"KeystoneAtlasSearchService leaks tasks on shutdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Split projects/keystone/cmd/exporter/main.py by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Is KeystoneAmberFilterStore safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"KeystoneMoonlitSDKCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"# projects/keystone/internal/auth/refresh.go\n[worker.keystonemicaprofilecoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystonemicaprofilecoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystonemicaprofilecoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneMicaProfileCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51152\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/keystone/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":"Raven: Ticket OPS-51116: retire the legacy replay path for KeystoneSummitProxyFlow\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 KeystoneSummitProxyFlow 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":"KeystoneWillowCodecFlow returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/keystone/ml/pipeline/features.py and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"On compact widths, KeystoneMicaProfileStore'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":"Sable: Ticket OPS-51156: retire the legacy replay path for KeystoneSpruceDaemonCoordinator\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\nWire KeystoneSpruceDaemonCoordinator'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.8,"slice":"pasted-context","lang":"en"} +{"prompt":"One contained cleanup in projects/keystone/workers/thumbnail/consumer.ex: remove the obsolete KeystoneOpalRouterService import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-51135: finish the compact KeystoneHarborIndexFlow filter experience\n\nRoute: /catalog/search\nSource: projects/keystone/apps/console/routes/usage.svelte\nFramework: gRPC\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 KeystoneHarborIndexFlow'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":"Move KeystoneGarnetModalStore's clock and ID generation behind the existing environment type so tests no longer reach global state; outputs and scheduling order must stay identical. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/keystone/engine/render/atlas.cpp b/projects/keystone/engine/render/atlas.cpp\nindex 62d71aa..90f3c1e 100644\n--- a/projects/keystone/engine/render/atlas.cpp\n+++ b/projects/keystone/engine/render/atlas.cpp\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure KeystoneDeltaCanvasFlow 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":"The behavior of KeystoneWillowCodecService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/keystone/ml/pipeline/features.py. 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- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current FastAPI operational envelope\n\nThe relevant code crosses collaboration, C++, Next.js. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Bring KeystoneFlintTimelineStore'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.5,"slice":"core","lang":"en"} +{"prompt":"The destination for KeystoneLumenChartService is broadly agreed; the missing piece is a reversible route from projects/keystone/Sources/CLI/Commands/Doctor.swift to that target. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneLumenChartService\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"KeystoneCopperBridgeCoordinator: ship a sensible version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"KeystoneSableParserCoordinator: handle the lingering thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Tide: The destination for KeystoneEmberRelayStore is broadly agreed; the missing piece is a reversible route from projects/keystone/crates/index/src/segment.rs to that target. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneEmberRelayStore\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Two asks around KeystonePineMetricsCoordinator: (1) finish KeystonePineMetricsCoordinator's responsive empty and retry states; (2) capture the contract and rollback note for consumers. Keep public behavior and serialized data unchanged, and leave a clear boundary between the resulting artifacts or edits.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Test Suite 'KeystoneMoonlitSDKFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[KeystoneMoonlitSDKFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/keystone/pkg/cache/lease.rs:144: error: -[KeystoneMoonlitSDKFlowTests 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 '-[KeystoneMoonlitSDKFlowTests 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 KeystoneMoonlitSDKFlow's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Documente le contrat KeystoneFrostPanelStore","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"fr"} +{"prompt":"What sequence would let KeystoneSableParserService adopt gRPC with dual reads but no dual writes? Include data validation, canary scope, and the decision that ends compatibility mode.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Walk through KeystoneFernSnapshotStore's main.py","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Does KeystoneQuartzPlayerService preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Teach KeystoneCinderAuthFlow to verify signed continuation tokens, reject cross-tenant cursors, and rotate keys without invalidating tokens issued during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Memory attributed to KeystoneLumenChartFlow rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"// projects/keystone/web/components/FilterDrawer.vue\nfinal class KeystoneFrostPanelFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 KeystoneFrostPanelFlow 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":"Three teams extended KeystoneEchoRegistryStore independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current gRPC operational envelope\n\nThe relevant code crosses collaboration, C++, Next.js. Prefer evidence from the repository and make any assumption explicit.\n\nThe individual edits look tiny, but the semantic cleanup spans the repository and must preserve behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Three teams extended KeystoneSpruceDaemonService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current OpenTelemetry operational envelope\n\nThe relevant code crosses collaboration, C++, Next.js. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"KeystoneRainfallDBService's staging timeout is already known to be wrong: change the single projects/keystone/Sources/App/SessionStore.swift value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"KeystoneSlateEditorService flakes under UTC","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"2026-07-30T08:14:11.409Z level=info service=keystonemosaicgridflow pod=keystonemosaicgridflow-7cf8 request_id=51117 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=keystonemosaicgridflow request_id=51117 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=keystonemosaicgridflow request_id=51117 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=keystonemosaicgridflow request_id=51117 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=keystonemosaicgridflow request_id=51117 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=keystonemosaicgridflow request_id=51117 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=keystonemosaicgridflow request_id=51117 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=keystonemosaicgridflow request_id=51117 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nReconstruct the KeystoneMosaicGridFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"KeystoneNovaPickerCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-51119\n\n08:02 deploy KeystoneIrisBatchFlow 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 KeystoneIrisBatchFlow 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":"Umbra: // projects/keystone/ui/settings/PrivacyPane.tsx\nfinal class KeystoneDriftConsoleFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 KeystoneDriftConsoleFlow'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":"Zentriere das KeystoneIrisBatchStore-Modal","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"de"} +{"prompt":"KeystonePrismCacheCoordinator: give it a nicer flow","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Vela: # projects/keystone/services/ledger/replay.go\n[worker.keystonebasilrunnercoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystonebasilrunnercoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystonebasilrunnercoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneBasilRunnerCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51157\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/keystone/services/ledger/replay.go. 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":"Willow: # projects/keystone/app/src/main/SyncWorker.kt\n[worker.keystoneacornwidgetflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystoneacornwidgetflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystoneacornwidgetflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneAcornWidgetFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51125\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/keystone/app/src/main/SyncWorker.kt and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"KeystoneAtlasSearchCoordinator: diagnose, then assess","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Fresh release brief for KeystoneEchoRegistryCoordinator:\n- primary outcome: separate KeystoneEchoRegistryCoordinator's policy from transport without behavior changes\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/keystone/src/sync/reconcile.ts\n- platform constraint: gRPC\n- known complication: a misleading timeout name used in five packages\n\nBoth results are required, but they should remain independently reviewable. Keep public behavior and serialized data unchanged; 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":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"UI ticket DES-51149: finish the compact KeystoneNimbusFormFlow filter experience\n\nRoute: /catalog/search\nSource: projects/keystone/ml/pipeline/features.py\nFramework: FastAPI\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 KeystoneNimbusFormFlow 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":"How does KeystoneSableParserStore propagate cancellation through the gRPC boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Two asks around KeystoneFernSnapshotCoordinator: (1) find the unknown cause of a feature flag whose default differs between environments; (2) capture the contract and rollback note for consumers. Keep public behavior and serialized data unchanged, and leave a clear boundary between the resulting artifacts or edits.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"A flaky failure around KeystoneVelaDrawerStore survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneVelaDrawerStore\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add a bounded KeystoneCloudReconcilerService export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Ownership of KeystoneRavenSessionService is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current gRPC operational envelope\n\nThe relevant code crosses collaboration, C++, Next.js. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Support wants the behavior in projects/keystone/ml/pipeline/features.py recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Style KeystonePineMetricsStore's offline state","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Documente o contrato de KeystoneFrostPanelService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"pt"} +{"prompt":"Ticket OPS-51154: retire the legacy replay path for KeystoneLumenChartCoordinator\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 KeystoneLumenChartCoordinator behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Xylem: UI ticket DES-51133: finish the compact KeystoneCedarPolicyFlow filter experience\n\nRoute: /catalog/search\nSource: projects/keystone/packages/api/openapi.yaml\nFramework: Room\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring KeystoneCedarPolicyFlow'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":"KeystoneNovaPickerStore has four wrappers that only translate the same error enum. Collapse them into one adapter and preserve every public case, message, and metric label. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"KeystoneCedarPolicyCoordinator needs a paired pass: separate KeystoneCedarPolicyCoordinator's policy from transport without behavior changes, plus give the existing implementation a read-only safety pass. Use projects/keystone/config/staging.toml as the source of truth, preserve the Room contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Center the KeystoneSlateEditorStore modal","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} -{"prompt":"Yarrow: UI ticket DES-51141: finish the compact KeystoneOpalRouterFlow filter experience\n\nRoute: /catalog/search\nSource: projects/keystone/workers/thumbnail/consumer.ex\nFramework: OpenTelemetry\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 KeystoneOpalRouterFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"KeystoneSpruceDaemonFlow needs an idempotent replay endpoint backed by OpenTelemetry; accept a cursor, cap each page at 500 items, and return a stable continuation token.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Could the reasoning behind KeystoneTideWorkerStore's gRPC choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"boundary","lang":"en"} -{"prompt":"KeystoneOrbitSyncCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.62,"slice":"mixed","lang":"en"} -{"prompt":"KeystoneNimbusFormCoordinator: untangle the messy bit","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"vague-eval","lang":"en"} -{"prompt":"KeystoneOrbitSyncStore's PrivacyPane.tsx needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"// projects/keystone/lib/codec/frame.cc\nfinal class KeystoneCopperBridgeFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 KeystoneCopperBridgeFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Security flagged KeystoneSummitProxyStore for a read-only pass because its OpenTelemetry boundary mixes tenant data, retries, and cancellation in subtle ways. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current OpenTelemetry operational envelope\n\nThe relevant code crosses collaboration, C++, Next.js. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.69,"slice":"boundary","lang":"en"} -{"prompt":"Ticket OPS-51118: retire the legacy replay path for KeystoneAtlasSearchFlow\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 KeystoneAtlasSearchFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"pasted-context","lang":"en"} -{"prompt":"Introduce a durable deduplication key for KeystoneNovaPickerService events and enforce it in both the database migration and the ingestion path.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"KeystoneCoralUploadService's staging.toml needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"The KeystoneMicaProfileFlow 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.14,"slice":"boundary","lang":"en"} -{"prompt":"Match KeystoneLedgerGateStore's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"boundary","lang":"en"} -{"prompt":"diff --git a/projects/keystone/Sources/CLI/Commands/Doctor.swift b/projects/keystone/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/keystone/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/keystone/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate KeystonePrismCacheFlow'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.87,"slice":"pasted-context","lang":"en"} -{"prompt":"KeystoneRavenSessionFlow's staging timeout is already known to be wrong: change the single projects/keystone/src/sync/reconcile.ts value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"boundary","lang":"en"} -{"prompt":"KeystoneHarborIndexCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"vague-eval","lang":"en"} -{"prompt":"PM needs a concise migration note for KeystoneTideWorkerService, including the user impact, rollback trigger, and the one configuration key operators must change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"KeystoneLedgerGateCoordinator needs a paired pass: separate KeystoneLedgerGateCoordinator's policy from transport without behavior changes, plus give the existing implementation a read-only safety pass. Use projects/keystone/src/sync/reconcile.ts as the source of truth, preserve the gRPC contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.63,"slice":"mixed","lang":"en"} -{"prompt":"In projects/keystone/ui/settings/PrivacyPane.tsx hat KeystoneDriftConsoleService ein sporadisches Problem im OpenTelemetry-Ablauf. Die Ursache ist klar: Ändere nur das Staging-Timeout von 15 auf 30 Sekunden und passe die Assertion an.\n\nRandbedingungen:\n- OpenTelemetry weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf KeystoneDriftConsoleService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um KeystoneDriftConsoleService mit OpenTelemetry kompatibel.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.28,"slice":"core","lang":"de"} -{"prompt":"The data is already available in projects/keystone/lib/codec/frame.cc; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"Zephyr: # projects/keystone/src/sync/reconcile.ts\n[worker.keystonetideworkerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystonetideworkerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystonetideworkerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneTideWorkerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51140\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/keystone/src/sync/reconcile.ts and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"pasted-context","lang":"en"} -{"prompt":"Checkout: The KeystoneEmberRelayFlow 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.17,"slice":"boundary","lang":"en"} -{"prompt":"KeystoneAmberFilterCoordinator: restructure, then correct","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.63,"slice":"mixed","lang":"en"} -{"prompt":"Is KeystoneBeaconStoreService safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"For KeystoneJuniperCLICoordinator, produce a consumer guide for KeystoneJuniperCLICoordinator; once that is complete, give the existing implementation a read-only safety pass. Work from projects/keystone/workers/thumbnail/consumer.ex, stay with OpenTelemetry, and keep public behavior and serialized data unchanged. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.45,"slice":"mixed","lang":"en"} -{"prompt":"En projects/keystone/workers/thumbnail/consumer.ex, KeystoneDriftConsoleStore tiene un problema intermitente en el flujo de OpenTelemetry. Sigue queue, scheduler y cancelación, compara hipótesis y encuentra la causa antes de proponer cambios.\n\nRestricciones:\n- seguir con OpenTelemetry\n- conservar compatibilidad y cancelación\n- limitar el cambio a KeystoneDriftConsoleStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con OpenTelemetry alrededor de KeystoneDriftConsoleStore.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"boundary","lang":"es"} -{"prompt":"projects/keystone/packages/api/openapi.yaml 里的 KeystoneOspreyJobStore 最近在 Room 流程中出现间歇性问题。 请拆分职责并去掉重复，同时保持 API、wire value、顺序和可观察行为不变。\n\n约束：\n- 继续使用 Room\n- 保持兼容性和取消语义\n- 改动只限于 KeystoneOspreyJobStore","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"zh"} -{"prompt":"Where did KeystoneCedarPolicyStore's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"Pin KeystoneMosaicGridService's Swift dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-51115\n\n08:02 deploy KeystoneMarbleTokenFlow 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\nFind the source of this KeystoneMarbleTokenFlow 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.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Split projects/keystone/web/components/FilterDrawer.vue by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"thread 'tokio-runtime-worker' panicked at projects/keystone/packages/api/openapi.yaml:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: keystonecinderauthcoordinator::scheduler::LeaseTask::flush\n at ./projects/keystone/packages/api/openapi.yaml:217:18\n 4: keystonecinderauthcoordinator::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Reconstruct the KeystoneCinderAuthCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.95,"slice":"pasted-context","lang":"ja"} -{"prompt":"Exporter: # projects/keystone/Sources/CLI/Commands/Doctor.swift\n[worker.keystonewrenexportflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystonewrenexportflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystonewrenexportflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneWrenExportFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51124\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/keystone/Sources/CLI/Commands/Doctor.swift. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.43,"slice":"pasted-context","lang":"en"} -{"prompt":"Does KeystoneMoonlitSDKStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Scheduler: // projects/keystone/cmd/exporter/main.py\nfinal class KeystoneCraneWorkspaceFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 KeystoneCraneWorkspaceFlow 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.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Dashboard: projects/keystone/infra/modules/edge/main.tf has grown through several launches, and KeystoneMapleQueueStore now mixes policy, transport, persistence, and metrics in one place. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing Swift 6 deployment\n- keep the work scoped to KeystoneMapleQueueStore and its direct tests\n\nSeveral teams work in this collaboration, C++, Next.js monorepo, so keep ownership and handoff points understandable in a small review.\n\nThe individual edits look tiny, but the semantic cleanup spans the repository and must preserve behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.74,"slice":"boundary","lang":"en"} -{"prompt":"diff --git a/projects/keystone/crates/index/src/segment.rs b/projects/keystone/crates/index/src/segment.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/keystone/crates/index/src/segment.rs\n+++ b/projects/keystone/crates/index/src/segment.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure KeystoneEmberRelayCoordinator 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.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Worker: diff --git a/projects/keystone/pkg/cache/lease.rs b/projects/keystone/pkg/cache/lease.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/keystone/pkg/cache/lease.rs\n+++ b/projects/keystone/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\nRestructure KeystoneSlateEditorFlow 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.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Introduce a durable deduplication key for KeystoneDeltaCanvasStore events and enforce it in both the database migration and the ingestion path.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Simulator: The KeystoneBasilRunnerFlow empty state in projects/keystone/web/components/FilterDrawer.vue needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"boundary","lang":"en"} -{"prompt":"Two deliverables are holding up KeystoneMapleQueueCoordinator. First, produce a consumer guide for KeystoneMapleQueueCoordinator. In the same workstream, correct the known stale timeout beside it. The relevant starting point is projects/keystone/infra/modules/edge/main.tf, which follows Swift 6 conventions and currently suffers from cancellation being swallowed at the repository boundary. Keep public behavior and serialized data unchanged.\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":"writing","secondary":"quickFix","mixed":true,"difficulty":0.64,"slice":"mixed","lang":"en"} -{"prompt":"PM needs a concise migration note for KeystoneCloudReconcilerStore, including the user impact, rollback trigger, and the one configuration key operators must change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"boundary","lang":"en"} -{"prompt":"We expect KeystoneWillowCodecStore to outgrow its current FastAPI arrangement next quarter, but changing everything at once would be risky. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing FastAPI deployment\n- keep the work scoped to KeystoneWillowCodecStore and its direct tests\n\nSeveral teams work in this collaboration, C++, Next.js monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"boundary","lang":"en"} -{"prompt":"Check KeystonePineMetricsService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"KeystoneTideWorkerCoordinator: make this less weird","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"vague-eval","lang":"en"} -{"prompt":"Incident timeline — INC-51123\n\n08:02 deploy KeystoneCoralUploadFlow 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 KeystoneCoralUploadFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.65,"slice":"pasted-context","lang":"en"} -{"prompt":"Ticket OPS-51126: retire the legacy replay path for KeystoneQuartzPlayerFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for KeystoneQuartzPlayerFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.59,"slice":"pasted-context","lang":"en"} -{"prompt":"KeystoneGarnetModalCoordinator: take care of the warning","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"Runbook: Ticket OPS-51114: retire the legacy replay path for KeystoneVelaDrawerFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for KeystoneVelaDrawerFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.67,"slice":"pasted-context","lang":"en"} +{"prompt":"Center the KeystoneSlateEditorStore modal","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Yarrow: UI ticket DES-51141: finish the compact KeystoneOpalRouterFlow filter experience\n\nRoute: /catalog/search\nSource: projects/keystone/workers/thumbnail/consumer.ex\nFramework: OpenTelemetry\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 KeystoneOpalRouterFlow'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":"KeystoneSpruceDaemonFlow needs an idempotent replay endpoint backed by OpenTelemetry; accept a cursor, cap each page at 500 items, and return a stable continuation token.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Could the reasoning behind KeystoneTideWorkerStore's gRPC choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"KeystoneOrbitSyncCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"KeystoneNimbusFormCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"KeystoneOrbitSyncStore's PrivacyPane.tsx needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"// projects/keystone/lib/codec/frame.cc\nfinal class KeystoneCopperBridgeFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 KeystoneCopperBridgeFlow; 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":"Security flagged KeystoneSummitProxyStore for a read-only pass because its OpenTelemetry boundary mixes tenant data, retries, and cancellation in subtle ways. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current OpenTelemetry operational envelope\n\nThe relevant code crosses collaboration, C++, Next.js. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-51118: retire the legacy replay path for KeystoneAtlasSearchFlow\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 KeystoneAtlasSearchFlow 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":"Introduce a durable deduplication key for KeystoneNovaPickerService 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":"KeystoneCoralUploadService's staging.toml needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"The KeystoneMicaProfileFlow 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":"Match KeystoneLedgerGateStore's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/keystone/Sources/CLI/Commands/Doctor.swift b/projects/keystone/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/keystone/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/keystone/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate KeystonePrismCacheFlow'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":"KeystoneRavenSessionFlow's staging timeout is already known to be wrong: change the single projects/keystone/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":"KeystoneHarborIndexCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"PM needs a concise migration note for KeystoneTideWorkerService, 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":"KeystoneLedgerGateCoordinator needs a paired pass: separate KeystoneLedgerGateCoordinator's policy from transport without behavior changes, plus give the existing implementation a read-only safety pass. Use projects/keystone/src/sync/reconcile.ts as the source of truth, preserve the gRPC contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"In projects/keystone/ui/settings/PrivacyPane.tsx hat KeystoneDriftConsoleService ein sporadisches Problem im OpenTelemetry-Ablauf. Die Ursache ist klar: Ändere nur das Staging-Timeout von 15 auf 30 Sekunden und passe die Assertion an.\n\nRandbedingungen:\n- OpenTelemetry weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf KeystoneDriftConsoleService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um KeystoneDriftConsoleService mit OpenTelemetry kompatibel.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"de"} +{"prompt":"The data is already available in projects/keystone/lib/codec/frame.cc; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Zephyr: # projects/keystone/src/sync/reconcile.ts\n[worker.keystonetideworkerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystonetideworkerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystonetideworkerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneTideWorkerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51140\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/keystone/src/sync/reconcile.ts and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Checkout: The KeystoneEmberRelayFlow 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":"KeystoneAmberFilterCoordinator: restructure, then correct","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Is KeystoneBeaconStoreService safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"For KeystoneJuniperCLICoordinator, produce a consumer guide for KeystoneJuniperCLICoordinator; once that is complete, give the existing implementation a read-only safety pass. Work from projects/keystone/workers/thumbnail/consumer.ex, stay with OpenTelemetry, and keep public behavior and serialized data unchanged. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"En projects/keystone/workers/thumbnail/consumer.ex, KeystoneDriftConsoleStore tiene un problema intermitente en el flujo de OpenTelemetry. Sigue queue, scheduler y cancelación, compara hipótesis y encuentra la causa antes de proponer cambios.\n\nRestricciones:\n- seguir con OpenTelemetry\n- conservar compatibilidad y cancelación\n- limitar el cambio a KeystoneDriftConsoleStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con OpenTelemetry alrededor de KeystoneDriftConsoleStore.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"es"} +{"prompt":"projects/keystone/packages/api/openapi.yaml 里的 KeystoneOspreyJobStore 最近在 Room 流程中出现间歇性问题。 请拆分职责并去掉重复，同时保持 API、wire value、顺序和可观察行为不变。\n\n约束：\n- 继续使用 Room\n- 保持兼容性和取消语义\n- 改动只限于 KeystoneOspreyJobStore","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"Where did KeystoneCedarPolicyStore's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Pin KeystoneMosaicGridService's Swift dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-51115\n\n08:02 deploy KeystoneMarbleTokenFlow 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\nFind the source of this KeystoneMarbleTokenFlow symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Split projects/keystone/web/components/FilterDrawer.vue by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"thread 'tokio-runtime-worker' panicked at projects/keystone/packages/api/openapi.yaml:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: keystonecinderauthcoordinator::scheduler::LeaseTask::flush\n at ./projects/keystone/packages/api/openapi.yaml:217:18\n 4: keystonecinderauthcoordinator::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Reconstruct the KeystoneCinderAuthCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Exporter: # projects/keystone/Sources/CLI/Commands/Doctor.swift\n[worker.keystonewrenexportflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystonewrenexportflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystonewrenexportflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneWrenExportFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51124\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/keystone/Sources/CLI/Commands/Doctor.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":"Does KeystoneMoonlitSDKStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Scheduler: // projects/keystone/cmd/exporter/main.py\nfinal class KeystoneCraneWorkspaceFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 KeystoneCraneWorkspaceFlow 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":"Dashboard: projects/keystone/infra/modules/edge/main.tf has grown through several launches, and KeystoneMapleQueueStore now mixes policy, transport, persistence, and metrics in one place. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing Swift 6 deployment\n- keep the work scoped to KeystoneMapleQueueStore and its direct tests\n\nSeveral teams work in this collaboration, C++, Next.js monorepo, so keep ownership and handoff points understandable in a small review.\n\nThe individual edits look tiny, but the semantic cleanup spans the repository and must preserve behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/keystone/crates/index/src/segment.rs b/projects/keystone/crates/index/src/segment.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/keystone/crates/index/src/segment.rs\n+++ b/projects/keystone/crates/index/src/segment.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure KeystoneEmberRelayCoordinator 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Worker: diff --git a/projects/keystone/pkg/cache/lease.rs b/projects/keystone/pkg/cache/lease.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/keystone/pkg/cache/lease.rs\n+++ b/projects/keystone/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\nRestructure KeystoneSlateEditorFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Introduce a durable deduplication key for KeystoneDeltaCanvasStore events and enforce it in both the database migration and the ingestion path.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Simulator: The KeystoneBasilRunnerFlow empty state in projects/keystone/web/components/FilterDrawer.vue needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Two deliverables are holding up KeystoneMapleQueueCoordinator. First, produce a consumer guide for KeystoneMapleQueueCoordinator. In the same workstream, correct the known stale timeout beside it. The relevant starting point is projects/keystone/infra/modules/edge/main.tf, which follows Swift 6 conventions and currently suffers from cancellation being swallowed at the repository boundary. Keep public behavior and serialized data unchanged.\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":"writing","secondary":"quickFix","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"PM needs a concise migration note for KeystoneCloudReconcilerStore, 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":"We expect KeystoneWillowCodecStore to outgrow its current FastAPI arrangement next quarter, but changing everything at once would be risky. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing FastAPI deployment\n- keep the work scoped to KeystoneWillowCodecStore and its direct tests\n\nSeveral teams work in this collaboration, C++, Next.js monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Check KeystonePineMetricsService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"KeystoneTideWorkerCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-51123\n\n08:02 deploy KeystoneCoralUploadFlow 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 KeystoneCoralUploadFlow, 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":"Ticket OPS-51126: retire the legacy replay path for KeystoneQuartzPlayerFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for KeystoneQuartzPlayerFlow, 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":"KeystoneGarnetModalCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Runbook: Ticket OPS-51114: retire the legacy replay path for KeystoneVelaDrawerFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for KeystoneVelaDrawerFlow, 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":"Compare the old and new KeystoneCraneWorkspaceService adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"How should KeystoneSummitProxyService be decomposed?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Give KeystoneAsterWebhookService'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.49,"slice":"core","lang":"en"} -{"prompt":"KeystoneRainfallDBCoordinator: the docs need something","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"vague-eval","lang":"en"} -{"prompt":"Trace: Incident timeline — INC-51113\n\n08:02 deploy KeystoneKiteSchedulerFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Turn the material above into a concise KeystoneKiteSchedulerFlow 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.65,"slice":"pasted-context","lang":"es"} -{"prompt":"Test Suite 'KeystoneRainfallDBFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[KeystoneRainfallDBFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/keystone/Sources/App/SessionStore.swift:144: error: -[KeystoneRainfallDBFlowTests 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 '-[KeystoneRainfallDBFlowTests 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\nFinish the visible KeystoneRainfallDBFlow 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.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Profiler: PM is preparing the KeystoneEchoRegistryService rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneEchoRegistryService\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.49,"slice":"core","lang":"en"} -{"prompt":"Assess the KeystoneAcornWidgetStore diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"projects/keystone/workers/thumbnail/consumer.ex の KeystoneFlintTimelineFlow で、OpenTelemetry の flow に断続的な問題が起きています。 原因は判明済みです。staging timeout だけを 15 秒から 30 秒へ変え、対応する assertion を直してください。\n\n制約:\n- OpenTelemetry を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は KeystoneFlintTimelineFlow のみ","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"boundary","lang":"ja"} -{"prompt":"Console: diff --git a/projects/keystone/db/migrations/20260730_events.sql b/projects/keystone/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/keystone/db/migrations/20260730_events.sql\n+++ b/projects/keystone/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit KeystoneLedgerGateFlow 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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"How does KeystoneCraneWorkspaceStore propagate cancellation through the FastAPI boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Workspace: // projects/keystone/app/src/main/SyncWorker.kt\nfinal class KeystoneSableParserFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Split KeystoneSableParserFlow 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.77,"slice":"pasted-context","lang":"zh"} -{"prompt":"The KeystoneMoonlitSDKService 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.17,"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_51122'\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_51122'::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\nDeliver the KeystoneBeaconStoreFlow 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.86,"slice":"pasted-context","lang":"en"} -{"prompt":"KeystoneWrenExportCoordinator needs a paired pass: assess ownership and failure handling in projects/keystone/Sources/App/SessionStore.swift, plus capture the contract and rollback note for consumers. Use projects/keystone/Sources/App/SessionStore.swift as the source of truth, preserve the FastAPI contract, and avoid unrelated cleanup.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"En projects/keystone/config/staging.toml, KeystoneCinderAuthService tiene un problema intermitente en el flujo de Room. Redacta una guía para consumidores con contrato, errores, retry y un ejemplo copiable; no cambies el handler.\n\nRestricciones:\n- seguir con Room\n- conservar compatibilidad y cancelación\n- limitar el cambio a KeystoneCinderAuthService Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con Room alrededor de KeystoneCinderAuthService.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"es"} -{"prompt":"Repository: # projects/keystone/ml/pipeline/features.py\n[worker.keystonefernsnapshotflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystonefernsnapshotflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystonefernsnapshotflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneFernSnapshotFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51129\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Align KeystoneFernSnapshotFlow'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.43,"slice":"pasted-context","lang":"fr"} -{"prompt":"Pipeline: Incident timeline — INC-51137\n\n08:02 deploy KeystoneAsterWebhookFlow 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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Turn the material above into a concise KeystoneAsterWebhookFlow 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.62,"slice":"pasted-context","lang":"pt"} -{"prompt":"KeystoneDriftConsoleCoordinator is blocking the next release because stale cursors when a page is resumed. I need two concrete outcomes from a single pass: change KeystoneDriftConsoleCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing OpenTelemetry conventions in projects/keystone/workers/thumbnail/consumer.ex; keep public behavior and serialized data unchanged. 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.38,"slice":"mixed","lang":"en"} -{"prompt":"Gateway: The behavior of KeystoneMapleQueueService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/keystone/internal/auth/refresh.go. 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- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current Swift 6 operational envelope\n\nThe relevant code crosses collaboration, C++, Next.js. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"This should remain a deliberately small patch: KeystoneMarbleTokenStore has one known configuration mistake in projects/keystone/app/src/main/SyncWorker.kt, not an open-ended failure investigation. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing gRPC deployment\n- keep the work scoped to KeystoneMarbleTokenStore and its direct tests\n\nSeveral teams work in this collaboration, C++, Next.js monorepo, so keep ownership and handoff points understandable in a small review.\n\nThe cause and exact value change are already known, so keep this as a contained correction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.25,"slice":"boundary","lang":"en"} -{"prompt":"Renderer: Incident timeline — INC-51150\n\n08:02 deploy KeystoneRavenSessionCoordinator 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nReconstruct the KeystoneRavenSessionCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Does KeystoneWrenExportStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Pin KeystoneJuniperCLIStore's OpenTelemetry dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"boundary","lang":"en"} -{"prompt":"Give KeystoneOpalRouterStore'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.46,"slice":"boundary","lang":"en"} -{"prompt":"Em projects/keystone/app/src/main/SyncWorker.kt, o KeystoneHarborIndexStore tem um problema intermitente no fluxo de gRPC. Leia o fluxo atual e avalie ownership, cancelamento e ordem; preciso apenas da análise.\n\nRestrições:\n- continuar com gRPC\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao KeystoneHarborIndexStore","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"pt"} -{"prompt":"Split projects/keystone/app/src/main/SyncWorker.kt by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"Check KeystoneWrenExportService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"// projects/keystone/web/components/FilterDrawer.vue\nfinal class KeystoneGarnetModalFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 KeystoneGarnetModalFlow'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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Translate the KeystoneQuartzPlayerStore setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current KeystoneMosaicGridStore design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneMosaicGridStore\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"KeystoneCloudReconcilerCoordinator: make the api less awkward","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"vague-eval","lang":"en"} -{"prompt":"Ticket OPS-51142: retire the legacy replay path for KeystoneNovaPickerFlow\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 KeystoneNovaPickerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.62,"slice":"pasted-context","lang":"en"} -{"prompt":"What sequence would let KeystoneBasilRunnerStore adopt Swift 6 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.67,"slice":"core","lang":"en"} -{"prompt":"We expect KeystoneMicaProfileService to outgrow its current Swift 6 arrangement next quarter, but changing everything at once would be risky. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing Swift 6 deployment\n- keep the work scoped to KeystoneMicaProfileService and its direct tests\n\nSeveral teams work in this collaboration, C++, Next.js monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.83,"slice":"core","lang":"en"} -{"prompt":"KeystoneVelaDrawerCoordinator is blocking the next release because a deadlock that appears only during shutdown. I need two concrete outcomes from a single pass: change KeystoneVelaDrawerCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing FastAPI conventions in projects/keystone/Sources/CLI/Commands/Doctor.swift; keep public behavior and serialized data unchanged. 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.45,"slice":"mixed","lang":"en"} -{"prompt":"Centre la modale KeystoneIrisBatchService","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"fr"} -{"prompt":"KeystoneCraneWorkspaceCoordinator: smooth out this interaction","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"Indexer: projects/keystone/config/staging.toml の KeystoneOspreyJobService で、Room の flow に断続的な問題が起きています。 段階、互換性、metrics、rollback、ownership を提案し、コード変更の前で止めてください。\n\n制約:\n- Room を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は KeystoneOspreyJobService のみ","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"} -{"prompt":"KeystoneMosaicGridCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.65,"slice":"mixed","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.09,"slice":"boundary","lang":"en"} -{"prompt":"LongbowMoonlitSDKCoordinator: diagnose, then correct","purpose":"debugging","secondary":"quickFix","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Apparently: Check LongbowEmberRelayService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"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.58,"slice":"boundary","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.33,"slice":"boundary","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":"boundary","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":null,"mixed":false,"difficulty":0.52,"slice":"boundary","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.6,"slice":"boundary","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.96,"slice":"pasted-context","lang":"en"} -{"prompt":"LongbowMarbleTokenCoordinator: handle the lingering thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"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] = [:]\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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"LongbowMapleQueueCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"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.52,"slice":"core","lang":"en"} -{"prompt":"Responsive layout for LongbowCinderAuthStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"boundary","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.4,"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.76,"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.12,"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.12,"slice":"boundary","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.38,"slice":"boundary","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.55,"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.82,"slice":"boundary","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.41,"slice":"pasted-context","lang":"en"} -{"prompt":"Match LongbowMoonlitSDKStore's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"boundary","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.95,"slice":"pasted-context","lang":"ja"} -{"prompt":"LongbowWrenExportCoordinator: the docs need something","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"vague-eval","lang":"en"} -{"prompt":"Summarize the LongbowRavenSessionService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"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.3,"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.62,"slice":"boundary","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.67,"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.95,"slice":"pasted-context","lang":"en"} -{"prompt":"Split LongbowOpalRouterService without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Give LongbowCinderAuthService a README example","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"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] = [:]\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.74,"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.66,"slice":"core","lang":"en"} -{"prompt":"Describe LongbowBirchMigratorService's error envelope","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"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.52,"slice":"core","lang":"en"} +{"prompt":"How should KeystoneSummitProxyService be decomposed?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Give KeystoneAsterWebhookService'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":"KeystoneRainfallDBCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Trace: Incident timeline — INC-51113\n\n08:02 deploy KeystoneKiteSchedulerFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Turn the material above into a concise KeystoneKiteSchedulerFlow 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":"Test Suite 'KeystoneRainfallDBFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[KeystoneRainfallDBFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/keystone/Sources/App/SessionStore.swift:144: error: -[KeystoneRainfallDBFlowTests 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 '-[KeystoneRainfallDBFlowTests 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\nFinish the visible KeystoneRainfallDBFlow 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":"Profiler: PM is preparing the KeystoneEchoRegistryService rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneEchoRegistryService\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Assess the KeystoneAcornWidgetStore diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"projects/keystone/workers/thumbnail/consumer.ex の KeystoneFlintTimelineFlow で、OpenTelemetry の flow に断続的な問題が起きています。 原因は判明済みです。staging timeout だけを 15 秒から 30 秒へ変え、対応する assertion を直してください。\n\n制約:\n- OpenTelemetry を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は KeystoneFlintTimelineFlow のみ","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"ja"} +{"prompt":"Console: diff --git a/projects/keystone/db/migrations/20260730_events.sql b/projects/keystone/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/keystone/db/migrations/20260730_events.sql\n+++ b/projects/keystone/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit KeystoneLedgerGateFlow 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":"How does KeystoneCraneWorkspaceStore propagate cancellation through the FastAPI boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Workspace: // projects/keystone/app/src/main/SyncWorker.kt\nfinal class KeystoneSableParserFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Split KeystoneSableParserFlow 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":"The KeystoneMoonlitSDKService 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":"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_51122'\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_51122'::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\nDeliver the KeystoneBeaconStoreFlow server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"KeystoneWrenExportCoordinator needs a paired pass: assess ownership and failure handling in projects/keystone/Sources/App/SessionStore.swift, plus capture the contract and rollback note for consumers. Use projects/keystone/Sources/App/SessionStore.swift as the source of truth, preserve the FastAPI contract, and avoid unrelated cleanup.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"En projects/keystone/config/staging.toml, KeystoneCinderAuthService tiene un problema intermitente en el flujo de Room. Redacta una guía para consumidores con contrato, errores, retry y un ejemplo copiable; no cambies el handler.\n\nRestricciones:\n- seguir con Room\n- conservar compatibilidad y cancelación\n- limitar el cambio a KeystoneCinderAuthService Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con Room alrededor de KeystoneCinderAuthService.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} +{"prompt":"Repository: # projects/keystone/ml/pipeline/features.py\n[worker.keystonefernsnapshotflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystonefernsnapshotflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystonefernsnapshotflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneFernSnapshotFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51129\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Align KeystoneFernSnapshotFlow'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":"Pipeline: Incident timeline — INC-51137\n\n08:02 deploy KeystoneAsterWebhookFlow 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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Turn the material above into a concise KeystoneAsterWebhookFlow release note and operator runbook section. State impact, detection, rollback, and the client-visible contract; do not modify code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} +{"prompt":"KeystoneDriftConsoleCoordinator is blocking the next release because stale cursors when a page is resumed. I need two concrete outcomes from a single pass: change KeystoneDriftConsoleCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing OpenTelemetry conventions in projects/keystone/workers/thumbnail/consumer.ex; keep public behavior and serialized data unchanged. 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.5,"slice":"mixed","lang":"en"} +{"prompt":"Gateway: The behavior of KeystoneMapleQueueService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/keystone/internal/auth/refresh.go. 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- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current Swift 6 operational envelope\n\nThe relevant code crosses collaboration, C++, Next.js. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"This should remain a deliberately small patch: KeystoneMarbleTokenStore has one known configuration mistake in projects/keystone/app/src/main/SyncWorker.kt, not an open-ended failure investigation. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing gRPC deployment\n- keep the work scoped to KeystoneMarbleTokenStore and its direct tests\n\nSeveral teams work in this collaboration, C++, Next.js monorepo, so keep ownership and handoff points understandable in a small review.\n\nThe cause and exact value change are already known, so keep this as a contained correction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Renderer: Incident timeline — INC-51150\n\n08:02 deploy KeystoneRavenSessionCoordinator 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nReconstruct the KeystoneRavenSessionCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Does KeystoneWrenExportStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Pin KeystoneJuniperCLIStore's OpenTelemetry dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Give KeystoneOpalRouterStore'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.5,"slice":"core","lang":"en"} +{"prompt":"Em projects/keystone/app/src/main/SyncWorker.kt, o KeystoneHarborIndexStore tem um problema intermitente no fluxo de gRPC. Leia o fluxo atual e avalie ownership, cancelamento e ordem; preciso apenas da análise.\n\nRestrições:\n- continuar com gRPC\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao KeystoneHarborIndexStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"pt"} +{"prompt":"Split projects/keystone/app/src/main/SyncWorker.kt by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Check KeystoneWrenExportService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"// projects/keystone/web/components/FilterDrawer.vue\nfinal class KeystoneGarnetModalFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 KeystoneGarnetModalFlow'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":"Translate the KeystoneQuartzPlayerStore setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current KeystoneMosaicGridStore design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneMosaicGridStore\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"KeystoneCloudReconcilerCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Ticket OPS-51142: retire the legacy replay path for KeystoneNovaPickerFlow\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 KeystoneNovaPickerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"What sequence would let KeystoneBasilRunnerStore adopt Swift 6 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.8,"slice":"core","lang":"en"} +{"prompt":"We expect KeystoneMicaProfileService to outgrow its current Swift 6 arrangement next quarter, but changing everything at once would be risky. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing Swift 6 deployment\n- keep the work scoped to KeystoneMicaProfileService and its direct tests\n\nSeveral teams work in this collaboration, C++, Next.js monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"KeystoneVelaDrawerCoordinator is blocking the next release because a deadlock that appears only during shutdown. I need two concrete outcomes from a single pass: change KeystoneVelaDrawerCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing FastAPI conventions in projects/keystone/Sources/CLI/Commands/Doctor.swift; keep public behavior and serialized data unchanged. 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.5,"slice":"mixed","lang":"en"} +{"prompt":"Centre la modale KeystoneIrisBatchService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"fr"} +{"prompt":"KeystoneCraneWorkspaceCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Indexer: projects/keystone/config/staging.toml の KeystoneOspreyJobService で、Room の flow に断続的な問題が起きています。 段階、互換性、metrics、rollback、ownership を提案し、コード変更の前で止めてください。\n\n制約:\n- Room を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は KeystoneOspreyJobService のみ","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"ja"} +{"prompt":"KeystoneMosaicGridCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","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] = [:]\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] = [:]\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.71,"slice":"boundary","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.53,"slice":"core","lang":"en"} -{"prompt":"Decouple LongbowPrismCacheService's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"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.33,"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.58,"slice":"boundary","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.49,"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.59,"slice":"boundary","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.43,"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.78,"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.38,"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.86,"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.76,"slice":"boundary","lang":"en"} -{"prompt":"LongbowIrisBatchCoordinator: untangle the messy bit","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"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.72,"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.87,"slice":"pasted-context","lang":"en"} -{"prompt":"LongbowRavenSessionCoordinator: restructure, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.7,"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.89,"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.76,"slice":"pasted-context","lang":"en"} -{"prompt":"LongbowSummitProxyCoordinator: could this be clearer","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"vague-eval","lang":"en"} -{"prompt":"LongbowEmberRelayStore leaks tasks on shutdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"boundary","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.67,"slice":"pasted-context","lang":"en"} -{"prompt":"Cadre la migration de LongbowDeltaCanvasService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"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 \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.86,"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.88,"slice":"core","lang":"en"} -{"prompt":"LongbowCoralUploadCoordinator: deal with the small issue","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"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.67,"slice":"boundary","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.91,"slice":"pasted-context","lang":"en"} -{"prompt":"What does LongbowWillowCodecService own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"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.86,"slice":"pasted-context","lang":"zh"} -{"prompt":"Is LongbowMoonlitSDKService safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"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.33,"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.38,"slice":"pasted-context","lang":"en"} -{"prompt":"Assess the LongbowFlintTimelineStore diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","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":"boundary","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.77,"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.5,"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.72,"slice":"core","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.53,"slice":"core","lang":"zh"} -{"prompt":"Draft LongbowMicaProfileService's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"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.76,"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] = [:]\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.77,"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.78,"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.83,"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.65,"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.6,"slice":"core","lang":"en"} -{"prompt":"Translate the LongbowEchoRegistryStore setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"boundary","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.68,"slice":"pasted-context","lang":"en"} -{"prompt":"LongbowQuartzPlayerCoordinator: ship a sensible version","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"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.43,"slice":"boundary","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.63,"slice":"boundary","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.78,"slice":"pasted-context","lang":"fr"} -{"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.7,"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.46,"slice":"boundary","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.57,"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.67,"slice":"boundary","lang":"en"} -{"prompt":"Warum hängt LongbowDeltaCanvasStore?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","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.33,"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.63,"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.62,"slice":"pasted-context","lang":"pt"} -{"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.33,"slice":"pasted-context","lang":"en"} -{"prompt":"LongbowSableParserCoordinator: polish, then assess","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.61,"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.14,"slice":"boundary","lang":"en"} -{"prompt":"LongbowNimbusFormService's frame.cc needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"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.55,"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.78,"slice":"mixed","lang":"en"} -{"prompt":"LongbowAcornWidgetCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"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] = [:]\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.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Enforce LongbowEchoRegistryService's idempotency key","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","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.51,"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.7,"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.59,"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":"review","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","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.12,"slice":"boundary","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.73,"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.41,"slice":"pasted-context","lang":"es"} -{"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":"boundary","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.73,"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.89,"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.59,"slice":"pasted-context","lang":"en"} -{"prompt":"Corrija o timeout de LongbowLumenChartService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"core","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.55,"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.44,"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.59,"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":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"de"} -{"prompt":"LongbowMosaicGridCoordinator: take care of the warning","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"vague-eval","lang":"en"} -{"prompt":"LongbowPrismCacheCoordinator: ship, then assess","purpose":"backendImpl","secondary":"review","mixed":true,"difficulty":0.72,"slice":"mixed","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.53,"slice":"boundary","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.74,"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] = [:]\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":null,"mixed":false,"difficulty":0.87,"slice":"pasted-context","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.65,"slice":"boundary","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.64,"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.43,"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.43,"slice":"core","lang":"en"} -{"prompt":"Extract LongbowOspreyJobService's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"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.88,"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.83,"slice":"core","lang":"en"} -{"prompt":"LongbowAmberFilterCoordinator: maybe tighten this up","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"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.69,"slice":"boundary","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.62,"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.62,"slice":"mixed","lang":"en"} -{"prompt":"Spell LongbowSableParserStore's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"boundary","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.59,"slice":"core","lang":"en"} -{"prompt":"Assess the LongbowWillowCodecStore diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","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 \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.92,"slice":"pasted-context","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 \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] = [:]\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] = [:]\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] = [:]\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 \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.43,"slice":"mixed","lang":"en"} -{"prompt":"Unify the LongbowSpruceDaemonService validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"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.49,"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.92,"slice":"mixed","lang":"en"} -{"prompt":"Animate the LongbowBasilRunnerStore drawer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"boundary","lang":"en"} -{"prompt":"Frost: Compare LongbowGarnetModalService's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"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.41,"slice":"pasted-context","lang":"en"} -{"prompt":"LongbowOspreyJobCoordinator: correct, then document","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.22,"slice":"mixed","lang":"en"} -{"prompt":"Trace LongbowBasilRunnerService's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Outline a safer LongbowFlintTimelineService cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Draft LongbowRavenSessionStore's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"boundary","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.54,"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.43,"slice":"boundary","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.69,"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.38,"slice":"boundary","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] = [:]\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.77,"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.83,"slice":"boundary","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.68,"slice":"core","lang":"en"} -{"prompt":"LongbowOrbitSyncCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"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.82,"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.17,"slice":"boundary","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.74,"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.53,"slice":"boundary","lang":"pt"} -{"prompt":"Trace LongbowGarnetModalStore's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","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.76,"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.96,"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.63,"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.77,"slice":"boundary","lang":"en"} -{"prompt":"LongbowBeaconStoreCoordinator: polish the last piece","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"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.55,"slice":"core","lang":"en"} -{"prompt":"Remove LongbowSableParserService's stray comma","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"core","lang":"en"} +{"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] = [:]\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.82,"slice":"mixed","lang":"en"} -{"prompt":"LongbowAtlasSearchCoordinator: the screen feels unfinished","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"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.09,"slice":"boundary","lang":"en"} -{"prompt":"LongbowGarnetModalCoordinator: ship, then assess","purpose":"backendImpl","secondary":"review","mixed":true,"difficulty":0.67,"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.79,"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] = [:]\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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"LongbowKiteSchedulerCoordinator: clean up that old path","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"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] = [:]\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.82,"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.53,"slice":"boundary","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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"LongbowLumenChartStore est-il sûr ?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","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.91,"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.49,"slice":"boundary","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.69,"slice":"boundary","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.67,"slice":"pasted-context","lang":"en"} -{"prompt":"LongbowDriftConsoleCoordinator: sort out the rough edge","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"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.87,"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.76,"slice":"pasted-context","lang":"en"} -{"prompt":"LongbowDeltaCanvasCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.53,"slice":"mixed","lang":"en"} -{"prompt":"LongbowNimbusFormCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.48,"slice":"mixed","lang":"en"} -{"prompt":"Milestones for replacing LongbowMicaProfileStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","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.14,"slice":"core","lang":"en"} -{"prompt":"Find LongbowNimbusFormStore's duplicate retry source","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"boundary","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":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"ja"} -{"prompt":"Rename LongbowSpruceDaemonStore's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"diff --git a/projects/meridian/Sources/CLI/Commands/Doctor.swift b/projects/meridian/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/meridian/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate MeridianTideWorkerFlow'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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"projects/meridian/workers/thumbnail/consumer.ex 里的 MeridianGarnetModalStore 最近在 SQLite 流程中出现间歇性问题。 原因已经明确：只把 staging timeout 从 15 秒改成 30 秒，并调整对应 assertion。\n\n约束：\n- 继续使用 SQLite\n- 保持兼容性和取消语义\n- 改动只限于 MeridianGarnetModalStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"boundary","lang":"zh"} -{"prompt":"Quartz: // projects/meridian/apps/console/routes/usage.svelte\nfinal class MeridianFlintTimelineFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianFlintTimelineFlow 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Three teams extended MeridianVelaDrawerService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current PostgreSQL 17 operational envelope\n\nSeveral teams work in this geospatial, Deno, iPadOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"MeridianDeltaCanvasService's staging timeout is already known to be wrong: change the single projects/meridian/db/migrations/20260730_events.sql value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"core","lang":"en"} -{"prompt":"Raven: // projects/meridian/app/src/main/SyncWorker.kt\nfinal class MeridianOrbitSyncFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianOrbitSyncFlow 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"MeridianCopperBridgeCoordinator needs a paired pass: change MeridianCopperBridgeCoordinator's known staging timeout from 15 to 30 seconds, plus capture the contract and rollback note for consumers. Use projects/meridian/db/migrations/20260730_events.sql as the source of truth, preserve the WebGPU contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.24,"slice":"mixed","lang":"en"} -{"prompt":"Sable: // projects/meridian/infra/modules/edge/main.tf\nfinal class MeridianCloudReconcilerFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianCloudReconcilerFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Compare the old and new MeridianDriftConsoleFlow adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Compare the old and new MeridianSableParserService adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Tide: // projects/meridian/packages/api/openapi.yaml\nfinal class MeridianFernSnapshotFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianFernSnapshotFlow 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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Since the last release, MeridianEchoRegistryService has shown an accessibility label that reads the internal enum; nobody on the team can reproduce it reliably on a laptop. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- do not introduce another runtime dependency\n- stay compatible with the existing NATS JetStream deployment\n- keep the work scoped to MeridianEchoRegistryService and its direct tests\n\nThis repository spans geospatial, Deno, iPadOS; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"en"} -{"prompt":"Rename MeridianAtlasSearchService's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Center the MeridianBeaconStoreStore modal","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} -{"prompt":"Bring MeridianOspreyJobStore'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.54,"slice":"boundary","lang":"en"} -{"prompt":"Move MeridianOpalRouterStore'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.58,"slice":"boundary","lang":"en"} -{"prompt":"MeridianDeltaCanvasCoordinator: ship a sensible version","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} -{"prompt":"Walk through MeridianAcornWidgetService's features.py","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Match MeridianPineMetricsStore's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} -{"prompt":"MeridianNovaPickerCoordinator: polish the last piece","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"vague-eval","lang":"en"} -{"prompt":"Umbra: Incident timeline — INC-53159\n\n08:02 deploy MeridianKiteSchedulerCoordinator 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 MeridianKiteSchedulerCoordinator migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"MeridianRainfallDBService crashes after reconnect","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Vela: projects/meridian/Sources/App/SessionStore.swift has grown through several launches, and MeridianAmberFilterStore now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- do not introduce another runtime dependency\n- stay compatible with the existing NATS JetStream deployment\n- keep the work scoped to MeridianAmberFilterStore and its direct tests\n\nThis repository spans geospatial, Deno, iPadOS; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"Ticket OPS-53146: retire the legacy replay path for MeridianRavenSessionFlow\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 MeridianRavenSessionFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.59,"slice":"pasted-context","lang":"en"} -{"prompt":"Ownership of MeridianMapleQueueStore is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current SQLite operational envelope\n\nSeveral teams work in this geospatial, Deno, iPadOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"boundary","lang":"en"} -{"prompt":"Willow: # projects/meridian/internal/auth/refresh.go\n[worker.meridianmoonlitsdkflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.meridianmoonlitsdkflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.meridianmoonlitsdkflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.MeridianMoonlitSDKFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-53144\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/meridian/internal/auth/refresh.go and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.43,"slice":"pasted-context","lang":"en"} -{"prompt":"Memory attributed to MeridianPrismCacheService rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"This should remain a deliberately small patch: MeridianMosaicGridStore has one known configuration mistake in projects/meridian/ui/settings/PrivacyPane.tsx, not an open-ended failure investigation. 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- do not introduce another runtime dependency\n- stay compatible with the existing SQLite deployment\n- keep the work scoped to MeridianMosaicGridStore and its direct tests\n\nThis repository spans geospatial, Deno, iPadOS; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"boundary","lang":"en"} -{"prompt":"Bring MeridianBasilRunnerStore'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.52,"slice":"core","lang":"en"} -{"prompt":"Xylem: Ticket OPS-53140: retire the legacy replay path for MeridianPrismCacheFlow\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 MeridianPrismCacheFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"MeridianCedarPolicyCoordinator needs a paired pass: finish MeridianCedarPolicyCoordinator's responsive empty and retry states, plus give the existing implementation a read-only safety pass. Use projects/meridian/web/components/FilterDrawer.vue as the source of truth, preserve the Tokio contract, and avoid unrelated cleanup.","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.64,"slice":"mixed","lang":"en"} -{"prompt":"What is the safest way to split projects/meridian/app/src/main/SyncWorker.kt into independently owned modules while MeridianFlintTimelineStore's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"MeridianMicaProfileCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"vague-eval","lang":"en"} -{"prompt":"Support wants the behavior in projects/meridian/packages/api/openapi.yaml recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary. The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"boundary","lang":"en"} -{"prompt":"Pin MeridianCedarPolicyStore's Tokio dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"boundary","lang":"en"} -{"prompt":"PM needs a concise migration note for MeridianEmberRelayStore, including the user impact, rollback trigger, and the one configuration key operators must change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Move MeridianNimbusFormService'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.53,"slice":"core","lang":"en"} -{"prompt":"Security flagged MeridianAtlasSearchStore for a read-only pass because its Tokio boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current Tokio operational envelope\n\nSeveral teams work in this geospatial, Deno, iPadOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"boundary","lang":"en"} -{"prompt":"MeridianRavenSessionCoordinator: make this less weird","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"vague-eval","lang":"en"} -{"prompt":"MeridianCinderAuthStore returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/meridian/web/components/FilterDrawer.vue and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","lang":"en"} -{"prompt":"The MeridianOpalRouterService surface in projects/meridian/app/src/main/SyncWorker.kt 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.38,"slice":"core","lang":"en"} -{"prompt":"Read projects/meridian/internal/auth/refresh.go and tell me whether MeridianCloudReconcilerStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"diff --git a/projects/meridian/internal/auth/refresh.go b/projects/meridian/internal/auth/refresh.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/internal/auth/refresh.go\n+++ b/projects/meridian/internal/auth/refresh.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate MeridianSlateEditorFlow'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.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Yarrow: Bring MeridianFlintTimelineService'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.49,"slice":"core","lang":"en"} -{"prompt":"Zephyr: diff --git a/projects/meridian/lib/codec/frame.cc b/projects/meridian/lib/codec/frame.cc\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/lib/codec/frame.cc\n+++ b/projects/meridian/lib/codec/frame.cc\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\nAdd the bounded MeridianPineMetricsFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"Checkout: diff --git a/projects/meridian/src/sync/reconcile.ts b/projects/meridian/src/sync/reconcile.ts\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/src/sync/reconcile.ts\n+++ b/projects/meridian/src/sync/reconcile.ts\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure MeridianCopperBridgeFlow 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Draft MeridianAmberFilterService's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"Two asks around MeridianFernSnapshotCoordinator: (1) find the unknown cause of a feature flag whose default differs between environments; (2) give the existing implementation a read-only safety pass. Do not introduce another runtime dependency, and leave a clear boundary between the resulting artifacts or edits.","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.73,"slice":"mixed","lang":"en"} -{"prompt":"Polish the MeridianBeaconStoreService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} -{"prompt":"MeridianCoralUploadService est-il sûr ?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"fr"} -{"prompt":"MeridianMosaicGridService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. 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- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current SQLite operational envelope\n\nSeveral teams work in this geospatial, Deno, iPadOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"MeridianAmberFilterCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.62,"slice":"mixed","lang":"en"} -{"prompt":"Ticket OPS-53150: retire the legacy replay path for MeridianLumenChartCoordinator\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 MeridianLumenChartCoordinator 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.57,"slice":"pasted-context","lang":"en"} -{"prompt":"PM needs a concise migration note for MeridianMapleQueueFlow, including the user impact, rollback trigger, and the one configuration key operators must change. The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"boundary","lang":"en"} -{"prompt":"The MeridianLumenChartStore 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.09,"slice":"core","lang":"en"} -{"prompt":"We expect MeridianLumenChartService to outgrow its current PostgreSQL 17 arrangement next quarter, but changing everything at once would be risky. 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- do not introduce another runtime dependency\n- stay compatible with the existing PostgreSQL 17 deployment\n- keep the work scoped to MeridianLumenChartService and its direct tests\n\nThis repository spans geospatial, Deno, iPadOS; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"MeridianIrisBatchCoordinator is blocking the next release because timestamps rendered one day ahead near UTC midnight. I need two concrete outcomes from a single pass: change MeridianIrisBatchCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing PostgreSQL 17 conventions in projects/meridian/packages/api/openapi.yaml; do not introduce another runtime dependency. 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.35,"slice":"mixed","lang":"en"} -{"prompt":"MeridianRavenSessionStore's staging timeout is already known to be wrong: change the single projects/meridian/Sources/CLI/Commands/Doctor.swift value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"boundary","lang":"en"} -{"prompt":"MeridianSableParserCoordinator: rethink this area","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"vague-eval","lang":"en"} -{"prompt":"# CI job 53133: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: SQLite\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] MeridianAsterWebhookFlowIntegration.replays_after_timeout ... ok\n[test] MeridianAsterWebhookFlowIntegration.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 \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\nReconstruct the MeridianAsterWebhookFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.95,"slice":"pasted-context","lang":"en"} -{"prompt":"Lay out a two-milestone strategy for eliminating duplicate retries after a network handoff in MeridianEmberRelayFlow, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"Assess the MeridianOrbitSyncService diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"$ pnpm test --filter MeridianAcornWidgetFlow\n RUN v3.2.4 /workspace/apps/console\n × MeridianAcornWidgetFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=53121 phase=resume storedCursor=seg-0183\n session=53121 phase=fetch requestCursor=seg-0183 pageSize=200\n session=53121 phase=commit receivedCursor=seg-0184 itemCount=0\n session=53121 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Reconstruct the MeridianAcornWidgetFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"de"} -{"prompt":"MeridianBeaconStoreCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Center the MeridianLedgerGateStore modal","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"boundary","lang":"en"} -{"prompt":"Exporter: The API work is done; what remains for MeridianKiteSchedulerStore is the visible interaction layer across loading, offline, empty, and success cases. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside MeridianKiteSchedulerStore\n- do not introduce another runtime dependency\n\nThe relevant code crosses geospatial, Deno, iPadOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Fresh release brief for MeridianAtlasSearchCoordinator:\n- primary outcome: change MeridianAtlasSearchCoordinator'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/meridian/internal/auth/refresh.go\n- platform constraint: Tokio\n- known complication: lost focus when the drawer animation finishes\n\nBoth results are required, but they should remain independently reviewable. Do not introduce another runtime dependency; 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.45,"slice":"mixed","lang":"en"} -{"prompt":"Scheduler: Ticket OPS-53114: retire the legacy replay path for MeridianAtlasSearchFlow\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 MeridianAtlasSearchFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"MeridianNimbusFormCoordinator: smooth out this interaction","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"vague-eval","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] = [:]\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] = [:]\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"} +{"prompt":"diff --git a/projects/meridian/Sources/CLI/Commands/Doctor.swift b/projects/meridian/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/meridian/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate MeridianTideWorkerFlow'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":"projects/meridian/workers/thumbnail/consumer.ex 里的 MeridianGarnetModalStore 最近在 SQLite 流程中出现间歇性问题。 原因已经明确：只把 staging timeout 从 15 秒改成 30 秒，并调整对应 assertion。\n\n约束：\n- 继续使用 SQLite\n- 保持兼容性和取消语义\n- 改动只限于 MeridianGarnetModalStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"zh"} +{"prompt":"Quartz: // projects/meridian/apps/console/routes/usage.svelte\nfinal class MeridianFlintTimelineFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianFlintTimelineFlow 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":"Three teams extended MeridianVelaDrawerService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current PostgreSQL 17 operational envelope\n\nSeveral teams work in this geospatial, Deno, iPadOS 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":"MeridianDeltaCanvasService's staging timeout is already known to be wrong: change the single projects/meridian/db/migrations/20260730_events.sql value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Raven: // projects/meridian/app/src/main/SyncWorker.kt\nfinal class MeridianOrbitSyncFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianOrbitSyncFlow 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":"MeridianCopperBridgeCoordinator needs a paired pass: change MeridianCopperBridgeCoordinator's known staging timeout from 15 to 30 seconds, plus capture the contract and rollback note for consumers. Use projects/meridian/db/migrations/20260730_events.sql as the source of truth, preserve the WebGPU contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Sable: // projects/meridian/infra/modules/edge/main.tf\nfinal class MeridianCloudReconcilerFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianCloudReconcilerFlow; 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":"Compare the old and new MeridianDriftConsoleFlow 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":"Compare the old and new MeridianSableParserService 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":"Tide: // projects/meridian/packages/api/openapi.yaml\nfinal class MeridianFernSnapshotFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianFernSnapshotFlow 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":"Since the last release, MeridianEchoRegistryService has shown an accessibility label that reads the internal enum; nobody on the team can reproduce it reliably on a laptop. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- do not introduce another runtime dependency\n- stay compatible with the existing NATS JetStream deployment\n- keep the work scoped to MeridianEchoRegistryService and its direct tests\n\nThis repository spans geospatial, Deno, iPadOS; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Rename MeridianAtlasSearchService's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Center the MeridianBeaconStoreStore modal","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Bring MeridianOspreyJobStore'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.5,"slice":"core","lang":"en"} +{"prompt":"Move MeridianOpalRouterStore'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":"MeridianDeltaCanvasCoordinator: ship a sensible version","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Walk through MeridianAcornWidgetService's features.py","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Match MeridianPineMetricsStore's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"MeridianNovaPickerCoordinator: polish the last piece","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Umbra: Incident timeline — INC-53159\n\n08:02 deploy MeridianKiteSchedulerCoordinator 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 MeridianKiteSchedulerCoordinator migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"MeridianRainfallDBService crashes after reconnect","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Vela: projects/meridian/Sources/App/SessionStore.swift has grown through several launches, and MeridianAmberFilterStore now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- do not introduce another runtime dependency\n- stay compatible with the existing NATS JetStream deployment\n- keep the work scoped to MeridianAmberFilterStore and its direct tests\n\nThis repository spans geospatial, Deno, iPadOS; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-53146: retire the legacy replay path for MeridianRavenSessionFlow\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 MeridianRavenSessionFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Ownership of MeridianMapleQueueStore is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current SQLite operational envelope\n\nSeveral teams work in this geospatial, Deno, iPadOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Willow: # projects/meridian/internal/auth/refresh.go\n[worker.meridianmoonlitsdkflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.meridianmoonlitsdkflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.meridianmoonlitsdkflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.MeridianMoonlitSDKFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-53144\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/meridian/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":"Memory attributed to MeridianPrismCacheService rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"This should remain a deliberately small patch: MeridianMosaicGridStore has one known configuration mistake in projects/meridian/ui/settings/PrivacyPane.tsx, not an open-ended failure investigation. 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- do not introduce another runtime dependency\n- stay compatible with the existing SQLite deployment\n- keep the work scoped to MeridianMosaicGridStore and its direct tests\n\nThis repository spans geospatial, Deno, iPadOS; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Bring MeridianBasilRunnerStore'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":"Xylem: Ticket OPS-53140: retire the legacy replay path for MeridianPrismCacheFlow\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 MeridianPrismCacheFlow 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":"MeridianCedarPolicyCoordinator needs a paired pass: finish MeridianCedarPolicyCoordinator's responsive empty and retry states, plus give the existing implementation a read-only safety pass. Use projects/meridian/web/components/FilterDrawer.vue as the source of truth, preserve the Tokio contract, and avoid unrelated cleanup.","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"What is the safest way to split projects/meridian/app/src/main/SyncWorker.kt into independently owned modules while MeridianFlintTimelineStore's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"MeridianMicaProfileCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Support wants the behavior in projects/meridian/packages/api/openapi.yaml recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary. The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Pin MeridianCedarPolicyStore's Tokio dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"PM needs a concise migration note for MeridianEmberRelayStore, 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":"Move MeridianNimbusFormService'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":"Security flagged MeridianAtlasSearchStore for a read-only pass because its Tokio boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current Tokio operational envelope\n\nSeveral teams work in this geospatial, Deno, iPadOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"MeridianRavenSessionCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"MeridianCinderAuthStore returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/meridian/web/components/FilterDrawer.vue and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"The MeridianOpalRouterService surface in projects/meridian/app/src/main/SyncWorker.kt 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":"Read projects/meridian/internal/auth/refresh.go and tell me whether MeridianCloudReconcilerStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/meridian/internal/auth/refresh.go b/projects/meridian/internal/auth/refresh.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/internal/auth/refresh.go\n+++ b/projects/meridian/internal/auth/refresh.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate MeridianSlateEditorFlow'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":"Yarrow: Bring MeridianFlintTimelineService'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":"Zephyr: diff --git a/projects/meridian/lib/codec/frame.cc b/projects/meridian/lib/codec/frame.cc\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/lib/codec/frame.cc\n+++ b/projects/meridian/lib/codec/frame.cc\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\nAdd the bounded MeridianPineMetricsFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Checkout: diff --git a/projects/meridian/src/sync/reconcile.ts b/projects/meridian/src/sync/reconcile.ts\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/src/sync/reconcile.ts\n+++ b/projects/meridian/src/sync/reconcile.ts\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure MeridianCopperBridgeFlow 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":"Draft MeridianAmberFilterService's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Two asks around MeridianFernSnapshotCoordinator: (1) find the unknown cause of a feature flag whose default differs between environments; (2) give the existing implementation a read-only safety pass. Do not introduce another runtime dependency, and leave a clear boundary between the resulting artifacts or edits.","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Polish the MeridianBeaconStoreService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"MeridianCoralUploadService est-il sûr ?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"fr"} +{"prompt":"MeridianMosaicGridService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. 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- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current SQLite operational envelope\n\nSeveral teams work in this geospatial, Deno, iPadOS 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":"MeridianAmberFilterCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Ticket OPS-53150: retire the legacy replay path for MeridianLumenChartCoordinator\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 MeridianLumenChartCoordinator 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":"PM needs a concise migration note for MeridianMapleQueueFlow, including the user impact, rollback trigger, and the one configuration key operators must change. The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"The MeridianLumenChartStore 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":"We expect MeridianLumenChartService to outgrow its current PostgreSQL 17 arrangement next quarter, but changing everything at once would be risky. 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- do not introduce another runtime dependency\n- stay compatible with the existing PostgreSQL 17 deployment\n- keep the work scoped to MeridianLumenChartService and its direct tests\n\nThis repository spans geospatial, Deno, iPadOS; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"MeridianIrisBatchCoordinator is blocking the next release because timestamps rendered one day ahead near UTC midnight. I need two concrete outcomes from a single pass: change MeridianIrisBatchCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing PostgreSQL 17 conventions in projects/meridian/packages/api/openapi.yaml; do not introduce another runtime dependency. 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":"MeridianRavenSessionStore's staging timeout is already known to be wrong: change the single projects/meridian/Sources/CLI/Commands/Doctor.swift value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"MeridianSableParserCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"# CI job 53133: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: SQLite\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] MeridianAsterWebhookFlowIntegration.replays_after_timeout ... ok\n[test] MeridianAsterWebhookFlowIntegration.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 \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\nReconstruct the MeridianAsterWebhookFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating duplicate retries after a network handoff in MeridianEmberRelayFlow, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Assess the MeridianOrbitSyncService diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"$ pnpm test --filter MeridianAcornWidgetFlow\n RUN v3.2.4 /workspace/apps/console\n × MeridianAcornWidgetFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=53121 phase=resume storedCursor=seg-0183\n session=53121 phase=fetch requestCursor=seg-0183 pageSize=200\n session=53121 phase=commit receivedCursor=seg-0184 itemCount=0\n session=53121 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Reconstruct the MeridianAcornWidgetFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"MeridianBeaconStoreCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Center the MeridianLedgerGateStore modal","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Exporter: The API work is done; what remains for MeridianKiteSchedulerStore is the visible interaction layer across loading, offline, empty, and success cases. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside MeridianKiteSchedulerStore\n- do not introduce another runtime dependency\n\nThe relevant code crosses geospatial, Deno, iPadOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Fresh release brief for MeridianAtlasSearchCoordinator:\n- primary outcome: change MeridianAtlasSearchCoordinator'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/meridian/internal/auth/refresh.go\n- platform constraint: Tokio\n- known complication: lost focus when the drawer animation finishes\n\nBoth results are required, but they should remain independently reviewable. Do not introduce another runtime dependency; 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.4,"slice":"mixed","lang":"en"} +{"prompt":"Scheduler: Ticket OPS-53114: retire the legacy replay path for MeridianAtlasSearchFlow\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 MeridianAtlasSearchFlow 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":"MeridianNimbusFormCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"Two asks around MeridianPineMetricsCoordinator: (1) lay out a staged migration for MeridianPineMetricsCoordinator; (2) also add the visible loading and offline states. Do not introduce another runtime dependency, and leave a clear boundary between the resulting artifacts or edits.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"MeridianWrenExportCoordinator: restructure, then document","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.63,"slice":"mixed","lang":"en"} -{"prompt":"Clarify MeridianPineMetricsService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"MeridianMoonlitSDKCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"vague-eval","lang":"en"} -{"prompt":"projects/meridian/ui/settings/PrivacyPane.tsx の MeridianGarnetModalService で、SQLite の flow に断続的な問題が起きています。 consumer 向けに contract、error、retry、コピー可能な例を含む文書を書き、handler は変更しないでください。\n\n制約:\n- SQLite を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は MeridianGarnetModalService のみ","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"ja"} -{"prompt":"Dashboard: The minimum supported SQLite version in projects/meridian/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.17,"slice":"boundary","lang":"en"} -{"prompt":"Translate the MeridianSlateEditorStore setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"boundary","lang":"en"} -{"prompt":"Worker: The data is already available in projects/meridian/infra/modules/edge/main.tf; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"boundary","lang":"en"} -{"prompt":"# projects/meridian/services/ledger/replay.go\n[worker.meridiancedarpolicyflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.meridiancedarpolicyflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.meridiancedarpolicyflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.MeridianCedarPolicyFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-53129\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. The intended correction is already known: change only the stale 15-second setting to 30 seconds in projects/meridian/services/ledger/replay.go and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.43,"slice":"pasted-context","lang":"fr"} -{"prompt":"Animate the MeridianFrostPanelService drawer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} -{"prompt":"# CI job 53112: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: WebGPU\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] MeridianSummitProxyFlowIntegration.replays_after_timeout ... ok\n[test] MeridianSummitProxyFlowIntegration.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 \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\nReconstruct the MeridianSummitProxyFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.92,"slice":"pasted-context","lang":"en"} -{"prompt":"Before touching projects/meridian/src/sync/reconcile.ts, 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.67,"slice":"core","lang":"en"} -{"prompt":"Could MeridianMicaProfileStore show the active SQLite sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} -{"prompt":"I inherited MeridianSummitProxyService and need a careful read of projects/meridian/src/sync/reconcile.ts before I can sign off on the next release. 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- do not introduce another runtime dependency\n- stay compatible with the existing WebGPU deployment\n- keep the work scoped to MeridianSummitProxyService and its direct tests\n\nThis repository spans geospatial, Deno, iPadOS; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"MeridianCinderAuthCoordinator: clean up that old path","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"Where did MeridianFernSnapshotService's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"MeridianTideWorkerCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"Simulator: # projects/meridian/Sources/CLI/Commands/Doctor.swift\n[worker.meridianechoregistrycoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.meridianechoregistrycoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.meridianechoregistrycoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.MeridianEchoRegistryCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-53156\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/meridian/Sources/CLI/Commands/Doctor.swift and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.36,"slice":"pasted-context","lang":"en"} -{"prompt":"Runbook: # projects/meridian/cmd/exporter/main.py\n[worker.meridianharborindexflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.meridianharborindexflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.meridianharborindexflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.MeridianHarborIndexFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-53131\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/meridian/cmd/exporter/main.py. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.36,"slice":"pasted-context","lang":"en"} -{"prompt":"MeridianCoralUploadCoordinator: correct, then assess","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.29,"slice":"mixed","lang":"en"} -{"prompt":"Trace: projects/meridian/ml/pipeline/features.py の MeridianBirchMigratorFlow で、NATS JetStream の flow に断続的な問題が起きています。 段階、互換性、metrics、rollback、ownership を提案し、コード変更の前で止めてください。\n\n制約:\n- NATS JetStream を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は MeridianBirchMigratorFlow のみ","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"ja"} -{"prompt":"Read projects/meridian/crates/index/src/segment.rs and tell me whether MeridianPrismCacheStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"MeridianCraneWorkspaceCoordinator: untangle the messy bit","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"vague-eval","lang":"en"} -{"prompt":"Ticket: projects/meridian/config/staging.toml 里的 MeridianCraneWorkspaceService 最近在 PostgreSQL 17 流程中出现间歇性问题。 请拆分职责并去掉重复，同时保持 API、wire value、顺序和可观察行为不变。\n\n约束：\n- 继续使用 PostgreSQL 17\n- 保持兼容性和取消语义\n- 改动只限于 MeridianCraneWorkspaceService","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"zh"} -{"prompt":"Check MeridianWrenExportStore's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"diff --git a/projects/meridian/lib/codec/frame.cc b/projects/meridian/lib/codec/frame.cc\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/lib/codec/frame.cc\n+++ b/projects/meridian/lib/codec/frame.cc\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 MeridianMicaProfileFlow'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.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Incident timeline — INC-53127\n\n08:02 deploy MeridianJuniperCLIFlow 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 MeridianJuniperCLIFlow rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"diff --git a/projects/meridian/Sources/CLI/Commands/Doctor.swift b/projects/meridian/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/meridian/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit MeridianAmberFilterFlow 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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Compare the old and new MeridianNimbusFormStore adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Profiler: // projects/meridian/services/ledger/replay.go\nfinal class MeridianCinderAuthFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianCinderAuthFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Incident timeline — INC-53141\n\n08:02 deploy MeridianSableParserFlow 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 MeridianSableParserFlow 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.59,"slice":"pasted-context","lang":"en"} -{"prompt":"Em projects/meridian/packages/api/openapi.yaml, o MeridianCraneWorkspaceStore tem um problema intermitente no fluxo de PostgreSQL 17. A causa já é conhecida: mude apenas o timeout de staging de 15 para 30 segundos e ajuste a assertion.\n\nRestrições:\n- continuar com PostgreSQL 17\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao MeridianCraneWorkspaceStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"boundary","lang":"pt"} -{"prompt":"SDK consumers are ready for durable continuation tokens, so the remaining work lives in MeridianSummitProxyStore's API, storage, and worker layers. Add signed cursor parsing, bounded pagination, key rotation, tenant checks, and a resumable background path with metrics for lag, retries, and terminal failures.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside MeridianSummitProxyStore\n- do not introduce another runtime dependency\n\nThe relevant code crosses geospatial, Deno, iPadOS. Prefer evidence from the repository and make any assumption explicit.\n\nThe contract notes are context; the requested outcome is the working server path.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"boundary","lang":"en"} -{"prompt":"En projects/meridian/ui/settings/PrivacyPane.tsx, MeridianBasilRunnerService tiene un problema intermitente en el flujo de SQLite. La causa ya está clara: cambia solo el timeout de staging de 15 a 30 segundos y ajusta su assertion.\n\nRestricciones:\n- seguir con SQLite\n- conservar compatibilidad y cancelación\n- limitar el cambio a MeridianBasilRunnerService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"es"} -{"prompt":"Wire a MeridianKiteSchedulerFlow background task in projects/meridian/services/ledger/replay.go that expires abandoned sessions, records an OpenTelemetry span, and yields cleanly when shutdown begins.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"MeridianSpruceDaemonFlow occasionally exhibits an accessibility label that reads the internal enum, but only after a reconnect. Follow the data and cancellation paths in projects/meridian/db/migrations/20260730_events.sql and identify the cause before changing anything.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"boundary","lang":"en"} -{"prompt":"Ticket OPS-53154: retire the legacy replay path for MeridianEmberRelayCoordinator\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 MeridianEmberRelayCoordinator 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.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Two deliverables are holding up MeridianMosaicGridCoordinator. First, assess ownership and failure handling in projects/meridian/ui/settings/PrivacyPane.tsx. In the same workstream, capture the contract and rollback note for consumers. The relevant starting point is projects/meridian/ui/settings/PrivacyPane.tsx, which follows SQLite conventions and currently suffers from a flaky snapshot caused by locale-dependent sorting. Do not introduce another runtime dependency.\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":"review","secondary":"writing","mixed":true,"difficulty":0.84,"slice":"mixed","lang":"en"} -{"prompt":"Pin MeridianIrisBatchService's PostgreSQL dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"core","lang":"en"} -{"prompt":"Lay out a two-milestone strategy for eliminating duplicate retries after a network handoff in MeridianEchoRegistryStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Any races in MeridianLedgerGateService?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Console: // projects/meridian/packages/api/openapi.yaml\nfinal class MeridianNimbusFormFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Consolidate MeridianNimbusFormFlow'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.77,"slice":"pasted-context","lang":"zh"} -{"prompt":"The behavior of MeridianBirchMigratorService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/meridian/ml/pipeline/features.py. 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- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current NATS JetStream operational envelope\n\nSeveral teams work in this geospatial, Deno, iPadOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} -{"prompt":"The MeridianCinderAuthService surface in projects/meridian/services/ledger/replay.go 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.43,"slice":"core","lang":"en"} -{"prompt":"For MeridianSlateEditorCoordinator, lay out a staged migration for MeridianSlateEditorCoordinator; once that is complete, consolidate the duplicated normalization paths without changing behavior. Work from projects/meridian/infra/modules/edge/main.tf, stay with Tokio, and do not introduce another runtime dependency. Keep the two outcomes separately reviewable.","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.82,"slice":"mixed","lang":"en"} -{"prompt":"Workspace: Incident timeline — INC-53137\n\n08:02 deploy MeridianOpalRouterFlow 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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Capture the MeridianOpalRouterFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.62,"slice":"pasted-context","lang":"pt"} -{"prompt":"A flaky failure around MeridianSpruceDaemonService survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside MeridianSpruceDaemonService\n- do not introduce another runtime dependency\n\nThe relevant code crosses geospatial, Deno, iPadOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.84,"slice":"core","lang":"en"} -{"prompt":"For MeridianJuniperCLICoordinator, produce a consumer guide for MeridianJuniperCLICoordinator; once that is complete, give the existing implementation a read-only safety pass. Work from projects/meridian/app/src/main/SyncWorker.kt, stay with WebGPU, and do not introduce another runtime dependency. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.48,"slice":"mixed","lang":"en"} -{"prompt":"Por que MeridianJuniperCLIService trava?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"pt"} -{"prompt":"Repository: # projects/meridian/config/staging.toml\n[worker.meridianirisbatchflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.meridianirisbatchflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.meridianirisbatchflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.MeridianIrisBatchFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-53115\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 MeridianIrisBatchFlow'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.33,"slice":"pasted-context","lang":"en"} -{"prompt":"PM is preparing the MeridianMapleQueueService rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside MeridianMapleQueueService\n- do not introduce another runtime dependency\n\nThe relevant code crosses geospatial, Deno, iPadOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Pipeline: Ticket OPS-53120: retire the legacy replay path for MeridianWrenExportFlow\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 MeridianWrenExportFlow 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.57,"slice":"pasted-context","lang":"en"} -{"prompt":"Three teams extended MeridianDriftConsoleService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current WebGPU operational envelope\n\nSeveral teams work in this geospatial, Deno, iPadOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Gateway: diff --git a/projects/meridian/db/migrations/20260730_events.sql b/projects/meridian/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/db/migrations/20260730_events.sql\n+++ b/projects/meridian/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit MeridianQuartzPlayerFlow 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Renderer: The name pendingAck means two different things across MeridianDeltaCanvasStore's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"MeridianLedgerGateCoordinator needs a paired pass: separate MeridianLedgerGateCoordinator's policy from transport without behavior changes, plus capture the contract and rollback note for consumers. Use projects/meridian/Sources/CLI/Commands/Doctor.swift as the source of truth, preserve the NATS JetStream contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"Indexer: Incident timeline — INC-53123\n\n08:02 deploy MeridianFrostPanelFlow 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 MeridianFrostPanelFlow 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.65,"slice":"pasted-context","lang":"en"} -{"prompt":"UI ticket DES-53139: finish the compact MeridianOspreyJobFlow filter experience\n\nRoute: /catalog/search\nSource: projects/meridian/web/components/FilterDrawer.vue\nFramework: Tokio\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nUse the UI evidence to complete MeridianOspreyJobFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Apparently: diff --git a/projects/meridian/crates/index/src/segment.rs b/projects/meridian/crates/index/src/segment.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/crates/index/src/segment.rs\n+++ b/projects/meridian/crates/index/src/segment.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit MeridianVelaDrawerFlow 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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Lately: The public surface of MeridianIrisBatchStore is frozen, but its internal ownership in projects/meridian/packages/api/openapi.yaml is difficult to test and even harder to change safely. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside MeridianIrisBatchStore\n- do not introduce another runtime dependency\n\nThe relevant code crosses geospatial, Deno, iPadOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.69,"slice":"boundary","lang":"en"} +{"prompt":"MeridianWrenExportCoordinator: restructure, then document","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Clarify MeridianPineMetricsService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"MeridianMoonlitSDKCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"projects/meridian/ui/settings/PrivacyPane.tsx の MeridianGarnetModalService で、SQLite の flow に断続的な問題が起きています。 consumer 向けに contract、error、retry、コピー可能な例を含む文書を書き、handler は変更しないでください。\n\n制約:\n- SQLite を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は MeridianGarnetModalService のみ","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"ja"} +{"prompt":"Dashboard: The minimum supported SQLite version in projects/meridian/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":"Translate the MeridianSlateEditorStore setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Worker: The data is already available in projects/meridian/infra/modules/edge/main.tf; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"# projects/meridian/services/ledger/replay.go\n[worker.meridiancedarpolicyflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.meridiancedarpolicyflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.meridiancedarpolicyflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.MeridianCedarPolicyFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-53129\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. The intended correction is already known: change only the stale 15-second setting to 30 seconds in projects/meridian/services/ledger/replay.go and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"pasted-context","lang":"en"} +{"prompt":"Animate the MeridianFrostPanelService drawer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"# CI job 53112: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: WebGPU\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] MeridianSummitProxyFlowIntegration.replays_after_timeout ... ok\n[test] MeridianSummitProxyFlowIntegration.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 \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\nReconstruct the MeridianSummitProxyFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Before touching projects/meridian/src/sync/reconcile.ts, 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.9,"slice":"core","lang":"en"} +{"prompt":"Could MeridianMicaProfileStore show the active SQLite sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"I inherited MeridianSummitProxyService and need a careful read of projects/meridian/src/sync/reconcile.ts before I can sign off on the next release. 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- do not introduce another runtime dependency\n- stay compatible with the existing WebGPU deployment\n- keep the work scoped to MeridianSummitProxyService and its direct tests\n\nThis repository spans geospatial, Deno, iPadOS; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"MeridianCinderAuthCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Where did MeridianFernSnapshotService's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"MeridianTideWorkerCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Simulator: # projects/meridian/Sources/CLI/Commands/Doctor.swift\n[worker.meridianechoregistrycoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.meridianechoregistrycoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.meridianechoregistrycoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.MeridianEchoRegistryCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-53156\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/meridian/Sources/CLI/Commands/Doctor.swift and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Runbook: # projects/meridian/cmd/exporter/main.py\n[worker.meridianharborindexflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.meridianharborindexflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.meridianharborindexflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.MeridianHarborIndexFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-53131\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/meridian/cmd/exporter/main.py. 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":"MeridianCoralUploadCoordinator: correct, then assess","purpose":"backendImpl","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Trace: projects/meridian/ml/pipeline/features.py の MeridianBirchMigratorFlow で、NATS JetStream の flow に断続的な問題が起きています。 段階、互換性、metrics、rollback、ownership を提案し、コード変更の前で止めてください。\n\n制約:\n- NATS JetStream を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は MeridianBirchMigratorFlow のみ","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"ja"} +{"prompt":"Read projects/meridian/crates/index/src/segment.rs and tell me whether MeridianPrismCacheStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"MeridianCraneWorkspaceCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Ticket: projects/meridian/config/staging.toml 里的 MeridianCraneWorkspaceService 最近在 PostgreSQL 17 流程中出现间歇性问题。 请拆分职责并去掉重复，同时保持 API、wire value、顺序和可观察行为不变。\n\n约束：\n- 继续使用 PostgreSQL 17\n- 保持兼容性和取消语义\n- 改动只限于 MeridianCraneWorkspaceService","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"Check MeridianWrenExportStore's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/meridian/lib/codec/frame.cc b/projects/meridian/lib/codec/frame.cc\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/lib/codec/frame.cc\n+++ b/projects/meridian/lib/codec/frame.cc\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 MeridianMicaProfileFlow'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":"Incident timeline — INC-53127\n\n08:02 deploy MeridianJuniperCLIFlow 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 MeridianJuniperCLIFlow 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":"diff --git a/projects/meridian/Sources/CLI/Commands/Doctor.swift b/projects/meridian/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/meridian/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit MeridianAmberFilterFlow 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":"Compare the old and new MeridianNimbusFormStore 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":"Profiler: // projects/meridian/services/ledger/replay.go\nfinal class MeridianCinderAuthFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianCinderAuthFlow; 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":"Incident timeline — INC-53141\n\n08:02 deploy MeridianSableParserFlow 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 MeridianSableParserFlow 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":"Em projects/meridian/packages/api/openapi.yaml, o MeridianCraneWorkspaceStore tem um problema intermitente no fluxo de PostgreSQL 17. A causa já é conhecida: mude apenas o timeout de staging de 15 para 30 segundos e ajuste a assertion.\n\nRestrições:\n- continuar com PostgreSQL 17\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao MeridianCraneWorkspaceStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"pt"} +{"prompt":"SDK consumers are ready for durable continuation tokens, so the remaining work lives in MeridianSummitProxyStore's API, storage, and worker layers. Add signed cursor parsing, bounded pagination, key rotation, tenant checks, and a resumable background path with metrics for lag, retries, and terminal failures.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside MeridianSummitProxyStore\n- do not introduce another runtime dependency\n\nThe relevant code crosses geospatial, Deno, iPadOS. Prefer evidence from the repository and make any assumption explicit.\n\nThe contract notes are context; the requested outcome is the working server path.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"En projects/meridian/ui/settings/PrivacyPane.tsx, MeridianBasilRunnerService tiene un problema intermitente en el flujo de SQLite. La causa ya está clara: cambia solo el timeout de staging de 15 a 30 segundos y ajusta su assertion.\n\nRestricciones:\n- seguir con SQLite\n- conservar compatibilidad y cancelación\n- limitar el cambio a MeridianBasilRunnerService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"es"} +{"prompt":"Wire a MeridianKiteSchedulerFlow background task in projects/meridian/services/ledger/replay.go that expires abandoned sessions, records an OpenTelemetry span, and yields cleanly when shutdown begins.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"MeridianSpruceDaemonFlow occasionally exhibits an accessibility label that reads the internal enum, but only after a reconnect. Follow the data and cancellation paths in projects/meridian/db/migrations/20260730_events.sql and identify the cause before changing anything.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-53154: retire the legacy replay path for MeridianEmberRelayCoordinator\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 MeridianEmberRelayCoordinator 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":"Two deliverables are holding up MeridianMosaicGridCoordinator. First, assess ownership and failure handling in projects/meridian/ui/settings/PrivacyPane.tsx. In the same workstream, capture the contract and rollback note for consumers. The relevant starting point is projects/meridian/ui/settings/PrivacyPane.tsx, which follows SQLite conventions and currently suffers from a flaky snapshot caused by locale-dependent sorting. Do not introduce another runtime dependency.\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":"review","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Pin MeridianIrisBatchService's PostgreSQL dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating duplicate retries after a network handoff in MeridianEchoRegistryStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Any races in MeridianLedgerGateService?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Console: // projects/meridian/packages/api/openapi.yaml\nfinal class MeridianNimbusFormFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Consolidate MeridianNimbusFormFlow'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":"The behavior of MeridianBirchMigratorService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/meridian/ml/pipeline/features.py. 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- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current NATS JetStream operational envelope\n\nSeveral teams work in this geospatial, Deno, iPadOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"The MeridianCinderAuthService surface in projects/meridian/services/ledger/replay.go 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":"For MeridianSlateEditorCoordinator, lay out a staged migration for MeridianSlateEditorCoordinator; once that is complete, consolidate the duplicated normalization paths without changing behavior. Work from projects/meridian/infra/modules/edge/main.tf, stay with Tokio, and do not introduce another runtime dependency. Keep the two outcomes separately reviewable.","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Workspace: Incident timeline — INC-53137\n\n08:02 deploy MeridianOpalRouterFlow 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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Capture the MeridianOpalRouterFlow 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":"A flaky failure around MeridianSpruceDaemonService survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside MeridianSpruceDaemonService\n- do not introduce another runtime dependency\n\nThe relevant code crosses geospatial, Deno, iPadOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"For MeridianJuniperCLICoordinator, produce a consumer guide for MeridianJuniperCLICoordinator; once that is complete, give the existing implementation a read-only safety pass. Work from projects/meridian/app/src/main/SyncWorker.kt, stay with WebGPU, and do not introduce another runtime dependency. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Por que MeridianJuniperCLIService trava?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"pt"} +{"prompt":"Repository: # projects/meridian/config/staging.toml\n[worker.meridianirisbatchflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.meridianirisbatchflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.meridianirisbatchflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.MeridianIrisBatchFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-53115\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 MeridianIrisBatchFlow'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":"PM is preparing the MeridianMapleQueueService rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside MeridianMapleQueueService\n- do not introduce another runtime dependency\n\nThe relevant code crosses geospatial, Deno, iPadOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"Pipeline: Ticket OPS-53120: retire the legacy replay path for MeridianWrenExportFlow\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 MeridianWrenExportFlow 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":"Three teams extended MeridianDriftConsoleService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current WebGPU operational envelope\n\nSeveral teams work in this geospatial, Deno, iPadOS 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":"Gateway: diff --git a/projects/meridian/db/migrations/20260730_events.sql b/projects/meridian/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/db/migrations/20260730_events.sql\n+++ b/projects/meridian/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit MeridianQuartzPlayerFlow 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":"Renderer: The name pendingAck means two different things across MeridianDeltaCanvasStore's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"MeridianLedgerGateCoordinator needs a paired pass: separate MeridianLedgerGateCoordinator's policy from transport without behavior changes, plus capture the contract and rollback note for consumers. Use projects/meridian/Sources/CLI/Commands/Doctor.swift as the source of truth, preserve the NATS JetStream contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Indexer: Incident timeline — INC-53123\n\n08:02 deploy MeridianFrostPanelFlow 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 MeridianFrostPanelFlow 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":"UI ticket DES-53139: finish the compact MeridianOspreyJobFlow filter experience\n\nRoute: /catalog/search\nSource: projects/meridian/web/components/FilterDrawer.vue\nFramework: Tokio\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nUse the UI evidence to complete MeridianOspreyJobFlow'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":"Apparently: diff --git a/projects/meridian/crates/index/src/segment.rs b/projects/meridian/crates/index/src/segment.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/crates/index/src/segment.rs\n+++ b/projects/meridian/crates/index/src/segment.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit MeridianVelaDrawerFlow 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":"Lately: The public surface of MeridianIrisBatchStore is frozen, but its internal ownership in projects/meridian/packages/api/openapi.yaml is difficult to test and even harder to change safely. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside MeridianIrisBatchStore\n- do not introduce another runtime dependency\n\nThe relevant code crosses geospatial, Deno, iPadOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Oddly: For MeridianAsterWebhookCoordinator, lay out a staged migration for MeridianAsterWebhookCoordinator; once that is complete, consolidate the duplicated normalization paths without changing behavior. Work from projects/meridian/ui/settings/PrivacyPane.tsx, stay with SQLite, and do not introduce another runtime dependency. Keep the two outcomes separately reviewable.","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Add a bounded MeridianRavenSessionService export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Does MeridianLumenChartFlow enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"MeridianCloudReconcilerService 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.63,"slice":"core","lang":"en"} -{"prompt":"Responsive layout for MeridianFernSnapshotStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"boundary","lang":"en"} -{"prompt":"Currently: Incident timeline — INC-53153\n\n08:02 deploy MeridianBasilRunnerCoordinator 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Turn the material above into a concise MeridianBasilRunnerCoordinator 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.65,"slice":"pasted-context","lang":"ja"} -{"prompt":"Two asks around MeridianHarborIndexCoordinator: (1) finish MeridianHarborIndexCoordinator's responsive empty and retry states; (2) correct the known stale timeout beside it. Do not introduce another runtime dependency, and leave a clear boundary between the resulting artifacts or edits.","purpose":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.56,"slice":"mixed","lang":"en"} -{"prompt":"Today: The MeridianBasilRunnerFlow surface in projects/meridian/ui/settings/PrivacyPane.tsx is stable now; turn its edge cases into API documentation with one successful example and one cancellation example. The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"boundary","lang":"en"} -{"prompt":"projects/meridian/services/ledger/replay.go has grown through several launches, and MeridianKiteSchedulerService now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- do not introduce another runtime dependency\n- stay compatible with the existing Tokio deployment\n- keep the work scoped to MeridianKiteSchedulerService and its direct tests\n\nThis repository spans geospatial, Deno, iPadOS; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} +{"prompt":"Add a bounded MeridianRavenSessionService export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Does MeridianLumenChartFlow enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"MeridianCloudReconcilerService 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":"Responsive layout for MeridianFernSnapshotStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Currently: Incident timeline — INC-53153\n\n08:02 deploy MeridianBasilRunnerCoordinator 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Turn the material above into a concise MeridianBasilRunnerCoordinator 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":"Two asks around MeridianHarborIndexCoordinator: (1) finish MeridianHarborIndexCoordinator's responsive empty and retry states; (2) correct the known stale timeout beside it. Do not introduce another runtime dependency, and leave a clear boundary between the resulting artifacts or edits.","purpose":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Today: The MeridianBasilRunnerFlow surface in projects/meridian/ui/settings/PrivacyPane.tsx is stable now; turn its edge cases into API documentation with one successful example and one cancellation example. The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"projects/meridian/services/ledger/replay.go has grown through several launches, and MeridianKiteSchedulerService now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- do not introduce another runtime dependency\n- stay compatible with the existing Tokio deployment\n- keep the work scoped to MeridianKiteSchedulerService and its direct tests\n\nThis repository spans geospatial, Deno, iPadOS; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"MeridianEmberRelayService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. 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- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current Tokio operational envelope\n\nSeveral teams work in this geospatial, Deno, iPadOS 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":"A previously stable test around MeridianTideWorkerStore now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"boundary","lang":"en"} -{"prompt":"Context: Incident timeline — INC-53113\n\n08:02 deploy MeridianMosaicGridFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Map a safe route from the current MeridianMosaicGridFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"pasted-context","lang":"es"} -{"prompt":"Background: The behavior of MeridianOrbitSyncStore is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/meridian/apps/console/routes/usage.svelte. 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- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current WebGPU operational envelope\n\nSeveral teams work in this geospatial, Deno, iPadOS monorepo, so keep ownership and handoff points understandable in a small review.\n\nThe server contract is the subject, but the requested output is documentation rather than handler code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.54,"slice":"boundary","lang":"en"} -{"prompt":"Ticket OPS-53152: retire the legacy replay path for MeridianSpruceDaemonCoordinator\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 MeridianSpruceDaemonCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.62,"slice":"pasted-context","lang":"en"} -{"prompt":"MeridianPrismCacheCoordinator: the docs need something","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"vague-eval","lang":"en"} -{"prompt":"2026-07-30T08:14:11.409Z level=info service=meridiandriftconsolecoordinator pod=meridiandriftconsolecoordinator-7cf8 request_id=53157 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=meridiandriftconsolecoordinator request_id=53157 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=meridiandriftconsolecoordinator request_id=53157 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=meridiandriftconsolecoordinator request_id=53157 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=meridiandriftconsolecoordinator request_id=53157 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=meridiandriftconsolecoordinator request_id=53157 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=meridiandriftconsolecoordinator request_id=53157 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=meridiandriftconsolecoordinator request_id=53157 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nReconstruct the MeridianDriftConsoleCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.92,"slice":"pasted-context","lang":"en"} -{"prompt":"MeridianSummitProxyCoordinator is blocking the next release because an empty state that flashes before cached data arrives. I need two concrete outcomes from a single pass: change MeridianSummitProxyCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing WebGPU conventions in projects/meridian/db/migrations/20260730_events.sql; do not introduce another runtime dependency. 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.4,"slice":"mixed","lang":"en"} -{"prompt":"MeridianGarnetModalCoordinator: check the suspicious part","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"vague-eval","lang":"en"} -{"prompt":"Move MeridianDriftConsoleStore'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.58,"slice":"core","lang":"en"} -{"prompt":"Read projects/meridian/lib/codec/frame.cc and tell me whether MeridianMicaProfileService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Question: Ticket OPS-53126: retire the legacy replay path for MeridianLedgerGateFlow\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 MeridianLedgerGateFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"MeridianOpalRouterCoordinator: why is this odd","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"vague-eval","lang":"en"} -{"prompt":"Match MeridianQuartzPlayerService's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"core","lang":"en"} -{"prompt":"Queue MeridianHarborIndexService's expired sessions","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"MeridianAcornWidgetCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.62,"slice":"mixed","lang":"en"} -{"prompt":"Observation: Ticket OPS-53138: retire the legacy replay path for MeridianNovaPickerFlow\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 MeridianNovaPickerFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"pasted-context","lang":"en"} -{"prompt":"Fresh release brief for MeridianMarbleTokenCoordinator:\n- primary outcome: assess ownership and failure handling in projects/meridian/ml/pipeline/features.py\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/meridian/ml/pipeline/features.py\n- platform constraint: NATS JetStream\n- known complication: out-of-order events after consumer rebalancing\n\nBoth results are required, but they should remain independently reviewable. Do not introduce another runtime dependency; 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.79,"slice":"mixed","lang":"en"} -{"prompt":"Document MeridianAcornWidgetStore's cancellation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"Before touching projects/meridian/Sources/App/SessionStore.swift, 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.65,"slice":"boundary","lang":"en"} -{"prompt":"MeridianBirchMigratorStore'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.12,"slice":"core","lang":"en"} -{"prompt":"MeridianCloudReconcilerCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"vague-eval","lang":"en"} -{"prompt":"Enforce MeridianSlateEditorService's idempotency key","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"MeridianOrbitSyncCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.48,"slice":"mixed","lang":"en"} -{"prompt":"One contained cleanup in projects/meridian/config/staging.toml: remove the obsolete MeridianWillowCodecStore import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"core","lang":"en"} -{"prompt":"Draft MeridianRainfallDBStore's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"boundary","lang":"en"} -{"prompt":"MeridianFrostPanelCoordinator: restructure, then document","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"diff --git a/projects/meridian/engine/render/atlas.cpp b/projects/meridian/engine/render/atlas.cpp\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/engine/render/atlas.cpp\n+++ b/projects/meridian/engine/render/atlas.cpp\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 MeridianMapleQueueCoordinator 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.84,"slice":"pasted-context","lang":"en"} -{"prompt":"What is the safest way to split projects/meridian/cmd/exporter/main.py into independently owned modules while MeridianSableParserStore's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"Two deliverables are holding up MeridianVelaDrawerCoordinator. First, lay out a staged migration for MeridianVelaDrawerCoordinator. In the same workstream, also add the visible loading and offline states. The relevant starting point is projects/meridian/pkg/cache/lease.rs, which follows PostgreSQL 17 conventions and currently suffers from a deadlock that appears only during shutdown. Do not introduce another runtime dependency.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.88,"slice":"mixed","lang":"en"} -{"prompt":"Store MeridianCopperBridgeStore's delivery receipts","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"Assess the MeridianAsterWebhookService diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Ticket OPS-53142: retire the legacy replay path for MeridianDeltaCanvasFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for MeridianDeltaCanvasFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.62,"slice":"pasted-context","lang":"en"} -{"prompt":"Could MeridianMoonlitSDKService show the active Tokio sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"MeridianQuartzPlayerCoordinator: restructure, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Give MeridianCedarPolicyService a loading skeleton","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-53111\n\n08:02 deploy MeridianMarbleTokenFlow 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 MeridianMarbleTokenFlow 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.59,"slice":"pasted-context","lang":"en"} +{"prompt":"A previously stable test around MeridianTideWorkerStore 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":"Context: Incident timeline — INC-53113\n\n08:02 deploy MeridianMosaicGridFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Map a safe route from the current MeridianMosaicGridFlow 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":"Background: The behavior of MeridianOrbitSyncStore is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/meridian/apps/console/routes/usage.svelte. 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- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current WebGPU operational envelope\n\nSeveral teams work in this geospatial, Deno, iPadOS monorepo, so keep ownership and handoff points understandable in a small review.\n\nThe server contract is the subject, but the requested output is documentation rather than handler code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Ticket OPS-53152: retire the legacy replay path for MeridianSpruceDaemonCoordinator\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 MeridianSpruceDaemonCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"MeridianPrismCacheCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"2026-07-30T08:14:11.409Z level=info service=meridiandriftconsolecoordinator pod=meridiandriftconsolecoordinator-7cf8 request_id=53157 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=meridiandriftconsolecoordinator request_id=53157 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=meridiandriftconsolecoordinator request_id=53157 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=meridiandriftconsolecoordinator request_id=53157 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=meridiandriftconsolecoordinator request_id=53157 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=meridiandriftconsolecoordinator request_id=53157 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=meridiandriftconsolecoordinator request_id=53157 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=meridiandriftconsolecoordinator request_id=53157 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nReconstruct the MeridianDriftConsoleCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"MeridianSummitProxyCoordinator is blocking the next release because an empty state that flashes before cached data arrives. I need two concrete outcomes from a single pass: change MeridianSummitProxyCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing WebGPU conventions in projects/meridian/db/migrations/20260730_events.sql; do not introduce another runtime dependency. 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.7,"slice":"mixed","lang":"en"} +{"prompt":"MeridianGarnetModalCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Move MeridianDriftConsoleStore'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":"Read projects/meridian/lib/codec/frame.cc and tell me whether MeridianMicaProfileService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Question: Ticket OPS-53126: retire the legacy replay path for MeridianLedgerGateFlow\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 MeridianLedgerGateFlow 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":"MeridianOpalRouterCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Match MeridianQuartzPlayerService's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Queue MeridianHarborIndexService's expired sessions","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"MeridianAcornWidgetCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Observation: Ticket OPS-53138: retire the legacy replay path for MeridianNovaPickerFlow\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 MeridianNovaPickerFlow 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":"Fresh release brief for MeridianMarbleTokenCoordinator:\n- primary outcome: assess ownership and failure handling in projects/meridian/ml/pipeline/features.py\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/meridian/ml/pipeline/features.py\n- platform constraint: NATS JetStream\n- known complication: out-of-order events after consumer rebalancing\n\nBoth results are required, but they should remain independently reviewable. Do not introduce another runtime dependency; 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":"Document MeridianAcornWidgetStore's cancellation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Before touching projects/meridian/Sources/App/SessionStore.swift, 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":"MeridianBirchMigratorStore'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":"MeridianCloudReconcilerCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Enforce MeridianSlateEditorService's idempotency key","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"MeridianOrbitSyncCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"One contained cleanup in projects/meridian/config/staging.toml: remove the obsolete MeridianWillowCodecStore import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Draft MeridianRainfallDBStore's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"MeridianFrostPanelCoordinator: restructure, then document","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"diff --git a/projects/meridian/engine/render/atlas.cpp b/projects/meridian/engine/render/atlas.cpp\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/engine/render/atlas.cpp\n+++ b/projects/meridian/engine/render/atlas.cpp\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 MeridianMapleQueueCoordinator 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":"What is the safest way to split projects/meridian/cmd/exporter/main.py into independently owned modules while MeridianSableParserStore's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Two deliverables are holding up MeridianVelaDrawerCoordinator. First, lay out a staged migration for MeridianVelaDrawerCoordinator. In the same workstream, also add the visible loading and offline states. The relevant starting point is projects/meridian/pkg/cache/lease.rs, which follows PostgreSQL 17 conventions and currently suffers from a deadlock that appears only during shutdown. Do not introduce another runtime dependency.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Store MeridianCopperBridgeStore's delivery receipts","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Assess the MeridianAsterWebhookService diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-53142: retire the legacy replay path for MeridianDeltaCanvasFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for MeridianDeltaCanvasFlow, 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":"Could MeridianMoonlitSDKService show the active Tokio sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"MeridianQuartzPlayerCoordinator: restructure, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Give MeridianCedarPolicyService a loading skeleton","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-53111\n\n08:02 deploy MeridianMarbleTokenFlow 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 MeridianMarbleTokenFlow 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":"Is MeridianWrenExportService safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-53151\n\n08:02 deploy MeridianBirchMigratorCoordinator 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 MeridianBirchMigratorCoordinator, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.59,"slice":"pasted-context","lang":"en"} -{"prompt":"thread 'tokio-runtime-worker' panicked at projects/meridian/crates/index/src/segment.rs:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: meridianrainfalldbflow::scheduler::LeaseTask::flush\n at ./projects/meridian/crates/index/src/segment.rs:217:18\n 4: meridianrainfalldbflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nReconstruct the MeridianRainfallDBFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Where did MeridianFrostPanelStore's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"Test Suite 'MeridianBeaconStoreFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[MeridianBeaconStoreFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/meridian/engine/render/atlas.cpp:144: error: -[MeridianBeaconStoreFlowTests 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 '-[MeridianBeaconStoreFlowTests 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 MeridianBeaconStoreFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.76,"slice":"pasted-context","lang":"en"} -{"prompt":"En projects/meridian/ml/pipeline/features.py, MeridianMarbleTokenStore tiene un problema intermitente en el flujo de NATS JetStream. La causa ya está clara: cambia solo el timeout de staging de 15 a 30 segundos y ajusta su assertion.\n\nRestricciones:\n- seguir con NATS JetStream\n- conservar compatibilidad y cancelación\n- limitar el cambio a MeridianMarbleTokenStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.28,"slice":"boundary","lang":"es"} -{"prompt":"Before we approve MeridianNovaPickerService, 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.58,"slice":"core","lang":"en"} -{"prompt":"For MeridianRainfallDBCoordinator, lay out a staged migration for MeridianRainfallDBCoordinator; once that is complete, consolidate the duplicated normalization paths without changing behavior. Work from projects/meridian/pkg/cache/lease.rs, stay with PostgreSQL 17, and do not introduce another runtime dependency. Keep the two outcomes separately reviewable.","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.72,"slice":"mixed","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_53135'\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_53135'::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\nDeliver the MeridianCraneWorkspaceFlow 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.81,"slice":"pasted-context","lang":"en"} -{"prompt":"Documente le contrat MeridianJuniperCLIStore","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"fr"} -{"prompt":"MeridianFlintTimelineCoordinator: sort out the rough edge","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"vague-eval","lang":"en"} -{"prompt":"// projects/meridian/ui/settings/PrivacyPane.tsx\nfinal class MeridianGarnetModalFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianGarnetModalFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Map MeridianQuartzPlayerStore's ownership split","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Warum hängt MeridianCoralUploadStore?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","lang":"de"} -{"prompt":"Our support and SDK teams keep answering the same questions about MeridianVelaDrawerStore, but the current prose in projects/meridian/pkg/cache/lease.rs only describes the happy path. 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- do not introduce another runtime dependency\n- stay compatible with the existing PostgreSQL 17 deployment\n- keep the work scoped to MeridianVelaDrawerStore and its direct tests\n\nThis repository spans geospatial, Deno, iPadOS; use its existing conventions rather than importing a new abstraction.\n\nThe server contract is the subject, but the requested output is documentation rather than handler code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.49,"slice":"boundary","lang":"en"} -{"prompt":"Compare MeridianAsterWebhookStore's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Remove MeridianHarborIndexStore's stray comma","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"boundary","lang":"en"} -{"prompt":"MeridianOspreyJobCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"vague-eval","lang":"en"} -{"prompt":"SDK consumers are ready for durable continuation tokens, so the remaining work lives in MeridianWillowCodecService's API, storage, and worker layers. Add signed cursor parsing, bounded pagination, key rotation, tenant checks, and a resumable background path with metrics for lag, retries, and terminal failures.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside MeridianWillowCodecService\n- do not introduce another runtime dependency\n\nThe relevant code crosses geospatial, Deno, iPadOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"In projects/meridian/cmd/exporter/main.py hat MeridianMarbleTokenService ein sporadisches Problem im NATS JetStream-Ablauf. Trenne Verantwortlichkeiten und entferne Duplikate, ohne API, Wire-Werte, Reihenfolge oder sichtbares Verhalten zu ändern.\n\nRandbedingungen:\n- NATS JetStream weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf MeridianMarbleTokenService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um MeridianMarbleTokenService mit NATS JetStream kompatibel.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"de"} -{"prompt":"MeridianOspreyJobService'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.19,"slice":"core","lang":"en"} -{"prompt":"MeridianCopperBridgeService leaks tasks on shutdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"// projects/meridian/config/staging.toml\nfinal class MeridianWillowCodecCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianWillowCodecCoordinator; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"pasted-context","lang":"en"} -{"prompt":"On compact widths, MeridianTideWorkerService'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.46,"slice":"core","lang":"en"} -{"prompt":"Constraint: // projects/meridian/web/components/FilterDrawer.vue\nfinal class MeridianCoralUploadFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianCoralUploadFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Compare the old and new NorthstarCopperBridgeFlow adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Please resist widening this one: NorthstarHarborIndexService works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarHarborIndexService\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"Spell NorthstarBirchMigratorStore's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"boundary","lang":"en"} -{"prompt":"Request: Incident timeline — INC-54138\n\n08:02 deploy NorthstarIrisBatchFlow 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 NorthstarIrisBatchFlow rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"pasted-context","lang":"en"} -{"prompt":"Match NorthstarMicaProfileService's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"UI ticket DES-54110: finish the compact NorthstarOpalRouterFlow filter experience\n\nRoute: /catalog/search\nSource: projects/northstar/internal/auth/refresh.go\nFramework: Spring Boot\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 NorthstarOpalRouterFlow 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.68,"slice":"pasted-context","lang":"en"} -{"prompt":"Goal: # projects/northstar/workers/thumbnail/consumer.ex\n[worker.northstaramberfilterflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.northstaramberfilterflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.northstaramberfilterflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.NorthstarAmberFilterFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-54139\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/northstar/workers/thumbnail/consumer.ex. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.43,"slice":"pasted-context","lang":"en"} -{"prompt":"diff --git a/projects/northstar/src/sync/reconcile.ts b/projects/northstar/src/sync/reconcile.ts\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/src/sync/reconcile.ts\n+++ b/projects/northstar/src/sync/reconcile.ts\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 NorthstarCraneWorkspaceCoordinator's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"UI ticket DES-54148: finish the compact NorthstarFernSnapshotFlow filter experience\n\nRoute: /catalog/search\nSource: projects/northstar/db/migrations/20260730_events.sql\nFramework: Kotlin coroutines\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring NorthstarFernSnapshotFlow'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.76,"slice":"pasted-context","lang":"en"} -{"prompt":"PM is preparing the NorthstarMoonlitSDKStore rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarMoonlitSDKStore\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.54,"slice":"boundary","lang":"en"} -{"prompt":"Give NorthstarKiteSchedulerService a README example","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"The NorthstarFrostPanelStore 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.12,"slice":"boundary","lang":"en"} -{"prompt":"A previously stable test around NorthstarMosaicGridService now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Symptom: Incident timeline — INC-54126\n\n08:02 deploy NorthstarBasilRunnerFlow 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 NorthstarBasilRunnerFlow rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"Milestones for replacing NorthstarMapleQueueStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"NorthstarMarbleTokenService needs an idempotent replay endpoint backed by Cloudflare Workers; accept a cursor, cap each page at 500 items, and return a stable continuation token.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"NorthstarCoralUploadStore 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.58,"slice":"boundary","lang":"en"} -{"prompt":"NorthstarMoonlitSDKCoordinator: diagnose, then document","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.78,"slice":"mixed","lang":"en"} -{"prompt":"NorthstarQuartzPlayerCoordinator: could this be clearer","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"vague-eval","lang":"en"} -{"prompt":"# CI job 54132: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: Kafka\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] NorthstarKiteSchedulerFlowIntegration.replays_after_timeout ... ok\n[test] NorthstarKiteSchedulerFlowIntegration.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 \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\nReconstruct the NorthstarKiteSchedulerFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.92,"slice":"pasted-context","lang":"en"} -{"prompt":"Headsup: // projects/northstar/Sources/CLI/Commands/Doctor.swift\nfinal class NorthstarCinderAuthFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 NorthstarCinderAuthFlow 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Bring NorthstarAtlasSearchStore'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.49,"slice":"boundary","lang":"en"} -{"prompt":"In projects/northstar/packages/api/openapi.yaml hat NorthstarNovaPickerService ein sporadisches Problem im GraphQL-Ablauf. Verfasse eine Consumer-Doku mit Vertrag, Fehlern, Retry und einem kopierbaren Beispiel; ändere keinen Handler.\n\nRandbedingungen:\n- GraphQL weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf NorthstarNovaPickerService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um NorthstarNovaPickerService mit GraphQL kompatibel.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"de"} -{"prompt":"NorthstarTideWorkerFlow returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/northstar/ui/settings/PrivacyPane.tsx and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","lang":"en"} -{"prompt":"Match NorthstarEchoRegistryService's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Two deliverables are holding up NorthstarOspreyJobCoordinator. First, assess ownership and failure handling in projects/northstar/Sources/CLI/Commands/Doctor.swift. In the same workstream, capture the contract and rollback note for consumers. The relevant starting point is projects/northstar/Sources/CLI/Commands/Doctor.swift, which follows Kafka conventions and currently suffers from lost focus when the drawer animation finishes. Make rollback possible without deleting user data.\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":"review","secondary":"writing","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"FYI: # projects/northstar/src/sync/reconcile.ts\n[worker.northstarnimbusformflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.northstarnimbusformflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.northstarnimbusformflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.NorthstarNimbusFormFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-54118\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/northstar/src/sync/reconcile.ts. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.41,"slice":"pasted-context","lang":"en"} -{"prompt":"NorthstarLumenChartCoordinator: diagnose, then document","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"The NorthstarCedarPolicyFlow 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.14,"slice":"boundary","lang":"en"} -{"prompt":"NorthstarFlintTimelineCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.43,"slice":"mixed","lang":"en"} -{"prompt":"Before we approve NorthstarOrbitSyncStore, assess whether a misleading timeout name used in five packages is an actual correctness risk or merely confusing structure. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"We expect NorthstarDeltaCanvasStore to outgrow its current Spring Boot arrangement next quarter, but changing everything at once would be risky. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- make rollback possible without deleting user data\n- stay compatible with the existing Spring Boot deployment\n- keep the work scoped to NorthstarDeltaCanvasStore and its direct tests\n\nSeveral teams work in this developer tools, Java, WebGL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.78,"slice":"boundary","lang":"en"} -{"prompt":"Does NorthstarEchoRegistryStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Incident timeline — INC-54116\n\n08:02 deploy NorthstarGarnetModalFlow 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 NorthstarGarnetModalFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"I inherited NorthstarCopperBridgeService and need a careful read of projects/northstar/web/components/FilterDrawer.vue before I can sign off on the next release. 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- make rollback possible without deleting user data\n- stay compatible with the existing Spring Boot deployment\n- keep the work scoped to NorthstarCopperBridgeService and its direct tests\n\nSeveral teams work in this developer tools, Java, WebGL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"diff --git a/projects/northstar/pkg/cache/lease.rs b/projects/northstar/pkg/cache/lease.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/pkg/cache/lease.rs\n+++ b/projects/northstar/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\nRead the artifact above as a skeptical reviewer. Is NorthstarFrostPanelFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Give NorthstarBirchMigratorService a README example","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Pin NorthstarWillowCodecStore's Kotlin dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"boundary","lang":"en"} -{"prompt":"Meanwhile: diff --git a/projects/northstar/config/staging.toml b/projects/northstar/config/staging.toml\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/config/staging.toml\n+++ b/projects/northstar/config/staging.toml\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 NorthstarBeaconStoreFlow'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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Ownership of NorthstarPrismCacheStore is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Kotlin coroutines operational envelope\n\nThe relevant code crosses developer tools, Java, WebGL. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"boundary","lang":"en"} -{"prompt":"NorthstarOrbitSyncService occasionally exhibits two validators with subtly different error strings, but only after a reconnect. Follow the data and cancellation paths in projects/northstar/infra/modules/edge/main.tf and identify the cause before changing anything.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"En projects/northstar/config/staging.toml, NorthstarNovaPickerStore tiene un problema intermitente en el flujo de GraphQL. Propón fases, compatibilidad, métricas, rollback y ownership; detente antes de tocar código.\n\nRestricciones:\n- seguir con GraphQL\n- conservar compatibilidad y cancelación\n- limitar el cambio a NorthstarNovaPickerStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con GraphQL alrededor de NorthstarNovaPickerStore.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.81,"slice":"boundary","lang":"es"} -{"prompt":"Locally: The NorthstarQuartzPlayerStore surface in projects/northstar/services/ledger/replay.go 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.33,"slice":"boundary","lang":"en"} -{"prompt":"NorthstarAtlasSearchService'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.14,"slice":"core","lang":"en"} -{"prompt":"Production: The API work is done; what remains for NorthstarPineMetricsService is the visible interaction layer across loading, offline, empty, and success cases. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarPineMetricsService\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Staging: The NorthstarSlateEditorService empty state in projects/northstar/ml/pipeline/features.py needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-54114\n\n08:02 deploy NorthstarSableParserFlow 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 NorthstarSableParserFlow rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"Is NorthstarVelaDrawerStore safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"CI: The NorthstarAmberFilterStore surface in projects/northstar/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.43,"slice":"boundary","lang":"en"} -{"prompt":"Investigate the NorthstarBasilRunnerService hang","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Atlas: Incident timeline — INC-54130\n\n08:02 deploy NorthstarDriftConsoleFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current NorthstarDriftConsoleFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current NorthstarOpalRouterService design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarOpalRouterService\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"What does NorthstarFlintTimelineStore own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Ticket OPS-54121: retire the legacy replay path for NorthstarMicaProfileFlow\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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Capture the NorthstarMicaProfileFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.59,"slice":"pasted-context","lang":"de"} -{"prompt":"NorthstarNimbusFormCoordinator: correct, then assess","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.27,"slice":"mixed","lang":"en"} -{"prompt":"Beacon: The minimum supported Cloudflare Workers version in projects/northstar/engine/render/atlas.cpp is one patch behind the lockfile. Align that single value and regenerate only the affected metadata.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"core","lang":"en"} -{"prompt":"NorthstarAmberFilterCoordinator: make this less weird","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"vague-eval","lang":"en"} -{"prompt":"diff --git a/projects/northstar/packages/api/openapi.yaml b/projects/northstar/packages/api/openapi.yaml\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/packages/api/openapi.yaml\n+++ b/projects/northstar/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\nRestructure NorthstarMapleQueueFlow 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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"NorthstarSlateEditorCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} -{"prompt":"Test Suite 'NorthstarPineMetricsCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[NorthstarPineMetricsCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/northstar/packages/api/openapi.yaml:144: error: -[NorthstarPineMetricsCoordinatorTests 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 '-[NorthstarPineMetricsCoordinatorTests 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 NorthstarPineMetricsCoordinator'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.7,"slice":"pasted-context","lang":"en"} -{"prompt":"What sequence would let NorthstarAmberFilterService adopt Cloudflare Workers 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.72,"slice":"core","lang":"en"} -{"prompt":"Set NorthstarLumenChartStore's port to 8081","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"boundary","lang":"en"} -{"prompt":"For NorthstarWillowCodecCoordinator, separate NorthstarWillowCodecCoordinator's policy from transport without behavior changes; once that is complete, capture the contract and rollback note for consumers. Work from projects/northstar/src/sync/reconcile.ts, stay with Kotlin coroutines, and make rollback possible without deleting user data. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Cinder: Incident timeline — INC-54152\n\n08:02 deploy NorthstarCedarPolicyCoordinator 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 NorthstarCedarPolicyCoordinator 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.62,"slice":"pasted-context","lang":"en"} -{"prompt":"Delta: diff --git a/projects/northstar/infra/modules/edge/main.tf b/projects/northstar/infra/modules/edge/main.tf\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/infra/modules/edge/main.tf\n+++ b/projects/northstar/infra/modules/edge/main.tf\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is NorthstarOrbitSyncFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"pasted-context","lang":"en"} -{"prompt":"Documente o contrato de NorthstarEmberRelayService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"pt"} -{"prompt":"NorthstarMapleQueueService leaks tasks on shutdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"The name pendingAck means two different things across NorthstarHarborIndexStore's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Design handed over a final pass for NorthstarTideWorkerStore, and the basic data flow in projects/northstar/workers/thumbnail/consumer.ex already works. 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- make rollback possible without deleting user data\n- stay compatible with the existing Cloudflare Workers deployment\n- keep the work scoped to NorthstarTideWorkerStore and its direct tests\n\nSeveral teams work in this developer tools, Java, WebGL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Move NorthstarVelaDrawerService behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"NorthstarCinderAuthCoordinator: diagnose, then correct","purpose":"debugging","secondary":"quickFix","mixed":true,"difficulty":0.78,"slice":"mixed","lang":"en"} -{"prompt":"NorthstarSlateEditorStore'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.14,"slice":"boundary","lang":"en"} -{"prompt":"Ember: What is the safest way to split projects/northstar/apps/console/routes/usage.svelte into independently owned modules while NorthstarRainfallDBStore's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"NorthstarSableParserCoordinator is blocking the next release because an accessibility label that reads the internal enum. I need two concrete outcomes from a single pass: change NorthstarSableParserCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing Cloudflare Workers conventions in projects/northstar/engine/render/atlas.cpp; make rollback possible without deleting user data. 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.45,"slice":"mixed","lang":"en"} -{"prompt":"Security flagged NorthstarGarnetModalStore for a read-only pass because its GraphQL boundary mixes tenant data, retries, and cancellation in subtle ways. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current GraphQL operational envelope\n\nThe relevant code crosses developer tools, Java, WebGL. Prefer evidence from the repository and make any assumption explicit.\n\nNothing is reported broken, so judge and explain current behavior without inventing a failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.69,"slice":"boundary","lang":"en"} -{"prompt":"Ticket OPS-54129: retire the legacy replay path for NorthstarEchoRegistryFlow\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À partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Assess NorthstarEchoRegistryFlow 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.84,"slice":"pasted-context","lang":"fr"} -{"prompt":"Corrige le timeout de NorthstarEmberRelayStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"boundary","lang":"fr"} -{"prompt":"// projects/northstar/services/ledger/replay.go\nfinal class NorthstarDeltaCanvasFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 NorthstarDeltaCanvasFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"pasted-context","lang":"en"} -{"prompt":"NorthstarEmberRelayCoordinator needs a paired pass: assess ownership and failure handling in projects/northstar/cmd/exporter/main.py, plus capture the contract and rollback note for consumers. Use projects/northstar/cmd/exporter/main.py as the source of truth, preserve the Kafka contract, and avoid unrelated cleanup.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"We expect NorthstarCraneWorkspaceService to outgrow its current Kotlin coroutines arrangement next quarter, but changing everything at once would be risky. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- make rollback possible without deleting user data\n- stay compatible with the existing Kotlin coroutines deployment\n- keep the work scoped to NorthstarCraneWorkspaceService and its direct tests\n\nSeveral teams work in this developer tools, Java, WebGL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"core","lang":"en"} -{"prompt":"projects/northstar/services/ledger/replay.go 里的 NorthstarSummitProxyService 最近在 Spring Boot 流程中出现间歇性问题。 请实现幂等 endpoint，包含持久 cursor、tenant 鉴权、spans 和 retry 测试。\n\n约束：\n- 继续使用 Spring Boot\n- 保持兼容性和取消语义\n- 改动只限于 NorthstarSummitProxyService","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"zh"} +{"prompt":"Incident timeline — INC-53151\n\n08:02 deploy MeridianBirchMigratorCoordinator 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 MeridianBirchMigratorCoordinator, 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":"thread 'tokio-runtime-worker' panicked at projects/meridian/crates/index/src/segment.rs:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: meridianrainfalldbflow::scheduler::LeaseTask::flush\n at ./projects/meridian/crates/index/src/segment.rs:217:18\n 4: meridianrainfalldbflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nReconstruct the MeridianRainfallDBFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Where did MeridianFrostPanelStore's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Test Suite 'MeridianBeaconStoreFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[MeridianBeaconStoreFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/meridian/engine/render/atlas.cpp:144: error: -[MeridianBeaconStoreFlowTests 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 '-[MeridianBeaconStoreFlowTests 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 MeridianBeaconStoreFlow'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":"En projects/meridian/ml/pipeline/features.py, MeridianMarbleTokenStore tiene un problema intermitente en el flujo de NATS JetStream. La causa ya está clara: cambia solo el timeout de staging de 15 a 30 segundos y ajusta su assertion.\n\nRestricciones:\n- seguir con NATS JetStream\n- conservar compatibilidad y cancelación\n- limitar el cambio a MeridianMarbleTokenStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"es"} +{"prompt":"Before we approve MeridianNovaPickerService, 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.3,"slice":"core","lang":"en"} +{"prompt":"For MeridianRainfallDBCoordinator, lay out a staged migration for MeridianRainfallDBCoordinator; once that is complete, consolidate the duplicated normalization paths without changing behavior. Work from projects/meridian/pkg/cache/lease.rs, stay with PostgreSQL 17, and do not introduce another runtime dependency. Keep the two outcomes separately reviewable.","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.8,"slice":"mixed","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_53135'\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_53135'::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\nDeliver the MeridianCraneWorkspaceFlow server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Documente le contrat MeridianJuniperCLIStore","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"fr"} +{"prompt":"MeridianFlintTimelineCoordinator: sort out the rough edge","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"// projects/meridian/ui/settings/PrivacyPane.tsx\nfinal class MeridianGarnetModalFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianGarnetModalFlow; 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":"Map MeridianQuartzPlayerStore's ownership split","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Warum hängt MeridianCoralUploadStore?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"de"} +{"prompt":"Our support and SDK teams keep answering the same questions about MeridianVelaDrawerStore, but the current prose in projects/meridian/pkg/cache/lease.rs only describes the happy path. 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- do not introduce another runtime dependency\n- stay compatible with the existing PostgreSQL 17 deployment\n- keep the work scoped to MeridianVelaDrawerStore and its direct tests\n\nThis repository spans geospatial, Deno, iPadOS; use its existing conventions rather than importing a new abstraction.\n\nThe server contract is the subject, but the requested output is documentation rather than handler code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Compare MeridianAsterWebhookStore's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Remove MeridianHarborIndexStore's stray comma","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"MeridianOspreyJobCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"SDK consumers are ready for durable continuation tokens, so the remaining work lives in MeridianWillowCodecService's API, storage, and worker layers. Add signed cursor parsing, bounded pagination, key rotation, tenant checks, and a resumable background path with metrics for lag, retries, and terminal failures.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside MeridianWillowCodecService\n- do not introduce another runtime dependency\n\nThe relevant code crosses geospatial, Deno, iPadOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"In projects/meridian/cmd/exporter/main.py hat MeridianMarbleTokenService ein sporadisches Problem im NATS JetStream-Ablauf. Trenne Verantwortlichkeiten und entferne Duplikate, ohne API, Wire-Werte, Reihenfolge oder sichtbares Verhalten zu ändern.\n\nRandbedingungen:\n- NATS JetStream weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf MeridianMarbleTokenService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um MeridianMarbleTokenService mit NATS JetStream kompatibel.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} +{"prompt":"MeridianOspreyJobService's metric is misspelled as succesful_total in one declaration. Correct that literal and its exact test expectation, without renaming anything else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"MeridianCopperBridgeService leaks tasks on shutdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"// projects/meridian/config/staging.toml\nfinal class MeridianWillowCodecCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianWillowCodecCoordinator; 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":"On compact widths, MeridianTideWorkerService'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.4,"slice":"core","lang":"en"} +{"prompt":"Constraint: // projects/meridian/web/components/FilterDrawer.vue\nfinal class MeridianCoralUploadFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianCoralUploadFlow; 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":"Compare the old and new NorthstarCopperBridgeFlow adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Please resist widening this one: NorthstarHarborIndexService works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarHarborIndexService\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Spell NorthstarBirchMigratorStore's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Request: Incident timeline — INC-54138\n\n08:02 deploy NorthstarIrisBatchFlow 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 NorthstarIrisBatchFlow 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":"Match NorthstarMicaProfileService's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"UI ticket DES-54110: finish the compact NorthstarOpalRouterFlow filter experience\n\nRoute: /catalog/search\nSource: projects/northstar/internal/auth/refresh.go\nFramework: Spring Boot\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 NorthstarOpalRouterFlow 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":"Goal: # projects/northstar/workers/thumbnail/consumer.ex\n[worker.northstaramberfilterflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.northstaramberfilterflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.northstaramberfilterflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.NorthstarAmberFilterFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-54139\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/northstar/workers/thumbnail/consumer.ex. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"pasted-context","lang":"en"} +{"prompt":"diff --git a/projects/northstar/src/sync/reconcile.ts b/projects/northstar/src/sync/reconcile.ts\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/src/sync/reconcile.ts\n+++ b/projects/northstar/src/sync/reconcile.ts\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 NorthstarCraneWorkspaceCoordinator'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":"UI ticket DES-54148: finish the compact NorthstarFernSnapshotFlow filter experience\n\nRoute: /catalog/search\nSource: projects/northstar/db/migrations/20260730_events.sql\nFramework: Kotlin coroutines\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring NorthstarFernSnapshotFlow'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":"PM is preparing the NorthstarMoonlitSDKStore rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarMoonlitSDKStore\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Give NorthstarKiteSchedulerService a README example","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"The NorthstarFrostPanelStore 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":"A previously stable test around NorthstarMosaicGridService 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":"Symptom: Incident timeline — INC-54126\n\n08:02 deploy NorthstarBasilRunnerFlow 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 NorthstarBasilRunnerFlow 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":"Milestones for replacing NorthstarMapleQueueStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"NorthstarMarbleTokenService needs an idempotent replay endpoint backed by Cloudflare Workers; accept a cursor, cap each page at 500 items, and return a stable continuation token.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"NorthstarCoralUploadStore 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":"NorthstarMoonlitSDKCoordinator: diagnose, then document","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"NorthstarQuartzPlayerCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"# CI job 54132: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: Kafka\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] NorthstarKiteSchedulerFlowIntegration.replays_after_timeout ... ok\n[test] NorthstarKiteSchedulerFlowIntegration.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 \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\nReconstruct the NorthstarKiteSchedulerFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Headsup: // projects/northstar/Sources/CLI/Commands/Doctor.swift\nfinal class NorthstarCinderAuthFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 NorthstarCinderAuthFlow 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":"Bring NorthstarAtlasSearchStore'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":"In projects/northstar/packages/api/openapi.yaml hat NorthstarNovaPickerService ein sporadisches Problem im GraphQL-Ablauf. Verfasse eine Consumer-Doku mit Vertrag, Fehlern, Retry und einem kopierbaren Beispiel; ändere keinen Handler.\n\nRandbedingungen:\n- GraphQL weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf NorthstarNovaPickerService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um NorthstarNovaPickerService mit GraphQL kompatibel.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"de"} +{"prompt":"NorthstarTideWorkerFlow returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/northstar/ui/settings/PrivacyPane.tsx and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Match NorthstarEchoRegistryService's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Two deliverables are holding up NorthstarOspreyJobCoordinator. First, assess ownership and failure handling in projects/northstar/Sources/CLI/Commands/Doctor.swift. In the same workstream, capture the contract and rollback note for consumers. The relevant starting point is projects/northstar/Sources/CLI/Commands/Doctor.swift, which follows Kafka conventions and currently suffers from lost focus when the drawer animation finishes. Make rollback possible without deleting user data.\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":"review","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"FYI: # projects/northstar/src/sync/reconcile.ts\n[worker.northstarnimbusformflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.northstarnimbusformflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.northstarnimbusformflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.NorthstarNimbusFormFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-54118\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/northstar/src/sync/reconcile.ts. 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":"NorthstarLumenChartCoordinator: diagnose, then document","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"The NorthstarCedarPolicyFlow 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":"NorthstarFlintTimelineCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Before we approve NorthstarOrbitSyncStore, assess whether a misleading timeout name used in five packages is an actual correctness risk or merely confusing structure. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"We expect NorthstarDeltaCanvasStore to outgrow its current Spring Boot arrangement next quarter, but changing everything at once would be risky. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- make rollback possible without deleting user data\n- stay compatible with the existing Spring Boot deployment\n- keep the work scoped to NorthstarDeltaCanvasStore and its direct tests\n\nSeveral teams work in this developer tools, Java, WebGL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Does NorthstarEchoRegistryStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-54116\n\n08:02 deploy NorthstarGarnetModalFlow 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 NorthstarGarnetModalFlow 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":"I inherited NorthstarCopperBridgeService and need a careful read of projects/northstar/web/components/FilterDrawer.vue before I can sign off on the next release. 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- make rollback possible without deleting user data\n- stay compatible with the existing Spring Boot deployment\n- keep the work scoped to NorthstarCopperBridgeService and its direct tests\n\nSeveral teams work in this developer tools, Java, WebGL 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":"diff --git a/projects/northstar/pkg/cache/lease.rs b/projects/northstar/pkg/cache/lease.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/pkg/cache/lease.rs\n+++ b/projects/northstar/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\nRead the artifact above as a skeptical reviewer. Is NorthstarFrostPanelFlow'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":"Give NorthstarBirchMigratorService a README example","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Pin NorthstarWillowCodecStore's Kotlin dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Meanwhile: diff --git a/projects/northstar/config/staging.toml b/projects/northstar/config/staging.toml\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/config/staging.toml\n+++ b/projects/northstar/config/staging.toml\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 NorthstarBeaconStoreFlow'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":"Ownership of NorthstarPrismCacheStore is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Kotlin coroutines operational envelope\n\nThe relevant code crosses developer tools, Java, WebGL. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"NorthstarOrbitSyncService occasionally exhibits two validators with subtly different error strings, but only after a reconnect. Follow the data and cancellation paths in projects/northstar/infra/modules/edge/main.tf and identify the cause before changing anything.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"En projects/northstar/config/staging.toml, NorthstarNovaPickerStore tiene un problema intermitente en el flujo de GraphQL. Propón fases, compatibilidad, métricas, rollback y ownership; detente antes de tocar código.\n\nRestricciones:\n- seguir con GraphQL\n- conservar compatibilidad y cancelación\n- limitar el cambio a NorthstarNovaPickerStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con GraphQL alrededor de NorthstarNovaPickerStore.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"es"} +{"prompt":"Locally: The NorthstarQuartzPlayerStore surface in projects/northstar/services/ledger/replay.go 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":"NorthstarAtlasSearchService's metric is misspelled as succesful_total in one declaration. Correct that literal and its exact test expectation, without renaming anything else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Production: The API work is done; what remains for NorthstarPineMetricsService is the visible interaction layer across loading, offline, empty, and success cases. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarPineMetricsService\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Staging: The NorthstarSlateEditorService empty state in projects/northstar/ml/pipeline/features.py needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-54114\n\n08:02 deploy NorthstarSableParserFlow 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 NorthstarSableParserFlow 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":"Is NorthstarVelaDrawerStore safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"CI: The NorthstarAmberFilterStore surface in projects/northstar/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":"Investigate the NorthstarBasilRunnerService hang","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Atlas: Incident timeline — INC-54130\n\n08:02 deploy NorthstarDriftConsoleFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current NorthstarDriftConsoleFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current NorthstarOpalRouterService design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarOpalRouterService\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"What does NorthstarFlintTimelineStore own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-54121: retire the legacy replay path for NorthstarMicaProfileFlow\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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Capture the NorthstarMicaProfileFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"NorthstarNimbusFormCoordinator: correct, then assess","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Beacon: The minimum supported Cloudflare Workers version in projects/northstar/engine/render/atlas.cpp 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":"NorthstarAmberFilterCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"diff --git a/projects/northstar/packages/api/openapi.yaml b/projects/northstar/packages/api/openapi.yaml\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/packages/api/openapi.yaml\n+++ b/projects/northstar/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\nRestructure NorthstarMapleQueueFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"NorthstarSlateEditorCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Test Suite 'NorthstarPineMetricsCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[NorthstarPineMetricsCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/northstar/packages/api/openapi.yaml:144: error: -[NorthstarPineMetricsCoordinatorTests 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 '-[NorthstarPineMetricsCoordinatorTests 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 NorthstarPineMetricsCoordinator's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"What sequence would let NorthstarAmberFilterService adopt Cloudflare Workers 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.8,"slice":"core","lang":"en"} +{"prompt":"Set NorthstarLumenChartStore's port to 8081","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"For NorthstarWillowCodecCoordinator, separate NorthstarWillowCodecCoordinator's policy from transport without behavior changes; once that is complete, capture the contract and rollback note for consumers. Work from projects/northstar/src/sync/reconcile.ts, stay with Kotlin coroutines, and make rollback possible without deleting user data. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Cinder: Incident timeline — INC-54152\n\n08:02 deploy NorthstarCedarPolicyCoordinator 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 NorthstarCedarPolicyCoordinator 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":"Delta: diff --git a/projects/northstar/infra/modules/edge/main.tf b/projects/northstar/infra/modules/edge/main.tf\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/infra/modules/edge/main.tf\n+++ b/projects/northstar/infra/modules/edge/main.tf\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is NorthstarOrbitSyncFlow'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":"Documente o contrato de NorthstarEmberRelayService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"pt"} +{"prompt":"NorthstarMapleQueueService leaks tasks on shutdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"The name pendingAck means two different things across NorthstarHarborIndexStore's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Design handed over a final pass for NorthstarTideWorkerStore, and the basic data flow in projects/northstar/workers/thumbnail/consumer.ex already works. 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- make rollback possible without deleting user data\n- stay compatible with the existing Cloudflare Workers deployment\n- keep the work scoped to NorthstarTideWorkerStore and its direct tests\n\nSeveral teams work in this developer tools, Java, WebGL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Move NorthstarVelaDrawerService behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"NorthstarCinderAuthCoordinator: diagnose, then correct","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"NorthstarSlateEditorStore's metric is misspelled as succesful_total in one declaration. Correct that literal and its exact test expectation, without renaming anything else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Ember: What is the safest way to split projects/northstar/apps/console/routes/usage.svelte into independently owned modules while NorthstarRainfallDBStore's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"NorthstarSableParserCoordinator is blocking the next release because an accessibility label that reads the internal enum. I need two concrete outcomes from a single pass: change NorthstarSableParserCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing Cloudflare Workers conventions in projects/northstar/engine/render/atlas.cpp; make rollback possible without deleting user data. 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":"Security flagged NorthstarGarnetModalStore for a read-only pass because its GraphQL boundary mixes tenant data, retries, and cancellation in subtle ways. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current GraphQL operational envelope\n\nThe relevant code crosses developer tools, Java, WebGL. Prefer evidence from the repository and make any assumption explicit.\n\nNothing is reported broken, so judge and explain current behavior without inventing a failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-54129: retire the legacy replay path for NorthstarEchoRegistryFlow\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À partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Assess NorthstarEchoRegistryFlow for durability, tenant isolation, races, and misleading observability. Separate blockers from questions and do not produce a patch.","purpose":"planning","secondary":"review","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Corrige le timeout de NorthstarEmberRelayStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"fr"} +{"prompt":"// projects/northstar/services/ledger/replay.go\nfinal class NorthstarDeltaCanvasFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 NorthstarDeltaCanvasFlow; 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":"NorthstarEmberRelayCoordinator needs a paired pass: assess ownership and failure handling in projects/northstar/cmd/exporter/main.py, plus capture the contract and rollback note for consumers. Use projects/northstar/cmd/exporter/main.py as the source of truth, preserve the Kafka contract, and avoid unrelated cleanup.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"We expect NorthstarCraneWorkspaceService to outgrow its current Kotlin coroutines arrangement next quarter, but changing everything at once would be risky. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- make rollback possible without deleting user data\n- stay compatible with the existing Kotlin coroutines deployment\n- keep the work scoped to NorthstarCraneWorkspaceService and its direct tests\n\nSeveral teams work in this developer tools, Java, WebGL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"projects/northstar/services/ledger/replay.go 里的 NorthstarSummitProxyService 最近在 Spring Boot 流程中出现间歇性问题。 请实现幂等 endpoint，包含持久 cursor、tenant 鉴权、spans 和 retry 测试。\n\n约束：\n- 继续使用 Spring Boot\n- 保持兼容性和取消语义\n- 改动只限于 NorthstarSummitProxyService","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} {"prompt":"NorthstarVelaDrawerCoordinator needs a paired pass: separate NorthstarVelaDrawerCoordinator's policy from transport without behavior changes, plus give the existing implementation a read-only safety pass. Use projects/northstar/app/src/main/SyncWorker.kt as the source of truth, preserve the Kotlin coroutines contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Document NorthstarSableParserService's cancellation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Frost: Ticket OPS-54111: retire the legacy replay path for NorthstarNovaPickerFlow\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 NorthstarNovaPickerFlow 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.77,"slice":"pasted-context","lang":"en"} +{"prompt":"Document NorthstarSableParserService's cancellation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Frost: Ticket OPS-54111: retire the legacy replay path for NorthstarNovaPickerFlow\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 NorthstarNovaPickerFlow 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":"Garnet: projects/northstar/app/src/main/SyncWorker.kt の NorthstarWrenExportService で、Kotlin coroutines の flow に断続的な問題が起きています。 責務を分離して重複をなくし、API、wire value、順序、観測可能な動作は変えないでください。\n\n制約:\n- Kotlin coroutines を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は NorthstarWrenExportService のみ","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"ja"} -{"prompt":"Persist NorthstarQuartzPlayerService delivery attempts in projects/northstar/web/components/FilterDrawer.vue, claim them safely across workers, and make duplicate webhook receipts return the original accepted result.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"diff --git a/projects/northstar/app/src/main/SyncWorker.kt b/projects/northstar/app/src/main/SyncWorker.kt\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/app/src/main/SyncWorker.kt\n+++ b/projects/northstar/app/src/main/SyncWorker.kt\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure NorthstarWrenExportFlow 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.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Flip NorthstarMicaProfileStore's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"boundary","lang":"en"} -{"prompt":"Fresh release brief for NorthstarPrismCacheCoordinator:\n- primary outcome: produce a consumer guide for NorthstarPrismCacheCoordinator\n- companion outcome: give the existing implementation a read-only safety pass\n- repository entry point: projects/northstar/app/src/main/SyncWorker.kt\n- platform constraint: Kotlin coroutines\n- known complication: timestamps rendered one day ahead near UTC midnight\n\nBoth results are required, but they should remain independently reviewable. Make rollback possible without deleting user data; 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":"writing","secondary":"review","mixed":true,"difficulty":0.67,"slice":"mixed","lang":"en"} -{"prompt":"Move NorthstarMoonlitSDKService behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Harbor: Ticket OPS-54159: retire the legacy replay path for NorthstarTideWorkerCoordinator\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for NorthstarTideWorkerCoordinator, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.67,"slice":"pasted-context","lang":"en"} -{"prompt":"The name pendingAck means two different things across NorthstarMarbleTokenStore's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Iris: projects/northstar/lib/codec/frame.cc now contains NorthstarAcornWidgetStore'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.63,"slice":"boundary","lang":"en"} +{"prompt":"Persist NorthstarQuartzPlayerService delivery attempts in projects/northstar/web/components/FilterDrawer.vue, 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":"diff --git a/projects/northstar/app/src/main/SyncWorker.kt b/projects/northstar/app/src/main/SyncWorker.kt\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/app/src/main/SyncWorker.kt\n+++ b/projects/northstar/app/src/main/SyncWorker.kt\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure NorthstarWrenExportFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Flip NorthstarMicaProfileStore's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fresh release brief for NorthstarPrismCacheCoordinator:\n- primary outcome: produce a consumer guide for NorthstarPrismCacheCoordinator\n- companion outcome: give the existing implementation a read-only safety pass\n- repository entry point: projects/northstar/app/src/main/SyncWorker.kt\n- platform constraint: Kotlin coroutines\n- known complication: timestamps rendered one day ahead near UTC midnight\n\nBoth results are required, but they should remain independently reviewable. Make rollback possible without deleting user data; 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":"writing","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Move NorthstarMoonlitSDKService behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Harbor: Ticket OPS-54159: retire the legacy replay path for NorthstarTideWorkerCoordinator\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for NorthstarTideWorkerCoordinator, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"The name pendingAck means two different things across NorthstarMarbleTokenStore's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Iris: projects/northstar/lib/codec/frame.cc now contains NorthstarAcornWidgetStore'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":"This should remain a deliberately small patch: NorthstarCedarPolicyService has one known configuration mistake in projects/northstar/Sources/CLI/Commands/Doctor.swift, not an open-ended failure investigation. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- make rollback possible without deleting user data\n- stay compatible with the existing Kafka deployment\n- keep the work scoped to NorthstarCedarPolicyService and its direct tests\n\nSeveral teams work in this developer tools, Java, WebGL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Juniper: diff --git a/projects/northstar/db/migrations/20260730_events.sql b/projects/northstar/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/db/migrations/20260730_events.sql\n+++ b/projects/northstar/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is NorthstarWillowCodecFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.82,"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_54145'\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_54145'::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\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Find the source of this NorthstarQuartzPlayerFlow 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.87,"slice":"pasted-context","lang":"zh"} -{"prompt":"Kestrel: The public surface of NorthstarCloudReconcilerService is frozen, but its internal ownership in projects/northstar/ml/pipeline/features.py is difficult to test and even harder to change safely. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarCloudReconcilerService\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Animate the NorthstarCinderAuthService drawer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"core","lang":"en"} -{"prompt":"NorthstarMarbleTokenCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"vague-eval","lang":"en"} -{"prompt":"NorthstarTideWorkerService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Cloudflare Workers operational envelope\n\nThe relevant code crosses developer tools, Java, WebGL. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Lumen: Ticket OPS-54157: retire the legacy replay path for NorthstarCloudReconcilerCoordinator\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 NorthstarCloudReconcilerCoordinator behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"Maple: What sequence would let NorthstarCloudReconcilerStore adopt Kafka 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.67,"slice":"core","lang":"en"} -{"prompt":"Nimbus: # projects/northstar/apps/console/routes/usage.svelte\n[worker.northstarveladrawerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.northstarveladrawerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.northstarveladrawerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.NorthstarVelaDrawerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-54133\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/northstar/apps/console/routes/usage.svelte. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.41,"slice":"pasted-context","lang":"en"} -{"prompt":"UI ticket DES-54154: finish the compact NorthstarHarborIndexCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/northstar/lib/codec/frame.cc\nFramework: Cloudflare Workers\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring NorthstarHarborIndexCoordinator'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.78,"slice":"pasted-context","lang":"en"} -{"prompt":"NorthstarIrisBatchStore's staging timeout is already known to be wrong: change the single projects/northstar/db/migrations/20260730_events.sql value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"boundary","lang":"en"} -{"prompt":"Incident timeline — INC-54134\n\n08:02 deploy NorthstarMarbleTokenFlow 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 NorthstarMarbleTokenFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"Ticket OPS-54119: retire the legacy replay path for NorthstarRavenSessionFlow\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 NorthstarRavenSessionFlow 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.67,"slice":"pasted-context","lang":"en"} -{"prompt":"NorthstarIrisBatchCoordinator: smooth out this interaction","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"vague-eval","lang":"en"} -{"prompt":"NorthstarSummitProxyCoordinator: ship a sensible version","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"vague-eval","lang":"en"} -{"prompt":"Opal: projects/northstar/Sources/CLI/Commands/Doctor.swift has grown through several launches, and NorthstarOspreyJobStore now mixes policy, transport, persistence, and metrics in one place. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- make rollback possible without deleting user data\n- stay compatible with the existing Kafka deployment\n- keep the work scoped to NorthstarOspreyJobStore and its direct tests\n\nSeveral teams work in this developer tools, Java, WebGL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.74,"slice":"boundary","lang":"en"} -{"prompt":"Prism: projects/northstar/apps/console/routes/usage.svelte 里的 NorthstarWrenExportStore 最近在 Kotlin coroutines 流程中出现间歇性问题。 请完成 responsive layout、空状态、retry、键盘焦点、dark mode 和 reduced motion。\n\n约束：\n- 继续使用 Kotlin coroutines\n- 保持兼容性和取消语义\n- 改动只限于 NorthstarWrenExportStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"zh"} -{"prompt":"Clarify NorthstarSpruceDaemonStore's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"boundary","lang":"en"} -{"prompt":"Quartz: The NorthstarBeaconStoreService surface in projects/northstar/config/staging.toml 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.35,"slice":"core","lang":"en"} -{"prompt":"diff --git a/projects/northstar/cmd/exporter/main.py b/projects/northstar/cmd/exporter/main.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/cmd/exporter/main.py\n+++ b/projects/northstar/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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Deliver the NorthstarAtlasSearchFlow 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.86,"slice":"pasted-context","lang":"pt"} -{"prompt":"Raven: projects/northstar/config/staging.toml の NorthstarPineMetricsFlow で、GraphQL の flow に断続的な問題が起きています。 現在の flow を読み、ownership、cancel、順序が安全か評価してください。分析だけで十分です。\n\n制約:\n- GraphQL を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は NorthstarPineMetricsFlow のみ","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"ja"} -{"prompt":"Sable: The first NorthstarPineMetricsStore request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"For NorthstarSpruceDaemonCoordinator, assess ownership and failure handling in projects/northstar/services/ledger/replay.go; once that is complete, capture the contract and rollback note for consumers. Work from projects/northstar/services/ledger/replay.go, stay with Spring Boot, and make rollback possible without deleting user data. Keep the two outcomes separately reviewable.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"Draft NorthstarDeltaCanvasService's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"Two asks around NorthstarEchoRegistryCoordinator: (1) finish NorthstarEchoRegistryCoordinator's responsive empty and retry states; (2) capture the contract and rollback note for consumers. Make rollback possible without deleting user data, and leave a clear boundary between the resulting artifacts or edits.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.64,"slice":"mixed","lang":"en"} -{"prompt":"Test Suite 'NorthstarLedgerGateFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[NorthstarLedgerGateFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/northstar/ui/settings/PrivacyPane.tsx:144: error: -[NorthstarLedgerGateFlowTests 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 '-[NorthstarLedgerGateFlowTests 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\nFinish the visible NorthstarLedgerGateFlow 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.78,"slice":"pasted-context","lang":"en"} -{"prompt":"The minimum supported Kotlin coroutines version in projects/northstar/src/sync/reconcile.ts is one patch behind the lockfile. Align that single value and regenerate only the affected metadata.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"core","lang":"en"} -{"prompt":"Is there a cleaner way to separate NorthstarCloudReconcilerFlow'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.58,"slice":"boundary","lang":"en"} -{"prompt":"NorthstarAtlasSearchCoordinator: make the api less awkward","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"vague-eval","lang":"en"} -{"prompt":"Introduce a durable deduplication key for NorthstarCraneWorkspaceFlow events and enforce it in both the database migration and the ingestion path.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"Tide: The API work is done; what remains for NorthstarCraneWorkspaceStore is the visible interaction layer across loading, offline, empty, and success cases. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarCraneWorkspaceStore\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"boundary","lang":"en"} -{"prompt":"Split NorthstarFlintTimelineService without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Before we approve NorthstarFernSnapshotService, assess whether an empty state that flashes before cached data arrives is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Fresh release brief for NorthstarOpalRouterCoordinator:\n- primary outcome: lay out a staged migration for NorthstarOpalRouterCoordinator\n- companion outcome: then implement the bounded durable-cursor handler\n- repository entry point: projects/northstar/infra/modules/edge/main.tf\n- platform constraint: Spring Boot\n- known complication: an empty state that flashes before cached data arrives\n\nBoth results are required, but they should remain independently reviewable. Make rollback possible without deleting user data; retain serialization and authorization boundaries; cover cancellation, idempotent retries, and rollback; and avoid drive-by cleanup. Use the code as the source of truth, call out assumptions, and state how an on-call engineer can tell that either part is unsafe to ship.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.88,"slice":"mixed","lang":"en"} -{"prompt":"NorthstarRainfallDBFlow returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/northstar/app/src/main/SyncWorker.kt and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"projects/northstar/infra/modules/edge/main.tf now contains NorthstarJuniperCLIFlow'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.53,"slice":"boundary","lang":"en"} -{"prompt":"NorthstarRavenSessionService est-il sûr ?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"fr"} -{"prompt":"Ticket OPS-54153: retire the legacy replay path for NorthstarRainfallDBCoordinator\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 を維持し、根拠と判断を明確にしてください。 Assess NorthstarRainfallDBCoordinator 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.82,"slice":"pasted-context","lang":"ja"} -{"prompt":"Responsive layout for NorthstarKiteSchedulerStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"boundary","lang":"en"} -{"prompt":"Find NorthstarDriftConsoleService's duplicate retry source","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Umbra: Ticket OPS-54127: retire the legacy replay path for NorthstarEmberRelayFlow\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 NorthstarEmberRelayFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.62,"slice":"pasted-context","lang":"en"} -{"prompt":"NorthstarFrostPanelCoordinator: take care of the warning","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"vague-eval","lang":"en"} -{"prompt":"PM is preparing the NorthstarPrismCacheService rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarPrismCacheService\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Split projects/northstar/workers/thumbnail/consumer.ex by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"projects/northstar/pkg/cache/lease.rs now contains NorthstarFrostPanelService'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.55,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-54136\n\n08:02 deploy NorthstarMosaicGridFlow 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 NorthstarMosaicGridFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.59,"slice":"pasted-context","lang":"en"} -{"prompt":"Introduce a durable deduplication key for NorthstarCoralUploadService events and enforce it in both the database migration and the ingestion path.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Sequence NorthstarNimbusFormStore's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Move NorthstarBeaconStoreStore'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.55,"slice":"boundary","lang":"en"} -{"prompt":"Vela: Ticket OPS-54123: retire the legacy replay path for NorthstarLumenChartFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for NorthstarLumenChartFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.65,"slice":"pasted-context","lang":"en"} -{"prompt":"Test Suite 'NorthstarPrismCacheFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[NorthstarPrismCacheFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/northstar/apps/console/routes/usage.svelte:144: error: -[NorthstarPrismCacheFlowTests 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 '-[NorthstarPrismCacheFlowTests 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\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Finish the visible NorthstarPrismCacheFlow 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.76,"slice":"pasted-context","lang":"es"} -{"prompt":"Walk through NorthstarBasilRunnerStore's segment.rs","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"diff --git a/projects/northstar/web/components/FilterDrawer.vue b/projects/northstar/web/components/FilterDrawer.vue\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/web/components/FilterDrawer.vue\n+++ b/projects/northstar/web/components/FilterDrawer.vue\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure NorthstarSpruceDaemonFlow 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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"NorthstarAcornWidgetCoordinator: handle the lingering thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"vague-eval","lang":"en"} -{"prompt":"For NorthstarMapleQueueCoordinator, produce a consumer guide for NorthstarMapleQueueCoordinator; once that is complete, give the existing implementation a read-only safety pass. Work from projects/northstar/config/staging.toml, stay with GraphQL, and make rollback possible without deleting user data. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.45,"slice":"mixed","lang":"en"} -{"prompt":"NorthstarGarnetModalCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.45,"slice":"mixed","lang":"en"} -{"prompt":"Ownership of NorthstarJuniperCLIService is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Spring Boot operational envelope\n\nThe relevant code crosses developer tools, Java, WebGL. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"On compact widths, NorthstarCedarPolicyStore'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.49,"slice":"core","lang":"en"} -{"prompt":"Two asks around NorthstarBasilRunnerCoordinator: (1) separate NorthstarBasilRunnerCoordinator's policy from transport without behavior changes; (2) correct the known stale timeout beside it. Make rollback possible without deleting user data, and leave a clear boundary between the resulting artifacts or edits.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"NorthstarFernSnapshotCoordinator: untangle the messy bit","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"vague-eval","lang":"en"} -{"prompt":"Design the NorthstarGarnetModalService rollback","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Willow: Two deliverables are holding up NorthstarDeltaCanvasCoordinator. First, produce a consumer guide for NorthstarDeltaCanvasCoordinator. In the same workstream, correct the known stale timeout beside it. The relevant starting point is projects/northstar/web/components/FilterDrawer.vue, which follows Spring Boot conventions and currently suffers from lease renewal code copied across three workers. Make rollback possible without deleting user data.\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":"writing","secondary":"quickFix","mixed":true,"difficulty":0.59,"slice":"mixed","lang":"en"} -{"prompt":"NorthstarJuniperCLIStore 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.53,"slice":"core","lang":"en"} -{"prompt":"Give NorthstarWillowCodecService a loading skeleton","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} -{"prompt":"NorthstarMosaicGridCoordinator: check the suspicious part","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"vague-eval","lang":"en"} -{"prompt":"NorthstarOrbitSyncCoordinator: sort out the rough edge","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"vague-eval","lang":"en"} -{"prompt":"NorthstarWrenExportCoordinator: give it a nicer flow","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"vague-eval","lang":"en"} -{"prompt":"The minimum supported GraphQL version in projects/northstar/pkg/cache/lease.rs is one patch behind the lockfile. Align that single value and regenerate only the affected metadata.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"boundary","lang":"en"} -{"prompt":"Read projects/northstar/pkg/cache/lease.rs and tell me whether NorthstarAsterWebhookFlow can acknowledge work before its durable write completes; this is a read-only safety pass. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"NorthstarBeaconStoreCoordinator: something is off here","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"Xylem: # projects/northstar/services/ledger/replay.go\n[worker.northstarsummitproxyflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.northstarsummitproxyflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.northstarsummitproxyflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.NorthstarSummitProxyFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-54135\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 NorthstarSummitProxyFlow'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.33,"slice":"pasted-context","lang":"en"} -{"prompt":"Spell NorthstarNimbusFormService's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"core","lang":"en"} -{"prompt":"NorthstarLedgerGateCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"vague-eval","lang":"en"} -{"prompt":"Yarrow: # projects/northstar/services/ledger/replay.go\n[worker.northstarcopperbridgecoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.northstarcopperbridgecoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.northstarcopperbridgecoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.NorthstarCopperBridgeCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-54155\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/northstar/services/ledger/replay.go and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"pasted-context","lang":"en"} -{"prompt":"Zephyr: The behavior of NorthstarOpalRouterStore is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/northstar/infra/modules/edge/main.tf. 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- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Spring Boot operational envelope\n\nThe relevant code crosses developer tools, Java, WebGL. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.49,"slice":"boundary","lang":"en"} -{"prompt":"En projects/northstar/app/src/main/SyncWorker.kt, NorthstarRainfallDBService tiene un problema intermitente en el flujo de Kotlin coroutines. Separa responsabilidades y elimina duplicación, conservando API, wire values, orden y comportamiento observable.\n\nRestricciones:\n- seguir con Kotlin coroutines\n- conservar compatibilidad y cancelación\n- limitar el cambio a NorthstarRainfallDBService","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"es"} -{"prompt":"Checkout: // projects/northstar/engine/render/atlas.cpp\nfinal class NorthstarAcornWidgetFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 NorthstarAcornWidgetFlow'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.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current NorthstarSableParserStore design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarSableParserStore\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.\n\nNothing is reported broken, so judge and explain current behavior without inventing a failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"boundary","lang":"en"} -{"prompt":"Remove NorthstarDriftConsoleStore's stray comma","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"boundary","lang":"en"} -{"prompt":"NorthstarMicaProfileCoordinator: ship, then assess","purpose":"backendImpl","secondary":"review","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Add a bounded NorthstarHarborIndexFlow export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Two engineers disagree about whether NorthstarCopperBridgeStore's cache is authoritative. Walk the reads and writes in projects/northstar/services/ledger/replay.go and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Exporter: // projects/northstar/Sources/App/SessionStore.swift\nfinal class NorthstarOspreyJobFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 NorthstarOspreyJobFlow 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Scheduler: Two asks around NorthstarKiteSchedulerCoordinator: (1) assess ownership and failure handling in projects/northstar/Sources/CLI/Commands/Doctor.swift; (2) capture the contract and rollback note for consumers. Make rollback possible without deleting user data, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"Dashboard: # projects/northstar/cmd/exporter/main.py\n[worker.northstarmoonlitsdkflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.northstarmoonlitsdkflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.northstarmoonlitsdkflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.NorthstarMoonlitSDKFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-54117\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 NorthstarMoonlitSDKFlow'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.38,"slice":"pasted-context","lang":"en"} -{"prompt":"Where did NorthstarCinderAuthStore's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"boundary","lang":"en"} -{"prompt":"Release engineering needs a NorthstarAsterWebhookStore changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"diff --git a/projects/northstar/ml/pipeline/features.py b/projects/northstar/ml/pipeline/features.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/ml/pipeline/features.py\n+++ b/projects/northstar/ml/pipeline/features.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 NorthstarSlateEditorFlow'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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"NorthstarRavenSessionCoordinator: ship, then correct","purpose":"backendImpl","secondary":"quickFix","mixed":true,"difficulty":0.77,"slice":"mixed","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_54124'\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_54124'::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\nFind the source of this NorthstarBirchMigratorFlow 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.96,"slice":"pasted-context","lang":"en"} -{"prompt":"NorthstarAsterWebhookService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current GraphQL operational envelope\n\nThe relevant code crosses developer tools, Java, WebGL. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"NorthstarCoralUploadCoordinator: clean up that old path","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"vague-eval","lang":"en"} -{"prompt":"NorthstarDriftConsoleCoordinator needs a paired pass: produce a consumer guide for NorthstarDriftConsoleCoordinator, plus correct the known stale timeout beside it. Use projects/northstar/infra/modules/edge/main.tf as the source of truth, preserve the Spring Boot contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.43,"slice":"mixed","lang":"en"} -{"prompt":"NorthstarNovaPickerCoordinator is blocking the next release because a flaky snapshot caused by locale-dependent sorting. I need two concrete outcomes from a single pass: separate NorthstarNovaPickerCoordinator's policy from transport without behavior changes, and correct the known stale timeout beside it. Use the existing GraphQL conventions in projects/northstar/config/staging.toml; make rollback possible without deleting user data. 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":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"Support wants the behavior in projects/northstar/ui/settings/PrivacyPane.tsx recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Before touching projects/northstar/src/sync/reconcile.ts, 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":"boundary","lang":"en"} -{"prompt":"Map NorthstarLumenChartService's ownership split","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"The behavior of NorthstarOspreyJobService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/northstar/Sources/App/SessionStore.swift. 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- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Kafka operational envelope\n\nThe relevant code crosses developer tools, Java, WebGL. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Em projects/northstar/web/components/FilterDrawer.vue, o NorthstarSummitProxyStore tem um problema intermitente no fluxo de Spring Boot. Leia o fluxo atual e avalie ownership, cancelamento e ordem; preciso apenas da análise.\n\nRestrições:\n- continuar com Spring Boot\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao NorthstarSummitProxyStore","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"pt"} -{"prompt":"Incident timeline — INC-54142\n\n08:02 deploy NorthstarCoralUploadFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current NorthstarCoralUploadFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"$ pnpm test --filter NorthstarFlintTimelineFlow\n RUN v3.2.4 /workspace/apps/console\n × NorthstarFlintTimelineFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=54120 phase=resume storedCursor=seg-0183\n session=54120 phase=fetch requestCursor=seg-0183 pageSize=200\n session=54120 phase=commit receivedCursor=seg-0184 itemCount=0\n session=54120 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nReconstruct the NorthstarFlintTimelineFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.87,"slice":"pasted-context","lang":"en"} +{"prompt":"Juniper: diff --git a/projects/northstar/db/migrations/20260730_events.sql b/projects/northstar/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/db/migrations/20260730_events.sql\n+++ b/projects/northstar/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is NorthstarWillowCodecFlow'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":"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_54145'\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_54145'::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\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Find the source of this NorthstarQuartzPlayerFlow symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Kestrel: The public surface of NorthstarCloudReconcilerService is frozen, but its internal ownership in projects/northstar/ml/pipeline/features.py is difficult to test and even harder to change safely. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarCloudReconcilerService\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Animate the NorthstarCinderAuthService drawer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"NorthstarMarbleTokenCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"NorthstarTideWorkerService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Cloudflare Workers operational envelope\n\nThe relevant code crosses developer tools, Java, WebGL. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Lumen: Ticket OPS-54157: retire the legacy replay path for NorthstarCloudReconcilerCoordinator\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 NorthstarCloudReconcilerCoordinator 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":"Maple: What sequence would let NorthstarCloudReconcilerStore adopt Kafka 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.8,"slice":"core","lang":"en"} +{"prompt":"Nimbus: # projects/northstar/apps/console/routes/usage.svelte\n[worker.northstarveladrawerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.northstarveladrawerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.northstarveladrawerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.NorthstarVelaDrawerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-54133\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/northstar/apps/console/routes/usage.svelte. 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":"UI ticket DES-54154: finish the compact NorthstarHarborIndexCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/northstar/lib/codec/frame.cc\nFramework: Cloudflare Workers\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring NorthstarHarborIndexCoordinator'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":"NorthstarIrisBatchStore's staging timeout is already known to be wrong: change the single projects/northstar/db/migrations/20260730_events.sql value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-54134\n\n08:02 deploy NorthstarMarbleTokenFlow 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 NorthstarMarbleTokenFlow 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":"Ticket OPS-54119: retire the legacy replay path for NorthstarRavenSessionFlow\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 NorthstarRavenSessionFlow 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":"NorthstarIrisBatchCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"NorthstarSummitProxyCoordinator: ship a sensible version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Opal: projects/northstar/Sources/CLI/Commands/Doctor.swift has grown through several launches, and NorthstarOspreyJobStore now mixes policy, transport, persistence, and metrics in one place. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- make rollback possible without deleting user data\n- stay compatible with the existing Kafka deployment\n- keep the work scoped to NorthstarOspreyJobStore and its direct tests\n\nSeveral teams work in this developer tools, Java, WebGL 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":"Prism: projects/northstar/apps/console/routes/usage.svelte 里的 NorthstarWrenExportStore 最近在 Kotlin coroutines 流程中出现间歇性问题。 请完成 responsive layout、空状态、retry、键盘焦点、dark mode 和 reduced motion。\n\n约束：\n- 继续使用 Kotlin coroutines\n- 保持兼容性和取消语义\n- 改动只限于 NorthstarWrenExportStore","purpose":"frontendImpl","secondary":"debugging","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"zh"} +{"prompt":"Clarify NorthstarSpruceDaemonStore's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Quartz: The NorthstarBeaconStoreService surface in projects/northstar/config/staging.toml 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":"diff --git a/projects/northstar/cmd/exporter/main.py b/projects/northstar/cmd/exporter/main.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/cmd/exporter/main.py\n+++ b/projects/northstar/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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Deliver the NorthstarAtlasSearchFlow server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Raven: projects/northstar/config/staging.toml の NorthstarPineMetricsFlow で、GraphQL の flow に断続的な問題が起きています。 現在の flow を読み、ownership、cancel、順序が安全か評価してください。分析だけで十分です。\n\n制約:\n- GraphQL を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は NorthstarPineMetricsFlow のみ","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"} +{"prompt":"Sable: The first NorthstarPineMetricsStore request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"For NorthstarSpruceDaemonCoordinator, assess ownership and failure handling in projects/northstar/services/ledger/replay.go; once that is complete, capture the contract and rollback note for consumers. Work from projects/northstar/services/ledger/replay.go, stay with Spring Boot, and make rollback possible without deleting user data. Keep the two outcomes separately reviewable.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Draft NorthstarDeltaCanvasService's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Two asks around NorthstarEchoRegistryCoordinator: (1) finish NorthstarEchoRegistryCoordinator's responsive empty and retry states; (2) capture the contract and rollback note for consumers. Make rollback possible without deleting user data, and leave a clear boundary between the resulting artifacts or edits.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Test Suite 'NorthstarLedgerGateFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[NorthstarLedgerGateFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/northstar/ui/settings/PrivacyPane.tsx:144: error: -[NorthstarLedgerGateFlowTests 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 '-[NorthstarLedgerGateFlowTests 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\nFinish the visible NorthstarLedgerGateFlow 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":"The minimum supported Kotlin coroutines version in projects/northstar/src/sync/reconcile.ts 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":"Is there a cleaner way to separate NorthstarCloudReconcilerFlow'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":"NorthstarAtlasSearchCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Introduce a durable deduplication key for NorthstarCraneWorkspaceFlow 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":"Tide: The API work is done; what remains for NorthstarCraneWorkspaceStore is the visible interaction layer across loading, offline, empty, and success cases. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarCraneWorkspaceStore\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Split NorthstarFlintTimelineService without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Before we approve NorthstarFernSnapshotService, assess whether an empty state that flashes before cached data arrives is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Fresh release brief for NorthstarOpalRouterCoordinator:\n- primary outcome: lay out a staged migration for NorthstarOpalRouterCoordinator\n- companion outcome: then implement the bounded durable-cursor handler\n- repository entry point: projects/northstar/infra/modules/edge/main.tf\n- platform constraint: Spring Boot\n- known complication: an empty state that flashes before cached data arrives\n\nBoth results are required, but they should remain independently reviewable. Make rollback possible without deleting user data; retain serialization and authorization boundaries; cover cancellation, idempotent retries, and rollback; and avoid drive-by cleanup. Use the code as the source of truth, call out assumptions, and state how an on-call engineer can tell that either part is unsafe to ship.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"NorthstarRainfallDBFlow returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/northstar/app/src/main/SyncWorker.kt and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"projects/northstar/infra/modules/edge/main.tf now contains NorthstarJuniperCLIFlow'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":"NorthstarRavenSessionService est-il sûr ?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"fr"} +{"prompt":"Ticket OPS-54153: retire the legacy replay path for NorthstarRainfallDBCoordinator\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 を維持し、根拠と判断を明確にしてください。 Assess NorthstarRainfallDBCoordinator 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":"Responsive layout for NorthstarKiteSchedulerStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Find NorthstarDriftConsoleService's duplicate retry source","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Umbra: Ticket OPS-54127: retire the legacy replay path for NorthstarEmberRelayFlow\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 NorthstarEmberRelayFlow 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":"NorthstarFrostPanelCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"PM is preparing the NorthstarPrismCacheService rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarPrismCacheService\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Split projects/northstar/workers/thumbnail/consumer.ex by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"projects/northstar/pkg/cache/lease.rs now contains NorthstarFrostPanelService'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.4,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-54136\n\n08:02 deploy NorthstarMosaicGridFlow 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 NorthstarMosaicGridFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Introduce a durable deduplication key for NorthstarCoralUploadService 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":"Sequence NorthstarNimbusFormStore's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Move NorthstarBeaconStoreStore'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":"Vela: Ticket OPS-54123: retire the legacy replay path for NorthstarLumenChartFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for NorthstarLumenChartFlow, 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":"Test Suite 'NorthstarPrismCacheFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[NorthstarPrismCacheFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/northstar/apps/console/routes/usage.svelte:144: error: -[NorthstarPrismCacheFlowTests 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 '-[NorthstarPrismCacheFlowTests 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\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Finish the visible NorthstarPrismCacheFlow state described above: responsive layout, correct selection restoration, keyboard focus, accessible labels, dark mode, and reduced-motion behavior.","purpose":"debugging","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Walk through NorthstarBasilRunnerStore's segment.rs","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/northstar/web/components/FilterDrawer.vue b/projects/northstar/web/components/FilterDrawer.vue\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/web/components/FilterDrawer.vue\n+++ b/projects/northstar/web/components/FilterDrawer.vue\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure NorthstarSpruceDaemonFlow 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":"NorthstarAcornWidgetCoordinator: handle the lingering thing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"For NorthstarMapleQueueCoordinator, produce a consumer guide for NorthstarMapleQueueCoordinator; once that is complete, give the existing implementation a read-only safety pass. Work from projects/northstar/config/staging.toml, stay with GraphQL, and make rollback possible without deleting user data. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"NorthstarGarnetModalCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Ownership of NorthstarJuniperCLIService is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Spring Boot operational envelope\n\nThe relevant code crosses developer tools, Java, WebGL. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"On compact widths, NorthstarCedarPolicyStore'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":"Two asks around NorthstarBasilRunnerCoordinator: (1) separate NorthstarBasilRunnerCoordinator's policy from transport without behavior changes; (2) correct the known stale timeout beside it. Make rollback possible without deleting user data, and leave a clear boundary between the resulting artifacts or edits.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"NorthstarFernSnapshotCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Design the NorthstarGarnetModalService rollback","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Willow: Two deliverables are holding up NorthstarDeltaCanvasCoordinator. First, produce a consumer guide for NorthstarDeltaCanvasCoordinator. In the same workstream, correct the known stale timeout beside it. The relevant starting point is projects/northstar/web/components/FilterDrawer.vue, which follows Spring Boot conventions and currently suffers from lease renewal code copied across three workers. Make rollback possible without deleting user data.\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":"writing","secondary":"quickFix","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"NorthstarJuniperCLIStore 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":"Give NorthstarWillowCodecService a loading skeleton","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"NorthstarMosaicGridCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"NorthstarOrbitSyncCoordinator: sort out the rough edge","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"NorthstarWrenExportCoordinator: give it a nicer flow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"The minimum supported GraphQL version in projects/northstar/pkg/cache/lease.rs 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":"Read projects/northstar/pkg/cache/lease.rs and tell me whether NorthstarAsterWebhookFlow can acknowledge work before its durable write completes; this is a read-only safety pass. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"NorthstarBeaconStoreCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Xylem: # projects/northstar/services/ledger/replay.go\n[worker.northstarsummitproxyflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.northstarsummitproxyflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.northstarsummitproxyflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.NorthstarSummitProxyFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-54135\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 NorthstarSummitProxyFlow'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":"Spell NorthstarNimbusFormService's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"NorthstarLedgerGateCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Yarrow: # projects/northstar/services/ledger/replay.go\n[worker.northstarcopperbridgecoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.northstarcopperbridgecoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.northstarcopperbridgecoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.NorthstarCopperBridgeCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-54155\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/northstar/services/ledger/replay.go and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Zephyr: The behavior of NorthstarOpalRouterStore is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/northstar/infra/modules/edge/main.tf. 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- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Spring Boot operational envelope\n\nThe relevant code crosses developer tools, Java, WebGL. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"En projects/northstar/app/src/main/SyncWorker.kt, NorthstarRainfallDBService tiene un problema intermitente en el flujo de Kotlin coroutines. Separa responsabilidades y elimina duplicación, conservando API, wire values, orden y comportamiento observable.\n\nRestricciones:\n- seguir con Kotlin coroutines\n- conservar compatibilidad y cancelación\n- limitar el cambio a NorthstarRainfallDBService","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"es"} +{"prompt":"Checkout: // projects/northstar/engine/render/atlas.cpp\nfinal class NorthstarAcornWidgetFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 NorthstarAcornWidgetFlow'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":"Nobody is asking for code changes yet; we first need to understand whether the current NorthstarSableParserStore design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarSableParserStore\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.\n\nNothing is reported broken, so judge and explain current behavior without inventing a failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remove NorthstarDriftConsoleStore's stray comma","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"NorthstarMicaProfileCoordinator: ship, then assess","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Add a bounded NorthstarHarborIndexFlow export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Two engineers disagree about whether NorthstarCopperBridgeStore's cache is authoritative. Walk the reads and writes in projects/northstar/services/ledger/replay.go and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Exporter: // projects/northstar/Sources/App/SessionStore.swift\nfinal class NorthstarOspreyJobFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 NorthstarOspreyJobFlow 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":"Scheduler: Two asks around NorthstarKiteSchedulerCoordinator: (1) assess ownership and failure handling in projects/northstar/Sources/CLI/Commands/Doctor.swift; (2) capture the contract and rollback note for consumers. Make rollback possible without deleting user data, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Dashboard: # projects/northstar/cmd/exporter/main.py\n[worker.northstarmoonlitsdkflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.northstarmoonlitsdkflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.northstarmoonlitsdkflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.NorthstarMoonlitSDKFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-54117\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 NorthstarMoonlitSDKFlow'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":"Where did NorthstarCinderAuthStore's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Release engineering needs a NorthstarAsterWebhookStore 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":"diff --git a/projects/northstar/ml/pipeline/features.py b/projects/northstar/ml/pipeline/features.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/ml/pipeline/features.py\n+++ b/projects/northstar/ml/pipeline/features.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 NorthstarSlateEditorFlow'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":"NorthstarRavenSessionCoordinator: ship, then correct","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","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_54124'\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_54124'::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\nFind the source of this NorthstarBirchMigratorFlow symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"NorthstarAsterWebhookService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current GraphQL operational envelope\n\nThe relevant code crosses developer tools, Java, WebGL. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"NorthstarCoralUploadCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"NorthstarDriftConsoleCoordinator needs a paired pass: produce a consumer guide for NorthstarDriftConsoleCoordinator, plus correct the known stale timeout beside it. Use projects/northstar/infra/modules/edge/main.tf as the source of truth, preserve the Spring Boot contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"NorthstarNovaPickerCoordinator is blocking the next release because a flaky snapshot caused by locale-dependent sorting. I need two concrete outcomes from a single pass: separate NorthstarNovaPickerCoordinator's policy from transport without behavior changes, and correct the known stale timeout beside it. Use the existing GraphQL conventions in projects/northstar/config/staging.toml; make rollback possible without deleting user data. 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":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Support wants the behavior in projects/northstar/ui/settings/PrivacyPane.tsx recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Before touching projects/northstar/src/sync/reconcile.ts, 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":"Map NorthstarLumenChartService's ownership split","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"The behavior of NorthstarOspreyJobService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/northstar/Sources/App/SessionStore.swift. 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- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Kafka operational envelope\n\nThe relevant code crosses developer tools, Java, WebGL. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Em projects/northstar/web/components/FilterDrawer.vue, o NorthstarSummitProxyStore tem um problema intermitente no fluxo de Spring Boot. Leia o fluxo atual e avalie ownership, cancelamento e ordem; preciso apenas da análise.\n\nRestrições:\n- continuar com Spring Boot\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao NorthstarSummitProxyStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"pt"} +{"prompt":"Incident timeline — INC-54142\n\n08:02 deploy NorthstarCoralUploadFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current NorthstarCoralUploadFlow 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":"$ pnpm test --filter NorthstarFlintTimelineFlow\n RUN v3.2.4 /workspace/apps/console\n × NorthstarFlintTimelineFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=54120 phase=resume storedCursor=seg-0183\n session=54120 phase=fetch requestCursor=seg-0183 pageSize=200\n session=54120 phase=commit receivedCursor=seg-0184 itemCount=0\n session=54120 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nReconstruct the NorthstarFlintTimelineFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} {"prompt":"Any races in NorthstarSpruceDaemonService?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"2026-07-30T08:14:11.409Z level=info service=northstarasterwebhookcoordinator pod=northstarasterwebhookcoordinator-7cf8 request_id=54156 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=northstarasterwebhookcoordinator request_id=54156 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=northstarasterwebhookcoordinator request_id=54156 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=northstarasterwebhookcoordinator request_id=54156 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=northstarasterwebhookcoordinator request_id=54156 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=northstarasterwebhookcoordinator request_id=54156 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=northstarasterwebhookcoordinator request_id=54156 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=northstarasterwebhookcoordinator request_id=54156 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nReconstruct the NorthstarAsterWebhookCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"NorthstarBirchMigratorCoordinator needs a paired pass: finish NorthstarBirchMigratorCoordinator's responsive empty and retry states, plus correct the known stale timeout beside it. Use projects/northstar/lib/codec/frame.cc as the source of truth, preserve the Cloudflare Workers contract, and avoid unrelated cleanup.","purpose":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.64,"slice":"mixed","lang":"en"} -{"prompt":"Warum hängt NorthstarRavenSessionStore?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","lang":"de"} -{"prompt":"Incident timeline — INC-54150\n\n08:02 deploy NorthstarJuniperCLICoordinator 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 NorthstarJuniperCLICoordinator, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"pasted-context","lang":"en"} -{"prompt":"Is there a cleaner way to separate OvertureWillowCodecStore'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.55,"slice":"core","lang":"en"} +{"prompt":"2026-07-30T08:14:11.409Z level=info service=northstarasterwebhookcoordinator pod=northstarasterwebhookcoordinator-7cf8 request_id=54156 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=northstarasterwebhookcoordinator request_id=54156 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=northstarasterwebhookcoordinator request_id=54156 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=northstarasterwebhookcoordinator request_id=54156 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=northstarasterwebhookcoordinator request_id=54156 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=northstarasterwebhookcoordinator request_id=54156 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=northstarasterwebhookcoordinator request_id=54156 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=northstarasterwebhookcoordinator request_id=54156 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nReconstruct the NorthstarAsterWebhookCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"NorthstarBirchMigratorCoordinator needs a paired pass: finish NorthstarBirchMigratorCoordinator's responsive empty and retry states, plus correct the known stale timeout beside it. Use projects/northstar/lib/codec/frame.cc as the source of truth, preserve the Cloudflare Workers contract, and avoid unrelated cleanup.","purpose":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Warum hängt NorthstarRavenSessionStore?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"de"} +{"prompt":"Incident timeline — INC-54150\n\n08:02 deploy NorthstarJuniperCLICoordinator 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 NorthstarJuniperCLICoordinator, 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":"Is there a cleaner way to separate OvertureWillowCodecStore'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":"OvertureCopperBridgeCoordinator needs a paired pass: lay out a staged migration for OvertureCopperBridgeCoordinator, plus consolidate the duplicated normalization paths without changing behavior. Use projects/overture/Sources/App/SessionStore.swift as the source of truth, preserve the Room contract, and avoid unrelated cleanup.","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Bring OvertureSableParserService'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.49,"slice":"core","lang":"en"} -{"prompt":"En projects/overture/services/ledger/replay.go, OvertureIrisBatchStore tiene un problema intermitente en el flujo de OpenTelemetry. Termina el layout responsive, estados vacío y retry, foco por teclado, dark mode y reduced motion.\n\nRestricciones:\n- seguir con OpenTelemetry\n- conservar compatibilidad y cancelación\n- limitar el cambio a OvertureIrisBatchStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"es"} -{"prompt":"Worker: Incident timeline — INC-55117\n\n08:02 deploy OvertureAcornWidgetFlow 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 OvertureAcornWidgetFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.62,"slice":"pasted-context","lang":"en"} -{"prompt":"SDK consumers are ready for durable continuation tokens, so the remaining work lives in OvertureMosaicGridService's API, storage, and worker layers. Wire the schema, repository, handler, and worker so duplicate deliveries return the original result and shutdown never acknowledges uncommitted work.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside OvertureMosaicGridService\n- preserve cancellation and back-pressure semantics\n\nSeveral teams work in this IoT fleet, Ruby, SolidJS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.83,"slice":"core","lang":"en"} -{"prompt":"OvertureMoonlitSDKCoordinator: the screen feels unfinished","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"vague-eval","lang":"en"} -{"prompt":"Please resist widening this one: OvertureOrbitSyncStore works, but staging still carries a setting that production corrected last month. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside OvertureOrbitSyncStore\n- preserve cancellation and back-pressure semantics\n\nSeveral teams work in this IoT fleet, Ruby, SolidJS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"boundary","lang":"en"} -{"prompt":"OvertureAcornWidgetCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"Security flagged OvertureCoralUploadStore for a read-only pass because its gRPC 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- preserve cancellation and back-pressure semantics\n- retain the current gRPC operational envelope\n\nThis repository spans IoT fleet, Ruby, SolidJS; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.66,"slice":"boundary","lang":"en"} +{"prompt":"Bring OvertureSableParserService'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.5,"slice":"core","lang":"en"} +{"prompt":"En projects/overture/services/ledger/replay.go, OvertureIrisBatchStore tiene un problema intermitente en el flujo de OpenTelemetry. Termina el layout responsive, estados vacío y retry, foco por teclado, dark mode y reduced motion.\n\nRestricciones:\n- seguir con OpenTelemetry\n- conservar compatibilidad y cancelación\n- limitar el cambio a OvertureIrisBatchStore","purpose":"frontendImpl","secondary":"debugging","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"es"} +{"prompt":"Worker: Incident timeline — INC-55117\n\n08:02 deploy OvertureAcornWidgetFlow 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 OvertureAcornWidgetFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"SDK consumers are ready for durable continuation tokens, so the remaining work lives in OvertureMosaicGridService's API, storage, and worker layers. Wire the schema, repository, handler, and worker so duplicate deliveries return the original result and shutdown never acknowledges uncommitted work.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside OvertureMosaicGridService\n- preserve cancellation and back-pressure semantics\n\nSeveral teams work in this IoT fleet, Ruby, SolidJS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"OvertureMoonlitSDKCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Please resist widening this one: OvertureOrbitSyncStore works, but staging still carries a setting that production corrected last month. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside OvertureOrbitSyncStore\n- preserve cancellation and back-pressure semantics\n\nSeveral teams work in this IoT fleet, Ruby, SolidJS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"OvertureAcornWidgetCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Security flagged OvertureCoralUploadStore for a read-only pass because its gRPC 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- preserve cancellation and back-pressure semantics\n- retain the current gRPC operational envelope\n\nThis repository spans IoT fleet, Ruby, SolidJS; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Two asks around OvertureCloudReconcilerCoordinator: (1) assess ownership and failure handling in projects/overture/lib/codec/frame.cc; (2) capture the contract and rollback note for consumers. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} {"prompt":"This should remain a deliberately small patch: OvertureMarbleTokenService has one known configuration mistake in projects/overture/config/staging.toml, 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- preserve cancellation and back-pressure semantics\n- stay compatible with the existing Swift 6 deployment\n- keep the work scoped to OvertureMarbleTokenService and its direct tests\n\nThe relevant code crosses IoT fleet, Ruby, SolidJS. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"OvertureMicaProfileCoordinator: polish the last piece","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"vague-eval","lang":"en"} -{"prompt":"The data is already available in projects/overture/engine/render/atlas.cpp; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"boundary","lang":"en"} -{"prompt":"Before we approve OvertureDeltaCanvasStore, assess whether a misleading timeout name used in five packages is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Our support and SDK teams keep answering the same questions about OvertureBeaconStoreStore, but the current prose in projects/overture/src/sync/reconcile.ts 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- preserve cancellation and back-pressure semantics\n- stay compatible with the existing FastAPI deployment\n- keep the work scoped to OvertureBeaconStoreStore and its direct tests\n\nThe relevant code crosses IoT fleet, Ruby, SolidJS. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"We expect OvertureMapleQueueService to outgrow its current FastAPI 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- preserve cancellation and back-pressure semantics\n- stay compatible with the existing FastAPI deployment\n- keep the work scoped to OvertureMapleQueueService and its direct tests\n\nThe relevant code crosses IoT fleet, Ruby, SolidJS. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"core","lang":"en"} -{"prompt":"Simulator: The OvertureEmberRelayFlow 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.09,"slice":"boundary","lang":"en"} -{"prompt":"OvertureNimbusFormCoordinator: untangle the messy bit","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"vague-eval","lang":"en"} -{"prompt":"Ticket OPS-55152: retire the legacy replay path for OvertureEchoRegistryCoordinator\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 OvertureEchoRegistryCoordinator 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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"projects/overture/ui/settings/PrivacyPane.tsx 里的 OvertureOspreyJobService 最近在 gRPC 流程中出现间歇性问题。 原因已经明确：只把 staging timeout 从 15 秒改成 30 秒，并调整对应 assertion。\n\n约束：\n- 继续使用 gRPC\n- 保持兼容性和取消语义\n- 改动只限于 OvertureOspreyJobService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"core","lang":"zh"} -{"prompt":"For OvertureRainfallDBCoordinator, change OvertureRainfallDBCoordinator's known staging timeout from 15 to 30 seconds; once that is complete, give the existing implementation a read-only safety pass. Work from projects/overture/internal/auth/refresh.go, stay with OpenTelemetry, and preserve cancellation and back-pressure semantics. Keep the two outcomes separately reviewable.","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.22,"slice":"mixed","lang":"en"} -{"prompt":"Runbook: Two asks around OverturePineMetricsCoordinator: (1) lay out a staged migration for OverturePineMetricsCoordinator; (2) then implement the bounded durable-cursor handler. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.82,"slice":"mixed","lang":"en"} -{"prompt":"// projects/overture/app/src/main/SyncWorker.kt\nfinal class OvertureBasilRunnerFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 OvertureBasilRunnerFlow'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.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Ticket OPS-55132: retire the legacy replay path for OvertureTideWorkerFlow\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 OvertureTideWorkerFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"Could the reasoning behind OvertureLumenChartService's OpenTelemetry choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"OvertureQuartzPlayerCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Split OvertureCedarPolicyStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"Two asks around OvertureHarborIndexCoordinator: (1) separate OvertureHarborIndexCoordinator's policy from transport without behavior changes; (2) capture the contract and rollback note for consumers. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Cadre la migration de OvertureHarborIndexStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"fr"} -{"prompt":"Could OvertureVelaDrawerFlow show the active OpenTelemetry sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"boundary","lang":"en"} -{"prompt":"Center the OvertureTideWorkerStore modal","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"boundary","lang":"en"} -{"prompt":"Read projects/overture/engine/render/atlas.cpp and tell me whether OvertureEmberRelayStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Architect a gradual ownership transfer for OvertureCinderAuthStore across two teams, including module seams, temporary interfaces, observability, handoff criteria, and rollback responsibility. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"Investigate the OvertureCedarPolicyService hang","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Trace: Incident timeline — INC-55135\n\n08:02 deploy OvertureOspreyJobFlow 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 OvertureOspreyJobFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"pasted-context","lang":"en"} -{"prompt":"What does OvertureFernSnapshotService own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"We need to move OvertureSpruceDaemonStore from the legacy store to Room. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Diff: The OvertureBasilRunnerStore surface in projects/overture/apps/console/routes/usage.svelte 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.43,"slice":"boundary","lang":"en"} -{"prompt":"Bump OvertureRainfallDBService's timeout to 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"core","lang":"en"} -{"prompt":"Fresh release brief for OvertureAmberFilterCoordinator:\n- primary outcome: separate OvertureAmberFilterCoordinator's policy from transport without behavior changes\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/overture/crates/index/src/segment.rs\n- platform constraint: Swift 6\n- known complication: an accessibility label that reads the internal enum\n\nBoth results are required, but they should remain independently reviewable. Preserve cancellation and back-pressure semantics; 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":"refactor","secondary":"writing","mixed":true,"difficulty":0.84,"slice":"mixed","lang":"en"} -{"prompt":"Check OvertureQuartzPlayerStore's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"One contained cleanup in projects/overture/packages/api/openapi.yaml: remove the obsolete OvertureMarbleTokenStore import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"core","lang":"en"} -{"prompt":"Profiler: Two asks around OvertureOpalRouterCoordinator: (1) assess ownership and failure handling in projects/overture/cmd/exporter/main.py; (2) capture the contract and rollback note for consumers. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"OvertureAtlasSearchCoordinator is blocking the next release because lost focus when the drawer animation finishes. I need two concrete outcomes from a single pass: lay out a staged migration for OvertureAtlasSearchCoordinator, and consolidate the duplicated normalization paths without changing behavior. Use the existing gRPC conventions in projects/overture/lib/codec/frame.cc; preserve cancellation and back-pressure semantics. 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.88,"slice":"mixed","lang":"en"} -{"prompt":"En projects/overture/cmd/exporter/main.py, OvertureDriftConsoleService tiene un problema intermitente en el flujo de Room. Añade el endpoint idempotente con cursor durable, autorización tenant, spans y tests de retry.\n\nRestricciones:\n- seguir con Room\n- conservar compatibilidad y cancelación\n- limitar el cambio a OvertureDriftConsoleService Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con Room alrededor de OvertureDriftConsoleService.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.81,"slice":"core","lang":"es"} -{"prompt":"In projects/overture/web/components/FilterDrawer.vue hat OvertureIrisBatchService ein sporadisches Problem im OpenTelemetry-Ablauf. Trenne Verantwortlichkeiten und entferne Duplikate, ohne API, Wire-Werte, Reihenfolge oder sichtbares Verhalten zu ändern.\n\nRandbedingungen:\n- OpenTelemetry weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf OvertureIrisBatchService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um OvertureIrisBatchService mit OpenTelemetry kompatibel.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"de"} -{"prompt":"Test Suite 'OvertureLedgerGateFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[OvertureLedgerGateFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/overture/crates/index/src/segment.rs:144: error: -[OvertureLedgerGateFlowTests 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 '-[OvertureLedgerGateFlowTests 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\nReconstruct the OvertureLedgerGateFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.92,"slice":"pasted-context","lang":"en"} -{"prompt":"Test Suite 'OvertureVelaDrawerCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[OvertureVelaDrawerCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/overture/internal/auth/refresh.go:144: error: -[OvertureVelaDrawerCoordinatorTests 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 '-[OvertureVelaDrawerCoordinatorTests 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 OvertureVelaDrawerCoordinator'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.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Incident timeline — INC-55113\n\n08:02 deploy OvertureOrbitSyncFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. From this evidence, draft consumer-facing migration guidance for OvertureOrbitSyncFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.65,"slice":"pasted-context","lang":"es"} -{"prompt":"Any races in OvertureLedgerGateStore?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"thread 'tokio-runtime-worker' panicked at projects/overture/Sources/CLI/Commands/Doctor.swift:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: overturecopperbridgeflow::scheduler::LeaseTask::flush\n at ./projects/overture/Sources/CLI/Commands/Doctor.swift:217:18\n 4: overturecopperbridgeflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nReconstruct the OvertureCopperBridgeFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.95,"slice":"pasted-context","lang":"en"} -{"prompt":"The minimum supported OpenTelemetry version in projects/overture/internal/auth/refresh.go is one patch behind the lockfile. Align that single value and regenerate only the affected metadata.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"core","lang":"en"} -{"prompt":"OvertureJuniperCLICoordinator: sequence, then polish","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"On compact widths, OvertureVelaDrawerStore'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.46,"slice":"core","lang":"en"} -{"prompt":"How does OvertureSableParserStore propagate cancellation through the Swift 6 boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"For OvertureTideWorkerCoordinator, find the unknown cause of two validators with subtly different error strings; once that is complete, give the existing implementation a read-only safety pass. Work from projects/overture/crates/index/src/segment.rs, stay with Swift 6, and preserve cancellation and back-pressure semantics. Keep the two outcomes separately reviewable.","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.78,"slice":"mixed","lang":"en"} -{"prompt":"Milestones for replacing OvertureTideWorkerService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"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_55158'\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_55158'::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\nReconstruct the OvertureSummitProxyCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.95,"slice":"pasted-context","lang":"en"} -{"prompt":"OvertureOspreyJobCoordinator: clean up that old path","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"diff --git a/projects/overture/src/sync/reconcile.ts b/projects/overture/src/sync/reconcile.ts\nindex 62d71aa..90f3c1e 100644\n--- a/projects/overture/src/sync/reconcile.ts\n+++ b/projects/overture/src/sync/reconcile.ts\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure OverturePineMetricsFlow 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.87,"slice":"pasted-context","lang":"en"} -{"prompt":"2026-07-30T08:14:11.409Z level=info service=overtureslateeditorflow pod=overtureslateeditorflow-7cf8 request_id=55120 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=overtureslateeditorflow request_id=55120 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=overtureslateeditorflow request_id=55120 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=overtureslateeditorflow request_id=55120 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=overtureslateeditorflow request_id=55120 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=overtureslateeditorflow request_id=55120 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=overtureslateeditorflow request_id=55120 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=overtureslateeditorflow request_id=55120 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nFind the source of this OvertureSlateEditorFlow 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.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Our support and SDK teams keep answering the same questions about OvertureAtlasSearchService, but the current prose in projects/overture/engine/render/atlas.cpp 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- preserve cancellation and back-pressure semantics\n- stay compatible with the existing gRPC deployment\n- keep the work scoped to OvertureAtlasSearchService and its direct tests\n\nThe relevant code crosses IoT fleet, Ruby, SolidJS. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.49,"slice":"core","lang":"en"} -{"prompt":"OvertureMicaProfileService needs an idempotent replay endpoint backed by FastAPI; accept a cursor, cap each page at 500 items, and return a stable continuation token.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Console: Could the reasoning behind OvertureEchoRegistryStore's Swift 6 choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"Unify the OvertureQuartzPlayerService validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Assess the OvertureFernSnapshotStore diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"Workspace: Ticket OPS-55131: retire the legacy replay path for OvertureCraneWorkspaceFlow\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 OvertureCraneWorkspaceFlow 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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Three teams extended OvertureMosaicGridStore independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current FastAPI operational envelope\n\nThis repository spans IoT fleet, Ruby, SolidJS; use its existing conventions rather than importing a new abstraction.\n\nThe target structure is settled; carry out the behavior-preserving edits rather than writing another strategy.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.79,"slice":"boundary","lang":"en"} -{"prompt":"Em projects/overture/workers/thumbnail/consumer.ex, o OvertureOspreyJobStore tem um problema intermitente no fluxo de gRPC. Separe responsabilidades e remova duplicação sem mudar API, wire values, ordem ou comportamento observável.\n\nRestrições:\n- continuar com gRPC\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao OvertureOspreyJobStore","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"pt"} -{"prompt":"Cadre la migration de OvertureFrostPanelService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"fr"} -{"prompt":"Production says OvertureKiteSchedulerService is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current gRPC operational envelope\n\nThis repository spans IoT fleet, Ruby, SolidJS; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current OvertureEmberRelayService 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 OvertureEmberRelayService\n- preserve cancellation and back-pressure semantics\n\nSeveral teams work in this IoT fleet, Ruby, SolidJS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"OvertureSlateEditorCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"Draft OvertureBeaconStoreService's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"UI ticket DES-55145: finish the compact OvertureCinderAuthFlow filter experience\n\nRoute: /catalog/search\nSource: projects/overture/workers/thumbnail/consumer.ex\nFramework: gRPC\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\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Finish the visible OvertureCinderAuthFlow 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.68,"slice":"pasted-context","lang":"zh"} -{"prompt":"Repository: diff --git a/projects/overture/pkg/cache/lease.rs b/projects/overture/pkg/cache/lease.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/overture/pkg/cache/lease.rs\n+++ b/projects/overture/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\nRead the artifact above as a skeptical reviewer. Is OvertureAmberFilterFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"OvertureWrenExportCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.45,"slice":"mixed","lang":"en"} -{"prompt":"UI ticket DES-55151: finish the compact OvertureWillowCodecCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/overture/web/components/FilterDrawer.vue\nFramework: OpenTelemetry\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 OvertureWillowCodecCoordinator 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.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Could the reasoning behind OvertureMoonlitSDKService's gRPC choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"The behavior of OvertureSummitProxyService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/overture/Sources/CLI/Commands/Doctor.swift. 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- preserve cancellation and back-pressure semantics\n- retain the current Room operational envelope\n\nThis repository spans IoT fleet, Ruby, SolidJS; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Incident timeline — INC-55146\n\n08:02 deploy OvertureLumenChartFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nReconstruct the OvertureLumenChartFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Two engineers disagree about whether OvertureBirchMigratorService's cache is authoritative. Walk the reads and writes in projects/overture/config/staging.toml and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Pipeline: Incident timeline — INC-55111\n\n08:02 deploy OvertureIrisBatchFlow 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\nFind the source of this OvertureIrisBatchFlow 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.9,"slice":"pasted-context","lang":"en"} -{"prompt":"projects/overture/Sources/App/SessionStore.swift has grown through several launches, and OvertureSummitProxyStore now mixes policy, transport, persistence, and metrics in one place. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- preserve cancellation and back-pressure semantics\n- stay compatible with the existing Room deployment\n- keep the work scoped to OvertureSummitProxyStore and its direct tests\n\nThe relevant code crosses IoT fleet, Ruby, SolidJS. Prefer evidence from the repository and make any assumption explicit.\n\nThe target structure is settled; carry out the behavior-preserving edits rather than writing another strategy.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.77,"slice":"boundary","lang":"en"} -{"prompt":"Gateway: Incident timeline — INC-55115\n\n08:02 deploy OvertureCoralUploadFlow 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 OvertureCoralUploadFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"// projects/overture/engine/render/atlas.cpp\nfinal class OvertureAtlasSearchFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nWire OvertureAtlasSearchFlow'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.81,"slice":"pasted-context","lang":"en"} -{"prompt":"Ticket OPS-55116: retire the legacy replay path for OvertureWrenExportFlow\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 OvertureWrenExportFlow 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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Release engineering needs a OvertureSpruceDaemonService changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"OvertureFlintTimelineCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"vague-eval","lang":"en"} -{"prompt":"Responsive layout for OvertureAcornWidgetService","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"core","lang":"en"} -{"prompt":"Renderer: projects/overture/Sources/App/SessionStore.swift now contains OvertureDeltaCanvasService'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.6,"slice":"core","lang":"en"} -{"prompt":"OvertureDriftConsoleStore'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.17,"slice":"core","lang":"en"} -{"prompt":"OvertureRavenSessionService 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.58,"slice":"core","lang":"en"} -{"prompt":"OvertureBasilRunnerCoordinator: check the suspicious part","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"vague-eval","lang":"en"} -{"prompt":"Indexer: The OvertureMicaProfileStore 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.19,"slice":"boundary","lang":"en"} -{"prompt":"Please resist widening this one: OvertureVelaDrawerService works, but staging still carries a setting that production corrected last month. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside OvertureVelaDrawerService\n- preserve cancellation and back-pressure semantics\n\nSeveral teams work in this IoT fleet, Ruby, SolidJS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.28,"slice":"core","lang":"en"} -{"prompt":"OvertureGarnetModalCoordinator: take care of the warning","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"vague-eval","lang":"en"} -{"prompt":"Rename OvertureSlateEditorService's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"OvertureBirchMigratorCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"vague-eval","lang":"en"} -{"prompt":"Apparently: // projects/overture/apps/console/routes/usage.svelte\nfinal class OvertureGarnetModalFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 OvertureGarnetModalFlow 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.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Please turn OvertureKiteSchedulerStore'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.33,"slice":"core","lang":"en"} -{"prompt":"OvertureNimbusFormService'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.12,"slice":"core","lang":"en"} -{"prompt":"SDK consumers are ready for durable continuation tokens, so the remaining work lives in OvertureAmberFilterService's API, storage, and worker layers. Wire the schema, repository, handler, and worker so duplicate deliveries return the original result and shutdown never acknowledges uncommitted work.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside OvertureAmberFilterService\n- preserve cancellation and back-pressure semantics\n\nSeveral teams work in this IoT fleet, Ruby, SolidJS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Teach OvertureMarbleTokenFlow to verify signed continuation tokens, reject cross-tenant cursors, and rotate keys without invalidating tokens issued during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"The data is already available in projects/overture/src/sync/reconcile.ts; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"boundary","lang":"en"} -{"prompt":"Lately: // projects/overture/cmd/exporter/main.py\nfinal class OvertureJuniperCLIFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 OvertureJuniperCLIFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Spell OvertureOpalRouterService's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.17,"slice":"core","lang":"en"} -{"prompt":"OvertureAmberFilterStore is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current Swift 6 operational envelope\n\nThis repository spans IoT fleet, Ruby, SolidJS; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"OvertureCinderAuthCoordinator: deal with the small issue","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"vague-eval","lang":"en"} -{"prompt":"Incident timeline — INC-55153\n\n08:02 deploy OvertureDriftConsoleCoordinator 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Capture the OvertureDriftConsoleCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.65,"slice":"pasted-context","lang":"ja"} -{"prompt":"Oddly: # projects/overture/apps/console/routes/usage.svelte\n[worker.overturemosaicgridcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.overturemosaicgridcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.overturemosaicgridcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.OvertureMosaicGridCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-55159\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/overture/apps/console/routes/usage.svelte. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.43,"slice":"pasted-context","lang":"en"} -{"prompt":"OvertureCraneWorkspaceCoordinator needs a paired pass: finish OvertureCraneWorkspaceCoordinator's responsive empty and retry states, plus capture the contract and rollback note for consumers. Use projects/overture/services/ledger/replay.go as the source of truth, preserve the OpenTelemetry contract, and avoid unrelated cleanup.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.56,"slice":"mixed","lang":"en"} -{"prompt":"OvertureNovaPickerCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"vague-eval","lang":"en"} -{"prompt":"Add a bounded OvertureMapleQueueStore export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Ticket OPS-55140: retire the legacy replay path for OvertureMoonlitSDKFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for OvertureMoonlitSDKFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.57,"slice":"pasted-context","lang":"en"} -{"prompt":"Currently: Please turn OvertureMosaicGridFlow'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.43,"slice":"boundary","lang":"en"} -{"prompt":"Today: projects/overture/ml/pipeline/features.py 里的 OvertureFlintTimelineStore 最近在 Room 流程中出现间歇性问题。 请给出阶段、兼容层、指标、rollback 和 ownership，先不要修改代码。\n\n约束：\n- 继续使用 Room\n- 保持兼容性和取消语义\n- 改动只限于 OvertureFlintTimelineStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"zh"} -{"prompt":"Collapse the OvertureCraneWorkspaceService wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Design the OvertureJuniperCLIService rollback","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Polish the OverturePineMetricsService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"OvertureSableParserCoordinator: handle the lingering thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"vague-eval","lang":"en"} -{"prompt":"Before touching projects/overture/Sources/CLI/Commands/Doctor.swift, propose how to retire its legacy format while old clients remain active for ninety days and operators retain a reversible escape hatch. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"This should remain a deliberately small patch: OvertureAcornWidgetStore has one known configuration mistake in projects/overture/config/staging.toml, 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- preserve cancellation and back-pressure semantics\n- stay compatible with the existing Swift 6 deployment\n- keep the work scoped to OvertureAcornWidgetStore and its direct tests\n\nThe relevant code crosses IoT fleet, Ruby, SolidJS. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"Trace OvertureOpalRouterStore's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"Context: Incident timeline — INC-55143\n\n08:02 deploy OvertureFlintTimelineFlow 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 OvertureFlintTimelineFlow rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"pasted-context","lang":"en"} -{"prompt":"Background: Incident timeline — INC-55121\n\n08:02 deploy OvertureFernSnapshotFlow 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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Turn the material above into a concise OvertureFernSnapshotFlow 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.59,"slice":"pasted-context","lang":"de"} -{"prompt":"Question: Incident timeline — INC-55157\n\n08:02 deploy OvertureMarbleTokenCoordinator 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 OvertureMarbleTokenCoordinator 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.62,"slice":"pasted-context","lang":"en"} -{"prompt":"Assess the OvertureCoralUploadService diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Test Suite 'OvertureNovaPickerFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[OvertureNovaPickerFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/overture/db/migrations/20260730_events.sql:144: error: -[OvertureNovaPickerFlowTests 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 '-[OvertureNovaPickerFlowTests 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 OvertureNovaPickerFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Does OvertureLumenChartStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"Summarize the OvertureCopperBridgeService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"Does OvertureCopperBridgeStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Any races in OvertureCloudReconcilerStore?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Test Suite 'OvertureEmberRelayCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[OvertureEmberRelayCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/overture/engine/render/atlas.cpp:144: error: -[OvertureEmberRelayCoordinatorTests 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 '-[OvertureEmberRelayCoordinatorTests 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 OvertureEmberRelayCoordinator'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.68,"slice":"pasted-context","lang":"en"} -{"prompt":"Draft OvertureCloudReconcilerService's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"What sequence would let OvertureBirchMigratorStore adopt Swift 6 with dual reads but no dual writes? Include data validation, canary scope, and the decision that ends compatibility mode. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"OvertureFrostPanelCoordinator: diagnose, then document","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.83,"slice":"mixed","lang":"en"} -{"prompt":"Clarify OverturePineMetricsStore's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"boundary","lang":"en"} -{"prompt":"OvertureFernSnapshotCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.45,"slice":"mixed","lang":"en"} -{"prompt":"Before touching projects/overture/crates/index/src/segment.rs, propose how to retire its legacy format while old clients remain active for ninety days and operators retain a reversible escape hatch. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Compare OvertureCraneWorkspaceStore's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"Polish the OvertureWrenExportService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"projects/overture/infra/modules/edge/main.tf now contains OverturePrismCacheStore'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.55,"slice":"boundary","lang":"en"} -{"prompt":"# projects/overture/ml/pipeline/features.py\n[worker.overtureopalrouterflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.overtureopalrouterflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.overtureopalrouterflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.OvertureOpalRouterFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-55133\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/overture/ml/pipeline/features.py and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.41,"slice":"pasted-context","lang":"en"} -{"prompt":"Observation: # projects/overture/packages/api/openapi.yaml\n[worker.overturesableparserflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.overturesableparserflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.overturesableparserflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.OvertureSableParserFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-55137\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Align OvertureSableParserFlow'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.38,"slice":"pasted-context","lang":"pt"} -{"prompt":"Constraint: // projects/overture/config/staging.toml\nfinal class OvertureBirchMigratorFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 OvertureBirchMigratorFlow 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.82,"slice":"pasted-context","lang":"en"} -{"prompt":"# CI job 55114: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: FastAPI\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] OvertureBeaconStoreFlowIntegration.replays_after_timeout ... ok\n[test] OvertureBeaconStoreFlowIntegration.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 \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\nAdd the bounded OvertureBeaconStoreFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"One contained cleanup in projects/overture/workers/thumbnail/consumer.ex: remove the obsolete OvertureKiteSchedulerFlow import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"boundary","lang":"en"} -{"prompt":"Bring OvertureNimbusFormStore'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.46,"slice":"boundary","lang":"en"} -{"prompt":"Request: projects/overture/src/sync/reconcile.ts now contains OvertureMapleQueueFlow'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.63,"slice":"boundary","lang":"en"} -{"prompt":"OvertureOrbitSyncCoordinator is blocking the next release because lease renewal code copied across three workers. I need two concrete outcomes from a single pass: produce a consumer guide for OvertureOrbitSyncCoordinator, and give the existing implementation a read-only safety pass. Use the existing Room conventions in projects/overture/cmd/exporter/main.py; preserve cancellation and back-pressure semantics. Keep the outcomes distinct so reviewers can see which evidence supports the assessment and which files or prose satisfy the requested change.\n\nConstraints:\n- preserve public wire values and tenant boundaries\n- cover cancellation and retry behavior\n- avoid generated code and unrelated cleanup\n- include a rollback trigger that an on-call engineer can measure\n\nThis is a fresh workstream for the release, so derive everything from the repository and the context here.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.67,"slice":"mixed","lang":"en"} -{"prompt":"Goal: // projects/overture/workers/thumbnail/consumer.ex\nfinal class OvertureCedarPolicyFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 OvertureCedarPolicyFlow'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.77,"slice":"pasted-context","lang":"en"} -{"prompt":"OverturePrismCacheCoordinator: give it a nicer flow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"vague-eval","lang":"en"} -{"prompt":"OvertureRavenSessionCoordinator: maybe tighten this up","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"vague-eval","lang":"en"} -{"prompt":"Incident timeline — INC-55119\n\n08:02 deploy OvertureFrostPanelFlow 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 OvertureFrostPanelFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.67,"slice":"pasted-context","lang":"en"} -{"prompt":"Bring OvertureBasilRunnerService'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.54,"slice":"core","lang":"en"} -{"prompt":"Two deliverables are holding up OvertureIrisBatchCoordinator. First, find the unknown cause of timestamps rendered one day ahead near UTC midnight. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/overture/services/ledger/replay.go, which follows OpenTelemetry conventions and currently suffers from timestamps rendered one day ahead near UTC midnight. Preserve cancellation and back-pressure semantics.\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.92,"slice":"mixed","lang":"en"} -{"prompt":"Symptom: # projects/overture/Sources/App/SessionStore.swift\n[worker.overturequartzplayerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.overturequartzplayerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.overturequartzplayerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.OvertureQuartzPlayerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-55118\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/overture/Sources/App/SessionStore.swift and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.41,"slice":"pasted-context","lang":"en"} -{"prompt":"Please resist widening this one: OvertureWrenExportStore works, but staging still carries a setting that production corrected last month. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside OvertureWrenExportStore\n- preserve cancellation and back-pressure semantics\n\nSeveral teams work in this IoT fleet, Ruby, SolidJS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.28,"slice":"boundary","lang":"en"} -{"prompt":"# CI job 55154: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: FastAPI\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] OvertureMapleQueueCoordinatorIntegration.replays_after_timeout ... ok\n[test] OvertureMapleQueueCoordinatorIntegration.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 \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 OvertureMapleQueueCoordinator 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.91,"slice":"pasted-context","lang":"en"} -{"prompt":"OvertureLedgerGateCoordinator: diagnose, then document","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.78,"slice":"mixed","lang":"en"} -{"prompt":"This should remain a deliberately small patch: OvertureOrbitSyncService has one known configuration mistake in projects/overture/ml/pipeline/features.py, not an open-ended failure investigation. Correct the known literal and the test that intentionally mirrors it; the final diff should stay local enough for an on-call engineer to verify at a glance.\n\nConstraints:\n- preserve cancellation and back-pressure semantics\n- stay compatible with the existing Room deployment\n- keep the work scoped to OvertureOrbitSyncService and its direct tests\n\nThe relevant code crosses IoT fleet, Ruby, SolidJS. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"PM is preparing the OvertureAtlasSearchStore 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 OvertureAtlasSearchStore\n- preserve cancellation and back-pressure semantics\n\nSeveral teams work in this IoT fleet, Ruby, SolidJS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.49,"slice":"boundary","lang":"en"} -{"prompt":"diff --git a/projects/overture/infra/modules/edge/main.tf b/projects/overture/infra/modules/edge/main.tf\nindex 62d71aa..90f3c1e 100644\n--- a/projects/overture/infra/modules/edge/main.tf\n+++ b/projects/overture/infra/modules/edge/main.tf\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit OvertureRainfallDBFlow 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.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Headsup: projects/overture/cmd/exporter/main.py の OvertureFlintTimelineService で、Room の flow に断続的な問題が起きています。 現在の flow を読み、ownership、cancel、順序が安全か評価してください。分析だけで十分です。\n\n制約:\n- Room を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は OvertureFlintTimelineService のみ","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"ja"} -{"prompt":"Production says OvertureEchoRegistryService is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current Swift 6 operational envelope\n\nThis repository spans IoT fleet, Ruby, SolidJS; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.84,"slice":"core","lang":"en"} -{"prompt":"Why does OvertureGarnetModalService's FastAPI worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"UI ticket DES-55127: finish the compact OvertureHarborIndexFlow filter experience\n\nRoute: /catalog/search\nSource: projects/overture/config/staging.toml\nFramework: Swift 6\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 OvertureHarborIndexFlow 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.73,"slice":"pasted-context","lang":"en"} -{"prompt":"Ticket OPS-55136: retire the legacy replay path for OverturePrismCacheFlow\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 OverturePrismCacheFlow 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.59,"slice":"pasted-context","lang":"en"} -{"prompt":"OvertureCedarPolicyCoordinator needs a paired pass: change OvertureCedarPolicyCoordinator's known staging timeout from 15 to 30 seconds, plus capture the contract and rollback note for consumers. Use projects/overture/ui/settings/PrivacyPane.tsx as the source of truth, preserve the gRPC contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.19,"slice":"mixed","lang":"en"} -{"prompt":"FYI: Does OvertureLedgerGateService preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Responsive layout for OvertureJuniperCLIStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} -{"prompt":"OvertureSpruceDaemonCoordinator: ship a sensible version","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"vague-eval","lang":"en"} -{"prompt":"Meanwhile: # projects/overture/engine/render/atlas.cpp\n[worker.overturecloudreconcilerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.overturecloudreconcilerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.overturecloudreconcilerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.OvertureCloudReconcilerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-55130\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/overture/engine/render/atlas.cpp and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.33,"slice":"pasted-context","lang":"en"} -{"prompt":"2026-07-30T08:14:11.409Z level=info service=overturekiteschedulercoordinator pod=overturekiteschedulercoordinator-7cf8 request_id=55155 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=overturekiteschedulercoordinator request_id=55155 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=overturekiteschedulercoordinator request_id=55155 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=overturekiteschedulercoordinator request_id=55155 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=overturekiteschedulercoordinator request_id=55155 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=overturekiteschedulercoordinator request_id=55155 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=overturekiteschedulercoordinator request_id=55155 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=overturekiteschedulercoordinator request_id=55155 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nReconstruct the OvertureKiteSchedulerCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Locally: Test Suite 'OvertureAsterWebhookFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[OvertureAsterWebhookFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/overture/app/src/main/SyncWorker.kt:144: error: -[OvertureAsterWebhookFlowTests 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 '-[OvertureAsterWebhookFlowTests 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. Find the source of this OvertureAsterWebhookFlow 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.96,"slice":"pasted-context","lang":"fr"} -{"prompt":"A previously stable test around OvertureNovaPickerService now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"diff --git a/projects/overture/Sources/CLI/Commands/Doctor.swift b/projects/overture/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/overture/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/overture/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure OvertureSpruceDaemonFlow 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.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Two engineers disagree about whether OvertureGarnetModalStore's cache is authoritative. Walk the reads and writes in projects/overture/app/src/main/SyncWorker.kt and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Split projects/overture/cmd/exporter/main.py by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Extract OvertureAsterWebhookService's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Rename OvertureRainfallDBStore's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"I inherited OvertureWillowCodecService and need a careful read of projects/overture/services/ledger/replay.go 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- preserve cancellation and back-pressure semantics\n- stay compatible with the existing OpenTelemetry deployment\n- keep the work scoped to OvertureWillowCodecService and its direct tests\n\nThe relevant code crosses IoT fleet, Ruby, SolidJS. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Ticket OPS-55138: retire the legacy replay path for OvertureDeltaCanvasFlow\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 OvertureDeltaCanvasFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"pasted-context","lang":"en"} -{"prompt":"Production: Ticket OPS-55142: retire the legacy replay path for OvertureRavenSessionFlow\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 OvertureRavenSessionFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"Staging: Two deliverables are holding up OvertureBeaconStoreCoordinator. First, separate OvertureBeaconStoreCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/overture/src/sync/reconcile.ts, which follows FastAPI conventions and currently suffers from duplicate retries after a network handoff. Preserve cancellation and back-pressure semantics.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.89,"slice":"mixed","lang":"en"} -{"prompt":"OvertureLumenChartCoordinator: the docs need something","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"Remove OvertureAsterWebhookStore's stray comma","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.19,"slice":"boundary","lang":"en"} -{"prompt":"For OvertureAsterWebhookCoordinator, separate OvertureAsterWebhookCoordinator's policy from transport without behavior changes; once that is complete, give the existing implementation a read-only safety pass. Work from projects/overture/apps/console/routes/usage.svelte, stay with FastAPI, and preserve cancellation and back-pressure semantics. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.73,"slice":"mixed","lang":"en"} -{"prompt":"Is there a cleaner way to separate OvertureCinderAuthService'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.53,"slice":"core","lang":"en"} -{"prompt":"OvertureDeltaCanvasCoordinator: could this be clearer","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"Atlas: projects/overture/services/ledger/replay.go の OvertureWillowCodecFlow で、OpenTelemetry の flow に断続的な問題が起きています。 責務を分離して重複をなくし、API、wire value、順序、観測可能な動作は変えないでください。\n\n制約:\n- OpenTelemetry を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は OvertureWillowCodecFlow のみ","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"ja"} -{"prompt":"PM needs a concise migration note for OvertureRavenSessionStore, including the user impact, rollback trigger, and the one configuration key operators must change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"en"} -{"prompt":"Beacon: Ticket OPS-55144: retire the legacy replay path for OvertureMicaProfileFlow\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 OvertureMicaProfileFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"Incident timeline — INC-55141\n\n08:02 deploy OvertureNimbusFormFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current OvertureNimbusFormFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"Documente o contrato de OvertureHarborIndexService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"pt"} -{"prompt":"Fresh release brief for OvertureCoralUploadCoordinator:\n- primary outcome: change OvertureCoralUploadCoordinator'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/overture/workers/thumbnail/consumer.ex\n- platform constraint: gRPC\n- known complication: a query plan that changes after statistics refresh\n\nBoth results are required, but they should remain independently reviewable. Preserve cancellation and back-pressure semantics; 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.35,"slice":"mixed","lang":"en"} -{"prompt":"Draft OvertureSlateEditorStore's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"boundary","lang":"en"} -{"prompt":"Zentriere das OvertureFrostPanelStore-Modal","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"boundary","lang":"de"} +{"prompt":"OvertureMicaProfileCoordinator: polish the last piece","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"The data is already available in projects/overture/engine/render/atlas.cpp; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Before we approve OvertureDeltaCanvasStore, assess whether a misleading timeout name used in five packages is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Our support and SDK teams keep answering the same questions about OvertureBeaconStoreStore, but the current prose in projects/overture/src/sync/reconcile.ts 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- preserve cancellation and back-pressure semantics\n- stay compatible with the existing FastAPI deployment\n- keep the work scoped to OvertureBeaconStoreStore and its direct tests\n\nThe relevant code crosses IoT fleet, Ruby, SolidJS. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"We expect OvertureMapleQueueService to outgrow its current FastAPI 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- preserve cancellation and back-pressure semantics\n- stay compatible with the existing FastAPI deployment\n- keep the work scoped to OvertureMapleQueueService and its direct tests\n\nThe relevant code crosses IoT fleet, Ruby, SolidJS. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Simulator: The OvertureEmberRelayFlow 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":"OvertureNimbusFormCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Ticket OPS-55152: retire the legacy replay path for OvertureEchoRegistryCoordinator\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 OvertureEchoRegistryCoordinator 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/overture/ui/settings/PrivacyPane.tsx 里的 OvertureOspreyJobService 最近在 gRPC 流程中出现间歇性问题。 原因已经明确：只把 staging timeout 从 15 秒改成 30 秒，并调整对应 assertion。\n\n约束：\n- 继续使用 gRPC\n- 保持兼容性和取消语义\n- 改动只限于 OvertureOspreyJobService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"zh"} +{"prompt":"For OvertureRainfallDBCoordinator, change OvertureRainfallDBCoordinator's known staging timeout from 15 to 30 seconds; once that is complete, give the existing implementation a read-only safety pass. Work from projects/overture/internal/auth/refresh.go, stay with OpenTelemetry, and preserve cancellation and back-pressure semantics. Keep the two outcomes separately reviewable.","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Runbook: Two asks around OverturePineMetricsCoordinator: (1) lay out a staged migration for OverturePineMetricsCoordinator; (2) then implement the bounded durable-cursor handler. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"// projects/overture/app/src/main/SyncWorker.kt\nfinal class OvertureBasilRunnerFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 OvertureBasilRunnerFlow'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":"Ticket OPS-55132: retire the legacy replay path for OvertureTideWorkerFlow\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 OvertureTideWorkerFlow 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":"Could the reasoning behind OvertureLumenChartService's OpenTelemetry choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"OvertureQuartzPlayerCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Split OvertureCedarPolicyStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Two asks around OvertureHarborIndexCoordinator: (1) separate OvertureHarborIndexCoordinator's policy from transport without behavior changes; (2) capture the contract and rollback note for consumers. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Cadre la migration de OvertureHarborIndexStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"fr"} +{"prompt":"Could OvertureVelaDrawerFlow show the active OpenTelemetry sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Center the OvertureTideWorkerStore modal","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Read projects/overture/engine/render/atlas.cpp and tell me whether OvertureEmberRelayStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Architect a gradual ownership transfer for OvertureCinderAuthStore across two teams, including module seams, temporary interfaces, observability, handoff criteria, and rollback responsibility. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Investigate the OvertureCedarPolicyService hang","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Trace: Incident timeline — INC-55135\n\n08:02 deploy OvertureOspreyJobFlow 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 OvertureOspreyJobFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"What does OvertureFernSnapshotService own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"We need to move OvertureSpruceDaemonStore from the legacy store to Room. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Diff: The OvertureBasilRunnerStore surface in projects/overture/apps/console/routes/usage.svelte 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":"Bump OvertureRainfallDBService's timeout to 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fresh release brief for OvertureAmberFilterCoordinator:\n- primary outcome: separate OvertureAmberFilterCoordinator's policy from transport without behavior changes\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/overture/crates/index/src/segment.rs\n- platform constraint: Swift 6\n- known complication: an accessibility label that reads the internal enum\n\nBoth results are required, but they should remain independently reviewable. Preserve cancellation and back-pressure semantics; 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":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Check OvertureQuartzPlayerStore's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"One contained cleanup in projects/overture/packages/api/openapi.yaml: remove the obsolete OvertureMarbleTokenStore import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Profiler: Two asks around OvertureOpalRouterCoordinator: (1) assess ownership and failure handling in projects/overture/cmd/exporter/main.py; (2) capture the contract and rollback note for consumers. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"OvertureAtlasSearchCoordinator is blocking the next release because lost focus when the drawer animation finishes. I need two concrete outcomes from a single pass: lay out a staged migration for OvertureAtlasSearchCoordinator, and consolidate the duplicated normalization paths without changing behavior. Use the existing gRPC conventions in projects/overture/lib/codec/frame.cc; preserve cancellation and back-pressure semantics. 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":"En projects/overture/cmd/exporter/main.py, OvertureDriftConsoleService tiene un problema intermitente en el flujo de Room. Añade el endpoint idempotente con cursor durable, autorización tenant, spans y tests de retry.\n\nRestricciones:\n- seguir con Room\n- conservar compatibilidad y cancelación\n- limitar el cambio a OvertureDriftConsoleService Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con Room alrededor de OvertureDriftConsoleService.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"es"} +{"prompt":"In projects/overture/web/components/FilterDrawer.vue hat OvertureIrisBatchService ein sporadisches Problem im OpenTelemetry-Ablauf. Trenne Verantwortlichkeiten und entferne Duplikate, ohne API, Wire-Werte, Reihenfolge oder sichtbares Verhalten zu ändern.\n\nRandbedingungen:\n- OpenTelemetry weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf OvertureIrisBatchService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um OvertureIrisBatchService mit OpenTelemetry kompatibel.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"de"} +{"prompt":"Test Suite 'OvertureLedgerGateFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[OvertureLedgerGateFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/overture/crates/index/src/segment.rs:144: error: -[OvertureLedgerGateFlowTests 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 '-[OvertureLedgerGateFlowTests 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\nReconstruct the OvertureLedgerGateFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Test Suite 'OvertureVelaDrawerCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[OvertureVelaDrawerCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/overture/internal/auth/refresh.go:144: error: -[OvertureVelaDrawerCoordinatorTests 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 '-[OvertureVelaDrawerCoordinatorTests 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 OvertureVelaDrawerCoordinator'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-55113\n\n08:02 deploy OvertureOrbitSyncFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. From this evidence, draft consumer-facing migration guidance for OvertureOrbitSyncFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"Any races in OvertureLedgerGateStore?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"thread 'tokio-runtime-worker' panicked at projects/overture/Sources/CLI/Commands/Doctor.swift:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: overturecopperbridgeflow::scheduler::LeaseTask::flush\n at ./projects/overture/Sources/CLI/Commands/Doctor.swift:217:18\n 4: overturecopperbridgeflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nReconstruct the OvertureCopperBridgeFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"The minimum supported OpenTelemetry version in projects/overture/internal/auth/refresh.go 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":"OvertureJuniperCLICoordinator: sequence, then polish","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"On compact widths, OvertureVelaDrawerStore'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":"How does OvertureSableParserStore propagate cancellation through the Swift 6 boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"For OvertureTideWorkerCoordinator, find the unknown cause of two validators with subtly different error strings; once that is complete, give the existing implementation a read-only safety pass. Work from projects/overture/crates/index/src/segment.rs, stay with Swift 6, and preserve cancellation and back-pressure semantics. Keep the two outcomes separately reviewable.","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Milestones for replacing OvertureTideWorkerService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"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_55158'\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_55158'::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\nReconstruct the OvertureSummitProxyCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"OvertureOspreyJobCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"diff --git a/projects/overture/src/sync/reconcile.ts b/projects/overture/src/sync/reconcile.ts\nindex 62d71aa..90f3c1e 100644\n--- a/projects/overture/src/sync/reconcile.ts\n+++ b/projects/overture/src/sync/reconcile.ts\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure OverturePineMetricsFlow 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":"2026-07-30T08:14:11.409Z level=info service=overtureslateeditorflow pod=overtureslateeditorflow-7cf8 request_id=55120 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=overtureslateeditorflow request_id=55120 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=overtureslateeditorflow request_id=55120 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=overtureslateeditorflow request_id=55120 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=overtureslateeditorflow request_id=55120 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=overtureslateeditorflow request_id=55120 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=overtureslateeditorflow request_id=55120 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=overtureslateeditorflow request_id=55120 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nFind the source of this OvertureSlateEditorFlow 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":"Our support and SDK teams keep answering the same questions about OvertureAtlasSearchService, but the current prose in projects/overture/engine/render/atlas.cpp 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- preserve cancellation and back-pressure semantics\n- stay compatible with the existing gRPC deployment\n- keep the work scoped to OvertureAtlasSearchService and its direct tests\n\nThe relevant code crosses IoT fleet, Ruby, SolidJS. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"OvertureMicaProfileService needs an idempotent replay endpoint backed by FastAPI; accept a cursor, cap each page at 500 items, and return a stable continuation token.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Console: Could the reasoning behind OvertureEchoRegistryStore's Swift 6 choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Unify the OvertureQuartzPlayerService validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Assess the OvertureFernSnapshotStore diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Workspace: Ticket OPS-55131: retire the legacy replay path for OvertureCraneWorkspaceFlow\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 OvertureCraneWorkspaceFlow 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":"core","lang":"en"} +{"prompt":"Three teams extended OvertureMosaicGridStore independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current FastAPI operational envelope\n\nThis repository spans IoT fleet, Ruby, SolidJS; use its existing conventions rather than importing a new abstraction.\n\nThe target structure is settled; carry out the behavior-preserving edits rather than writing another strategy.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Em projects/overture/workers/thumbnail/consumer.ex, o OvertureOspreyJobStore tem um problema intermitente no fluxo de gRPC. Separe responsabilidades e remova duplicação sem mudar API, wire values, ordem ou comportamento observável.\n\nRestrições:\n- continuar com gRPC\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao OvertureOspreyJobStore","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"pt"} +{"prompt":"Cadre la migration de OvertureFrostPanelService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"fr"} +{"prompt":"Production says OvertureKiteSchedulerService is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current gRPC operational envelope\n\nThis repository spans IoT fleet, Ruby, SolidJS; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current OvertureEmberRelayService 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 OvertureEmberRelayService\n- preserve cancellation and back-pressure semantics\n\nSeveral teams work in this IoT fleet, Ruby, SolidJS 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":"OvertureSlateEditorCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Draft OvertureBeaconStoreService's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-55145: finish the compact OvertureCinderAuthFlow filter experience\n\nRoute: /catalog/search\nSource: projects/overture/workers/thumbnail/consumer.ex\nFramework: gRPC\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\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Finish the visible OvertureCinderAuthFlow 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":"Repository: diff --git a/projects/overture/pkg/cache/lease.rs b/projects/overture/pkg/cache/lease.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/overture/pkg/cache/lease.rs\n+++ b/projects/overture/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\nRead the artifact above as a skeptical reviewer. Is OvertureAmberFilterFlow'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":"OvertureWrenExportCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"UI ticket DES-55151: finish the compact OvertureWillowCodecCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/overture/web/components/FilterDrawer.vue\nFramework: OpenTelemetry\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 OvertureWillowCodecCoordinator 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 the reasoning behind OvertureMoonlitSDKService's gRPC choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"The behavior of OvertureSummitProxyService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/overture/Sources/CLI/Commands/Doctor.swift. 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- preserve cancellation and back-pressure semantics\n- retain the current Room operational envelope\n\nThis repository spans IoT fleet, Ruby, SolidJS; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-55146\n\n08:02 deploy OvertureLumenChartFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nReconstruct the OvertureLumenChartFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Two engineers disagree about whether OvertureBirchMigratorService's cache is authoritative. Walk the reads and writes in projects/overture/config/staging.toml and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Pipeline: Incident timeline — INC-55111\n\n08:02 deploy OvertureIrisBatchFlow 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\nFind the source of this OvertureIrisBatchFlow symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"projects/overture/Sources/App/SessionStore.swift has grown through several launches, and OvertureSummitProxyStore now mixes policy, transport, persistence, and metrics in one place. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- preserve cancellation and back-pressure semantics\n- stay compatible with the existing Room deployment\n- keep the work scoped to OvertureSummitProxyStore and its direct tests\n\nThe relevant code crosses IoT fleet, Ruby, SolidJS. Prefer evidence from the repository and make any assumption explicit.\n\nThe target structure is settled; carry out the behavior-preserving edits rather than writing another strategy.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Gateway: Incident timeline — INC-55115\n\n08:02 deploy OvertureCoralUploadFlow 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 OvertureCoralUploadFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"// projects/overture/engine/render/atlas.cpp\nfinal class OvertureAtlasSearchFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nWire OvertureAtlasSearchFlow'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.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Ticket OPS-55116: retire the legacy replay path for OvertureWrenExportFlow\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 OvertureWrenExportFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Release engineering needs a OvertureSpruceDaemonService 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":"OvertureFlintTimelineCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Responsive layout for OvertureAcornWidgetService","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Renderer: projects/overture/Sources/App/SessionStore.swift now contains OvertureDeltaCanvasService'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":"OvertureDriftConsoleStore'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":"OvertureRavenSessionService 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":"OvertureBasilRunnerCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Indexer: The OvertureMicaProfileStore 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":"Please resist widening this one: OvertureVelaDrawerService works, but staging still carries a setting that production corrected last month. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside OvertureVelaDrawerService\n- preserve cancellation and back-pressure semantics\n\nSeveral teams work in this IoT fleet, Ruby, SolidJS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"OvertureGarnetModalCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Rename OvertureSlateEditorService's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"OvertureBirchMigratorCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Apparently: // projects/overture/apps/console/routes/usage.svelte\nfinal class OvertureGarnetModalFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 OvertureGarnetModalFlow 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":"Please turn OvertureKiteSchedulerStore'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":"OvertureNimbusFormService'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":"SDK consumers are ready for durable continuation tokens, so the remaining work lives in OvertureAmberFilterService's API, storage, and worker layers. Wire the schema, repository, handler, and worker so duplicate deliveries return the original result and shutdown never acknowledges uncommitted work.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside OvertureAmberFilterService\n- preserve cancellation and back-pressure semantics\n\nSeveral teams work in this IoT fleet, Ruby, SolidJS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Teach OvertureMarbleTokenFlow to verify signed continuation tokens, reject cross-tenant cursors, and rotate keys without invalidating tokens issued during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"The data is already available in projects/overture/src/sync/reconcile.ts; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Lately: // projects/overture/cmd/exporter/main.py\nfinal class OvertureJuniperCLIFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 OvertureJuniperCLIFlow; 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":"Spell OvertureOpalRouterService's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"OvertureAmberFilterStore is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current Swift 6 operational envelope\n\nThis repository spans IoT fleet, Ruby, SolidJS; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"OvertureCinderAuthCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-55153\n\n08:02 deploy OvertureDriftConsoleCoordinator 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Capture the OvertureDriftConsoleCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"Oddly: # projects/overture/apps/console/routes/usage.svelte\n[worker.overturemosaicgridcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.overturemosaicgridcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.overturemosaicgridcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.OvertureMosaicGridCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-55159\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/overture/apps/console/routes/usage.svelte. 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":"OvertureCraneWorkspaceCoordinator needs a paired pass: finish OvertureCraneWorkspaceCoordinator's responsive empty and retry states, plus capture the contract and rollback note for consumers. Use projects/overture/services/ledger/replay.go as the source of truth, preserve the OpenTelemetry contract, and avoid unrelated cleanup.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"OvertureNovaPickerCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Add a bounded OvertureMapleQueueStore export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-55140: retire the legacy replay path for OvertureMoonlitSDKFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for OvertureMoonlitSDKFlow, 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":"Currently: Please turn OvertureMosaicGridFlow'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":"Today: projects/overture/ml/pipeline/features.py 里的 OvertureFlintTimelineStore 最近在 Room 流程中出现间歇性问题。 请给出阶段、兼容层、指标、rollback 和 ownership，先不要修改代码。\n\n约束：\n- 继续使用 Room\n- 保持兼容性和取消语义\n- 改动只限于 OvertureFlintTimelineStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"Collapse the OvertureCraneWorkspaceService wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Design the OvertureJuniperCLIService rollback","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Polish the OverturePineMetricsService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"OvertureSableParserCoordinator: handle the lingering thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Before touching projects/overture/Sources/CLI/Commands/Doctor.swift, propose how to retire its legacy format while old clients remain active for ninety days and operators retain a reversible escape hatch. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"This should remain a deliberately small patch: OvertureAcornWidgetStore has one known configuration mistake in projects/overture/config/staging.toml, 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- preserve cancellation and back-pressure semantics\n- stay compatible with the existing Swift 6 deployment\n- keep the work scoped to OvertureAcornWidgetStore and its direct tests\n\nThe relevant code crosses IoT fleet, Ruby, SolidJS. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Trace OvertureOpalRouterStore's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Context: Incident timeline — INC-55143\n\n08:02 deploy OvertureFlintTimelineFlow 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 OvertureFlintTimelineFlow 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":"Background: Incident timeline — INC-55121\n\n08:02 deploy OvertureFernSnapshotFlow 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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Turn the material above into a concise OvertureFernSnapshotFlow 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":"Question: Incident timeline — INC-55157\n\n08:02 deploy OvertureMarbleTokenCoordinator 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 OvertureMarbleTokenCoordinator 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":"Assess the OvertureCoralUploadService diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'OvertureNovaPickerFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[OvertureNovaPickerFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/overture/db/migrations/20260730_events.sql:144: error: -[OvertureNovaPickerFlowTests 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 '-[OvertureNovaPickerFlowTests 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 OvertureNovaPickerFlow'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":"Does OvertureLumenChartStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Summarize the OvertureCopperBridgeService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Does OvertureCopperBridgeStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Any races in OvertureCloudReconcilerStore?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'OvertureEmberRelayCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[OvertureEmberRelayCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/overture/engine/render/atlas.cpp:144: error: -[OvertureEmberRelayCoordinatorTests 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 '-[OvertureEmberRelayCoordinatorTests 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 OvertureEmberRelayCoordinator's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Draft OvertureCloudReconcilerService's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"What sequence would let OvertureBirchMigratorStore adopt Swift 6 with dual reads but no dual writes? Include data validation, canary scope, and the decision that ends compatibility mode. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"OvertureFrostPanelCoordinator: diagnose, then document","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Clarify OverturePineMetricsStore's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"OvertureFernSnapshotCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Before touching projects/overture/crates/index/src/segment.rs, propose how to retire its legacy format while old clients remain active for ninety days and operators retain a reversible escape hatch. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Compare OvertureCraneWorkspaceStore's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Polish the OvertureWrenExportService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"projects/overture/infra/modules/edge/main.tf now contains OverturePrismCacheStore'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":"# projects/overture/ml/pipeline/features.py\n[worker.overtureopalrouterflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.overtureopalrouterflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.overtureopalrouterflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.OvertureOpalRouterFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-55133\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/overture/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":"Observation: # projects/overture/packages/api/openapi.yaml\n[worker.overturesableparserflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.overturesableparserflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.overturesableparserflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.OvertureSableParserFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-55137\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Align OvertureSableParserFlow'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":"Constraint: // projects/overture/config/staging.toml\nfinal class OvertureBirchMigratorFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 OvertureBirchMigratorFlow 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":"# CI job 55114: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: FastAPI\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] OvertureBeaconStoreFlowIntegration.replays_after_timeout ... ok\n[test] OvertureBeaconStoreFlowIntegration.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 \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\nAdd the bounded OvertureBeaconStoreFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"One contained cleanup in projects/overture/workers/thumbnail/consumer.ex: remove the obsolete OvertureKiteSchedulerFlow import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Bring OvertureNimbusFormStore'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":"Request: projects/overture/src/sync/reconcile.ts now contains OvertureMapleQueueFlow'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.4,"slice":"core","lang":"en"} +{"prompt":"OvertureOrbitSyncCoordinator is blocking the next release because lease renewal code copied across three workers. I need two concrete outcomes from a single pass: produce a consumer guide for OvertureOrbitSyncCoordinator, and give the existing implementation a read-only safety pass. Use the existing Room conventions in projects/overture/cmd/exporter/main.py; preserve cancellation and back-pressure semantics. Keep the outcomes distinct so reviewers can see which evidence supports the assessment and which files or prose satisfy the requested change.\n\nConstraints:\n- preserve public wire values and tenant boundaries\n- cover cancellation and retry behavior\n- avoid generated code and unrelated cleanup\n- include a rollback trigger that an on-call engineer can measure\n\nThis is a fresh workstream for the release, so derive everything from the repository and the context here.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Goal: // projects/overture/workers/thumbnail/consumer.ex\nfinal class OvertureCedarPolicyFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 OvertureCedarPolicyFlow'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":"OverturePrismCacheCoordinator: give it a nicer flow","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"OvertureRavenSessionCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-55119\n\n08:02 deploy OvertureFrostPanelFlow 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 OvertureFrostPanelFlow, 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":"Bring OvertureBasilRunnerService'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":"Two deliverables are holding up OvertureIrisBatchCoordinator. First, find the unknown cause of timestamps rendered one day ahead near UTC midnight. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/overture/services/ledger/replay.go, which follows OpenTelemetry conventions and currently suffers from timestamps rendered one day ahead near UTC midnight. Preserve cancellation and back-pressure semantics.\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":"Symptom: # projects/overture/Sources/App/SessionStore.swift\n[worker.overturequartzplayerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.overturequartzplayerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.overturequartzplayerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.OvertureQuartzPlayerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-55118\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/overture/Sources/App/SessionStore.swift and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Please resist widening this one: OvertureWrenExportStore works, but staging still carries a setting that production corrected last month. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside OvertureWrenExportStore\n- preserve cancellation and back-pressure semantics\n\nSeveral teams work in this IoT fleet, Ruby, SolidJS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"# CI job 55154: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: FastAPI\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] OvertureMapleQueueCoordinatorIntegration.replays_after_timeout ... ok\n[test] OvertureMapleQueueCoordinatorIntegration.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 \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 OvertureMapleQueueCoordinator 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":"OvertureLedgerGateCoordinator: diagnose, then document","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"This should remain a deliberately small patch: OvertureOrbitSyncService has one known configuration mistake in projects/overture/ml/pipeline/features.py, not an open-ended failure investigation. Correct the known literal and the test that intentionally mirrors it; the final diff should stay local enough for an on-call engineer to verify at a glance.\n\nConstraints:\n- preserve cancellation and back-pressure semantics\n- stay compatible with the existing Room deployment\n- keep the work scoped to OvertureOrbitSyncService and its direct tests\n\nThe relevant code crosses IoT fleet, Ruby, SolidJS. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"PM is preparing the OvertureAtlasSearchStore 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 OvertureAtlasSearchStore\n- preserve cancellation and back-pressure semantics\n\nSeveral teams work in this IoT fleet, Ruby, SolidJS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/overture/infra/modules/edge/main.tf b/projects/overture/infra/modules/edge/main.tf\nindex 62d71aa..90f3c1e 100644\n--- a/projects/overture/infra/modules/edge/main.tf\n+++ b/projects/overture/infra/modules/edge/main.tf\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit OvertureRainfallDBFlow 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":"Headsup: projects/overture/cmd/exporter/main.py の OvertureFlintTimelineService で、Room の flow に断続的な問題が起きています。 現在の flow を読み、ownership、cancel、順序が安全か評価してください。分析だけで十分です。\n\n制約:\n- Room を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は OvertureFlintTimelineService のみ","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"ja"} +{"prompt":"Production says OvertureEchoRegistryService is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current Swift 6 operational envelope\n\nThis repository spans IoT fleet, Ruby, SolidJS; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Why does OvertureGarnetModalService's FastAPI worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-55127: finish the compact OvertureHarborIndexFlow filter experience\n\nRoute: /catalog/search\nSource: projects/overture/config/staging.toml\nFramework: Swift 6\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 OvertureHarborIndexFlow 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":"Ticket OPS-55136: retire the legacy replay path for OverturePrismCacheFlow\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 OverturePrismCacheFlow 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":"OvertureCedarPolicyCoordinator needs a paired pass: change OvertureCedarPolicyCoordinator's known staging timeout from 15 to 30 seconds, plus capture the contract and rollback note for consumers. Use projects/overture/ui/settings/PrivacyPane.tsx as the source of truth, preserve the gRPC contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"FYI: Does OvertureLedgerGateService preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Responsive layout for OvertureJuniperCLIStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"OvertureSpruceDaemonCoordinator: ship a sensible version","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Meanwhile: # projects/overture/engine/render/atlas.cpp\n[worker.overturecloudreconcilerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.overturecloudreconcilerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.overturecloudreconcilerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.OvertureCloudReconcilerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-55130\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/overture/engine/render/atlas.cpp and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"2026-07-30T08:14:11.409Z level=info service=overturekiteschedulercoordinator pod=overturekiteschedulercoordinator-7cf8 request_id=55155 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=overturekiteschedulercoordinator request_id=55155 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=overturekiteschedulercoordinator request_id=55155 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=overturekiteschedulercoordinator request_id=55155 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=overturekiteschedulercoordinator request_id=55155 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=overturekiteschedulercoordinator request_id=55155 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=overturekiteschedulercoordinator request_id=55155 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=overturekiteschedulercoordinator request_id=55155 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nReconstruct the OvertureKiteSchedulerCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Locally: Test Suite 'OvertureAsterWebhookFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[OvertureAsterWebhookFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/overture/app/src/main/SyncWorker.kt:144: error: -[OvertureAsterWebhookFlowTests 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 '-[OvertureAsterWebhookFlowTests 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. Find the source of this OvertureAsterWebhookFlow 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":"A previously stable test around OvertureNovaPickerService now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/overture/Sources/CLI/Commands/Doctor.swift b/projects/overture/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/overture/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/overture/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure OvertureSpruceDaemonFlow 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":"Two engineers disagree about whether OvertureGarnetModalStore's cache is authoritative. Walk the reads and writes in projects/overture/app/src/main/SyncWorker.kt and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Split projects/overture/cmd/exporter/main.py by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Extract OvertureAsterWebhookService's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Rename OvertureRainfallDBStore's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"I inherited OvertureWillowCodecService and need a careful read of projects/overture/services/ledger/replay.go 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- preserve cancellation and back-pressure semantics\n- stay compatible with the existing OpenTelemetry deployment\n- keep the work scoped to OvertureWillowCodecService and its direct tests\n\nThe relevant code crosses IoT fleet, Ruby, SolidJS. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-55138: retire the legacy replay path for OvertureDeltaCanvasFlow\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 OvertureDeltaCanvasFlow 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":"Production: Ticket OPS-55142: retire the legacy replay path for OvertureRavenSessionFlow\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 OvertureRavenSessionFlow 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":"Staging: Two deliverables are holding up OvertureBeaconStoreCoordinator. First, separate OvertureBeaconStoreCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/overture/src/sync/reconcile.ts, which follows FastAPI conventions and currently suffers from duplicate retries after a network handoff. Preserve cancellation and back-pressure semantics.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"OvertureLumenChartCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Remove OvertureAsterWebhookStore's stray comma","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"For OvertureAsterWebhookCoordinator, separate OvertureAsterWebhookCoordinator's policy from transport without behavior changes; once that is complete, give the existing implementation a read-only safety pass. Work from projects/overture/apps/console/routes/usage.svelte, stay with FastAPI, and preserve cancellation and back-pressure semantics. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Is there a cleaner way to separate OvertureCinderAuthService'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":"OvertureDeltaCanvasCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Atlas: projects/overture/services/ledger/replay.go の OvertureWillowCodecFlow で、OpenTelemetry の flow に断続的な問題が起きています。 責務を分離して重複をなくし、API、wire value、順序、観測可能な動作は変えないでください。\n\n制約:\n- OpenTelemetry を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は OvertureWillowCodecFlow のみ","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"ja"} +{"prompt":"PM needs a concise migration note for OvertureRavenSessionStore, 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: Ticket OPS-55144: retire the legacy replay path for OvertureMicaProfileFlow\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 OvertureMicaProfileFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Incident timeline — INC-55141\n\n08:02 deploy OvertureNimbusFormFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current OvertureNimbusFormFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Documente o contrato de OvertureHarborIndexService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"pt"} +{"prompt":"Fresh release brief for OvertureCoralUploadCoordinator:\n- primary outcome: change OvertureCoralUploadCoordinator'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/overture/workers/thumbnail/consumer.ex\n- platform constraint: gRPC\n- known complication: a query plan that changes after statistics refresh\n\nBoth results are required, but they should remain independently reviewable. Preserve cancellation and back-pressure semantics; 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.6,"slice":"mixed","lang":"en"} +{"prompt":"Draft OvertureSlateEditorStore's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Zentriere das OvertureFrostPanelStore-Modal","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"de"} diff --git a/data/purpose-prompts.jsonl b/data/purpose-prompts.jsonl index 8438e58..c4f55bc 100644 --- a/data/purpose-prompts.jsonl +++ b/data/purpose-prompts.jsonl @@ -1,8043 +1,7846 @@ -{"prompt":"design the offline sync layer for Kestrel, our SwiftUI notes app. i need a conflict resolution story for concurrent edits on iPad + Mac, plus a migration path off the current UserDefaults blob. write it up as an RFC with the tradeoffs of CRDT vs last-write-wins spelled out","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} +{"prompt":"design the offline sync layer for Kestrel, our SwiftUI notes app. i need a conflict resolution story for concurrent edits on iPad + Mac, plus a migration path off the current UserDefaults blob. write it up as an RFC with the tradeoffs of CRDT vs last-write-wins spelled out","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"add a GET /v1/exports endpoint in Go that streams NDJSON out of the reports table, cursor paginated on (created_at, id)","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"make the toolbar collapse on scroll","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"make the toolbar collapse on scroll","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"bump golang.org/x/net to 0.38","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"SessionStore.swift is up to 900 lines. pull the keychain access and the token refresh timer out into their own types, same behavior after","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"crashes on launch for a handful of users on 18.4, never in the simulator. crashlytics gives me this and i'm lost:\n\nFatal Exception: NSInternalInconsistencyException\nModifying state during view update, this will cause undefined behavior.\n0 SwiftUI 0x1a2 closure #1 in AttributeGraph.withMutation + 412\n1 SwiftUI 0x1a2 StateBox.setValue(_:transaction:) + 88\n2 Kestrel 0x104 LibraryViewModel.reload() + 240 (LibraryViewModel.swift:118)\n3 Kestrel 0x104 closure #2 in LibraryView.body.getter + 96 (LibraryView.swift:64)\n4 SwiftUI 0x1a2 ViewGraph.updateOutputs + 1204\n5 UIKitCore 0x18f _UIUpdateSequenceRun + 84\n6 CoreFoundation 0x180 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 36\n\nLibraryViewModel.reload() is called from .task and from a NotificationCenter observer for .didFinishImport. no idea why only device builds","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"pasted-context","lang":"en"} -{"prompt":"walk me through how our terraform module wires ALB target groups to the ECS service — mainly i want to know who actually owns the health check config, the tg or the task def","purpose":"review","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"draft release notes for 3.4 off the merged PRs since the v3.3 tag, user facing tone, group by area","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"how would we get off single-node postgres onto citus for the events table? i don't want code yet, just the phases, what has to be dual-written, and which of our queries break when there's no global sequence","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"our openapi.yaml has bare field names and nothing else for /webhooks/*. fill in descriptions and realistic examples for every field and document the retry/backoff semantics we already implement. don't touch the handlers","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"generate openapi.yaml from the existing gin route handlers and struct tags, and wire swag into the make target so it regenerates on build","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"empty state for the workspace picker — illustration, one line of copy, a Create workspace button. match the spacing of the other empties","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} +{"prompt":"SessionStore.swift is up to 900 lines. pull the keychain access and the token refresh timer out into their own types, same behavior after","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"crashes on launch for a handful of users on 18.4, never in the simulator. crashlytics gives me this and i'm lost:\n\nFatal Exception: NSInternalInconsistencyException\nModifying state during view update, this will cause undefined behavior.\n0 SwiftUI 0x1a2 closure #1 in AttributeGraph.withMutation + 412\n1 SwiftUI 0x1a2 StateBox.setValue(_:transaction:) + 88\n2 Kestrel 0x104 LibraryViewModel.reload() + 240 (LibraryViewModel.swift:118)\n3 Kestrel 0x104 closure #2 in LibraryView.body.getter + 96 (LibraryView.swift:64)\n4 SwiftUI 0x1a2 ViewGraph.updateOutputs + 1204\n5 UIKitCore 0x18f _UIUpdateSequenceRun + 84\n6 CoreFoundation 0x180 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 36\n\nLibraryViewModel.reload() is called from .task and from a NotificationCenter observer for .didFinishImport. no idea why only device builds","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"walk me through how our terraform module wires ALB target groups to the ECS service — mainly i want to know who actually owns the health check config, the tg or the task def","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"draft release notes for 3.4 off the merged PRs since the v3.3 tag, user facing tone, group by area","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"how would we get off single-node postgres onto citus for the events table? i don't want code yet, just the phases, what has to be dual-written, and which of our queries break when there's no global sequence","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"our openapi.yaml has bare field names and nothing else for /webhooks/*. fill in descriptions and realistic examples for every field and document the retry/backoff semantics we already implement. don't touch the handlers","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"generate openapi.yaml from the existing gin route handlers and struct tags, and wire swag into the make target so it regenerates on build","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"empty state for the workspace picker — illustration, one line of copy, a Create workspace button. match the spacing of the other empties","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"rename the local var `resp` to `httpResp` in fetchInvoices, it shadows the outer one and it's confusing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"we're calling it Organization everywhere in the API but Tenant in the db layer and Account in a few older services. standardize on Organization across the whole repo including column aliases and proto field comments, no functional change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"we're calling it Organization everywhere in the API but Tenant in the db layer and Account in a few older services. standardize on Organization across the whole repo including column aliases and proto field comments, no functional change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the nightly ingest job silently processes 0 rows about one run in five, no error logged, no alert. figure out what's happening","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"why does the shipment reducer dispatch twice for a single scan event? not saying it's wrong, i just want to understand the flow before i touch it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.45,"slice":"boundary","lang":"en"} -{"prompt":"plan and then build the rate limiter for our public API — per-key token bucket, redis backed, needs to survive a redis blip without locking everyone out. give me the design first then the go code","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.75,"slice":"mixed","lang":"en"} +{"prompt":"why does the shipment reducer dispatch twice for a single scan event? not saying it's wrong, i just want to understand the flow before i touch it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"plan and then build the rate limiter for our public API — per-key token bucket, redis backed, needs to survive a redis blip without locking everyone out. give me the design first then the go code","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"commit message for these staged changes pls","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"milestones for the Q3 auth rewrite","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"need a background worker in python that watches the s3 bucket prefix raw/telemetry/, batches parquet files into 15 minute windows, and upserts into clickhouse. idempotent on rerun, and it has to handle files landing out of order up to 2h late. use the existing boto session helper in common/aws.py","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"need a background worker in python that watches the s3 bucket prefix raw/telemetry/, batches parquet files into 15 minute windows, and upserts into clickhouse. idempotent on rerun, and it has to handle files landing out of order up to 2h late. use the existing boto session helper in common/aws.py","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"sketch the interaction model for the new inline comment threads (hover affordance, focus states, keyboard nav) and then implement the React side. no backend, the endpoints exist","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"feature flag `new_billing_summary` is still gated to staff only, open it to everyone","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.15,"slice":"core","lang":"en"} -{"prompt":"dedupe the three copies of retryWithBackoff","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"the /search endpoint got 4x slower after we shipped last thursday and nothing in that diff touches search. p99 went 180ms -> 750ms. where do i even start","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"boundary","lang":"en"} -{"prompt":"is our jwt refresh flow safe against replay if someone grabs a refresh token off a stolen device? read through auth/refresh.go and tell me what you think, don't change anything yet","purpose":"review","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"compare our current celery setup against just using postgres SKIP LOCKED for the job queue. we do maybe 200 jobs/min, mostly short","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"explain what pkg/ledger/reconcile.go actually does, line by line if you have to. inherited it and nobody left knows","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"summarize the reconcile flow for the onboarding doc — same file, but i want three paragraphs a new hire can read, not a code walkthrough","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"boundary","lang":"en"} +{"prompt":"feature flag `new_billing_summary` is still gated to staff only, open it to everyone","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"dedupe the three copies of retryWithBackoff","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the /search endpoint got 4x slower after we shipped last thursday and nothing in that diff touches search. p99 went 180ms -> 750ms. where do i even start","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"is our jwt refresh flow safe against replay if someone grabs a refresh token off a stolen device? read through auth/refresh.go and tell me what you think, don't change anything yet","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"compare our current celery setup against just using postgres SKIP LOCKED for the job queue. we do maybe 200 jobs/min, mostly short","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"explain what pkg/ledger/reconcile.go actually does, line by line if you have to. inherited it and nobody left knows","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"roadmap for deprecating the v1 REST API. we have 40ish external integrators, 9 months of runway, and i need something i can show the CTO on monday","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"how should we shard the notification fanout? design only","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"we want an audit log for every admin mutation. figure out the approach — trigger based, app level, or CDC off the wal — and write up which one you'd pick and why before anyone writes code","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.75,"slice":"boundary","lang":"en"} -{"prompt":"implement soft delete on the projects table: deleted_at column, partial unique index on slug where deleted_at is null, and update every query in internal/projects to filter it. also a nightly purge after 30 days","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"write a small CLI in rust, `envdiff`, that takes two .env files and prints keys only present in one, keys whose values differ, and exits 1 if there's any drift","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"webhook signature verification for the stripe events handler, constant time compare, tolerate 5 min clock skew","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"dark mode for the settings sheet is unreadable — the secondary labels are basically the same value as the background. go through Settings/ and fix the color roles properly instead of hardcoding hex","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"add a skeleton loader to the analytics cards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"the primary button has 14px padding on web and 12 on the marketing site. make them both 14","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"typo in the onboarding modal, 'Contine' -> 'Continue'","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"core","lang":"en"} +{"prompt":"how should we shard the notification fanout? design only","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"we want an audit log for every admin mutation. figure out the approach — trigger based, app level, or CDC off the wal — and write up which one you'd pick and why before anyone writes code","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"implement soft delete on the projects table: deleted_at column, partial unique index on slug where deleted_at is null, and update every query in internal/projects to filter it. also a nightly purge after 30 days","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"write a small CLI in rust, `envdiff`, that takes two .env files and prints keys only present in one, keys whose values differ, and exits 1 if there's any drift","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"webhook signature verification for the stripe events handler, constant time compare, tolerate 5 min clock skew","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"dark mode for the settings sheet is unreadable — the secondary labels are basically the same value as the background. go through Settings/ and fix the color roles properly instead of hardcoding hex","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"add a skeleton loader to the analytics cards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the primary button has 14px padding on web and 12 on the marketing site. make them both 14","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"typo in the onboarding modal, 'Contine' -> 'Continue'","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"set the readiness probe initialDelaySeconds to 20 in the api deployment, it's flapping on cold start","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"break InvoiceService apart. right now it does pdf rendering, tax calc, and the stripe calls in one class and i can't test any of it in isolation. keep the public methods identical so callers don't change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} +{"prompt":"break InvoiceService apart. right now it does pdf rendering, tax calc, and the stripe calls in one class and i can't test any of it in isolation. keep the public methods identical so callers don't change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"collapse our four nearly identical Dockerfiles into one multi-stage with build args","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"convert the callback-style code in lib/uploader.js to async/await, don't change any behavior including the weird double-callback guard","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"flaky test, fails maybe 1 in 12 locally and more in CI:\n\n=================================== FAILURES ===================================\n_______________________ test_expiry_sweeper_removes_stale ______________________\n\n async def test_expiry_sweeper_removes_stale(session, freezer):\n await create_lease(session, ttl=30)\n freezer.move_to('+45s')\n await sweeper.run_once(session)\n> assert await count_leases(session) == 0\nE assert 1 == 0\nE + where 1 = \n\ntests/test_sweeper.py:88: AssertionError\n------------------------------ Captured log call -------------------------------\nDEBUG app.sweeper:sweeper.py:41 sweep start cutoff=2026-03-02T10:00:45+00:00\nDEBUG app.sweeper:sweeper.py:57 candidate leases=1\nDEBUG app.sweeper:sweeper.py:63 skipped lease id=8812 reason=locked\n=========================== short test summary info ============================\nFAILED tests/test_sweeper.py::test_expiry_sweeper_removes_stale - assert 1 == 0\n1 failed, 213 passed, 4 skipped in 61.42s\n\nthe 'locked' skip only shows up on the failing runs","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} {"prompt":"memory climbs about 40MB/hour in the websocket gateway until the pod gets oomkilled overnight. connections are stable around 3k. help me find the leak","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"gradle build hangs at :app:kaptDebugKotlin, no output, have to ctrl-c after 10 min. worked yesterday","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} +{"prompt":"gradle build hangs at :app:kaptDebugKotlin, no output, have to ctrl-c after 10 min. worked yesterday","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"PR description for the branch feat/multi-region-reads, include the migration steps ops needs to run and the rollback","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"write doc comments for every exported symbol in pkg/schedule, godoc style, mention the timezone caveat on NextRun","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"our README still says node 16 and describes the old yarn workspaces setup. rewrite the getting started section for the current pnpm + turbo layout","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"escribe la documentación del endpoint POST /pedidos en el openapi, incluyendo los códigos de error y un ejemplo de payload real","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"es"} +{"prompt":"write doc comments for every exported symbol in pkg/schedule, godoc style, mention the timezone caveat on NextRun","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"our README still says node 16 and describes the old yarn workspaces setup. rewrite the getting started section for the current pnpm + turbo layout","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"escribe la documentación del endpoint POST /pedidos en el openapi, incluyendo los códigos de error y un ejemplo de payload real","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} {"prompt":"changelog entry for the 2.1.7 patch, we fixed the timezone bug in recurring reminders and dropped support for android 8","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"translate the error strings in Localizable.strings to de and fr, keep the format specifiers in the same order","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"架构一下我们的实时协作编辑，需要支持离线编辑和多端同步，先给方案不要写代码","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"zh"} +{"prompt":"架构一下我们的实时协作编辑，需要支持离线编辑和多端同步，先给方案不要写代码","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"zh"} {"prompt":"we keep firefighting the same three classes of prod incident. help me put together a plan for the next quarter that actually reduces them — my notes: no request tracing across services, alerts fire on symptoms not causes, and nobody owns the canary step","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"how do i structure a plugin system for the editor so third parties can add commands without us shipping their code in the bundle? want the design tradeoffs, esp sandboxing","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"add cursor based pagination to the ListDevices grpc method, keep the old offset params working for one release","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"parse the vendor's fixed width inventory feed. spec attached below in the ticket text, 320 byte records, EBCDIC in a couple of the numeric fields apparently. go, streaming, don't load the whole file","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"wire up SSO with our okta tenant — SAML, JIT provisioning into the users table, and map the groups claim onto our existing roles","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"drag to reorder on the playlist rows, with haptics","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"build the compare view: two device timelines side by side, shared x axis, scrub together, and it needs to stay smooth at 5k points each. we're on SwiftUI Charts","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"nudge the badge 2px left on the tab bar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"how do i structure a plugin system for the editor so third parties can add commands without us shipping their code in the bundle? want the design tradeoffs, esp sandboxing","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"add cursor based pagination to the ListDevices grpc method, keep the old offset params working for one release","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"parse the vendor's fixed width inventory feed. spec attached below in the ticket text, 320 byte records, EBCDIC in a couple of the numeric fields apparently. go, streaming, don't load the whole file","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"wire up SSO with our okta tenant — SAML, JIT provisioning into the users table, and map the groups claim onto our existing roles","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"drag to reorder on the playlist rows, with haptics","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"build the compare view: two device timelines side by side, shared x axis, scrub together, and it needs to stay smooth at 5k points each. we're on SwiftUI Charts","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"nudge the badge 2px left on the tab bar","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"prod is on log level debug, drop it to info","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"the retry count is 3 but the ticket says it should be 5 for the payout webhook. one line, i know where it is, worker/payouts.ts around line 70","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"add .DS_Store and .idea/ to gitignore and untrack whatever's already in","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.15,"slice":"core","lang":"en"} -{"prompt":"extract the validation out of every handler into middleware. it's copy pasted in 22 places and i want them all going through one path with the same error shape","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} +{"prompt":"the retry count is 3 but the ticket says it should be 5 for the payout webhook. one line, i know where it is, worker/payouts.ts around line 70","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"add .DS_Store and .idea/ to gitignore and untrack whatever's already in","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"extract the validation out of every handler into middleware. it's copy pasted in 22 places and i want them all going through one path with the same error shape","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"kill the God object. AppState in our react-native app holds auth, cart, feature flags, and the socket. split by domain, keep the selector API stable for now","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"move the shared types into a packages/contracts workspace so the api and the web app stop importing across each other's src/","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"getting this on every deploy to the eu cluster only:\n\nEvents:\n Type Reason Age From Message\n ---- ------ ---- ---- -------\n Normal Scheduled 4m12s default-scheduler Successfully assigned prod/api-7d9c8-hlq2n to ip-10-3-42-118\n Normal Pulled 4m10s kubelet Container image \"registry.internal/api:9f2c1a\" already present on machine\n Normal Created 4m10s kubelet Created container api\n Normal Started 4m9s kubelet Started container api\n Warning Unhealthy 3m40s (x6 over 4m) kubelet Readiness probe failed: Get \"http://10.3.42.7:8080/readyz\": context deadline exceeded\n Warning BackOff 2m1s (x4 over 3m) kubelet Back-off restarting failed container api\n\nand in the container logs:\nlevel=info msg=\"connecting to pgbouncer\" host=pgb.eu-central.internal\nlevel=warn msg=\"tls handshake retry\" attempt=1\nlevel=warn msg=\"tls handshake retry\" attempt=2\nlevel=fatal msg=\"x509: certificate is valid for pgb.us-east.internal, not pgb.eu-central.internal\"\n\nus-east is totally fine which is what confuses me","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} -{"prompt":"someone dropped this in #eng-help and left for the day:\n\n> hey so the CSV export for org 44121 has been producing files where about 3% of rows have the amount column shifted one to the right. only that org. started sometime after the 12th. i checked and their data doesn't look special, no weird currency. the file opens fine in excel it's just wrong. customer is escalating\n\ncan you dig into it? export code is in services/reporting/csv.py","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"pasted-context","lang":"en"} -{"prompt":"audio glitches for ~200ms every time we switch bluetooth routes on the embedded player. only on the nRF52 build, not the sim","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"is it a problem that we're doing the password hash on the request goroutine with argon2 at 64MB? worried about a thundering herd at login but i haven't measured anything","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} +{"prompt":"getting this on every deploy to the eu cluster only:\n\nEvents:\n Type Reason Age From Message\n ---- ------ ---- ---- -------\n Normal Scheduled 4m12s default-scheduler Successfully assigned prod/api-7d9c8-hlq2n to ip-10-3-42-118\n Normal Pulled 4m10s kubelet Container image \"registry.internal/api:9f2c1a\" already present on machine\n Normal Created 4m10s kubelet Created container api\n Normal Started 4m9s kubelet Started container api\n Warning Unhealthy 3m40s (x6 over 4m) kubelet Readiness probe failed: Get \"http://10.3.42.7:8080/readyz\": context deadline exceeded\n Warning BackOff 2m1s (x4 over 3m) kubelet Back-off restarting failed container api\n\nand in the container logs:\nlevel=info msg=\"connecting to pgbouncer\" host=pgb.eu-central.internal\nlevel=warn msg=\"tls handshake retry\" attempt=1\nlevel=warn msg=\"tls handshake retry\" attempt=2\nlevel=fatal msg=\"x509: certificate is valid for pgb.us-east.internal, not pgb.eu-central.internal\"\n\nus-east is totally fine which is what confuses me","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"someone dropped this in #eng-help and left for the day:\n\n> hey so the CSV export for org 44121 has been producing files where about 3% of rows have the amount column shifted one to the right. only that org. started sometime after the 12th. i checked and their data doesn't look special, no weird currency. the file opens fine in excel it's just wrong. customer is escalating\n\ncan you dig into it? export code is in services/reporting/csv.py","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"audio glitches for ~200ms every time we switch bluetooth routes on the embedded player. only on the nRF52 build, not the sim","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"is it a problem that we're doing the password hash on the request goroutine with argon2 at 64MB? worried about a thundering herd at login but i haven't measured anything","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"review the diff on my branch before i open the PR, specifically the transaction boundaries in the transfer path","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"what's the difference between our useSyncedQuery hook and just using react-query's useQuery with our fetcher? feels like we reimplemented it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"document the event payload schemas for the pubsub topics in docs/events.md AND add the missing JSON schema files under schemas/ so we can validate in CI","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.55,"slice":"mixed","lang":"en"} +{"prompt":"what's the difference between our useSyncedQuery hook and just using react-query's useQuery with our fetcher? feels like we reimplemented it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"document the event payload schemas for the pubsub topics in docs/events.md AND add the missing JSON schema files under schemas/ so we can validate in CI","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} {"prompt":"figure out why the checkout total is off by a cent for some carts and then write up the postmortem, we told the customer we'd have both by friday","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"picking the payment-flow bug back up from yesterday — the 3DS redirect lands on a blank page maybe a third of the time in safari. no console error, network tab shows the POST to /confirm returning 302 and then nothing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} +{"prompt":"picking the payment-flow bug back up from yesterday — the 3DS redirect lands on a blank page maybe a third of the time in safari. no console error, network tab shows the POST to /confirm returning 302 and then nothing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"come up with the migration plan for moving our 4TB mysql instance to aurora with under 15 min of write downtime, and list the go/no-go checks","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"break the vector search feature into two week chunks for a team of three","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"before we build anything, i want an ADR on whether the mobile clients talk to a BFF or straight to the services. we have ios, android, and a watch app coming","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.75,"slice":"boundary","lang":"en"} -{"prompt":"implement optimistic locking on the inventory adjust path with a version column, return 409 with the current version on conflict","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"hook the feature flag SDK into our fastapi app so flags resolve once per request and get attached to the request state. also expose them on /debug/flags behind the admin guard","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"write the migration + backfill for splitting `full_name` into first/last on the contacts table. 8M rows, can't lock it","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} +{"prompt":"break the vector search feature into two week chunks for a team of three","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"before we build anything, i want an ADR on whether the mobile clients talk to a BFF or straight to the services. we have ios, android, and a watch app coming","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"implement optimistic locking on the inventory adjust path with a version column, return 409 with the current version on conflict","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"hook the feature flag SDK into our fastapi app so flags resolve once per request and get attached to the request state. also expose them on /debug/flags behind the admin guard","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"write the migration + backfill for splitting `full_name` into first/last on the contacts table. 8M rows, can't lock it","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"the achievement popup needs to feel good — slide up, slight overshoot, confetti burst, auto dismiss after 3s but pause if the player is holding a button. unity, we're using the UI toolkit","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"responsive pass on the pricing page, it's broken between 768 and 900","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"responsive pass on the pricing page, it's broken between 768 and 900","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} {"prompt":"add a compact density option to the data grid — user setting, persists, rows go 44 -> 32 and the font drops a step","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"swap the deprecated `substr` calls for slice in utils/text.ts, six spots","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.15,"slice":"boundary","lang":"en"} -{"prompt":"cors is missing the staging origin, add https://staging.acme.dev to the allowlist","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.15,"slice":"core","lang":"en"} -{"prompt":"off by one in the pagination footer, it says 'showing 1-20 of 20' when there are 21. i know it's the `hasMore ? end : total` bit in Pager.tsx, just fix it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"consolidate the two http clients. one's axios with our interceptors, one's raw fetch with a hand rolled retry. pick fetch, keep every call site's behavior identical including the odd 204 handling","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"swap the deprecated `substr` calls for slice in utils/text.ts, six spots","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"cors is missing the staging origin, add https://staging.acme.dev to the allowlist","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"off by one in the pagination footer, it says 'showing 1-20 of 20' when there are 21. i know it's the `hasMore ? end : total` bit in Pager.tsx, just fix it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"consolidate the two http clients. one's axios with our interceptors, one's raw fetch with a hand rolled retry. pick fetch, keep every call site's behavior identical including the odd 204 handling","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"untangle the import cycle between internal/billing and internal/accounts","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"simplify this state machine, there are 11 states and i'm pretty sure 4 are unreachable. behavior must not change for the reachable ones","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"rust won't let me do the thing and i've been at it an hour:\n\nerror[E0502]: cannot borrow `self.buffer` as mutable because it is also borrowed as immutable\n --> src/decoder.rs:214:13\n |\n209 | let frame = self.peek_frame()?;\n | ---- immutable borrow occurs here\n...\n214 | self.buffer.advance(frame.len);\n | ^^^^^^^^^^^^^^^^^^^ mutable borrow occurs here\n...\n219 | Ok(frame)\n | ----- immutable borrow later used here\n\nerror[E0499]: cannot borrow `*self` as mutable more than once at a time\n --> src/decoder.rs:231:9\n |\n230 | let hdr = self.header_mut();\n | ---- first mutable borrow occurs here\n231 | self.reset_crc();\n | ^^^^ second mutable borrow occurs here\n\nerror: could not compile `wire-codec` (lib) due to 2 previous errors\n\npeek_frame returns a &Frame into the buffer. what's the right shape here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"simplify this state machine, there are 11 states and i'm pretty sure 4 are unreachable. behavior must not change for the reachable ones","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"rust won't let me do the thing and i've been at it an hour:\n\nerror[E0502]: cannot borrow `self.buffer` as mutable because it is also borrowed as immutable\n --> src/decoder.rs:214:13\n |\n209 | let frame = self.peek_frame()?;\n | ---- immutable borrow occurs here\n...\n214 | self.buffer.advance(frame.len);\n | ^^^^^^^^^^^^^^^^^^^ mutable borrow occurs here\n...\n219 | Ok(frame)\n | ----- immutable borrow later used here\n\nerror[E0499]: cannot borrow `*self` as mutable more than once at a time\n --> src/decoder.rs:231:9\n |\n230 | let hdr = self.header_mut();\n | ---- first mutable borrow occurs here\n231 | self.reset_crc();\n | ^^^^ second mutable borrow occurs here\n\nerror: could not compile `wire-codec` (lib) due to 2 previous errors\n\npeek_frame returns a &Frame into the buffer. what's the right shape here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} {"prompt":"intermittent 502s from the api gateway, maybe 1 in 400 requests, no pattern i can see by endpoint or region. logs on our side show a clean 200","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"warum liefert unser cache manchmal veraltete daten obwohl die TTL 30s ist? ich verstehe es nicht, redis sieht sauber aus","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"de"} -{"prompt":"read through the terraform in infra/prod and tell me what would break if we lost the whole eu-west-1 region tomorrow","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"does this query plan look sane to you? it's the dashboard aggregate, runs 400ms on 2M rows and i can't tell if that's good or bad for what it's doing","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"warum liefert unser cache manchmal veraltete daten obwohl die TTL 30s ist? ich verstehe es nicht, redis sieht sauber aus","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} +{"prompt":"read through the terraform in infra/prod and tell me what would break if we lost the whole eu-west-1 region tomorrow","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"does this query plan look sane to you? it's the dashboard aggregate, runs 400ms on 2M rows and i can't tell if that's good or bad for what it's doing","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"explain the difference in guarantees between our at-least-once sqs consumer and the kafka one, i keep confusing myself in design reviews","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"internal blog post about the latency work we did last quarter. audience is other engineers here, ~800 words, i can give you the numbers","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"runbook for the on-call rotation covering the four alerts that actually page us","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"internal blog post about the latency work we did last quarter. audience is other engineers here, ~800 words, i can give you the numbers","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"runbook for the on-call rotation covering the four alerts that actually page us","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"the CONTRIBUTING.md is 3 lines. write a real one — branch naming, how to run the test suite, what we expect in a PR, and the codegen step people always forget","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"spec out the multiplayer lobby then get the netcode skeleton in — matchmaking rules first as a doc, then the actual go server with the room state machine","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.85,"slice":"mixed","lang":"en"} -{"prompt":"evaluate whether we should adopt bazel. monorepo, ~60 services, mixed go/ts/python, current builds are makefiles and 14 min of CI. i want a recommendation with a phased rollout, not a yes/no","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} +{"prompt":"spec out the multiplayer lobby then get the netcode skeleton in — matchmaking rules first as a doc, then the actual go server with the room state machine","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"evaluate whether we should adopt bazel. monorepo, ~60 services, mixed go/ts/python, current builds are makefiles and 14 min of CI. i want a recommendation with a phased rollout, not a yes/no","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"what's a reasonable retention + partitioning strategy for the raw telemetry table? we ingest ~90GB/day and only ever query the last 14 days interactively","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"write the presigned upload flow: POST /uploads returns a presigned put + an id, then a lambda on s3:ObjectCreated validates the mime type and marks the row ready. reject anything over 25MB, and clean up rows that never get an object after 24h","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"give the CLI a `--json` output mode across all subcommands, stable field names, and make sure nothing else writes to stdout when it's set","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} +{"prompt":"write the presigned upload flow: POST /uploads returns a presigned put + an id, then a lambda on s3:ObjectCreated validates the mime type and marks the row ready. reject anything over 25MB, and clean up rows that never get an object after 24h","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"give the CLI a `--json` output mode across all subcommands, stable field names, and make sure nothing else writes to stdout when it's set","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"batch the embedding calls in the indexer, 64 at a time, with a semaphore so we don't blow the rate limit. retry the whole batch on 429 with jitter","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"sticky column headers in the transactions table, and the horizontal scroll shadow like linear has","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the map pins overlap badly when zoomed out. cluster them","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"make the loading spinner smaller on mobile","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"increase the lambda timeout to 60s and memory to 1024","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"sticky column headers in the transactions table, and the horizontal scroll shadow like linear has","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the map pins overlap badly when zoomed out. cluster them","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"make the loading spinner smaller on mobile","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"increase the lambda timeout to 60s and memory to 1024","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} {"prompt":"we're pinning pydantic 1.10 in requirements.txt but the code is v2 style. change the pin","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"the healthcheck path in nginx.conf points at /health but the app serves /healthz. one char fix basically","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"pull the pure functions out of the OrderViewModel so i can unit test them without a view. no logic changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"we have `getUserById`, `fetchUser`, `loadUserRecord` and `userLookup` all doing the same query with slightly different caching. unify them","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"replace the stringly typed status field with a proper enum everywhere, including the db check constraint and the ts union","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"espresso test keeps failing on CI but passes on my machine every time. IdlingResource is registered. anyone would think it's timing but i've bumped the timeouts to 30s and it still fails at the same assertion","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"pull the pure functions out of the OrderViewModel so i can unit test them without a view. no logic changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"we have `getUserById`, `fetchUser`, `loadUserRecord` and `userLookup` all doing the same query with slightly different caching. unify them","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"replace the stringly typed status field with a proper enum everywhere, including the db check constraint and the ts union","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"espresso test keeps failing on CI but passes on my machine every time. IdlingResource is registered. anyone would think it's timing but i've bumped the timeouts to 30s and it still fails at the same assertion","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"npm ci exploded on the release build:\n\nnpm error code ERESOLVE\nnpm error ERESOLVE could not resolve\nnpm error\nnpm error While resolving: @acme/design-system@4.2.0\nnpm error Found: react@19.1.0\nnpm error node_modules/react\nnpm error react@\"^19.1.0\" from the root project\nnpm error\nnpm error Could not resolve dependency:\nnpm error peer react@\"^18.2.0\" from @acme/charts@2.9.4\nnpm error node_modules/@acme/charts\nnpm error @acme/charts@\"^2.9.0\" from @acme/design-system@4.2.0\nnpm error\nnpm error Conflicting peer dependency: react@18.3.1\nnpm error node_modules/react\nnpm error peer react@\"^18.2.0\" from @acme/charts@2.9.4\nnpm error\nnpm error Fix the upstream dependency conflict, or retry\nnpm error this command with --force or --legacy-peer-deps\nnpm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-04-11T02_14_08_112Z-debug.log\n\nlocal install was fine last week and nothing in our package.json changed","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} -{"prompt":"why do we get duplicate rows in the nightly rollup only on the first of the month","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"why do we get duplicate rows in the nightly rollup only on the first of the month","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"security look at the file upload path — internal/media/upload.go plus the nginx config. what can a hostile client do","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"is there any reason this uses a mutex instead of a channel here? genuinely asking, the code works fine","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"is there any reason this uses a mutex instead of a channel here? genuinely asking, the code works fine","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"read the PR from the contractor (#4471) and give me an honest assessment. it's 2800 lines and touches the scheduler","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"api reference page for the new /v2/search endpoint — params, sort syntax, the facet response shape, rate limits, and a couple of curl examples","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"boundary","lang":"en"} +{"prompt":"api reference page for the new /v2/search endpoint — params, sort syntax, the facet response shape, rate limits, and a couple of curl examples","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"summarize this week's incidents into something i can paste in the weekly update. i'll give you the three tickets","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"migration guide for integrators moving off the v1 webhooks — field mapping table, the signature change, and a timeline","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"clean up and also make it faster","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"rename `Widget` to `Panel` throughout the design system package and then update the docs site examples to match","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.55,"slice":"mixed","lang":"en"} -{"prompt":"audit our dependency tree for anything unmaintained or with known CVEs and give me the list ranked by how exposed we actually are, then patch the trivial ones","purpose":"review","secondary":"quickFix","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"propose the schema for multi-tenant row level security in postgres. we currently do it in the app layer with a where clause and i don't trust it","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"we need a story for feature flags at build time on embedded. 200KB of flash left, no network. options?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"outline the steps to get our monorepo CI under 5 minutes","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"clean up and also make it faster","purpose":"refactor","secondary":"backendImpl","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"rename `Widget` to `Panel` throughout the design system package and then update the docs site examples to match","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"audit our dependency tree for anything unmaintained or with known CVEs and give me the list ranked by how exposed we actually are, then patch the trivial ones","purpose":"review","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"propose the schema for multi-tenant row level security in postgres. we currently do it in the app layer with a where clause and i don't trust it","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"we need a story for feature flags at build time on embedded. 200KB of flash left, no network. options?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"outline the steps to get our monorepo CI under 5 minutes","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"implement the delta sync endpoint: client sends a cursor, server returns changed + deleted ids since then, tombstones kept 30 days. also needs to work when the client's cursor is older than the tombstone window","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"build a tiny http server in zig that serves a directory with range requests and etags. no deps","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"put a dead letter queue behind the notification consumer, 5 attempts then park, plus a small admin endpoint to replay a parked message by id","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"keyboard shortcuts overlay, cmd+/ to open, grouped by section, and it should reflect the actual registered commands not a hardcoded list","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"the onboarding carousel doesn't respect reduce motion. also the page dots are too small to tap","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"ajoute un mode sombre au tableau de bord, en respectant les tokens de couleur existants","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"fr"} +{"prompt":"build a tiny http server in zig that serves a directory with range requests and etags. no deps","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"put a dead letter queue behind the notification consumer, 5 attempts then park, plus a small admin endpoint to replay a parked message by id","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"keyboard shortcuts overlay, cmd+/ to open, grouped by section, and it should reflect the actual registered commands not a hardcoded list","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the onboarding carousel doesn't respect reduce motion. also the page dots are too small to tap","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"ajoute un mode sombre au tableau de bord, en respectant les tokens de couleur existants","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"fr"} {"prompt":"regenerate the protobuf stubs, someone committed stale ones","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"the cron is set to 0 3 * * * but ops wants it at 3am pacific not utc, and the container has no TZ set. fix both","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"drop the console.log i left in checkout.tsx","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"core","lang":"en"} +{"prompt":"drop the console.log i left in checkout.tsx","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"decouple the pdf renderer from the web request lifecycle — it's currently reaching into flask's g for the tenant and i want it to take an explicit context object","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"the test helpers have drifted into three overlapping factory modules. merge them, keep every existing test passing untouched","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"flatten the four levels of inheritance under BaseRepository into composition","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"TODO list from the tech debt session, can you work through it:\n\n- [ ] `PaymentGateway` and `PaymentsGateway` both exist, one is a thin wrapper around the other. collapse\n- [ ] the `legacy_` prefix on 11 methods in BillingService means nothing anymore, drop the prefix\n- [ ] move `money.rb` out of app/lib into a proper Money value object under app/values\n- [ ] every controller has its own `current_org` memo, hoist to ApplicationController\n- [ ] `Invoice#total`, `Invoice#total_cents`, `Invoice#grand_total` — pick one, keep cents as the source of truth\n\nnone of this should change what the app does, our specs should stay green as-is","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"profiler says 60% of wall time is in json marshal on the hot path but the payloads are tiny. something's off, help me understand what i'm looking at","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"flatten the four levels of inheritance under BaseRepository into composition","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"TODO list from the tech debt session, can you work through it:\n\n- [ ] `PaymentGateway` and `PaymentsGateway` both exist, one is a thin wrapper around the other. collapse\n- [ ] the `legacy_` prefix on 11 methods in BillingService means nothing anymore, drop the prefix\n- [ ] move `money.rb` out of app/lib into a proper Money value object under app/values\n- [ ] every controller has its own `current_org` memo, hoist to ApplicationController\n- [ ] `Invoice#total`, `Invoice#total_cents`, `Invoice#grand_total` — pick one, keep cents as the source of truth\n\nnone of this should change what the app does, our specs should stay green as-is","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"profiler says 60% of wall time is in json marshal on the hot path but the payloads are tiny. something's off, help me understand what i'm looking at","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"user reports the timer keeps running after they background the app on android 14 but the notification disappears. can't reproduce on my pixel","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"sqlite db is getting corrupted on the field devices, maybe 1 in 50 units after a power cut. WAL is on. what am i doing wrong","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"here's the diff, tell me if the locking is right:\n\n@@ -142,17 +142,29 @@ func (s *Scheduler) Claim(ctx context.Context, workerID string) (*Job, error) {\n-\ts.mu.Lock()\n-\tdefer s.mu.Unlock()\n-\n-\tjob := s.queue.Pop()\n-\tif job == nil {\n-\t\treturn nil, ErrNoJobs\n-\t}\n+\ts.mu.RLock()\n+\tjob := s.queue.Peek()\n+\ts.mu.RUnlock()\n+\n+\tif job == nil {\n+\t\treturn nil, ErrNoJobs\n+\t}\n+\n+\ts.mu.Lock()\n+\tif s.queue.Peek() != job {\n+\t\ts.mu.Unlock()\n+\t\treturn s.Claim(ctx, workerID)\n+\t}\n+\ts.queue.Pop()\n+\ts.mu.Unlock()\n \n \tjob.WorkerID = workerID\n \tjob.ClaimedAt = time.Now()\n-\treturn job, s.store.Update(ctx, job)\n+\tif err := s.store.Update(ctx, job); err != nil {\n+\t\ts.mu.Lock()\n+\t\ts.queue.Push(job)\n+\t\ts.mu.Unlock()\n+\t\treturn nil, err\n+\t}\n+\treturn job, nil\n }\n\nnot asking you to change it, i want to know if the retry path can spin or lose a job","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"pasted-context","lang":"en"} -{"prompt":"does our GDPR delete actually delete everything? trace a user id through every store including the analytics warehouse and the s3 exports","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} +{"prompt":"sqlite db is getting corrupted on the field devices, maybe 1 in 50 units after a power cut. WAL is on. what am i doing wrong","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"here's the diff, tell me if the locking is right:\n\n@@ -142,17 +142,29 @@ func (s *Scheduler) Claim(ctx context.Context, workerID string) (*Job, error) {\n-\ts.mu.Lock()\n-\tdefer s.mu.Unlock()\n-\n-\tjob := s.queue.Pop()\n-\tif job == nil {\n-\t\treturn nil, ErrNoJobs\n-\t}\n+\ts.mu.RLock()\n+\tjob := s.queue.Peek()\n+\ts.mu.RUnlock()\n+\n+\tif job == nil {\n+\t\treturn nil, ErrNoJobs\n+\t}\n+\n+\ts.mu.Lock()\n+\tif s.queue.Peek() != job {\n+\t\ts.mu.Unlock()\n+\t\treturn s.Claim(ctx, workerID)\n+\t}\n+\ts.queue.Pop()\n+\ts.mu.Unlock()\n \n \tjob.WorkerID = workerID\n \tjob.ClaimedAt = time.Now()\n-\treturn job, s.store.Update(ctx, job)\n+\tif err := s.store.Update(ctx, job); err != nil {\n+\t\ts.mu.Lock()\n+\t\ts.queue.Push(job)\n+\t\ts.mu.Unlock()\n+\t\treturn nil, err\n+\t}\n+\treturn job, nil\n }\n\nnot asking you to change it, i want to know if the retry path can spin or lose a job","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"does our GDPR delete actually delete everything? trace a user id through every store including the analytics warehouse and the s3 exports","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"what does the `-tags fastpath` build actually change in this repo","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"deprecation notice for the SDK's `Client.legacyUpload` — what to use instead, when it goes away, and a before/after snippet","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"リリースノートを日本語で書いて、v5.2の変更点は認証周りの修正とパフォーマンス改善","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"ja"} -{"prompt":"our error codes are documented nowhere. go through the codebase, collect every code we return, and produce a reference table with meaning + suggested client action","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"design the permissions model for shared folders — inheritance, explicit deny, link sharing — and then implement the check function once we're happy with the model","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.85,"slice":"mixed","lang":"en"} +{"prompt":"deprecation notice for the SDK's `Client.legacyUpload` — what to use instead, when it goes away, and a before/after snippet","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"リリースノートを日本語で書いて、v5.2の変更点は認証周りの修正とパフォーマンス改善","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"ja"} +{"prompt":"our error codes are documented nowhere. go through the codebase, collect every code we return, and produce a reference table with meaning + suggested client action","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"design the permissions model for shared folders — inheritance, explicit deny, link sharing — and then implement the check function once we're happy with the model","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} {"prompt":"what's the plan for supporting airplane mode in the field app","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"i want to introduce typed errors across our python services. write up the convention and the rollout order so 12 teams can adopt it without a big bang","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.75,"slice":"boundary","lang":"en"} -{"prompt":"add a /metrics endpoint with prometheus counters for request count, latency histogram by route, and queue depth","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"implementa el login con refresh tokens rotativos en el servicio de auth, con revocación por dispositivo","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"es"} +{"prompt":"i want to introduce typed errors across our python services. write up the convention and the rollout order so 12 teams can adopt it without a big bang","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"boundary","lang":"en"} +{"prompt":"add a /metrics endpoint with prometheus counters for request count, latency histogram by route, and queue depth","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"implementa el login con refresh tokens rotativos en el servicio de auth, con revocación por dispositivo","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"es"} {"prompt":"graphql resolver for `organization.usage(period:)` that hits the materialized view, with dataloader batching so we don't n+1 across the org list","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"virtualize the log viewer, it chokes past 10k lines. keep the find-in-page highlight working","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"give the empty chart state something better than 'No data'","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"virtualize the log viewer, it chokes past 10k lines. keep the find-in-page highlight working","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"give the empty chart state something better than 'No data'","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"sidebar should remember collapsed state per workspace","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"set `strictNullChecks` true in tsconfig — just the flag, i'll deal with the fallout separately","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.15,"slice":"boundary","lang":"en"} -{"prompt":"the s3 bucket policy is missing the deny-insecure-transport statement, add it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.25,"slice":"core","lang":"en"} +{"prompt":"set `strictNullChecks` true in tsconfig — just the flag, i'll deal with the fallout separately","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"the s3 bucket policy is missing the deny-insecure-transport statement, add it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"our slack alert says 'CPU is high' with no service name. include $SERVICE and the runbook link in the template","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"hoist the duplicated auth setup out of all 40 test files into a shared fixture","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the Kotlin data layer has repository interfaces that are only implemented once and add nothing. inline them and delete the abstraction","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"port utils/date.js to typescript, same exports, no behavior change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"ci went red on main and the output is useless to me:\n\n$ go test ./... -race -count=1\n==================\nWARNING: DATA RACE\nWrite at 0x00c0004b2118 by goroutine 87:\n github.com/acme/relay/internal/hub.(*Hub).register()\n /src/internal/hub/hub.go:132 +0x64\n github.com/acme/relay/internal/hub.(*Hub).Run.func2()\n /src/internal/hub/hub.go:88 +0x3c\n\nPrevious read at 0x00c0004b2118 by goroutine 12:\n github.com/acme/relay/internal/hub.(*Hub).Broadcast()\n /src/internal/hub/hub.go:201 +0x118\n github.com/acme/relay/internal/api.(*Server).handlePublish()\n /src/internal/api/publish.go:57 +0x244\n\nGoroutine 87 (running) created at:\n github.com/acme/relay/internal/hub.(*Hub).Run()\n /src/internal/hub/hub.go:84 +0xd8\n==================\nFAIL github.com/acme/relay/internal/hub 3.412s\nok github.com/acme/relay/internal/api 1.204s\nFAIL\nmake: *** [Makefile:31: test] Error 1\n\nthis passed on the PR branch with the same commit sha, which makes no sense to me","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"the model's eval accuracy dropped 6 points after we changed nothing but the data loader. same seed, same checkpoint","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"keyboard pushes the input off screen on some androids and not others. no idea","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"look over the new caching layer and tell me where the invalidation can go wrong. i'm not aware of a bug, i just want a second pair of eyes before we roll it out","purpose":"review","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"how does our request id propagate from the edge worker through to the db slow query log","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"worth switching from bcrypt to argon2id for us? we have 900k users and a hot login path","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"the auth module has zero comments and three non-obvious invariants. document them inline where they matter, and add a short doc/auth-invariants.md","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"ticket text for the backlog item we talked about in standup — 'inventory counts drift after partial refunds'. i want repro steps, impact, and acceptance criteria written properly","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"escreve um resumo técnico da arquitetura atual do serviço de pagamentos para o time novo, mais ou menos uma página","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"pt"} +{"prompt":"hoist the duplicated auth setup out of all 40 test files into a shared fixture","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the Kotlin data layer has repository interfaces that are only implemented once and add nothing. inline them and delete the abstraction","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"port utils/date.js to typescript, same exports, no behavior change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"ci went red on main and the output is useless to me:\n\n$ go test ./... -race -count=1\n==================\nWARNING: DATA RACE\nWrite at 0x00c0004b2118 by goroutine 87:\n github.com/acme/relay/internal/hub.(*Hub).register()\n /src/internal/hub/hub.go:132 +0x64\n github.com/acme/relay/internal/hub.(*Hub).Run.func2()\n /src/internal/hub/hub.go:88 +0x3c\n\nPrevious read at 0x00c0004b2118 by goroutine 12:\n github.com/acme/relay/internal/hub.(*Hub).Broadcast()\n /src/internal/hub/hub.go:201 +0x118\n github.com/acme/relay/internal/api.(*Server).handlePublish()\n /src/internal/api/publish.go:57 +0x244\n\nGoroutine 87 (running) created at:\n github.com/acme/relay/internal/hub.(*Hub).Run()\n /src/internal/hub/hub.go:84 +0xd8\n==================\nFAIL github.com/acme/relay/internal/hub 3.412s\nok github.com/acme/relay/internal/api 1.204s\nFAIL\nmake: *** [Makefile:31: test] Error 1\n\nthis passed on the PR branch with the same commit sha, which makes no sense to me","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"the model's eval accuracy dropped 6 points after we changed nothing but the data loader. same seed, same checkpoint","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"keyboard pushes the input off screen on some androids and not others. no idea","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"look over the new caching layer and tell me where the invalidation can go wrong. i'm not aware of a bug, i just want a second pair of eyes before we roll it out","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"how does our request id propagate from the edge worker through to the db slow query log","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"worth switching from bcrypt to argon2id for us? we have 900k users and a hot login path","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"the auth module has zero comments and three non-obvious invariants. document them inline where they matter, and add a short doc/auth-invariants.md","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"ticket text for the backlog item we talked about in standup — 'inventory counts drift after partial refunds'. i want repro steps, impact, and acceptance criteria written properly","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"escreve um resumo técnico da arquitetura atual do serviço de pagamentos para o time novo, mais ou menos uma página","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"pt"} {"prompt":"fix the sort order thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"picking the search relevance work back up. plan the reranking approach and then implement the first pass — we have bm25 from opensearch and 1.2M docs with click logs","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.85,"slice":"mixed","lang":"en"} -{"prompt":"reduce our aws bill. i have the cost explorer breakdown, biggest lines are nat gateway data processing, rds on-demand, and cloudwatch logs ingestion. give me a prioritized plan","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} +{"prompt":"picking the search relevance work back up. plan the reranking approach and then implement the first pass — we have bm25 from opensearch and 1.2M docs with click logs","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"reduce our aws bill. i have the cost explorer breakdown, biggest lines are nat gateway data processing, rds on-demand, and cloudwatch logs ingestion. give me a prioritized plan","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"seed script that builds a realistic dev dataset: 50 orgs, skewed user counts, a year of activity with weekday/weekend shape, deterministic from a seed arg","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"toast notifications, stacked, max 3 visible, swipe to dismiss, and they shouldn't cover the FAB","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"shave the extra pixel off the divider under the nav","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"boundary","lang":"en"} -{"prompt":"extract the rate limit config into one place, it's currently hardcoded in four middleware files with different numbers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.45,"slice":"boundary","lang":"en"} -{"prompt":"double charge happened for 6 customers on the 14th. i need to know how before i tell finance","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"is the way we're doing optimistic UI in the comment box actually safe if the mutation fails mid-flight? no bug reported, just want your read on it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"write up how the deploy pipeline works for the wiki, from merge to prod, including the manual approval gate and who can click it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} +{"prompt":"shave the extra pixel off the divider under the nav","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"extract the rate limit config into one place, it's currently hardcoded in four middleware files with different numbers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"double charge happened for 6 customers on the 14th. i need to know how before i tell finance","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"is the way we're doing optimistic UI in the comment box actually safe if the mutation fails mid-flight? no bug reported, just want your read on it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"write up how the deploy pipeline works for the wiki, from merge to prod, including the manual approval gate and who can click it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"just make it work","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"yesterday's grafana dashboard work — finish wiring the panels","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"- header should stick after 80px of scroll\n- shadow appears only when stuck\n- logo shrinks to the mark only\n- on mobile the whole thing hides on scroll down, shows on scroll up\n\nsvelte, the layout is in src/routes/+layout.svelte","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"button label says \"Sav Changes\"","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"boundary","lang":"en"} -{"prompt":"the modal is 480px wide, design wants 560","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"ok so the input debounce, i think its 300 but feels laggy... anyway can you build the async combobox properly — remote search, loading state in the dropdown, keyboard nav, clears on escape, and it has to work inside our form lib","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"physics tick is decoupled from render now but the camera jitters at 144hz. i think its interpolation but not sure","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"sprite batching for the tilemap renderer, one draw call per atlas, cull offscreen chunks","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"how should save games be versioned so old saves keep loading as we change the entity schema? want the design, several options if there are several","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} +{"prompt":"yesterday's grafana dashboard work — finish wiring the panels","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"- header should stick after 80px of scroll\n- shadow appears only when stuck\n- logo shrinks to the mark only\n- on mobile the whole thing hides on scroll down, shows on scroll up\n\nsvelte, the layout is in src/routes/+layout.svelte","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"button label says \"Sav Changes\"","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"the modal is 480px wide, design wants 560","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"ok so the input debounce, i think its 300 but feels laggy... anyway can you build the async combobox properly — remote search, loading state in the dropdown, keyboard nav, clears on escape, and it has to work inside our form lib","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"physics tick is decoupled from render now but the camera jitters at 144hz. i think its interpolation but not sure","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"sprite batching for the tilemap renderer, one draw call per atlas, cull offscreen chunks","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"how should save games be versioned so old saves keep loading as we change the entity schema? want the design, several options if there are several","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"patch notes for build 0.9.4:\n- fixed enemies pathing through the fence\n- rebalanced crossbow (dmg 24 -> 19, reload 1.1s -> 0.9s)\n- new tutorial popup on first craft\n- known issue: audio cuts on alt-tab\n\nmake it read like the notes players actually enjoy, keep the numbers","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"extract the entity component storage out of World into its own type so i can test archetype queries in isolation. no gameplay change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"explain how the input buffer window works in our fighting game netcode. i'm reading it and can't tell if rollback re-simulates buffered inputs or drops them","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"boundary","lang":"en"} -{"prompt":"the stm32 firmware locks up after ~6 hours of runtime, watchdog doesnt fire. no crash dump, uart just stops","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"i2c driver for the SHT41 on our esp32 board, blocking reads are fine, expose temp+humidity with a status enum for CRC failures","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"the ISR does a printf. thats obviously bad but before i touch it — what's the actual failure mode here and why hasnt it bitten us yet","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"extract the entity component storage out of World into its own type so i can test archetype queries in isolation. no gameplay change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain how the input buffer window works in our fighting game netcode. i'm reading it and can't tell if rollback re-simulates buffered inputs or drops them","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the stm32 firmware locks up after ~6 hours of runtime, watchdog doesnt fire. no crash dump, uart just stops","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"i2c driver for the SHT41 on our esp32 board, blocking reads are fine, expose temp+humidity with a status enum for CRC failures","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the ISR does a printf. thats obviously bad but before i touch it — what's the actual failure mode here and why hasnt it bitten us yet","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} {"prompt":"bump the uart baud in the config header from 115200 to 921600","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"we need OTA updates on the sensor fleet. 40k devices, LTE-M, batteries. i want a design covering A/B partitions, rollback, staged rollout and how we don't brick a field unit","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"the HAL wrapper duplicates the vendor's gpio functions with slightly different names for no reason. delete the wrapper and call the vendor api directly everywhere","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"docs for the register map — every field, bit positions, reset values, and the two write-order requirements that arent obvious from the datasheet","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} +{"prompt":"the HAL wrapper duplicates the vendor's gpio functions with slightly different names for no reason. delete the wrapper and call the vendor api directly everywhere","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"docs for the register map — every field, bit positions, reset values, and the two write-order requirements that arent obvious from the datasheet","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"vite build output is 2.4MB of js and i dont know whats in it. figure out whats big and why the vendor chunk includes the whole icon set","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"add optimistic reordering to the kanban board with dnd-kit, persist on drop, revert visually if the mutation fails","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"increase the toast duration to 6 seconds","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"boundary","lang":"en"} -{"prompt":"things to do on the settings page:\n- move the danger zone to the bottom\n- delete account needs a confirm dialog typing the org name\n- avatar upload should crop square client side\n- the two-column layout collapses badly at 900px\n- billing tab is a stub, wire it to the real data\n\ntake them in order, react + tanstack query","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"hydration mismatch warning on the product page, only in prod, and the price flashes the wrong currency for a frame","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"is there a reason our server components fetch the same user object three times per page? not broken, just seems wasteful and i want to know if next dedupes it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"outline how we'd migrate from CRA to vite without a big-bang PR","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} +{"prompt":"add optimistic reordering to the kanban board with dnd-kit, persist on drop, revert visually if the mutation fails","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"increase the toast duration to 6 seconds","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"things to do on the settings page:\n- move the danger zone to the bottom\n- delete account needs a confirm dialog typing the org name\n- avatar upload should crop square client side\n- the two-column layout collapses badly at 900px\n- billing tab is a stub, wire it to the real data\n\ntake them in order, react + tanstack query","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"hydration mismatch warning on the product page, only in prod, and the price flashes the wrong currency for a frame","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"is there a reason our server components fetch the same user object three times per page? not broken, just seems wasteful and i want to know if next dedupes it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"outline how we'd migrate from CRA to vite without a big-bang PR","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"pull the form validation schemas out of the components into a shared zod module. exact same rules and messages","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"server action for the invite flow — create invite row, send email via resend, rate limit 10/hour per org, and return a typed error the form can render","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"storybook stories for the 14 components in packages/ui that dont have any","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"write the docs page for our theming system — token names, how to override, dark mode, and the css var escape hatch","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"boundary","lang":"en"} -{"prompt":"plan the design system v2 — token structure, component inventory, how we ship breaking changes to 6 consuming apps — and then start with the button + input primitives","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.85,"slice":"mixed","lang":"en"} -{"prompt":"so the thing where the list scrolls to top","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"server action for the invite flow — create invite row, send email via resend, rate limit 10/hour per org, and return a typed error the form can render","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"storybook stories for the 14 components in packages/ui that dont have any","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"write the docs page for our theming system — token names, how to override, dark mode, and the css var escape hatch","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"plan the design system v2 — token structure, component inventory, how we ship breaking changes to 6 consuming apps — and then start with the button + input primitives","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"so the thing where the list scrolls to top","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"what would it take to support undo/redo across the whole editor? currently zero support. i want the architecture, command pattern vs snapshots vs crdt history, and what it costs us","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"rough out the milestones for the web app rewrite. 3 devs, 4 months, must ship incrementally behind a flag, cant freeze feature work","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"we want live cursors in the doc editor. give me the approach — transport, presence expiry, how many peers before it falls apart — before any code","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"implement the image resize proxy: /img/:width/:path, cache in r2, webp when the accept header allows, and 404 fast for paths outside the allowlist","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"websocket server in node that fans out board updates to room members, with presence and a 30s heartbeat. redis pubsub between instances","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"write the leaderboard service — top 100 global, top 100 per region, plus the requesting player's rank. redis sorted sets, needs to handle 2k score submits/sec","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the settings gear icon is 20px, everything else in the toolbar is 16","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"boundary","lang":"en"} -{"prompt":"placeholder text in the search box should say \"Search projects\" not \"Search\"","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"boundary","lang":"en"} -{"prompt":"the aria-label on the close button is missing, add it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"rough out the milestones for the web app rewrite. 3 devs, 4 months, must ship incrementally behind a flag, cant freeze feature work","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"we want live cursors in the doc editor. give me the approach — transport, presence expiry, how many peers before it falls apart — before any code","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"implement the image resize proxy: /img/:width/:path, cache in r2, webp when the accept header allows, and 404 fast for paths outside the allowlist","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"websocket server in node that fans out board updates to room members, with presence and a 30s heartbeat. redis pubsub between instances","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"write the leaderboard service — top 100 global, top 100 per region, plus the requesting player's rank. redis sorted sets, needs to handle 2k score submits/sec","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the settings gear icon is 20px, everything else in the toolbar is 16","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"placeholder text in the search box should say \"Search projects\" not \"Search\"","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"the aria-label on the close button is missing, add it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"our css is 40% unused. purge properly, split the critical path, and stop importing the whole tailwind config in the email templates. no visual diff allowed","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the game's Entity class has update(), render(), serialize() and net sync in one place. separate them, behavior identical, i'll do perf after","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"deduplicate the fetch wrappers in the frontend — there's useApi, apiClient, and a raw fetch helper. one of them","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} +{"prompt":"deduplicate the fetch wrappers in the frontend — there's useApi, apiClient, and a raw fetch helper. one of them","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"browser console on the checkout page, safari 18 only:\n\n[Error] Unhandled Promise Rejection: NotAllowedError: The request is not allowed by the user agent or the platform in the current context.\n\t(anonymous function) (PaymentSheet.tsx:88)\n\tasyncFunctionResume\n\t(anonymous function) (usePaymentRequest.ts:41)\n[Warning] Attempted to load a resource with an invalid URL: about:invalid (checkout, line 0)\n[Log] payment-request availability: – true\n[Log] payment-request show() called from: – \"useEffect\"\n[Error] Unhandled Promise Rejection: AbortError: The operation was aborted.\n\nworks in chrome and firefox. the show() call is in a useEffect after we get the availability result — that might be the issue but i want to be sure before i restructure the component","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} -{"prompt":"frames drop to 40 on the level 3 boss on switch, fine everywhere else. profiler points at the particle system but the counts look the same as level 2","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the device reboots when the radio and the sd card write happen together. brownout maybe? i havent scoped it yet","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"look at our lazy loading setup and tell me whether the below-fold images are actually deferred or if we just added the attribute","purpose":"review","secondary":null,"mixed":false,"difficulty":0.45,"slice":"boundary","lang":"en"} -{"prompt":"why does the useEffect in DataTable run on every render? i want to understand the dependency array before i change it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"assess the risk of our current localStorage token approach vs httpOnly cookies for this app. spa, same domain api, no third party embeds","purpose":"review","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"PR body for the sprite atlas change, mention that artists need to re-export from the tool and link the new naming convention","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"release notes for firmware 2.3.0 in the format the hardware team wants: affected SKUs, changes, upgrade path, and known limitations","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"write up the component api docs for — props, slots, events, and the three controlled/uncontrolled gotchas","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"boundary","lang":"en"} -{"prompt":"prioritize this list and tell me what to cut, i cant ship all of it in 3 weeks:\n\n1. multiplayer spectate mode\n2. controller remapping ui\n3. cloud saves\n4. localization for 5 languages\n5. steam achievements\n6. the crash on level load some people get\n7. accessibility: colorblind palettes, subtitle sizing\n\ni'm one dev, the crash affects maybe 2% of players","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} -{"prompt":"design the input abstraction so keyboard, gamepad and touch all feed the same action map, and rebinding works at runtime","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.75,"slice":"boundary","lang":"en"} +{"prompt":"frames drop to 40 on the level 3 boss on switch, fine everywhere else. profiler points at the particle system but the counts look the same as level 2","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the device reboots when the radio and the sd card write happen together. brownout maybe? i havent scoped it yet","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"look at our lazy loading setup and tell me whether the below-fold images are actually deferred or if we just added the attribute","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"why does the useEffect in DataTable run on every render? i want to understand the dependency array before i change it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"assess the risk of our current localStorage token approach vs httpOnly cookies for this app. spa, same domain api, no third party embeds","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"PR body for the sprite atlas change, mention that artists need to re-export from the tool and link the new naming convention","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"release notes for firmware 2.3.0 in the format the hardware team wants: affected SKUs, changes, upgrade path, and known limitations","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"write up the component api docs for — props, slots, events, and the three controlled/uncontrolled gotchas","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"prioritize this list and tell me what to cut, i cant ship all of it in 3 weeks:\n\n1. multiplayer spectate mode\n2. controller remapping ui\n3. cloud saves\n4. localization for 5 languages\n5. steam achievements\n6. the crash on level load some people get\n7. accessibility: colorblind palettes, subtitle sizing\n\ni'm one dev, the crash affects maybe 2% of players","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"design the input abstraction so keyboard, gamepad and touch all feed the same action map, and rebinding works at runtime","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"how do we test the firmware in CI without hardware. options + what we lose with each","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"add a ring buffer logger to the firmware that survives a reset and can be dumped over uart on boot. fixed 4KB in a noinit section","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"build the replay recording — deterministic input log with a header for build hash and seed, and a player that can seek","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"edge middleware that does geo based routing and sets a cookie for the chosen locale, respecting an explicit user override","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"skeleton -> content transition is jarring, fade it","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.25,"slice":"boundary","lang":"en"} -{"prompt":"the whole onboarding needs a visual pass. it looks like a form from 2015. keep the steps and copy, redo the layout, spacing, progress indicator, and make the illustrations do something","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"build the replay recording — deterministic input log with a header for build hash and seed, and a player that can seek","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"edge middleware that does geo based routing and sets a cookie for the chosen locale, respecting an explicit user override","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"skeleton -> content transition is jarring, fade it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"the whole onboarding needs a visual pass. it looks like a form from 2015. keep the steps and copy, redo the layout, spacing, progress indicator, and make the illustrations do something","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"hud health bar should chunk into segments instead of a smooth fill","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"css var --radius-md is 6px in one theme file and 8 in the other, make them both 8","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"remove the beta badge from the reports nav item","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"boundary","lang":"en"} -{"prompt":"z-index on the dropdown is under the sticky header, bump it above","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"our vue components use both options api and composition api. move everything to composition, script setup, no template changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"split the 2000 line main.c into modules — sensors, radio, power, app logic. same binary behavior, keep the interrupt priorities exactly as they are","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"rename the `tmp2`, `flag`, `doIt` identifiers in physics/solver.cpp to something meaningful. nothing else","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} +{"prompt":"css var --radius-md is 6px in one theme file and 8 in the other, make them both 8","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"remove the beta badge from the reports nav item","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"z-index on the dropdown is under the sticky header, bump it above","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"our vue components use both options api and composition api. move everything to composition, script setup, no template changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"split the 2000 line main.c into modules — sensors, radio, power, app logic. same binary behavior, keep the interrupt priorities exactly as they are","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"rename the `tmp2`, `flag`, `doIt` identifiers in physics/solver.cpp to something meaningful. nothing else","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"test output from the visual regression suite, 6 failures and i dont get the pattern:\n\n ✕ Button/primary/hover (diff 4.12%)\n ✕ Button/primary/focus (diff 4.09%)\n ✕ Card/elevated (diff 0.81%)\n ✓ Card/flat\n ✕ Modal/default (diff 3.94%)\n ✕ Modal/scrollable (diff 3.91%)\n ✓ Tooltip/top\n ✕ Select/open (diff 4.02%)\n\n ● Button/primary/hover\n Expected image to match within 0.5% but was 4.12% different.\n Snapshot: __image_snapshots__/button-primary-hover.png\n Received: __image_snapshots__/__diff_output__/button-primary-hover-diff.png\n\n Chromium 133.0.6943.16 viewport 1280x720 deviceScaleFactor 1\n CI runner: ubuntu-24.04\n\nthe ones failing all have a box-shadow. we didnt touch shadows. the runner image changed last week though","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} -{"prompt":"memory grows every level load and never comes back down. i suspect we're keeping references in the event bus but havent proven it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"le formulaire perd les données saisies quand on change d'onglet, mais seulement sur firefox. je ne comprends pas pourquoi","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"fr"} -{"prompt":"check whether our service worker can serve a stale index.html after a deploy. i think it can but the caching code is dense","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"read through the shader in assets/shaders/water.frag and explain what each pass is doing, i inherited it and want to modify the foam","purpose":"review","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"our DMA setup — is it safe with the cache enabled on this part? i want an analysis not a fix","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"memory grows every level load and never comes back down. i suspect we're keeping references in the event bus but havent proven it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"le formulaire perd les données saisies quand on change d'onglet, mais seulement sur firefox. je ne comprends pas pourquoi","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"fr"} +{"prompt":"check whether our service worker can serve a stale index.html after a deploy. i think it can but the caching code is dense","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"read through the shader in assets/shaders/water.frag and explain what each pass is doing, i inherited it and want to modify the foam","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"our DMA setup — is it safe with the cache enabled on this part? i want an analysis not a fix","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"we need a CONTRIBUTING for the open source repo — how to build the sample app, the DCO requirement, review expectations, and what kinds of PRs we'll decline","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"document the wire protocol between the device and our cloud: framing, message types, ack semantics, and what happens on version mismatch","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"summarize the perf investigation into a two paragraph update for the channel, no jargon, we found the n+1 and the missing index","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.25,"slice":"core","lang":"en"} +{"prompt":"document the wire protocol between the device and our cloud: framing, message types, ack semantics, and what happens on version mismatch","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"summarize the perf investigation into a two paragraph update for the channel, no jargon, we found the n+1 and the missing index","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"make it look like the figma","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"track down the flicker on the graph and then rename the two components involved to match the rest of the folder, they're still called Chart1 and Chart2","purpose":"debugging","secondary":"refactor","mixed":true,"difficulty":0.55,"slice":"mixed","lang":"en"} -{"prompt":"figure out the pause menu regression and write the fix note in the changelog","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.55,"slice":"mixed","lang":"en"} +{"prompt":"track down the flicker on the graph and then rename the two components involved to match the rest of the folder, they're still called Chart1 and Chart2","purpose":"debugging","secondary":"refactor","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"figure out the pause menu regression and write the fix note in the changelog","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} {"prompt":"propose the plugin api for the tool, then implement the loader and one example plugin so we can see if the shape is right","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"what's the sanest way to structure state in this app now that we have 5 slices talking to each other? i want a recommendation, not a refactor yet","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"estimate + sequence the work for SSR on our vue spa. seo is the driver, we have 40 routes, 12 of them behind auth","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"what's the sanest way to structure state in this app now that we have 5 slices talking to each other? i want a recommendation, not a refactor yet","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"estimate + sequence the work for SSR on our vue spa. seo is the driver, we have 40 routes, 12 of them behind auth","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"i need a strategy for keeping our 300 component snapshots useful instead of everyone just running -u","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"endpoint that returns a signed url for the replay upload plus a row in `replays`, and a companion webhook receiver for when the transcode finishes","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"implement the anti-cheat check server side: validate score submissions against the replay length and max theoretical rate, flag not reject","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"low power mode for the tracker: sleep between samples, wake on accelerometer interrupt, and batch uploads every 15 min or 20 samples whichever first","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} +{"prompt":"endpoint that returns a signed url for the replay upload plus a row in `replays`, and a companion webhook receiver for when the transcode finishes","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"implement the anti-cheat check server side: validate score submissions against the replay length and max theoretical rate, flag not reject","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"low power mode for the tracker: sleep between samples, wake on accelerometer interrupt, and batch uploads every 15 min or 20 samples whichever first","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"tooltip should follow the cursor on the chart instead of snapping to the nearest point","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"gamepad navigation for all the menus, including focus wrap and the sound on move","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"hide the debug overlay in production builds","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.15,"slice":"core","lang":"en"} +{"prompt":"hide the debug overlay in production builds","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"the polling interval on the status page is 1s, thats hammering us. 10s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"we forgot `rel=\"noopener\"` on the external links in the footer","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"the two nearly identical Modal and Dialog components need to become one. keep both export names working for now so nothing breaks","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"move the inline styles in the marketing pages into the tailwind classes we use everywhere else, pixel identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"our C code passes structs by value all over the hot path. change to const pointers, same semantics","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"from the QA channel this morning:\n\n> repro: 1) open the app on iPad 2) rotate to landscape 3) tap any list row 4) rotate back to portrait\n> result: detail view is blank, back button does nothing, have to force quit\n> happens 10/10 on iPad Air 5 (18.4), 0/10 on iPhone, 0/10 on iPad simulator\n> also: if you rotate again it comes back, sometimes\n\nno crash log because it doesnt crash. NavigationSplitView. i've read the docs three times","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"pasted-context","lang":"en"} -{"prompt":"cpu pegs at 100% in the render loop after about 20 minutes idle on the title screen. nothing should be running","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"form submits twice when the user hits enter in the last field but only in the embedded iframe version","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"is the throttling in our scroll handler correct or does it drop the last event? i want to know before i change anything, the current behavior might be intentional","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"go through packages/auth-client and tell me what a malicious page in another tab could do with our postMessage handler","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"do we need the polyfills in the entry bundle still? which browsers actually require them given our analytics","purpose":"review","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"the storybook docs pages have no prose, just the auto generated props table. write usage guidance for the form components — when to use which, accessibility notes, do/dont","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"boundary","lang":"en"} +{"prompt":"the two nearly identical Modal and Dialog components need to become one. keep both export names working for now so nothing breaks","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"move the inline styles in the marketing pages into the tailwind classes we use everywhere else, pixel identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"our C code passes structs by value all over the hot path. change to const pointers, same semantics","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"from the QA channel this morning:\n\n> repro: 1) open the app on iPad 2) rotate to landscape 3) tap any list row 4) rotate back to portrait\n> result: detail view is blank, back button does nothing, have to force quit\n> happens 10/10 on iPad Air 5 (18.4), 0/10 on iPhone, 0/10 on iPad simulator\n> also: if you rotate again it comes back, sometimes\n\nno crash log because it doesnt crash. NavigationSplitView. i've read the docs three times","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"cpu pegs at 100% in the render loop after about 20 minutes idle on the title screen. nothing should be running","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"form submits twice when the user hits enter in the last field but only in the embedded iframe version","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"is the throttling in our scroll handler correct or does it drop the last event? i want to know before i change anything, the current behavior might be intentional","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"go through packages/auth-client and tell me what a malicious page in another tab could do with our postMessage handler","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"do we need the polyfills in the entry bundle still? which browsers actually require them given our analytics","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the storybook docs pages have no prose, just the auto generated props table. write usage guidance for the form components — when to use which, accessibility notes, do/dont","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"commit message, i touched the renderer, the asset pipeline and one shader. conventional commits style","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"escribe el README del paquete de componentes: instalación, uso básico, tematización y cómo contribuir","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} -{"prompt":"next","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"lay out the plan for shipping our first mobile build of the web app — capacitor vs react native vs pwa — and be opinionated. we have 2 web devs and no mobile experience","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"we keep breaking the embed on customer sites. i want a compatibility plan: what we version, how we test against old versions, and a deprecation policy","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} +{"prompt":"we keep breaking the embed on customer sites. i want a compatibility plan: what we version, how we test against old versions, and a deprecation policy","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"roadmap for getting lighthouse above 90 on the three main pages","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"add server side pagination + sorting to the /api/logs endpoint, and a cheap total count that's allowed to be approximate over 10k","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"write the export worker: takes a report id, renders to pdf with playwright, uploads, emails the link, marks the row done. must be safe to retry","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"implement per-tenant api keys with prefix + hash storage, last used timestamp, and a rotate endpoint that keeps the old key valid 24h","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"settings page needs a two-pane layout on desktop, stacked on mobile, with the nav highlighting the visible section as you scroll","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"the number inputs should allow arrow key increment and reject non numeric paste","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"add a copy button to the code blocks in the docs","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"the og:image meta points at a deleted file, point it at /og/default-v2.png","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"core","lang":"en"} +{"prompt":"add server side pagination + sorting to the /api/logs endpoint, and a cheap total count that's allowed to be approximate over 10k","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"write the export worker: takes a report id, renders to pdf with playwright, uploads, emails the link, marks the row done. must be safe to retry","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"implement per-tenant api keys with prefix + hash storage, last used timestamp, and a rotate endpoint that keeps the old key valid 24h","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"settings page needs a two-pane layout on desktop, stacked on mobile, with the nav highlighting the visible section as you scroll","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the number inputs should allow arrow key increment and reject non numeric paste","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"add a copy button to the code blocks in the docs","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the og:image meta points at a deleted file, point it at /og/default-v2.png","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"our robots.txt is blocking /docs, it shouldnt","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"set `sameSite: 'lax'` on the session cookie, its currently unset","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.15,"slice":"core","lang":"en"} -{"prompt":"the api layer has both camelCase and snake_case leaking through depending on the endpoint. normalize at the boundary once, everything internal camel","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"unnest the callback pyramid in scripts/deploy.js, it's 7 levels deep","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the enum for game states is duplicated in the client and the server as string literals. share one definition","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"gdb on the crash, this is all i have:\n\nProgram received signal SIGSEGV, Segmentation fault.\n0x0000555555571a2c in ChunkMesher::emit_quad (this=0x0, v0=..., v1=..., v2=..., v3=...) at src/render/mesher.cpp:214\n214\t\tvertices[count++] = v0;\n(gdb) bt\n#0 0x0000555555571a2c in ChunkMesher::emit_quad (this=0x0, ...) at src/render/mesher.cpp:214\n#1 0x0000555555572118 in ChunkMesher::mesh_face (this=0x0, f=NORTH) at src/render/mesher.cpp:301\n#2 0x00005555555723f0 in World::rebuild_dirty_chunks (this=0x5555559a1200) at src/world/world.cpp:512\n#3 0x0000555555560884 in Game::tick (this=0x7fffffffdc40, dt=0.0166667) at src/game.cpp:188\n#4 0x000055555555f210 in main (argc=1, argv=0x7fffffffde48) at src/main.cpp:64\n(gdb) p this\n$1 = (ChunkMesher *) 0x0\n(gdb) f 2\n#2 ... rebuild_dirty_chunks ...\n(gdb) p chunk->mesher\n$2 = (ChunkMesher *) 0x0\n\nmesher is created in Chunk::activate. only crashes when you fly fast across the world","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"pasted-context","lang":"en"} -{"prompt":"the timer drifts about 3 seconds an hour on the device. rtc or my software timer, no idea which","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"set `sameSite: 'lax'` on the session cookie, its currently unset","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"the api layer has both camelCase and snake_case leaking through depending on the endpoint. normalize at the boundary once, everything internal camel","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"unnest the callback pyramid in scripts/deploy.js, it's 7 levels deep","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the enum for game states is duplicated in the client and the server as string literals. share one definition","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"gdb on the crash, this is all i have:\n\nProgram received signal SIGSEGV, Segmentation fault.\n0x0000555555571a2c in ChunkMesher::emit_quad (this=0x0, v0=..., v1=..., v2=..., v3=...) at src/render/mesher.cpp:214\n214\t\tvertices[count++] = v0;\n(gdb) bt\n#0 0x0000555555571a2c in ChunkMesher::emit_quad (this=0x0, ...) at src/render/mesher.cpp:214\n#1 0x0000555555572118 in ChunkMesher::mesh_face (this=0x0, f=NORTH) at src/render/mesher.cpp:301\n#2 0x00005555555723f0 in World::rebuild_dirty_chunks (this=0x5555559a1200) at src/world/world.cpp:512\n#3 0x0000555555560884 in Game::tick (this=0x7fffffffdc40, dt=0.0166667) at src/game.cpp:188\n#4 0x000055555555f210 in main (argc=1, argv=0x7fffffffde48) at src/main.cpp:64\n(gdb) p this\n$1 = (ChunkMesher *) 0x0\n(gdb) f 2\n#2 ... rebuild_dirty_chunks ...\n(gdb) p chunk->mesher\n$2 = (ChunkMesher *) 0x0\n\nmesher is created in Chunk::activate. only crashes when you fly fast across the world","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"the timer drifts about 3 seconds an hour on the device. rtc or my software timer, no idea which","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"half our users get logged out randomly. sessions are 30 days, no pattern by browser. i'm stuck","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain the difference in behavior between our two rendering paths (canvas and svg) for the same chart spec, and which one handles 50k points better","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"look over the migration i wrote before i run it on prod. 2M row table, adding two columns and an index","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"why is this using a WeakMap here","purpose":"review","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"write the tutorial doc: from zero to a running local dev env with seeded data, on mac and linux, with the three things that always go wrong called out","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"changelog for the component library, we went 3.x -> 4.0 with breaking prop renames. include the codemod instructions","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"boundary","lang":"en"} -{"prompt":"one paragraph for the app store update text, we improved sync speed and fixed the widget","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.15,"slice":"core","lang":"en"} -{"prompt":"just clean it up idk","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"plan the sharding of our game servers by region and then write the matchmaker's server selection logic","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.85,"slice":"mixed","lang":"en"} +{"prompt":"explain the difference in behavior between our two rendering paths (canvas and svg) for the same chart spec, and which one handles 50k points better","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"look over the migration i wrote before i run it on prod. 2M row table, adding two columns and an index","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"why is this using a WeakMap here","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"write the tutorial doc: from zero to a running local dev env with seeded data, on mac and linux, with the three things that always go wrong called out","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"changelog for the component library, we went 3.x -> 4.0 with breaking prop renames. include the codemod instructions","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"one paragraph for the app store update text, we improved sync speed and fixed the widget","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"just clean it up idk","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"plan the sharding of our game servers by region and then write the matchmaker's server selection logic","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} {"prompt":"review the firmware pr from the contractor and document the parts that are undocumented while you're reading it","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"extract the shared validation into a package and update the docs that reference the old import path","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.55,"slice":"mixed","lang":"en"} -{"prompt":"sequence the work to get our web build under 500KB and then do the first item on the list","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"figure out what's up with the double render in the editor, then add a note in the architecture doc about the render lifecycle since nobody understands it","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"get the dark theme colors right — audit what we have against the contrast requirements and then fix the failures","purpose":"review","secondary":"frontendImpl","mixed":true,"difficulty":0.55,"slice":"mixed","lang":"en"} +{"prompt":"extract the shared validation into a package and update the docs that reference the old import path","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"sequence the work to get our web build under 500KB and then do the first item on the list","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"figure out what's up with the double render in the editor, then add a note in the architecture doc about the render lifecycle since nobody understands it","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"get the dark theme colors right — audit what we have against the contrast requirements and then fix the failures","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} {"prompt":"wire the new /v2/session endpoint into the client and update the api reference to match","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} -{"prompt":"how do we handle the daylight savings edge in the scheduler? design it properly, i've patched around it twice already","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.75,"slice":"boundary","lang":"en"} -{"prompt":"structure the monorepo so the game, the tools and the shared math library dont circularly depend. propose the layout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"sse endpoint for build logs, resumable with Last-Event-ID, and it needs to work through our nginx without buffering","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"background job that recomputes the search index for a project when any of its docs change, coalescing rapid edits into one rebuild per 30s","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"how do we handle the daylight savings edge in the scheduler? design it properly, i've patched around it twice already","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"structure the monorepo so the game, the tools and the shared math library dont circularly depend. propose the layout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"sse endpoint for build logs, resumable with Last-Event-ID, and it needs to work through our nginx without buffering","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"background job that recomputes the search index for a project when any of its docs change, coalescing rapid edits into one rebuild per 30s","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the achievements screen: grid of cards, locked ones greyed with a silhouette, progress bar on partial ones, and a filter for unlocked only","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the sidebar scrollbar is always visible on windows, make it overlay style like mac","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"the sidebar scrollbar is always visible on windows, make it overlay style like mac","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"gzip is on but brotli isnt, enable it in the cdn config","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"the retry limit for the asset download is 1, make it 3 with backoff","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.25,"slice":"core","lang":"en"} -{"prompt":"pull the magic numbers in the tuning constants out into a data file the designers can edit without a rebuild. same values to start","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"unify the three logging approaches in the firmware — printf, a macro, and a custom uart write. one macro, compile time level","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"lint says 90 warnings about unused vars and shadowing. clean them all up without changing behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"the retry limit for the asset download is 1, make it 3 with backoff","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"pull the magic numbers in the tuning constants out into a data file the designers can edit without a rebuild. same values to start","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"unify the three logging approaches in the firmware — printf, a macro, and a custom uart write. one macro, compile time level","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"lint says 90 warnings about unused vars and shadowing. clean them all up without changing behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"webpack -> vite migration left this and i cant read it:\n\n[vite]: Rollup failed to resolve import \"~@acme/tokens/scss/index.scss\" from \"/src/styles/app.scss\".\nThis is most likely unintended because it can break your application at runtime.\nIf you do want to externalize this module explicitly add it to\n`build.rollupOptions.external`\n\n file: /src/styles/app.scss\n error during build:\n Error: [vite]: Rollup failed to resolve import ...\n at viteWarn (file:///node_modules/vite/dist/node/chunks/dep-C6uTJdX2.js:65613:17)\n at onwarn (file:///node_modules/@vitejs/plugin-vue/dist/index.mjs:1412:9)\n at onRollupWarning (...)\n\nalso 40 more of these for every ~@ import. the old webpack config had a resolve.alias with a tilde thing. whats the vite equivalent and is it just the alias or is sass involved too","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} -{"prompt":"the collision response makes objects sink into the floor at high velocity. i know its probably substepping but i want to actually diagnose it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"assess whether our current asset pipeline can handle 4x the content. read the build scripts, tell me where it falls over","purpose":"review","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"walk me through the boot sequence in the bootloader, especially who validates the signature and when","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"write the hardware bring-up guide for the new revision: jumper settings, flashing steps, and how to tell if the power rail is bad","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"our internal wiki page for the frontend build is 2 years stale. rewrite it against what the repo actually does now","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"make the empty state nicer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"wrap up the thing from this morning","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"check the pr","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"there's a rounding thing in the totals somewhere, chase it down","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"our tween library is 40KB for two easing functions. write the two functions and drop the dep","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"the toolbar buttons need tooltips with the keyboard shortcut shown on the right","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} +{"prompt":"the collision response makes objects sink into the floor at high velocity. i know its probably substepping but i want to actually diagnose it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"assess whether our current asset pipeline can handle 4x the content. read the build scripts, tell me where it falls over","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"walk me through the boot sequence in the bootloader, especially who validates the signature and when","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"write the hardware bring-up guide for the new revision: jumper settings, flashing steps, and how to tell if the power rail is bad","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"our internal wiki page for the frontend build is 2 years stale. rewrite it against what the repo actually does now","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"make the empty state nicer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"check the pr","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"there's a rounding thing in the totals somewhere, chase it down","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"our tween library is 40KB for two easing functions. write the two functions and drop the dep","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"the toolbar buttons need tooltips with the keyboard shortcut shown on the right","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"implement the presence heartbeat on the server side, mark a user offline after 45s of silence and broadcast the change","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"the version string in the about dialog is hardcoded 1.2.0, read it from package.json","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"give me the migration plan for our custom scene format to gltf, including how we keep old scenes loadable during the transition","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain how our texture streaming decides what to evict, and whether the priority accounts for the camera","purpose":"review","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} +{"prompt":"explain how our texture streaming decides what to evict, and whether the priority accounts for the camera","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"draft the deprecation announcement for the v1 embed script, 6 month timeline, with a section for the 12 largest customers","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"we need to get the notification fan-out off the primary postgres. write me an RFC comparing SNS+SQS, a self-hosted NATS cluster, and just using pg_notify better — include a rollout order and where the kill switches go","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"design the multi-tenant audit log schema for us — 7 year retention, queryable by actor and by resource, tenants can export their own slice. i only want the design doc right now, don't touch the migrations","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"we need to get the notification fan-out off the primary postgres. write me an RFC comparing SNS+SQS, a self-hosted NATS cluster, and just using pg_notify better — include a rollout order and where the kill switches go","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"design the multi-tenant audit log schema for us — 7 year retention, queryable by actor and by resource, tenants can export their own slice. i only want the design doc right now, don't touch the migrations","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"plan and then start building the offline write queue for the android client. ordering guarantees matter, we can't have a note edit land before its create","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"add a /v2/exports endpoint to the go service that streams a zipped csv per tenant — chunked writes, never buffer the whole archive in memory, and it has to survive a 20 minute download","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"add a /v2/exports endpoint to the go service that streams a zipped csv per tenant — chunked writes, never buffer the whole archive in memory, and it has to survive a 20 minute download","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"idempotency keys on POST /charges please. 24h window, keys in redis, replay returns the original response body and status verbatim","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"from the notion doc, please build it:\n\n- POST /v1/holds { seat_ids: [uuid], hold_ttl_seconds: int (default 600, max 1800) }\n- returns 201 { hold_id, expires_at } or 409 with the conflicting seat ids\n- holds expire without a cron — lazy expiry on read is fine\n- a second hold on the same seats from the SAME session extends instead of conflicting\n- DELETE /v1/holds/:id releases early, must be idempotent\n- all of it behind the seat_holds flag\n\npostgres + sqlc, copy the repo layer patterns from internal/reserve","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"from the notion doc, please build it:\n\n- POST /v1/holds { seat_ids: [uuid], hold_ttl_seconds: int (default 600, max 1800) }\n- returns 201 { hold_id, expires_at } or 409 with the conflicting seat ids\n- holds expire without a cron — lazy expiry on read is fine\n- a second hold on the same seats from the SAME session extends instead of conflicting\n- DELETE /v1/holds/:id releases early, must be idempotent\n- all of it behind the seat_holds flag\n\npostgres + sqlc, copy the repo layer patterns from internal/reserve","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"build the settings screen in SwiftUI — sections for account, notifications, appearance. use Form, match the row styling in ProfileView, and the appearance section needs a live preview tile","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"dark mode toggle for the docs site","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"swap the spinner on the feed for the shimmer placeholder we already use in Notifications","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"bump ruff to 0.6.9 in pyproject and clear whatever new lint errors it throws","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"dark mode toggle for the docs site","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"swap the spinner on the feed for the shimmer placeholder we already use in Notifications","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"bump ruff to 0.6.9 in pyproject and clear whatever new lint errors it throws","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"typo: 'unathorized' in auth/middleware.go","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"one line thing — the retry cap in worker.rs should be 5 not 3. double check nothing else reads that const before you change it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"PaymentsCoordinator is 1400 lines and i can't test any of it. split the state machine out from the networking, identical behavior, the existing snapshot tests should still pass untouched","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the retry + backoff logic is copy pasted across all six of our http clients. pull it into one middleware and have them all use it","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"rename the `usr` param to `user` in handlers/*.go, it's like 40 call sites but purely mechanical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"one line thing — the retry cap in worker.rs should be 5 not 3. double check nothing else reads that const before you change it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"PaymentsCoordinator is 1400 lines and i can't test any of it. split the state machine out from the networking, identical behavior, the existing snapshot tests should still pass untouched","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the retry + backoff logic is copy pasted across all six of our http clients. pull it into one middleware and have them all use it","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"rename the `usr` param to `user` in handlers/*.go, it's like 40 call sites but purely mechanical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"our nightly ETL hangs about 40 minutes in. no error, no cpu, no log lines, just sits there until the k8s deadline kills it. maybe 1 run in 4. figure out what's going on","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"got this on the payments worker an hour ago, third time this week\n\npanic: runtime error: invalid memory address or nil pointer dereference\n[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x8f2a41]\n\ngoroutine 4417 [running]:\ngithub.com/acme/ledger/internal/settle.(*Batcher).flush(0xc000a3e000, {0x1043a20, 0xc0004b2340})\n\t/app/internal/settle/batcher.go:212 +0x1c1\ngithub.com/acme/ledger/internal/settle.(*Batcher).run(0xc000a3e000)\n\t/app/internal/settle/batcher.go:141 +0xf5\ncreated by github.com/acme/ledger/internal/settle.NewBatcher in goroutine 1\n\t/app/internal/settle/batcher.go:88 +0x145\n\nbatcher.go hasn't been touched since march. i'm lost","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} {"prompt":"why is my build 4x slower since friday","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"walk me through the refill math in internal/ratelimit, specifically why there's a second clamp after the burst add","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"if i drop the FOR UPDATE in reserveSeat does that open a race, or does the unique constraint already save us? just want your read, don't change anything yet","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"if i drop the FOR UPDATE in reserveSeat does that open a race, or does the unique constraint already save us? just want your read, don't change anything yet","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"go through the terraform in infra/ and tell me if anything lets a dev-role principal touch prod state or assume the deploy role","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"release notes for 3.4.0 off the commits since 3.3.2, split into user-facing and internal, and call out the deprecation","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"the openapi spec still says amount is an integer in cents, we switched it to a decimal string last month. get the spec and the endpoint descriptions current","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"write the cutover runbook for the shard migration and also add the pre-flight check script it references","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"release notes for 3.4.0 off the commits since 3.3.2, split into user-facing and internal, and call out the deprecation","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the openapi spec still says amount is an integer in cents, we switched it to a decimal string last month. get the spec and the endpoint descriptions current","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"write the cutover runbook for the shard migration and also add the pre-flight check script it references","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"we want the feature store off pandas-in-airflow and onto something real. i have three engineers and one quarter. give me a roadmap with what we cut","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"thinking out loud here — every service reinvents pagination, some cursor some offset, the mobile team is furious. i want one story for pagination across all of them but i don't know if we version the APIs or add a parallel param set or what. help me think it through and land on a strategy","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"dumping the migration TODOs from our doc, turn it into a sequenced plan with dependencies called out, i suspect half of these can't happen in the order listed:\n\n- move sessions table to its own database\n- kill the legacy /api/session endpoint (mobile 4.2 still calls it, 11% of DAU)\n- switch session ids from int to uuidv7\n- stop writing session rows on anonymous traffic\n- add the read replica for analytics\n- delete the sessions_archive_2019 table (nobody knows if finance reads it)\n- rotate the signing key, needs dual-accept window\n- redis session cache TTL down from 7d to 24h","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Room migration for the offline notes table — add synced_at, backfill it from updated_at, and don't destructive-migrate, people have unsynced data","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"duckdb loader for the parquet exports. partition by dt, skip anything already in the manifest table, and it should be safe to run twice","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the api docs already describe GET /v1/segments in full detail but the endpoint doesn't exist. make the code match the docs","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"compose bottom sheet for the filter chips, sticky Apply button at the bottom, material3 tokens only, and it should keep its selection across rotation","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"make the chart legend wrap","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"thinking out loud here — every service reinvents pagination, some cursor some offset, the mobile team is furious. i want one story for pagination across all of them but i don't know if we version the APIs or add a parallel param set or what. help me think it through and land on a strategy","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"dumping the migration TODOs from our doc, turn it into a sequenced plan with dependencies called out, i suspect half of these can't happen in the order listed:\n\n- move sessions table to its own database\n- kill the legacy /api/session endpoint (mobile 4.2 still calls it, 11% of DAU)\n- switch session ids from int to uuidv7\n- stop writing session rows on anonymous traffic\n- add the read replica for analytics\n- delete the sessions_archive_2019 table (nobody knows if finance reads it)\n- rotate the signing key, needs dual-accept window\n- redis session cache TTL down from 7d to 24h","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Room migration for the offline notes table — add synced_at, backfill it from updated_at, and don't destructive-migrate, people have unsynced data","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"duckdb loader for the parquet exports. partition by dt, skip anything already in the manifest table, and it should be safe to run twice","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the api docs already describe GET /v1/segments in full detail but the endpoint doesn't exist. make the code match the docs","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"compose bottom sheet for the filter chips, sticky Apply button at the bottom, material3 tokens only, and it should keep its selection across rotation","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"make the chart legend wrap","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"priya left this in #design-review, can you do it:\n\n\"ok looked at the build on my 13 mini. the header eats like a third of the screen — the avatar and the greeting can be one row not two. the segmented control is fine but the selected pill has no contrast in dark mode, it's basically invisible. the card shadows are way too heavy, we said 4% not 20%. and the pull to refresh spinner appears BEHIND the header which looks broken. everything else 👍\"","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} {"prompt":"gradle targetSdk to 35","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"the s3 lifecycle rule should expire at 90 days not 30, it's in infra/storage somewhere","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"alembic's env.py has compare_type=False, flip it on and regenerate nothing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"the feature engineering lives in notebooks/features.ipynb and gets copy-pasted into prod by hand. lift it into a real module, same numbers out, add tests that pin the current output","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"FeedViewModel does retrofit calls directly in four places. push all of it behind FeedRepository like the other screens do","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"we have two parse_timestamp helpers that disagree on trailing Z. collapse them into one, keep the utils/time.py behavior since more callers depend on it","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"duplicate rows show up in the daily rollup but only when a backfill window overlaps a live run. the merge key looks right to me. i don't get it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"alembic's env.py has compare_type=False, flip it on and regenerate nothing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"the feature engineering lives in notebooks/features.ipynb and gets copy-pasted into prod by hand. lift it into a real module, same numbers out, add tests that pin the current output","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"FeedViewModel does retrofit calls directly in four places. push all of it behind FeedRepository like the other screens do","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"we have two parse_timestamp helpers that disagree on trailing Z. collapse them into one, keep the utils/time.py behavior since more callers depend on it","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"duplicate rows show up in the daily rollup but only when a backfill window overlaps a live run. the merge key looks right to me. i don't get it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"ANR in FeedFragment after rotation, ~60% of the reports are pixels on android 14. logcat isn't telling me much","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"this passes locally every time:\n\n=================================== FAILURES ===================================\n_______________________ test_rollup_dedupes_late_events ________________________\n\n def test_rollup_dedupes_late_events():\n run_rollup(day=date(2026, 3, 14))\n> assert warehouse.count(\"rollup_daily\", day=\"2026-03-14\") == 1\nE assert 2 == 1\nE + where 2 = count('rollup_daily', day='2026-03-14')\n\ntests/test_rollup.py:118: AssertionError\n----------------------------- Captured log call ------------------------------\nWARNING rollup.merge:merge.py:64 late event 4a91 arrived after watermark 2026-03-14T23:59:59Z\nINFO rollup.merge:merge.py:71 upsert conflict target (day, tenant) -> 1 row\nINFO rollup.merge:merge.py:71 upsert conflict target (day, tenant) -> 1 row\n=========== 1 failed, 214 passed, 3 skipped in 41.22s ===========","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} -{"prompt":"after we added the partial index the planner switched to a seq scan on the orders join. expected or did we break something","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"this passes locally every time:\n\n=================================== FAILURES ===================================\n_______________________ test_rollup_dedupes_late_events ________________________\n\n def test_rollup_dedupes_late_events():\n run_rollup(day=date(2026, 3, 14))\n> assert warehouse.count(\"rollup_daily\", day=\"2026-03-14\") == 1\nE assert 2 == 1\nE + where 2 = count('rollup_daily', day='2026-03-14')\n\ntests/test_rollup.py:118: AssertionError\n----------------------------- Captured log call ------------------------------\nWARNING rollup.merge:merge.py:64 late event 4a91 arrived after watermark 2026-03-14T23:59:59Z\nINFO rollup.merge:merge.py:71 upsert conflict target (day, tenant) -> 1 row\nINFO rollup.merge:merge.py:71 upsert conflict target (day, tenant) -> 1 row\n=========== 1 failed, 214 passed, 3 skipped in 41.22s ===========","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"after we added the partial index the planner switched to a seq scan on the orders join. expected or did we break something","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"explain what our celery beat schedule actually does, the crontab entries are impossible to read and i don't trust the comments","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"帮我看下这个 PR 里的 SQL migration 有没有锁表风险，表大概 2 亿行。只要分析，先别改代码","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"zh"} +{"prompt":"帮我看下这个 PR 里的 SQL migration 有没有锁表风险，表大概 2 亿行。只要分析，先别改代码","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} {"prompt":"README for the dbt project — how to run it locally, how to add a model, the naming conventions we settled on, and the bit about not committing target/","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"pr description for this branch. lead with the breaking change to the webhook payload shape so reviewers can't miss it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"write up the postmortem for last night's outage and then land the missing index that caused it","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} -{"prompt":"picking the feature store thing back up","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"architecture for the on-device inference path: we want the tiny classifier to run in a coreml model but fall back to the server when the device is old. where does the decision live, how do we keep both versions in sync, what do we log","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"write up the postmortem for last night's outage and then land the missing index that caused it","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"architecture for the on-device inference path: we want the tiny classifier to run in a coreml model but fall back to the server when the device is old. where does the decision live, how do we keep both versions in sync, what do we log","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"milestones for killing our custom feature flag service and moving to openfeature. weekly chunks, each one revertible on its own","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"figure out an approach for the firmware OTA rollout — staged by device cohort, must survive a power cut mid-flash, and we only have 128k for the bootloader. write it up before any code","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"boundary","lang":"en"} -{"prompt":"rust: parse the .ndjson event feed, tolerate trailing garbage on a line, emit a counter for malformed records instead of bailing out","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"nightly celery job that reconciles stripe invoices against our ledger, idempotent, writes discrepancies to a table instead of alerting","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"postgres migration: composite index on events (tenant_id, created_at desc), concurrently, table is 800M rows and we can't take a lock","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"skeleton loading state for the dashboard cards. shimmer, but bail to a static grey if prefers-reduced-motion","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"animate the tab bar selection with matchedGeometryEffect, and the icon should scale a touch on tap","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"sidebar collapses at 1024 but tablet users get a mangled layout around 900. redo the breakpoints, and the nav should stay reachable at every width","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"figure out an approach for the firmware OTA rollout — staged by device cohort, must survive a power cut mid-flash, and we only have 128k for the bootloader. write it up before any code","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"rust: parse the .ndjson event feed, tolerate trailing garbage on a line, emit a counter for malformed records instead of bailing out","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"nightly celery job that reconciles stripe invoices against our ledger, idempotent, writes discrepancies to a table instead of alerting","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"postgres migration: composite index on events (tenant_id, created_at desc), concurrently, table is 800M rows and we can't take a lock","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"skeleton loading state for the dashboard cards. shimmer, but bail to a static grey if prefers-reduced-motion","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"animate the tab bar selection with matchedGeometryEffect, and the icon should scale a touch on tap","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"sidebar collapses at 1024 but tablet users get a mangled layout around 900. redo the breakpoints, and the nav should stay reachable at every width","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} {"prompt":"docker healthcheck interval to 10s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"in der nginx.conf client_max_body_size auf 50m setzen, uploads schlagen bei 12mb fehl","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"de"} -{"prompt":"new_pricing_page on in staging only, prod stays off","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"new_pricing_page on in staging only, prod stays off","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"three copies of formatCurrency — web, mobile-web, admin. one implementation, one package, delete the others","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"convert the callback-style s3 helpers in lib/storage to async/await. keep the exported signatures compatible where you can and note anywhere you couldn't","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"SearchController knows about the network layer, the cache, analytics AND the keyboard. decouple it — protocols at the boundaries, no behavior drift, the ui should look identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"convert the callback-style s3 helpers in lib/storage to async/await. keep the exported signatures compatible where you can and note anywhere you couldn't","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"SearchController knows about the network layer, the cache, analytics AND the keyboard. decouple it — protocols at the boundaries, no behavior drift, the ui should look identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"the websocket gateway grows about 200mb an hour and gets oomkilled overnight. node 22. heap snapshots look boring, nothing obviously retained","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"app freezes on launch, iOS 17 only, 18 is fine. main thread checker yells something about CoreData and then nothing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"sentry issue, 340 events in 2h, all from the same customer:\n\nTypeError: Cannot read properties of undefined (reading 'currency')\n at formatTotal (checkout/summary.tsx:88:31)\n at CartSummary (checkout/summary.tsx:142:18)\n at renderWithHooks (react-dom.production.min.js:1:1)\n\nbreadcrumbs\n navigation /cart -> /checkout\n xhr GET /api/cart 200 (412ms)\n console warn: cart line 9f21 has no price snapshot\n xhr POST /api/checkout/quote 500 (88ms)\n ui.click button[data-test=place-order]\n\ntags: release 2026.7.3, browser chrome 141, locale de-CH\n\nour cart response is supposed to always have currency. what's actually happening","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"sentry issue, 340 events in 2h, all from the same customer:\n\nTypeError: Cannot read properties of undefined (reading 'currency')\n at formatTotal (checkout/summary.tsx:88:31)\n at CartSummary (checkout/summary.tsx:142:18)\n at renderWithHooks (react-dom.production.min.js:1:1)\n\nbreadcrumbs\n navigation /cart -> /checkout\n xhr GET /api/cart 200 (412ms)\n console warn: cart line 9f21 has no price snapshot\n xhr POST /api/checkout/quote 500 (88ms)\n ui.click button[data-test=place-order]\n\ntags: release 2026.7.3, browser chrome 141, locale de-CH\n\nour cart response is supposed to always have currency. what's actually happening","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} {"prompt":"is our jwt refresh flow safe if someone lifts a refresh token out of localStorage? rotation is on but i want a second pair of eyes on the reuse detection","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"what does this regex do","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"bull vs temporal for our job layer — read what we have in workers/ and tell me honestly whether switching buys us anything. no code","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"godoc comments on everything exported in pkg/graph. mention the panic conditions, they're not obvious","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"what does this regex do","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"bull vs temporal for our job layer — read what we have in workers/ and tell me honestly whether switching buys us anything. no code","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"godoc comments on everything exported in pkg/graph. mention the panic conditions, they're not obvious","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"changelog entry: we removed --legacy-auth from the cli, and there's no replacement flag, people need to use the config file","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"commit message for what's staged","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"map out how we'd add row level security to the reporting db without breaking the 40-odd existing queries, then do the first table as a proof","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"clean up whatever's left","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"map out how we'd add row level security to the reporting db without breaking the 40-odd existing queries, then do the first table as a proof","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} {"prompt":"we're getting rate limited by the maps provider at peak. write up options — client side caching, a proxy with a shared cache, or negotiating tiers — with cost estimates and what each one costs us in latency","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"i want a design for replay: given an aggregate id we should be able to rebuild its state from the event log at any point in time. we have 14 event types and three of them changed shape without versioning. how do we handle that","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"grpc streaming endpoint for live telemetry, server-side only, 5k concurrent devices, backpressure via a bounded channel and drop-oldest","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"grpc streaming endpoint for live telemetry, server-side only, 5k concurrent devices, backpressure via a bounded channel and drop-oldest","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"cli subcommand `vault export --format=env` that dumps decrypted secrets to stdout, refuses if stdout is a tty unless you pass --force","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"implement the sliding window counter for the abuse limiter in go, per-ip and per-account, redis lua so it's atomic","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"implement the sliding window counter for the abuse limiter in go, per-ip and per-account, redis lua so it's atomic","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the empty state for Saved Items is just the word 'empty'. give it an illustration slot, a headline, a subhead and a CTA that deep links to browse","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"toast notifications — stack up to 3, auto dismiss at 4s, pause the timer on hover, swipe to dismiss on touch. no libraries, we already have framer motion","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"kerning on the pricing table headers is off and the third column is 2px wider than the others for no reason i can find","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"pin actions/checkout to a sha instead of v4 in all the workflows","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"kerning on the pricing table headers is off and the third column is 2px wider than the others for no reason i can find","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"pin actions/checkout to a sha instead of v4 in all the workflows","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"log line says 'Retrying in {}s' with no arg filled in, fix the format call","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"clippy is unhappy after the toolchain bump:\n\nwarning: this expression creates a reference which is immediately dereferenced by the compiler\n --> src/index/segment.rs:214:27\n |\n214 | self.merge_into(&mut writer, &fields)\n | ^^^^^^^ help: change this to: `fields`\n = note: `-W clippy::needless-borrow` implied by `-D warnings`\n\nwarning: called `map(..).flatten()` on an `Iterator`\n --> src/index/segment.rs:301:18\n |\n301 | .map(|d| d.terms()).flatten()\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: try: `flat_map(|d| d.terms())`\n\nwarning: redundant clone\n --> src/query/plan.rs:77:41\n |\n77 | let filters = self.filters.clone();\n | ^^^^^^^^ help: remove this\n\nerror: could not compile `tantivy-lite` (lib) due to 3 warnings\n\nCI is red on -D warnings, just get it green","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"pasted-context","lang":"en"} {"prompt":"kill the singleton in AnalyticsManager.shared, inject it instead. every call site, tests included, same events firing at the same times","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"hoist the duplicated zod schemas out of the route files into schemas/ and re-export, nothing about validation behavior should change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"swap our hand rolled Result type for anyhow across the crate. it's mechanical but there are a few places we match on the error variant","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"test_scheduler.py::test_backoff_jitter fails maybe 5% of the time in CI, never once locally, and the assertion is on a duration so i assume timing but i've been wrong about that before","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"swap our hand rolled Result type for anyhow across the crate. it's mechanical but there are a few places we match on the error variant","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"test_scheduler.py::test_backoff_jitter fails maybe 5% of the time in CI, never once locally, and the assertion is on a duration so i assume timing but i've been wrong about that before","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"pods keep restarting after the deploy, here's kubectl describe:\n\nEvents:\n Type Reason Age From Message\n ---- ------ ---- ---- -------\n Normal Pulled 8m kubelet Container image \"registry/api:2026.7.4\" already present\n Normal Created 8m kubelet Created container api\n Normal Started 8m kubelet Started container api\n Warning Unhealthy 7m (x3 over 7m) kubelet Readiness probe failed: HTTP probe failed with statuscode: 503\n Warning Unhealthy 6m (x2 over 6m) kubelet Liveness probe failed: Get \"http://10.42.3.19:8080/healthz\": context deadline exceeded\n Normal Killing 6m kubelet Container api failed liveness probe, will be restarted\n Warning BackOff 2m (x14 over 6m) kubelet Back-off restarting failed container\n\nthe same image runs fine in staging with the same manifests","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"warum liefert unser Cache nach dem Deploy gelegentlich Daten vom Vortag? TTL ist 60s, ich verstehe es nicht","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} +{"prompt":"warum liefert unser Cache nach dem Deploy gelegentlich Daten vom Vortag? TTL ist 60s, ich verstehe es nicht","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"de"} {"prompt":"read through migrations/ and tell me which of these are not reversible, i want to know before we promise a rollback plan","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"second opinion on this hunk before i merge:\n\n@@ -41,15 +41,22 @@ func (s *Store) Claim(ctx context.Context, workerID string) (*Job, error) {\n-\trow := s.db.QueryRowContext(ctx, `\n-\t\tUPDATE jobs SET state='running', worker_id=$1, claimed_at=now()\n-\t\tWHERE id = (SELECT id FROM jobs WHERE state='queued' ORDER BY priority DESC, id LIMIT 1)\n-\t\tRETURNING id, payload`, workerID)\n+\ttx, err := s.db.BeginTx(ctx, nil)\n+\tif err != nil {\n+\t\treturn nil, err\n+\t}\n+\tdefer tx.Rollback()\n+\trow := tx.QueryRowContext(ctx, `\n+\t\tSELECT id, payload FROM jobs\n+\t\tWHERE state='queued' ORDER BY priority DESC, id\n+\t\tLIMIT 1 FOR UPDATE SKIP LOCKED`)\n \tvar j Job\n \tif err := row.Scan(&j.ID, &j.Payload); err != nil {\n \t\treturn nil, err\n \t}\n+\tif _, err := tx.ExecContext(ctx, `UPDATE jobs SET state='running', worker_id=$1, claimed_at=now() WHERE id=$2`, workerID, j.ID); err != nil {\n+\t\treturn nil, err\n+\t}\n+\treturn &j, tx.Commit()\n }","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"is it actually a problem that we hold the mutex across the http call in fetchProfile, or am i being paranoid","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"is it actually a problem that we hold the mutex across the http call in fetchProfile, or am i being paranoid","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"migration guide for people on v2 of the sdk. the auth constructor changed, retries are opt-out now instead of opt-in, and the pagination helper is gone","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"translate the error message catalog in i18n/errors.en.json to fr and pt-BR, keep the placeholders exactly as they are","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"the /webhooks docs page doesn't mention retry semantics or the signature header at all. document both, and be precise about the timestamp tolerance window","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"do the thing we talked about with the queue","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"the /webhooks docs page doesn't mention retry semantics or the signature header at all. document both, and be precise about the timestamp tolerance window","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"shape up a proposal for how we test the embedded firmware in CI. we have 6 boards on a bench and no automation. include what we fake vs what we run on metal","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"propose the data model for a shared shopping list — offline edits on multiple devices, we need last-writer-wins per field not per row, and deletes have to survive a sync that arrives out of order","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"propose the data model for a shared shopping list — offline edits on multiple devices, we need last-writer-wins per field not per row, and deletes have to survive a sync that arrives out of order","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"estrategia para migrar del monolito Django a servicios, tenemos 8 meses. quiero el orden de extracción y los riesgos, sin código todavía","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"es"} -{"prompt":"webhook delivery service: at-least-once, exponential backoff to 24h, dead letter after that, per-endpoint concurrency cap so one slow customer can't starve the pool","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"webhook delivery service: at-least-once, exponential backoff to 24h, dead letter after that, per-endpoint concurrency cap so one slow customer can't starve the pool","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"add SAML SSO to the admin panel, okta first. just-in-time provisioning, and the group claim maps to our roles table","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"write the tree-sitter based symbol indexer for the language server, incremental on edit, python and ts to start","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"drag to reorder for the playlist rows in SwiftUI, haptic on pickup, and the row being dragged should lift with a shadow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the game's pause menu needs controller focus handling — dpad moves selection, B backs out, and the currently focused item should be obvious at a glance on a tv","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"make the copy button in the code blocks actually visible instead of appearing on hover only, mobile users can't get to it","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"drag to reorder for the playlist rows in SwiftUI, haptic on pickup, and the row being dragged should lift with a shadow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the game's pause menu needs controller focus handling — dpad moves selection, B backs out, and the currently focused item should be obvious at a glance on a tv","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"make the copy button in the code blocks actually visible instead of appearing on hover only, mobile users can't get to it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"vite config, raise chunkSizeWarningLimit, the warning is noise","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"we spell it 'canceled' in half the ui strings and 'cancelled' in the other half. pick the double-l one and make it uniform","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"we spell it 'canceled' in half the ui strings and 'cancelled' in the other half. pick the double-l one and make it uniform","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"the cors config is missing the new preview domain, add *.preview.acme.dev","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"flatten the three levels of inheritance under BaseRepository into composition. i don't want to change a single query","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"split the god module utils.py — 2200 lines, everything imports it, circular imports everywhere. by concern, keep re-exports so nothing breaks","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"rename the whole `Widget` concept to `Panel` — types, files, css classes, storybook stories, the graphql field too. it's the term everyone actually uses","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"the mac app hangs for ~8 seconds on first launch after an update, spindump shows a bunch of threads waiting on something in our keychain code but i can't tell what's blocking","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"search results come back in a different order for the same query depending on which replica answers. shouldn't the sort be deterministic","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"asan on the firmware sim:\n\n==2917==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60300000ef34 at pc 0x000104a1b2c1 bp 0x7ff7bfef1f10 sp 0x7ff7bfef1ed0\nREAD of size 4 at 0x60300000ef34 thread T0\n #0 0x104a1b2c0 in ring_pop ring.c:88\n #1 0x104a19a44 in uart_drain uart.c:213\n #2 0x104a1c110 in main_loop main.c:64\n\n0x60300000ef34 is located 0 bytes to the right of 20-byte region [0x60300000ef20,0x60300000ef34)\nallocated by thread T0 here:\n #0 0x10a4c1b90 in wrap_calloc\n #1 0x104a1ae08 in ring_init ring.c:31\n\nSUMMARY: AddressSanitizer: heap-buffer-overflow ring.c:88 in ring_pop\n\nonly trips when the buffer wraps. i've stared at the modulo for an hour","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"explain the ownership model in src/session — who's allowed to mutate a Session and when, because i keep getting borrow errors and i think i'm holding it wrong conceptually","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"how does our feature flag evaluation order work when a user matches two segments","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"give me a tour of the build pipeline in Makefile + scripts/, i inherited this repo yesterday","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"adr for the decision to keep sessions in postgres instead of redis. context, options we looked at, consequences, the usual shape","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"summarize what changed in the auth service over the last two weeks for the team update, plain language, no commit hashes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"onboarding doc for new backend hires — local setup, how to get seed data, the four services they'll actually touch, who to ask about what","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"flatten the three levels of inheritance under BaseRepository into composition. i don't want to change a single query","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"split the god module utils.py — 2200 lines, everything imports it, circular imports everywhere. by concern, keep re-exports so nothing breaks","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"rename the whole `Widget` concept to `Panel` — types, files, css classes, storybook stories, the graphql field too. it's the term everyone actually uses","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the mac app hangs for ~8 seconds on first launch after an update, spindump shows a bunch of threads waiting on something in our keychain code but i can't tell what's blocking","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"search results come back in a different order for the same query depending on which replica answers. shouldn't the sort be deterministic","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"asan on the firmware sim:\n\n==2917==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60300000ef34 at pc 0x000104a1b2c1 bp 0x7ff7bfef1f10 sp 0x7ff7bfef1ed0\nREAD of size 4 at 0x60300000ef34 thread T0\n #0 0x104a1b2c0 in ring_pop ring.c:88\n #1 0x104a19a44 in uart_drain uart.c:213\n #2 0x104a1c110 in main_loop main.c:64\n\n0x60300000ef34 is located 0 bytes to the right of 20-byte region [0x60300000ef20,0x60300000ef34)\nallocated by thread T0 here:\n #0 0x10a4c1b90 in wrap_calloc\n #1 0x104a1ae08 in ring_init ring.c:31\n\nSUMMARY: AddressSanitizer: heap-buffer-overflow ring.c:88 in ring_pop\n\nonly trips when the buffer wraps. i've stared at the modulo for an hour","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"explain the ownership model in src/session — who's allowed to mutate a Session and when, because i keep getting borrow errors and i think i'm holding it wrong conceptually","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"how does our feature flag evaluation order work when a user matches two segments","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"give me a tour of the build pipeline in Makefile + scripts/, i inherited this repo yesterday","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"adr for the decision to keep sessions in postgres instead of redis. context, options we looked at, consequences, the usual shape","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"summarize what changed in the auth service over the last two weeks for the team update, plain language, no commit hashes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"onboarding doc for new backend hires — local setup, how to get seed data, the four services they'll actually touch, who to ask about what","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"outline how we'd add end to end encryption to attachments and then wire up the key derivation piece","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} {"prompt":"fix the flaky one and write the note for the ticket about why it was flaky","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"i want to introduce a read model for the inventory dashboard because the joins are killing us. write the design — where projections live, how we rebuild, what staleness we accept — and flag anything that forces an api change","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"how should we structure the monorepo now that we have 3 apps and 11 packages? turborepo is in already but the boundaries are mush. give me a target layout and a path to get there","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"batch import endpoint, csv up to 500mb, presigned upload then async processing, per-row errors reported back with line numbers","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"full text search over the notes table with tsvector, weighted title over body, and a trigger to keep the column current","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the docs promise an `X-Request-Id` echo on every response but the middleware only sets it on 2xx. make reality match the docs","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"i want to introduce a read model for the inventory dashboard because the joins are killing us. write the design — where projections live, how we rebuild, what staleness we accept — and flag anything that forces an api change","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"how should we structure the monorepo now that we have 3 apps and 11 packages? turborepo is in already but the boundaries are mush. give me a target layout and a path to get there","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"batch import endpoint, csv up to 500mb, presigned upload then async processing, per-row errors reported back with line numbers","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"full text search over the notes table with tsvector, weighted title over body, and a trigger to keep the column current","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the docs promise an `X-Request-Id` echo on every response but the middleware only sets it on 2xx. make reality match the docs","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"onboarding carousel, 4 pages, page dots, skip in the corner, and it should never show again after completion","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"virtualize the log viewer, we render 200k rows and the tab dies. keep the sticky timestamp column and the find-in-page highlight working","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"spacing on the invoice pdf preview is off — line items too tight, totals block should hug the right edge with a rule above it","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"virtualize the log viewer, we render 200k rows and the tab dies. keep the sticky timestamp column and the find-in-page highlight working","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"spacing on the invoice pdf preview is off — line items too tight, totals block should hug the right edge with a rule above it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"raise the pg pool from 10 to 25 in config/database.yml","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"npm audit is screaming about the tar transitive dep, get us onto a patched version without breaking the build","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"the date format string is MM/DD/YYYY in ExportPanel but everywhere else we use ISO, change it there too","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"untangle the circular dep between the auth package and the user package. probably an interface in a third place, behavior stays put","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"npm audit is screaming about the tar transitive dep, get us onto a patched version without breaking the build","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"the date format string is MM/DD/YYYY in ExportPanel but everywhere else we use ISO, change it there too","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"untangle the circular dep between the auth package and the user package. probably an interface in a third place, behavior stays put","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"our reducers all have the same 30 lines of optimistic-update bookkeeping. factor it into one helper and adopt it in all seven","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"simplify these nested ternaries in PriceBadge, they're unreadable. same rendered output, i'll diff the snapshots","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"requests to the payments provider started timing out at exactly 10s about 40% of the time, started tuesday, nothing deployed tuesday. their status page is green","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"simplify these nested ternaries in PriceBadge, they're unreadable. same rendered output, i'll diff the snapshots","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"requests to the payments provider started timing out at exactly 10s about 40% of the time, started tuesday, nothing deployed tuesday. their status page is green","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"tail of the failing CI job, this is the fourth rerun:\n\n ✓ apps/web:test (48.2s)\n ✓ packages/ui:test (12.9s)\n ✗ apps/api:test\n\n FAIL src/queue/consumer.test.ts > consumer > acks after successful handler\n Error: Timeout of 5000ms exceeded. The last call to done() was never made.\n at listOnTimeout (node:internal/timers:581:17)\n\n stderr | src/queue/consumer.test.ts\n [amqp] connection closed unexpectedly (code 320, CONNECTION_FORCED)\n [amqp] reconnect attempt 1 in 500ms\n [amqp] reconnect attempt 2 in 1000ms\n\n Test Files 1 failed | 22 passed (23)\n Tests 1 failed | 318 passed (319)\n Duration 91.44s\n\nERROR: command finished with error: exit 1\n\nit passed 60 times in a row before this week","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} {"prompt":"iOS widget shows stale data until you open the app, timeline provider looks right to me","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"read the caching layer in internal/cache and tell me under what conditions we can serve a stale value. i'm not saying anything's wrong, i just need to know the guarantees","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"read the caching layer in internal/cache and tell me under what conditions we can serve a stale value. i'm not saying anything's wrong, i just need to know the guarantees","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"security pass on the file upload path — content type sniffing, path traversal in the key, and whether a signed url can be replayed","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"où est-ce que le token est validé exactement dans le middleware? explique moi le chemin complet d'une requête authentifiée","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"fr"} {"prompt":"blog post draft about how we cut p95 from 900ms to 210ms. technical audience, real numbers, no marketing voice","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"inline comments in scheduler.go explaining the priority inversion guard, future me will not remember why that sleep is there","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"deprecation notice for the /v1 endpoints — sunset date, what to use instead, and the header we'll start returning","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"inline comments in scheduler.go explaining the priority inversion guard, future me will not remember why that sleep is there","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"deprecation notice for the /v1 endpoints — sunset date, what to use instead, and the header we'll start returning","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"just get it working","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"we keep hitting the 6MB lambda response limit on the report endpoint. lay out the options — s3 handoff, pagination, streaming through an alb — and recommend one given our client is a react app that renders the whole table","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"break the accessibility work into shippable chunks. audit found 140 issues across 30 screens and leadership wants a quarterly commitment","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"設計だけお願いしたい。マルチテナントの権限モデルを RBAC から ReBAC に寄せたい場合の移行方針を書いて、既存の 60 個くらいのパーミッションチェックへの影響も洗い出して","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"ja"} -{"prompt":"wire up outbox pattern for the order events — write to outbox in the same tx, a poller publishes to kafka, dedupe on the consumer side by event id","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"wire up outbox pattern for the order events — write to outbox in the same tx, a poller publishes to kafka, dedupe on the consumer side by event id","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"python service that pulls the hourly weather grib files, subsets to our bounding boxes and writes zarr. retries on partial downloads, resumable","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"add cursor pagination to GET /activity. opaque cursor, stable under inserts, include has_more, and don't break the existing page/limit callers","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"add cursor pagination to GET /activity. opaque cursor, stable under inserts, include has_more, and don't break the existing page/limit callers","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"keyboard shortcut palette, cmd+k, fuzzy filter, recent commands at top, and it has to trap focus properly","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"the map pins overlap at low zoom, cluster them and animate the expand when you zoom in","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"shrink the avatar in the comment header, it's competing with the name","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"shrink the avatar in the comment header, it's competing with the name","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"prod log level is debug, drop it to info before we burn more money","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"off by one in the pagination footer, it says 'showing 1-20 of 20' when there are 21","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"esse timeout de 3s no client HTTP tá curto demais, sobe pra 15s e deixa configurável por env","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"pt"} -{"prompt":"move the 12 test helpers out of conftest.py into a fixtures package, group by domain, all 900 tests should pass unchanged","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"off by one in the pagination footer, it says 'showing 1-20 of 20' when there are 21","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"esse timeout de 3s no client HTTP tá curto demais, sobe pra 15s e deixa configurável por env","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"pt"} +{"prompt":"move the 12 test helpers out of conftest.py into a fixtures package, group by domain, all 900 tests should pass unchanged","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"replace our bespoke event emitter with node's EventEmitter, keep the same subscribe/unsubscribe semantics including the once behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"extract the 200 line switch in handleCommand into a dispatch table, one file per command, no functional change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"extract the 200 line switch in handleCommand into a dispatch table, one file per command, no functional change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"csv exports come out with mojibake for anything non-ascii but only when downloaded from safari. same bytes look fine in curl","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"tsc suddenly unhappy after pulling main, i didn't touch types:\n\nsrc/features/billing/useSubscription.ts:44:5 - error TS2322: Type '{ status: string; renewsAt: string | null; }' is not assignable to type 'Subscription'.\n Types of property 'status' are incompatible.\n Type 'string' is not assignable to type 'SubscriptionStatus'.\n\n44 return { status: data.status, renewsAt: data.renews_at }\n ~~~~~~\n\nsrc/features/billing/PlanCard.tsx:19:34 - error TS2339: Property 'renewsAt' does not exist on type 'Subscription | LegacySubscription'.\n Property 'renewsAt' does not exist on type 'LegacySubscription'.\n\n19 const label = formatRenewal(sub.renewsAt)\n ~~~~~~~~\n\nFound 2 errors in 2 files.\n\nnobody on the team knows where LegacySubscription came from","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} -{"prompt":"gpu memory climbs across training epochs until it OOMs around epoch 30. torch 2.6, i'm detaching the loss, i think","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"does our retry logic in the sms client risk double-sending? walk me through what happens on a timeout after the provider already accepted","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"tsc suddenly unhappy after pulling main, i didn't touch types:\n\nsrc/features/billing/useSubscription.ts:44:5 - error TS2322: Type '{ status: string; renewsAt: string | null; }' is not assignable to type 'Subscription'.\n Types of property 'status' are incompatible.\n Type 'string' is not assignable to type 'SubscriptionStatus'.\n\n44 return { status: data.status, renewsAt: data.renews_at }\n ~~~~~~\n\nsrc/features/billing/PlanCard.tsx:19:34 - error TS2339: Property 'renewsAt' does not exist on type 'Subscription | LegacySubscription'.\n Property 'renewsAt' does not exist on type 'LegacySubscription'.\n\n19 const label = formatRenewal(sub.renewsAt)\n ~~~~~~~~\n\nFound 2 errors in 2 files.\n\nnobody on the team knows where LegacySubscription came from","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"gpu memory climbs across training epochs until it OOMs around epoch 30. torch 2.6, i'm detaching the loss, i think","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"does our retry logic in the sms client risk double-sending? walk me through what happens on a timeout after the provider already accepted","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"review the new dockerfile, i'm mostly worried about image size and whether we're leaking build secrets into a layer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"what's the difference between our two queue implementations and why do both exist","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"what's the difference between our two queue implementations and why do both exist","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"user facing help article for the new saved-views feature. friendly tone, screenshots marked as TODO where they go","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"the CONTRIBUTING file predates the monorepo move and tells people to run yarn. rewrite it for pnpm and the new package layout","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"rfc doc for the rewrite plus a proof of concept of the new renderer so people can see it's not vapor","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"explain what the throttle in useScrollSpy is doing and then rewrite it with the shared hook","purpose":"review","secondary":"refactor","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} -{"prompt":"back to the payment flow bug from yesterday","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"the CONTRIBUTING file predates the monorepo move and tells people to run yarn. rewrite it for pnpm and the new package layout","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"rfc doc for the rewrite plus a proof of concept of the new renderer so people can see it's not vapor","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"explain what the throttle in useScrollSpy is doing and then rewrite it with the shared hook","purpose":"review","secondary":"refactor","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} {"prompt":"we need a story for schema evolution on the kafka topics. avro + registry, or protobuf, or just json and pray. write it up with what each costs us operationally","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"sketch the state machine for the checkout flow. states, allowed transitions, what happens on a browser back, where we persist. diagram in mermaid is fine","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"rate limiter for the public api — tiered by plan, burst allowance, 429 with retry-after, and the counters can't be a single redis hot key","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"soft delete on the projects table plus the scoping so nothing leaks into list endpoints, and a hard-purge job for the 30 day mark","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"go worker that watches the s3 bucket via sqs notifications and thumbnails anything new, three sizes, skip if the derivative already exists","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"rate limiter for the public api — tiered by plan, burst allowance, 429 with retry-after, and the counters can't be a single redis hot key","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"soft delete on the projects table plus the scoping so nothing leaks into list endpoints, and a hard-purge job for the 30 day mark","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"go worker that watches the s3 bucket via sqs notifications and thumbnails anything new, three sizes, skip if the derivative already exists","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"inline editing on the table cells — click to edit, esc cancels, enter commits and moves down a row, optimistic with a rollback on error","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"hero section for the landing page: big headline, gradient mesh behind it, two ctas, and it can't jank on scroll","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the destructive action in the context menu should be red and last in the list, right now it's first and looks like everything else","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"the destructive action in the context menu should be red and last in the list, right now it's first and looks like everything else","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"add a .nvmrc with 22","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"the ignore list in .gitignore is missing .env.local and someone will commit it eventually","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"our health endpoint returns 200 even when the db check fails, it should be 503. small change in health.go, i know exactly where","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"our health endpoint returns 200 even when the db check fails, it should be 503. small change in health.go, i know exactly where","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"the graphql resolvers reach into the ORM directly. put a service layer between them, one service per domain, resolvers get thin. no schema changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"swift concurrency cleanup in NetworkClient — it's half completion handlers half async, unify on async and mark the actor boundaries properly","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"kill the dead code under legacy/ — but check nothing outside legacy/ imports it first, including the cron scripts","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"two users report their calendar events shifted by an hour but only for events created before the DST switch. we store utc so i genuinely don't see how","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"kill the dead code under legacy/ — but check nothing outside legacy/ imports it first, including the cron scripts","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"two users report their calendar events shifted by an hour but only for events created before the DST switch. we store utc so i genuinely don't see how","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"docker build dies on the arm runner only:\n\n #12 [builder 6/9] RUN cargo build --release --locked\n #12 24.31 Compiling ring v0.17.8\n #12 31.02 error: failed to run custom build command for `ring v0.17.8`\n #12 31.02 \n #12 31.02 Caused by:\n #12 31.02 process didn't exit successfully: `/app/target/release/build/ring-8f1d/build-script-build` (exit status: 101)\n #12 31.02 --- stderr\n #12 31.02 thread 'main' panicked at build.rs:684:9:\n #12 31.02 error building ring: exit status: 1\n #12 31.02 note: run with `RUST_BACKTRACE=1`\n------\nfailed to solve: process \"/bin/sh -c cargo build --release --locked\" did not complete successfully: exit code: 101\n\nx86 builds fine, same dockerfile, same lockfile","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} {"prompt":"intermittent 502s from the ingress, maybe 1 in 500 requests, no matching error in the app logs at all","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"does the new websocket auth actually prevent a user from subscribing to another tenant's channel? show me where that's enforced","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"does the new websocket auth actually prevent a user from subscribing to another tenant's channel? show me where that's enforced","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"read AGENTS.md and the two scripts it references and tell me if a fresh clone could actually follow it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"how much of the query cost in the dashboard comes from the permission filter vs the actual data fetch, based on reading the code not profiling","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"terraform docs for the vpc module — inputs, outputs, an example, and the note about why the nat gateway is single-az on purpose","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"changelog for the last three releases, we never wrote them and now someone asked","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"docstrings for the pandas transforms in etl/transform.py, including what each one assumes about the input index","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"how much of the query cost in the dashboard comes from the permission filter vs the actual data fetch, based on reading the code not profiling","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"terraform docs for the vpc module — inputs, outputs, an example, and the note about why the nat gateway is single-az on purpose","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"changelog for the last three releases, we never wrote them and now someone asked","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"docstrings for the pandas transforms in etl/transform.py, including what each one assumes about the input index","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"would you mind drafting the design for the replay system in our netcode? deterministic lockstep vs snapshot interpolation, 60hz sim, up to 8 players, and replays have to stay valid across patch versions","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"help me carve the k8s migration into phases. we're on ECS today, nobody here has run kubernetes in prod, and we can't have a hard cutover weekend","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"work out the approach for sharding leaderboard writes and write it down. i don't want an implementation yet, just the shape and where it breaks","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"please implement the matchmaking queue — mmr buckets that widen the longer you wait, parties up to 4, and a soft cap so a stack of 4 never faces 4 solos","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"help me carve the k8s migration into phases. we're on ECS today, nobody here has run kubernetes in prod, and we can't have a hard cutover weekend","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"work out the approach for sharding leaderboard writes and write it down. i don't want an implementation yet, just the shape and where it breaks","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"please implement the matchmaking queue — mmr buckets that widen the longer you wait, parties up to 4, and a soft cap so a stack of 4 never faces 4 solos","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"terraform module for a spot-backed gpu node group with an on-demand fallback group, taints and tolerations so only training jobs land there","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the design in docs/adr-014 is already signed off, just build the outbox poller for telemetry events per that doc","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"the design in docs/adr-014 is already signed off, just build the outbox poller for telemetry events per that doc","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"floating damage numbers in the hud — spawn at hit position, drift up, fade over 0.8s, pooled so we don't allocate per hit","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"loading bar looks dead, animate it","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"from the ticket, build this screen:\n\nTitle: Squad detail sheet\nAs a player I want to see my squad's recent matches so I can tell who's been carrying.\n\n- opens as a half sheet from the squad row, drag to full height\n- top: squad crest (48pt), name, member count, join code with a copy button\n- segmented control: Matches / Members / Settings (settings only visible to the owner)\n- Matches tab: list of last 20, each row = map thumbnail, result pill (W/L/D), duration, relative time\n- empty state when a new squad has no matches yet\n- Members tab: avatar rows with online dot, owner gets a swipe-to-kick action\n- pull to refresh on both tabs, skeleton rows while loading\n\nSwiftUI, and reuse ResultPill from the match history screen","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"loading bar looks dead, animate it","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"from the ticket, build this screen:\n\nTitle: Squad detail sheet\nAs a player I want to see my squad's recent matches so I can tell who's been carrying.\n\n- opens as a half sheet from the squad row, drag to full height\n- top: squad crest (48pt), name, member count, join code with a copy button\n- segmented control: Matches / Members / Settings (settings only visible to the owner)\n- Matches tab: list of last 20, each row = map thumbnail, result pill (W/L/D), duration, relative time\n- empty state when a new squad has no matches yet\n- Members tab: avatar rows with online dot, owner gets a swipe-to-kick action\n- pull to refresh on both tabs, skeleton rows while loading\n\nSwiftUI, and reuse ResultPill from the match history screen","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"helm values, replicaCount 3","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"tooltip says 'recieve', fix","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"default port should be 8443 not 8080 — the config struct and the sample yaml both","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"train.py and eval.py each build the whole dataloader from scratch and they've drifted. one shared builder, both scripts use it, metrics should come out identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"tooltip says 'recieve', fix","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0,"slice":"core","lang":"en"} +{"prompt":"default port should be 8443 not 8080 — the config struct and the sample yaml both","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"train.py and eval.py each build the whole dataloader from scratch and they've drifted. one shared builder, both scripts use it, metrics should come out identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"our unity managers are all static singletons which makes the test scene impossible. put interfaces in front of them and inject through the bootstrapper","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the pipeline configs use snake_case for column names in some yamls and camelCase in others. normalize on snake everywhere including the dbt models that reference them","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"gpu sits at 12% the whole training run, num_workers is 8, prefetch is on, i've been staring at nsight for two hours and cant find the stall","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"why is the mesh flickering","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"spark job dies on the join stage, third time today:\n\n25/07/29 03:12:44 WARN TaskSetManager: Lost task 118.0 in stage 7.0 (TID 4412) (10.0.7.44 executor 12): ExecutorLostFailure (executor 12 exited caused by one of the running tasks) Reason: Container killed by YARN for exceeding physical memory limits. 28.4 GB of 28 GB physical memory used. Consider boosting spark.executor.memoryOverhead.\n25/07/29 03:12:51 INFO DAGScheduler: Resubmitting ShuffleMapStage 6 (mapToPair) due to fetch failure\n25/07/29 03:14:09 WARN BlockManagerMasterEndpoint: No more replicas available for shuffle_3_118_0\n25/07/29 03:16:22 ERROR TaskSetManager: Task 118 in stage 7.0 failed 4 times; aborting job\n\nspark.sql.shuffle.partitions is 2000 already. the input only grew ~5% week over week so this feels like something else","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"explain how our terraform state locking works with that dynamodb table, and what actually happens if two applies race","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"is it expected that the physics step runs twice on the first frame after a scene load? trying to tell if that's by design in our bootstrap or not","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"look over the IAM policy attached to the CI role and tell me what it can do that it shouldn't","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the pipeline configs use snake_case for column names in some yamls and camelCase in others. normalize on snake everywhere including the dbt models that reference them","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"gpu sits at 12% the whole training run, num_workers is 8, prefetch is on, i've been staring at nsight for two hours and cant find the stall","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"why is the mesh flickering","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"spark job dies on the join stage, third time today:\n\n25/07/29 03:12:44 WARN TaskSetManager: Lost task 118.0 in stage 7.0 (TID 4412) (10.0.7.44 executor 12): ExecutorLostFailure (executor 12 exited caused by one of the running tasks) Reason: Container killed by YARN for exceeding physical memory limits. 28.4 GB of 28 GB physical memory used. Consider boosting spark.executor.memoryOverhead.\n25/07/29 03:12:51 INFO DAGScheduler: Resubmitting ShuffleMapStage 6 (mapToPair) due to fetch failure\n25/07/29 03:14:09 WARN BlockManagerMasterEndpoint: No more replicas available for shuffle_3_118_0\n25/07/29 03:16:22 ERROR TaskSetManager: Task 118 in stage 7.0 failed 4 times; aborting job\n\nspark.sql.shuffle.partitions is 2000 already. the input only grew ~5% week over week so this feels like something else","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"explain how our terraform state locking works with that dynamodb table, and what actually happens if two applies race","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"is it expected that the physics step runs twice on the first frame after a scene load? trying to tell if that's by design in our bootstrap or not","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"look over the IAM policy attached to the CI role and tell me what it can do that it shouldn't","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"runbook for when the nightly training run fails — how to tell if it's data or infra, how to resume from the last checkpoint, who to page","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"document the /predict endpoint contract properly — input tensor shapes, the accepted dtypes, every error code and what triggers it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"document the /predict endpoint contract properly — input tensor shapes, the accepted dtypes, every error code and what triggers it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"patch notes for the mod tools update, player-facing, upbeat but not cringe","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"same thing but for the eu region","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"i need a plan for getting off our homegrown migrations tool. 340 migration files, some hand-edited in prod, and two databases that have diverged. tell me how you'd sequence it and what we do about the drift","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"roadmap please, one quarter, for making the cli usable offline. today every command hits the api","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"diseña el flujo de invitaciones para equipos: enlaces con expiración, roles preasignados, y qué pasa si el email ya tiene cuenta en otra org. sólo el diseño por ahora","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"es"} {"prompt":"could you add a websocket presence channel — who's viewing a document right now, heartbeat every 20s, cleanup on disconnect, and it should survive a server restart without ghost users","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"sqlite fts5 index for the local notes cache in the mac app, incremental update on save","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"sqlite fts5 index for the local notes cache in the mac app, incremental update on save","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"job that expires trial accounts at 14 days, sends the two reminder emails at day 10 and 13, and never double sends even if it runs twice","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"settings panel needs a two column layout on desktop, single column under 768. the section nav on the left should be sticky and highlight the section you're in","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"bar chart for weekly active devices, hover tooltip with exact counts, and the y axis shouldn't start at zero-ish weirdness like it does now","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the badge on the notifications icon is 1px off center, and it should hide entirely at zero instead of showing '0'","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"mypy is red after i added the protocol, probably five minutes of work:\n\nsrc/acme/store/redis_store.py:31: error: Signature of \"get\" incompatible with supertype \"KeyValueStore\" [override]\nsrc/acme/store/redis_store.py:31: note: Superclass:\nsrc/acme/store/redis_store.py:31: note: def get(self, key: str) -> bytes | None\nsrc/acme/store/redis_store.py:31: note: Subclass:\nsrc/acme/store/redis_store.py:31: note: def get(self, key: str, default: bytes = ...) -> bytes\nsrc/acme/store/memory_store.py:19: error: Missing return statement [return]\nsrc/acme/api/deps.py:57: error: Argument 1 to \"Depends\" has incompatible type \"Callable[[Request], Coroutine[Any, Any, KeyValueStore]]\"; expected \"Callable[..., KeyValueStore]\" [arg-type]\nFound 3 errors in 3 files (checked 214 source files)","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"pasted-context","lang":"en"} -{"prompt":"sentry dsn is hardcoded in main.ts, move it to an env var","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"bar chart for weekly active devices, hover tooltip with exact counts, and the y axis shouldn't start at zero-ish weirdness like it does now","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the badge on the notifications icon is 1px off center, and it should hide entirely at zero instead of showing '0'","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"mypy is red after i added the protocol, probably five minutes of work:\n\nsrc/acme/store/redis_store.py:31: error: Signature of \"get\" incompatible with supertype \"KeyValueStore\" [override]\nsrc/acme/store/redis_store.py:31: note: Superclass:\nsrc/acme/store/redis_store.py:31: note: def get(self, key: str) -> bytes | None\nsrc/acme/store/redis_store.py:31: note: Subclass:\nsrc/acme/store/redis_store.py:31: note: def get(self, key: str, default: bytes = ...) -> bytes\nsrc/acme/store/memory_store.py:19: error: Missing return statement [return]\nsrc/acme/api/deps.py:57: error: Argument 1 to \"Depends\" has incompatible type \"Callable[[Request], Coroutine[Any, Any, KeyValueStore]]\"; expected \"Callable[..., KeyValueStore]\" [arg-type]\nFound 3 errors in 3 files (checked 214 source files)","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} +{"prompt":"sentry dsn is hardcoded in main.ts, move it to an env var","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"prometheus scrape interval 15s -> 30s, we're drowning in cardinality anyway","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"the api handlers each do their own auth check with slightly different logic. one middleware, applied at the router, identical decisions to what we have now — audit them first so nothing gets accidentally opened up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"our css is 40% dead. we have tailwind AND a legacy sass bundle. consolidate onto tailwind, screens should render pixel identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"pull the magic numbers in the gameplay tuning code into a config asset. same values, designers should be able to edit them without a rebuild","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"search suggestions endpoint got 4x slower after we shipped last week. p50 fine, p99 terrible. no query changes in the diff that i can see","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"pull the magic numbers in the gameplay tuning code into a config asset. same values, designers should be able to edit them without a rebuild","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"search suggestions endpoint got 4x slower after we shipped last week. p50 fine, p99 terrible. no query changes in the diff that i can see","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the android release build crashes at startup but debug is fine. proguard i assume but the mapping file isnt telling me much","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"prometheus fired this at 4am and i can't reproduce it now:\n\nALERT: KafkaConsumerLagGrowing\nSTATE: firing (7m)\nlabels:\n consumergroup=enrichment-v3\n topic=events.raw\n partition=11\n severity=warning\nannotations:\n summary=consumer lag 1.2M and climbing on partition 11 only\n runbook=https://wiki/int/kafka-lag\nvalue: 1214883\n\nother 23 partitions were at basically zero lag the whole time. rebalance count didn't change. what makes ONE partition fall behind like that","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"what happens to in-flight requests when we scale down? read the shutdown path and tell me if we actually drain","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"prometheus fired this at 4am and i can't reproduce it now:\n\nALERT: KafkaConsumerLagGrowing\nSTATE: firing (7m)\nlabels:\n consumergroup=enrichment-v3\n topic=events.raw\n partition=11\n severity=warning\nannotations:\n summary=consumer lag 1.2M and climbing on partition 11 only\n runbook=https://wiki/int/kafka-lag\nvalue: 1214883\n\nother 23 partitions were at basically zero lag the whole time. rebalance count didn't change. what makes ONE partition fall behind like that","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"what happens to in-flight requests when we scale down? read the shutdown path and tell me if we actually drain","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"explain the diff between our two dockerfiles, dev and prod, i can't tell which differences are intentional","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"sanity check my understanding of the batching in the embedding service before i build on it — where does a request wait, and what's the worst case latency for a single-item request","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"we need an internal doc explaining the difference between our three environments and which one is safe to break. nobody knows and people keep asking in slack","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"summarize the design tradeoffs already captured in the comments of consensus.rs into a proper doc — i'd rather have it in one place than scattered across 900 lines","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"sanity check my understanding of the batching in the embedding service before i build on it — where does a request wait, and what's the worst case latency for a single-item request","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"we need an internal doc explaining the difference between our three environments and which one is safe to break. nobody knows and people keep asking in slack","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"summarize the design tradeoffs already captured in the comments of consensus.rs into a proper doc — i'd rather have it in one place than scattered across 900 lines","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"plan the move to server components and then convert the marketing pages as the first batch","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"figure out why the dedupe is dropping legit rows and once you know, write the ticket update explaining it","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"finish it up","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"thinking about our on-call load. 60% of pages are the same three alerts and none of them are actionable. i want a plan to fix the alerting itself, not just tune thresholds","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"how would you structure a plugin api for the editor? third parties, sandboxed, versioned, and we don't want to be stuck supporting whatever we ship forever. write the proposal","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"milestones for the postgres 14 -> 17 upgrade, logical replication, zero downtime, we have 4TB and one maintenance window a month","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"milestones for the postgres 14 -> 17 upgrade, logical replication, zero downtime, we have 4TB and one maintenance window a month","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"oauth device flow for the cli so people on headless boxes can log in. poll interval respected, and store the token in the os keyring not a dotfile","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"bloom filter in front of the object existence check, tune for 1% fp at 50M keys, rebuilt nightly","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the swagger page documents a `fields` query param for sparse fieldsets on every resource. that param does nothing. implement it for real, at least on users and projects","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"the swagger page documents a `fields` query param for sparse fieldsets on every resource. that param does nothing. implement it for real, at least on users and projects","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"diff viewer component — side by side, syntax highlighting, collapsible unchanged regions, line links. it's the last big thing before we can dogfood","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the tab order on the invite modal is chaos and the close button isn't reachable by keyboard at all","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"put a subtle divider between the list sections, right now they run together","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"the retention env var says RETENTION_DAYS but the code reads RETAIN_DAYS, align them","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"swap the deprecated `substr` calls for `slice` in the two spots eslint flags","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"the tab order on the invite modal is chaos and the close button isn't reachable by keyboard at all","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"put a subtle divider between the list sections, right now they run together","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"the retention env var says RETENTION_DAYS but the code reads RETAIN_DAYS, align them","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"swap the deprecated `substr` calls for `slice` in the two spots eslint flags","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"cache-control on the static assets is 300s, make it a year with the hashed filenames","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"our error types are strings compared with ==. introduce a proper error enum and update every comparison, same control flow though","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"move the shared types out of the api package into a types package so the frontend stops importing server code","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"collapse UserService and AccountService, they're the same concept split by an old naming argument. keep the public methods that are actually called","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"move the shared types out of the api package into a types package so the frontend stops importing server code","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"collapse UserService and AccountService, they're the same concept split by an old naming argument. keep the public methods that are actually called","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"some uploads finish but the file is 0 bytes. maybe 1 in 300. no error anywhere, the presigned put returns 200","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"xcodebuild fails only on CI:\n\n❌ /Users/runner/work/app/Sources/Sync/SyncEngine.swift:212:34: error: sending 'self.pendingOps' risks causing data races\n 212 | await withTaskGroup { group in\n 213 | for op in pendingOps {\n | `- note: sending task-isolated 'self.pendingOps' to nonisolated callee risks causing data races\n\n❌ /Users/runner/work/app/Sources/Sync/SyncEngine.swift:240:9: error: main actor-isolated property 'lastSyncedAt' can not be mutated from a nonisolated context\n\n** BUILD FAILED **\n\nThe following build commands failed:\n\tSwiftCompile normal arm64 Compiling SyncEngine.swift\n(1 failure)\n\nlocal xcode builds clean, same swift version supposedly. what's different","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"scroll position jumps to the top when the list refetches, but only sometimes, and only in the embedded webview","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"code review on the branch — mostly want your eyes on the transaction boundaries in the transfer handler","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"why do we set both `SameSite=Lax` and check the origin header? one of those seems redundant, is it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"trace what happens end to end when someone clicks 'export' — i want every hop, including the lambda i keep forgetting about","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"api reference page for the rust crate — module overview, the three main entry points, and a worked example that compiles","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"scroll position jumps to the top when the list refetches, but only sometimes, and only in the embedded webview","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"code review on the branch — mostly want your eyes on the transaction boundaries in the transfer handler","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"why do we set both `SameSite=Lax` and check the origin header? one of those seems redundant, is it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"trace what happens end to end when someone clicks 'export' — i want every hop, including the lambda i keep forgetting about","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"api reference page for the rust crate — module overview, the three main entry points, and a worked example that compiles","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"release notes for the desktop app 5.2, and please mention the sparkle update fix prominently, people have been complaining","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"commit messages for these 6 commits i'm about to rebase, they all say 'wip'","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"ok so","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"commit messages for these 6 commits i'm about to rebase, they all say 'wip'","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"wir müssen die Suche von Elasticsearch auf Typesense migrieren. schreib mir einen Migrationsplan mit Zwischenschritten, wir können nicht alles auf einmal umstellen","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"de"} {"prompt":"design doc for background sync on the ios app — what we sync, when, how we handle the 30 second bg task budget, and conflict resolution","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"we have three services that each keep their own copy of the org hierarchy and they disagree. i want a strategy, not a patch","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"csv -> parquet converter cli in rust, streaming, schema inference with an override flag, progress bar to stderr","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"we have three services that each keep their own copy of the org hierarchy and they disagree. i want a strategy, not a patch","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"csv -> parquet converter cli in rust, streaming, schema inference with an override flag, progress bar to stderr","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"audit trail on every write to the settings table — who, when, before and after, using a trigger so nobody can bypass it from the app","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"graphql subscription for build status, redis pubsub behind it, and clients that reconnect should get the current state immediately not just future events","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"sortable columns on the results table — click to sort, shift click for secondary, and the sort should persist in the url","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"iPad layout: the split view collapses to a single column when it shouldn't, and the detail pane loses its scroll position on rotation","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"focus ring is invisible on our brand blue buttons, needs an offset outline that works on both","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"add `--json` to the status command, same data, machine readable","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"iPad layout: the split view collapses to a single column when it shouldn't, and the detail pane loses its scroll position on rotation","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"focus ring is invisible on our brand blue buttons, needs an offset outline that works on both","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"add `--json` to the status command, same data, machine readable","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"the copyright year in the footer is 2024","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"set the k8s cpu request on the api deployment to 500m, it's currently unset and the scheduler is packing them badly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"set the k8s cpu request on the api deployment to 500m, it's currently unset and the scheduler is packing them badly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"the ViewController is doing layout, networking, and analytics. break it apart following the pattern in the newer screens. no visual or behavioral change, screenshots should be identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"we have `getUser`, `fetchUser`, `loadUser` and `userById` and they all do the same thing with different caching. pick one, migrate everything, delete the rest","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"we have `getUser`, `fetchUser`, `loadUser` and `userById` and they all do the same thing with different caching. pick one, migrate everything, delete the rest","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"invert the dependency between the parser and the diagnostics collector so the parser stops knowing about our error formatting","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"customers on the enterprise plan report the export button does nothing. no js errors in their console, works for every account i test with","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"esp32 reboots every ~40 minutes, watchdog i assume, but the logs just stop:\n\nI (2412088) mqtt: publishing telemetry seq=4409 len=212\nI (2412094) mqtt: publish ok\nI (2417088) sensor: read ok t=22.4 h=41.2\nI (2422088) mqtt: publishing telemetry seq=4410 len=212\nRST:0x8 (TG1WDT_SYS_RST),boot:0x13 (SPI_FAST_FLASH_BOOT)\nconfigsip: 0, SPIWP:0xee\nload:0x3fff0030,len:4832\nentry 0x400806a8\nI (31) boot: ESP-IDF v5.2.1 2nd stage bootloader\n\nheap looks stable in the logs before it goes, ~84k free the whole time. TG1WDT is the task watchdog on timer group 1 right? nothing i wrote uses that timer directly","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"il y a une fuite mémoire quelque part dans le worker d'images, la RSS monte jusqu'à l'OOM en 6h. pas de fuite évidente côté go pprof","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"fr"} -{"prompt":"is this migration safe to run during business hours","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"compare the two approaches sitting in the repo for the pdf renderer — the puppeteer one and the typst one — and tell me which i should keep","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"esp32 reboots every ~40 minutes, watchdog i assume, but the logs just stop:\n\nI (2412088) mqtt: publishing telemetry seq=4409 len=212\nI (2412094) mqtt: publish ok\nI (2417088) sensor: read ok t=22.4 h=41.2\nI (2422088) mqtt: publishing telemetry seq=4410 len=212\nRST:0x8 (TG1WDT_SYS_RST),boot:0x13 (SPI_FAST_FLASH_BOOT)\nconfigsip: 0, SPIWP:0xee\nload:0x3fff0030,len:4832\nentry 0x400806a8\nI (31) boot: ESP-IDF v5.2.1 2nd stage bootloader\n\nheap looks stable in the logs before it goes, ~84k free the whole time. TG1WDT is the task watchdog on timer group 1 right? nothing i wrote uses that timer directly","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"il y a une fuite mémoire quelque part dans le worker d'images, la RSS monte jusqu'à l'OOM en 6h. pas de fuite évidente côté go pprof","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"fr"} +{"prompt":"is this migration safe to run during business hours","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"compare the two approaches sitting in the repo for the pdf renderer — the puppeteer one and the typst one — and tell me which i should keep","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"read scripts/deploy.sh line by line and tell me what it does if the health check never passes","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"write the doc comments for our public swift package api, docc style, with a short discussion section on each type explaining when you'd use it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"write the doc comments for our public swift package api, docc style, with a short discussion section on each type explaining when you'd use it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"internal announcement post about the new deploy process. what changed, what people need to do differently, keep it under 300 words","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"translate the onboarding emails to ja, they're in emails/onboarding/*.mjml, keep the liquid tags intact","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"translate the onboarding emails to ja, they're in emails/onboarding/*.mjml, keep the liquid tags intact","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"design the multi-region failover and then implement the health check propagation part of it","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"rename the Tenant model to Workspace everywhere and update the docs that reference it","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"handle it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"i keep going back and forth on whether the sync engine should be crdt based or just server-authoritative with a merge ui. write up both, be opinionated at the end","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"rename the Tenant model to Workspace everywhere and update the docs that reference it","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"i keep going back and forth on whether the sync engine should be crdt based or just server-authoritative with a merge ui. write up both, be opinionated at the end","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"what's the migration path from our current session cookies to passkeys, with a period where both work","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"outline the test strategy for the payment integration — what's unit, what hits their sandbox, what we record and replay","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"implement optimistic concurrency on the document update endpoint, version column, 409 with the current version on conflict","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"implement optimistic concurrency on the document update endpoint, version column, 409 with the current version on conflict","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"connection pooling for the mysql driver in our go service, plus a circuit breaker that trips on repeated timeouts and half-opens after 30s","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"s3 multipart upload with resume from a local manifest, 8mb parts, 4 in flight","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"build the comparison table for the pricing page, 3 tiers, feature rows with checkmarks and tooltips, sticky header when you scroll past it, and it has to be readable on a phone","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"custom shader for the water surface, cheap — mobile targets. gerstner waves and a fresnel-ish edge foam","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"hide the beta ribbon on the dashboard, we launched","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"content-security-policy is missing frame-ancestors, add 'none'","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"the seed script inserts 10 users, make it 1000 so the pagination is actually exercised locally","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"s3 multipart upload with resume from a local manifest, 8mb parts, 4 in flight","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"build the comparison table for the pricing page, 3 tiers, feature rows with checkmarks and tooltips, sticky header when you scroll past it, and it has to be readable on a phone","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"custom shader for the water surface, cheap — mobile targets. gerstner waves and a fresnel-ish edge foam","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"hide the beta ribbon on the dashboard, we launched","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"content-security-policy is missing frame-ancestors, add 'none'","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"the seed script inserts 10 users, make it 1000 so the pagination is actually exercised locally","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"increase the sqs visibility timeout to 5 min, the handler takes longer than 30s now","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"the test suite has 40 helpers that build fixtures inline. introduce factories, port the tests, same assertions","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the test suite has 40 helpers that build fixtures inline. introduce factories, port the tests, same assertions","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"our redux slices reach into each other's state directly. put selectors at the boundaries so we can move things later. behavior identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"s/AcmeCorpInternalHttpClientWrapper/HttpClient/g basically, but do it properly including the file names and the DI registration","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"two of our three api pods serve stale feature flags after a config push. the third is fine. same image, same env","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"s/AcmeCorpInternalHttpClientWrapper/HttpClient/g basically, but do it properly including the file names and the DI registration","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"two of our three api pods serve stale feature flags after a config push. the third is fine. same image, same env","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"playwright test is flaking on the login step, i've pasted the trace summary:\n\n 1) [chromium] › auth/login.spec.ts:24:5 › logs in with email ─────────────────\n\n TimeoutError: locator.click: Timeout 15000ms exceeded.\n Call log:\n - waiting for getByRole('button', { name: 'Continue' })\n - locator resolved to \n - attempting click action\n - waiting for element to be enabled\n - element is not enabled - waiting...\n (repeated 74 times)\n\n at auth/login.spec.ts:31:52\n\n Retry #1 ─ passed (4.2s)\n\n 1 flaky, 89 passed (2.1m)\n\nthe button is disabled until the email validates, which is debounced 300ms. but 15 seconds?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} {"prompt":"requests from the mobile app get a 401 about 2% of the time right after a token refresh. clock skew maybe? not sure","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"how do we currently decide which shard a tenant lands on","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"the new caching decorator in api/decorators.py — is it going to cache per-user data across users? that's my worry, tell me if the key covers it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"how do we currently decide which shard a tenant lands on","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the new caching decorator in api/decorators.py — is it going to cache per-user data across users? that's my worry, tell me if the key covers it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"give me an honest assessment of the test coverage in the billing module. not the number, the actual risk","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"our http error responses aren't documented anywhere. write the reference — status, code string, when it happens, whether retrying helps","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"our http error responses aren't documented anywhere. write the reference — status, code string, when it happens, whether retrying helps","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"quickstart for the sdk, 5 minutes to first successful call, node and python","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"escreve a descrição do PR, tem uma mudança de comportamento no cálculo de imposto que precisa ficar bem clara","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"pt"} -{"prompt":"you know what needs doing","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"propose how we'd support self-hosted installs. licensing, telemetry opt-out, upgrade path, what we cut from cloud-only features. i need something i can show the exec team","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"we're at 900 e2e tests and 50 minutes of CI. plan how we get under 15 without deleting coverage","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"sketch out an api design for bulk operations. i keep wanting to just add /bulk endpoints per resource but that feels wrong","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"we're at 900 e2e tests and 50 minutes of CI. plan how we get under 15 without deleting coverage","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"sketch out an api design for bulk operations. i keep wanting to just add /bulk endpoints per resource but that feels wrong","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"server-sent events endpoint for the activity feed, resumable with Last-Event-ID, heartbeat comment every 15s to keep proxies happy","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"write the migration + backfill to split the `name` column into given/family. 4M rows, chunked, and keep `name` as a generated column during the transition","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"add a `serve` command to the cli that hosts the built site with live reload, pick a free port if 3000 is taken","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"write the migration + backfill to split the `name` column into given/family. 4M rows, chunked, and keep `name` as a generated column during the transition","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"add a `serve` command to the cli that hosts the built site with live reload, pick a free port if 3000 is taken","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"photo grid with lazy loaded thumbnails, 3 across on phone, and tapping should zoom out of the tapped cell not cross-fade","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"our forms have no inline validation, everything blows up on submit. add field-level errors on blur across the signup flow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"bump the modal max-width to 640, the form is squeezed","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"our forms have no inline validation, everything blows up on submit. add field-level errors on blur across the signup flow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"bump the modal max-width to 640, the form is squeezed","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"we're logging the full request body including passwords on 400s. strip it, today","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"the rust edition in Cargo.toml is 2018, move to 2021 and fix the fallout","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"the rust edition in Cargo.toml is 2018, move to 2021 and fix the fallout","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} {"prompt":"the makefile's `test` target doesn't run the integration tests, add them","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"hoist the shared validation out of the three signup paths (web, invite accept, sso jit) into one function, same rules, same error messages","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"hoist the shared validation out of the three signup paths (web, invite accept, sso jit) into one function, same rules, same error messages","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"the python package has modules importing from __init__ which imports from them. straighten out the import graph without changing the public surface","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"our sql lives in string literals scattered through the handlers. move it to .sql files and generate the accessors, identical queries","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"one customer's webhooks stopped delivering three days ago. our logs say 200 from their endpoint, they say they never got them","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"cpu pegged at 100% on one core in the render thread, profiler blames a function that should be trivial","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"ansible run bombs partway through, hosts end up half configured which is the worst outcome:\n\nTASK [postgres : ensure replication slot exists] *******************************\nfatal: [db-03.prod]: FAILED! => {\"changed\": false, \"msg\": \"unable to connect to database: connection to server at \\\"10.4.1.22\\\", port 5432 failed: FATAL: remaining connection slots are reserved for non-replication superuser connections\"}\n\nTASK [postgres : reload config] ***********************************************\nskipping: [db-03.prod]\n\nTASK [pgbouncer : write userlist] *********************************************\nchanged: [db-01.prod]\nchanged: [db-02.prod]\n\nPLAY RECAP ********************************************************************\ndb-01.prod : ok=41 changed=6 unreachable=0 failed=0\ndb-02.prod : ok=41 changed=6 unreachable=0 failed=0\ndb-03.prod : ok=28 changed=3 unreachable=0 failed=1\n\nmax_connections is 400 and we were at maybe 190 when this ran","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"walk me through the lock ordering in the scheduler, i want to know if a deadlock is possible before i add another lock","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"these two functions look like they should be the same but return different things for empty input. which one is right?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"cpu pegged at 100% on one core in the render thread, profiler blames a function that should be trivial","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"ansible run bombs partway through, hosts end up half configured which is the worst outcome:\n\nTASK [postgres : ensure replication slot exists] *******************************\nfatal: [db-03.prod]: FAILED! => {\"changed\": false, \"msg\": \"unable to connect to database: connection to server at \\\"10.4.1.22\\\", port 5432 failed: FATAL: remaining connection slots are reserved for non-replication superuser connections\"}\n\nTASK [postgres : reload config] ***********************************************\nskipping: [db-03.prod]\n\nTASK [pgbouncer : write userlist] *********************************************\nchanged: [db-01.prod]\nchanged: [db-02.prod]\n\nPLAY RECAP ********************************************************************\ndb-01.prod : ok=41 changed=6 unreachable=0 failed=0\ndb-02.prod : ok=41 changed=6 unreachable=0 failed=0\ndb-03.prod : ok=28 changed=3 unreachable=0 failed=1\n\nmax_connections is 400 and we were at maybe 190 when this ran","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"walk me through the lock ordering in the scheduler, i want to know if a deadlock is possible before i add another lock","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"these two functions look like they should be the same but return different things for empty input. which one is right?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} {"prompt":"review the terraform plan diff before i apply, i'm nervous about the security group changes:\n\n # aws_security_group_rule.api_ingress will be destroyed\n - resource \"aws_security_group_rule\" \"api_ingress\" {\n - cidr_blocks = [\"10.0.0.0/8\"] -> null\n - from_port = 443 -> null\n - protocol = \"tcp\" -> null\n - security_group_id = \"sg-0a91f\" -> null\n - type = \"ingress\" -> null\n }\n\n # aws_security_group_rule.api_ingress_v2 will be created\n + resource \"aws_security_group_rule\" \"api_ingress_v2\" {\n + cidr_blocks = [\"0.0.0.0/0\"]\n + from_port = 443\n + protocol = \"tcp\"\n + security_group_id = \"sg-0a91f\"\n + type = \"ingress\"\n }\n\n # aws_lb_listener.https will be updated in-place\n ~ resource \"aws_lb_listener\" \"https\" {\n ~ ssl_policy = \"ELBSecurityPolicy-2016-08\" -> \"ELBSecurityPolicy-TLS13-1-2-2021-06\"\n }\n\nPlan: 1 to add, 1 to change, 1 to destroy.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} -{"prompt":"the graphql schema has no descriptions on anything. add them, field by field, and be accurate about nullability semantics","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"summarize this week's merged PRs into a short changelog for the team channel","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"write up the security disclosure policy for the repo, SECURITY.md, include the response time we're committing to","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the graphql schema has no descriptions on anything. add them, field by field, and be accurate about nullability semantics","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"summarize this week's merged PRs into a short changelog for the team channel","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"write up the security disclosure policy for the repo, SECURITY.md, include the response time we're committing to","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"figure out the plan for the search relevance work then knock out the tokenizer change first","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"explain what our rate limiter does today and then write the doc for it, we have neither","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} -{"prompt":"carry on with the widget stuff","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"我们要把日志系统从 Loki 换成 ClickHouse，先写个方案：成本、查询延迟、迁移期间双写怎么做","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"zh"} +{"prompt":"我们要把日志系统从 Loki 换成 ClickHouse，先写个方案：成本、查询延迟、迁移期间双写怎么做","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"zh"} {"prompt":"break down what it would take to support real-time collaboration on our forms builder. i want phases where each one ships something users notice","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"plan the api versioning scheme before we have customers, i don't want to be stuck","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"implement scim user provisioning, users and groups, patch semantics done properly because okta is strict about it","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"distributed lock helper over redis with a fencing token, and make the api hard to misuse — no way to hold it past the ttl silently","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the reference docs describe cursor pagination on /events with a `before` param. the handler only supports `after`. add `before`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"plan the api versioning scheme before we have customers, i don't want to be stuck","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"implement scim user provisioning, users and groups, patch semantics done properly because okta is strict about it","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"distributed lock helper over redis with a fencing token, and make the api hard to misuse — no way to hold it past the ttl silently","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the reference docs describe cursor pagination on /events with a `before` param. the handler only supports `after`. add `before`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} {"prompt":"command palette needs a recent-files section and file icons by extension. match the visual density of the sidebar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the swiftui list scrolls like garbage with 2000 rows, rows have async images. make it smooth","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"the swiftui list scrolls like garbage with 2000 rows, rows have async images. make it smooth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"onboarding checklist card on the dashboard — 4 steps, progress ring, collapses once complete, dismissible","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"trailing whitespace in the generated file breaks our lint, add a strip","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"the retry decorator doesn't retry on 429, add it to the retryable set","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"trailing whitespace in the generated file breaks our lint, add a strip","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"the retry decorator doesn't retry on 429, add it to the retryable set","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"pyproject requires-python says >=3.9 but we use match statements, so >=3.10","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"our components take 14 props each because we kept adding variants. introduce composition — slots instead of booleans — and migrate the call sites without changing what renders","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"move everything under src/util into named modules, util is a graveyard. no behavior change, keep a shim for one release","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the emailer takes 9 positional args. make it a struct/options object, update the 30 call sites","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"move everything under src/util into named modules, util is a graveyard. no behavior change, keep a shim for one release","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the emailer takes 9 positional args. make it a struct/options object, update the 30 call sites","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"since the node 22 upgrade our streaming responses get truncated at exactly 65536 bytes sometimes. only through the cdn, direct to origin is fine","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"the numbers in the finance report are off by a few cents for about 1 in 200 invoices and finance is not happy","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"dbt run failed overnight, here's the tail:\n\n05:12:44 1 of 84 START sql incremental model analytics.fct_sessions ..... [RUN]\n05:14:02 1 of 84 ERROR creating sql incremental model analytics.fct_sessions [ERROR in 78.1s]\n05:14:02 Database Error in model fct_sessions (models/marts/fct_sessions.sql)\n05:14:02 Cannot insert a NULL value into column: 'session_key' in table 'FCT_SESSIONS'\n05:14:02 compiled Code at target/run/marts/fct_sessions.sql\n05:14:09 16 of 84 SKIP relation analytics.fct_engagement ................ [SKIP]\n05:14:09 Done. PASS=61 WARN=0 ERROR=1 SKIP=22 TOTAL=84\n\nsession_key is a surrogate key from dbt_utils.generate_surrogate_key over (user_id, session_start). so one of those is null now, which shouldn't be possible upstream","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"does our soft delete actually prevent deleted records from showing up in search? i see the filter in the query builder but not in the reindex job","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"what's the blast radius if the config service is down","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"dbt run failed overnight, here's the tail:\n\n05:12:44 1 of 84 START sql incremental model analytics.fct_sessions ..... [RUN]\n05:14:02 1 of 84 ERROR creating sql incremental model analytics.fct_sessions [ERROR in 78.1s]\n05:14:02 Database Error in model fct_sessions (models/marts/fct_sessions.sql)\n05:14:02 Cannot insert a NULL value into column: 'session_key' in table 'FCT_SESSIONS'\n05:14:02 compiled Code at target/run/marts/fct_sessions.sql\n05:14:09 16 of 84 SKIP relation analytics.fct_engagement ................ [SKIP]\n05:14:09 Done. PASS=61 WARN=0 ERROR=1 SKIP=22 TOTAL=84\n\nsession_key is a surrogate key from dbt_utils.generate_surrogate_key over (user_id, session_start). so one of those is null now, which shouldn't be possible upstream","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"does our soft delete actually prevent deleted records from showing up in search? i see the filter in the query builder but not in the reindex job","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"what's the blast radius if the config service is down","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"read through the new contributor's PR and give me a review i can paste, be kind but thorough, they're a first timer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"changelog + upgrade notes for the breaking change in the config format. include a before/after yaml","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"explain the caching headers we set, in prose, for the docs site's performance page","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"explain the caching headers we set, in prose, for the docs site's performance page","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"the architecture diagram in the wiki is 2 years stale. write an updated description of the system, i'll draw from that","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"nope","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"- new AppIntent for \"start a focus session\"\n- needs to work from spotlight and shortcuts\n- parameter for duration, default 25m\n- return a snippet view showing the timer\n- and it should deep link into the app if you tap it\n\nswiftui, ios 18 target","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the menu bar extra should show a live count and a popover with the last 5 items, plus a preference for launch at login","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"sqlite is fine for now but at some point we need real concurrency. write up when we'd have to move, to what, and what our schema does that would make it painful","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"- new AppIntent for \"start a focus session\"\n- needs to work from spotlight and shortcuts\n- parameter for duration, default 25m\n- return a snippet view showing the timer\n- and it should deep link into the app if you tap it\n\nswiftui, ios 18 target","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"the menu bar extra should show a live count and a popover with the last 5 items, plus a preference for launch at login","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"sqlite is fine for now but at some point we need real concurrency. write up when we'd have to move, to what, and what our schema does that would make it painful","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} {"prompt":"shell completions for bash zsh and fish, generated from the command tree not hand written","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"so the tricky part is that `deploy --watch` needs to keep streaming logs while also handling ctrl-c cleanly and not leaving the remote build orphaned... anyway implement it","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"half our funcs return (T, error) and half return a custom Result. unify on the idiomatic go one, no behavior change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"rename --dir to --path but keep --dir working with a deprecation warning","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"index bloat on the audit table, 40gb of index on 12gb of data. what do we do about it and in what order","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"why does EXPLAIN say rows=1 when there are clearly 40k matching","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"walk me through what our vacuum settings actually mean for the events table, autovacuum_vacuum_scale_factor is 0.01 and i don't remember why","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"man page for the cli. every flag, exit codes, three examples at the bottom, standard troff sections","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"half our funcs return (T, error) and half return a custom Result. unify on the idiomatic go one, no behavior change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"rename --dir to --path but keep --dir working with a deprecation warning","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"index bloat on the audit table, 40gb of index on 12gb of data. what do we do about it and in what order","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"why does EXPLAIN say rows=1 when there are clearly 40k matching","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"walk me through what our vacuum settings actually mean for the events table, autovacuum_vacuum_scale_factor is 0.01 and i don't remember why","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"man page for the cli. every flag, exit codes, three examples at the bottom, standard troff sections","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"the Info.plist is missing NSMicrophoneUsageDescription and the app store rejected us","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"our Core Data stack, the CloudKit sync, and the view models are all tangled through NSManagedObject subclasses in the views. put a domain model layer in between. the ui must behave exactly the same, including the animations on insert","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"keyboard shortcuts in the mac app: cmd+shift+n new window, cmd+opt+arrows to move between panes, and they need to show in the menu","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"keyboard shortcuts in the mac app: cmd+shift+n new window, cmd+opt+arrows to move between panes, and they need to show in the menu","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"table has 80M rows and no partitioning. plan the move to monthly partitions with no downtime, including how we handle the existing indexes and the fk from line_items","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"postgres advisory locks vs a lock table for our job claiming — which do we already use, and where. just tell me what's there","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"the app hangs when you open the third window, spindump attached mentally: everything's waiting on a main-thread dispatch that never returns. this started when i added the shared ModelContainer","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"wrong results from the group by when a tenant has no rows in the date range — we get a row with count 0 for the WRONG tenant sometimes. i've read the query 20 times","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"postgres advisory locks vs a lock table for our job claiming — which do we already use, and where. just tell me what's there","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the app hangs when you open the third window, spindump attached mentally: everything's waiting on a main-thread dispatch that never returns. this started when i added the shared ModelContainer","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"wrong results from the group by when a tenant has no rows in the date range — we get a row with count 0 for the WRONG tenant sometimes. i've read the query 20 times","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"put together the docs for our sql style guide — cte naming, when to use lateral joins, why we ban select *","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"extract the argument parsing out of main.go, it's 400 lines and impossible to test. same flags, same help text byte for byte","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"extract the argument parsing out of main.go, it's 400 lines and impossible to test. same flags, same help text byte for byte","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"sheet presentation detents, medium and large, and the drag indicator should be hidden when it's at large","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"the --verbose flag prints to stdout, should be stderr","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"review the schema in db/schema.sql and tell me where we're going to regret our choices in a year","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"write the tutorial for building a first plugin, end to end, someone should have a working thing in 20 minutes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"wrap it up","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"the --verbose flag prints to stdout, should be stderr","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"review the schema in db/schema.sql and tell me where we're going to regret our choices in a year","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"write the tutorial for building a first plugin, end to end, someone should have a working thing in 20 minutes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"goal: cut cold start on the lambda from 2.4s to under 500ms\nconstraints: python, we need pandas (yes really), and we can't move to a container image this quarter\nwant: a plan with the options ranked by effort vs payoff, and tell me which ones are dead ends","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"presigned upload flow for user avatars — validate content type server side after the upload, reject anything that isn't actually an image, and generate the 3 sizes","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"presigned upload flow for user avatars — validate content type server side after the upload, reject anything that isn't actually an image, and generate the 3 sizes","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"notification center in the web app: unread dot, mark all read, grouped by day, infinite scroll, and it should update live over the existing socket","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the ttl on the session cache should be 24h not 7d","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"we call it `slug` in the db, `handle` in the api, and `username` in the ui. pick `handle`, make it consistent through all three layers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"we call it `slug` in the db, `handle` in the api, and `username` in the ui. pick `handle`, make it consistent through all three layers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"intermittent 'database is locked' from sqlite in the desktop app. WAL is on, one writer, i thought that was supposed to be enough","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"is there any way a user can end up with two active subscriptions? read the checkout + webhook paths and tell me","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"our api guide says rate limits are per-key. they're per-ip in the code. update the guide and the error message copy to match reality","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"wondering if we should just... ok, question: how does the retry queue know not to reprocess an event that a different worker already handled","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"unread badge sync between the widget and the app is off by one after you read something in the widget","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"implement soft rate limiting on the graphql endpoint by query complexity, not request count. reject over 1000 points with a useful message","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"empty states for all six list screens, consistent illustration + copy pattern, and each one needs a different primary action","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"is there any way a user can end up with two active subscriptions? read the checkout + webhook paths and tell me","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"our api guide says rate limits are per-key. they're per-ip in the code. update the guide and the error message copy to match reality","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"wondering if we should just... ok, question: how does the retry queue know not to reprocess an event that a different worker already handled","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"unread badge sync between the widget and the app is off by one after you read something in the widget","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"implement soft rate limiting on the graphql endpoint by query complexity, not request count. reject over 1000 points with a useful message","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"empty states for all six list screens, consistent illustration + copy pattern, and each one needs a different primary action","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"bump the sdk to 2.14.0 and see if anything breaks","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"sort out the layering in internal/ — right now the store imports the handler package for a type, which is backwards. move the type, nothing else changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"sort out the layering in internal/ — right now the store imports the handler package for a type, which is backwards. move the type, nothing else changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"roadmap for the offline-first rewrite of the notes app. three months, two devs, and we can't break existing users' data","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"clicking a search result opens the wrong document about 5% of the time, and i can't reproduce it locally at all","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"what's actually different between our staging and prod postgres configs and does any of it matter for query plans","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"notes for the app review submission — what changed, what to test, and the demo account credentials placeholder","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"here's the failing output, i think it's a one line change somewhere in the formatter:\n\n$ acmectl fmt --check config/\nconfig/prod.yaml\n--- expected\n+++ actual\n@@ -12,7 +12,7 @@\n replicas: 3\n resources:\n limits:\n- memory: \"2Gi\"\n+ memory: 2Gi\n requests:\n- memory: \"1Gi\"\n+ memory: 1Gi\n \n1 file would be reformatted, 22 files already formatted\nexit status 1\n\nour formatter is stripping the quotes off values that look like numbers-with-suffixes, which k8s then reads differently. it should leave quoted scalars alone","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} +{"prompt":"clicking a search result opens the wrong document about 5% of the time, and i can't reproduce it locally at all","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"what's actually different between our staging and prod postgres configs and does any of it matter for query plans","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"notes for the app review submission — what changed, what to test, and the demo account credentials placeholder","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"here's the failing output, i think it's a one line change somewhere in the formatter:\n\n$ acmectl fmt --check config/\nconfig/prod.yaml\n--- expected\n+++ actual\n@@ -12,7 +12,7 @@\n replicas: 3\n resources:\n limits:\n- memory: \"2Gi\"\n+ memory: 2Gi\n requests:\n- memory: \"1Gi\"\n+ memory: 1Gi\n \n1 file would be reformatted, 22 files already formatted\nexit status 1\n\nour formatter is stripping the quotes off values that look like numbers-with-suffixes, which k8s then reads differently. it should leave quoted scalars alone","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"pasted-context","lang":"en"} {"prompt":"figure out the plan for encrypting the notes at rest with a user passphrase, then implement the keychain part","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"tidy the SettingsView hierarchy and while you're in there fix the toggle that doesn't persist","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} -{"prompt":"one more pass on the importer","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"tidy the SettingsView hierarchy and while you're in there fix the toggle that doesn't persist","purpose":"refactor","secondary":"debugging","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} {"prompt":"batch job to recompute the denormalized counters nightly, and a --dry-run that reports drift without writing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"make the drag and drop between kanban columns work on touch, currently mouse only","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"make the drag and drop between kanban columns work on touch, currently mouse only","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"el índice unique en (email) debería ser en (lower(email)), tenemos duplicados con mayúsculas","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"es"} -{"prompt":"explain to me, like i'm new here, how a request gets from the load balancer to a handler including the two middleware layers nobody documented","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"explain to me, like i'm new here, how a request gets from the load balancer to a handler including the two middleware layers nobody documented","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"consolidate the four date helper files into one module. there's overlap and at least two of them handle timezones differently — pick the correct behavior and note where callers change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"sequence the work for adding audit logs to every mutation. 60 mutations, and we want it enforced by types so a new one can't skip it","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"user says the app deleted their data. the sync log shows a tombstone we didn't send. i need to know how that's possible","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"user says the app deleted their data. the sync log shows a tombstone we didn't send. i need to know how that's possible","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"faq section for the docs based on the last 3 months of support tickets in support/exports/, group by theme","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"pagination on the admin users list, server side, 50 per page, keep the search query when you page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"the health check hits the db on every request, cache it for 5 seconds","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"read the new indexing strategy doc in docs/ and tell me whether it holds up against our actual query patterns in queries/","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"implement two-phase deletes for accounts — 30 day grace, anonymize immediately, purge after, and everything queryable during the grace period must exclude them","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"get rid of the `_v2` suffix on the four services that have it, nothing is on v1 anymore","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"our postgres connections spike to the max every morning at 9:02 and recover by 9:06. pooler is pgbouncer in transaction mode. what is doing that","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"write the docs for the new `--profile` flag including how it interacts with the env vars and the config file, precedence order especially","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"liquid glass sidebar treatment on macOS 26, but keep the legacy material path for older versions","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"pagination on the admin users list, server side, 50 per page, keep the search query when you page","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"the health check hits the db on every request, cache it for 5 seconds","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"read the new indexing strategy doc in docs/ and tell me whether it holds up against our actual query patterns in queries/","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"implement two-phase deletes for accounts — 30 day grace, anonymize immediately, purge after, and everything queryable during the grace period must exclude them","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"get rid of the `_v2` suffix on the four services that have it, nothing is on v1 anymore","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"our postgres connections spike to the max every morning at 9:02 and recover by 9:06. pooler is pgbouncer in transaction mode. what is doing that","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"write the docs for the new `--profile` flag including how it interacts with the env vars and the config file, precedence order especially","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"liquid glass sidebar treatment on macOS 26, but keep the legacy material path for older versions","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"design how we'd let customers bring their own s3 bucket for exports. credentials, validation, what happens when they revoke access mid-job","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"eslint --fix left 3 things it can't fix, take a look","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"does the transaction in `transferFunds` actually roll back the ledger entry if the notification send fails? trace it for me","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"here's the thing that's been driving me nuts:\n\n2026-07-28T14:22:09.114Z INFO [importer] batch 41 start rows=5000\n2026-07-28T14:22:09.882Z INFO [importer] batch 41 upserted=5000 skipped=0\n2026-07-28T14:22:10.004Z INFO [importer] batch 42 start rows=5000\n2026-07-28T14:22:41.229Z WARN [importer] batch 42 slow: 31.2s\n2026-07-28T14:22:41.230Z INFO [importer] batch 42 upserted=4998 skipped=2\n2026-07-28T14:22:41.401Z INFO [importer] batch 43 start rows=5000\n2026-07-28T14:22:42.109Z INFO [importer] batch 43 upserted=5000 skipped=0\n\nevery ~40th batch takes 30+ seconds and skips exactly 2 rows. the rest are sub-second. i've checked for hot keys, nothing obvious. skipped means the on-conflict did nothing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"write the section of the readme about local development on apple silicon, the docker-compose needs platform overrides and nobody knows that","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"eslint --fix left 3 things it can't fix, take a look","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"does the transaction in `transferFunds` actually roll back the ledger entry if the notification send fails? trace it for me","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"here's the thing that's been driving me nuts:\n\n2026-07-28T14:22:09.114Z INFO [importer] batch 41 start rows=5000\n2026-07-28T14:22:09.882Z INFO [importer] batch 41 upserted=5000 skipped=0\n2026-07-28T14:22:10.004Z INFO [importer] batch 42 start rows=5000\n2026-07-28T14:22:41.229Z WARN [importer] batch 42 slow: 31.2s\n2026-07-28T14:22:41.230Z INFO [importer] batch 42 upserted=4998 skipped=2\n2026-07-28T14:22:41.401Z INFO [importer] batch 43 start rows=5000\n2026-07-28T14:22:42.109Z INFO [importer] batch 43 upserted=5000 skipped=0\n\nevery ~40th batch takes 30+ seconds and skips exactly 2 rows. the rest are sub-second. i've checked for hot keys, nothing obvious. skipped means the on-conflict did nothing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"write the section of the readme about local development on apple silicon, the docker-compose needs platform overrides and nobody knows that","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"pull-to-refresh on the timeline plus a small 'new posts' pill that appears when items arrive while you're scrolled down","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"webhook signature verification, hmac sha256, constant time compare, tolerate 5 min clock skew, reject replays with a nonce cache","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"webhook signature verification, hmac sha256, constant time compare, tolerate 5 min clock skew, reject replays with a nonce cache","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"hoist the feature flag checks scattered through the render tree into one place at the route level. same features on/off for the same users","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"still broken","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"we need a position on how to do multi-tenancy in the new service: schema per tenant, row level, or separate databases. write the analysis with our actual constraints — 4000 tenants, biggest one is 40% of the data","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"grpc gateway in front of the internal services so the mobile team gets rest. codegen not hand written","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the video player controls should auto hide after 3s of no interaction, fade not snap, and stay up while the scrubber is being dragged","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"gitignore the .DS_Store files that snuck in and remove them from the index","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"the two implementations of exponential backoff (one in the http client, one in the queue consumer) should be one. the queue one is the correct one, it has jitter","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"requests hang for exactly 60s then succeed, roughly 1 in 50, only from our eu pods to the us database. dns? tcp? no idea","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"assess whether the new auth library we're considering (openfga) actually fits our permission model. read models/permissions.go first","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"the two implementations of exponential backoff (one in the http client, one in the queue consumer) should be one. the queue one is the correct one, it has jitter","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"requests hang for exactly 60s then succeed, roughly 1 in 50, only from our eu pods to the us database. dns? tcp? no idea","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"assess whether the new auth library we're considering (openfga) actually fits our permission model. read models/permissions.go first","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"release notes 2026.8, and there's a behavior change in how we resolve relative paths that people will hit, lead with that","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"wire up push notifications on android — fcm, topic per project, deep links into the right screen, and a quiet hours setting that's respected server side","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"tighten up the spacing in the compact table density, rows should be 32px not 40, and the checkbox column shouldn't shift","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"our github action uses ubuntu-20.04 which is retiring, move to 24.04","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"restructure the test suite into unit/integration/e2e directories with separate make targets. same tests, same assertions, nothing skipped","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"wire up push notifications on android — fcm, topic per project, deep links into the right screen, and a quiet hours setting that's respected server side","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"tighten up the spacing in the compact table density, rows should be 32px not 40, and the checkbox column shouldn't shift","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"our github action uses ubuntu-20.04 which is retiring, move to 24.04","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"restructure the test suite into unit/integration/e2e directories with separate make targets. same tests, same assertions, nothing skipped","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"audit our dependency tree for anything unmaintained or with a weird license, we're doing a compliance thing","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"guide for writing a custom exporter, aimed at people who've never touched our internals","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"memory on the ios app climbs 5mb per screen push and never comes back down. i suspect a retain cycle in the coordinator but instruments is showing me a wall of Malloc blocks and no obvious cycle","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"memory on the ios app climbs 5mb per screen push and never comes back down. i suspect a retain cycle in the coordinator but instruments is showing me a wall of Malloc blocks and no obvious cycle","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"phased plan for introducing typescript to the 60k line js codebase. allowJs, then per-directory strictness, i think? tell me the right order and where the pain is","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"just do whatever's next on the list","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"从 REST 迁移到 gRPC 的方案，先不写代码。我们有 12 个内部服务，客户端 SDK 是 TS 和 Kotlin","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"zh"} -{"prompt":"streaming json parser for the ndjson api responses so we don't hold 400mb in memory. rust, and it needs to handle a truncated final line","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"从 REST 迁移到 gRPC 的方案，先不写代码。我们有 12 个内部服务，客户端 SDK 是 TS 和 Kotlin","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"zh"} +{"prompt":"streaming json parser for the ndjson api responses so we don't hold 400mb in memory. rust, and it needs to handle a truncated final line","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"the settings sidebar in the electron app should collapse to icons under 900px wide, with tooltips","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"we log at info in the hot loop, drop that one to debug","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"the naming in the payments code is a mess — `txn`, `transaction`, `payment`, `charge` all mean the same thing in different files. standardize on `charge` since that's what the provider calls it","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"we get 'context canceled' errors on maybe 1% of writes and the data doesn't land, but the client sees a 200. that combination shouldn't be possible","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"is there a reason the worker pool size is 7? just want to know if that's meaningful before i change it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"the naming in the payments code is a mess — `txn`, `transaction`, `payment`, `charge` all mean the same thing in different files. standardize on `charge` since that's what the provider calls it","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"we get 'context canceled' errors on maybe 1% of writes and the data doesn't land, but the client sees a 200. that combination shouldn't be possible","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"is there a reason the worker pool size is 7? just want to know if that's meaningful before i change it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"prose for the pricing page's fine print about api limits, legal-adjacent but readable","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"csv import wizard: upload, column mapping ui with type detection, preview of the first 20 rows, then commit. the mapping step is the hard part visually","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"add etag support to the collection endpoints, weak etags off updated_at max, and honor if-none-match","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"our github workflows have the same 30 lines of setup copy pasted 9 times. make it a composite action","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"explain what the `--legacy-peer-deps` in our install step is papering over, and whether we can drop it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"documentation for the event schema — every event type, its fields, when it fires, and which are guaranteed vs best effort","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"add etag support to the collection endpoints, weak etags off updated_at max, and honor if-none-match","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"our github workflows have the same 30 lines of setup copy pasted 9 times. make it a composite action","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"explain what the `--legacy-peer-deps` in our install step is papering over, and whether we can drop it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"documentation for the event schema — every event type, its fields, when it fires, and which are guaranteed vs best effort","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"haptics on the dial control, subtle tick at each 5 degree stop, and it should respect the system haptics setting","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"plan the observability work: traces we don't have, the 4 golden signals per service, and what we do about the fact that half our services don't propagate context","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"chown in the entrypoint takes 90 seconds on a big volume, we should only do it if needed","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"server returns 500 on this payload and the error says 'invalid input syntax for type json' but the payload is valid json, i validated it three ways:\n\nPOST /v1/ingest\n{\n \"source\": \"crm\",\n \"records\": [\n {\"id\": \"a1\", \"attrs\": {\"note\": \"customer said \\\"maybe\\\" on renewal\"}},\n {\"id\": \"a2\", \"attrs\": {\"note\": \"path is C:\\\\Users\\\\temp\"}}\n ]\n}\n\nresponse:\n{\"error\":\"internal\",\"request_id\":\"req_8812f\"}\n\nserver log:\nERROR ingest: pq: invalid input syntax for type json\nDETAIL: Token \"Users\" is invalid.\nCONTEXT: JSON data, line 1: ...\"note\": \"path is C:\\Users...\n\nwe're passing the attrs through to a jsonb column. something is unescaping on the way","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"chown in the entrypoint takes 90 seconds on a big volume, we should only do it if needed","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"server returns 500 on this payload and the error says 'invalid input syntax for type json' but the payload is valid json, i validated it three ways:\n\nPOST /v1/ingest\n{\n \"source\": \"crm\",\n \"records\": [\n {\"id\": \"a1\", \"attrs\": {\"note\": \"customer said \\\"maybe\\\" on renewal\"}},\n {\"id\": \"a2\", \"attrs\": {\"note\": \"path is C:\\\\Users\\\\temp\"}}\n ]\n}\n\nresponse:\n{\"error\":\"internal\",\"request_id\":\"req_8812f\"}\n\nserver log:\nERROR ingest: pq: invalid input syntax for type json\nDETAIL: Token \"Users\" is invalid.\nCONTEXT: JSON data, line 1: ...\"note\": \"path is C:\\Users...\n\nwe're passing the attrs through to a jsonb column. something is unescaping on the way","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} {"prompt":"design the permissions model for shared folders and then build the check function, i'll do the endpoints","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"review the migration i wrote and if it's wrong just fix it","purpose":"review","secondary":"quickFix","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} -{"prompt":"eh, next thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"review the migration i wrote and if it's wrong just fix it","purpose":"review","secondary":"backendImpl","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} {"prompt":"i want an rfc for how we'd expose usage-based billing. metering, aggregation windows, what we do about clock skew across regions, and how a customer disputes a number","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"kafka consumer in go for the enrichment topic, manual commit after the sink succeeds, and a dlq topic for poison messages with the original headers preserved","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the dashboard needs a date range picker — presets plus custom, and it should sync to the url so people can share a view","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the dashboard needs a date range picker — presets plus custom, and it should sync to the url so people can share a view","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"sentry sample rate is 1.0 in prod, take it to 0.2","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"our api client is generated but we've hand edited it 6 times. regenerate properly and move the hand edits into wrapper functions so the next regen doesn't clobber them","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"our api client is generated but we've hand edited it 6 times. regenerate properly and move the hand edits into wrapper functions so the next regen doesn't clobber them","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"ci passes, prod breaks. the difference is the timezone on the runners i think but the failure is in the date math and i can't pin it down","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"read the pr and tell me if the new index is actually going to be used by the query it's meant for","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"postmortem writeup for the double-charge incident. timeline, root cause, what we're changing. i'll fill in the timestamps","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"toolbar buttons in the ipad app are too close to the edge in landscape, and the popover anchors to the wrong point","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"implement graceful shutdown properly — stop accepting, drain in flight with a 30s cap, close the db pool last, and log what got dropped","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the same regex for parsing our resource ids appears in 11 files. one function, one place, and add the tests that pin the edge cases we've hit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"faites-moi une revue de la couche de cache, surtout l'invalidation. pas de modifications, juste votre avis","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"fr"} -{"prompt":"readme badges are broken and the install instructions reference a package name we changed","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"read the pr and tell me if the new index is actually going to be used by the query it's meant for","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"postmortem writeup for the double-charge incident. timeline, root cause, what we're changing. i'll fill in the timestamps","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"toolbar buttons in the ipad app are too close to the edge in landscape, and the popover anchors to the wrong point","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"implement graceful shutdown properly — stop accepting, drain in flight with a 30s cap, close the db pool last, and log what got dropped","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the same regex for parsing our resource ids appears in 11 files. one function, one place, and add the tests that pin the edge cases we've hit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"faites-moi une revue de la couche de cache, surtout l'invalidation. pas de modifications, juste votre avis","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"fr"} +{"prompt":"readme badges are broken and the install instructions reference a package name we changed","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"spike out how we'd do a/b tests on the ios app without a server round trip per assignment","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the linter wants explicit return types on 40 exported functions, add them","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"the linter wants explicit return types on 40 exported functions, add them","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} {"prompt":"search returns nothing for queries with an apostrophe. works for everything else","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"give me the rundown on what happens during our blue/green deploy and where a request can get dropped, i'm writing a doc after this","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"give me the rundown on what happens during our blue/green deploy and where a request can get dropped, i'm writing a doc after this","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} {"prompt":"chart component for the metrics page, line + area, 3 series max, live updating without a full re-render, and a crosshair tooltip","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"no","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"we're going to need a plan for the data residency requirement. eu customers' data stays in eu, including backups and logs, and our current architecture assumes one region","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"implement the diff algorithm for our document sync — myers is probably fine, operating on paragraph blocks not characters","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"implement the diff algorithm for our document sync — myers is probably fine, operating on paragraph blocks not characters","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"avatar stack component, overlapping circles, +N overflow chip, tooltip listing everyone on hover","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"readonly db user has write grants, revoke them","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"our components import from '../../../lib/x' all over. set up path aliases and rewrite the imports, no other changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"kubectl logs show the pod handling the request but the trace has a gap of 4 seconds with no span. what could be eating that time","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain the difference between our `sync` and `reconcile` functions, they both seem to do the same thing and i don't want to delete the wrong one","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"docs page comparing our three storage backends for users choosing one — honest about tradeoffs, not marketing","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"our components import from '../../../lib/x' all over. set up path aliases and rewrite the imports, no other changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"kubectl logs show the pod handling the request but the trace has a gap of 4 seconds with no span. what could be eating that time","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain the difference between our `sync` and `reconcile` functions, they both seem to do the same thing and i don't want to delete the wrong one","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"docs page comparing our three storage backends for users choosing one — honest about tradeoffs, not marketing","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"in-app purchase flow with storekit 2, restore purchases, and handle the case where the receipt validates but our server doesn't know about the user yet","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the modal's backdrop click closes it even when a form is dirty, gate that behind a confirm","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"move the 12 constants duplicated between the client and the server into a shared package, single source","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"how bad is it that we're storing the api keys hashed with sha256 and no salt? i know it's not great, tell me how not-great and what the actual exposure is","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"our error messages say things like 'invalid input'. rewrite the user-facing copy for the 20 most common ones to say what to actually do","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"map out the steps to get our terraform out of one giant state file. 400 resources, and we can't have an outage during the moves","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the modal's backdrop click closes it even when a form is dirty, gate that behind a confirm","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"move the 12 constants duplicated between the client and the server into a shared package, single source","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"how bad is it that we're storing the api keys hashed with sha256 and no salt? i know it's not great, tell me how not-great and what the actual exposure is","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"our error messages say things like 'invalid input'. rewrite the user-facing copy for the 20 most common ones to say what to actually do","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"map out the steps to get our terraform out of one giant state file. 400 resources, and we can't have an outage during the moves","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"the go.sum has a stale entry after the replace directive, tidy it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"gh actions annotation from the failing job, this is blocking three PRs:\n\nError: The process '/usr/bin/git' failed with exit code 128\n ##[error]fatal: could not read Username for 'https://github.com': No such device or address\n at ExecState._setResult (/home/runner/work/_actions/actions/checkout/v4/dist/index.js:2417:25)\n at ExecState.CheckComplete (/home/runner/work/_actions/actions/checkout/v4/dist/index.js:2400:18)\n\nWarning: The `set-output` command is deprecated\nWarning: Node.js 16 actions are deprecated\n\nRun actions/cache@v4\n Cache not found for input keys: node-cache-Linux-x64-8f21a...\n\nit only fails on PRs from forks. worked last week. we did rotate a PAT on tuesday but that shouldn't matter for forks right","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} -{"prompt":"toast when a background upload finishes, tappable to jump to the file, and it shouldn't cover the tab bar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"build the reconciliation report: for every order in our db compare against the provider's settlement file, output the mismatches as csv with a reason code","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"toast when a background upload finishes, tappable to jump to the file, and it shouldn't cover the tab bar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"build the reconciliation report: for every order in our db compare against the provider's settlement file, output the mismatches as csv with a reason code","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"our validation lives in three layers and they disagree on what a valid slug is. pick the strictest, put it in one place, everything calls that","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"what do these two goroutines actually synchronize on, i can't tell if the channel or the mutex is doing the work here","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"adr for choosing sqlite over postgres for the desktop app's local store. i want the reasoning captured before people forget","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"plan for handling schema changes in the mobile app's local db when users skip 4 versions","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"dark mode in the ios app inverts the brand color in one place, ColorTheme.accent i think","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"app store connect rejected the build for a privacy manifest thing, i don't understand what it wants:\n\nITMS-91053: Missing API declaration - Your app's code in the \"AcmeNotes\" file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryUserDefaults. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, you must include a NSPrivacyAccessedAPITypes array in your app's privacy manifest.\n\nITMS-91061: Missing privacy manifest - Your app includes \"Frameworks/SentrySwift.framework/SentrySwift\", which is a third-party SDK that requires a privacy manifest.\n\nwe do have a PrivacyInfo.xcprivacy, i added it last release","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} -{"prompt":"explain how our session invalidation works on password change, and whether it covers the mobile refresh tokens","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"what do these two goroutines actually synchronize on, i can't tell if the channel or the mutex is doing the work here","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"adr for choosing sqlite over postgres for the desktop app's local store. i want the reasoning captured before people forget","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"plan for handling schema changes in the mobile app's local db when users skip 4 versions","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"dark mode in the ios app inverts the brand color in one place, ColorTheme.accent i think","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"app store connect rejected the build for a privacy manifest thing, i don't understand what it wants:\n\nITMS-91053: Missing API declaration - Your app's code in the \"AcmeNotes\" file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryUserDefaults. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, you must include a NSPrivacyAccessedAPITypes array in your app's privacy manifest.\n\nITMS-91061: Missing privacy manifest - Your app includes \"Frameworks/SentrySwift.framework/SentrySwift\", which is a third-party SDK that requires a privacy manifest.\n\nwe do have a PrivacyInfo.xcprivacy, i added it last release","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"explain how our session invalidation works on password change, and whether it covers the mobile refresh tokens","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"write the migration guide for the plugin api v2 and mark which v1 methods are gone versus renamed","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"settings screen on android: preference screens with categories, a slider for sync frequency, and the switch states have to survive process death","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"cursor based iterator over the s3 inventory manifest, python, lazily fetching pages, and resumable from a saved cursor","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"settings screen on android: preference screens with categories, a slider for sync frequency, and the switch states have to survive process death","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"cursor based iterator over the s3 inventory manifest, python, lazily fetching pages, and resumable from a saved cursor","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"sketch how we'd support undo across the whole editor. command pattern probably, but the tricky bit is collaborative edits landing in the middle of your undo stack","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"unwrap the double negative in shouldSkipValidation, it's `!isNotDisabled` and nobody can read it","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"requests to /reports time out at 30s for exactly one customer. their dataset isn't the biggest. i've run their query manually and it takes 400ms","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"put together the internal doc on how our feature flags work and who can flip what, then i want to make the ui match it","purpose":"writing","secondary":"frontendImpl","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} -{"prompt":"work out an approach for the batch export queue and then build the worker side","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"keep going where we left off on the sync engine","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"unwrap the double negative in shouldSkipValidation, it's `!isNotDisabled` and nobody can read it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"requests to /reports time out at 30s for exactly one customer. their dataset isn't the biggest. i've run their query manually and it takes 400ms","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"put together the internal doc on how our feature flags work and who can flip what, then i want to make the ui match it","purpose":"writing","secondary":"frontendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"work out an approach for the batch export queue and then build the worker side","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"ok stream of thought — we have four services that all need the org tree, one of them caches it for 5 min, one hits the db every request, one has a copy in redis that nobody refreshes. i don't want to patch this, i want the actual strategy for owning that data in one place. write it up","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"implement the tar-like archive format we specced, streaming write, checksums per entry, and a verify subcommand","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"implement the tar-like archive format we specced, streaming write, checksums per entry, and a verify subcommand","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"the file tree in the sidebar needs multi-select with shift and cmd, and a right click menu that respects the selection","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"the CORS preflight cache is 5s, bump to an hour","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"convert the class components in src/legacy to function components with hooks, one directory at a time, snapshots must not change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"duplicate notifications, two per event, started after we scaled the worker deployment to 2 replicas. i thought the queue handled that","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"is our idempotency actually idempotent if the first request is still in flight when the retry arrives","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"docs for the CLI's config file — every key, defaults, and which ones can be set by env var. table format","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"add prometheus metrics to the go service: request duration histogram by route, in flight gauge, and a counter for each error class","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the print stylesheet is nonexistent, invoices print with the nav bar and dark backgrounds","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"delete the commented out code in payments/legacy_gateway.py, it's been there since 2023","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"collapse our 5 environment config files into one with overlays, same effective values per env — diff them before and after to prove it","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"check the new websocket reconnect logic for me, specifically whether we can end up with two open sockets","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"is our idempotency actually idempotent if the first request is still in flight when the retry arrives","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"docs for the CLI's config file — every key, defaults, and which ones can be set by env var. table format","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"add prometheus metrics to the go service: request duration histogram by route, in flight gauge, and a counter for each error class","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the print stylesheet is nonexistent, invoices print with the nav bar and dark backgrounds","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"delete the commented out code in payments/legacy_gateway.py, it's been there since 2023","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"collapse our 5 environment config files into one with overlays, same effective values per env — diff them before and after to prove it","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"check the new websocket reconnect logic for me, specifically whether we can end up with two open sockets","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"we promised a status page. write the incident communication templates — investigating, identified, monitoring, resolved — with placeholders","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"outline the plan for supporting webhooks with customer-provided mTLS certs, including how we store and rotate them","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"one of our cron jobs runs twice on the last sunday in october. i'm pretty sure i know why but the fix isn't obvious to me","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"outline the plan for supporting webhooks with customer-provided mTLS certs, including how we store and rotate them","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"one of our cron jobs runs twice on the last sunday in october. i'm pretty sure i know why but the fix isn't obvious to me","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"swipe actions on the list rows — archive on left, delete on right with a confirm, and undo via a snackbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"das Feature-Flag `new_billing_ui` ist nur noch an einer Stelle relevant, räum die alten Verzweigungen weg ohne das Verhalten zu ändern","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"de"} -{"prompt":"so uh","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"das Feature-Flag `new_billing_ui` ist nur noch an einer Stelle relevant, räum die alten Verzweigungen weg ohne das Verhalten zu ändern","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"de"} {"prompt":"from the ticket queue, top priority:\n\n[BUG-4471] Scanner screen freezes on Samsung A54\nReported by 3 users, all A54 / One UI 6.1. Steps: open scanner, point at any barcode, hold ~5s. UI stops responding, no crash, no ANR dialog for another 10s.\nLogs from one user (attached, trimmed):\n W/CameraDevice: Camera 0 stream configuration changed while capture in progress\n I/AcmeScanner: analyzer frame drop count=412\n W/System: A resource failed to call release.\nWorks fine on Pixel 7, 8, and a Fold 5. We use CameraX 1.4.0 + MLKit barcode.\n\nno idea where to start with this one","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"bottom nav with 5 tabs and badges on two of them, jetpack navigation, and back should always land on the home tab not exit","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"bottom nav with 5 tabs and badges on two of them, jetpack navigation, and back should always land on the home tab not exit","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"drop the splash delay from 1200ms to 0","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"workmanager job to upload queued readings when the network comes back, exponential backoff, and it must not run on metered connections unless the user opted in","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"our compose screens each fetch their own data in a LaunchedEffect. move it all into the viewmodels with a proper state holder, same behavior on rotation and process death","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"lay out how we'd support ble firmware updates from the phone app. we have 4 hardware revisions in the field and two of them have a 64kb ota partition","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"read through the ble reconnect logic and tell me under what conditions we'd keep a stale gatt handle","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"read through the ble reconnect logic and tell me under what conditions we'd keep a stale gatt handle","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"hardware setup guide for the dev kit — flashing, serial console settings, jumper positions, and the gotcha about holding boot0","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"sensor reads drift upward over hours and reset after a power cycle. i've calibrated, it's not that","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"sensor reads drift upward over hours and reset after a power cycle. i've calibrated, it's not that","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"skeleton loaders on every route instead of the full-page spinner, use the shape of the actual content","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the input debounce is 150ms and it feels laggy, make it 50","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"is the i2c read in the interrupt handler safe? i inherited this and it makes me nervous but i can't point to a specific problem","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"server side rendering for the product pages, streaming, and the cart state can't flash empty on hydration","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the input debounce is 150ms and it feels laggy, make it 50","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"is the i2c read in the interrupt handler safe? i inherited this and it makes me nervous but i can't point to a specific problem","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"server side rendering for the product pages, streaming, and the cart state can't flash empty on hydration","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"milestones for shipping our design system as a package. 60 components in the app, maybe 25 are actually reusable","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"endpoint that accepts a batch of sensor readings, validates the device signature, and writes to timescale. 500 devices posting every 10s","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"extract the retry+chunking from the uploader into a reusable transport, the ble path and the wifi path both need it and currently duplicate it","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"endpoint that accepts a batch of sensor readings, validates the device signature, and writes to timescale. 500 devices posting every 10s","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"extract the retry+chunking from the uploader into a reusable transport, the ble path and the wifi path both need it and currently duplicate it","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"changelog for the firmware 1.8 release, and separate the customer-visible items from the internal ones","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"why does the app show a stale reading for a few seconds after you reconnect the device","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"the modal traps scroll on the body but not on ios safari, and the address bar collapse makes it worse","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"why does the app show a stale reading for a few seconds after you reconnect the device","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the modal traps scroll on the body but not on ios safari, and the address bar collapse makes it worse","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"kotlin: change the default page size constant from 20 to 50","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"what does the ring buffer in comms.c guarantee if the producer is an isr and the consumer is the main loop? i want to know before i add a second producer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"make the api reference for the device protocol readable — right now it's a spreadsheet of register addresses. prose plus tables, with the byte order stated explicitly because everyone gets it wrong","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"provision the staging fleet with terraform — 3 nodes, the mqtt broker, and a bastion. reuse the prod module with a smaller instance class","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"our compose theme has hardcoded colors in 30 files instead of using the theme. sweep them into tokens, identical rendering","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"just push it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"what does the ring buffer in comms.c guarantee if the producer is an isr and the consumer is the main loop? i want to know before i add a second producer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"make the api reference for the device protocol readable — right now it's a spreadsheet of register addresses. prose plus tables, with the byte order stated explicitly because everyone gets it wrong","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"provision the staging fleet with terraform — 3 nodes, the mqtt broker, and a bastion. reuse the prod module with a smaller instance class","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"our compose theme has hardcoded colors in 30 files instead of using the theme. sweep them into tokens, identical rendering","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"slack thread, need this sorted today:\n\n@dana: heads up the checkout page is throwing for anyone with a saved card from before march\n@marco: confirmed, i see it — TypeError: t.card.brand is undefined in PaymentMethodRow\n@dana: old records have `card_brand` at the top level, new ones nest under `card`\n@marco: so we changed the shape and never backfilled 😬\n@dana: it's like 8% of accounts. can we handle both shapes in the component for now and backfill after\n\nyeah let's do the component fix first","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} {"prompt":"design the offline queue for the android app properly. room-backed, ordering per entity, and a conflict policy i can explain to support","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"implement pkce oauth in the mobile app, custom scheme redirect, and refresh in the background before expiry not on 401","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the hero image causes a 400ms CLS on mobile, and lighthouse is yelling about it","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"typo in the analytics event name, 'chekout_started'. it's already in the warehouse so we need to keep emitting both for a bit","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"our vue components mix options api and composition api. move everything to composition, no template changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"battery drain complaints on android 15 only, our foreground service is the top consumer in the battery report but it's supposed to be idle most of the time","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"does the coroutine scope in our repository get cancelled when the viewmodel clears? i think so but i want confirmation from the code","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"implement pkce oauth in the mobile app, custom scheme redirect, and refresh in the background before expiry not on 401","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the hero image causes a 400ms CLS on mobile, and lighthouse is yelling about it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"typo in the analytics event name, 'chekout_started'. it's already in the warehouse so we need to keep emitting both for a bit","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"our vue components mix options api and composition api. move everything to composition, no template changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"battery drain complaints on android 15 only, our foreground service is the top consumer in the battery report but it's supposed to be idle most of the time","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"does the coroutine scope in our repository get cancelled when the viewmodel clears? i think so but i want confirmation from the code","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"write the play store listing copy and the what's new text for this release","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"plan out how we deprecate the v1 mobile api. 30% of installs are still on it and some of those devices will never update","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"plan out how we deprecate the v1 mobile api. 30% of installs are still on it and some of those devices will never update","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"rest endpoints for the device group CRUD, nested under org, with the permission checks matching the existing pattern in the fleet handlers","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"grid gap is 16 everywhere except the cards page where it's 12, unify on 16","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"esplain what happens if two devices claim the same serial number during provisioning, i want to know if we already handle it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"grid gap is 16 everywhere except the cards page where it's 12, unify on 16","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"esplain what happens if two devices claim the same serial number during provisioning, i want to know if we already handle it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} {"prompt":"flatten the nested conditionals in shouldShowUpsell, five levels deep, same truth table. write the tests first if that helps you prove it","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"internal wiki page: how our ota rollout works, the cohort percentages, and how to halt one","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"webview in the android app renders our chart at 2x and it's blurry on some devices but not others","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"infinite scroll on the feed with a proper loading sentinel, and it should stop hammering the api when the user is offline","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the mqtt keepalive should be 30s not 300, devices behind cgnat are getting dropped","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"sequence the accessibility fixes for the android app — talkback labels, touch target sizes, contrast. i want to know what's a day and what's a week","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"infinite scroll on the feed with a proper loading sentinel, and it should stop hammering the api when the user is offline","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the mqtt keepalive should be 30s not 300, devices behind cgnat are getting dropped","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"sequence the accessibility fixes for the android app — talkback labels, touch target sizes, contrast. i want to know what's a day and what's a week","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"implement device shadow / desired-state sync: server stores desired config, device reports actual, and we surface the delta","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"give the deprecation notice for the v1 api in the docs, plus the code changes to start returning the Sunset header","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} -{"prompt":"diagnose the freeze on the scanner screen and then write up what we tell the affected users","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"give the deprecation notice for the v1 api in the docs, plus the code changes to start returning the Sunset header","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"diagnose the freeze on the scanner screen and then write up what we tell the affected users","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"i need the strategy for our image pipeline. we serve 40M images a month off a single origin with no cdn, no responsive variants, and marketing keeps uploading 8MB pngs. what's the sequence of fixes and what do we get from each","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"image resize service, on the fly with a signed url so nobody can DOS us with arbitrary dimensions, cached at the edge","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"image resize service, on the fly with a signed url so nobody can DOS us with arbitrary dimensions, cached at the edge","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"responsive images with srcset across the marketing pages, and the art direction on the hero needs a picture element","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"swap the deprecated `` import for the new metadata export in the 6 pages that still use it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"our tailwind config has 40 custom colors that mostly duplicate each other. collapse to a real scale, update the classes, nothing should look different","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"swap the deprecated `` import for the new metadata export in the 6 pages that still use it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"our tailwind config has 40 custom colors that mostly duplicate each other. collapse to a real scale, update the classes, nothing should look different","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"images 404 in production but only for files uploaded in the last hour. after that they work. cdn cache? bucket replication? tell me","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"check whether our signed urls can be extended by a client just editing the expiry param","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"doc the image url format — the transform params, allowed ranges, what happens on an invalid combo","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"doc the image url format — the transform params, allowed ranges, what happens on an invalid combo","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"figure out the plan for moving our monolith's static assets to a proper build pipeline. it's currently sprockets and jquery in 2026","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"background removal endpoint that calls the ml service, queues if it's busy, and returns a job id the client polls","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"background removal endpoint that calls the ml service, queues if it's busy, and returns a job id the client polls","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"crop and rotate ui for uploaded photos, pinch to zoom, aspect ratio presets, and it needs to work with a mouse too","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"alt text on the 12 images in the marketing footer, they have none","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"the thumbnail generation code is copy pasted in the upload handler, the import job, and the admin backfill. one function, three callers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the thumbnail generation code is copy pasted in the upload handler, the import job, and the admin backfill. one function, three callers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"vite dev server is fine, prod build breaks on this and i can't tell what it's actually complaining about:\n\n✓ 1842 modules transformed.\nRollup failed to resolve import \"virtual:acme-icons\" from \"/src/components/IconButton.vue\".\nThis is most likely unintended because it can break your application at runtime.\nIf you do want to externalize this module explicitly add it to\nbuild.rollupOptions.external\n\nerror during build:\nError: [vite]: Rollup failed to resolve import\n at viteWarn (file:///app/node_modules/vite/dist/node/chunks/dep-Cc9c9V5r.js:52178:23)\n at onwarn (file:///app/node_modules/vite/dist/node/chunks/dep-Cc9c9V5r.js:52178:5)\n\nthe virtual module comes from our own plugin in plugins/icons.ts which definitely has a resolveId","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} -{"prompt":"how does our cdn decide what to cache — read the headers we set and the cdn config and tell me if they agree","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"how does our cdn decide what to cache — read the headers we set and the cdn config and tell me if they agree","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"a short guide for designers on how to export assets for us, what formats, naming, and where to drop them","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"we want the editor to support pasting images. plan the whole path — clipboard, temp storage, the placeholder while uploading, failure states","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"we want the editor to support pasting images. plan the whole path — clipboard, temp storage, the placeholder while uploading, failure states","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"wasm module for the client-side image decoding, rust, exposed through a tiny js wrapper","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"lightbox for the gallery, arrow key nav, escape closes, preload the next image, and it must not shift the page behind it","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"lightbox for the gallery, arrow key nav, escape closes, preload the next image, and it must not shift the page behind it","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"the og:image meta tag points at a deleted file","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"the api layer, the cache layer and the transform layer all reimplement 'is this a supported format'. pick one list, one function","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the api layer, the cache layer and the transform layer all reimplement 'is this a supported format'. pick one list, one function","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"uploads over 20mb fail silently on safari only. the request just never completes, no error event","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"is the exif stripping actually happening before we store the file, or after? privacy review is asking","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"explain our caching strategy in a doc for the team, we've never written it down and there are four layers","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"later","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"is the exif stripping actually happening before we store the file, or after? privacy review is asking","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"explain our caching strategy in a doc for the team, we've never written it down and there are four layers","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"sketch the architecture for our new events pipeline. requirements: 200k events/sec peak, exactly-once into the warehouse, replayable for 30 days, and the schema changes weekly. i want the doc to include what we're explicitly NOT solving","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"kinesis consumer with checkpointing in dynamo, handles resharding, and idempotent writes downstream","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the metrics explorer needs a query builder ui — dimension pickers, filter rows you can add and remove, and a live preview of the resulting chart","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the airflow dag start_date is a dynamic datetime.now(), that's the bug, fix it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"the metrics explorer needs a query builder ui — dimension pickers, filter rows you can add and remove, and a live preview of the resulting chart","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the airflow dag start_date is a dynamic datetime.now(), that's the bug, fix it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"our three notebooks and the prod job compute 'active user' differently. define it once in the dbt layer and have everything reference that","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the model's precision dropped from 0.91 to 0.72 in prod but the offline eval is unchanged. training data looks the same. help me find the skew","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"look at the feature pipeline and tell me if there's leakage — target is churn in the next 30 days and i think one of the aggregates peeks","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"model card for the churn classifier — data, metrics, known limitations, and the fairness slices we checked","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the model's precision dropped from 0.91 to 0.72 in prod but the offline eval is unchanged. training data looks the same. help me find the skew","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"look at the feature pipeline and tell me if there's leakage — target is churn in the next 30 days and i think one of the aggregates peeks","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"model card for the churn classifier — data, metrics, known limitations, and the fairness slices we checked","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"roadmap for getting a feature store in place. we have 40 features defined in sql across 6 repos","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"batch inference job, reads from bigquery, writes predictions back with a run id, and skips rows already scored for that model version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"confusion matrix component with a color scale and cell tooltips, and it should stay readable at 20 classes","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"seed the random state in the eval script, results move between runs","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"the preprocessing code exists twice — once in the training pipeline, once in the serving path — and they've diverged. make them literally the same code","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"training loss goes to nan around step 3000, only with bf16, only on the 8-gpu run. single gpu is fine","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"explain what the collate_fn is doing to variable length sequences here, i'm not sure the padding mask lines up","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"write the experiment writeup: hypothesis, setup, results table, and what we'd do next. numbers are in results/exp-114/","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"confusion matrix component with a color scale and cell tooltips, and it should stay readable at 20 classes","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"seed the random state in the eval script, results move between runs","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"the preprocessing code exists twice — once in the training pipeline, once in the serving path — and they've diverged. make them literally the same code","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"training loss goes to nan around step 3000, only with bf16, only on the 8-gpu run. single gpu is fine","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"explain what the collate_fn is doing to variable length sequences here, i'm not sure the padding mask lines up","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"write the experiment writeup: hypothesis, setup, results table, and what we'd do next. numbers are in results/exp-114/","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"plan the rag evaluation harness. golden set, retrieval metrics vs answer metrics, and how we keep it from rotting","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"vector index over the docs corpus with pgvector, hybrid search with the existing tsvector column, and reranking","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"chat ui with streaming tokens, stop button, and a copy-code affordance on code blocks","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the max_tokens in the summarize call is 256 and answers are getting cut, take it up","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"our prompt templates are f-strings scattered across 8 files. put them in one module with named templates, byte-identical output","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"explain the retry logic around the embedding api calls and whether we can double-charge ourselves on a timeout","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"make the readme for the eval repo actually usable, right now it says 'run make'","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the max_tokens in the summarize call is 256 and answers are getting cut, take it up","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"our prompt templates are f-strings scattered across 8 files. put them in one module with named templates, byte-identical output","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain the retry logic around the embedding api calls and whether we can double-charge ourselves on a timeout","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"make the readme for the eval repo actually usable, right now it says 'run make'","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"design the retrieval pipeline then build the chunker as the first piece","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"audit the sql in the analytics models for correctness and fix the obvious ones as you go","purpose":"review","secondary":"quickFix","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"hmm let's try something else","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"wie strukturieren wir die Migration von unserem Redis-basierten Job-System zu Temporal? Bitte einen Plan mit Phasen, wir haben 30 Job-Typen","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"de"} +{"prompt":"audit the sql in the analytics models for correctness and fix the obvious ones as you go","purpose":"review","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"wie strukturieren wir die Migration von unserem Redis-basierten Job-System zu Temporal? Bitte einen Plan mit Phasen, wir haben 30 Job-Typen","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"de"} {"prompt":"cron endpoint that rotates our api signing keys, keeps the previous one valid for 24h, and publishes the jwks","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"step indicator for the 5 step wizard, completed steps clickable, current one emphasized, and it collapses to 'Step 3 of 5' on narrow screens","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"step indicator for the 5 step wizard, completed steps clickable, current one emphasized, and it collapses to 'Step 3 of 5' on narrow screens","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"the dockerfile copies the whole repo before installing deps, flip the order so the layer caches","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"we have two http servers in the same binary for historical reasons. merge them onto one mux, same routes, same middlewares per route","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"we have two http servers in the same binary for historical reasons. merge them onto one mux, same routes, same middlewares per route","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"deploys succeed but the new version doesn't take effect for ~10 minutes. no rollout in the k8s events after the first one","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"how do we currently prevent a customer from reading another customer's uploads — is it the bucket prefix, the signed url, or an actual check","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"how do we currently prevent a customer from reading another customer's uploads — is it the bucket prefix, the signed url, or an actual check","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"write the on-call handbook section for the ingest service: what alerts exist, what each one means, first three things to check","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"long term plan for our test data. every team seeds their own and it's all inconsistent, and the e2e suite depends on a snapshot from 2024","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"implement the admin impersonation flow — audited, time boxed to an hour, and impossible for a non-admin to trigger even with a forged token","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"long term plan for our test data. every team seeds their own and it's all inconsistent, and the e2e suite depends on a snapshot from 2024","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"implement the admin impersonation flow — audited, time boxed to an hour, and impossible for a non-admin to trigger even with a forged token","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"banner component for maintenance windows, dismissible per session, and it should push the layout down not overlay","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"the favicon is the default vite one","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"the favicon is the default vite one","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} {"prompt":"our middleware chain is built by string keys in a map, which means order is nondeterministic across restarts. make it explicit and ordered, same effective chain as today","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"logs show the request finishing in 40ms but the client measures 2.3 seconds. consistently. where's the time going","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"tell me what this cron expression does and whether it accounts for dst","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"docs for the new sdk retry behavior — defaults, how to override, and the interaction with the server's retry-after","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"logs show the request finishing in 40ms but the client measures 2.3 seconds. consistently. where's the time going","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"tell me what this cron expression does and whether it accounts for dst","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"docs for the new sdk retry behavior — defaults, how to override, and the interaction with the server's retry-after","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"recommend a path to zero-downtime deploys for the rails monolith. we currently take 90 seconds of 502s every deploy","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"bulk actions on the table: select all across pages, then archive/tag/delete with a confirm that says how many","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the queue name in the staging config points at the prod queue. that's terrifying, fix it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"here's what i'm seeing in the logs when it goes wrong, and i genuinely can't work out the ordering:\n\n14:02:11.220 [http-3] INFO OrderService - creating order id=ord_7712 user=u_449\n14:02:11.221 [http-3] DEBUG Outbox - staged event order.created id=ev_a1\n14:02:11.244 [http-3] INFO OrderService - committed tx=tx_88a\n14:02:11.198 [outbox-1] DEBUG Outbox - polled 1 events\n14:02:11.199 [outbox-1] INFO Publisher - published ev_a1 to topic orders\n14:02:11.401 [consumer-2] WARN OrderProjector - order ord_7712 not found, requeue attempt=1\n14:02:12.410 [consumer-2] WARN OrderProjector - order ord_7712 not found, requeue attempt=2\n14:02:14.418 [consumer-2] ERROR OrderProjector - giving up on ev_a1\n\nnote the outbox timestamp is BEFORE the staged log line. clocks are ntp synced, same host","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"the queue name in the staging config points at the prod queue. that's terrifying, fix it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"here's what i'm seeing in the logs when it goes wrong, and i genuinely can't work out the ordering:\n\n14:02:11.220 [http-3] INFO OrderService - creating order id=ord_7712 user=u_449\n14:02:11.221 [http-3] DEBUG Outbox - staged event order.created id=ev_a1\n14:02:11.244 [http-3] INFO OrderService - committed tx=tx_88a\n14:02:11.198 [outbox-1] DEBUG Outbox - polled 1 events\n14:02:11.199 [outbox-1] INFO Publisher - published ev_a1 to topic orders\n14:02:11.401 [consumer-2] WARN OrderProjector - order ord_7712 not found, requeue attempt=1\n14:02:12.410 [consumer-2] WARN OrderProjector - order ord_7712 not found, requeue attempt=2\n14:02:14.418 [consumer-2] ERROR OrderProjector - giving up on ev_a1\n\nnote the outbox timestamp is BEFORE the staged log line. clocks are ntp synced, same host","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} {"prompt":"consolidate the two auth middlewares (session and api key) into one that handles both, same accept/reject decisions","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"is there a path where we send a password reset email to an unverified address","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"is there a path where we send a password reset email to an unverified address","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"release announcement for the api v3 beta. audience is existing integrators, be concrete about what's new and what breaks","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"grpc health checks on all internal services so the mesh stops routing to warming pods","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"ugh whatever, you pick","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"grpc health checks on all internal services so the mesh stops routing to warming pods","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"we need to decide how the desktop app updates itself. sparkle vs our own, delta updates or full, and what the rollback story is when a release is bad. write the options up","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"local http server in the electron main process for the oauth callback, bound to loopback, shut down after the first request","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"the preferences window needs tabs, and the window size should be remembered per tab like xcode does","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"hardcoded 'localhost:3000' in the api client, read it from config","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"the ipc between main and renderer passes raw objects around with no contract. define the channel types in one place and make both sides use them, no behavior change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the app won't quit — cmd+q does nothing when a background sync is running, and eventually you get the force quit dialog","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"how does our auto-update verify the signature? point me at the code path, i want to confirm we're not just checking the https cert","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"user guide chapter on keyboard shortcuts, grouped by context, with the mac and windows chords side by side","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the app won't quit — cmd+q does nothing when a background sync is running, and eventually you get the force quit dialog","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"how does our auto-update verify the signature? point me at the code path, i want to confirm we're not just checking the https cert","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"user guide chapter on keyboard shortcuts, grouped by context, with the mac and windows chords side by side","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"plan the notarization + signing pipeline in CI, we currently do it on someone's laptop","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"sqlite migration runner for the desktop app that handles users jumping several versions and can't ever lose data","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the traffic light buttons overlap our custom titlebar content at small widths","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"sqlite migration runner for the desktop app that handles users jumping several versions and can't ever lose data","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the traffic light buttons overlap our custom titlebar content at small widths","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"auto-updater checks every 5 minutes, make it hourly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"we have `Document`, `Doc` and `FileModel` for the same thing across the codebase. settle on `Document` and sweep","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"we have `Document`, `Doc` and `FileModel` for the same thing across the codebase. settle on `Document` and sweep","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"on windows only, the file watcher fires twice per save and we run the sync twice","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"review the ipc surface for anything a compromised renderer could abuse","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"prose for the app's about box and the credits/licenses screen, generated from the dependency licenses","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"prose for the app's about box and the credits/licenses screen, generated from the dependency licenses","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"what would it take to make our editor collaborative? i want a realistic assessment and a phased plan, not a yes/no","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"implement file locking so two open windows can't clobber the same document, with a clear takeover flow","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the tooltip on the toolbar appears instantly and it's annoying, give it a 400ms delay","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"our python code uses `%` formatting, `.format()`, and f-strings depending on who wrote it. standardize on f-strings, no output changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"the tooltip on the toolbar appears instantly and it's annoying, give it a 400ms delay","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"our python code uses `%` formatting, `.format()`, and f-strings depending on who wrote it. standardize on f-strings, no output changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"ipad app crashes on cold launch from a share extension about 1 in 10 times, and only when the app wasn't already running","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explique-moi comment fonctionne le mécanisme de reprise du téléchargement dans downloader.rs, je veux comprendre avant de le modifier","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"fr"} +{"prompt":"explique-moi comment fonctionne le mécanisme de reprise du téléchargement dans downloader.rs, je veux comprendre avant de le modifier","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"fr"} {"prompt":"the troubleshooting page needs a section on the 'sync stuck' state, what causes it and the three things a user can try","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"outline the migration from our custom telemetry to opentelemetry, including what we lose","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"implement conflict detection on save: if the remote version changed, present both and let the user pick, don't silently overwrite","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the empty trash confirm says 'Are you sure?' — write real copy that says what's permanent","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"implement conflict detection on save: if the remote version changed, present both and let the user pick, don't silently overwrite","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"the empty trash confirm says 'Are you sure?' — write real copy that says what's permanent","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"extract the document serialization into its own crate so the cli and the app share it, byte-identical output on the test corpus","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"search is case sensitive and shouldn't be","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"double check the crash-safety of our save path: temp file, fsync, rename — is that actually what the code does","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"focus jumps to the first field when the autosave fires, which loses what you were typing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"list view needs an outline mode with collapsible groups, chevrons that rotate, and state persisted across launches","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"plan and start the work for splitting our shared package into three, i'll review the plan before you go far","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"explain the licensing check and then write the docs page for enterprise customers about how offline activation works","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"actually hold on, do the other one first","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"search is case sensitive and shouldn't be","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"double check the crash-safety of our save path: temp file, fsync, rename — is that actually what the code does","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"focus jumps to the first field when the autosave fires, which loses what you were typing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"list view needs an outline mode with collapsible groups, chevrons that rotate, and state persisted across launches","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"plan and start the work for splitting our shared package into three, i'll review the plan before you go far","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"explain the licensing check and then write the docs page for enterprise customers about how offline activation works","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} {"prompt":"quiero un plan para dividir el frontend monolítico en módulos por dominio, sin romper las rutas actuales. tres meses, cuatro devs","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"es"} {"prompt":"graphql dataloader for the org + membership resolvers, we're doing 200 queries per page load","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"the pricing toggle between monthly and annual should animate the numbers, and annual needs the '2 months free' pill","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"we're still on node 18 in the dockerfile, go to 22","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"we're still on node 18 in the dockerfile, go to 22","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"our api responses are built with three different serialization approaches. pick the one in the newest handlers and convert the rest, byte-identical json","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"one specific customer's csv import produces rows shifted by one column, but only rows after about line 4000. their file opens fine in excel","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"tell me what our current password policy actually enforces vs what the ui claims","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"getting started guide for self-hosters — docker compose, the four required env vars, and the first-admin bootstrap step people always miss","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"could you put together the design for our tenant onboarding pipeline? spring boot, and the awkward part is that provisioning touches four systems and any of them can fail halfway. i want the doc before code","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"implement the saga for tenant provisioning as specced in docs/design/provisioning.md — compensations for each step, state in postgres","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"tell me what our current password policy actually enforces vs what the ui claims","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"getting started guide for self-hosters — docker compose, the four required env vars, and the first-admin bootstrap step people always miss","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"could you put together the design for our tenant onboarding pipeline? spring boot, and the awkward part is that provisioning touches four systems and any of them can fail halfway. i want the doc before code","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"implement the saga for tenant provisioning as specced in docs/design/provisioning.md — compensations for each step, state in postgres","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"spring: add a filter that stamps a correlation id onto MDC and propagates it downstream through the feign clients","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"would you mind building the account switcher in the ios app? avatar row, checkmark on active, add-account row at the bottom, and switching should tear down the old session cleanly","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the nav title should be inline not large on the detail screens","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"please bump spring boot to 3.4.1 and deal with whatever deprecations show up","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"the actuator health endpoint is exposed on the public port, move it to the management port","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"our service classes are annotated with @Transactional at the class level which means read paths open write transactions. tighten it per-method, semantics preserved where it matters","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"rename the `Beacon` entity to `Device` across the java code, the flyway migrations going forward, and the openapi models","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"requests occasionally take 5+ seconds with nothing in the app logs and the db query log shows 3ms. hikari pool is 20, we're at maybe 8 concurrent. what else could it be","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"why is the widget timeline only refreshing once a day","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"i'd appreciate a read on our transaction boundaries in the order service, specifically whether the outbox write is inside the same tx as the state change","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"is it safe to run two instances of the scheduler? asking because someone scaled the deployment and i want to know what we're in for","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"javadoc on the public service interfaces, and please state the transactional expectations of each method since that's the thing callers get wrong","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"would you mind building the account switcher in the ios app? avatar row, checkmark on active, add-account row at the bottom, and switching should tear down the old session cleanly","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"the nav title should be inline not large on the detail screens","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"please bump spring boot to 3.4.1 and deal with whatever deprecations show up","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"the actuator health endpoint is exposed on the public port, move it to the management port","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"our service classes are annotated with @Transactional at the class level which means read paths open write transactions. tighten it per-method, semantics preserved where it matters","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"rename the `Beacon` entity to `Device` across the java code, the flyway migrations going forward, and the openapi models","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"requests occasionally take 5+ seconds with nothing in the app logs and the db query log shows 3ms. hikari pool is 20, we're at maybe 8 concurrent. what else could it be","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"why is the widget timeline only refreshing once a day","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"i'd appreciate a read on our transaction boundaries in the order service, specifically whether the outbox write is inside the same tx as the state change","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"is it safe to run two instances of the scheduler? asking because someone scaled the deployment and i want to know what we're in for","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"javadoc on the public service interfaces, and please state the transactional expectations of each method since that's the thing callers get wrong","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"write the swiftui migration notes for the team — what we learned moving the settings screens, patterns to copy, things to avoid","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"argo rollouts with a canary — 10% for 5 minutes, then 50%, auto-abort on the error rate SLO. plan it first, i want to review before anything lands in the cluster","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"argo rollouts with a canary — 10% for 5 minutes, then 50%, auto-abort on the error rate SLO. plan it first, i want to review before anything lands in the cluster","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"helm chart for the new worker service, following the pattern in charts/api, with the hpa and pdb","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"control room screen for the ops team: service tiles with rag status, last deploy time, and a click-through to logs. dense, no wasted space","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the pdb minAvailable is 100% which blocks node drains, set it to 50%","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"our ci has 7 nearly identical jobs. collapse into a matrix, same jobs run, same names in the required checks","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"nodes go NotReady one at a time every few days, kubelet logs mention PLEG. we're on eks 1.31 with bottlerocket","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"have a look at our network policies and tell me whether the worker namespace can actually reach the database, i think we have overlapping rules","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"document our deployment process from merge to prod, including the manual approval gate and who can click it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"control room screen for the ops team: service tiles with rag status, last deploy time, and a click-through to logs. dense, no wasted space","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the pdb minAvailable is 100% which blocks node drains, set it to 50%","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"our ci has 7 nearly identical jobs. collapse into a matrix, same jobs run, same names in the required checks","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"nodes go NotReady one at a time every few days, kubelet logs mention PLEG. we're on eks 1.31 with bottlerocket","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"have a look at our network policies and tell me whether the worker namespace can actually reach the database, i think we have overlapping rules","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"document our deployment process from merge to prod, including the manual approval gate and who can click it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"figure out what we do about the 40 pending dependabot PRs, i want a policy not a marathon","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"yeah go ahead","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"ok so here's my problem, i've been going back and forth on this for a week. we need per-customer rate limits but our gateway is envoy and the limits live in a postgres table that the control plane owns, and i don't want a hot path db read. do we push config to envoy, run a local rls service, or something else. write up the options with what each one costs us operationally and pick one","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"ok so here's my problem, i've been going back and forth on this for a week. we need per-customer rate limits but our gateway is envoy and the limits live in a postgres table that the control plane owns, and i don't want a hot path db read. do we push config to envoy, run a local rls service, or something else. write up the options with what each one costs us operationally and pick one","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"build the rate limit service that envoy's rls will call, redis backed, and a control plane endpoint to update limits without a restart","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"usage meter component showing consumption vs limit with a warning state at 80% and a hard state at 100%","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"limit header says X-Rate-Limit but the docs say X-RateLimit, pick the docs spelling in the code","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"our config structs are read from viper in 20 places with string keys. load once into a typed struct, pass it down, same values","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"rate limits are rejecting legitimate traffic from one customer whose usage hasn't changed. counters look wrong but i can't tell why","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain the difference between the two ways we can be at 'limit exceeded' — the local token bucket and the global counter. which wins","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"write the customer-facing docs for rate limits: the numbers per plan, the headers, and the recommended backoff","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"limit header says X-Rate-Limit but the docs say X-RateLimit, pick the docs spelling in the code","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"our config structs are read from viper in 20 places with string keys. load once into a typed struct, pass it down, same values","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"rate limits are rejecting legitimate traffic from one customer whose usage hasn't changed. counters look wrong but i can't tell why","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain the difference between the two ways we can be at 'limit exceeded' — the local token bucket and the global counter. which wins","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"write the customer-facing docs for rate limits: the numbers per plan, the headers, and the recommended backoff","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"i keep thinking about how we'd do soft deletes properly across 40 tables without every query needing to remember the filter. row level security? views? a query layer? write it up","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"add the `restore` mutation for soft-deleted projects, plus the cascade rules for their tasks","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"add the `restore` mutation for soft-deleted projects, plus the cascade rules for their tasks","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"trash screen: list of deleted items with days remaining, restore button per row, empty trash in the toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"deleted items still show in the count on the sidebar","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"our repository methods each hand-write `WHERE deleted_at IS NULL`. move it into the base query so a new method can't forget, and verify none of the 90 existing methods change behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"restoring a project brings back tasks that were deleted separately before the project was. shouldn't happen and i don't see where the timestamps get compared","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"quick sanity check — does our purge job actually delete the s3 objects too or only the db rows","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"deleted items still show in the count on the sidebar","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"our repository methods each hand-write `WHERE deleted_at IS NULL`. move it into the base query so a new method can't forget, and verify none of the 90 existing methods change behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"restoring a project brings back tasks that were deleted separately before the project was. shouldn't happen and i don't see where the timestamps get compared","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"quick sanity check — does our purge job actually delete the s3 objects too or only the db rows","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"help doc explaining the 30 day trash policy to end users, and what admins can do that regular users can't","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"here's the stack, this is happening in prod maybe 20 times an hour:\n\njava.lang.IllegalStateException: Cannot forward after response has been committed\n\tat org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:315)\n\tat com.acme.atlas.web.ErrorPageFilter.doFilter(ErrorPageFilter.java:97)\n\tat com.acme.atlas.web.StreamingExportController.export(StreamingExportController.java:64)\n\tat java.base/java.lang.reflect.Method.invoke(Method.java:580)\n\tat org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:118)\nCaused by: org.postgresql.util.PSQLException: An I/O error occurred while sending to the backend.\n\tat org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:379)\n\nthe export streams a large result set. i think the client disconnects mid-stream but i don't understand why that turns into a forward attempt","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"design the api for scheduled reports and then implement the scheduling part, i'll do the rendering","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"rename the confusingly-named `process()` methods across the pipeline classes and update the architecture doc that references them","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} -{"prompt":"sync stuff again","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"here's the review request from the ticket, please take a look and tell me what you think, no changes yet:\n\n```go\nfunc (s *Server) HandleUpload(w http.ResponseWriter, r *http.Request) {\n\tf, hdr, err := r.FormFile(\"file\")\n\tif err != nil {\n\t\thttp.Error(w, err.Error(), 400)\n\t\treturn\n\t}\n\tdefer f.Close()\n\n\tname := filepath.Join(s.uploadDir, hdr.Filename)\n\tout, err := os.Create(name)\n\tif err != nil {\n\t\thttp.Error(w, \"cannot write\", 500)\n\t\treturn\n\t}\n\tdefer out.Close()\n\n\tif _, err := io.Copy(out, f); err != nil {\n\t\thttp.Error(w, \"copy failed\", 500)\n\t\treturn\n\t}\n\tjson.NewEncoder(w).Encode(map[string]string{\"path\": name})\n}\n```","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"here's the stack, this is happening in prod maybe 20 times an hour:\n\njava.lang.IllegalStateException: Cannot forward after response has been committed\n\tat org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:315)\n\tat com.acme.atlas.web.ErrorPageFilter.doFilter(ErrorPageFilter.java:97)\n\tat com.acme.atlas.web.StreamingExportController.export(StreamingExportController.java:64)\n\tat java.base/java.lang.reflect.Method.invoke(Method.java:580)\n\tat org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:118)\nCaused by: org.postgresql.util.PSQLException: An I/O error occurred while sending to the backend.\n\tat org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:379)\n\nthe export streams a large result set. i think the client disconnects mid-stream but i don't understand why that turns into a forward attempt","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"design the api for scheduled reports and then implement the scheduling part, i'll do the rendering","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"rename the confusingly-named `process()` methods across the pipeline classes and update the architecture doc that references them","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"here's the review request from the ticket, please take a look and tell me what you think, no changes yet:\n\n```go\nfunc (s *Server) HandleUpload(w http.ResponseWriter, r *http.Request) {\n\tf, hdr, err := r.FormFile(\"file\")\n\tif err != nil {\n\t\thttp.Error(w, err.Error(), 400)\n\t\treturn\n\t}\n\tdefer f.Close()\n\n\tname := filepath.Join(s.uploadDir, hdr.Filename)\n\tout, err := os.Create(name)\n\tif err != nil {\n\t\thttp.Error(w, \"cannot write\", 500)\n\t\treturn\n\t}\n\tdefer out.Close()\n\n\tif _, err := io.Copy(out, f); err != nil {\n\t\thttp.Error(w, \"copy failed\", 500)\n\t\treturn\n\t}\n\tjson.NewEncoder(w).Encode(map[string]string{\"path\": name})\n}\n```","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} {"prompt":"roadmap for our internal developer platform. right now teams copy a template repo and diverge immediately","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"scaffolding generator for new services — repo layout, ci, chart, otel wiring, all from one command","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"service catalog page: search, owner, on-call, tier, links out to dashboards. data comes from the yaml files in the platform repo","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"the template's default cpu limit is 100m which is nonsense, make it 1","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"extract the shared otel setup from all 12 services into a library. same spans, same attributes, same sampling","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"traces are missing the db spans for one service only. same library version, same init code as far as i can tell","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"extract the shared otel setup from all 12 services into a library. same spans, same attributes, same sampling","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"traces are missing the db spans for one service only. same library version, same init code as far as i can tell","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"what conventions does the service template actually enforce vs merely suggest","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"docs for the platform cli — the four commands, what each generates, and how to opt out of the defaults","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"propose how we handle secrets. right now some are in sealed-secrets, some in the aws secrets manager, and two are in a helm values file in git","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"docs for the platform cli — the four commands, what each generates, and how to opt out of the defaults","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"propose how we handle secrets. right now some are in sealed-secrets, some in the aws secrets manager, and two are in a helm values file in git","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"external-secrets operator wiring for the api namespace, with the refresh interval and a fallback if the provider is down at startup","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the secrets in charts/legacy/values.yaml are committed. rotate them out, that's a today problem","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the secrets in charts/legacy/values.yaml are committed. rotate them out, that's a today problem","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} {"prompt":"settings form with a masked secret field, reveal on click, and a 'last rotated' timestamp under it","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"our env var names are inconsistent — some ACME_, some APP_, some bare. unify on ACME_ with a compat shim for one release","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"pods start fine but 30 minutes later start failing auth to the database. token expiry i assume, but we're using iam auth which is supposed to refresh","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"trace where the db password comes from in each of our four environments, i suspect one of them is still reading the committed file","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"our env var names are inconsistent — some ACME_, some APP_, some bare. unify on ACME_ with a compat shim for one release","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"pods start fine but 30 minutes later start failing auth to the database. token expiry i assume, but we're using iam auth which is supposed to refresh","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"trace where the db password comes from in each of our four environments, i suspect one of them is still reading the committed file","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} {"prompt":"runbook for rotating the database credentials without downtime, including the pgbouncer reload step","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"ちょっと相談。Kubernetes の Job で動かしているバッチを Argo Workflows に移す方針を書いてほしい。依存関係のあるジョブが 20 個ある","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"ja"} -{"prompt":"sonst nichts, nur den Timeout im Ingress von 60s auf 300s hochsetzen für den Export-Endpoint","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"de"} -{"prompt":"swiftui: charts view for the weekly summary using Swift Charts, bar marks, and a selection overlay that shows the day's total","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"sonst nichts, nur den Timeout im Ingress von 60s auf 300s hochsetzen für den Export-Endpoint","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"de"} +{"prompt":"swiftui: charts view for the weekly summary using Swift Charts, bar marks, and a selection overlay that shows the day's total","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"background refresh via BGAppRefreshTask, budget aware, and it should coalesce with the push-triggered refresh instead of doubling up","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"pull the networking out of the SwiftUI views — they're calling URLSession directly in .task blocks. put it behind a service, same requests, same order","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"our app icon on the watch is the iphone one scaled and it looks awful","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"list scrolling stutters on iphone 12 when the images load, and only after you scroll past about 40 rows","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"does our keychain access group setup actually let the widget read the token, or is it falling back to something else","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"write the privacy nutrition label details for the app store — what we collect, linked or not, and why","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"our app icon on the watch is the iphone one scaled and it looks awful","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"list scrolling stutters on iphone 12 when the images load, and only after you scroll past about 40 rows","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"does our keychain access group setup actually let the widget read the token, or is it falling back to something else","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"write the privacy nutrition label details for the app store — what we collect, linked or not, and why","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"plan how we support the watch app talking to the phone when the phone is offline. what's cached, what's queued, what we tell the user","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"live activity for an in-progress delivery, compact and expanded, updated via push","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the push token registration retries forever if the first attempt fails, cap it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"live activity for an in-progress delivery, compact and expanded, updated via push","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"the push token registration retries forever if the first attempt fails, cap it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"share the model layer between the app, the widget and the watch target. right now each has its own copy of the structs and they drift","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"notifications arrive on some devices and not others, same account, both opted in. apns says success for all of them","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"read the sync conflict resolution and tell me what happens if the same field is edited on two devices while both are offline","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the api reference for our push payload format needs writing, including the silent-push variant and the fields the widget reads","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"everything's fine now","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"notifications arrive on some devices and not others, same account, both opted in. apns says success for all of them","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"read the sync conflict resolution and tell me what happens if the same field is edited on two devices while both are offline","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the api reference for our push payload format needs writing, including the silent-push variant and the fields the widget reads","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"so i've been staring at our billing code and i think we need to step back. proration is computed in three places, credits are applied after tax in one path and before in another, and nobody knows what happens on a mid-cycle downgrade to a cheaper annual plan. write me the model we SHOULD have, and then how we get from here to there without breaking existing invoices","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"implement proration for mid-cycle plan changes, credit the unused portion, and produce an invoice preview endpoint that shows the math","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"invoice detail page — line items, the proration rows explained in plain language, download pdf, and a 'why this amount' expander","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"tax is rounded with banker's rounding in one file and half-up in another. make it half-up everywhere, that's what finance expects","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"tax is rounded with banker's rounding in one file and half-up in another. make it half-up everywhere, that's what finance expects","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"money is a float in six places. move everything to integer cents with a Money type, and prove no invoice total changes on the last 12 months of data","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"one customer's invoice is off by $0.03 and the sum of the line items doesn't match the total. only theirs","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"is our webhook handler for `invoice.payment_failed` idempotent? we got three dunning emails for one failure","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"write the billing docs for customers: cycles, proration, what happens when you cancel, refunds policy. finance will review so be precise","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"one customer's invoice is off by $0.03 and the sum of the line items doesn't match the total. only theirs","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"is our webhook handler for `invoice.payment_failed` idempotent? we got three dunning emails for one failure","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"write the billing docs for customers: cycles, proration, what happens when you cancel, refunds policy. finance will review so be precise","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"sequence the work for supporting purchase orders and invoicing outside stripe, enterprise deals need it","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"dunning state machine: retry schedule, emails at each step, downgrade to free after 21 days, and everything auditable","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"dunning state machine: retry schedule, emails at each step, downgrade to free after 21 days, and everything auditable","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"payment failed banner, persistent, with a fix-payment cta and a dismissible-until-tomorrow option","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"the trial length constant says 14 but marketing is advertising 30","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"pull the entitlement checks out of the controllers into a policy object. same allow/deny for every plan, add tests that enumerate the matrix","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the trial length constant says 14 but marketing is advertising 30","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"pull the entitlement checks out of the controllers into a policy object. same allow/deny for every plan, add tests that enumerate the matrix","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"users on the team plan sometimes see the free plan limits for a few minutes after upgrading","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"how do we decide a subscription is 'active' — there seem to be three different checks and i want to know which is authoritative","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"release notes for the billing revamp, and a separate internal note for support about what changes in the admin tools","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"how do we decide a subscription is 'active' — there seem to be three different checks and i want to know which is authoritative","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"release notes for the billing revamp, and a separate internal note for support about what changes in the admin tools","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"plan the seats-based pricing model change and then build the seat counting service","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"walk me through the dunning flow and then document it for support","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} -{"prompt":"todo list from standup, take the top one:\n\n- [ ] invoice pdf shows the old logo\n- [ ] proration preview off by a day on month boundaries\n- [ ] webhook retries hammer us during their outages, need backoff\n- [ ] admin can't refund partial amounts\n- [ ] the currency symbol is hardcoded to $ in three emails","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"pasted-context","lang":"en"} -{"prompt":"que onda con esto","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"es"} -{"prompt":"i want a design for how the game server handles reconnects. player drops mid-match, we hold their slot for 90 seconds, an ai takes over, and their state has to be exactly restored. write it up including what the client sends on rejoin","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"authoritative movement validation on the server — reject impossible deltas, allow for 150ms of latency, and log the rejections for tuning","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"walk me through the dunning flow and then document it for support","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"todo list from standup, take the top one:\n\n- [ ] invoice pdf shows the old logo\n- [ ] proration preview off by a day on month boundaries\n- [ ] webhook retries hammer us during their outages, need backoff\n- [ ] admin can't refund partial amounts\n- [ ] the currency symbol is hardcoded to $ in three emails","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"que onda con esto","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"es"} +{"prompt":"i want a design for how the game server handles reconnects. player drops mid-match, we hold their slot for 90 seconds, an ai takes over, and their state has to be exactly restored. write it up including what the client sends on rejoin","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"authoritative movement validation on the server — reject impossible deltas, allow for 150ms of latency, and log the rejections for tuning","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"scoreboard overlay, sorted live, team colors, and the local player's row highlighted and pinned visible","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"the tick rate constant is 30, we agreed on 60","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"our entity update loops are three separate passes over the same list. merge them into one pass, same resulting state each frame","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"players rubber band near the map edges but only on the eu server. same build as us-east","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"look at the interest management code and tell me how much bandwidth per player we're actually sending at 40 players","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"modding documentation: the lua api surface, the sandbox restrictions, and how to package a mod","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"plan the migration of our save format to something versioned. players have saves from four years of builds","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"replay recording that captures inputs not state, with a compact binary format and a version header","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"our entity update loops are three separate passes over the same list. merge them into one pass, same resulting state each frame","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"players rubber band near the map edges but only on the eu server. same build as us-east","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"look at the interest management code and tell me how much bandwidth per player we're actually sending at 40 players","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"modding documentation: the lua api surface, the sandbox restrictions, and how to package a mod","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"plan the migration of our save format to something versioned. players have saves from four years of builds","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"replay recording that captures inputs not state, with a compact binary format and a version header","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"settings menu with graphics presets, and changing a preset should show which individual settings it changes before you apply","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"mouse sensitivity slider goes to 100 and the top half is unusable, cap it at 20","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"our ability system is 4000 lines of switch statements. move to data-driven definitions, same abilities behaving the same in the test scenarios","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"frame time spikes to 40ms every ~4 seconds on the main menu of all things. the profiler says gc","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain how our netcode handles packet loss right now — is there any redundancy or is it pure reliable-ordered over enet","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"patch notes for the balance pass, and the internal doc explaining the reasoning so we remember next time","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"postgres logical replication to a read replica in another region for analytics, and please plan the initial sync so it doesn't take the primary down","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"our ability system is 4000 lines of switch statements. move to data-driven definitions, same abilities behaving the same in the test scenarios","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"frame time spikes to 40ms every ~4 seconds on the main menu of all things. the profiler says gc","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain how our netcode handles packet loss right now — is there any redundancy or is it pure reliable-ordered over enet","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"patch notes for the balance pass, and the internal doc explaining the reasoning so we remember next time","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"postgres logical replication to a read replica in another region for analytics, and please plan the initial sync so it doesn't take the primary down","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"materialized view for the daily metrics with a concurrent refresh, and a job that refreshes it every 15 min","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the analytics page needs a compare-to-previous-period toggle, with the delta shown per metric","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the analytics page needs a compare-to-previous-period toggle, with the delta shown per metric","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"statement_timeout isn't set on the analytics role, set it to 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"the 30 report queries share 5 patterns with slight variations. build them from composable pieces, identical sql output — diff the generated queries to prove it","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"one report returns different numbers depending on whether you run it in the morning or evening. the date filter looks timezone-correct to me","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"read the query in reports/retention.sql and tell me if the cohort definition matches what we say in the docs","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"data dictionary for the warehouse — table by table, column meanings, grain, and which ones are safe to join","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"one report returns different numbers depending on whether you run it in the morning or evening. the date filter looks timezone-correct to me","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"read the query in reports/retention.sql and tell me if the cohort definition matches what we say in the docs","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"data dictionary for the warehouse — table by table, column meanings, grain, and which ones are safe to join","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"outline how we'd let customers write their own sql against their data safely. read only, resource limited, and no way to see another tenant","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"sql editor with autocomplete from the schema, run button, results grid, and a cost estimate before you run","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"query timeout error shows the raw pg message to users, wrap it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"pgbouncer in transaction mode plus our use of prepared statements is a known bad combo — sort out which one we change, then do it","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"explain the deadlock our logs keep reporting between the two update paths on the inventory table:\n\n2026-07-29 11:04:02.881 UTC [4412] ERROR: deadlock detected\n2026-07-29 11:04:02.881 UTC [4412] DETAIL: Process 4412 waits for ShareLock on transaction 88192441; blocked by process 4390.\n\tProcess 4390 waits for ShareLock on transaction 88192438; blocked by process 4412.\n\tProcess 4412: UPDATE inventory SET qty = qty - $1 WHERE sku = $2 AND warehouse_id = $3\n\tProcess 4390: UPDATE inventory SET qty = qty + $1 WHERE warehouse_id = $2 AND sku = ANY($3)\n2026-07-29 11:04:02.881 UTC [4412] HINT: See server log for query details.\n2026-07-29 11:04:02.881 UTC [4412] CONTEXT: while updating tuple (441,12) in relation \"inventory\"\n\ni understand deadlocks in general, i want to know specifically what ordering these two take","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"write up the postgres tuning we did and why, otherwise the next person will undo it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"replica lag spikes to 40 seconds during our nightly job and the app serves stale data. the job isn't doing anything huge, 200k updates","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"same as before pls","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"we're adding a public api and i need the versioning and deprecation policy written down before we ship anything. header vs path, how long we support a version, what counts as breaking","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"api key management: create, scope, rotate, revoke, last-used tracking, and prefix them so leaks are detectable in scanners","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"sql editor with autocomplete from the schema, run button, results grid, and a cost estimate before you run","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"query timeout error shows the raw pg message to users, wrap it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"pgbouncer in transaction mode plus our use of prepared statements is a known bad combo — sort out which one we change, then do it","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"explain the deadlock our logs keep reporting between the two update paths on the inventory table:\n\n2026-07-29 11:04:02.881 UTC [4412] ERROR: deadlock detected\n2026-07-29 11:04:02.881 UTC [4412] DETAIL: Process 4412 waits for ShareLock on transaction 88192441; blocked by process 4390.\n\tProcess 4390 waits for ShareLock on transaction 88192438; blocked by process 4412.\n\tProcess 4412: UPDATE inventory SET qty = qty - $1 WHERE sku = $2 AND warehouse_id = $3\n\tProcess 4390: UPDATE inventory SET qty = qty + $1 WHERE warehouse_id = $2 AND sku = ANY($3)\n2026-07-29 11:04:02.881 UTC [4412] HINT: See server log for query details.\n2026-07-29 11:04:02.881 UTC [4412] CONTEXT: while updating tuple (441,12) in relation \"inventory\"\n\ni understand deadlocks in general, i want to know specifically what ordering these two take","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"write up the postgres tuning we did and why, otherwise the next person will undo it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"replica lag spikes to 40 seconds during our nightly job and the app serves stale data. the job isn't doing anything huge, 200k updates","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"we're adding a public api and i need the versioning and deprecation policy written down before we ship anything. header vs path, how long we support a version, what counts as breaking","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"api key management: create, scope, rotate, revoke, last-used tracking, and prefix them so leaks are detectable in scanners","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"api keys page: create modal that shows the key once with a copy button, table with last used and scopes, revoke with confirm","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the key prefix is 'sk_' which collides with stripe's, make it 'ak_'","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"our three auth paths (session, api key, service token) each build a different user context shape. one shape, one builder","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"api keys stop working after exactly 7 days for some customers. we don't have expiry on keys. i'm confused","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"check whether a revoked key can still be used from a warm cache, and for how long","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"authentication docs for the api — the three auth methods, when to use each, code samples in curl, js and python","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"the key prefix is 'sk_' which collides with stripe's, make it 'ak_'","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"our three auth paths (session, api key, service token) each build a different user context shape. one shape, one builder","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"api keys stop working after exactly 7 days for some customers. we don't have expiry on keys. i'm confused","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"check whether a revoked key can still be used from a warm cache, and for how long","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"authentication docs for the api — the three auth methods, when to use each, code samples in curl, js and python","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"design the audit log we'd need to pass soc2, then implement the middleware that captures it","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"clean up the naming in the auth package and update the readme diagram that references the old names","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} {"prompt":"sso for the admin console, oidc, and it has to work with google workspace and entra without per-customer code","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"login screen redesign: sso first, email/password behind a 'more options' disclosure, and the error copy shouldn't leak whether an account exists","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"password field has autocomplete=off which fights password managers, remove it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"audit the session handling for fixation and make sure we rotate the session id on privilege change. tell me first, don't change anything","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"audit the session handling for fixation and make sure we rotate the session id on privilege change. tell me first, don't change anything","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"sso login works but users land on a blank page about 1 in 20 times, and refreshing fixes it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"admin guide for configuring sso, per idp, with the exact claim mappings we need and screenshots marked todo","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"map out what mfa support looks like for us — totp first, webauthn later, recovery codes, and the enforcement policy per org","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"totp enrollment and verification, drift window of one step, and rate limit the verify endpoint hard","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"mfa setup flow ui: qr code, manual key fallback, verify field with autofocus, then the recovery codes screen with a download","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the totp window is 3 steps which is too loose, make it 1","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"our validation errors come back in two different json shapes depending on which layer rejected. unify the shape, keep the same status codes and messages","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"recovery codes work twice. they should be single use and i see the delete call right there","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"so what now","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"totp enrollment and verification, drift window of one step, and rate limit the verify endpoint hard","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"mfa setup flow ui: qr code, manual key fallback, verify field with autofocus, then the recovery codes screen with a download","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the totp window is 3 steps which is too loose, make it 1","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"our validation errors come back in two different json shapes depending on which layer rejected. unify the shape, keep the same status codes and messages","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"recovery codes work twice. they should be single use and i see the delete call right there","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} {"prompt":"we need a plan for the storage engine rewrite. current one is a naive append log with a full scan on startup and startup is now 40 seconds. i want options — lsm, b-tree, or keep the log but add an index — with what each costs in write amplification and what the migration looks like for existing data files","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"implement the wal with crc per record, torn-write detection on recovery, and fsync batching with a configurable interval","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"the checkout page needs an order summary that stays visible while you scroll the form on desktop, and collapses to a sticky total bar on mobile","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the free shiping threshold in the banner says 50 but the actual rule is 75","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"we hae two Arc> caches that do the same thing in different modules, merge them into one type and use it in both places, no behavior change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the compactor thread deadlocks maybe once a week under load. lock order looks fine to me but obviously it isnt","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"explain what guarantees our current flush path gives on power loss, i need to know before i promise anything to a customer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"write the on-disk format spec — header layout, record framing, endianness, version negotiation. someone should be able to write a reader from this doc alone","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"- add size variants to the ProductCard (sm/md/lg)\n- price should show strikethrough when there's a sale\n- badge slot top-left for \"new\" / \"low stock\"\n- image aspect 4:5, no layout shift\n- the whole card is a link but the wishlist heart shouldn't trigger navigation","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"implement the wal with crc per record, torn-write detection on recovery, and fsync batching with a configurable interval","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the checkout page needs an order summary that stays visible while you scroll the form on desktop, and collapses to a sticky total bar on mobile","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the free shiping threshold in the banner says 50 but the actual rule is 75","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"we hae two Arc> caches that do the same thing in different modules, merge them into one type and use it in both places, no behavior change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the compactor thread deadlocks maybe once a week under load. lock order looks fine to me but obviously it isnt","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"explain what guarantees our current flush path gives on power loss, i need to know before i promise anything to a customer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"write the on-disk format spec — header layout, record framing, endianness, version negotiation. someone should be able to write a reader from this doc alone","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"- add size variants to the ProductCard (sm/md/lg)\n- price should show strikethrough when there's a sale\n- badge slot top-left for \"new\" / \"low stock\"\n- image aspect 4:5, no layout shift\n- the whole card is a link but the wishlist heart shouldn't trigger navigation","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"inventory reservation service — reserve on add-to-cart with a 20 min hold, release on abandon, and don't oversell under concurrent checkout","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"roadmap for internationalizing the store. currency, tax, addresses, and the copy. we have 4 markets planned and one of them is japan","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the sort dropdown resets to default when you paginate","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"our cart total is computed on the client for display and on the server for charging, and they've drifted. single implementation shared by both, and the totals must match to the cent on the test fixtures","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the sort dropdown resets to default when you paginate","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"our cart total is computed on the client for display and on the server for charging, and they've drifted. single implementation shared by both, and the totals must match to the cent on the test fixtures","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} {"prompt":"carts randomly empty for logged-out users. we store them in a cookie plus localstorage and i think theyre fighting each other but i cant reproduce reliably","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"does our discount stacking logic allow combining a percentage code with a fixed-amount code? read the code and tell me, marketing is asking","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"product copy guidelines doc for the merch team — voice, length limits per field, and what our templates do with line breaks","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"does our discount stacking logic allow combining a percentage code with a fixed-amount code? read the code and tell me, marketing is asking","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"product copy guidelines doc for the merch team — voice, length limits per field, and what our templates do with line breaks","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"spark job to backfill the orders fact table from the raw event archive, 3 years, idempotent per day partition","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"plan how we go from batch-daily to near-real-time on the orders pipeline without maintaining two implementations of the same logic","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"the airflow retries is set to 0 on the ingest dag, make it 3 with a 5 minute delay","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"our dbt models are one giant folder. reorganize into staging/intermediate/marts with the naming convention, same compiled sql","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"row counts in the mart are 3% lower than the source and it moves every run. i've checked the joins twice","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"review our partitioning and clustering choices on the events table in bigquery, we're spending too much on scans","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the pipeline docs describe a `raw.orders_v2` table that doesn't exist, and omits the two tables we actually use. get it accurate","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"chart page for the merchandising team: revenue by category over time, stacked area, with a category picker and csv export","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"idk just look at it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"pasting the profile output because i dont know what to make of it. this is the hot path in our tokenizer:\n\n Overhead Command Shared Object Symbol\n 31.44% lexer lexer [.] acme_lex_next\n 18.02% lexer libc.so.6 [.] __memmove_avx_unaligned_erms\n 12.71% lexer lexer [.] acme_intern_symbol\n 9.88% lexer libc.so.6 [.] malloc\n 7.10% lexer libc.so.6 [.] free\n 4.02% lexer lexer [.] acme_buf_reserve\n\nso 17% in malloc/free and 18% in memmove. we tokenize about 40MB/s and i want 200. where do i start","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"arena allocator for the parser so we stop malloc'ing per node, and free the whole arena at the end of a parse","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"syntax highlighting in the code editor component, incremental, and it can't block typing on a 5000 line file","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"our dbt models are one giant folder. reorganize into staging/intermediate/marts with the naming convention, same compiled sql","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"row counts in the mart are 3% lower than the source and it moves every run. i've checked the joins twice","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"review our partitioning and clustering choices on the events table in bigquery, we're spending too much on scans","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the pipeline docs describe a `raw.orders_v2` table that doesn't exist, and omits the two tables we actually use. get it accurate","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"chart page for the merchandising team: revenue by category over time, stacked area, with a category picker and csv export","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"pasting the profile output because i dont know what to make of it. this is the hot path in our tokenizer:\n\n Overhead Command Shared Object Symbol\n 31.44% lexer lexer [.] acme_lex_next\n 18.02% lexer libc.so.6 [.] __memmove_avx_unaligned_erms\n 12.71% lexer lexer [.] acme_intern_symbol\n 9.88% lexer libc.so.6 [.] malloc\n 7.10% lexer libc.so.6 [.] free\n 4.02% lexer lexer [.] acme_buf_reserve\n\nso 17% in malloc/free and 18% in memmove. we tokenize about 40MB/s and i want 200. where do i start","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"arena allocator for the parser so we stop malloc'ing per node, and free the whole arena at the end of a parse","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"syntax highlighting in the code editor component, incremental, and it can't block typing on a 5000 line file","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the -O2 in the makefile should be -O3 for the release target","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"our error handling is a mix of return codes and a global errno-alike. move to consistent return codes, same failure behavior at every call site","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"what does the memory ordering on that atomic actually buy us? relaxed vs acquire here, i genuinely dont know if the current code is correct","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"developer docs for embedding the library — build flags, the two init modes, threading rules, and please be explicit about what's not thread safe","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"decide the approach for our plugin abi. c abi with opaque handles, or wasm, or a subprocess with ipc. write the comparison and recommend","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"segfault in the destructor path but only in the release build with lto on. debug and reldebug are clean","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"cross compile the lib for aarch64 in CI and publish both artifacts","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"our error handling is a mix of return codes and a global errno-alike. move to consistent return codes, same failure behavior at every call site","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"what does the memory ordering on that atomic actually buy us? relaxed vs acquire here, i genuinely dont know if the current code is correct","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"developer docs for embedding the library — build flags, the two init modes, threading rules, and please be explicit about what's not thread safe","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"decide the approach for our plugin abi. c abi with opaque handles, or wasm, or a subprocess with ipc. write the comparison and recommend","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"segfault in the destructor path but only in the release build with lto on. debug and reldebug are clean","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"cross compile the lib for aarch64 in CI and publish both artifacts","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"the promo code input should show inline validation and the applied discount as a row in the summary, not a toast","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"our currency formatting helper is duplicated in the email templates, the web app and the pdf renderer. one shared function, identical output on the golden files","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"tax is calculated before shipping in one flow and after in another, and i'm pretty sure one of them is wrong but i dont know which","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"compare our two approaches to search on the storefront — the postgres tsvector one on the branch and the meilisearch spike — and tell me which to take forward","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"checkout error copy is all 'something went wrong'. write real messages for the 8 cases we can actually distinguish","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"gift cards. design the whole thing — issuance, partial redemption, expiry rules per market, and what happens on a refund to a gift card order","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"address autocomplete integration with a fallback to manual entry, and normalize what we store so the shipping label doesn't break","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"our currency formatting helper is duplicated in the email templates, the web app and the pdf renderer. one shared function, identical output on the golden files","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"tax is calculated before shipping in one flow and after in another, and i'm pretty sure one of them is wrong but i dont know which","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"compare our two approaches to search on the storefront — the postgres tsvector one on the branch and the meilisearch spike — and tell me which to take forward","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"checkout error copy is all 'something went wrong'. write real messages for the 8 cases we can actually distinguish","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"gift cards. design the whole thing — issuance, partial redemption, expiry rules per market, and what happens on a refund to a gift card order","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"address autocomplete integration with a fallback to manual entry, and normalize what we store so the shipping label doesn't break","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"the size picker should disable out-of-stock sizes instead of letting you select them and fail at checkout","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"order confirmation email has the wrong support address","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"figure out the plan for headless — decoupling our storefront from the platform templates — then do the product listing page as the pilot","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"work out why the inventory numbers drift and then write the note for the ops team","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"go on then","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"ok brain dump: our observability is three tools that dont talk to each other, logs in cloudwatch, metrics in datadog, traces in a self hosted jaeger that half the services dont report to. every incident starts with 10 minutes of tab switching. i want a plan to consolidate, including what we accept losing and roughly what it costs","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"otel collector deployment with tail sampling — keep all errors, keep anything over 1s, sample the rest at 5%","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"trace waterfall view in our internal tool, collapsible spans, and highlight the critical path","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"work out why the inventory numbers drift and then write the note for the ops team","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"ok brain dump: our observability is three tools that dont talk to each other, logs in cloudwatch, metrics in datadog, traces in a self hosted jaeger that half the services dont report to. every incident starts with 10 minutes of tab switching. i want a plan to consolidate, including what we accept losing and roughly what it costs","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"otel collector deployment with tail sampling — keep all errors, keep anything over 1s, sample the rest at 5%","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"trace waterfall view in our internal tool, collapsible spans, and highlight the critical path","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"log retention is 400 days, we only need 30","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"our log statements use 5 different key names for the request id. pick request_id and sweep the whole codebase","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"some traces have a 900ms span called 'unknown' with no attributes and no children. what generates that","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"our log statements use 5 different key names for the request id. pick request_id and sweep the whole codebase","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"some traces have a 900ms span called 'unknown' with no attributes and no children. what generates that","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"how much are we actually spending on logs per service, based on the volume in the config and the retention","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"write our logging conventions doc: levels and when to use them, what must never be logged, and the required fields","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"slo definitions for the 6 tier-1 services, with the error budget policy and what happens when we burn it. i want the doc, not the dashboards","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"synthetic checks hitting our critical flows every minute from 3 regions, alerting only when 2 of 3 fail","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"status page component that reads from our incidents api, per-service history strip for the last 90 days","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"write our logging conventions doc: levels and when to use them, what must never be logged, and the required fields","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"slo definitions for the 6 tier-1 services, with the error budget policy and what happens when we burn it. i want the doc, not the dashboards","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"synthetic checks hitting our critical flows every minute from 3 regions, alerting only when 2 of 3 fail","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"status page component that reads from our incidents api, per-service history strip for the last 90 days","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"pagerduty urgency for the disk alert is high, should be low","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"our alert rules are copy pasted per service with the service name changed. template them, exact same rules firing at the exact same thresholds","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the disk alert fires and resolves every 20 minutes all night. disk is at 71% and stable","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"our alert rules are copy pasted per service with the service name changed. template them, exact same rules firing at the exact same thresholds","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the disk alert fires and resolves every 20 minutes all night. disk is at 71% and stable","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"read our runbooks and tell me which ones reference tools or hosts that dont exist anymore","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"incident review doc for the 3 hour degradation last thursday. i'll give you the timeline, you write the narrative and the action items","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"esto es lo que sale en los logs y no entiendo qué lo provoca:\n\n2026-07-28 22:14:02 WARN [pool-3-thread-7] c.a.sync.Reconciler - remote version 41 < local version 43, skipping\n2026-07-28 22:14:02 INFO [pool-3-thread-7] c.a.sync.Reconciler - marking local dirty entity=doc_8812\n2026-07-28 22:14:03 WARN [pool-3-thread-2] c.a.sync.Reconciler - remote version 41 < local version 43, skipping\n2026-07-28 22:14:03 INFO [pool-3-thread-2] c.a.sync.Reconciler - marking local dirty entity=doc_8812\n2026-07-28 22:14:04 ERROR [pool-3-thread-9] c.a.sync.Reconciler - version conflict unresolvable entity=doc_8812 attempts=32\n\ndos hilos procesan la misma entidad. debería haber un lock por entidad","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"es"} +{"prompt":"incident review doc for the 3 hour degradation last thursday. i'll give you the timeline, you write the narrative and the action items","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"esto es lo que sale en los logs y no entiendo qué lo provoca:\n\n2026-07-28 22:14:02 WARN [pool-3-thread-7] c.a.sync.Reconciler - remote version 41 < local version 43, skipping\n2026-07-28 22:14:02 INFO [pool-3-thread-7] c.a.sync.Reconciler - marking local dirty entity=doc_8812\n2026-07-28 22:14:03 WARN [pool-3-thread-2] c.a.sync.Reconciler - remote version 41 < local version 43, skipping\n2026-07-28 22:14:03 INFO [pool-3-thread-2] c.a.sync.Reconciler - marking local dirty entity=doc_8812\n2026-07-28 22:14:04 ERROR [pool-3-thread-9] c.a.sync.Reconciler - version conflict unresolvable entity=doc_8812 attempts=32\n\ndos hilos procesan la misma entidad. debería haber un lock por entidad","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"es"} {"prompt":"make the deploy notification message include the diff link and the author","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"so uh i think our feature flag system is the problem. 200 flags, no owners, no expiry, and the evaluation is a 400 line if-chain. plan the cleanup and the guardrails so it doesnt happen again","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"flag evaluation service with percentage rollouts, targeting rules, and a local cache with a streaming update channel","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"so uh i think our feature flag system is the problem. 200 flags, no owners, no expiry, and the evaluation is a 400 line if-chain. plan the cleanup and the guardrails so it doesnt happen again","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"flag evaluation service with percentage rollouts, targeting rules, and a local cache with a streaming update channel","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"flags admin ui: list with owner and age, filter for stale, and a detail view showing the rules and current exposure","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"remove the `legacy_checkout` flag, its been 100% off for a year — delete both branches, keeping the off behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"a flag flipped to on for 4% of users who shouldnt match the targeting rule. only in the eu pods","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain how a flag change propagates to a running pod and what the worst case delay is","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"remove the `legacy_checkout` flag, its been 100% off for a year — delete both branches, keeping the off behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"a flag flipped to on for 4% of users who shouldnt match the targeting rule. only in the eu pods","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"explain how a flag change propagates to a running pod and what the worst case delay is","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"write the guide for adding a flag: naming, owner, expiry date, and the cleanup checklist","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"just the usual","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"graphql federation across our 5 services, or a single gateway schema stitched manually, or just... not. write the analysis. our clients are one web app and one mobile app, and the mobile team wants fewer round trips","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"graphql federation across our 5 services, or a single gateway schema stitched manually, or just... not. write the analysis. our clients are one web app and one mobile app, and the mobile team wants fewer round trips","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"persisted queries so the mobile client sends a hash instead of the document, with a build step that extracts them","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the query result panel needs a json tree view with collapse-all and a copy-path action per node","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the query result panel needs a json tree view with collapse-all and a copy-path action per node","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"introspection is enabled in prod, turn it off","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"our resolvers do auth checks inline, inconsistently. move to a directive, same access decisions — enumerate them first so we can compare","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"one nested query takes 12 seconds and the dataloader batching looks like its not kicking in for that path only","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"is our depth limiting actually enforced, or just configured? i see the plugin registered but not in the request path","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"schema documentation for external consumers — the three main entry points, pagination conventions, and error extensions","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"our resolvers do auth checks inline, inconsistently. move to a directive, same access decisions — enumerate them first so we can compare","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"one nested query takes 12 seconds and the dataloader batching looks like its not kicking in for that path only","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"is our depth limiting actually enforced, or just configured? i see the plugin registered but not in the request path","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"schema documentation for external consumers — the three main entry points, pagination conventions, and error extensions","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"chart out the migration from our rest api to graphql for the mobile client, screen by screen, with a way to run both during the transition","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"subscriptions over websockets with auth on connect, and per-subscription authorization not just connection-level","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the loading skeleton flashes for cached queries, only show it after 200ms","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"our generated types are checked in and stale. regenerate and wire the generation into the build so it cant drift","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"mutations succeed but the ui doesn't update for one specific list. cache normalization thing probably, i dont know apollo well enough","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"review the schema for anything that will be painful to change later — non-nullable fields we're not sure about, enums that should be strings, that kind of thing","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"write the changelog for the schema changes this month, and mark which are additive vs breaking for clients","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the loading skeleton flashes for cached queries, only show it after 200ms","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"our generated types are checked in and stale. regenerate and wire the generation into the build so it cant drift","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"mutations succeed but the ui doesn't update for one specific list. cache normalization thing probably, i dont know apollo well enough","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"review the schema for anything that will be painful to change later — non-nullable fields we're not sure about, enums that should be strings, that kind of thing","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"write the changelog for the schema changes this month, and mark which are additive vs breaking for clients","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} {"prompt":"cron expression in the k8s cronjob is `0 0 * * 0` but it should run daily","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"here's the failing test, i think its a small thing:\n\nFAIL src/lib/slug.test.ts > slugify > handles unicode\n\nAssertionError: expected 'cafe-latte' to be 'café-latte'\n\n- Expected\n+ Received\n\n- café-latte\n+ cafe-latte\n\n at src/lib/slug.test.ts:22:31\n\nTest Files 1 failed (14)\n Tests 1 failed | 88 passed (89)\n\nwe changed slugify to strip diacritics last week for url safety, but this test wants them preserved. i think the TEST is what's wrong now, we decided ascii-only slugs. can you sort it out either way","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"pasted-context","lang":"en"} -{"prompt":"design the multi-step form framework we keep needing — validation per step, back without losing data, resumable from a saved draft","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"draft saving for the long application form, autosave every 10s and on blur, with a 'last saved' indicator","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"file upload field with drag and drop, per-file progress, cancel, and thumbnails for images","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"here's the failing test, i think its a small thing:\n\nFAIL src/lib/slug.test.ts > slugify > handles unicode\n\nAssertionError: expected 'cafe-latte' to be 'café-latte'\n\n- Expected\n+ Received\n\n- café-latte\n+ cafe-latte\n\n at src/lib/slug.test.ts:22:31\n\nTest Files 1 failed (14)\n Tests 1 failed | 88 passed (89)\n\nwe changed slugify to strip diacritics last week for url safety, but this test wants them preserved. i think the TEST is what's wrong now, we decided ascii-only slugs. can you sort it out either way","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"design the multi-step form framework we keep needing — validation per step, back without losing data, resumable from a saved draft","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"draft saving for the long application form, autosave every 10s and on blur, with a 'last saved' indicator","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"file upload field with drag and drop, per-file progress, cancel, and thumbnails for images","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"the required asterisk is on the optional fields and missing on the required ones, which is impressively wrong","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"we have four form libraries in the repo. standardize on react-hook-form and port the others, same validation behavior and error copy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"submitting the form twice fast creates two records. i thought the button disabled on submit","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"how does our validation handle a field that becomes required based on another field's value? point me at where that's implemented","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"we have four form libraries in the repo. standardize on react-hook-form and port the others, same validation behavior and error copy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"submitting the form twice fast creates two records. i thought the button disabled on submit","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"how does our validation handle a field that becomes required based on another field's value? point me at where that's implemented","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"help text for every field in the application form, short, and it needs to say WHY we're asking for the sensitive ones","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"plan the accessibility remediation and then fix the form labels as the first pass","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"explain what the middleware chain does then write it up for the readme","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} -{"prompt":"ok next bit","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"plan the accessibility remediation and then fix the form labels as the first pass","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"explain what the middleware chain does then write it up for the readme","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} {"prompt":"i want the design for our email sending. currently three services each talk to sendgrid directly with their own templates and nobody can tell what we sent a user. i'm thinking one service, template registry, per-user send log, and preference enforcement in one place","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"email service with template rendering, a send log, and unsubscribe enforcement that no caller can bypass","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"email preferences screen — per-category toggles, a digest frequency picker, and an unsubscribe-from-all with a confirm","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"reply-to on the notification emails is noreply@ but should be support@","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"our 22 email templates each have their own copy of the header and footer html. extract layouts, and the rendered output should be byte identical for the existing tests","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"our 22 email templates each have their own copy of the header and footer html. extract layouts, and the rendered output should be byte identical for the existing tests","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"emails render fine everywhere except outlook desktop where the layout collapses to one column","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"can a user who unsubscribed still get transactional emails? i want to know exactly which categories bypass the preference check","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"write the copy for the 6 lifecycle emails: welcome, day 3 tips, trial ending, trial ended, win-back, and the annual renewal reminder","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"can a user who unsubscribed still get transactional emails? i want to know exactly which categories bypass the preference check","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"write the copy for the 6 lifecycle emails: welcome, day 3 tips, trial ending, trial ended, win-back, and the annual renewal reminder","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"figure out how we'd support customer-specific smtp for enterprise, including bounce handling when it's their server","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"bounce and complaint webhook handling — suppress the address, notify the owner, and dont retry into a hard bounce","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the email preview in the admin renders raw html as text","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"template variables are referenced as {{user.name}} in some templates and {{name}} in others. normalize on the dotted form, rendered output unchanged","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"the email preview in the admin renders raw html as text","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"template variables are referenced as {{user.name}} in some templates and {{name}} in others. normalize on the dotted form, rendered output unchanged","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"one customer gets every email twice, has done for months, and their record looks identical to everyone elses","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"read the send path and tell me where a template rendering error would surface — does the job retry forever or dead letter","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"deliverability doc: our spf/dkim/dmarc setup, why the subdomain split exists, and what breaks if someone changes it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"sure whatever works","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"架构方案：把上传服务从单体里拆出来，需要支持断点续传和病毒扫描，先给方案不要写代码","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"zh"} -{"prompt":"virus scanning on upload via clamav in a sidecar, quarantine on detection, and the user sees a clear state not a generic error","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"file browser grid with type icons, multi select, and a details pane that slides in from the right","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"max upload size says 10MB in the ui and 8MB in the server config","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"read the send path and tell me where a template rendering error would surface — does the job retry forever or dead letter","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"deliverability doc: our spf/dkim/dmarc setup, why the subdomain split exists, and what breaks if someone changes it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"架构方案：把上传服务从单体里拆出来，需要支持断点续传和病毒扫描，先给方案不要写代码","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"zh"} +{"prompt":"virus scanning on upload via clamav in a sidecar, quarantine on detection, and the user sees a clear state not a generic error","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"file browser grid with type icons, multi select, and a details pane that slides in from the right","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"max upload size says 10MB in the ui and 8MB in the server config","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"the storage abstraction has s3 assumptions leaking through it — bucket names in the interface. clean the interface, both backends keep working","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"resumable uploads resume from the wrong offset when the client reconnects on a different pod","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"walk me through what happens if the scan sidecar is down when an upload arrives","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"docs for the upload api — the multipart protocol, resumption, size limits, and the scan states a client might see","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"plan for supporting folders and nested permissions in the file store. currently flat with per-file acls","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"share links with optional password and expiry, and a view-only mode that doesnt allow download","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the breadcrumb truncates the middle folders on narrow screens but hides the wrong end","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"our path handling uses string concat in 20 places, some with a leading slash some without. one helper, same resolved paths","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"resumable uploads resume from the wrong offset when the client reconnects on a different pod","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"walk me through what happens if the scan sidecar is down when an upload arrives","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"docs for the upload api — the multipart protocol, resumption, size limits, and the scan states a client might see","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"plan for supporting folders and nested permissions in the file store. currently flat with per-file acls","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"share links with optional password and expiry, and a view-only mode that doesnt allow download","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the breadcrumb truncates the middle folders on narrow screens but hides the wrong end","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"our path handling uses string concat in 20 places, some with a leading slash some without. one helper, same resolved paths","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"downloads of files with non-ascii names get mangled filenames on windows but only through the browser, curl is fine","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"audit whether a share link can be used to enumerate other files in the same folder","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"user-facing help page about sharing — the link types, what each one allows, and how to revoke","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"propose the approach for versioning files. keep n versions or all, dedupe by content hash, and how the ui presents history","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"audit whether a share link can be used to enumerate other files in the same folder","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"user-facing help page about sharing — the link types, what each one allows, and how to revoke","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"propose the approach for versioning files. keep n versions or all, dedupe by content hash, and how the ui presents history","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"content-addressed dedupe for uploads with reference counting, and a gc job that's safe to run while writes are happening","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"version history panel: list with timestamps and authors, preview, restore, and a diff for text files","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"gc runs at 3am utc which is peak for our apac customers, move it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"the sha256 helper appears in 6 files with slightly different chunk sizes. one implementation, same digests obviously","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"restoring an old version sometimes restores the wrong one, off by one in the ordering when two versions share a timestamp","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"explain the reference counting in the dedupe store and whether a crash mid-gc can orphan or delete live data","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"write the internal design doc for the dedupe store from the code as it exists, we never wrote one","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"plan the whole thing and then do the first slice","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"check the pr for correctness and tidy up the naming while you're there","purpose":"review","secondary":"refactor","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} -{"prompt":"resume","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"figure out how we do zero-downtime schema changes as a policy, not per-migration heroics. expand-contract, tooling, and how CI blocks a dangerous one","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"version history panel: list with timestamps and authors, preview, restore, and a diff for text files","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"gc runs at 3am utc which is peak for our apac customers, move it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"the sha256 helper appears in 6 files with slightly different chunk sizes. one implementation, same digests obviously","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"restoring an old version sometimes restores the wrong one, off by one in the ordering when two versions share a timestamp","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"explain the reference counting in the dedupe store and whether a crash mid-gc can orphan or delete live data","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"write the internal design doc for the dedupe store from the code as it exists, we never wrote one","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"plan the whole thing and then do the first slice","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"check the pr for correctness and tidy up the naming while you're there","purpose":"review","secondary":"refactor","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"figure out how we do zero-downtime schema changes as a policy, not per-migration heroics. expand-contract, tooling, and how CI blocks a dangerous one","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"migration linter in CI that rejects a migration adding a not-null column without a default, or taking an access exclusive lock on a big table","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"migration status page for the admin: which migrations have run per environment, and flag drift","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the migration timeout is 5s which fails every real migration, make it 15 minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"our 340 migrations include 40 that were edited after being applied. squash the pre-2025 ones into a baseline schema, verified identical against a prod dump","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"a migration applied cleanly in staging and hung for 20 minutes in prod on the same table size","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"review the pending migration for lock risk and tell me if it needs a maintenance window","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"document our migration workflow: naming, the review checklist, and the rollback expectations per type of change","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"migration status page for the admin: which migrations have run per environment, and flag drift","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the migration timeout is 5s which fails every real migration, make it 15 minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"our 340 migrations include 40 that were edited after being applied. squash the pre-2025 ones into a baseline schema, verified identical against a prod dump","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"a migration applied cleanly in staging and hung for 20 minutes in prod on the same table size","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"review the pending migration for lock risk and tell me if it needs a maintenance window","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"document our migration workflow: naming, the review checklist, and the rollback expectations per type of change","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"what's the story for testing against a real database in CI without 20 minutes of setup. template databases? snapshots? write the plan","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"testcontainers setup for the integration suite with a shared postgres per run and per-test schema isolation","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the test db name is hardcoded so two parallel runs clobber each other","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"our tests share mutable fixture state through module level globals. make each test independent, same assertions, and it should pass with random ordering","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"tests pass individually and fail as a suite, and which one fails changes depending on the order","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the test db name is hardcoded so two parallel runs clobber each other","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"our tests share mutable fixture state through module level globals. make each test independent, same assertions, and it should pass with random ordering","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"tests pass individually and fail as a suite, and which one fails changes depending on the order","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"look at our test suite and tell me what's actually covered vs what just executes without asserting anything meaningful","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"testing guide for the repo: what layer to test what at, our fixture conventions, and when a test is allowed to hit the network","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"list view for the audit log with filters by actor, action and date, virtualized, and a permalink per entry","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"eh nvm do the other thing","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"quick one — need `acme init` to detect an existing config and offer to merge instead of overwriting","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"quick one — need `acme init` to detect an existing config and offer to merge instead of overwriting","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} {"prompt":"stand up the plugin loader for the cli: discover from ~/.acme/plugins and PATH, version check against the host api, and fail loudly on a mismatch rather than half-loading","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"help text is 200 lines of one flat list. group by topic with short section headers, and the examples move to the bottom","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"spinner in the cli doesn't clear on ctrl-c and leaves the terminal cursor hidden","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"curious about the plugin api surface before we commit to it publicly — what are we exposing that we'd regret, read plugin/host.go and tell me","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"help text is 200 lines of one flat list. group by topic with short section headers, and the examples move to the bottom","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"spinner in the cli doesn't clear on ctrl-c and leaves the terminal cursor hidden","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"curious about the plugin api surface before we commit to it publicly — what are we exposing that we'd regret, read plugin/host.go and tell me","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"trim the duplicate flag parsing — every subcommand re-declares --profile, --verbose and --json. one shared flag set, identical help output per command","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"output is garbled when you pipe it — ansi codes in the json. should be detecting a tty somewhere and clearly isn't","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"cli reference docs, one page per command, generated from the command definitions so they can't drift","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"so the thing i keep circling on is whether the cli should talk to the api directly or go through a local daemon. daemon gives us caching and a socket for the editor plugin but it's another thing to install and keep alive. write up both and pick","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"output is garbled when you pipe it — ansi codes in the json. should be detecting a tty somewhere and clearly isn't","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"cli reference docs, one page per command, generated from the command definitions so they can't drift","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"so the thing i keep circling on is whether the cli should talk to the api directly or go through a local daemon. daemon gives us caching and a socket for the editor plugin but it's another thing to install and keep alive. write up both and pick","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"fastapi endpoint for bulk tag assignment, accepts up to 1000 ids, partial success reporting per id, all in one transaction per chunk","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the async db session is created per request but the background tasks reuse it after the response, which is why we get those closed-session errors. i think. sort it out properly","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"the async db session is created per request but the background tasks reuse it after the response, which is why we get those closed-session errors. i think. sort it out properly","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"pydantic v1 to v2 across the api models, validators included, same request/response shapes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the uvicorn worker count is 1 in the container","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"point me at where the request timeout is enforced — i see a setting in three places and none of them seem to be the one that fires","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"requests pile up and the event loop stalls for seconds at a time, roughly when the export endpoint is being used. i thought that was async","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the uvicorn worker count is 1 in the container","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"point me at where the request timeout is enforced — i see a setting in three places and none of them seem to be the one that fires","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"requests pile up and the event loop stalls for seconds at a time, roughly when the export endpoint is being used. i thought that was async","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"swiftui: the compose sheet needs an attachment tray, a send button that disables on empty, and it must not lose the draft if you swipe it away by accident","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"keyboard avoidance is broken in the compose sheet on ios 26, the toolbar sits under the keyboard","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"corner radius on the attachment thumbnails should be 8 not 12, matching the message bubbles","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"map out how we bring the mac app to feature parity. right now it's a catalyst build and it shows — no menu bar commands, no multiple windows, no keyboard nav. i want phases and an honest estimate","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"give me a walkthrough of how our undo manager interacts with the swiftdata context, i don't trust it and want to understand before touching anything","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"write the release notes and the app store what's-new for 4.1, plus the internal note about the schema migration for support","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"ticket says:\n\nTITLE: `acme sync` silently succeeds when the remote rejects half the batch\nREPRO:\n 1. create 40 local records, 3 with names > 255 chars\n 2. run `acme sync --push`\n 3. output: \"synced 40 records\"\n 4. server has 37\nEXPECTED: non-zero exit, report which records failed and why\nNOTES: the api returns 207 with a per-item status array. we only check the http status.\n\nplease fix and make the exit code meaningful","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} -{"prompt":"pull the shared http retry/auth code out of the cli and the editor plugin into one package, both consumers behave identically after","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"progress output for long operations — a proper multi-line status that redraws, degrades to plain lines when not a tty","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"and now?","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"…thinking about the worker topology again. one queue with priorities, or separate queues per job class with dedicated pools. we have 30 job types, three of them are latency sensitive and the rest are batch. write the analysis and a recommendation","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"keyboard avoidance is broken in the compose sheet on ios 26, the toolbar sits under the keyboard","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"corner radius on the attachment thumbnails should be 8 not 12, matching the message bubbles","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"map out how we bring the mac app to feature parity. right now it's a catalyst build and it shows — no menu bar commands, no multiple windows, no keyboard nav. i want phases and an honest estimate","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"give me a walkthrough of how our undo manager interacts with the swiftdata context, i don't trust it and want to understand before touching anything","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"write the release notes and the app store what's-new for 4.1, plus the internal note about the schema migration for support","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"ticket says:\n\nTITLE: `acme sync` silently succeeds when the remote rejects half the batch\nREPRO:\n 1. create 40 local records, 3 with names > 255 chars\n 2. run `acme sync --push`\n 3. output: \"synced 40 records\"\n 4. server has 37\nEXPECTED: non-zero exit, report which records failed and why\nNOTES: the api returns 207 with a per-item status array. we only check the http status.\n\nplease fix and make the exit code meaningful","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"pull the shared http retry/auth code out of the cli and the editor plugin into one package, both consumers behave identically after","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"progress output for long operations — a proper multi-line status that redraws, degrades to plain lines when not a tty","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"…thinking about the worker topology again. one queue with priorities, or separate queues per job class with dedicated pools. we have 30 job types, three of them are latency sensitive and the rest are batch. write the analysis and a recommendation","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"job scheduling with priorities and per-tenant fairness so one big customer can't starve everyone, python + redis streams","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"queue dashboard: depth per queue, oldest job age, workers online, and a retry-all for the dlq with a count confirmation","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the dlq alert threshold is 1 and it pages for a single poison message, make it 25 over 10 minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"queue dashboard: depth per queue, oldest job age, workers online, and a retry-all for the dlq with a count confirmation","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"the dlq alert threshold is 1 and it pages for a single poison message, make it 25 over 10 minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"every job class reimplements the same enqueue-with-dedupe-key logic slightly differently. one base class, and prove the dedupe behavior is unchanged per job type","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"jobs get processed twice when a worker is oomkilled mid-job. i know why in general terms but not what OUR code does about it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"is the visibility timeout longer than our slowest job? check the numbers, i suspect one job class exceeds it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"jobs get processed twice when a worker is oomkilled mid-job. i know why in general terms but not what OUR code does about it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"is the visibility timeout longer than our slowest job? check the numbers, i suspect one job class exceeds it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} {"prompt":"runbook for a backed up queue: how to tell if it's a slow consumer or a producer spike, and the safe ways to shed load","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"hook up structured logging in the workers with the job id, tenant and attempt on every line","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"hook up structured logging in the workers with the job id, tenant and attempt on every line","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"the retry count shows attempt 0 for first tries, off by one in the display","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"roadmap for the api gateway work — auth offload, rate limits, request validation from the openapi spec. what order, and what we do about the services that currently do their own auth","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"request validation middleware driven by the openapi spec, rejecting with the same error shape as our handlers do today","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"our openapi spec is hand maintained and lies in about 15 places. generate it from the code, and list every place the old spec was wrong","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"explain the difference between what the gateway rejects and what the service rejects, i want to know where a bad request actually dies","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"gateway adds 80ms to every request and the upstream reports 4ms. that gap has to be the auth lookup but the cache hit rate says 99%","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"api playground page — endpoint picker, editable request body, send, and show the curl equivalent","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the gateway timeout is shorter than the upstream's, which means we return 504 while the work completes. align them","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"consolidate the three request-id header names we accept into one canonical, still accepting the legacy ones on input","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"request validation middleware driven by the openapi spec, rejecting with the same error shape as our handlers do today","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"our openapi spec is hand maintained and lies in about 15 places. generate it from the code, and list every place the old spec was wrong","purpose":"backendImpl","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"explain the difference between what the gateway rejects and what the service rejects, i want to know where a bad request actually dies","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"gateway adds 80ms to every request and the upstream reports 4ms. that gap has to be the auth lookup but the cache hit rate says 99%","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"api playground page — endpoint picker, editable request body, send, and show the curl equivalent","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the gateway timeout is shorter than the upstream's, which means we return 504 while the work completes. align them","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"consolidate the three request-id header names we accept into one canonical, still accepting the legacy ones on input","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"design the tenant isolation story for the gateway — noisy neighbor protection, per-tenant quotas, and what we do when one tenant is under attack","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"sort out the plan for the search rewrite and then build the indexer","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"take a look at the caching layer and clean up the naming while you're in there","purpose":"review","secondary":"refactor","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} -{"prompt":"onwards","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"got a note from the security team, pasting it as is:\n\n> Finding S-2026-041 (Medium)\n> The password reset endpoint (POST /auth/reset/request) responds with 404 when the email\n> is not registered and 204 when it is. This allows account enumeration.\n> Additionally the reset token is a 6-digit numeric code with a 30 minute TTL and\n> no attempt limiting observed on POST /auth/reset/confirm.\n> Recommendation: uniform response, longer token entropy, and rate limiting per\n> account and per IP.\n>\n> Please advise on remediation timeline.\n\nneed this handled","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"take a look at the caching layer and clean up the naming while you're in there","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"got a note from the security team, pasting it as is:\n\n> Finding S-2026-041 (Medium)\n> The password reset endpoint (POST /auth/reset/request) responds with 404 when the email\n> is not registered and 204 when it is. This allows account enumeration.\n> Additionally the reset token is a 6-digit numeric code with a 30 minute TTL and\n> no attempt limiting observed on POST /auth/reset/confirm.\n> Recommendation: uniform response, longer token entropy, and rate limiting per\n> account and per IP.\n>\n> Please advise on remediation timeline.\n\nneed this handled","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} {"prompt":"webauthn registration and login, resident keys, and a fallback path that still works if the browser lacks support","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"passkey prompt ui with the platform sheet, and a clear explanation for people who've never seen one","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"session cookie is missing Secure in the staging config","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"our permission checks are string comparisons on role names scattered everywhere. introduce typed permissions with a single check function, identical allow/deny for every existing role","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"an org owner lost access to their own org and the only change was inviting a member. i cannot reproduce it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"tell me whether our csrf protection covers the json api or only the form posts","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"security page for the docs: what we do about encryption, sessions, mfa, and our vuln disclosure process. factual, no puffery","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"figure out how we'd do granular sharing permissions — view/comment/edit per resource, inherited from folders, with overrides. write the model","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"role editor ui: matrix of permissions by resource type, with inherited values shown greyed and overrides highlighted","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the 'admin' label in the members list should say 'owner' for the org creator","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"audit log for every permission change, who granted what to whom, immutable, and queryable by resource","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"a member with view-only can still hit the update endpoint directly and it works. that's obviously bad, find where the check is missing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"our permission checks are string comparisons on role names scattered everywhere. introduce typed permissions with a single check function, identical allow/deny for every existing role","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"an org owner lost access to their own org and the only change was inviting a member. i cannot reproduce it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"tell me whether our csrf protection covers the json api or only the form posts","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"security page for the docs: what we do about encryption, sessions, mfa, and our vuln disclosure process. factual, no puffery","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"figure out how we'd do granular sharing permissions — view/comment/edit per resource, inherited from folders, with overrides. write the model","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"role editor ui: matrix of permissions by resource type, with inherited values shown greyed and overrides highlighted","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the 'admin' label in the members list should say 'owner' for the org creator","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"audit log for every permission change, who granted what to whom, immutable, and queryable by resource","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"a member with view-only can still hit the update endpoint directly and it works. that's obviously bad, find where the check is missing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"write up how permission inheritance works for the help center, with a worked example that has an override","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"review the invite flow for anything that lets someone escalate their own role","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"review the invite flow for anything that lets someone escalate their own role","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"hmm, wondering if the right move is to just... ok. plan how we support customer-managed encryption keys. what's encrypted with what, key rotation, and what happens to backups","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"envelope encryption for the sensitive columns, kms-backed data keys cached in memory with a short ttl","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the encryption key id column is nullable and shouldn't be","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"envelope encryption for the sensitive columns, kms-backed data keys cached in memory with a short ttl","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} +{"prompt":"the encryption key id column is nullable and shouldn't be","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"our crypto helpers are spread across three modules with two different iv strategies. consolidate onto the correct one and re-encrypt nothing, just handle both on read","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"decryption fails for records written between march and may. those were written by the version with the old key derivation and i don't know what changed","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"key management doc — where keys live, who can access them, rotation cadence, and the break-glass procedure","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"settings ui for byok: key arn field, a test button that proves we can encrypt and decrypt, and a scary confirm before switching","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"does anything log the plaintext before encryption? grep-level answer is fine but i want you to actually check the paths","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"meh, do the simple version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"decryption fails for records written between march and may. those were written by the version with the old key derivation and i don't know what changed","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"key management doc — where keys live, who can access them, rotation cadence, and the break-glass procedure","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"settings ui for byok: key arn field, a test button that proves we can encrypt and decrypt, and a scary confirm before switching","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"does anything log the plaintext before encryption? grep-level answer is fine but i want you to actually check the paths","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"j'aimerais un plan pour découper notre service de notifications en deux : l'envoi et les préférences. on a 40 endpoints et pas de tests d'intégration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"fr"} {"prompt":"in-app notification center backend: fan-out on write, per-user read state, and a cap so a heavy account doesn't accumulate 100k rows","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"notification bell with an unread count, dropdown list, and a subtle animation when a new one lands while you're looking at it","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the count caps at 99 but shows '99' not '99+'","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"the count caps at 99 but shows '99' not '99+'","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"we build notification payloads in 14 places with 14 slightly different shapes. one builder, one shape, and the clients keep working","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"notifications arrive out of order in the list, timestamps look right in the db","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"how do we decide whether something goes to email, push, in-app, or all three? point me at the actual decision code","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"docs for the notification types — every event, the default channels, and which ones users can turn off","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"plan the digest emails: what gets batched, the windowing, timezone handling per user, and how we avoid sending an empty digest","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"notifications arrive out of order in the list, timestamps look right in the db","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"how do we decide whether something goes to email, push, in-app, or all three? point me at the actual decision code","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"docs for the notification types — every event, the default channels, and which ones users can turn off","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"plan the digest emails: what gets batched, the windowing, timezone handling per user, and how we avoid sending an empty digest","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"digest builder job that assembles per-user summaries at their local 8am, skipping users with nothing new","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"mute controls: per-project and per-thread, with a snooze-until picker","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"digest sends at 8am utc for everyone regardless of their timezone setting","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"mute controls: per-project and per-thread, with a snooze-until picker","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"digest sends at 8am utc for everyone regardless of their timezone setting","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"the batch window constant is 15 minutes, we agreed on 5","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"check whether a muted thread can still trigger a push through the mention path","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"check whether a muted thread can still trigger a push through the mention path","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} {"prompt":"our timezone handling uses three different libraries depending on the file. standardize, and verify the digest send times don't move for existing users","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"write the copy for the digest email template, including the empty-ish case where there's only one item","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"propose how we'd let users build their own alert rules — conditions on our event stream, thresholds, and delivery. i want the model and the ui shape sketched","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"rule evaluation engine over the event stream, windowed aggregates, and dedupe so a flapping condition doesn't spam","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"rule builder ui: condition rows with and/or grouping, a live preview of how many events matched in the last day","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"propose how we'd let users build their own alert rules — conditions on our event stream, thresholds, and delivery. i want the model and the ui shape sketched","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"rule evaluation engine over the event stream, windowed aggregates, and dedupe so a flapping condition doesn't spam","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"rule builder ui: condition rows with and/or grouping, a live preview of how many events matched in the last day","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"rules with an empty condition list match everything, they should match nothing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"a rule fires repeatedly for the same underlying event, dozens of times, and the dedupe key looks correct to me","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain the windowing semantics we implemented — tumbling or sliding? the code comments say both in different places","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"user docs for alert rules, with three example rules people actually want and the gotcha about evaluation delay","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"same","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"a rule fires repeatedly for the same underlying event, dozens of times, and the dedupe key looks correct to me","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain the windowing semantics we implemented — tumbling or sliding? the code comments say both in different places","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"user docs for alert rules, with three example rules people actually want and the gotcha about evaluation delay","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"picking the import pipeline back up from last week — next thing is the csv column type inference. dates in 6 formats, numbers with thousands separators, and booleans as yes/no/1/0. make it configurable per column with a sensible guess","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"plan out the whole import experience end to end — upload, map, validate, preview, commit, and what happens when 3% of rows fail","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"error report screen for a partial import: row number, the offending value, the reason, and a downloadable csv of just the failures","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"we say 'invalid date' without saying which column or row","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"the csv, xlsx and json importers each have their own validation. share it — one validator, three readers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"xlsx imports lose the leading zeros on postcodes but csv doesn't","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"read the importer and tell me what happens if the process dies at 60% — do we have a half-imported dataset","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"template csv plus a doc explaining every column, required vs optional, and the accepted formats","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"export the other way too — full account export as a zip of csvs plus the attachments, generated async with an email when ready","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"export button gives no feedback for the 30 seconds before the download starts","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"error report screen for a partial import: row number, the offending value, the reason, and a downloadable csv of just the failures","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"we say 'invalid date' without saying which column or row","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"the csv, xlsx and json importers each have their own validation. share it — one validator, three readers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"xlsx imports lose the leading zeros on postcodes but csv doesn't","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"read the importer and tell me what happens if the process dies at 60% — do we have a half-imported dataset","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"template csv plus a doc explaining every column, required vs optional, and the accepted formats","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"export the other way too — full account export as a zip of csvs plus the attachments, generated async with an email when ready","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"export button gives no feedback for the 30 seconds before the download starts","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} {"prompt":"the export filename has a colon in it which windows rejects","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"figure out our gdpr data export and deletion story properly, including the data in our warehouse and the backups, and write the plan","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"figure out our gdpr data export and deletion story properly, including the data in our warehouse and the backups, and write the plan","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"verify that the deletion job actually covers every table with user data — enumerate the tables and check each one against the job","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"our data retention doc says 90 days for logs and 30 for exports. the code says otherwise in both cases. update the doc to match reality and flag anything that looks like a compliance problem","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"deletion requests complete but the user's data reappears in search a day later","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"design and then build the first version of the activity feed, i'll take over the ui","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"our data retention doc says 90 days for logs and 30 for exports. the code says otherwise in both cases. update the doc to match reality and flag anything that looks like a compliance problem","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"deletion requests complete but the user's data reappears in search a day later","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"design and then build the first version of the activity feed, i'll take over the ui","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"find out why the export job stalls and once you know, add a note to the runbook","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"por favor sigue","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"es"} -{"prompt":"here's the whole thread from #incident-4419, i've only skimmed it:\n\n[09:12] otto: api error rate 4% and climbing\n[09:13] otto: mostly 500s from /v1/timeline\n[09:14] priya: rolled back the 09:02 deploy, no change\n[09:16] priya: db cpu is 40%, connections normal\n[09:18] otto: the 500s all have a redis timeout in the trace\n[09:19] priya: redis cpu 12%, memory 61%, no evictions\n[09:22] otto: hold on, redis latency p99 is 800ms and it was 2ms an hour ago\n[09:24] priya: SLOWLOG has a bunch of KEYS calls?? who is calling KEYS\n[09:26] otto: error rate down to 0.4% on its own\n[09:31] otto: back to normal, nothing changed\n\nnobody knows what happened. figure it out","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"replace the KEYS usage with SCAN wherever it appears, and add a lint rule so it can't come back","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"here's the whole thread from #incident-4419, i've only skimmed it:\n\n[09:12] otto: api error rate 4% and climbing\n[09:13] otto: mostly 500s from /v1/timeline\n[09:14] priya: rolled back the 09:02 deploy, no change\n[09:16] priya: db cpu is 40%, connections normal\n[09:18] otto: the 500s all have a redis timeout in the trace\n[09:19] priya: redis cpu 12%, memory 61%, no evictions\n[09:22] otto: hold on, redis latency p99 is 800ms and it was 2ms an hour ago\n[09:24] priya: SLOWLOG has a bunch of KEYS calls?? who is calling KEYS\n[09:26] otto: error rate down to 0.4% on its own\n[09:31] otto: back to normal, nothing changed\n\nnobody knows what happened. figure it out","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"replace the KEYS usage with SCAN wherever it appears, and add a lint rule so it can't come back","purpose":"refactor","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"redis maxmemory-policy is noeviction, should be allkeys-lru for the cache instance","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"plan the split of our single redis into a cache instance and a queue instance, including the migration with no lost jobs","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"cache warming on deploy for the top 200 tenants so we don't thundering-herd the db every release","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"plan the split of our single redis into a cache instance and a queue instance, including the migration with no lost jobs","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"cache warming on deploy for the top 200 tenants so we don't thundering-herd the db every release","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"cache stats panel in the admin: hit rate per key prefix, memory by prefix, and the top 20 largest keys","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"explain our cache invalidation for the tenant settings object — i count three writers and one of them doesn't invalidate","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"write the caching guidelines: what's cacheable, key naming, ttls by data class, and the rule about never caching authorization decisions","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"the ttl on the settings cache is 24h with no invalidation, that's why changes take a day. drop it to 60s as a stopgap","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"cache keys don't include the schema version so after a deploy we deserialize old shapes into new structs. tighten that up properly","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"after a deploy we get a burst of nil-pointer errors for about 30 seconds then it's fine. something about deserializing cached objects i think but i want certainty","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"sketch what a proper read-through cache layer looks like for us so callers stop hand-rolling get-or-set everywhere","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"read-through cache helper with single-flight so 400 concurrent misses become one db query","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"loading states flash on cached data because we always start in loading. only show loading if we don't have a cached value","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"wondering whether the single-flight actually dedupes across pods or just within one, tell me what our implementation does","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"ok fine","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"need the architecture for our webhooks-out feature written down before we build it. customer-configured endpoints, at-least-once, signed, replayable from the ui, and it must not be able to take down our workers when a customer's endpoint hangs for 30 seconds","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"explain our cache invalidation for the tenant settings object — i count three writers and one of them doesn't invalidate","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"write the caching guidelines: what's cacheable, key naming, ttls by data class, and the rule about never caching authorization decisions","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the ttl on the settings cache is 24h with no invalidation, that's why changes take a day. drop it to 60s as a stopgap","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"cache keys don't include the schema version so after a deploy we deserialize old shapes into new structs. tighten that up properly","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"after a deploy we get a burst of nil-pointer errors for about 30 seconds then it's fine. something about deserializing cached objects i think but i want certainty","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"sketch what a proper read-through cache layer looks like for us so callers stop hand-rolling get-or-set everywhere","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"read-through cache helper with single-flight so 400 concurrent misses become one db query","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"loading states flash on cached data because we always start in loading. only show loading if we don't have a cached value","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"wondering whether the single-flight actually dedupes across pods or just within one, tell me what our implementation does","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"need the architecture for our webhooks-out feature written down before we build it. customer-configured endpoints, at-least-once, signed, replayable from the ui, and it must not be able to take down our workers when a customer's endpoint hangs for 30 seconds","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"webhook delivery worker with per-endpoint circuit breaking, a 10s timeout, and delivery attempts recorded for the ui","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"webhook detail page: endpoint config, recent deliveries with status and duration, a replay button, and the request/response bodies","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the signature header name has a typo, 'X-Acme-Signaure'. it's public so we need both for a while","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"the signature header name has a typo, 'X-Acme-Signaure'. it's public so we need both for a while","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"our event serialization for webhooks duplicates the api serializers with small differences. share them so the payloads can't drift, and diff the output on the fixtures","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"one customer sees deliveries marked failed that they definitely received and processed","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"is our retry schedule actually exponential? the numbers in the config look linear to me","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"webhook integration guide: event catalog, signature verification in three languages, retry behavior, and how to test locally","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"plan the event catalog itself — naming convention, versioning of payload shapes, and how we add a field without breaking anyone","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"one customer sees deliveries marked failed that they definitely received and processed","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"is our retry schedule actually exponential? the numbers in the config look linear to me","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"webhook integration guide: event catalog, signature verification in three languages, retry behavior, and how to test locally","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"plan the event catalog itself — naming convention, versioning of payload shapes, and how we add a field without breaking anyone","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"local tunnel helper in the cli so integrators can receive webhooks on localhost without ngrok","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"event picker for the webhook config — grouped checkboxes with a select-all per group and a count of selected","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"we send events for internal state changes customers shouldn't see, filter those out of the catalog","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"event picker for the webhook config — grouped checkboxes with a select-all per group and a count of selected","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"we send events for internal state changes customers shouldn't see, filter those out of the catalog","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"endpoint verification on save — send a test ping and require a 2xx before enabling, with a clear error if it fails","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"tell me if a customer could use the webhook config to make us send requests to internal addresses","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"tell me if a customer could use the webhook config to make us send requests to internal addresses","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"changelog entry for the webhook signature change, with the migration window and exactly what integrators need to do","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"extract the ssrf-safe http client we half-wrote in the pdf renderer and use it for webhooks too","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"deliveries stop entirely for one endpoint with no failures logged, and resume if you toggle it off and on","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"das Retry-Intervall ist auf 1 Sekunde festgelegt, das sollte exponentiell sein — plan es erst, dann bau es","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"de"} +{"prompt":"extract the ssrf-safe http client we half-wrote in the pdf renderer and use it for webhooks too","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"deliveries stop entirely for one endpoint with no failures logged, and resume if you toggle it off and on","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"das Retry-Intervall ist auf 1 Sekunde festgelegt, das sollte exponentiell sein — plan es erst, dann bau es","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"de"} {"prompt":"review the delivery worker and fix anything obviously wrong as you go","purpose":"review","secondary":"quickFix","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"sidebar item spacing feels off, tighten it up a bit","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"make the dashboard feel faster","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"sidebar item spacing feels off, tighten it up a bit","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"make the dashboard feel faster","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"please put together the design for our model serving layer. we have 6 models, two need gpu, and the traffic is spiky — 10x for 20 minutes twice a day. i want to see the options for autoscaling and what the cold start cost is for each","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"triton inference server config for the two gpu models, dynamic batching with a 20ms queue delay, and a health endpoint the mesh understands","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"model registry ui: versions per model, which is serving in which env, and a promote action with a confirm that shows the eval delta","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"model registry ui: versions per model, which is serving in which env, and a promote action with a confirm that shows the eval delta","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the inference timeout is 2s and the p99 is 2.4s, raise it to 5","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"our preprocessing runs in the request handler for one model and in a sidecar for another. pick the sidecar approach for both, outputs must be numerically identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"gpu memory fragments over a day of serving and eventually a request OOMs even though total usage is under 40%","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"could you explain how the batching interacts with our per-request timeout? i want to know whether a slow batch can blow the deadline for everyone in it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"write the api docs for the inference endpoint — input schema per model, the batching behavior clients should expect, and the error codes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"gpu memory fragments over a day of serving and eventually a request OOMs even though total usage is under 40%","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"could you explain how the batching interacts with our per-request timeout? i want to know whether a slow batch can blow the deadline for everyone in it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"write the api docs for the inference endpoint — input schema per model, the batching behavior clients should expect, and the error codes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"kotlin: paging 3 for the transactions list, with a room-backed remote mediator so it works offline","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the transaction row layout: amount right-aligned and monospaced, merchant name truncating with the category chip never squeezed out","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"negative amounts show a minus AND red parentheses, pick one","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"would you mind planning the modularization of the android app? one big :app module today, 90k lines, and build times are 6 minutes incremental","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"would you mind planning the modularization of the android app? one big :app module today, 90k lines, and build times are 6 minutes incremental","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"our fragments and composables both exist for the same three screens because of a half-finished migration. finish it — delete the fragments, no behavior change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"app takes 4.5s to first frame on a mid-range device, was 1.8s three releases ago. no obvious single culprit in the startup trace","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"is the datastore migration from sharedprefs actually idempotent if the app is killed mid-migration? tell me what the code does","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"contribution guide for the android repo — module boundaries, the di conventions, and how to add a new screen","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"nix flake for the dev environment so people stop having version drift, with a devshell that includes the toolchains for all three services","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"our CI takes 34 minutes. i want a plan to get it under 10 — caching, splitting, what we move to a nightly job. include what we give up","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the docker build ignores .dockerignore because it's in the wrong directory","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"consolidate our four dockerfiles into a multi-stage one with targets, same final images by digest-equivalent content","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"builds are cache-missing on every run even though nothing in the lockfile changed. buildkit with a registry cache","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"app takes 4.5s to first frame on a mid-range device, was 1.8s three releases ago. no obvious single culprit in the startup trace","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"is the datastore migration from sharedprefs actually idempotent if the app is killed mid-migration? tell me what the code does","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"contribution guide for the android repo — module boundaries, the di conventions, and how to add a new screen","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"nix flake for the dev environment so people stop having version drift, with a devshell that includes the toolchains for all three services","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"our CI takes 34 minutes. i want a plan to get it under 10 — caching, splitting, what we move to a nightly job. include what we give up","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the docker build ignores .dockerignore because it's in the wrong directory","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"consolidate our four dockerfiles into a multi-stage one with targets, same final images by digest-equivalent content","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"builds are cache-missing on every run even though nothing in the lockfile changed. buildkit with a registry cache","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"take a look at our github actions permissions — i think several jobs have write access they don't need","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"document the release process: tags, what CI does automatically, the manual steps, and how to cut a hotfix","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"build status widget for our internal dashboard, per-branch, with the duration trend as a sparkline","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"just keep going","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"would you take a look at this and tell me what's happening? i've been at it since this morning:\n\n$ ./gradlew :app:assembleRelease\n\n> Task :app:minifyReleaseWithR8 FAILED\nAGPBI: {\"kind\":\"error\",\"text\":\"Missing class com.acme.sync.proto.SyncEnvelope$Builder (referenced from: void com.acme.sync.SyncClient.push(java.util.List))\",\"sources\":[{}],\"tool\":\"R8\"}\nAGPBI: {\"kind\":\"error\",\"text\":\"Missing class io.grpc.okhttp.OkHttpChannelBuilder (referenced from: io.grpc.ManagedChannelProvider)\",\"sources\":[{}],\"tool\":\"R8\"}\n\nFAILURE: Build failed with an exception.\n* What went wrong:\nExecution failed for task ':app:minifyReleaseWithR8'.\n> A failure occurred while executing com.android.build.gradle.internal.tasks.R8Task$R8Runnable\n > Compilation failed to complete, position: null, origin: null\n\ndebug builds are fine. we added the grpc dependency last week","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} {"prompt":"grpc client for the sync service in the android app, with a channel that survives network changes and doesn't leak on config change","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"sync status indicator in the toolbar: idle, syncing with a spinner, error with a tap-to-retry, and 'last synced 4m ago' text","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the sync interval is 15 minutes minimum per workmanager but we set 5, so it silently becomes 15. say so in the settings copy","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"plan the conflict resolution ui for sync conflicts, because right now last-write-wins silently and users lose edits","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the sync interval is 15 minutes minimum per workmanager but we set 5, so it silently becomes 15. say so in the settings copy","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"plan the conflict resolution ui for sync conflicts, because right now last-write-wins silently and users lose edits","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"our repositories all implement the same cache-then-network pattern with hand-rolled variations. one pattern, and the observable emission order must stay the same","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"pull-to-refresh spins forever if the request fails without an exception, like on a captive portal","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"explain the ordering guarantees of our outbox in the android client, specifically across app restarts","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"write the protocol doc for the sync api — envelope format, the cursor semantics, and how a client recovers from a rejected batch","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"pull-to-refresh spins forever if the request fails without an exception, like on a captive portal","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"explain the ordering guarantees of our outbox in the android client, specifically across app restarts","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"write the protocol doc for the sync api — envelope format, the cursor semantics, and how a client recovers from a rejected batch","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"sketch the strategy for supporting tablets and foldables properly, not just stretched phone layouts","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"two-pane layout on wide screens with the list on the left, and the selection should survive a fold/unfold","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"landscape on phones shows a stretched empty state illustration at 4x","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"our dimens are hardcoded dp in composables. move to a spacing scale in the theme, identical rendering at 1x","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"on a fold, opening the detail pane then folding loses the item and shows the empty state","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"check the app against talkback on the three main screens and tell me what's broken, don't fix anything yet","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"two-pane layout on wide screens with the list on the left, and the selection should survive a fold/unfold","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"landscape on phones shows a stretched empty state illustration at 4x","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"our dimens are hardcoded dp in composables. move to a spacing scale in the theme, identical rendering at 1x","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"on a fold, opening the detail pane then folding loses the item and shows the empty state","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"check the app against talkback on the three main screens and tell me what's broken, don't fix anything yet","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"accessibility statement for the play store listing and the website, honest about what's not there yet","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"in-app update prompt using the play core api, flexible for minor and immediate for a security release","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"in-app update prompt using the play core api, flexible for minor and immediate for a security release","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"design the offline map tile cache — size cap, eviction, and letting the user pin a region deliberately","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"downloaded regions list with sizes, a delete swipe, and a total storage used bar at the top","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"tile cache dir isn't in the app's cache directory so android never clears it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"figure out the plan for the maps sdk migration and then port the tile layer as a first step","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"diagnose the tile download stalls then note the workaround in the support doc","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"let's do the next one","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"tile cache dir isn't in the app's cache directory so android never clears it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"figure out the plan for the maps sdk migration and then port the tile layer as a first step","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"diagnose the tile download stalls then note the workaround in the support doc","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} {"prompt":"i'd like the design written down for how we shard the write path. our single postgres primary is at 70% cpu at peak and we've exhausted the easy wins. options as i see them: split by tenant to separate clusters, citus, or move the two hottest tables out. compare and recommend, with the failure modes of each","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"tenant-to-shard routing layer with a lookup table, connection pools per shard, and a way to move a tenant with a short write pause","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"tenant-to-shard routing layer with a lookup table, connection pools per shard, and a way to move a tenant with a short write pause","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"shard admin view: tenants per shard, size, write rate, and a move action that shows the estimated pause","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the shard id is an int in the code and a string in the config","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"every query in the repo assumes one connection. thread the shard context through properly — no global state, and every existing query hits the same data it does now","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"one tenant's writes land on the wrong shard occasionally and we end up with rows in two places","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"read the routing code and tell me what happens to an in-flight request during a tenant move","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the sharding doc for the team — how routing works, what's shard-local vs global, and the rules for writing a new query","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"the shard id is an int in the code and a string in the config","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"every query in the repo assumes one connection. thread the shard context through properly — no global state, and every existing query hits the same data it does now","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"one tenant's writes land on the wrong shard occasionally and we end up with rows in two places","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"read the routing code and tell me what happens to an in-flight request during a tenant move","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the sharding doc for the team — how routing works, what's shard-local vs global, and the rules for writing a new query","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"please add read-replica routing for the reporting queries, with a staleness guard so we don't serve a write-then-read from a lagging replica","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"reporting page shows a spinner then old data then new data, three states in two seconds. settle it down","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the replica lag threshold is 30s, way too lax, make it 2","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"outline how we'd test shard failover without a staging environment that has multiple shards","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"reporting page shows a spinner then old data then new data, three states in two seconds. settle it down","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the replica lag threshold is 30s, way too lax, make it 2","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"outline how we'd test shard failover without a staging environment that has multiple shards","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"our connection handling opens a transaction for read-only queries in half the endpoints. clean that up, same results, fewer write locks","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"does the replica routing respect an explicit transaction? i don't want a read inside a write tx going to a replica","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"after a failover last night some rows are missing from one table and present in the audit log. i need to understand what we lost and how","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"write the failover runbook, and be explicit about the steps that are NOT automated","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"お願いします。バッチ推論のパイプラインを設計してください。1日3億レコード、GPU は 8 枚、失敗したシャードだけ再実行できるように","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"ja"} +{"prompt":"does the replica routing respect an explicit transaction? i don't want a read inside a write tx going to a replica","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"after a failover last night some rows are missing from one table and present in the audit log. i need to understand what we lost and how","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"write the failover runbook, and be explicit about the steps that are NOT automated","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"お願いします。バッチ推論のパイプラインを設計してください。1日3億レコード、GPU は 8 枚、失敗したシャードだけ再実行できるように","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"ja"} {"prompt":"feature drift monitoring — compute the training/serving distribution distance per feature daily and alert on the ones that move","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"drift dashboard: one small multiple per feature, sorted by how much it moved, click through to the distributions","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"drift dashboard: one small multiple per feature, sorted by how much it moved, click through to the distributions","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"the drift threshold is hardcoded 0.1 for every feature, make it configurable per feature","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"our three notebooks that compute drift each define the metric slightly differently. one implementation in the library, all three call it","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"drift alerts fire for a feature that is provably constant. i've checked the input data, it's the same value every row","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"does our monitoring compare against the training distribution or the previous day? tell me which, because the alerts only make sense for one of those","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"docs for the monitoring service's api — the metrics endpoints, the query params, and what the response fields mean","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"cool cool","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"here's the TODO list i left myself, please turn it into a proper sequenced plan with what depends on what — i suspect it's not doable in this order:\n\n- switch the frontend to the new auth endpoints\n- delete the old session table\n- move refresh token storage to httpOnly cookies\n- add device list + revoke-per-device UI\n- backfill device records for existing sessions (we don't record device today)\n- rotate the signing key\n- turn off the legacy /login endpoint (the ios app 3.x still uses it, ~6% of users)\n- add rate limiting to /login (currently none)","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"drift alerts fire for a feature that is provably constant. i've checked the input data, it's the same value every row","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"does our monitoring compare against the training distribution or the previous day? tell me which, because the alerts only make sense for one of those","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"docs for the monitoring service's api — the metrics endpoints, the query params, and what the response fields mean","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"here's the TODO list i left myself, please turn it into a proper sequenced plan with what depends on what — i suspect it's not doable in this order:\n\n- switch the frontend to the new auth endpoints\n- delete the old session table\n- move refresh token storage to httpOnly cookies\n- add device list + revoke-per-device UI\n- backfill device records for existing sessions (we don't record device today)\n- rotate the signing key\n- turn off the legacy /login endpoint (the ios app 3.x still uses it, ~6% of users)\n- add rate limiting to /login (currently none)","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"device list endpoint with last-seen, ip and user agent, plus a revoke-one and revoke-all-others","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"active sessions screen — device icon by platform, current device labeled, revoke button per row with a confirm","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"user agent parsing puts 'Other' for every ios app request","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"user agent parsing puts 'Other' for every ios app request","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"rate limit /login per account and per ip, with a lockout that doesn't let an attacker lock out a victim","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"our token verification is implemented twice, once in the middleware and once in the websocket handler, with different clock skew tolerance. one implementation","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"logging out on one device logs you out everywhere, which is not what we want and not what i thought the code did","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"logging out on one device logs you out everywhere, which is not what we want and not what i thought the code did","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"help center article about active sessions and what revoking does, plus what it doesn't do","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"map out the plan for our mobile app's token storage. keychain/keystore, refresh rotation, and what happens on a device restore from backup","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"biometric gate on app open, with a passcode fallback and a setting to require it every time vs after 5 minutes","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the biometric prompt title says 'Authenticate' which is meaningless, write proper copy for it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"biometric gate on app open, with a passcode fallback and a setting to require it every time vs after 5 minutes","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the biometric prompt title says 'Authenticate' which is meaningless, write proper copy for it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} {"prompt":"lock screen overlay that blurs the content behind it, and it must appear before the app snapshot is taken","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"after a phone restore users get logged out but the app shows their cached data for a second first","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"review our token refresh for the case where two requests both get a 401 and both try to refresh","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the keychain accessibility is kSecAttrAccessibleAlways, should be AfterFirstUnlockThisDeviceOnly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"review our token refresh for the case where two requests both get a 401 and both try to refresh","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the keychain accessibility is kSecAttrAccessibleAlways, should be AfterFirstUnlockThisDeviceOnly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"propose the approach for supporting multiple accounts in the mobile apps, including how we keep their caches and push tokens separate","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"background upload queue that survives app kill, resumes on next launch, and reports progress to a notification","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"upload queue screen with per-item progress, retry, cancel, and a clear-completed action","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"progress notification doesn't clear when the queue finishes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"the upload code exists in the camera flow and the document flow separately. unify, same retry behavior and the same notification updates","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"uploads restart from zero after a network blip instead of resuming from the last part","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"walk me through what our uploader does when the file is deleted from the device mid-upload","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"internal doc on the upload protocol, part sizes, the resume handshake, and the server-side assembly step","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"podemos continuar","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"pt"} +{"prompt":"upload queue screen with per-item progress, retry, cancel, and a clear-completed action","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"progress notification doesn't clear when the queue finishes","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the upload code exists in the camera flow and the document flow separately. unify, same retry behavior and the same notification updates","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"uploads restart from zero after a network blip instead of resuming from the last part","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"walk me through what our uploader does when the file is deleted from the device mid-upload","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"internal doc on the upload protocol, part sizes, the resume handshake, and the server-side assembly step","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"propose the architecture for our new realtime collaboration service. requirements: 50 concurrent editors per doc, sub-100ms local echo, server authoritative ordering, and the doc has to be reconstructible from the log for audit. i'd like the tradeoffs of crdt vs ot spelled out for OUR constraints, not in general","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"operation log storage with per-doc ordering, compaction into snapshots every 500 ops, and a replay endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"presence cursors with names, colors assigned stably per user, and they should fade after 5s of inactivity","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"operation log storage with per-doc ordering, compaction into snapshots every 500 ops, and a replay endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"presence cursors with names, colors assigned stably per user, and they should fade after 5s of inactivity","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"cursor color palette has two nearly identical greens","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"the editor has its own document model separate from the sync layer's, and they're kept in step by hand. make one the source of truth","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"two people typing in the same paragraph occasionally produces interleaved garbage, roughly once an hour of active use","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"explain the ordering our server assigns to concurrent ops, and whether a client can observe two different orders across a reconnect","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"write up the sync protocol for the team, including the reconnect handshake and what the client must do with ops it already applied","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"comments anchored to text ranges that survive edits around them, including edits that delete the anchored text entirely","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"comment sidebar aligned to its anchor's vertical position, stacking when two are close, and highlighting the range on hover","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"resolved comments still show in the count","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"plan how we handle a doc that grows to 50MB of ops. compaction, cold storage, and what the ui does while a big doc loads","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"comments on deleted text end up anchored to position 0 and cluster at the top of the doc","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"look at the presence implementation and tell me how many messages per second 50 editors generate","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the version history uses timestamps for ordering and the ops log uses a lamport counter. make them consistent, history must show the same order the ops applied in","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the editor has its own document model separate from the sync layer's, and they're kept in step by hand. make one the source of truth","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"two people typing in the same paragraph occasionally produces interleaved garbage, roughly once an hour of active use","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"explain the ordering our server assigns to concurrent ops, and whether a client can observe two different orders across a reconnect","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"write up the sync protocol for the team, including the reconnect handshake and what the client must do with ops it already applied","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"comments anchored to text ranges that survive edits around them, including edits that delete the anchored text entirely","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"comment sidebar aligned to its anchor's vertical position, stacking when two are close, and highlighting the range on hover","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"resolved comments still show in the count","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"plan how we handle a doc that grows to 50MB of ops. compaction, cold storage, and what the ui does while a big doc loads","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"comments on deleted text end up anchored to position 0 and cluster at the top of the doc","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"look at the presence implementation and tell me how many messages per second 50 editors generate","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the version history uses timestamps for ordering and the ops log uses a lamport counter. make them consistent, history must show the same order the ops applied in","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"changelog and a short blog post about shipping collaborative editing, technical audience","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"design the offline editing story for the collaborative doc, then implement the local op queue","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"explain how anchoring works and then document it in the architecture folder","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"ok","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"design the offline editing story for the collaborative doc, then implement the local op queue","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"explain how anchoring works and then document it in the architecture folder","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} {"prompt":"need a plan for our search infrastructure. postgres full text is at its limit — 40M docs, faceting is slow, and no typo tolerance. opensearch, typesense, or a managed thing. include the reindexing story and how we keep it in sync with writes","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"indexing pipeline that tails the change log and updates the search index within a second, with a full reindex mode","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"search results page with facets in a left rail, counts per facet, and applied filters as removable chips at the top","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the search input doesn't submit on enter in safari","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"query building for search is duplicated between the api and the admin tool with different escaping. one query builder, and check the escaping is right in both cases","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"documents updated in the last few minutes sometimes don't appear in search and sometimes do. the indexer log shows them all as indexed","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"is our relevance tuning actually applied at query time or index time? and which fields are boosted","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"search api docs — the query syntax we support, facet params, pagination limits, and the relevance caveats","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"indexing pipeline that tails the change log and updates the search index within a second, with a full reindex mode","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"search results page with facets in a left rail, counts per facet, and applied filters as removable chips at the top","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the search input doesn't submit on enter in safari","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"query building for search is duplicated between the api and the admin tool with different escaping. one query builder, and check the escaping is right in both cases","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"documents updated in the last few minutes sometimes don't appear in search and sometimes do. the indexer log shows them all as indexed","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"is our relevance tuning actually applied at query time or index time? and which fields are boosted","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"search api docs — the query syntax we support, facet params, pagination limits, and the relevance caveats","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"typeahead endpoint with prefix matching, 50ms budget, and per-tenant filtering that can't be bypassed","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"typeahead dropdown with keyboard nav, grouped results by type, and a 'see all results' footer row","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"min query length for typeahead is 1, make it 2","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"plan how we'd measure search quality — click-through, zero-result rate, and an offline judgement set. i want to know if a relevance change helped","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"search analytics logging: query, result count, position clicked, latency, with the query text hashed for anything that looks like an email","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"zero results page: suggest spelling corrections, drop the least selective filter, and offer a saved-search signup","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"queries with a trailing space return nothing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"check the analytics logging for anything that would record pii, we log the raw query string in one path i think","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"we compute 'zero result rate' in the dashboard sql and in the python job differently. one definition, and say which numbers change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"search latency p99 tripled at 2pm yesterday and stayed there. index size is the same, query mix looks the same","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"write the internal doc on our relevance model and the levers we have, so the next person doesn't rediscover it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"ugh, fine, plan it properly then start on the indexer","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"review the reindex script and fix the obvious bugs","purpose":"review","secondary":"quickFix","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} -{"prompt":"one sec, actually the other file","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"plan how we'd measure search quality — click-through, zero-result rate, and an offline judgement set. i want to know if a relevance change helped","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"search analytics logging: query, result count, position clicked, latency, with the query text hashed for anything that looks like an email","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"zero results page: suggest spelling corrections, drop the least selective filter, and offer a saved-search signup","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"queries with a trailing space return nothing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"check the analytics logging for anything that would record pii, we log the raw query string in one path i think","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"we compute 'zero result rate' in the dashboard sql and in the python job differently. one definition, and say which numbers change","purpose":"backendImpl","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"search latency p99 tripled at 2pm yesterday and stayed there. index size is the same, query mix looks the same","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"write the internal doc on our relevance model and the levers we have, so the next person doesn't rediscover it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"review the reindex script and fix the obvious bugs","purpose":"review","secondary":"quickFix","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} {"prompt":"give me the migration plan from our custom auth to an off-the-shelf idp. 400k users with bcrypt hashes, social logins, and enterprise sso for 30 orgs. what moves first and how we avoid a mass password reset","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"lazy password migration — verify against bcrypt, rehash into the new format on successful login, and track the percentage migrated","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"lazy password migration — verify against bcrypt, rehash into the new format on successful login, and track the percentage migrated","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the login page needs a 'continue with' section that only shows the providers configured for that email's domain","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"bcrypt cost is 8, that's low. take it to 12 for new hashes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"our user lookup is by email in some places and by a normalized email in others, which is how we ended up with two accounts for one person. one normalization, applied everywhere","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"social login creates a duplicate account when the email matches an existing password account, but only for google not github","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"look at the account linking logic and tell me if an attacker could link their oauth identity to someone else's account","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"our user lookup is by email in some places and by a normalized email in others, which is how we ended up with two accounts for one person. one normalization, applied everywhere","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"social login creates a duplicate account when the email matches an existing password account, but only for google not github","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"look at the account linking logic and tell me if an attacker could link their oauth identity to someone else's account","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"write the migration comms — the email to users if anything changes for them, and the internal faq for support","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"account merge flow: detect the duplicate, show what will be combined, and do it transactionally with an undo window","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"merge accounts screen showing both accounts side by side with what's kept from each","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"account merge flow: detect the duplicate, show what will be combined, and do it transactionally with an undo window","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"merge accounts screen showing both accounts side by side with what's kept from each","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"the 'account already exists' error suggests signing in, but with the wrong provider name","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"figure out the plan for supporting org-enforced sso, where a member with a password account gets converted","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"users in an sso-enforced org can still log in with a password if they use the old bookmarked url","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"explain what our idp discovery does with an email whose domain is claimed by two orgs","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"admin docs for domain verification and sso enforcement, including the escape hatch for locked-out admins","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"consolidate the four places we build a login redirect url — they disagree on trailing slashes and one of them drops the `next` param","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"wrap up whatever's half done","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"ok so ive been thinking about our ability system in unreal and i keep coming back to gameplay ability system vs rolling our own. GAS is a lot of machinery and the team doesnt know it, but our own thing already has replication bugs we dont understand. write up the honest comparison for a 4 person team shipping in a year, and pick","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"server rpc validation for the interact action — range check, line of sight, and cooldown, all server side, and log rejections with the actor","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"radial menu for emotes, controller stick to select, snap to 8 sectors, and it should show which one is selected clearly at a glance","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain what our idp discovery does with an email whose domain is claimed by two orgs","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"admin docs for domain verification and sso enforcement, including the escape hatch for locked-out admins","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"consolidate the four places we build a login redirect url — they disagree on trailing slashes and one of them drops the `next` param","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"wrap up whatever's half done","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"ok so ive been thinking about our ability system in unreal and i keep coming back to gameplay ability system vs rolling our own. GAS is a lot of machinery and the team doesnt know it, but our own thing already has replication bugs we dont understand. write up the honest comparison for a 4 person team shipping in a year, and pick","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"server rpc validation for the interact action — range check, line of sight, and cooldown, all server side, and log rejections with the actor","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"radial menu for emotes, controller stick to select, snap to 8 sectors, and it should show which one is selected clearly at a glance","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"the interact range is 200 units, designers want 350","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"our actor components each hold a raw pointer back to the owner and cast it. clean that up with proper interfaces, same behavior in the test map","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"clients desync from the server after about 20 minutes and the only symptom is doors being open for some players and closed for others","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"whats our current replication cost per actor, roughly, based on the properties marked replicated? just read it and tell me","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"clients desync from the server after about 20 minutes and the only symptom is doors being open for some players and closed for others","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"whats our current replication cost per actor, roughly, based on the properties marked replicated? just read it and tell me","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"write the design doc for the loot system from what's already implemented, because nobody can tell whats intentional anymore","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"rails: background job to recalculate the leaderboard every 5 minutes, sidekiq, and it must be safe if two enqueue at once","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"our models have 40 scopes and half of them are unused. find the dead ones and remove them, nothing else changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"n+1 queries all over the profile page. bullet is screaming. sort it out","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"plan the upgrade from rails 6.1 to 7.2. 900 files, a lot of custom middleware, and we're on webpacker","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain what our ApplicationRecord callbacks do on save, in order, because something is touching updated_at that shouldnt","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"requests time out on one endpoint after we added an index, which makes no sense to me","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"api documentation for the public endpoints, from the controllers and serializers as they actually are, not what the old doc claims","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"rails: background job to recalculate the leaderboard every 5 minutes, sidekiq, and it must be safe if two enqueue at once","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"our models have 40 scopes and half of them are unused. find the dead ones and remove them, nothing else changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"n+1 queries all over the profile page. bullet is screaming. sort it out","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"plan the upgrade from rails 6.1 to 7.2. 900 files, a lot of custom middleware, and we're on webpacker","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"explain what our ApplicationRecord callbacks do on save, in order, because something is touching updated_at that shouldnt","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"requests time out on one endpoint after we added an index, which makes no sense to me","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"api documentation for the public endpoints, from the controllers and serializers as they actually are, not what the old doc claims","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"svelte: the settings page needs optimistic toggles that revert on failure with a small inline error, no toasts","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"astro build outputs a 900kb bundle for a mostly static site, and i cant tell what's pulling in what","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"focus outline is `outline: none` in the global reset","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"focus outline is `outline: none` in the global reset","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"we have three ways of doing modals in the app — a store-driven one, a context one, and one that just uses ``. pick the dialog one and port the rest, same behavior including focus handling","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"sketch out the plan for our marketing site rebuild — content in mdx, previews per branch, and the design team editing copy without a PR","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"sketch out the plan for our marketing site rebuild — content in mdx, previews per branch, and the design team editing copy without a PR","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"content collection schema for case studies, with the frontmatter validated at build time so a missing field fails the build","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"is the view transition api actually doing anything on our routes or are we just paying for the code? tell me what you see","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"docs page listing our css custom properties and what they control, for people theming the widget","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"is the view transition api actually doing anything on our routes or are we just paying for the code? tell me what you see","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"docs page listing our css custom properties and what they control, for people theming the widget","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"hero animation on the landing page: staggered fade-up on load, and it must not run again on client-side navigation back to home","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"go","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"so we've got this thing where our rails app and the new go service both write to the users table and i hate it. i want a plan to get the go service to stop writing directly — an api, or events, or just moving the ownership entirely. cost out each one, we have maybe 6 weeks of appetite for this","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"internal api on the rails side for user reads and writes so the go service can stop touching the table, with a token per consumer","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"so we've got this thing where our rails app and the new go service both write to the users table and i hate it. i want a plan to get the go service to stop writing directly — an api, or events, or just moving the ownership entirely. cost out each one, we have maybe 6 weeks of appetite for this","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"internal api on the rails side for user reads and writes so the go service can stop touching the table, with a token per consumer","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"admin ui to see which service last wrote each user record, from the audit trail","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"the go service's db user has full write grants, restrict it to read for now","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"both services define the user shape independently. generate one from the other so they cant drift, no field changes today","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"a user's email gets reverted to the old value occasionally, minutes after they change it. two writers obviously but i want to know exactly which path does it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"both services define the user shape independently. generate one from the other so they cant drift, no field changes today","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"a user's email gets reverted to the old value occasionally, minutes after they change it. two writers obviously but i want to know exactly which path does it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"compare how the two services validate an email address and tell me which is stricter","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"adr documenting who owns the user record after this change, and the rule for future services","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"here's the log from the failing job, i dont even know where to start:\n\nI, [2026-07-29T02:14:08.221Z] INFO -- : [Sidekiq] start ReindexJob jid=8a2f11 args=[\"batch\", 4412]\nW, [2026-07-29T02:14:39.902Z] WARN -- : [Sidekiq] ReindexJob jid=8a2f11 PG::TRDeadlockDetected\nI, [2026-07-29T02:14:39.905Z] INFO -- : [Sidekiq] fail ReindexJob jid=8a2f11 elapsed=31.68\nI, [2026-07-29T02:14:40.001Z] INFO -- : [Sidekiq] start ReindexJob jid=8a2f11 args=[\"batch\", 4412] retry=1\nW, [2026-07-29T02:15:11.442Z] WARN -- : [Sidekiq] ReindexJob jid=8a2f11 PG::TRDeadlockDetected\n...\nI, [2026-07-29T02:41:03.118Z] INFO -- : [Sidekiq] fail ReindexJob jid=8a2f11 retry=24 dead=true\n\nit deadlocks with itself as far as i can tell, theres only one worker on that queue","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"adr documenting who owns the user record after this change, and the rule for future services","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"here's the log from the failing job, i dont even know where to start:\n\nI, [2026-07-29T02:14:08.221Z] INFO -- : [Sidekiq] start ReindexJob jid=8a2f11 args=[\"batch\", 4412]\nW, [2026-07-29T02:14:39.902Z] WARN -- : [Sidekiq] ReindexJob jid=8a2f11 PG::TRDeadlockDetected\nI, [2026-07-29T02:14:39.905Z] INFO -- : [Sidekiq] fail ReindexJob jid=8a2f11 elapsed=31.68\nI, [2026-07-29T02:14:40.001Z] INFO -- : [Sidekiq] start ReindexJob jid=8a2f11 args=[\"batch\", 4412] retry=1\nW, [2026-07-29T02:15:11.442Z] WARN -- : [Sidekiq] ReindexJob jid=8a2f11 PG::TRDeadlockDetected\n...\nI, [2026-07-29T02:41:03.118Z] INFO -- : [Sidekiq] fail ReindexJob jid=8a2f11 retry=24 dead=true\n\nit deadlocks with itself as far as i can tell, theres only one worker on that queue","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} {"prompt":"batch reindex job that processes in stable id order with a bounded transaction per chunk, so it cant deadlock against itself","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the sidekiq concurrency is 25 against a pool of 10 connections","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"job queue page: per-queue depth, latency, and the dead set with a retry-selected action","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"our jobs take positional args in some cases and hashes in others, and a couple take activerecord objects which is asking for trouble. standardize on ids, no change in what each job does","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"plan how we'd move sidekiq jobs to a separate service so a bad job cant take down the web pods","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"read our job retry configuration and tell me which jobs will retry forever","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"write the job authoring guide: idempotency, argument rules, retry expectations, and how to make a job safe to run twice","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"unreal: the loading screen needs to not be a black frame for 2 seconds before the level streams in","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the pak file mount order means our patch content loses to the base content","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"plan the content patching pipeline and then build the manifest diffing tool","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"work out whats causing the hitching on level load and then write it up in the perf doc","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"nah do it the other way","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"the sidekiq concurrency is 25 against a pool of 10 connections","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"job queue page: per-queue depth, latency, and the dead set with a retry-selected action","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"our jobs take positional args in some cases and hashes in others, and a couple take activerecord objects which is asking for trouble. standardize on ids, no change in what each job does","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"plan how we'd move sidekiq jobs to a separate service so a bad job cant take down the web pods","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"read our job retry configuration and tell me which jobs will retry forever","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"write the job authoring guide: idempotency, argument rules, retry expectations, and how to make a job safe to run twice","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"unreal: the loading screen needs to not be a black frame for 2 seconds before the level streams in","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"the pak file mount order means our patch content loses to the base content","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"plan the content patching pipeline and then build the manifest diffing tool","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"work out whats causing the hitching on level load and then write it up in the perf doc","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} {"prompt":"im going round in circles on this. we need to support 'projects' having many 'environments' and each environment having its own config, secrets and deploy history. right now project and environment are the same table with a nullable parent id and its a nightmare. i want the data model and the migration path written out, including what happens to existing rows and the api compat story","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"environments crud with config inheritance from the project, and an override indicator per key","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"environments crud with config inheritance from the project, and an override indicator per key","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"environment switcher in the header, keyboard accessible, with the current env's color as a subtle accent so you know where you are","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"prod environment badge is green, should be red","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"the config resolution logic exists in the api, the cli and the deploy worker separately. one implementation, and the resolved config must be identical for every existing environment","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"config changes apply to the wrong environment about once a week according to the audit log. i cannot reproduce it and its terrifying","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"tell me how the config inheritance resolves when a key is set at both levels and one is an empty string","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"docs for the config api — precedence rules, the reserved key prefixes, and what a null vs empty value means","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"deploy history endpoint with the diff of config between deploys, paginated","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"deploy timeline ui: rows per deploy, status, duration, who, and an expander showing the config diff","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the relative timestamps say '2 hours ago' for things that happened 2 minutes ago in another timezone","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"prod environment badge is green, should be red","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"the config resolution logic exists in the api, the cli and the deploy worker separately. one implementation, and the resolved config must be identical for every existing environment","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"config changes apply to the wrong environment about once a week according to the audit log. i cannot reproduce it and its terrifying","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"tell me how the config inheritance resolves when a key is set at both levels and one is an empty string","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"docs for the config api — precedence rules, the reserved key prefixes, and what a null vs empty value means","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"deploy history endpoint with the diff of config between deploys, paginated","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"deploy timeline ui: rows per deploy, status, duration, who, and an expander showing the config diff","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the relative timestamps say '2 hours ago' for things that happened 2 minutes ago in another timezone","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"figure out the plan for rollbacks. currently 'deploy the old sha' which doesnt cover config or migrations","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"review the deploy worker for what happens if it dies halfway through, and whether we can end up with a half-applied config","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"deploys report success but the pods still run the old image about 5% of the time","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"review the deploy worker for what happens if it dies halfway through, and whether we can end up with a half-applied config","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"deploys report success but the pods still run the old image about 5% of the time","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"write the rollback runbook including the config and migration parts, and what we tell customers during one","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"consolidate the deploy status enum — the api says 'in_progress', the worker says 'running' and the ui maps between them. pick one, keep the api's public strings stable","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"unser Deploy-Webhook feuert zweimal pro Deploy. plan zuerst wie wir das sauber lösen, dann bau es","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"de"} -{"prompt":"have a look at the config resolver and tidy the naming as you go","purpose":"review","secondary":"refactor","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} -{"prompt":"do the needful","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"we're adding a public terraform provider. i want the design first — resource coverage for v1, import support, how we handle our api's eventual consistency in the read-after-create, and the release process for the registry","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"terraform provider resource for projects and environments, with import, and retries on the read after create until it's consistent","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"provider docs — one page per resource, every attribute, an import example, and the note about eventual consistency","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"consolidate the deploy status enum — the api says 'in_progress', the worker says 'running' and the ui maps between them. pick one, keep the api's public strings stable","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"unser Deploy-Webhook feuert zweimal pro Deploy. plan zuerst wie wir das sauber lösen, dann bau es","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"de"} +{"prompt":"have a look at the config resolver and tidy the naming as you go","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"do the needful","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"we're adding a public terraform provider. i want the design first — resource coverage for v1, import support, how we handle our api's eventual consistency in the read-after-create, and the release process for the registry","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"terraform provider resource for projects and environments, with import, and retries on the read after create until it's consistent","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"provider docs — one page per resource, every attribute, an import example, and the note about eventual consistency","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"the provider version constraint in our examples pins an old version","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"our api client in the provider duplicates the one in the cli. share it as a library, both keep working identically","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"terraform plan shows a change on every run for one attribute even when nothing changed","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"does our provider handle a resource deleted outside terraform gracefully, or does it error on refresh","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"a small web ui for browsing our resource schemas, generated from the provider's schema json","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"plan the sdk story — do we hand write three sdks or generate from openapi. include the maintenance cost and how idiomatic the generated ones would be","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"our api client in the provider duplicates the one in the cli. share it as a library, both keep working identically","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"terraform plan shows a change on every run for one attribute even when nothing changed","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"does our provider handle a resource deleted outside terraform gracefully, or does it error on refresh","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"a small web ui for browsing our resource schemas, generated from the provider's schema json","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"plan the sdk story — do we hand write three sdks or generate from openapi. include the maintenance cost and how idiomatic the generated ones would be","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"typescript sdk with typed responses, automatic pagination via async iterators, and a pluggable fetch","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the sdk readme example doesnt compile, wrong import path","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"sdk reference docs — every method, params, the error types, and a section on retries and timeouts","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"the python and ts sdks name the same concepts differently (client vs session, list vs iterate). align the naming across both, keeping the old names as aliases","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"the sdk readme example doesnt compile, wrong import path","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"sdk reference docs — every method, params, the error types, and a section on retries and timeouts","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the python and ts sdks name the same concepts differently (client vs session, list vs iterate). align the naming across both, keeping the old names as aliases","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the sdk hangs on a 429 instead of backing off, but only when the retry-after header is a date not a number","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"read the sdk's pagination and tell me what happens if a page boundary lands on a deleted record","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"docs site nav is 40 items flat, group it and add a search","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"later gator","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"read the sdk's pagination and tell me what happens if a page boundary lands on a deleted record","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"docs site nav is 40 items flat, group it and add a search","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"ok real talk our monitoring for the game servers is basically nothing. we know when a match server crashes because players complain. i want the plan: what we instrument, how we get it off the boxes, and the three alerts that would actually have caught the incidents we've had","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"match server heartbeat and metrics reporting — tick time, player count, memory, sent every 10s to the fleet manager","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"fleet view: servers as tiles by region, color by health, click for the match currently running on it","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the heartbeat timeout is 5s and gc pauses are 6s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"match server heartbeat and metrics reporting — tick time, player count, memory, sent every 10s to the fleet manager","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"fleet view: servers as tiles by region, color by health, click for the match currently running on it","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the heartbeat timeout is 5s and gc pauses are 6s","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"our server allocation code has three copies for the three regions with the hostnames swapped. one implementation, region as a parameter","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"match servers occasionally report 0 players while a match is clearly running, and then recover","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"explain how a crashed match server is detected and what happens to the players in it right now","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"match servers occasionally report 0 players while a match is clearly running, and then recover","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain how a crashed match server is detected and what happens to the players in it right now","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"ops doc for the game server fleet — how to drain a server, how to roll a build, and what the alerts mean","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"matchmaking backfill so a match that loses players can get topped up from the queue, with a skill window that respects the match in progress","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"matchmaking backfill so a match that loses players can get topped up from the queue, with a skill window that respects the match in progress","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"queue ui showing estimated wait and your current search range widening, without lying to the player","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"queue estimate shows 'less than a minute' always","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"queue estimate shows 'less than a minute' always","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"map out how we'd add a ranked mode. placement matches, decay, seasons, and the leaderboard consistency story","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"one region matches players 400 mmr apart and the others dont. same config as far as i can see","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"read the mmr update code and tell me if a player can lose rating for a win in any edge case","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"one region matches players 400 mmr apart and the others dont. same config as far as i can see","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"read the mmr update code and tell me if a player can lose rating for a win in any edge case","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"player-facing explainer for how ranked works, honest about what mmr is and isn't","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"the mmr math lives in the match server and the leaderboard service, separately implemented. one implementation, same ratings on the historical match set","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"现在的反作弊只有客户端检测。先给我方案，服务端能验证哪些行为，误报怎么处理","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"zh"} -{"prompt":"server side speed and teleport detection with a tolerance for latency, flagging not banning, and a review queue","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"review queue ui for flagged players: the evidence, a replay link, and actions with a required note","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the flag threshold is 1 event which flags everybody with bad wifi","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"legit players get flagged when their connection hiccups, and i cant tell from the code whether we account for the resync at all","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"explain the current client-side checks and what a determined cheater would have to do to bypass each one","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the mmr math lives in the match server and the leaderboard service, separately implemented. one implementation, same ratings on the historical match set","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"现在的反作弊只有客户端检测。先给我方案，服务端能验证哪些行为，误报怎么处理","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"zh"} +{"prompt":"server side speed and teleport detection with a tolerance for latency, flagging not banning, and a review queue","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"review queue ui for flagged players: the evidence, a replay link, and actions with a required note","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the flag threshold is 1 event which flags everybody with bad wifi","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"legit players get flagged when their connection hiccups, and i cant tell from the code whether we account for the resync at all","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain the current client-side checks and what a determined cheater would have to do to bypass each one","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"internal policy doc for enforcement actions — what triggers a warning, a suspension, a ban, and the appeal path","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"the anti-cheat report parsing duplicates the telemetry parser with a different struct. share the parsing, same reports produced","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"yeah that","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"need to decide how we store timeseries for the device fleet. 30k devices, one reading a minute, 18 month retention, and the queries are 'last value per device' and 'hourly average over a month'. timescale, clickhouse, or roll our own on postgres partitions. write it up with numbers","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"continuous aggregate for hourly averages with a refresh policy, and the last-value query needs to be fast without scanning","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"continuous aggregate for hourly averages with a refresh policy, and the last-value query needs to be fast without scanning","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"device detail page with a sparkline per metric, a range picker, and a live-updating current value","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the retention policy drops chunks at 12 months not 18","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"the retention policy drops chunks at 12 months not 18","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"our downsampling job and the continuous aggregate compute averages differently for partial hours. pick the aggregate's behavior and delete the job","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} {"prompt":"hourly averages are wrong for the hour containing a dst transition, in one direction only","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"check whether our ingest path can drop readings silently under load — i see a bounded channel with a default case","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"write up the data model and query patterns for the fleet timeseries so people stop writing full scans","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"alerting on device metrics: thresholds per device type, a sustained-for duration, and hysteresis so it doesnt flap","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"alert config form: metric picker, comparator, threshold, duration, and a preview of how often it would have fired last week","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the alert email says 'threshold exceeded' with no metric name or value","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"plan the firmware telemetry schema so we can add fields without breaking old devices or the ingest path","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"a device that goes offline stops triggering its 'no data' alert after 24 hours, which is backwards","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"explain the hysteresis in our alert evaluator, i want to know the exact conditions for clearing","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"customer facing docs for device alerts, what each metric means physically, and the sampling caveat","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"our alert state machine is spread across the evaluator, the notifier and a boolean column. make the state explicit in one place, same firing behavior on the replayed history","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"sure","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"pasted from the ticket, this is what the customer sent us:\n\n\"When we PATCH /v2/devices/{id} with only the `label` field, the response comes back with\n`tags: []` and our tags are gone. Sending the same request with `tags` included works.\nWe were told PATCH was a partial update. We've lost tags on about 900 devices.\nAlso: the response 200s so we had no idea until a customer of ours noticed.\"\n\nthis is bad. i need to know whether its a bug in the handler or the serializer, and what we do about the 900 devices","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"check whether our ingest path can drop readings silently under load — i see a bounded channel with a default case","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"write up the data model and query patterns for the fleet timeseries so people stop writing full scans","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"alerting on device metrics: thresholds per device type, a sustained-for duration, and hysteresis so it doesnt flap","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"alert config form: metric picker, comparator, threshold, duration, and a preview of how often it would have fired last week","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the alert email says 'threshold exceeded' with no metric name or value","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"plan the firmware telemetry schema so we can add fields without breaking old devices or the ingest path","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"a device that goes offline stops triggering its 'no data' alert after 24 hours, which is backwards","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"explain the hysteresis in our alert evaluator, i want to know the exact conditions for clearing","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"customer facing docs for device alerts, what each metric means physically, and the sampling caveat","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"our alert state machine is spread across the evaluator, the notifier and a boolean column. make the state explicit in one place, same firing behavior on the replayed history","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"pasted from the ticket, this is what the customer sent us:\n\n\"When we PATCH /v2/devices/{id} with only the `label` field, the response comes back with\n`tags: []` and our tags are gone. Sending the same request with `tags` included works.\nWe were told PATCH was a partial update. We've lost tags on about 900 devices.\nAlso: the response 200s so we had no idea until a customer of ours noticed.\"\n\nthis is bad. i need to know whether its a bug in the handler or the serializer, and what we do about the 900 devices","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} {"prompt":"proper patch semantics on the device endpoints — absent means untouched, explicit null means clear, and reject unknown fields","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the api docs describe PATCH as a partial update, which the code doesnt do. fix the docs for now and mark the discrepancy clearly","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"device edit form should only send changed fields","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"our request models use zero values as 'not provided' which is exactly this bug in seven other endpoints. move to explicit optionals everywhere, behavior fixed consistently","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"audit the other write endpoints for the same absent-vs-empty confusion and list them","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the api docs describe PATCH as a partial update, which the code doesnt do. fix the docs for now and mark the discrepancy clearly","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"device edit form should only send changed fields","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"our request models use zero values as 'not provided' which is exactly this bug in seven other endpoints. move to explicit optionals everywhere, behavior fixed consistently","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"audit the other write endpoints for the same absent-vs-empty confusion and list them","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"restore script for the 900 devices' tags from the audit log, dry run first","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"write the customer apology and the status page note, and be specific about what we're doing","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"plan how we prevent this class of bug — contract tests, or codegen from the spec, or a review checklist. pick something enforceable","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"write the customer apology and the status page note, and be specific about what we're doing","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"plan how we prevent this class of bug — contract tests, or codegen from the spec, or a review checklist. pick something enforceable","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"contract tests generated from the openapi spec, run in ci, failing on any response that doesnt match","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the spec's example for the device object is missing three fields the api returns","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"the spec's example for the device object is missing three fields the api returns","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"look at our error response shapes across endpoints and tell me how many distinct shapes we actually emit","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"unify the error response shape across all endpoints, keeping the status codes and messages identical to today","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"unify the error response shape across all endpoints, keeping the status codes and messages identical to today","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"validation errors return 400 on one endpoint and 422 on another for the same kind of problem","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"error reference page for the api: code, http status, meaning, and whether retrying will help","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"toast for api errors that shows the request id so support can find it, without being ugly about it","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"keep at it","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"error reference page for the api: code, http status, meaning, and whether retrying will help","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"toast for api errors that shows the request id so support can find it, without being ugly about it","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"design the plugin marketplace: submission, review, versioning, and the permission model for what a plugin can access. i want the security boundary spelled out precisely because this is the part we cant get wrong","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"plugin permission prompts at install time, enforced at runtime, and a way for the user to see what a plugin has accessed","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"marketplace browse page: cards with icon, name, author, install count, and a filter by permission required","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"plugin permission prompts at install time, enforced at runtime, and a way for the user to see what a plugin has accessed","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"marketplace browse page: cards with icon, name, author, install count, and a filter by permission required","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"install count shows 0 for everything, its reading the wrong field","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"the plugin host and the extension host are two implementations of the same sandbox with different capabilities. merge them, and enumerate any capability that changes for existing plugins","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"one plugin can read another plugin's stored data and i dont know if thats by design or a bug","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"assess our sandbox: what can a malicious plugin actually do today, concretely","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"plugin developer docs — the api surface, the permission declarations, the review criteria, and what gets you rejected","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"plugin update mechanism with a changelog shown to the user, and permission changes requiring re-consent","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the plugin host and the extension host are two implementations of the same sandbox with different capabilities. merge them, and enumerate any capability that changes for existing plugins","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"one plugin can read another plugin's stored data and i dont know if thats by design or a bug","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"assess our sandbox: what can a malicious plugin actually do today, concretely","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"plugin developer docs — the api surface, the permission declarations, the review criteria, and what gets you rejected","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"plugin update mechanism with a changelog shown to the user, and permission changes requiring re-consent","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"installed plugins list with enable/disable toggles, an update badge, and a settings link per plugin","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"disabled plugins still run their background handlers","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"disabled plugins still run their background handlers","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"the version comparison uses string sort so 1.10.0 < 1.9.0","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"map out the revenue share and payouts side of the marketplace, including tax and refunds, at a design level","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain what happens today if a plugin author deletes their published version that people have installed","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"marketplace listing guidelines and the review rubric, written so a reviewer and an author read it the same way","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"map out the revenue share and payouts side of the marketplace, including tax and refunds, at a design level","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"explain what happens today if a plugin author deletes their published version that people have installed","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"marketplace listing guidelines and the review rubric, written so a reviewer and an author read it the same way","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"our manifest parsing accepts three schema versions with a chain of if-statements. make it a proper versioned parser, same manifests accepted","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"figure out the sandbox design and then implement the permission check layer","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"explain how plugin storage isolation works then write the section for the developer docs","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"and the rest","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"explain how plugin storage isolation works then write the section for the developer docs","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} {"prompt":"would you mind auditing the checkout flow against wcag 2.2 AA and telling me what fails? no fixes yet, i need the list for a stakeholder meeting","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the date picker is a div soup with no keyboard support at all. rebuild it as a proper combobox+grid with roving tabindex","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"aria-label on the icon-only buttons in the toolbar, there are six of them","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"screen reader announces the row count wrong after filtering — says 40 when 3 are shown. live region timing i think but i'm guessing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"our components each hand-roll their focus trap. one shared hook, identical behavior including the shift-tab wrap","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"put together the accessibility plan for the next two quarters — what we fix, what we test automatically, and how we stop regressions","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the date picker is a div soup with no keyboard support at all. rebuild it as a proper combobox+grid with roving tabindex","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"aria-label on the icon-only buttons in the toolbar, there are six of them","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"screen reader announces the row count wrong after filtering — says 40 when 3 are shown. live region timing i think but i'm guessing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"our components each hand-roll their focus trap. one shared hook, identical behavior including the shift-tab wrap","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"put together the accessibility plan for the next two quarters — what we fix, what we test automatically, and how we stop regressions","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"write our accessibility guidelines for engineers, with the five patterns we get wrong most and how to do them right","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"keyboard shortcut for skip-to-content plus the visible skip link, and it needs to actually move focus not just scroll","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"python: incremental loader for the vendor sftp drops — new files only, checksum verified, and it should quarantine anything that fails schema validation instead of failing the whole run","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"could you explain what the airflow sensor is actually waiting on in the vendor dag? i inherited it and the poke interval seems wrong","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"the schedule_interval is '@daily' but the vendor drops at 23:40 local so we always process yesterday's file","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"our 14 dags each define their own default_args with slightly different retries and owners. one factory, same effective config per dag — list any that change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"one file out of about 300 a day produces rows with the columns shifted right by one. the file looks fine when i open it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"data contract doc for the vendor feed — every column, type, nullability, and what we do when they break it (they will)","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"please plan how we move from airflow to dagster, or decide not to. 14 dags, heavy on sensors, and two people who know airflow","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"swift command line tool that watches a directory and re-signs any new .app bundle it finds, with a launchd plist to keep it running","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the tool prints progress with \\r which looks broken in xcode's console","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"our helper tool and the main app both parse the same plist format with separate code. share it via a small package, identical parsing on the fixture set","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"codesign fails in CI with 'resource fork, Finder information, or similar detritus not allowed' and works on my machine","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"menu bar app with a settings window, launch at login, and a graceful path for when the accessibility permission is denied","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"review the entitlements we request and tell me which ones we don't actually need","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"readme for the helper tool: install, the permissions it needs and why, and how to verify it's running","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"map out the sandboxing work for the mac app so we can ship on the app store. what breaks, what needs a temporary exception, what we'd have to drop","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"python: incremental loader for the vendor sftp drops — new files only, checksum verified, and it should quarantine anything that fails schema validation instead of failing the whole run","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"could you explain what the airflow sensor is actually waiting on in the vendor dag? i inherited it and the poke interval seems wrong","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"the schedule_interval is '@daily' but the vendor drops at 23:40 local so we always process yesterday's file","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"our 14 dags each define their own default_args with slightly different retries and owners. one factory, same effective config per dag — list any that change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"one file out of about 300 a day produces rows with the columns shifted right by one. the file looks fine when i open it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"data contract doc for the vendor feed — every column, type, nullability, and what we do when they break it (they will)","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"please plan how we move from airflow to dagster, or decide not to. 14 dags, heavy on sensors, and two people who know airflow","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"swift command line tool that watches a directory and re-signs any new .app bundle it finds, with a launchd plist to keep it running","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the tool prints progress with \\r which looks broken in xcode's console","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"our helper tool and the main app both parse the same plist format with separate code. share it via a small package, identical parsing on the fixture set","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"codesign fails in CI with 'resource fork, Finder information, or similar detritus not allowed' and works on my machine","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"menu bar app with a settings window, launch at login, and a graceful path for when the accessibility permission is denied","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"review the entitlements we request and tell me which ones we don't actually need","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"readme for the helper tool: install, the permissions it needs and why, and how to verify it's running","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"map out the sandboxing work for the mac app so we can ship on the app store. what breaks, what needs a temporary exception, what we'd have to drop","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"xpc service for the privileged operations, with a tight allowlist of what the app can ask it to do","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"onward","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"pasting what the a11y consultant sent, please work through it:\n\nBLOCKERS\n1. Modal dialogs: focus is not moved into the dialog on open; background content is not\n hidden from AT (no aria-hidden / inert on the page container).\n2. Data table sort buttons: no aria-sort, and the sort state is only conveyed by an icon.\n3. Form errors: announced via a toast that disappears in 4s; not associated with the\n fields via aria-describedby.\n4. Custom select: uses role=\"listbox\" but options are divs without role=\"option\".\n5. Contrast: secondary button text #8A8F98 on #F4F5F7 = 2.9:1.\n\nMINOR\n6. Decorative icons missing aria-hidden.\n7. Page titles identical across routes.\n\nWe'd want blockers resolved before the audit report is finalized.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"the secondary button text color needs to hit 4.5:1, pick the nearest token that does","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"our page titles are all 'Acme' — set them per route from the route metadata","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"plan the design token overhaul so contrast is guaranteed by construction, not checked after the fact","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"form field component that wires label, description, and error to the input with the right aria attributes, so we stop getting this wrong per-form","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"explain how our current toast-based error announcement works and why AT users miss it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"pasting what the a11y consultant sent, please work through it:\n\nBLOCKERS\n1. Modal dialogs: focus is not moved into the dialog on open; background content is not\n hidden from AT (no aria-hidden / inert on the page container).\n2. Data table sort buttons: no aria-sort, and the sort state is only conveyed by an icon.\n3. Form errors: announced via a toast that disappears in 4s; not associated with the\n fields via aria-describedby.\n4. Custom select: uses role=\"listbox\" but options are divs without role=\"option\".\n5. Contrast: secondary button text #8A8F98 on #F4F5F7 = 2.9:1.\n\nMINOR\n6. Decorative icons missing aria-hidden.\n7. Page titles identical across routes.\n\nWe'd want blockers resolved before the audit report is finalized.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"the secondary button text color needs to hit 4.5:1, pick the nearest token that does","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"our page titles are all 'Acme' — set them per route from the route metadata","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"plan the design token overhaul so contrast is guaranteed by construction, not checked after the fact","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"form field component that wires label, description, and error to the input with the right aria attributes, so we stop getting this wrong per-form","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"explain how our current toast-based error announcement works and why AT users miss it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"axe checks in CI on the 10 main routes, failing the build on new violations but not on the existing backlog","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"our three select implementations should be one. keep the native-ish behavior of the newest, and every existing usage must still work","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"accessibility conformance report (VPAT-ish) draft based on the audit findings — factual, with the known gaps listed honestly","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"voiceover reads the table header twice for every cell in safari but not in chrome","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"spark structured streaming job from kafka to iceberg, exactly-once with checkpointing, and schema evolution handled without a restart","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"our batch and streaming jobs compute the same aggregates with duplicated logic. share the transformation, and prove the outputs match on a day of data","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the checkpoint location is in /tmp","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"would you write up the lakehouse layout for us — bronze/silver/gold, partitioning per table, and the compaction schedule","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"streaming job falls behind by hours overnight then catches up by 9am. the input rate is flat","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"read the iceberg table properties we set and tell me whether small file compaction is actually running","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"accessibility conformance report (VPAT-ish) draft based on the audit findings — factual, with the known gaps listed honestly","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"voiceover reads the table header twice for every cell in safari but not in chrome","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"spark structured streaming job from kafka to iceberg, exactly-once with checkpointing, and schema evolution handled without a restart","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"our batch and streaming jobs compute the same aggregates with duplicated logic. share the transformation, and prove the outputs match on a day of data","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the checkpoint location is in /tmp","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"would you write up the lakehouse layout for us — bronze/silver/gold, partitioning per table, and the compaction schedule","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"streaming job falls behind by hours overnight then catches up by 9am. the input rate is flat","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"read the iceberg table properties we set and tell me whether small file compaction is actually running","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"figure out the plan for backfilling three years of history into the new lakehouse tables without competing with the live stream","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"data quality dashboard: freshness per table, row count trend, and the failed expectation list from the last run","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"design the lineage story and then build the collector that reads it from the spark listener","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"find out why the freshness metric is wrong and add a note to the data catalog entry","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"picking this back up, whats left","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"we're getting asked for an audit trail by two enterprise prospects and i want to do it once, properly. every mutation, who and what changed, immutable, exportable, queryable by resource and actor, and retained for 7 years without bloating the primary db. write the design","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"audit event capture at the orm layer so no code path can skip it, with the diff stored as a compact json patch","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"we're getting asked for an audit trail by two enterprise prospects and i want to do it once, properly. every mutation, who and what changed, immutable, exportable, queryable by resource and actor, and retained for 7 years without bloating the primary db. write the design","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"audit event capture at the orm layer so no code path can skip it, with the diff stored as a compact json patch","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"audit log viewer: filters for actor, resource type, action and date, a diff view per entry, and csv export of the filtered set","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the audit table has no index on (resource_type, resource_id)","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"the audit table has no index on (resource_type, resource_id)","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"we log audit events from 30 call sites with hand-built payloads. move to the orm hook and remove the manual calls, same events recorded","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"audit entries have a null actor for about 4% of events and i can't tell which code path produces those","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"audit entries have a null actor for about 4% of events and i can't tell which code path produces those","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"is the audit log actually append-only, or can an admin edit it through some path? check the grants and the code","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"compliance-facing doc describing our audit logging: coverage, retention, integrity, and access controls","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"audit export to a customer's s3 bucket nightly, in a documented format, with a manifest","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"compliance-facing doc describing our audit logging: coverage, retention, integrity, and access controls","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"audit export to a customer's s3 bucket nightly, in a documented format, with a manifest","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"export settings page: bucket, role arn, a test connection button, and the last export status","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the export filename uses the local date so we get gaps and duplicates around midnight utc","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the export filename uses the local date so we get gaps and duplicates around midnight utc","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"plan the archival tier for audit data — hot for 90 days in postgres, then s3 with a query path that isn't a lie","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"queries against audit data older than 90 days return empty instead of erroring, so people think there's no data","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"walk me through how a customer's audit export could include another customer's events, if at all","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"docs for the audit export format — one page, the json schema, and a sample file","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"queries against audit data older than 90 days return empty instead of erroring, so people think there's no data","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"walk me through how a customer's audit export could include another customer's events, if at all","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"docs for the audit export format — one page, the json schema, and a sample file","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"extract the diffing code used by audit, version history and the deploy view into one utility. same diffs everywhere","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"por favor, planifica cómo vamos a migrar los reportes a la nueva API sin romper los clientes actuales, con fases","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"es"} {"prompt":"report scheduling: cron per report, delivery by email or s3, timezone per recipient, and skip if the report is empty","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"schedule editor with a human-readable summary under the cron input ('every weekday at 8am in Europe/Berlin')","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the cron input accepts 6 fields but our runner only reads 5","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"scheduled reports fire twice for recipients in timezones with a half-hour offset","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"pdf rendering for reports, headless chrome, with page breaks that don't split table rows and a header on every page","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the pdf uses a font that isn't embedded so cyrillic renders as boxes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"schedule editor with a human-readable summary under the cron input ('every weekday at 8am in Europe/Berlin')","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the cron input accepts 6 fields but our runner only reads 5","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"scheduled reports fire twice for recipients in timezones with a half-hour offset","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"pdf rendering for reports, headless chrome, with page breaks that don't split table rows and a header on every page","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"the pdf uses a font that isn't embedded so cyrillic renders as boxes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"check our pdf pipeline for whether a report can include data the recipient isn't allowed to see","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"help article on scheduled reports: setting one up, the timezone rules, and why an empty report doesn't send","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"yep","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"from the ops channel, please sort out the top two:\n\n> @ravi: heads up, three things piling up\n> 1. the nightly `vacuum_analyze` cron has been failing for 11 days, exit 1, no output captured\n> 2. our terraform state bucket has no versioning on it (found while doing the disaster recovery doc)\n> 3. staging db is a 6 month old dump, people keep testing against unrealistic data\n>\n> also unrelated but the grafana admin password is in the wiki 🙃","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} -{"prompt":"state bucket needs versioning and a lifecycle rule, plus block public access explicitly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"figure out our disaster recovery posture and write the plan — rpo, rto, what we actually test, and where we're lying to ourselves","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"help article on scheduled reports: setting one up, the timezone rules, and why an empty report doesn't send","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"from the ops channel, please sort out the top two:\n\n> @ravi: heads up, three things piling up\n> 1. the nightly `vacuum_analyze` cron has been failing for 11 days, exit 1, no output captured\n> 2. our terraform state bucket has no versioning on it (found while doing the disaster recovery doc)\n> 3. staging db is a 6 month old dump, people keep testing against unrealistic data\n>\n> also unrelated but the grafana admin password is in the wiki 🙃","purpose":"debugging","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"state bucket needs versioning and a lifecycle rule, plus block public access explicitly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"figure out our disaster recovery posture and write the plan — rpo, rto, what we actually test, and where we're lying to ourselves","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"automated staging refresh from a scrubbed prod dump, weekly, with pii replaced deterministically so referential integrity holds","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"the scrubbing script and the seed script both fake user data with different rules. one faker module, same shapes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"cron reports success in our monitoring but the actual command fails, so we didn't notice for 11 days","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"review our backup setup end to end and tell me whether we could actually restore, with the steps someone would follow","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"restore runbook, tested — write it as a checklist with the exact commands and expected output at each step","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"internal status board for scheduled jobs: last run, duration, exit code, and a red row if it hasn't run in 2x its interval","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"cron reports success in our monitoring but the actual command fails, so we didn't notice for 11 days","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"review our backup setup end to end and tell me whether we could actually restore, with the steps someone would follow","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"restore runbook, tested — write it as a checklist with the exact commands and expected output at each step","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"internal status board for scheduled jobs: last run, duration, exit code, and a red row if it hasn't run in 2x its interval","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} {"prompt":"cron wrapper that captures stdout/stderr, reports the exit code to our monitoring, and dead-man-switches if it doesn't run","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"our crontab has 22 entries with inline bash, half with no logging. move them to a scheduled job definition file, same schedules and commands","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the vacuum cron runs at 2am utc which overlaps the backup window","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"plan how we get secrets out of the wiki and into something real, including rotating everything that's been sitting there","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"grafana's admin password, the ci token and two api keys have been in the wiki. rotate them and tell me what depends on each","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"explain what our current monitoring would and wouldn't catch if the primary database went read-only","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"write the security incident procedure for a leaked credential — who does what, in what order, and the comms","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"one more thing then we're done","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"our crontab has 22 entries with inline bash, half with no logging. move them to a scheduled job definition file, same schedules and commands","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the vacuum cron runs at 2am utc which overlaps the backup window","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"plan how we get secrets out of the wiki and into something real, including rotating everything that's been sitting there","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"grafana's admin password, the ci token and two api keys have been in the wiki. rotate them and tell me what depends on each","purpose":"backendImpl","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"explain what our current monitoring would and wouldn't catch if the primary database went read-only","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"write the security incident procedure for a leaked credential — who does what, in what order, and the comms","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"i'd like a design for the multi-step approval workflow the enterprise customers keep asking for. arbitrary approver chains, conditional steps based on amount, delegation when someone's on holiday, and a full audit of who approved what. this feels like it wants to be a state machine but i want your take before we build","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"approval workflow engine: definitions in json, instances tracked per request, and the transitions validated server side","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"approval chain visualizer — steps as a horizontal flow, current step highlighted, completed ones with the approver and timestamp","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the approve button is enabled for people who aren't the current approver","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"the approval state lives in three columns plus a json blob and they can disagree. one representation, and migrate the in-flight instances safely","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"requests occasionally get stuck with no current approver and no way forward except a db edit","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"read the delegation code and tell me if a delegate can approve something the delegator couldn't","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"admin documentation for building approval chains, with three worked examples and the gotchas about conditional steps","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"approval workflow engine: definitions in json, instances tracked per request, and the transitions validated server side","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"approval chain visualizer — steps as a horizontal flow, current step highlighted, completed ones with the approver and timestamp","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the approve button is enabled for people who aren't the current approver","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the approval state lives in three columns plus a json blob and they can disagree. one representation, and migrate the in-flight instances safely","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"requests occasionally get stuck with no current approver and no way forward except a db edit","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"read the delegation code and tell me if a delegate can approve something the delegator couldn't","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"admin documentation for building approval chains, with three worked examples and the gotchas about conditional steps","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"reminder emails for pending approvals — after 24h, then daily, stopping when it moves on, and never on weekends","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"pending approvals inbox with bulk approve for the low-risk category and a required comment for rejections","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"pending approvals inbox with bulk approve for the low-risk category and a required comment for rejections","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} {"prompt":"reminders keep sending after the request is approved","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the weekend check uses the server's timezone not the approver's","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"the weekend check uses the server's timezone not the approver's","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"sketch how we'd let customers define their own conditions without giving them arbitrary code execution","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"expression evaluator for approval conditions — a small safe language, no loops, typed against the request fields","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"condition builder ui: field, operator, value rows with and/or, and a live 'this would match' indicator against a sample request","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"explain how our expression evaluator handles a missing field — null, error, or false? i need to know for the docs","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"reference page for the condition expression language: types, operators, functions, and the evaluation rules for nulls","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"our validation of conditions happens client side only, which is obviously not enough. move the check server side and keep the client one for ux","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"les conditions avec des montants négatifs passent alors qu'elles ne devraient pas. je ne comprends pas pourquoi","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"fr"} -{"prompt":"fine, next","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"could you plan the internationalization work for the product? 40k strings-ish, plurals, rtl for arabic, and the dates and numbers are formatted ad hoc everywhere. i want phases and an idea of what the translation workflow looks like","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"expression evaluator for approval conditions — a small safe language, no loops, typed against the request fields","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"condition builder ui: field, operator, value rows with and/or, and a live 'this would match' indicator against a sample request","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain how our expression evaluator handles a missing field — null, error, or false? i need to know for the docs","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"reference page for the condition expression language: types, operators, functions, and the evaluation rules for nulls","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"our validation of conditions happens client side only, which is obviously not enough. move the check server side and keep the client one for ux","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"les conditions avec des montants négatifs passent alors qu'elles ne devraient pas. je ne comprends pas pourquoi","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"fr"} +{"prompt":"could you plan the internationalization work for the product? 40k strings-ish, plurals, rtl for arabic, and the dates and numbers are formatted ad hoc everywhere. i want phases and an idea of what the translation workflow looks like","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"extraction and message catalog pipeline — pull strings from the code, push to the translation service, pull back and typecheck the keys","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"rtl layout support: logical properties throughout, mirrored icons where appropriate, and the sidebar flipping correctly","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the language switcher lists 'Portuguese' twice, one is pt-BR","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"we concatenate strings for sentences in 60 places which is untranslatable. move to full sentences with placeholders, same rendered english","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"german text overflows the buttons on the dashboard and the labels clip mid-word","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"explain how our plural handling works today, i think it's just a ternary on n !== 1 which won't fly for polish","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"localization guide for engineers: how to add a string, plural rules, what never to concatenate, and how to test a pseudo-locale","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"currency and number formatting through one helper that respects the user's locale, replacing the 30 ad hoc format calls","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"pseudo-locale mode in dev that expands strings 40% and brackets them, toggled by a query param","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"dates show as '2026/7/30' for en-GB users","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"plan how we handle user-generated content in mixed languages — do we detect, do we translate, what do we show","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"german text overflows the buttons on the dashboard and the labels clip mid-word","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"explain how our plural handling works today, i think it's just a ternary on n !== 1 which won't fly for polish","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"localization guide for engineers: how to add a string, plural rules, what never to concatenate, and how to test a pseudo-locale","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"currency and number formatting through one helper that respects the user's locale, replacing the 30 ad hoc format calls","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"pseudo-locale mode in dev that expands strings 40% and brackets them, toggled by a query param","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"dates show as '2026/7/30' for en-GB users","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"plan how we handle user-generated content in mixed languages — do we detect, do we translate, what do we show","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"translated emails render with the english subject line for two of the six locales","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"language picker that remembers the choice per account, falls back to the browser preference, and doesn't flash english first","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"tell me which of our strings are still hardcoded in the templates, and roughly how many","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"translator notes for the 200 strings with ambiguous context — the ones where 'Post' could be a verb or a noun","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"language picker that remembers the choice per account, falls back to the browser preference, and doesn't flash english first","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"tell me which of our strings are still hardcoded in the templates, and roughly how many","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"translator notes for the 200 strings with ambiguous context — the ones where 'Post' could be a verb or a noun","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"design the offline mode for the web app and then implement the service worker caching layer","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"look over the i18n helper and clean up the api while keeping the same output","purpose":"review","secondary":"refactor","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} -{"prompt":"carry on","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"here's the whole failing CI output, i've read it four times and i'm none the wiser:\n\nRun make integration\ndocker compose -f compose.ci.yml up -d --wait\n[+] Running 4/5\n ✔ Container ci-postgres-1 Healthy 8.1s\n ✔ Container ci-redis-1 Healthy 2.0s\n ✔ Container ci-minio-1 Healthy 3.4s\n ✘ Container ci-api-1 Error 31.2s\ndependency failed to start: container ci-api-1 exited (1)\n\ndocker compose logs api:\nci-api-1 | 2026/07/30 06:11:02 connecting to postgres host=postgres port=5432 db=acme\nci-api-1 | 2026/07/30 06:11:02 migrate: dirty database version 214, fix and force version\nci-api-1 | 2026/07/30 06:11:02 startup failed: migrate up: Dirty database version 214\n\nmake: *** [Makefile:41: integration] Error 1\n\nthe postgres container is fresh every run so how is it dirty","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"migration runner should fail loudly on a dirty state at startup instead of after partially connecting, and never leave it dirty on a failed apply","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the compose healthcheck for api uses curl which isn't in the image","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"plan how we make local dev and CI use the same compose setup so 'works on my machine' stops being a thing","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"we have compose.yml, compose.ci.yml and compose.local.yml with 80% overlap and three different postgres versions. consolidate with overrides, same effective services per environment","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"explain what the --wait flag actually waits for and whether our healthchecks mean what we think","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"look over the i18n helper and clean up the api while keeping the same output","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"here's the whole failing CI output, i've read it four times and i'm none the wiser:\n\nRun make integration\ndocker compose -f compose.ci.yml up -d --wait\n[+] Running 4/5\n ✔ Container ci-postgres-1 Healthy 8.1s\n ✔ Container ci-redis-1 Healthy 2.0s\n ✔ Container ci-minio-1 Healthy 3.4s\n ✘ Container ci-api-1 Error 31.2s\ndependency failed to start: container ci-api-1 exited (1)\n\ndocker compose logs api:\nci-api-1 | 2026/07/30 06:11:02 connecting to postgres host=postgres port=5432 db=acme\nci-api-1 | 2026/07/30 06:11:02 migrate: dirty database version 214, fix and force version\nci-api-1 | 2026/07/30 06:11:02 startup failed: migrate up: Dirty database version 214\n\nmake: *** [Makefile:41: integration] Error 1\n\nthe postgres container is fresh every run so how is it dirty","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"migration runner should fail loudly on a dirty state at startup instead of after partially connecting, and never leave it dirty on a failed apply","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the compose healthcheck for api uses curl which isn't in the image","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"plan how we make local dev and CI use the same compose setup so 'works on my machine' stops being a thing","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"we have compose.yml, compose.ci.yml and compose.local.yml with 80% overlap and three different postgres versions. consolidate with overrides, same effective services per environment","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"explain what the --wait flag actually waits for and whether our healthchecks mean what we think","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"developer setup doc that works from a clean machine, including the two things people always get stuck on","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"seeded dev data that's actually representative — 5 orgs of different sizes, a big one with 50k records, and edge cases like unicode names","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"dev toolbar in the app showing the current user, org, feature flags and a way to switch, only in non-prod","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the dev toolbar renders in production if you set the query param","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"tests pass on linux and fail on macos with a file path assertion","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"review the makefile and tell me which targets are broken or reference things that don't exist","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"write the architecture overview for new joiners — the six services, what talks to what, and where to start reading","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"seeded dev data that's actually representative — 5 orgs of different sizes, a big one with 50k records, and edge cases like unicode names","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"dev toolbar in the app showing the current user, org, feature flags and a way to switch, only in non-prod","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the dev toolbar renders in production if you set the query param","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"tests pass on linux and fail on macos with a file path assertion","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"review the makefile and tell me which targets are broken or reference things that don't exist","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"write the architecture overview for new joiners — the six services, what talks to what, and where to start reading","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"map out the plan for a proper preview environment per PR — database, seeded data, and a url in the PR comment","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"preview environment provisioner: namespace per PR, a database branch, teardown on merge or after 3 days idle","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"our test helpers reach into private methods in 40 places which makes any refactor a nightmare. rework them to use public seams, same coverage","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"our test helpers reach into private methods in 40 places which makes any refactor a nightmare. rework them to use public seams, same coverage","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"preview envs leak — we have 60 namespaces for 12 open PRs","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"figure out the design for our staging data privacy story, then implement the scrubber","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"just finish the last bit please","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"figure out the design for our staging data privacy story, then implement the scrubber","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} {"prompt":"- transcode ladder: 240p to 1080p, 5 rungs\n- per-title encoding would be nice but not v1\n- must handle a 4h source without blowing memory\n- output HLS + DASH from one pass if possible\n- retry a failed rung without redoing the whole thing\n\nwrite the design for this before anyone touches ffmpeg","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"transcode worker that shells out to ffmpeg per rung, streams progress to redis, and cleans up temp files even when it's killed","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"video player controls: scrubber with buffered ranges, quality menu, captions toggle, and keyboard shortcuts that match youtube's","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"video player controls: scrubber with buffered ranges, quality menu, captions toggle, and keyboard shortcuts that match youtube's","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"the hls segment length is 10s, drop it to 4","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"our ffmpeg args are built by string concatenation in four places with different escaping. one builder, byte-identical commands for the existing presets","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"some uploads produce a manifest with a 0-duration segment at the end and safari refuses to play it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain how our player picks the initial rung, i want to know if it's bandwidth estimation or just the lowest","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"docs for the playback api — the manifest urls, token expiry, and the drm handshake steps","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"some uploads produce a manifest with a 0-duration segment at the end and safari refuses to play it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain how our player picks the initial rung, i want to know if it's bandwidth estimation or just the lowest","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"docs for the playback api — the manifest urls, token expiry, and the drm handshake steps","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"signed playback tokens, short lived, bound to the session and the asset, and rotate without breaking an in-progress stream","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"thumbnail sprite generation at 1 frame per 5 seconds plus the vtt, for scrub previews","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"scrub preview thumbnails on hover, positioned above the cursor and clamped to the player bounds","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"thumbnail sprite generation at 1 frame per 5 seconds plus the vtt, for scrub previews","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"scrub preview thumbnails on hover, positioned above the cursor and clamped to the player bounds","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"captions default to on, should default to off unless the user's set it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"playback stalls at the exact same timestamp for one asset on every device. the segment downloads fine with curl","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"playback stalls at the exact same timestamp for one asset on every device. the segment downloads fine with curl","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"plan the live streaming feature — ingest, low latency hls, dvr window, and what we do when the broadcaster's connection drops for 10 seconds","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"read the packager code and tell me whether we're actually producing CMAF or just calling it that","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"read the packager code and tell me whether we're actually producing CMAF or just calling it that","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"encoding guide for content partners: accepted source formats, the bitrate we want, audio loudness target, and what we reject","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"rust: wasm module for client-side thumbnail decoding so the editor can scrub without hitting the server","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"rust: wasm module for client-side thumbnail decoding so the editor can scrub without hitting the server","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the wasm bundle is 4mb because we're not running wasm-opt","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"our rust crate has three error enums that wrap each other with From impls that lose context. one error type with a proper source chain, same failure classification","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"wasm panics in firefox only, with 'unreachable executed' and no useful stack","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"prism design system: build the Button with variants, sizes, loading state, and icon slots. it needs to work as a link too without duplicating styles","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"our component library exports 60 components and 40 of them re-declare the same size and tone props. extract shared prop types and variant logic, no visual change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"check the design system for components that don't forward refs, several of our composition patterns break because of it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"component docs for prism: props table per component, do/don't examples, and the accessibility notes we keep forgetting","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"keep going pls","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"we're at the point where the design system needs a real versioning and adoption strategy. three apps consume it, one is pinned to a version from january, and every breaking change turns into a week of coordination. write the plan — semver policy, codemods, deprecation windows, and how we get the pinned app current","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"our rust crate has three error enums that wrap each other with From impls that lose context. one error type with a proper source chain, same failure classification","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"wasm panics in firefox only, with 'unreachable executed' and no useful stack","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"prism design system: build the Button with variants, sizes, loading state, and icon slots. it needs to work as a link too without duplicating styles","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"our component library exports 60 components and 40 of them re-declare the same size and tone props. extract shared prop types and variant logic, no visual change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"check the design system for components that don't forward refs, several of our composition patterns break because of it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"component docs for prism: props table per component, do/don't examples, and the accessibility notes we keep forgetting","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"we're at the point where the design system needs a real versioning and adoption strategy. three apps consume it, one is pinned to a version from january, and every breaking change turns into a week of coordination. write the plan — semver policy, codemods, deprecation windows, and how we get the pinned app current","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"codemod that migrates the old Button props to the new api, handling the spread case and leaving a comment where it can't be sure","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"storybook stories for every component state including the ones we forget: loading, error, empty, and rtl","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the package's peerDependencies allows react 17 which we don't support anymore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"visual regression snapshots differ by a pixel on CI vs local for every text-containing component","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"tell me which components changed public api between 3.x and 4.x, from the code not the changelog","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"migration guide from prism 3 to 4, per component, with the codemod command for the ones we can automate","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"the package's peerDependencies allows react 17 which we don't support anymore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"visual regression snapshots differ by a pixel on CI vs local for every text-containing component","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"tell me which components changed public api between 3.x and 4.x, from the code not the changelog","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"migration guide from prism 3 to 4, per component, with the codemod command for the ones we can automate","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"tokens pipeline: figma variables to json to css custom properties and swift/kotlin constants, in one build step","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the token names in figma use spaces and our generator produces invalid css var names for those","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the token names in figma use spaces and our generator produces invalid css var names for those","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"our dark theme is a separate stylesheet that has drifted from light. derive both from tokens instead, and light mode must render identically to today","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"one component reads a token that doesn't exist in dark mode and falls back to black on black","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"one component reads a token that doesn't exist in dark mode and falls back to black on black","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"theme switcher with no flash of the wrong theme on first paint, and it should follow the system by default","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"outline how we'd support customer theming — how far we let them go, what stays fixed, and how we keep contrast legal","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain the cascade layers we use and whether a consumer's css can override our component styles by accident","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"write the theming docs for customers: what's themeable, the contrast requirements we enforce, and the preview flow","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"brand color picker with a live preview of six components and a warning when a combination fails contrast","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"server side theme resolution so the first byte already has the right variables, no client flash","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"outline how we'd support customer theming — how far we let them go, what stays fixed, and how we keep contrast legal","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"explain the cascade layers we use and whether a consumer's css can override our component styles by accident","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"write the theming docs for customers: what's themeable, the contrast requirements we enforce, and the preview flow","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"brand color picker with a live preview of six components and a warning when a combination fails contrast","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"server side theme resolution so the first byte already has the right variables, no client flash","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} {"prompt":"the contrast check helper uses the wrong luminance formula for the alpha case","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"design the icon system then implement the sprite build","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"figure out why the theme flashes and then note the fix in the design system readme","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"ok do that","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"picking up the ingest rewrite from last sprint. next piece is the dedupe — events arrive up to 3 times from the edge, keyed by (source, event_id), and the window needs to cover a 6 hour replay. build it","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"plan the edge ingest topology: workers per region, a durable buffer, and what happens when the central pipeline is down for an hour","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"ingest health page: events per second per region, dedupe rate, and the lag from edge to warehouse","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the dedupe window is 15 minutes, needs to be 6 hours","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"the edge worker and the central consumer both validate the event envelope with separate schemas that have drifted. one schema, generated, and list any events that would now be rejected","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"events from one region are 40 minutes stale but the region reports healthy and the queue is empty","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"walk me through what our edge buffer does when its disk fills up","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"write the event ingest api docs for our sdk authors — the envelope, the required fields, batching limits, and the dedupe contract","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"batch endpoint accepting up to 500 events with per-event accept/reject in the response, and a 413 with a clear message over that","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"design the icon system then implement the sprite build","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"figure out why the theme flashes and then note the fix in the design system readme","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"picking up the ingest rewrite from last sprint. next piece is the dedupe — events arrive up to 3 times from the edge, keyed by (source, event_id), and the window needs to cover a 6 hour replay. build it","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"plan the edge ingest topology: workers per region, a durable buffer, and what happens when the central pipeline is down for an hour","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"ingest health page: events per second per region, dedupe rate, and the lag from edge to warehouse","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the dedupe window is 15 minutes, needs to be 6 hours","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"the edge worker and the central consumer both validate the event envelope with separate schemas that have drifted. one schema, generated, and list any events that would now be rejected","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"events from one region are 40 minutes stale but the region reports healthy and the queue is empty","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"walk me through what our edge buffer does when its disk fills up","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"write the event ingest api docs for our sdk authors — the envelope, the required fields, batching limits, and the dedupe contract","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"batch endpoint accepting up to 500 events with per-event accept/reject in the response, and a 413 with a clear message over that","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"debug console showing the last 100 events received for a source, live, with the raw payload expandable","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the 413 response has an empty body","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"propose how we handle schema evolution on customer-defined event properties without the warehouse table exploding to 4000 columns","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"events with a property that changes type between string and number silently land as null in the warehouse","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the 413 response has an empty body","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"propose how we handle schema evolution on customer-defined event properties without the warehouse table exploding to 4000 columns","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"events with a property that changes type between string and number silently land as null in the warehouse","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"check whether a customer can send us an event that ends up in another customer's dataset, via the source id or otherwise","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"our property type coercion lives in the edge worker, the consumer and the warehouse loader with three sets of rules. unify, and report which historical events would be typed differently","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"docs page explaining property types, how we coerce, and what happens when a property changes type","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"wieder da — als nächstes bitte den Retry-Pfad für den Warehouse-Loader implementieren, idempotent pro Tagespartition","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"de"} -{"prompt":"warehouse loader with per-partition idempotency, a manifest of loaded files, and a repair mode for a single day","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the loader's manifest table has no unique constraint so a double load is possible","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"plan how we prove the pipeline is lossless — reconciliation counts at each hop and an alert when they diverge","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"our property type coercion lives in the edge worker, the consumer and the warehouse loader with three sets of rules. unify, and report which historical events would be typed differently","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"docs page explaining property types, how we coerce, and what happens when a property changes type","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"wieder da — als nächstes bitte den Retry-Pfad für den Warehouse-Loader implementieren, idempotent pro Tagespartition","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} +{"prompt":"warehouse loader with per-partition idempotency, a manifest of loaded files, and a repair mode for a single day","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the loader's manifest table has no unique constraint so a double load is possible","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"plan how we prove the pipeline is lossless — reconciliation counts at each hop and an alert when they diverge","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"reconciliation dashboard: counts per hop per hour, with the divergence highlighted and a drill-in to the missing ids","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"counts match at the edge and the consumer but the warehouse is short by 0.02% every day","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"explain the delivery guarantee we actually provide end to end today, hop by hop","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"counts match at the edge and the consumer but the warehouse is short by 0.02% every day","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"explain the delivery guarantee we actually provide end to end today, hop by hop","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"sla doc for data freshness and completeness, with what we commit to and how we measure it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"vamos","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"es"} -{"prompt":"here's the crash report from testflight, 40 users hit this yesterday:\n\nIncident Identifier: 8B21F4A1-...\nHardware Model: iPhone16,2\nOS Version: iPhone OS 26.1 (23B74)\n\nException Type: EXC_BREAKPOINT (SIGTRAP)\nException Codes: 0x0000000000000001, 0x00000001045f21c4\nTriggered by Thread: 0\n\nThread 0 name: Dispatch queue: com.apple.main-thread\nThread 0 Crashed:\n0 Halyard 0x1045f21c4 HalyardCore.MediaCache.evict(to:) + 340 (MediaCache.swift:188)\n1 Halyard 0x1045f0a08 HalyardCore.MediaCache.insert(_:key:) + 212 (MediaCache.swift:141)\n2 Halyard 0x10460b114 closure #1 in HalyardUI.FeedViewModel.prefetch() + 96 (FeedViewModel.swift:77)\n3 libswift_Concurrency.dylib 0x1a2f1c880 swift_task_switch + 60\n\nMediaCache.swift:188 is `precondition(bytes >= 0)`. so we're going negative on the byte count somewhere","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"rewrite MediaCache with an actor so the byte accounting can't race, same eviction policy and the same cache hit behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"here's the crash report from testflight, 40 users hit this yesterday:\n\nIncident Identifier: 8B21F4A1-...\nHardware Model: iPhone16,2\nOS Version: iPhone OS 26.1 (23B74)\n\nException Type: EXC_BREAKPOINT (SIGTRAP)\nException Codes: 0x0000000000000001, 0x00000001045f21c4\nTriggered by Thread: 0\n\nThread 0 name: Dispatch queue: com.apple.main-thread\nThread 0 Crashed:\n0 Halyard 0x1045f21c4 HalyardCore.MediaCache.evict(to:) + 340 (MediaCache.swift:188)\n1 Halyard 0x1045f0a08 HalyardCore.MediaCache.insert(_:key:) + 212 (MediaCache.swift:141)\n2 Halyard 0x10460b114 closure #1 in HalyardUI.FeedViewModel.prefetch() + 96 (FeedViewModel.swift:77)\n3 libswift_Concurrency.dylib 0x1a2f1c880 swift_task_switch + 60\n\nMediaCache.swift:188 is `precondition(bytes >= 0)`. so we're going negative on the byte count somewhere","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"rewrite MediaCache with an actor so the byte accounting can't race, same eviction policy and the same cache hit behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the cache size limit is 50mb which is nothing for video, make it 500","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"prefetching for the feed: next two items, cancelled when they scroll past, and never on cellular unless the user allowed it","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"feed cells that autoplay muted when 60% visible and pause otherwise, with a smooth first frame instead of a black flash","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"review our media cache eviction and tell me whether a large item can starve everything else","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"prefetching for the feed: next two items, cancelled when they scroll past, and never on cellular unless the user allowed it","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"feed cells that autoplay muted when 60% visible and pause otherwise, with a smooth first frame instead of a black flash","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"review our media cache eviction and tell me whether a large item can starve everything else","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"plan the offline downloads feature for the ios app — what's stored, the drm license, storage limits, and what happens when the user's subscription lapses","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"internal doc on how the media cache and the download store relate, they're two things and everyone thinks they're one","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"internal doc on how the media cache and the download store relate, they're two things and everyone thinks they're one","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"downloads screen with per-item progress, pause/resume, storage used, and a delete-all with the space it'll free","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"downloaded items disappear after an app update","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the download directory is in Documents so it's backed up to icloud, move it to Application Support with the exclude flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"license renewal for downloads in the background, before expiry, and a clear state in the ui when it fails","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"tell me how our download license expiry interacts with the device being offline for a month","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"downloaded items disappear after an app update","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the download directory is in Documents so it's backed up to icloud, move it to Application Support with the exclude flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"license renewal for downloads in the background, before expiry, and a clear state in the ui when it fails","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"tell me how our download license expiry interacts with the device being offline for a month","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"help article about downloads: what you can download, how long it stays, and the device limit","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"map out the plan for a tv app — which platforms, how much we share with ios, and the focus-engine work","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"our playback state is duplicated between the player wrapper and the view model, and they disagree during seeks. one source of truth","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"sure go","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"need a decision on our api pagination before the sdk ships. we currently return a `next_url` on some endpoints, page numbers on others, and one endpoint returns everything. i want one scheme, the reasoning, and the migration for the two public endpoints that already have consumers","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"cursor pagination on the remaining 14 endpoints, opaque cursors, stable ordering, and a hard max page size of 200","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"map out the plan for a tv app — which platforms, how much we share with ios, and the focus-engine work","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"our playback state is duplicated between the player wrapper and the view model, and they disagree during seeks. one source of truth","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"need a decision on our api pagination before the sdk ships. we currently return a `next_url` on some endpoints, page numbers on others, and one endpoint returns everything. i want one scheme, the reasoning, and the migration for the two public endpoints that already have consumers","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"cursor pagination on the remaining 14 endpoints, opaque cursors, stable ordering, and a hard max page size of 200","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"infinite list with a load-more button as a fallback and a live 'showing X of Y' when we know the total","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the page size param is capped at 1000 in one endpoint and unbounded in another","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"our list endpoints each implement their own pagination inline. one shared helper, and every endpoint returns the same result set as before","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the page size param is capped at 1000 in one endpoint and unbounded in another","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"our list endpoints each implement their own pagination inline. one shared helper, and every endpoint returns the same result set as before","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"paging through a list while items are being created skips records, and the cursor is supposedly stable","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"does our cursor encode enough to be stable if the sort column has duplicate values? check the encoding","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"pagination section for the api docs — the cursor contract, what's guaranteed, and the recommended loop with a code sample","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"filtering and sorting params across the list endpoints, consistent syntax, and reject unknown fields rather than ignoring them","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"filter builder ui that maps to the api's filter syntax, with a raw mode for power users","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"sorting by a nullable column puts nulls first ascending and first descending too","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"does our cursor encode enough to be stable if the sort column has duplicate values? check the encoding","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"pagination section for the api docs — the cursor contract, what's guaranteed, and the recommended loop with a code sample","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"filtering and sorting params across the list endpoints, consistent syntax, and reject unknown fields rather than ignoring them","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"filter builder ui that maps to the api's filter syntax, with a raw mode for power users","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"sorting by a nullable column puts nulls first ascending and first descending too","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"the default sort is by id which looks random to users, make it created_at desc","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"sketch out how we'd support field selection (sparse fieldsets) without letting someone request a 40-way join","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"sketch out how we'd support field selection (sparse fieldsets) without letting someone request a 40-way join","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"look at our filter parsing for injection risk, it builds sql fragments and i want to know how carefully","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"reference doc for the filter syntax — operators per type, combining rules, and the limits","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"our query param parsing accepts both snake_case and camelCase inconsistently per endpoint. pick snake_case, accept camel with a deprecation header for two releases","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"reference doc for the filter syntax — operators per type, combining rules, and the limits","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"our query param parsing accepts both snake_case and camelCase inconsistently per endpoint. pick snake_case, accept camel with a deprecation header for two releases","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} {"prompt":"plan the api v3 surface and then implement the new list endpoints","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"explain how the cursor works and then document it properly","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} -{"prompt":"next up?","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"our admin tooling is 40 rails views bolted on over four years and support can't do half of what they need without asking an engineer. i want the plan for a real internal tool: what support can do, the audit and permission model, and whether we build it or use retool","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"support impersonation with a banner, a time limit, full audit, and a hard block on the destructive actions","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"admin customer view: account summary, recent activity, subscription state, and the five actions support actually uses, all above the fold","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the impersonation banner is grey and people miss it, make it unmissable","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"our admin actions bypass the normal service layer and write directly. route them through the same services so validation and audit apply","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"explain how the cursor works and then document it properly","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"our admin tooling is 40 rails views bolted on over four years and support can't do half of what they need without asking an engineer. i want the plan for a real internal tool: what support can do, the audit and permission model, and whether we build it or use retool","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"support impersonation with a banner, a time limit, full audit, and a hard block on the destructive actions","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"admin customer view: account summary, recent activity, subscription state, and the five actions support actually uses, all above the fold","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the impersonation banner is grey and people miss it, make it unmissable","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"our admin actions bypass the normal service layer and write directly. route them through the same services so validation and audit apply","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} {"prompt":"a support action to reset a user's password sends the email to the admin's address about 1 in 20 times","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"list what actions in the admin tool have no audit record","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"list what actions in the admin tool have no audit record","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"support playbook: the ten most common tickets, what to check, and the exact admin action for each","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"bulk operations for support — apply a change to a list of accounts from a pasted csv, with a preview and a dry run","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"bulk action review screen: what will change per row, warnings for the risky ones, and a typed confirmation for over 100 rows","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"csv paste with a trailing newline creates one empty row that errors","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"figure out the permissions model for internal tools — roles for support, finance, and engineering, with least privilege actually enforced","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"a finance role can see the admin routes for account deletion even though the nav hides them","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"does hiding a nav item ever equal enforcing a permission in our admin? show me where the checks are","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"internal doc listing the admin roles and exactly what each can do, for the soc2 evidence","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the admin authorization is a mix of before_actions, view conditionals and a helper. one policy layer, same effective access for every existing role","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"ちょっと戻ってきた。次は管理画面の一括操作にプレビューを付けたい、まず設計から","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"ja"} -{"prompt":"half done, take it from here","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"i want the plan for making our onboarding not terrible. current state: 11 steps, 40% drop off at step 4 (workspace setup), no way to skip, and the empty product afterwards. i'd like the redesign proposal with what we can cut and what we measure","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"workspace provisioning on signup — create the org, the default project, sample data, and an invite link, all in one transaction-ish flow with rollback if a step fails","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"new onboarding: 4 steps, progress bar, skip-for-now on every step, and it resumes where you left off if you close the tab","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"step 2's continue button is disabled until a field that's supposedly optional is filled","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"the onboarding state is tracked in three places — a users column, localstorage, and a segment trait. one source of truth, and existing half-onboarded users must not be sent back to step 1","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"some users land in the product with no default project and everything 404s. can't tell which signup path does it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"bulk operations for support — apply a change to a list of accounts from a pasted csv, with a preview and a dry run","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"bulk action review screen: what will change per row, warnings for the risky ones, and a typed confirmation for over 100 rows","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"csv paste with a trailing newline creates one empty row that errors","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"figure out the permissions model for internal tools — roles for support, finance, and engineering, with least privilege actually enforced","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"a finance role can see the admin routes for account deletion even though the nav hides them","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"does hiding a nav item ever equal enforcing a permission in our admin? show me where the checks are","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"internal doc listing the admin roles and exactly what each can do, for the soc2 evidence","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the admin authorization is a mix of before_actions, view conditionals and a helper. one policy layer, same effective access for every existing role","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"ちょっと戻ってきた。次は管理画面の一括操作にプレビューを付けたい、まず設計から","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"} +{"prompt":"i want the plan for making our onboarding not terrible. current state: 11 steps, 40% drop off at step 4 (workspace setup), no way to skip, and the empty product afterwards. i'd like the redesign proposal with what we can cut and what we measure","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"workspace provisioning on signup — create the org, the default project, sample data, and an invite link, all in one transaction-ish flow with rollback if a step fails","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"new onboarding: 4 steps, progress bar, skip-for-now on every step, and it resumes where you left off if you close the tab","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"step 2's continue button is disabled until a field that's supposedly optional is filled","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the onboarding state is tracked in three places — a users column, localstorage, and a segment trait. one source of truth, and existing half-onboarded users must not be sent back to step 1","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"some users land in the product with no default project and everything 404s. can't tell which signup path does it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"trace every path into the app that creates a user, i suspect there are more than the three i know about","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"onboarding email sequence copy, 4 emails, tied to what the user has and hasn't done","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"sample data generator that produces a believable small workspace, deleteable in one click","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"empty states across the six main screens with a single clear next action each, replacing the current 'no data' text","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"onboarding email sequence copy, 4 emails, tied to what the user has and hasn't done","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"sample data generator that produces a believable small workspace, deleteable in one click","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"empty states across the six main screens with a single clear next action each, replacing the current 'no data' text","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"the sample data has 2024 dates so everything looks stale","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"plan the activation metrics — what counts as activated, how we instrument it, and the funnel we report weekly","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the funnel numbers in amplitude don't match our db counts by about 15% and i don't know which to trust","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"explain what our signup analytics events fire on, exactly, because i think one fires before the account exists","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"tracking plan doc: every onboarding event, when it fires, its properties, and who owns it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"the funnel numbers in amplitude don't match our db counts by about 15% and i don't know which to trust","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain what our signup analytics events fire on, exactly, because i think one fires before the account exists","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"tracking plan doc: every onboarding event, when it fires, its properties, and who owns it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"our analytics calls are sprinkled inline in components. move them behind a typed tracking module, same events with the same properties","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"invite flow: multiple emails at once, role per invite, resend, revoke, and a clear state for pending vs accepted","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"invite flow: multiple emails at once, role per invite, resend, revoke, and a clear state for pending vs accepted","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"members page with pending invites in the same list, greyed, with resend and revoke inline","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"an expired invite link says 'something went wrong' instead of 'this invite expired'","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"accepting an invite while logged into a different account joins the wrong account","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"check the invite token for whether it can be reused after acceptance, and whether it leaks the org name to a stranger","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"accepting an invite while logged into a different account joins the wrong account","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"check the invite token for whether it can be reused after acceptance, and whether it leaks the org name to a stranger","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"invite email copy plus the landing page copy for someone who's never heard of us","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"design the team roles model then build the invite-with-role part","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"design the team roles model then build the invite-with-role part","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"review the onboarding code and fix the small stuff you find","purpose":"review","secondary":"quickFix","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} -{"prompt":"thats it for now, just tidy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"need a design for group calls. currently p2p mesh which dies above 4 people. sfu vs mcu, self hosted vs a vendor, and what our bandwidth and cpu budget is per participant on a laptop. write it up with a recommendation","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"sfu integration: publish one stream up, subscribe to n down, simulcast three layers, and drop the top layer when cpu is high","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"call grid layout — speaker view and gallery, active speaker border, and it must reflow without a jarring jump when someone joins","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the mute button says 'Mute' when you're already muted","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"our peer connection setup is duplicated for the 1:1 path and the group path with subtly different ice config. one implementation, same connection behavior in both modes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"audio drops for one participant after about 8 minutes, every time, and reconnecting fixes it. only on wifi","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"explain our ice candidate gathering and whether we're actually using the turn server or falling back to it silently","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"write up the network requirements doc for customers — ports, the turn fallback, and the bandwidth per participant at each quality","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"sfu integration: publish one stream up, subscribe to n down, simulcast three layers, and drop the top layer when cpu is high","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"call grid layout — speaker view and gallery, active speaker border, and it must reflow without a jarring jump when someone joins","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the mute button says 'Mute' when you're already muted","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"our peer connection setup is duplicated for the 1:1 path and the group path with subtly different ice config. one implementation, same connection behavior in both modes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"audio drops for one participant after about 8 minutes, every time, and reconnecting fixes it. only on wifi","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"explain our ice candidate gathering and whether we're actually using the turn server or falling back to it silently","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"write up the network requirements doc for customers — ports, the turn fallback, and the bandwidth per participant at each quality","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"screen share with audio, tab or window or full screen, and a clear indicator to the sharer that they're sharing","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"screen share picks the wrong monitor on multi-display macs","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"call recording — server side composite, uploaded when the call ends, with the participants' consent recorded","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the recording indicator only shows for the person who started it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"the recording indicator only shows for the person who started it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"phoenix: presence tracking for the call room, with a channel per room and a clean leave on socket close","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"our genservers hold state that should be in ets and it's why a crash loses the room. rework it, same behavior when nothing crashes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the channel timeout is 60s and mobile clients get dropped when the app backgrounds","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"ghost participants stay in the presence list after they close the tab, sometimes for minutes","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"could you explain how our supervision tree handles a room process crashing — do the clients reconnect and rejoin automatically","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"docs for the realtime channel api — the events, their payloads, and the reconnect protocol clients must implement","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"our genservers hold state that should be in ets and it's why a crash loses the room. rework it, same behavior when nothing crashes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the channel timeout is 60s and mobile clients get dropped when the app backgrounds","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"ghost participants stay in the presence list after they close the tab, sometimes for minutes","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"could you explain how our supervision tree handles a room process crashing — do the clients reconnect and rejoin automatically","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"docs for the realtime channel api — the events, their payloads, and the reconnect protocol clients must implement","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"plan how we scale the phoenix layer past one node — distributed presence, pubsub across nodes, and sticky-ish routing","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"browser extension: content script that highlights our resource ids on any page and shows a hover card with the status","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"manifest v2 to v3 migration for the extension, background page to service worker, and the webRequest bits that no longer exist","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the extension requests and we only need two domains","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"extension loses its auth token whenever chrome suspends the service worker, users have to re-login daily","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"manifest v2 to v3 migration for the extension, background page to service worker, and the webRequest bits that no longer exist","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"the extension requests and we only need two domains","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"extension loses its auth token whenever chrome suspends the service worker, users have to re-login daily","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"review the extension's permissions and message passing for anything a malicious page could exploit","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"im back, whats the state of things","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"so ive been putting off the chat feature but sales keeps promising it. i want the plan: message storage, ordering, read receipts, typing indicators, attachments, and search. and it has to work in the mobile apps offline. whats the smallest thing we can ship that we wont have to throw away","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"message storage with per-conversation ordering, server-assigned sequence numbers, and a client-generated id for dedupe on retry","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"message list: bubbles, day separators, tail grouping for consecutive messages from one person, and it scrolls to the right place on open","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"so ive been putting off the chat feature but sales keeps promising it. i want the plan: message storage, ordering, read receipts, typing indicators, attachments, and search. and it has to work in the mobile apps offline. whats the smallest thing we can ship that we wont have to throw away","purpose":"planning","secondary":null,"mixed":false,"difficulty":1,"slice":"core","lang":"en"} +{"prompt":"message storage with per-conversation ordering, server-assigned sequence numbers, and a client-generated id for dedupe on retry","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"message list: bubbles, day separators, tail grouping for consecutive messages from one person, and it scrolls to the right place on open","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"timestamps show seconds, drop to minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"we render messages in three places — the chat, the search results and the notification preview — each parsing markdown differently. one renderer","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"messages sometimes appear twice for the sender and once for everyone else","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"does our read receipt update leak that a user read a message in a conversation they were later removed from","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"chat api docs: sending, the sequence number contract, pagination backwards through history, and the delivery semantics","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"messages sometimes appear twice for the sender and once for everyone else","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"does our read receipt update leak that a user read a message in a conversation they were later removed from","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"chat api docs: sending, the sequence number contract, pagination backwards through history, and the delivery semantics","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"typing indicators over the existing channel, throttled, and they should stop on send or after 5s of no keystrokes","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the typing indicator says 'X is typing' for people who left the conversation","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the typing indicator says 'X is typing' for people who left the conversation","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"attachments in chat: upload with a progress bubble, image previews inline, and a retry on the failed ones","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"attachment uploads succeed but the message never posts if the user navigates away","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"attachment uploads succeed but the message never posts if the user navigates away","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"plan the message search — per-conversation and global, respecting permissions, and it can't scan the whole table","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain how a message's permissions are evaluated at read time versus indexed at write time, from the code","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"explain how a message's permissions are evaluated at read time versus indexed at write time, from the code","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"user help page for chat: mentions, formatting, editing and deleting rules, and what other people see when you edit","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"message editing with an edit history, a 15 minute window, and an 'edited' marker","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the edit window is enforced client side only","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"our conversation membership checks are done in the resolver, the channel and the push sender separately, and one of them is wrong. one check","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"message editing with an edit history, a 15 minute window, and an 'edited' marker","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"the edit window is enforced client side only","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"our conversation membership checks are done in the resolver, the channel and the push sender separately, and one of them is wrong. one check","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} {"prompt":"design the mention and notification rules for chat, then implement the mention parser","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"work out why messages duplicate and then update the client integration docs","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"keep at it pls","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"pasting the chrome devtools output, would you mind having a look:\n\nUncaught (in promise) DOMException: Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote answer sdp: Called in wrong state: stable\n at negotiate (call-session.js:212:22)\n at RTCPeerConnection. (call-session.js:188:9)\n\ncall-session.js:241 [call] renegotiation requested while state=have-local-offer, queuing\ncall-session.js:241 [call] renegotiation requested while state=have-local-offer, queuing\ncall-session.js:241 [call] renegotiation requested while state=have-local-offer, queuing\ncall-session.js:266 [call] ice connection state: disconnected\ncall-session.js:266 [call] ice connection state: failed\n\nthis happens when two people turn their camera on at the same moment. i think its a glare/renegotiation thing but i dont know the right pattern","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"implement perfect negotiation properly in the call session — polite/impolite peer, offer collision handling, and a queue that doesn't grow forever","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"our signalling messages are untyped objects with a `type` string checked in a switch. define the message types properly, same wire format","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"work out why messages duplicate and then update the client integration docs","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"pasting the chrome devtools output, would you mind having a look:\n\nUncaught (in promise) DOMException: Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote answer sdp: Called in wrong state: stable\n at negotiate (call-session.js:212:22)\n at RTCPeerConnection. (call-session.js:188:9)\n\ncall-session.js:241 [call] renegotiation requested while state=have-local-offer, queuing\ncall-session.js:241 [call] renegotiation requested while state=have-local-offer, queuing\ncall-session.js:241 [call] renegotiation requested while state=have-local-offer, queuing\ncall-session.js:266 [call] ice connection state: disconnected\ncall-session.js:266 [call] ice connection state: failed\n\nthis happens when two people turn their camera on at the same moment. i think its a glare/renegotiation thing but i dont know the right pattern","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"implement perfect negotiation properly in the call session — polite/impolite peer, offer collision handling, and a queue that doesn't grow forever","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"our signalling messages are untyped objects with a `type` string checked in a switch. define the message types properly, same wire format","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"connection quality indicator: bars from the webrtc stats, and a 'poor connection' toast when it drops for 5+ seconds","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the stats polling interval is 100ms which is itself a cpu problem","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"read our stats collection and tell me which of the numbers we show are actually meaningful vs decorative","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"signalling protocol doc — message types, the state machine, and what a client must do on reconnect mid-call","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"plan the call quality analytics — what we log per call, how we detect a bad call after the fact, and the dashboard we'd want","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"post-call stats upload: aggregate the webrtc stats client side and send one summary, no per-second dump","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"call quality dashboard: distribution of mos-ish scores, worst calls list, and a breakdown by region and browser","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the stats polling interval is 100ms which is itself a cpu problem","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"read our stats collection and tell me which of the numbers we show are actually meaningful vs decorative","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"signalling protocol doc — message types, the state machine, and what a client must do on reconnect mid-call","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"plan the call quality analytics — what we log per call, how we detect a bad call after the fact, and the dashboard we'd want","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"post-call stats upload: aggregate the webrtc stats client side and send one summary, no per-second dump","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"call quality dashboard: distribution of mos-ish scores, worst calls list, and a breakdown by region and browser","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"the region field is null for 40% of calls","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"turn server deployment in three regions with credentials that rotate hourly and no long-lived shared secret in the client","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the turn credentials are static and checked into the repo","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"turn server deployment in three regions with credentials that rotate hourly and no long-lived shared secret in the client","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the turn credentials are static and checked into the repo","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"assess whether someone could use our turn servers as an open relay, and what it would cost us","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"ops doc for the turn fleet: capacity per node, how to tell if it's saturated, and the scaling procedure","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"gostaria de um plano para migrar nosso websocket caseiro para Phoenix Channels sem derrubar os clientes atuais","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"pt"} -{"prompt":"ecto migration adding a composite unique index on messages (conversation_id, client_id) to enforce dedupe at the db level","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"our ecto queries preload associations inconsistently, some with joins some with separate queries. standardize, and the returned data must be identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the pool_size in prod config is 10 with 40 concurrent liveviews","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"liveview reconnects wipe the form the user was filling in","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"liveview based admin page for the room list with live updating counts and a kick-participant action","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"explain what happens to a liveview's assigns across a reconnect and which of ours will misbehave","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"ecto migration adding a composite unique index on messages (conversation_id, client_id) to enforce dedupe at the db level","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"our ecto queries preload associations inconsistently, some with joins some with separate queries. standardize, and the returned data must be identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the pool_size in prod config is 10 with 40 concurrent liveviews","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"liveview reconnects wipe the form the user was filling in","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"liveview based admin page for the room list with live updating counts and a kick-participant action","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"explain what happens to a liveview's assigns across a reconnect and which of ours will misbehave","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} {"prompt":"write the elixir side of our contributing guide — the umbrella layout, how to run the tests, and the formatting rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"que sigue","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"es"} -{"prompt":"we've got a browser extension, a vscode extension and a cli that all authenticate slightly differently and share nothing. i want the plan for one auth story across all three — device flow, token storage per platform, and how a user sees their connected tools","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"device authorization flow endpoints — code issuance, polling with the right error codes, and expiry, per the rfc","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"we've got a browser extension, a vscode extension and a cli that all authenticate slightly differently and share nothing. i want the plan for one auth story across all three — device flow, token storage per platform, and how a user sees their connected tools","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"device authorization flow endpoints — code issuance, polling with the right error codes, and expiry, per the rfc","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the device code page: big code, copy button, and clear instructions that don't assume the user knows what a device code is","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"the device code is 4 digits, that's not enough entropy","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"our three clients each implement token refresh with their own retry logic. one shared library per language we support, same refresh timing","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the vscode extension gets logged out whenever the window reloads, but only on windows","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"check how each client stores its token and tell me which one is the weakest","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"docs for the device flow — the endpoints, the polling interval rules, and a worked example for a cli author","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"connected apps page: list of authorized clients with last used, scopes, and a revoke per entry","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the device code is 4 digits, that's not enough entropy","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"our three clients each implement token refresh with their own retry logic. one shared library per language we support, same refresh timing","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the vscode extension gets logged out whenever the window reloads, but only on windows","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"check how each client stores its token and tell me which one is the weakest","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"docs for the device flow — the endpoints, the polling interval rules, and a worked example for a cli author","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"connected apps page: list of authorized clients with last used, scopes, and a revoke per entry","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"revoking a client's access doesn't stop its in-flight refresh token","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"scoped tokens — a token can be limited to read-only or to one project, enforced server side","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the scope list in the consent screen shows internal scope names like 'proj:rw'","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"the scope list in the consent screen shows internal scope names like 'proj:rw'","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"plan the oauth app story for third parties — registration, review, redirect uri rules, and rate limits per app","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"look at our redirect uri validation, i want to know if a wildcard or a fragment could be abused","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"oauth app developer docs: registering, the flows we support, scope reference, and the security requirements we enforce","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"our consent screen is rendered by two different templates depending on the flow and they show different scope lists. one template, same information","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"look at our redirect uri validation, i want to know if a wildcard or a fragment could be abused","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"oauth app developer docs: registering, the flows we support, scope reference, and the security requirements we enforce","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"our consent screen is rendered by two different templates depending on the flow and they show different scope lists. one template, same information","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"vscode extension: a tree view of our resources with lazy children, and inline actions on hover","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the extension activates on startup for everyone, make it activate on our commands only","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"language server for our config format — diagnostics, completion from the schema, and go-to-definition for references","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"completion in the editor is 800ms behind typing on a large file","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain how our language server caches parses and whether an edit invalidates more than it needs to","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the extension activates on startup for everyone, make it activate on our commands only","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"language server for our config format — diagnostics, completion from the schema, and go-to-definition for references","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"completion in the editor is 800ms behind typing on a large file","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain how our language server caches parses and whether an edit invalidates more than it needs to","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"extension readme and marketplace description, with a gif placeholder and the three features people care about","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"plan how we ship the language server to all the editors — lsp, but the packaging and update story per editor","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"plan how we ship the language server to all the editors — lsp, but the packaging and update story per editor","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"our parser is used by the cli, the server and the language server, each with a vendored copy that's drifted. one package, and validate that all three still accept the same files","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the last one","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"i need the plan for our public roadmap and changelog infrastructure. sounds trivial but: it needs to pull from our issue tracker, have a public voting thing, and the changelog needs to be in the app as well as on the site. and marketing wants to edit copy without a deploy","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"i need the plan for our public roadmap and changelog infrastructure. sounds trivial but: it needs to pull from our issue tracker, have a public voting thing, and the changelog needs to be in the app as well as on the site. and marketing wants to edit copy without a deploy","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"changelog service backed by markdown in a repo, with a build step producing json the app consumes, and per-entry audience tags","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"in-app changelog panel with an unread indicator, and it should only count entries relevant to the user's plan","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the unread dot never clears","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the unread dot never clears","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"write the last three months of changelog entries from the merged PRs, split by audience","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"public roadmap page: three columns, vote counts, and a filter by area. votes need to be per-account not per-visit","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"vote counts jump around because we're counting per visit not per account","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"our markdown rendering happens in four places with different plugin sets, so the same entry looks different in each. one renderer","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"review the public roadmap for anything that leaks internal customer names from the issue titles","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"feedback widget: a small form, screenshot attach, and it should post to our tracker with the user's context attached","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the widget covers the chat launcher on mobile","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"plan how we triage inbound feedback at volume without it rotting in a queue","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"public roadmap page: three columns, vote counts, and a filter by area. votes need to be per-account not per-visit","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"vote counts jump around because we're counting per visit not per account","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"our markdown rendering happens in four places with different plugin sets, so the same entry looks different in each. one renderer","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"review the public roadmap for anything that leaks internal customer names from the issue titles","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"feedback widget: a small form, screenshot attach, and it should post to our tracker with the user's context attached","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"the widget covers the chat launcher on mobile","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"plan how we triage inbound feedback at volume without it rotting in a queue","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"feedback submissions from the widget lose the screenshot about a third of the time","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"explain what user context we attach to a feedback submission — i want to be sure we're not sending anything we shouldn't","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"explain what user context we attach to a feedback submission — i want to be sure we're not sending anything we shouldn't","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"privacy note for the feedback widget, in plain language, explaining what we collect when you submit","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"screenshot capture in the widget via the display capture api with a redaction tool for sensitive fields","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"moving on","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"would you mind putting together the plan for our status page and incident comms? we currently post in a slack channel and email people manually. i want automated component status from our monitoring, subscriber notifications, and a template-driven update flow so an on-call engineer isn't writing prose at 3am","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"screenshot capture in the widget via the display capture api with a redaction tool for sensitive fields","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"would you mind putting together the plan for our status page and incident comms? we currently post in a slack channel and email people manually. i want automated component status from our monitoring, subscriber notifications, and a template-driven update flow so an on-call engineer isn't writing prose at 3am","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"component status derived from our slo burn rates, with a manual override that an engineer can set and that expires","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"public status page: components with their state, the 90 day history strip, and active incidents at the top","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the status page is served from the same cluster it reports on","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"subscriber notifications by email and webhook, per component, with a digest option and a confirmed opt-in","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"subscribers get notified for components they didn't subscribe to","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"public status page: components with their state, the 90 day history strip, and active incidents at the top","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the status page is served from the same cluster it reports on","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"subscriber notifications by email and webhook, per component, with a digest option and a confirmed opt-in","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"subscribers get notified for components they didn't subscribe to","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"our notification sending for status updates duplicates the main email service's logic including its suppression list handling. use the shared service","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"incident update templates for the four phases, with the placeholders an engineer fills, plus guidance on tone","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"tell me what our status page would show right now if the database were down, based on the code not the intent","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"tell me what our status page would show right now if the database were down, based on the code not the intent","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} {"prompt":"incident management ui for the on-call: create, pick components, post an update from a template, and resolve","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the resolve button doesn't clear the component states","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"plan the uptime reporting we'd publish — how we compute it, what counts as downtime, and how it maps to the sla credits","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the monthly uptime number disagrees with our internal slo dashboard by half a percent","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"explain how our uptime calculation treats a partial outage affecting 5% of customers","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"sla document with the uptime commitment, the exclusions, how credits are calculated and claimed","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the resolve button doesn't clear the component states","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"plan the uptime reporting we'd publish — how we compute it, what counts as downtime, and how it maps to the sla credits","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the monthly uptime number disagrees with our internal slo dashboard by half a percent","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain how our uptime calculation treats a partial outage affecting 5% of customers","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"sla document with the uptime commitment, the exclusions, how credits are calculated and claimed","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"uptime computation job producing monthly numbers per component, from the historical status records","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"design the incident automation then implement the slo burn rate watcher","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"check the status page code and tidy up the duplication you find","purpose":"review","secondary":"refactor","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} -{"prompt":"eh, next","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"check the status page code and tidy up the duplication you find","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"here's what support pasted into the channel, i think its a small config thing but i want to be sure:\n\n> customer (Mercator Labs, enterprise) says the ip allowlist isn't working. they added\n> 203.0.113.0/24 and their requests from 203.0.113.44 are still rejected with\n> {\"error\":\"ip_not_allowed\"}. they've confirmed the source ip with our /whoami endpoint\n> which returns 203.0.113.44.\n>\n> i checked their org settings and the allowlist is saved correctly. tried it myself with\n> a proxy from a listed ip and got the same rejection.\n>\n> they're threatening to escalate, they've had this open 4 days","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} {"prompt":"ip allowlist evaluation using the correct client ip from the proxy chain, with the trusted proxy list configured explicitly","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"we read the client ip from three different places in the code, one of which is the raw remote addr behind the lb. one helper","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"we read the client ip from three different places in the code, one of which is the raw remote addr behind the lb. one helper","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"allowlist settings ui showing the user's current ip with an 'add this' button, and a warning if they're about to lock themselves out","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the allowlist input accepts a bare ip but not a /32","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"review the allowlist enforcement — does it cover the api, the ui, the webhooks-in, and the sso callback, or just the api","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"admin docs for ip allowlisting: what it covers, what it doesn't, ipv6, and the recovery path when you lock yourself out","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"plan the network security features enterprise keeps asking for — ip allowlist, private connectivity, and egress from a fixed ip","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"fixed egress ips for our outbound webhooks and api calls, documented and stable, per region","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"our egress ip list in the docs is out of date and customers' firewalls are blocking us","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"ipv6 addresses in the allowlist match nothing, silently","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"audit log entries for allowlist changes, and a notification to the other admins when one changes","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the allowlist input accepts a bare ip but not a /32","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"review the allowlist enforcement — does it cover the api, the ui, the webhooks-in, and the sso callback, or just the api","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"admin docs for ip allowlisting: what it covers, what it doesn't, ipv6, and the recovery path when you lock yourself out","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"plan the network security features enterprise keeps asking for — ip allowlist, private connectivity, and egress from a fixed ip","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"fixed egress ips for our outbound webhooks and api calls, documented and stable, per region","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"our egress ip list in the docs is out of date and customers' firewalls are blocking us","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"ipv6 addresses in the allowlist match nothing, silently","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"audit log entries for allowlist changes, and a notification to the other admins when one changes","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"settings page section for network security with the three features grouped and their enterprise-plan gating clear","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"explain how the plan gating for enterprise features is enforced — ui only or server side too","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"security whitepaper section on network controls, aimed at a customer's security reviewer","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain how the plan gating for enterprise features is enforced — ui only or server side too","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"security whitepaper section on network controls, aimed at a customer's security reviewer","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"our plan-gating checks are string comparisons against plan names in 60 places. move to a capability check, same gating for every existing plan","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"ok whats left then","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"- 3d finite volume solver, structured grid\n- currently openmp only, 40 min per run on 32 cores\n- want cuda for the flux kernel first, then the pressure solve\n- must reproduce the existing results bitwise-ish (within 1e-10)\n- and we need it to still build without cuda for the laptops\n\nplan this out before any kernels get written","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"cuda kernel for the flux computation, coalesced access on the halo layout we have, and a host fallback that shares the same math","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"the cfl number is hardcoded 0.9 in three files","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"our array indexing is done with raw macros that differ between the solver and the io code. one indexing abstraction, identical numerical output","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"results diverge from the reference after 2000 timesteps but only with -ffast-math on, which i know is the answer but i need to know WHERE","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"walk me through the halo exchange, i want to know if the mpi calls are actually overlapping with compute or just pretending to","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"numerical methods doc for the solver — the discretization, boundary conditions, and the stability constraints, in enough detail that a new phd student can follow","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"cuda kernel for the flux computation, coalesced access on the halo layout we have, and a host fallback that shares the same math","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the cfl number is hardcoded 0.9 in three files","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"our array indexing is done with raw macros that differ between the solver and the io code. one indexing abstraction, identical numerical output","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"results diverge from the reference after 2000 timesteps but only with -ffast-math on, which i know is the answer but i need to know WHERE","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"walk me through the halo exchange, i want to know if the mpi calls are actually overlapping with compute or just pretending to","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"numerical methods doc for the solver — the discretization, boundary conditions, and the stability constraints, in enough detail that a new phd student can follow","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"checkpoint/restart with hdf5, one file per run not per rank, and restart must be bit-identical to a continuous run","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"visualization frontend for the solver output: slice viewer, colormap picker, and a time slider that streams frames","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the colormap is jet, please anything but jet","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"restart from a checkpoint gives slightly different results than a continuous run, about 1e-7 after 100 steps","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"the colormap is jet, please anything but jet","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"restart from a checkpoint gives slightly different results than a continuous run, about 1e-7 after 100 steps","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"map out the plan for running our solver on the cluster's slurm queue — job scripts, sizing, and how we collect results without filling the home directory","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"shopify app: webhook handler for order/create that syncs into our system, with hmac verification and the 5 second response budget respected","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"our app embeds an admin ui in the shopify iframe and the modal breaks out of it on mobile","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the api version in our client is 2024-01, move to the current one","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"we hit the shopify rate limit during a sync and just fail. plan the proper approach — bulk operations, the leaky bucket, and where we queue","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"webhooks arrive out of order and we occasionally persist an older order state over a newer one","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"explain how our app handles a merchant uninstalling and reinstalling — what state survives and what shouldn't","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"shopify app: webhook handler for order/create that syncs into our system, with hmac verification and the 5 second response budget respected","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"our app embeds an admin ui in the shopify iframe and the modal breaks out of it on mobile","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"the api version in our client is 2024-01, move to the current one","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"we hit the shopify rate limit during a sync and just fail. plan the proper approach — bulk operations, the leaky bucket, and where we queue","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"webhooks arrive out of order and we occasionally persist an older order state over a newer one","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain how our app handles a merchant uninstalling and reinstalling — what state survives and what shouldn't","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"app listing copy for the shopify store plus the setup instructions merchants see after install","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"our three integrations (shopify, woo, bigcommerce) each have their own order normalization with different field mappings. one canonical order model, and prove the existing orders map identically","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"wpf: the settings dialog needs to be resizable with the tree on the left keeping its width, and it must remember size and position","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the app doesn't respect per-monitor dpi so it's blurry when you drag it to the second screen","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"installer doesn't create a start menu shortcut","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"check the .net app for anywhere we're blocking the ui thread on io, i suspect the file dialogs and the update check","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"back at it","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"the app doesn't respect per-monitor dpi so it's blurry when you drag it to the second screen","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"installer doesn't create a start menu shortcut","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"check the .net app for anywhere we're blocking the ui thread on io, i suspect the file dialogs and the update check","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} {"prompt":"…so the licensing thing. we sell perpetual licenses with a year of updates, plus site licenses, plus academic. currently it's a signed file the app checks at startup and it's been cracked twice. i want the design for something better that still works fully offline for our air-gapped customers. and the migration for the 4000 existing licenses","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"license verification with an offline-capable signed token, machine binding that survives a hardware upgrade, and a grace period on clock skew","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"license status pane: what edition, seats used, expiry, and a manual activation flow with a copy-paste request code","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"expired licenses show 'Invalid license' rather than saying it expired and when","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"the license check happens in 12 places with slightly different rules, one of which just returns true in a debug branch. one check","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"some customers' licenses stop validating after a windows update, specifically after a motherboard driver change i think","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"expired licenses show 'Invalid license' rather than saying it expired and when","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the license check happens in 12 places with slightly different rules, one of which just returns true in a debug branch. one check","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"some customers' licenses stop validating after a windows update, specifically after a motherboard driver change i think","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"assess our license enforcement honestly — how much effort is it to bypass, and which of our protections are theatre","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"licensing docs for customers: activation, moving to a new machine, offline activation, and the site license rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"licensing docs for customers: activation, moving to a new machine, offline activation, and the site license rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"license server endpoints for activation, deactivation and seat counting, with an audit of every activation","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"admin view for a customer's licenses: seats, activations with machine names, and a force-deactivate","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the seat count includes deactivated machines","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"admin view for a customer's licenses: seats, activations with machine names, and a force-deactivate","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the seat count includes deactivated machines","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} {"prompt":"plan the subscription option alongside perpetual, without turning the licensing code into a maze","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"activations occasionally count double, and the customer runs out of seats","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"explain what happens on our side if a customer's clock is set two years forward","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"internal doc on the license token format and the signing key handling, for the two of us who maintain it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"auto-update for the windows app with a delta download, signature verification, and a rollback if the new version crashes on launch","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"activations occasionally count double, and the customer runs out of seats","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain what happens on our side if a customer's clock is set two years forward","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"internal doc on the license token format and the signing key handling, for the two of us who maintain it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"auto-update for the windows app with a delta download, signature verification, and a rollback if the new version crashes on launch","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"update prompt that doesn't interrupt a long-running computation, and offers 'install on exit'","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the updater runs as admin and writes to a user-writable temp path first","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the updater runs as admin and writes to a user-writable temp path first","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"plan the cuda port and then write the first kernel","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"figure out why restart isn't bit-identical then document the numerics caveat","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"same but for windows","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"pasted the compiler output, this is after i tried to templatize the field class:\n\nsrc/solver/field.hpp:88:34: error: no matching function for call to 'apply_stencil'\n 88 | return apply_stencil(f, s, halo_);\n | ^~~~~~~~~~~~~\nsrc/solver/stencil.hpp:41:5: note: candidate template ignored: deduced conflicting types for parameter 'T' ('double' vs 'float')\n 41 | T apply_stencil(const Field& f, const Stencil& s, int halo);\n | ^\nsrc/solver/stencil.hpp:52:5: note: candidate function template not viable: requires 4 arguments, but 3 were provided\n\nsrc/solver/field.hpp:120:20: error: 'value_type' is not a member of 'Field'\n 120 | using scalar = Field::value_type;\n | ^\n\n2 errors generated.\n\nim clearly holding templates wrong. i want mixed precision to work — float for the transport, double for the pressure solve","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"make the field and stencil types precision-generic properly, and confirm the double-precision path produces identical results to today","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"mixed precision transport step: float storage, double accumulation, with a compile-time switch to go all-double","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"the -O3 build uses -march=native which breaks on the cluster's older nodes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"figure out the plan for a regression test suite for the solver — reference outputs, tolerances per case, and runtime under 10 minutes","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"read the pressure solver's convergence criterion and tell me whether it's absolute or relative, because the comment and the code disagree","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"write the paper's methods section describing our numerical scheme and the verification cases","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"job submission gui for the cluster: pick a case, set resources, submit, and watch the log tail","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"profiling harness that runs the standard cases and reports time per kernel, comparable across commits","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"runtime regressed 20% between two commits that only touched io code","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the timing output prints in scientific notation with 12 digits","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"explain our memory layout for the field arrays and whether it's actually cache friendly for the stencil we apply","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"performance notes doc: the layout, the vectorization we rely on, and the compiler flags that matter, so nobody undoes it accidentally","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"our io writes one file per rank per timestep, which is 40k files per run. move to collective io, same data recoverable","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"figure out why restart isn't bit-identical then document the numerics caveat","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"pasted the compiler output, this is after i tried to templatize the field class:\n\nsrc/solver/field.hpp:88:34: error: no matching function for call to 'apply_stencil'\n 88 | return apply_stencil(f, s, halo_);\n | ^~~~~~~~~~~~~\nsrc/solver/stencil.hpp:41:5: note: candidate template ignored: deduced conflicting types for parameter 'T' ('double' vs 'float')\n 41 | T apply_stencil(const Field& f, const Stencil& s, int halo);\n | ^\nsrc/solver/stencil.hpp:52:5: note: candidate function template not viable: requires 4 arguments, but 3 were provided\n\nsrc/solver/field.hpp:120:20: error: 'value_type' is not a member of 'Field'\n 120 | using scalar = Field::value_type;\n | ^\n\n2 errors generated.\n\nim clearly holding templates wrong. i want mixed precision to work — float for the transport, double for the pressure solve","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"make the field and stencil types precision-generic properly, and confirm the double-precision path produces identical results to today","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"mixed precision transport step: float storage, double accumulation, with a compile-time switch to go all-double","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the -O3 build uses -march=native which breaks on the cluster's older nodes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"figure out the plan for a regression test suite for the solver — reference outputs, tolerances per case, and runtime under 10 minutes","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"read the pressure solver's convergence criterion and tell me whether it's absolute or relative, because the comment and the code disagree","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"write the paper's methods section describing our numerical scheme and the verification cases","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"job submission gui for the cluster: pick a case, set resources, submit, and watch the log tail","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"profiling harness that runs the standard cases and reports time per kernel, comparable across commits","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"runtime regressed 20% between two commits that only touched io code","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the timing output prints in scientific notation with 12 digits","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"explain our memory layout for the field arrays and whether it's actually cache friendly for the stencil we apply","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"performance notes doc: the layout, the vectorization we rely on, and the compiler flags that matter, so nobody undoes it accidentally","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"our io writes one file per rank per timestep, which is 40k files per run. move to collective io, same data recoverable","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} {"prompt":"plan how we make the solver installable for external users — cmake, dependencies, and a conda or spack package","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"python bindings for the solver so people can drive it from a notebook, with numpy arrays sharing memory not copying","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the python module segfaults when the array is not c-contiguous","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"tutorial notebook for the python bindings: load a case, run 100 steps, plot a slice","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"sigue nomás","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"es"} +{"prompt":"the python module segfaults when the array is not c-contiguous","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"tutorial notebook for the python bindings: load a case, run 100 steps, plot a slice","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} {"prompt":"we're building the merchant-facing analytics for our commerce app and i want the plan first. metrics: revenue, aov, conversion by traffic source, cohort retention. data comes from webhooks with gaps, merchants have up to 5 years of history, and they expect it to match shopify's own numbers exactly (they won't, and i need a story for that)","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"backfill job that pulls a merchant's historical orders via the bulk api, resumable, and reconciles against the webhook-derived data","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"analytics dashboard for merchants: four kpi tiles with sparklines, a revenue chart, and a table of top products, all responsive","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the aov tile divides by total orders including cancelled ones","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"we define 'revenue' in the dashboard sql, the export, and the email digest with three different treatments of refunds and shipping. one definition, documented, and say which numbers move","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"our revenue number is 3-8% below the merchant's shopify report and the gap varies by merchant","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"read the cohort query and tell me whether a customer who orders twice in one month counts once or twice","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"metric definitions page for merchants — what each number includes and excludes, and why it may differ from their platform's report","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"backfill job that pulls a merchant's historical orders via the bulk api, resumable, and reconciles against the webhook-derived data","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"analytics dashboard for merchants: four kpi tiles with sparklines, a revenue chart, and a table of top products, all responsive","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the aov tile divides by total orders including cancelled ones","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"we define 'revenue' in the dashboard sql, the export, and the email digest with three different treatments of refunds and shipping. one definition, documented, and say which numbers move","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"our revenue number is 3-8% below the merchant's shopify report and the gap varies by merchant","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"read the cohort query and tell me whether a customer who orders twice in one month counts once or twice","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"metric definitions page for merchants — what each number includes and excludes, and why it may differ from their platform's report","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"weekly digest email with the merchant's numbers, a week-over-week comparison, and one insight worth reading","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the digest sends even when a merchant has zero orders, which reads as mockery","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"the digest sends even when a merchant has zero orders, which reads as mockery","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"date range picker with presets, comparison mode, and it should say what timezone it's using because merchants ask constantly","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"numbers change depending on whether you load the dashboard before or after midnight in the merchant's timezone, which is expected, but the labels don't say so","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"numbers change depending on whether you load the dashboard before or after midnight in the merchant's timezone, which is expected, but the labels don't say so","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"plan the multi-store support — one merchant with 4 storefronts wanting combined and per-store views","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain how our timezone handling works for aggregation — is a 'day' the store's day or utc","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"help doc about timezones in reporting, because this generates a support ticket a week","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"explain how our timezone handling works for aggregation — is a 'day' the store's day or utc","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"help doc about timezones in reporting, because this generates a support ticket a week","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"aggregation in the store's timezone with a per-store setting, and the historical aggregates rebuilt when a store changes theirs","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"product attribution: which product drove a first order, tracked from the landing page through checkout","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"attribution shows 'direct' for 60% of orders which can't be right","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the utm parsing drops parameters after the first ampersand","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"attribution breakdown view: sources as a bar chart, with a note about the attribution window and its limits","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"our tracking script and the server-side attribution use different session definitions. align them, and quantify how attribution shifts","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"check whether our tracking script sets any cookie that would need consent in the eu","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"attribution methodology doc, honest about the limits, for merchants who ask why it differs from google's numbers","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"plan the consent-aware tracking so we degrade gracefully without consent instead of just not working","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"ye go on","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"product attribution: which product drove a first order, tracked from the landing page through checkout","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"attribution shows 'direct' for 60% of orders which can't be right","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the utm parsing drops parameters after the first ampersand","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"attribution breakdown view: sources as a bar chart, with a note about the attribution window and its limits","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"our tracking script and the server-side attribution use different session definitions. align them, and quantify how attribution shifts","purpose":"backendImpl","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"check whether our tracking script sets any cookie that would need consent in the eu","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"attribution methodology doc, honest about the limits, for merchants who ask why it differs from google's numbers","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"plan the consent-aware tracking so we degrade gracefully without consent instead of just not working","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"so the .net desktop app has a plugin system that loads dlls from a folder with full trust, which was fine when we had three internal plugins and is not fine now that customers write their own. i want the plan for isolating them — appdomains are gone, so assemblyloadcontext, or out-of-process, or wasm. include what breaks for existing plugins","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"plugin host using AssemblyLoadContext with unload support, a versioned interface assembly, and a clean failure when a plugin targets an old contract","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"plugin manager window: installed list, enable/disable, version and contract compatibility shown, and a load-error detail expander","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"a plugin that throws in its constructor takes the whole app down","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the plugin folder is under Program Files so plugins need admin to install","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"our plugin interface has grown 40 members with obsolete ones still there. define a v2 contract, keep v1 working through an adapter","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"review what a malicious plugin can do to the host app and the user's machine as things stand","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"plugin developer guide for the v2 contract: the interfaces, the lifecycle, threading rules, and how to debug against a local build","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"unload plugins cleanly so a developer can rebuild and reload without restarting the app","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"memory grows every time a plugin is reloaded, so something's keeping the context alive","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the reload button is enabled for plugins that don't support unloading","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"figure out the plan for signing and distributing third party plugins, including a review step we can actually staff","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"explain how our app decides a plugin is trusted today, and whether the signature is verified or just present","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"plugin signing policy documentation for developers and for our support team","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"a plugin that throws in its constructor takes the whole app down","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the plugin folder is under Program Files so plugins need admin to install","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"our plugin interface has grown 40 members with obsolete ones still there. define a v2 contract, keep v1 working through an adapter","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"review what a malicious plugin can do to the host app and the user's machine as things stand","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"plugin developer guide for the v2 contract: the interfaces, the lifecycle, threading rules, and how to debug against a local build","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"unload plugins cleanly so a developer can rebuild and reload without restarting the app","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"memory grows every time a plugin is reloaded, so something's keeping the context alive","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the reload button is enabled for plugins that don't support unloading","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"figure out the plan for signing and distributing third party plugins, including a review step we can actually staff","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"explain how our app decides a plugin is trusted today, and whether the signature is verified or just present","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"plugin signing policy documentation for developers and for our support team","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"our wpf views bind directly to model objects in half the app and to viewmodels in the other half. get everything behind viewmodels, no visual or behavioral change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"settings persistence with a schema version and a migration path, replacing the current unversioned xml blob","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"settings persistence with a schema version and a migration path, replacing the current unversioned xml blob","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"settings get reset to defaults for users upgrading from 4.x","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"toolbar icons are 16px bitmaps and look terrible at 200% scaling, move to vectors","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"toolbar icons are 16px bitmaps and look terrible at 200% scaling, move to vectors","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"keyboard shortcuts don't work when focus is in the document canvas","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"release checklist for the desktop app: build, sign, notarize the mac build, smoke test matrix, and the update feed publish","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"release checklist for the desktop app: build, sign, notarize the mac build, smoke test matrix, and the update feed publish","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"plan the plugin isolation then implement the load context","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"audit the plugin api and clean up the obviously dead members","purpose":"review","secondary":"refactor","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"next please","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"here's the thing that came out of the customer call, pasting my notes:\n\n- they run our desktop app on 400 machines in a locked-down environment\n- no internet at all, updates come via a network share\n- they want to preconfigure settings centrally (registry or a config file, they don't care)\n- they need our app to not phone home AT ALL, including the crash reporter and the font loading\n- and they want an audit log of what users did, written to a share\n- oh and their IT wants an MSI not our current installer\n\nturn this into a plan with what's feasible this quarter","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"offline mode switch that disables every outbound network call including telemetry and the update check, verifiable with a network monitor","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"offline mode switch that disables every outbound network call including telemetry and the update check, verifiable with a network monitor","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"msi packaging with per-machine install, admin-configurable defaults, and a silent install command line","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the crash reporter posts before the user consents","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"find every outbound network call in the app and list them with what triggers each","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"enterprise deployment guide: msi options, the policy settings, the offline update procedure, and the audit log format","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"admin policy settings read from the registry with the app's ui showing which settings are locked by policy","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the crash reporter posts before the user consents","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"find every outbound network call in the app and list them with what triggers each","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"enterprise deployment guide: msi options, the policy settings, the offline update procedure, and the audit log format","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"admin policy settings read from the registry with the app's ui showing which settings are locked by policy","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"our network calls are made from 20 places with their own HttpClient instances, so there's no single place to gate them. one client, same requests","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the app hangs for 20 seconds on launch in an air-gapped environment, presumably a network timeout somewhere","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"user activity audit log written to a configurable path, append only, with a documented format","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the audit log path setting accepts a unc path but the writer fails silently on one","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"offline update via a network share: the app checks a manifest on the share, verifies signatures, and installs on next launch","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the update manifest schema isn't documented anywhere and their IT is asking","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"plan how we test the air-gapped configuration in CI, because we will break it otherwise","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"check whether the locked-by-policy settings can be changed by editing the config file directly","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"font loading falls back to a web font when the local one is missing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the app hangs for 20 seconds on launch in an air-gapped environment, presumably a network timeout somewhere","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"user activity audit log written to a configurable path, append only, with a documented format","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"the audit log path setting accepts a unc path but the writer fails silently on one","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"offline update via a network share: the app checks a manifest on the share, verifies signatures, and installs on next launch","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the update manifest schema isn't documented anywhere and their IT is asking","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"plan how we test the air-gapped configuration in CI, because we will break it otherwise","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"check whether the locked-by-policy settings can be changed by editing the config file directly","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"font loading falls back to a web font when the local one is missing","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"settings ui showing policy-locked fields as disabled with a tooltip saying who set it","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"figure out the offline story properly then build the manifest checker","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"and then that other thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"ros2: the navigation node drops to 2hz when the costmap updates and the robot overshoots. i don't know if it's the callback group setup or the costmap itself","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"ros2: the navigation node drops to 2hz when the costmap updates and the robot overshoots. i don't know if it's the callback group setup or the costmap itself","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"- new lifecycle node for the gripper controller\n- action server for grasp with feedback\n- must preempt cleanly on cancel\n- publish joint states at 100hz\n- and it needs to work with the sim and the real arm behind the same interface\n\nbuild it","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"teleop web ui: video feed, a virtual joystick, e-stop that's impossible to miss, and a latency readout","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"teleop web ui: video feed, a virtual joystick, e-stop that's impossible to miss, and a latency readout","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"the max velocity param is 2.0 m/s, safety wants 1.2","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"our tf frames are published from three nodes with overlapping responsibility and one of them is stale. consolidate the publishing, same transforms available","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"our tf frames are published from three nodes with overlapping responsibility and one of them is stale. consolidate the publishing, same transforms available","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"please plan the migration from ros1 to ros2 for the whole stack. 40 nodes, three of which are vendor binaries we can't rebuild","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"could you explain how our qos settings interact with the wifi link — i want to know which topics will drop messages when the link degrades","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"write the interface documentation for our robot's topics, services and actions — types, rates, and the frames each is expressed in","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"could you explain how our qos settings interact with the wifi link — i want to know which topics will drop messages when the link degrades","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"write the interface documentation for our robot's topics, services and actions — types, rates, and the frames each is expressed in","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"bag recording that captures only the topics we need for incident replay, rotating by size, with a trigger to keep the last 60s on an e-stop","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the e-stop topic is best-effort qos","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"robot fleet view: each robot as a card with battery, state, current task, and a click into its live telemetry","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"one robot in the fleet reports its pose in the wrong frame after a reboot, until you restart the localization node","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the e-stop topic is best-effort qos","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"robot fleet view: each robot as a card with battery, state, current task, and a click into its live telemetry","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"one robot in the fleet reports its pose in the wrong frame after a reboot, until you restart the localization node","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"hl7 v2 to fhir mapping service — ADT messages in, Patient and Encounter resources out, with the unmapped segments preserved for audit","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"would you plan the integration approach for the three hospital systems we're onboarding? two speak hl7 v2 over mllp, one has a fhir api that's mostly a lie. i need sequencing and where we absorb the mess","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"the mllp listener has no idle timeout so dead connections accumulate","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"our segment parsing has per-hospital special cases scattered through the parser as if-statements on the sending facility. move to per-source configuration, identical output for each existing source","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"messages from one hospital fail validation about 2% of the time with a date parse error, and the dates look fine to me","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"review our phi handling in the message pipeline — where it's logged, where it's cached, and whether anything unencrypted touches disk","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"integration guide for a new hospital's IT team: the connection details, the message types we accept, and the acknowledgement semantics","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"message viewer for our support team: search by patient id, the raw message, the parsed view, and the resulting resources","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"patient ids show in the browser tab title","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"route optimization for the delivery planner — 200 stops, time windows, vehicle capacities, and it needs an answer in under 30 seconds","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"route map view: stops numbered along the path, drag to reorder with the eta updating, and a warning badge on windows we'd miss","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the eta doesn't account for service time at each stop","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"ok next","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"from the ticket, this is affecting a paying customer daily:\n\nSUMMARY: Routes generated at 05:00 differ from routes generated at 05:05 for identical input\nIMPACT: Dispatchers regenerate a route and get a completely different order, they've lost\n trust in the planner.\nDETAIL: Same 84 stops, same vehicles, same constraints. Total distance differs by up to 9%.\n Both solutions are valid. We use a metaheuristic with a 20s time limit.\nDISPATCHER COMMENT: \"if I click the button twice I get two different answers, which one is right?\"\n\ni know why this happens technically. what i don't know is what we should DO about it","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"make route generation deterministic for identical input — fixed seed, stable tie-breaking, and a cached solution keyed on the input hash","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the random seed comes from the clock","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"our distance matrix is computed by three callers with different rounding and one that uses haversine instead of road distance. one source","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"read the solver's constraint handling and tell me whether a hard time window can be violated in the returned solution","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"documentation for dispatchers explaining how routes are built, what the planner optimizes for, and why the answer can vary","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"route comparison view so a dispatcher can see the old and new route side by side with the deltas","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the mllp listener has no idle timeout so dead connections accumulate","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"our segment parsing has per-hospital special cases scattered through the parser as if-statements on the sending facility. move to per-source configuration, identical output for each existing source","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"messages from one hospital fail validation about 2% of the time with a date parse error, and the dates look fine to me","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"review our phi handling in the message pipeline — where it's logged, where it's cached, and whether anything unencrypted touches disk","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"integration guide for a new hospital's IT team: the connection details, the message types we accept, and the acknowledgement semantics","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"message viewer for our support team: search by patient id, the raw message, the parsed view, and the resulting resources","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"patient ids show in the browser tab title","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"route optimization for the delivery planner — 200 stops, time windows, vehicle capacities, and it needs an answer in under 30 seconds","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"route map view: stops numbered along the path, drag to reorder with the eta updating, and a warning badge on windows we'd miss","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the eta doesn't account for service time at each stop","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"from the ticket, this is affecting a paying customer daily:\n\nSUMMARY: Routes generated at 05:00 differ from routes generated at 05:05 for identical input\nIMPACT: Dispatchers regenerate a route and get a completely different order, they've lost\n trust in the planner.\nDETAIL: Same 84 stops, same vehicles, same constraints. Total distance differs by up to 9%.\n Both solutions are valid. We use a metaheuristic with a 20s time limit.\nDISPATCHER COMMENT: \"if I click the button twice I get two different answers, which one is right?\"\n\ni know why this happens technically. what i don't know is what we should DO about it","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"make route generation deterministic for identical input — fixed seed, stable tie-breaking, and a cached solution keyed on the input hash","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the random seed comes from the clock","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"our distance matrix is computed by three callers with different rounding and one that uses haversine instead of road distance. one source","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"read the solver's constraint handling and tell me whether a hard time window can be violated in the returned solution","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"documentation for dispatchers explaining how routes are built, what the planner optimizes for, and why the answer can vary","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"route comparison view so a dispatcher can see the old and new route side by side with the deltas","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"routes with a single stop take the full 20 second time limit","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"plan how we handle mid-day replanning when a driver is late or a stop is cancelled, without reshuffling the whole day","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"plan how we handle mid-day replanning when a driver is late or a stop is cancelled, without reshuffling the whole day","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"driver app: today's route as a list, next stop prominent, arrive/complete/failed actions, and it works offline in a basement","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the complete button submits twice on a slow connection and marks two stops done","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"proof of delivery: photo, signature capture, and a note, queued offline and uploaded when there's signal","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the signature canvas doesn't scale on high dpi phones so the signature is tiny","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"explain how the driver app's offline queue orders its uploads, and what happens if a stop is completed then edited while offline","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the complete button submits twice on a slow connection and marks two stops done","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"proof of delivery: photo, signature capture, and a note, queued offline and uploaded when there's signal","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"the signature canvas doesn't scale on high dpi phones so the signature is tiny","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"explain how the driver app's offline queue orders its uploads, and what happens if a stop is completed then edited while offline","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"driver-facing help screens: what to do when a customer isn't home, how to report an issue, and how offline mode behaves","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"live tracking page for the end customer with an eta that updates, and it should not reveal the driver's whole route","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the tracking link works forever, it should expire after delivery + a day","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"eta updates lag reality by 10 minutes because we only recompute on stop completion","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the tracking link works forever, it should expire after delivery + a day","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"eta updates lag reality by 10 minutes because we only recompute on stop completion","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"plan the fhir server work then build the Patient resource endpoints","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"work out why the hl7 dates fail parsing then update the integration doc with what we found","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"continue where we stopped","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"work out why the hl7 dates fail parsing then update the integration doc with what we found","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} {"prompt":"i'd like the plan for our postgres extension. it adds a custom index type for our geometry-ish data and currently only builds against pg15. we need 15/16/17 support, a proper pgxs build, and an upgrade path for existing installs. also nobody but me understands the code, which is its own problem","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"extension build for pg15 through 17 with the version-conditional code isolated in one header rather than sprinkled through","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"the extension's control file has default_version 1.0 while the sql files go to 1.4","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"our #if PG_VERSION_NUM blocks appear in 30 files. collapse behind compat macros in one place, identical behavior per version","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the extension crashes the backend on pg17 during a parallel scan, works fine serially","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"would you review our memory context usage — i'm not confident we're allocating in the right context in the scan callbacks","purpose":"review","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"extension documentation: installation, the operators and functions it provides, the index type's semantics, and the version compatibility table","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"upgrade scripts for 1.0 through 1.4 so existing installs can ALTER EXTENSION UPDATE without a dump/restore","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"regression tests using pg_regress covering each version, run in CI against all three","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the test expected output has hardcoded oids","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"explain how our index's cost estimation function works and whether the planner is likely to pick us when it should","purpose":"review","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"plan how we get this extension into the pgxn/apt/yum ecosystems so customers stop building from source","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"next.js marketing site: programmatic landing pages per use case from a content collection, with proper canonical tags and sitemaps","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"our blog pages have no structured data and the previews look bad when shared","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"extension build for pg15 through 17 with the version-conditional code isolated in one header rather than sprinkled through","purpose":"backendImpl","secondary":"refactor","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"the extension's control file has default_version 1.0 while the sql files go to 1.4","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"our #if PG_VERSION_NUM blocks appear in 30 files. collapse behind compat macros in one place, identical behavior per version","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the extension crashes the backend on pg17 during a parallel scan, works fine serially","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"would you review our memory context usage — i'm not confident we're allocating in the right context in the scan callbacks","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"extension documentation: installation, the operators and functions it provides, the index type's semantics, and the version compatibility table","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"upgrade scripts for 1.0 through 1.4 so existing installs can ALTER EXTENSION UPDATE without a dump/restore","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"regression tests using pg_regress covering each version, run in CI against all three","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the test expected output has hardcoded oids","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"explain how our index's cost estimation function works and whether the planner is likely to pick us when it should","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"plan how we get this extension into the pgxn/apt/yum ecosystems so customers stop building from source","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"next.js marketing site: programmatic landing pages per use case from a content collection, with proper canonical tags and sitemaps","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"our blog pages have no structured data and the previews look bad when shared","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} {"prompt":"the robots.txt disallows everything, has done since the staging config leaked into prod","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"organic traffic dropped 40% three weeks ago, no algorithm update i can find, and search console shows pages 'crawled but not indexed'","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"organic traffic dropped 40% three weeks ago, no algorithm update i can find, and search console shows pages 'crawled but not indexed'","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"tell me which of our marketing pages are client-rendered and therefore probably invisible to crawlers","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"write the landing page copy for the enterprise use case — headline, three benefit sections, and the proof points","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"sitemap generation from the routes and content at build time, split into index + child sitemaps over 10k urls","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"our page metadata is defined three ways — a config file, a component, and inline in some pages. one approach, same output per page","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"sitemap generation from the routes and content at build time, split into index + child sitemaps over 10k urls","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"our page metadata is defined three ways — a config file, a component, and inline in some pages. one approach, same output per page","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"plan the content site's move from our custom cms to something the marketing team can use without us","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"LCP is 4.2s on mobile for the homepage, mostly the hero image and a font","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"pricing page: three tiers, a monthly/annual toggle, feature comparison below, and a contact-sales path for enterprise","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"keep going with that","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"LCP is 4.2s on mobile for the homepage, mostly the hero image and a font","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"pricing page: three tiers, a monthly/annual toggle, feature comparison below, and a contact-sales path for enterprise","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"we need to decide how to store patient data given the hipaa requirements and the fact that two of our hospital customers want their data in their own aws account. options as i see them: shared multi-tenant with envelope encryption per tenant, dedicated database per tenant, or full single-tenant deployments. write the analysis including the operational burden of each at 30 customers","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"per-tenant encryption keys with the tenant's kms key optionally, and a clean failure when their key is unavailable rather than a silent fallback","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"per-tenant encryption keys with the tenant's kms key optionally, and a clean failure when their key is unavailable rather than a silent fallback","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"tenant settings page for byok with the key arn, a validation step, and a clear statement of what becomes inaccessible if they revoke","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the kms client has no retry and a 1 second timeout","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"we have two encryption helpers, one for phi columns and one for attachments, with different key derivation. unify on the phi one's approach and keep both data sets readable","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"decrypting a batch of records is 40x slower than one at a time, which is backwards","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the kms client has no retry and a 1 second timeout","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"we have two encryption helpers, one for phi columns and one for attachments, with different key derivation. unify on the phi one's approach and keep both data sets readable","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"decrypting a batch of records is 40x slower than one at a time, which is backwards","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"audit every place phi crosses a service boundary and tell me whether it's encrypted in transit and at rest at each hop","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"hipaa-facing security documentation: encryption, access controls, audit logging, and our breach notification process","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"access logging for every phi read with the purpose recorded, queryable per patient for a disclosure request","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"access logging for every phi read with the purpose recorded, queryable per patient for a disclosure request","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"disclosure report generator: everyone who accessed a patient's record in a date range, as a pdf","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the access log records the service account not the human when a request comes through the api","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"break-glass access flow for emergencies: elevated read with a required reason, time boxed, and everyone notified","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the break-glass reason field is optional","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"explain what a support engineer can see about a patient today, without break-glass","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the access log records the service account not the human when a request comes through the api","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"break-glass access flow for emergencies: elevated read with a required reason, time boxed, and everyone notified","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the break-glass reason field is optional","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"explain what a support engineer can see about a patient today, without break-glass","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"internal policy doc for break-glass access: when it's allowed, the review process afterwards, and the consequences of misuse","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"audit review queue ui: break-glass events awaiting review, the reason given, and an approve/escalate action","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"plan how we'd support data residency for a canadian hospital group without forking the whole deployment","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"机器人的定位在长走廊里会漂移，激光雷达数据看起来正常。先帮我分析原因，不要改代码","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"zh"} -{"prompt":"scan matching parameters exposed as ros params with sane defaults, and a diagnostic topic reporting the match confidence","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the localization confidence isn't surfaced anywhere in the ui so operators can't tell when the robot is lost","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"机器人的定位在长走廊里会漂移，激光雷达数据看起来正常。先帮我分析原因，不要改代码","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"scan matching parameters exposed as ros params with sane defaults, and a diagnostic topic reporting the match confidence","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the localization confidence isn't surfaced anywhere in the ui so operators can't tell when the robot is lost","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} {"prompt":"our launch files duplicate 200 lines of parameter setup across four robot variants. parameterize them, same effective params per variant","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"review the safety controller's override logic and tell me whether a stale sensor reading can be treated as valid","purpose":"review","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"safety documentation for the robot: the stopping distances, the sensor coverage gaps, and the conditions under which autonomy disengages","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"plan the simulation setup so we can regression test navigation changes without a robot","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"just carry on for now","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"review the safety controller's override logic and tell me whether a stale sensor reading can be treated as valid","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"safety documentation for the robot: the stopping distances, the sensor coverage gaps, and the conditions under which autonomy disengages","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"plan the simulation setup so we can regression test navigation changes without a robot","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"here's the perf trace summary from the tracking page, the thing is genuinely unusable on a mid-range android:\n\nLargest Contentful Paint: 6,240 ms\nTotal Blocking Time: 1,890 ms\nCumulative Layout Shift: 0.31\n\nRender-blocking resources:\n /_next/static/css/app.css 84 KiB 410 ms\n https://maps.vendor.com/sdk.js 612 KiB 2,180 ms\n https://fonts.example.com/inter.css 11 KiB 190 ms\n\nLong tasks (main thread):\n maps.vendor.com/sdk.js 980 ms\n app-client.js (hydration) 520 ms\n analytics.js 210 ms\n\nLayout shifts:\n .tracking-map (0 -> 420px) 0.24\n .eta-banner (font swap) 0.07\n\nthe map is the whole point of the page so we can't just drop it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"lazy load the maps sdk after first paint with a static map image placeholder at the right dimensions so nothing shifts","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"lazy load the maps sdk after first paint with a static map image placeholder at the right dimensions so nothing shifts","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"self-host the font and preload it instead of the external stylesheet","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"plan the performance work for the customer-facing pages, with a budget per page and a check in CI that enforces it","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"lighthouse CI on the four public pages with budgets, failing the build when LCP or CLS regress","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"lighthouse CI on the four public pages with budgets, failing the build when LCP or CLS regress","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"our map component is instantiated three ways across the app with different option objects. one wrapper, identical behavior in each place","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"explain what our analytics script does before hydration and whether any of it needs to be there","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"explain what our analytics script does before hydration and whether any of it needs to be there","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"write the performance guidelines for the frontend team — what we measure, the budgets, and the patterns that keep breaking them","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"server-render the eta and initial stop list so the page is useful before the map loads","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"server-render the eta and initial stop list so the page is useful before the map loads","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} {"prompt":"the tracking page fetches the same route data three times on load","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"image optimization for the marketing site — the responsive sizes, avif with fallbacks, and cache headers","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"hero image is a 2.4mb png","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"image optimization for the marketing site — the responsive sizes, avif with fallbacks, and cache headers","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"hero image is a 2.4mb png","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} {"prompt":"figure out the plan for our edge caching — what's cacheable, per-user vs anonymous, and how we purge on content changes","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"logged-in users occasionally see another user's name in the header, which smells like an edge cache problem","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"check every route for whether it sets a cache-control header appropriate to whether it contains user data","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"internal doc on our caching layers, in order, with what each one keys on","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"our route handlers set cache headers ad hoc, some with `private` some not. centralize the policy, and list any route whose cacheability changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"logged-in users occasionally see another user's name in the header, which smells like an edge cache problem","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"check every route for whether it sets a cache-control header appropriate to whether it contains user data","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"internal doc on our caching layers, in order, with what each one keys on","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"our route handlers set cache headers ad hoc, some with `private` some not. centralize the policy, and list any route whose cacheability changes","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"design the tenant isolation approach then build the key management piece","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"keep it going","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"propose how we handle scheduling for the dispatch team. hard constraints: driver hours regulations, vehicle certifications for hazmat, and union break rules. soft: fairness across drivers week to week. i want the model and an honest read on whether we build this or buy it","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"driver hours tracking against the regulations with a warning before a violation, not after","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"weekly schedule grid: drivers as rows, days as columns, shifts as blocks you can drag, with violations highlighted live","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the hours calculation counts breaks as driving time","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"driver hours tracking against the regulations with a warning before a violation, not after","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"weekly schedule grid: drivers as rows, days as columns, shifts as blocks you can drag, with violations highlighted live","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the hours calculation counts breaks as driving time","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"our shift model has both a `duration_minutes` and start/end timestamps that can disagree. pick one representation and migrate, no schedule changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the fairness metric reports the same driver as overworked every week even after we rebalance","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"read the certification check and tell me if an expired certification blocks assignment or just warns","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"dispatcher handbook chapter on the scheduling rules we enforce and the ones we only warn about","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the fairness metric reports the same driver as overworked every week even after we rebalance","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"read the certification check and tell me if an expired certification blocks assignment or just warns","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"dispatcher handbook chapter on the scheduling rules we enforce and the ones we only warn about","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"shift swap requests between drivers with a dispatcher approval and the constraint check re-run on the swapped state","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"swap requests can be approved after the shift has started","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"driver app shift view with the swap request flow and a clear state for pending requests","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"swap requests can be approved after the shift has started","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"driver app shift view with the swap request flow and a clear state for pending requests","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"two drivers can both accept the same open shift if they tap at the same moment","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"plan the payroll export — hours by category, overtime rules per region, and the format their payroll provider wants","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain how we compute overtime today and whether it handles a week spanning a month boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"payroll export documentation for the finance team: the columns, the categories, and how to reconcile against the schedule","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"our hours aggregation exists in the payroll export, the dashboard and a compliance report, computed three ways. one implementation, and report the differences","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"figure out the plan for mobile time clock with geofencing, then build the clock-in endpoint","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"look over the scheduling constraint code and clean up the naming","purpose":"review","secondary":"refactor","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} -{"prompt":"and that's the lot, wrap it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"explain how we compute overtime today and whether it handles a week spanning a month boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"payroll export documentation for the finance team: the columns, the categories, and how to reconcile against the schedule","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"our hours aggregation exists in the payroll export, the dashboard and a compliance report, computed three ways. one implementation, and report the differences","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"figure out the plan for mobile time clock with geofencing, then build the clock-in endpoint","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"look over the scheduling constraint code and clean up the naming","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} {"prompt":"type inference for our config language — hindley-milner-ish, unify across included files, and error messages that point at the right span","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"so the interpreter. tree-walking is fine for our sizes but the startup parse of a 40k line config is 900ms and people notice. bytecode vm, or caching the parsed ast, or a faster parser. i want the plan with what each buys and what it costs us in maintenance","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"error messages say 'unexpected token' with no line number","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"our ast nodes are boxed enums with Vec children everywhere. move to an arena with indices, identical evaluation results","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"stack overflow on deeply nested expressions, around 900 levels, and it takes the process down instead of erroring","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain the evaluation order in our interpreter for a chain of lazy references — i can't tell from reading it whether cycles are detected before or during evaluation","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"language reference for our config format: syntax, the type system, the standard functions, and the evaluation semantics","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"formatter for the config language, idempotent, preserving comments and blank line groupings","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the formatter drops trailing comments on the last line of a block","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"so the interpreter. tree-walking is fine for our sizes but the startup parse of a 40k line config is 900ms and people notice. bytecode vm, or caching the parsed ast, or a faster parser. i want the plan with what each buys and what it costs us in maintenance","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"error messages say 'unexpected token' with no line number","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"our ast nodes are boxed enums with Vec children everywhere. move to an arena with indices, identical evaluation results","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"stack overflow on deeply nested expressions, around 900 levels, and it takes the process down instead of erroring","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"explain the evaluation order in our interpreter for a chain of lazy references — i can't tell from reading it whether cycles are detected before or during evaluation","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"language reference for our config format: syntax, the type system, the standard functions, and the evaluation semantics","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"formatter for the config language, idempotent, preserving comments and blank line groupings","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the formatter drops trailing comments on the last line of a block","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"playground page for the config language: editor on the left, evaluated output on the right, live, with shareable urls","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the playground url gets too long for big configs and breaks in slack","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"nuxt: the cms preview mode needs to render draft content without caching, and exit cleanly back to the published version","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"preview mode leaks into the public site for the next visitor after an editor uses it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the preview cookie has no SameSite and no expiry","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the playground url gets too long for big configs and breaks in slack","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"nuxt: the cms preview mode needs to render draft content without caching, and exit cleanly back to the published version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"preview mode leaks into the public site for the next visitor after an editor uses it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the preview cookie has no SameSite and no expiry","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"our content fetching happens in asyncData in some pages and in a composable in others, with different error handling. one approach, same rendered output","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"plan the incremental static regeneration story — which pages, the revalidation triggers from the cms, and what an editor sees while it rebuilds","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"webhook receiver that revalidates the affected pages when content changes, with a fallback full rebuild nightly","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"check whether an editor can publish content that breaks the build, and what happens to the live site if they do","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"webhook receiver that revalidates the affected pages when content changes, with a fallback full rebuild nightly","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"check whether an editor can publish content that breaks the build, and what happens to the live site if they do","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"editor handbook for the cms: content types, what each field does, the publishing flow, and the preview gotchas","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"rich text renderer for the cms content with our components mapped to the block types, and a fallback for unknown blocks","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"kafka: consumer group rebalances every few minutes and throughput tanks. session timeout is default, processing takes 2-3s per message","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the max.poll.records is 500 with a 3 second per-message handler","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"kafka: consumer group rebalances every few minutes and throughput tanks. session timeout is default, processing takes 2-3s per message","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the max.poll.records is 500 with a 3 second per-message handler","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"topic layout plan for the new event system — how many topics, partitioning key per topic, retention, and how we handle a topic that needs repartitioning later","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"walk me through our consumer's offset commit strategy and tell me exactly when a message can be processed twice","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"onwards then","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"walk me through our consumer's offset commit strategy and tell me exactly when a message can be processed twice","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"right so the queue situation. we have rabbitmq for the old services, kafka for the new event stream, and sqs for two lambdas. three sets of operational knowledge, three failure modes, three dashboards. i want a plan to get to one, or a defensible argument for keeping two. include the migration cost per service","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"kafka consumer in the notification service replacing the rabbit consumer, same at-least-once semantics and the same dedupe behavior","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"kafka consumer in the notification service replacing the rabbit consumer, same at-least-once semantics and the same dedupe behavior","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"queue metrics page: lag per consumer group, throughput, and the dlq counts, all in one view instead of three dashboards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the rabbit prefetch is unlimited on one consumer","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the rabbit prefetch is unlimited on one consumer","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"our four consumers each implement their own retry-with-backoff-and-dlq. one library, same retry counts and dlq routing per consumer","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"messages land in the dlq with no error recorded, so we have no idea why they failed","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"explain what happens to an in-flight rabbit message when the consumer pod is SIGTERMed","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"explain what happens to an in-flight rabbit message when the consumer pod is SIGTERMed","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"runbook for a growing dlq: how to inspect a message, how to replay a batch, and when not to","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"dlq replay tool with a filter, a dry run showing what would be replayed, and a rate limit so we don't self-ddos","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"dlq browser: paginated messages, the failure reason, the payload, and a replay-selected action","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"replay sends the messages back to the front of the queue instead of the back","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"plan the schema registry rollout — avro or protobuf, compatibility mode per topic, and how a producer gets blocked from breaking consumers","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"a producer deployed a schema change and consumers started failing to deserialize, even though compatibility is supposedly enforced","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"tell me which of our topics have compatibility checking enabled and which are wide open","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"event schema documentation generated from the registry, one page per topic with the fields and their history","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"producer library wrapper that registers schemas, validates before send, and fails loudly on an incompatible change at build time","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"our event payloads have both `userId` and `user_id` depending on the topic. normalize to snake_case with a compatibility window, and list every consumer that has to change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"dlq browser: paginated messages, the failure reason, the payload, and a replay-selected action","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"replay sends the messages back to the front of the queue instead of the back","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"plan the schema registry rollout — avro or protobuf, compatibility mode per topic, and how a producer gets blocked from breaking consumers","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"a producer deployed a schema change and consumers started failing to deserialize, even though compatibility is supposedly enforced","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"tell me which of our topics have compatibility checking enabled and which are wide open","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"event schema documentation generated from the registry, one page per topic with the fields and their history","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"producer library wrapper that registers schemas, validates before send, and fails loudly on an incompatible change at build time","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"our event payloads have both `userId` and `user_id` depending on the topic. normalize to snake_case with a compatibility window, and list every consumer that has to change","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"the schema registry url is hardcoded to the staging instance in one service","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"plan the queue consolidation then implement the first consumer migration","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"figure out why the dlq has no error context and then write the runbook entry","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"carry on then","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"here's the failing build, the config language tests are red after i touched the lexer:\n\nrunning 214 tests\ntest lexer::tests::string_escapes ... FAILED\ntest lexer::tests::nested_interpolation ... FAILED\ntest parser::tests::multiline_string ... FAILED\n\nfailures:\n\n---- lexer::tests::string_escapes stdout ----\nthread 'lexer::tests::string_escapes' panicked at src/lexer.rs:412:9:\nassertion `left == right` failed\n left: [Str(\"a\\\\nb\"), Eof]\n right: [Str(\"a\\nb\"), Eof]\n\n---- lexer::tests::nested_interpolation stdout ----\nthread 'lexer::tests::nested_interpolation' panicked at src/lexer.rs:455:9:\nassertion `left == right` failed\n left: [StrStart, Lit(\"x=\"), InterpStart, Ident(\"a\"), InterpEnd, StrEnd, Eof]\n right: [StrStart, Lit(\"x=\"), InterpStart, Ident(\"a\"), Plus, Ident(\"b\"), InterpEnd, StrEnd, Eof]\n\ntest result: FAILED. 211 passed; 3 failed\n\ni was trying to handle raw strings and clearly broke escape processing and interpolation","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"raw string literals in the lexer, r\"...\" style, without touching how escapes work in normal strings","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"our lexer's string handling is one 300 line function with nested state flags. split it into explicit states, same token stream for the whole test corpus","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"string interpolation nested two deep produces the wrong token order","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"syntax highlighting grammar for our config language, for vscode and for the docs site's code blocks","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the tmLanguage file doesn't highlight interpolation inside strings","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"review our lexer's handling of unicode identifiers and tell me whether we're consistent with what the docs claim","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"spec section on string literals: the escape table, raw strings, multiline behavior, and interpolation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"plan how we version the config language itself so we can make a breaking syntax change without breaking every existing file","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"raw string literals in the lexer, r\"...\" style, without touching how escapes work in normal strings","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"our lexer's string handling is one 300 line function with nested state flags. split it into explicit states, same token stream for the whole test corpus","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"string interpolation nested two deep produces the wrong token order","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"syntax highlighting grammar for our config language, for vscode and for the docs site's code blocks","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"the tmLanguage file doesn't highlight interpolation inside strings","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"review our lexer's handling of unicode identifiers and tell me whether we're consistent with what the docs claim","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"spec section on string literals: the escape table, raw strings, multiline behavior, and interpolation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"plan how we version the config language itself so we can make a breaking syntax change without breaking every existing file","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"fuzzing setup for the parser with a corpus from our customers' configs, running in CI nightly","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the fuzzer found a panic on an unterminated block comment","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"explain how our error recovery works when parsing an invalid file — do we report one error or try to continue","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"diagnostics rendering with the source snippet, a caret span, and a note when there's a likely fix — like rustc's output","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"error output uses ansi colors even when piped to a file","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"error message catalog doc — every diagnostic code, what causes it, and how to fix it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"the fuzzer found a panic on an unterminated block comment","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"explain how our error recovery works when parsing an invalid file — do we report one error or try to continue","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"diagnostics rendering with the source snippet, a caret span, and a note when there's a likely fix — like rustc's output","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"error output uses ansi colors even when piped to a file","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"error message catalog doc — every diagnostic code, what causes it, and how to fix it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"map out the plan for making the interpreter embeddable — a c api, a stable abi, and what we promise about memory ownership","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"wieder mal: die Cache-Invalidierung im CMS-Frontend greift nicht, wenn nur ein verschachtelter Block geändert wird. woran liegt das","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} -{"prompt":"content model for a page builder: sections with typed props, ordering, and per-section visibility rules","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"page builder ui: section list with drag reorder, an inline settings panel per section, and a live preview pane","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the preview pane reloads the whole iframe on every keystroke","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"wieder mal: die Cache-Invalidierung im CMS-Frontend greift nicht, wenn nur ein verschachtelter Block geändert wird. woran liegt das","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"de"} +{"prompt":"content model for a page builder: sections with typed props, ordering, and per-section visibility rules","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"page builder ui: section list with drag reorder, an inline settings panel per section, and a live preview pane","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the preview pane reloads the whole iframe on every keystroke","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"we have two component registries, one for the renderer and one for the editor's settings forms, and adding a component means touching both. unify, same components available in both","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"sections reorder correctly in the editor but publish in the original order","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"check whether an editor can inject html through any of the rich text fields and get it rendered unescaped","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"documentation for adding a new page-builder section, aimed at a developer joining next week","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"plan the localization of cms content — per-locale drafts, fallbacks, and what an editor sees when a translation is missing","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"i want the design for our multi-region active-active setup. writes in both regions, conflict resolution, and a story for the tables where conflicts are unacceptable (billing, primarily). also what we tell customers about consistency, because right now we'd be lying if we said strong","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"region-aware routing in the api so a write goes to the home region of the tenant, with a redirect rather than a cross-region write","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"region indicator in the app header for internal builds, showing which region served the request","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"the region config is read from an env var that isn't set in one deployment, defaulting to us-east","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"our db access assumes a single connection string throughout. thread the region through properly, with the same queries hitting the same data as today","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"requests from europe occasionally get served by the us region and take 400ms extra, but only for authenticated users","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain what consistency our current setup actually provides for a read immediately after a write from a different region","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"customer-facing doc on data residency and regions: where data lives, which operations are cross-region, and the latency implications","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"check whether an editor can inject html through any of the rich text fields and get it rendered unescaped","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"documentation for adding a new page-builder section, aimed at a developer joining next week","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"plan the localization of cms content — per-locale drafts, fallbacks, and what an editor sees when a translation is missing","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"i want the design for our multi-region active-active setup. writes in both regions, conflict resolution, and a story for the tables where conflicts are unacceptable (billing, primarily). also what we tell customers about consistency, because right now we'd be lying if we said strong","purpose":"planning","secondary":"writing","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"region-aware routing in the api so a write goes to the home region of the tenant, with a redirect rather than a cross-region write","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"region indicator in the app header for internal builds, showing which region served the request","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the region config is read from an env var that isn't set in one deployment, defaulting to us-east","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"our db access assumes a single connection string throughout. thread the region through properly, with the same queries hitting the same data as today","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"requests from europe occasionally get served by the us region and take 400ms extra, but only for authenticated users","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain what consistency our current setup actually provides for a read immediately after a write from a different region","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"customer-facing doc on data residency and regions: where data lives, which operations are cross-region, and the latency implications","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"tenant region migration: move a tenant's data to another region with a short write freeze and a verifiable cutover","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"region migration admin ui: pick a tenant, pick a target, show the estimated freeze, and a progress log","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the migration progress log shows percentages over 100","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"the migration progress log shows percentages over 100","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"plan how we test region failover for real, including the customer comms and the rollback","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"after a failover drill, some tenants had their region flag pointing at the old region for hours","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"read the failover automation and tell me which steps are actually automated versus documented","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"after a failover drill, some tenants had their region flag pointing at the old region for hours","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"read the failover automation and tell me which steps are actually automated versus documented","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"failover runbook, honest about the manual steps, with the exact commands and the verification at each stage","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"our health checks report per-pod health but nothing reports regional health. add a regional readiness signal the dns layer can use","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"next bit then","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"here's the ticket that's been bouncing around for a month, nobody wants it:\n\nTITLE: Bulk tag update times out for large accounts\nDETAIL: PATCH /v1/records/bulk-tag with 5000 record ids returns 504 after 60s for accounts\n with >2M records. Works fine under 500 ids. The gateway timeout is 60s and can't be raised.\nWHAT I TRIED: adding an index on record_tags(record_id) — no change. The slow part appears\n to be the tag reconciliation, we delete all tags for each record then reinsert.\nCUSTOMER: three enterprise accounts hitting this weekly, they've resorted to 200-at-a-time\n loops which take 40 minutes.\nAPPETITE: whatever it takes, this is embarrassing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"here's the ticket that's been bouncing around for a month, nobody wants it:\n\nTITLE: Bulk tag update times out for large accounts\nDETAIL: PATCH /v1/records/bulk-tag with 5000 record ids returns 504 after 60s for accounts\n with >2M records. Works fine under 500 ids. The gateway timeout is 60s and can't be raised.\nWHAT I TRIED: adding an index on record_tags(record_id) — no change. The slow part appears\n to be the tag reconciliation, we delete all tags for each record then reinsert.\nCUSTOMER: three enterprise accounts hitting this weekly, they've resorted to 200-at-a-time\n loops which take 40 minutes.\nAPPETITE: whatever it takes, this is embarrassing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} {"prompt":"make bulk tagging async — accept the request, return a job id, and provide a status endpoint with per-record results","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the delete-then-insert tag reconciliation should be a diff — compute added and removed, touch only those rows","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"bulk action ui that submits async and shows a progress toast with a link to the job result","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the bulk endpoint accepts unlimited ids, cap it at 10000 with a clear error","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"review our other bulk endpoints for the same delete-then-insert pattern","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"api docs for the async bulk pattern — submit, poll, interpret the per-item results, and the limits","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"plan the async job pattern properly so every long operation uses it instead of each endpoint inventing its own","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"job status polling hammers us — 4 requests per second per client because the ui polls at 250ms","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"job progress via server-sent events instead of polling, with a polling fallback","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the delete-then-insert tag reconciliation should be a diff — compute added and removed, touch only those rows","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"bulk action ui that submits async and shows a progress toast with a link to the job result","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the bulk endpoint accepts unlimited ids, cap it at 10000 with a clear error","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"review our other bulk endpoints for the same delete-then-insert pattern","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"api docs for the async bulk pattern — submit, poll, interpret the per-item results, and the limits","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"plan the async job pattern properly so every long operation uses it instead of each endpoint inventing its own","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"job status polling hammers us — 4 requests per second per client because the ui polls at 250ms","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"job progress via server-sent events instead of polling, with a polling fallback","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"tag picker with create-on-type, existing tags fuzzy matched, and a limit indicator when the record has many","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"creating a tag with a leading space creates a duplicate that looks identical","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"our tag normalization happens in the ui for creation and in the api for import, differently, which is where the duplicates come from. one normalizer, and dedupe the existing ones","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"explain how tag permissions work — can a viewer add tags, and is that enforced server side","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"creating a tag with a leading space creates a duplicate that looks identical","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"our tag normalization happens in the ui for creation and in the api for import, differently, which is where the duplicates come from. one normalizer, and dedupe the existing ones","purpose":"refactor","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"explain how tag permissions work — can a viewer add tags, and is that enforced server side","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"help article on tags: creating, renaming, merging, and what happens to records when you delete a tag","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"tag merge operation that reassigns records and keeps an alias so old api calls with the merged tag still work","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"plan how we'd support hierarchical tags without breaking the flat api","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"renaming a tag to an existing name silently merges them with no warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"ya, dale","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"es"} +{"prompt":"renaming a tag to an existing name silently merges them with no warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"propose the architecture for our ai features. we want summarization of a record's activity, a natural language query over the user's data, and suggested tags. constraints: no customer data leaves our vpc without an opt-in, latency under 3s for the interactive ones, and cost per tenant has to be attributable","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"summarization endpoint that assembles the context, calls the model, caches by content hash, and records token usage per tenant","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"summary panel with a streaming render, a regenerate action, and a clear 'ai generated' marker","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"summary panel with a streaming render, a regenerate action, and a clear 'ai generated' marker","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"the streaming render flickers because we re-render the whole markdown on every chunk","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"our three ai call sites each build prompts inline and handle errors differently. one client with the prompts in a registry, same prompts sent","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"summaries occasionally include content from a different record, which is the worst possible bug here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"review the context assembly for the summarizer and tell me whether it can ever include data the requesting user can't see","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"customer-facing doc about our ai features: what data is used, where it goes, retention, and how to turn it off","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"natural language to query translation with a validation pass that rejects anything touching another tenant, and shows the generated query to the user","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"query assistant ui: input, the generated query shown for review, run, and results with a 'this might be wrong' framing","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the token limit truncates long records silently mid-sentence","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"plan the evaluation harness for these features — a golden set, what we measure, and how we catch a regression before customers do","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"suggested tags are heavily biased toward the four most common tags regardless of content","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"check how we attribute model cost per tenant, and whether a shared cached response gets billed to the wrong one","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"internal doc on our prompt registry: how to add a prompt, the versioning, and the review requirement before it ships","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"per-tenant ai usage limits with a clear message when exceeded and an admin view of consumption","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"our three ai call sites each build prompts inline and handle errors differently. one client with the prompts in a registry, same prompts sent","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"summaries occasionally include content from a different record, which is the worst possible bug here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"review the context assembly for the summarizer and tell me whether it can ever include data the requesting user can't see","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"customer-facing doc about our ai features: what data is used, where it goes, retention, and how to turn it off","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"natural language to query translation with a validation pass that rejects anything touching another tenant, and shows the generated query to the user","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"query assistant ui: input, the generated query shown for review, run, and results with a 'this might be wrong' framing","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the token limit truncates long records silently mid-sentence","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"plan the evaluation harness for these features — a golden set, what we measure, and how we catch a regression before customers do","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"suggested tags are heavily biased toward the four most common tags regardless of content","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"check how we attribute model cost per tenant, and whether a shared cached response gets billed to the wrong one","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"internal doc on our prompt registry: how to add a prompt, the versioning, and the review requirement before it ships","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"per-tenant ai usage limits with a clear message when exceeded and an admin view of consumption","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"design the eval harness and then build the golden set runner","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"explain how the context assembly works then write it up for the security review","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"one more and then stop","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"explain how the context assembly works then write it up for the security review","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} {"prompt":"we need a plan for splitting the monolithic ledger service into separate read and write paths. postgres logical replication is on the table, so is debezium CDC. write it up as an RFC with explicit rollback points at each stage","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"add pagination to GET /v2/orders, cursor based","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"typo in the toast: \"Sucessfully saved\" -> \"Successfully saved\"","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"core","lang":"en"} +{"prompt":"typo in the toast: \"Sucessfully saved\" -> \"Successfully saved\"","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"SwiftUI settings screen for the notification prefs — grouped list, three toggles, a picker for quiet hours, matches the rest of the app's styling","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"UserManager is a terrible name at this point, it does account lifecycle only. rename it to AccountService everywhere including the test doubles and the DI registration","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"why does the invoice total come out 1 cent short sometimes? only on annual plans with a coupon as far as i can tell","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"UserManager is a terrible name at this point, it does account lifecycle only. rename it to AccountService everywhere including the test doubles and the DI registration","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"why does the invoice total come out 1 cent short sometimes? only on annual plans with a coupon as far as i can tell","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"is the upload handler in internal/media safe against zip bombs and path traversal? just want an assessment before we ship","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"README for the pgshovel CLI — install, the three subcommands, a quickstart with real flags, and a troubleshooting section","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"how should we shard the events table","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"bump axios to 1.8.2, lockfile too","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"bump axios to 1.8.2, lockfile too","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"rust: parser for the legacy .plm telemetry format. records are length-prefixed, big endian, header has a version byte and we need to support v2 and v3. stream it, don't read the whole file","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"make the nav sticky","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"walk me through how the offline queue in Sync/QueueCoordinator.swift decides what to retry. i've read it twice and i still don't get the ordering guarantees","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"make the nav sticky","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"walk me through how the offline queue in Sync/QueueCoordinator.swift decides what to retry. i've read it twice and i still don't get the ordering guarantees","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"extract the 400 lines of form state out of CheckoutPanel.tsx into hooks. same behavior, i just can't read it anymore","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"design doc for offline sync in the iOS app. we're on SwiftData now. cover the local store shape, conflict resolution when two devices edit the same note, and what happens if the refresh token expires halfway through a sync","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"plan and then build the retry/backoff layer for the webhook dispatcher. i want the design first but go ahead and land the code in the same go","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.75,"slice":"mixed","lang":"en"} -{"prompt":"flaky test: apps/api/test/session_reaper_test.go fails maybe 1 in 12 runs on CI, never locally. seen it fail two different assertions so i assume it's timing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"shrink the padding on the sidebar nav items, they're way too airy. 12px -> 6px vertical","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.15,"slice":"boundary","lang":"en"} -{"prompt":"migration guide for people upgrading from v3 to v4 of the sdk. the breaking changes are: constructor takes an options object now, `fetchAll` is gone, and errors are typed","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"postgres migration: partial index on orders (status) where status in ('pending','processing'), plus a backfill script that chunks so we don't lock the table. table is ~180M rows","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"there are three copies of the phone number validation regex — web, admin, and the twilio worker. one of them is subtly different. pull them into one place","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"compose bottom sheet for the filter panel, drag handle, snap to half and full, dim the scrim behind it","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} +{"prompt":"design doc for offline sync in the iOS app. we're on SwiftData now. cover the local store shape, conflict resolution when two devices edit the same note, and what happens if the refresh token expires halfway through a sync","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"plan and then build the retry/backoff layer for the webhook dispatcher. i want the design first but go ahead and land the code in the same go","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"flaky test: apps/api/test/session_reaper_test.go fails maybe 1 in 12 runs on CI, never locally. seen it fail two different assertions so i assume it's timing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"shrink the padding on the sidebar nav items, they're way too airy. 12px -> 6px vertical","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"migration guide for people upgrading from v3 to v4 of the sdk. the breaking changes are: constructor takes an options object now, `fetchAll` is gone, and errors are typed","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"postgres migration: partial index on orders (status) where status in ('pending','processing'), plus a backfill script that chunks so we don't lock the table. table is ~180M rows","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"there are three copies of the phone number validation regex — web, admin, and the twilio worker. one of them is subtly different. pull them into one place","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"compose bottom sheet for the filter panel, drag handle, snap to half and full, dim the scrim behind it","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"what does this do\n\n```\n(?<=\\bv)(\\d+)(?:\\.(\\d+))?(?:\\.(\\d+))?(?:-([0-9A-Za-z-.]+))?(?=\\s|$)\n```","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"roadmap for deprecating v1 of the pricing API across two quarters — sunset dates, what we migrate ourselves vs what partners have to do, and the checkpoints where we can still back out","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"missing await in `flushMetrics`, that's why the last batch drops on shutdown. one line","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"celery beat job that rolls up per-account usage every night at 2am UTC into the usage_daily table, idempotent so we can re-run a day, and it has to survive a worker dying mid-run","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"skeleton loaders for the dashboard cards instead of the spinner","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"necesito un plan para migrar de MySQL 5.7 a Postgres 16. son 40 tablas, hay triggers y dos stored procedures. quiero fases, ventanas de mantenimiento y cómo hacemos el dual-write mientras tanto","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"es"} -{"prompt":"PR description for the branch, keep it short, there's a linked ticket ENG-2291","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.25,"slice":"core","lang":"en"} +{"prompt":"roadmap for deprecating v1 of the pricing API across two quarters — sunset dates, what we migrate ourselves vs what partners have to do, and the checkpoints where we can still back out","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"missing await in `flushMetrics`, that's why the last batch drops on shutdown. one line","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"celery beat job that rolls up per-account usage every night at 2am UTC into the usage_daily table, idempotent so we can re-run a day, and it has to survive a worker dying mid-run","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"skeleton loaders for the dashboard cards instead of the spinner","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"necesito un plan para migrar de MySQL 5.7 a Postgres 16. son 40 tablas, hay triggers y dos stored procedures. quiero fases, ventanas de mantenimiento y cómo hacemos el dual-write mientras tanto","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"es"} +{"prompt":"PR description for the branch, keep it short, there's a linked ticket ENG-2291","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"refresh token rotation in the express auth service — rotate on every use, detect reuse of a revoked token and nuke the family, store hashes not the tokens","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the app hangs on launch about 1 in 5 cold starts on my M2. no crash, just a beachball. i suspect something on the main actor but the sample is a wall of dispatch frames","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the app hangs on launch about 1 in 5 cold starts on my M2. no crash, just a beachball. i suspect something on the main actor but the sample is a wall of dispatch frames","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"pasted from the sprint board, need your read on approach before i estimate:\n\n> ENG-1874 — Bulk member import\n> As an org admin I want to upload a CSV of up to 50k members and have them invited.\n> AC:\n> - accepts CSV and XLSX\n> - validates emails, shows a per-row error report before anything is sent\n> - partial success is allowed, admin can retry just the failed rows\n> - must not blow the sendgrid rate limit\n> - progress visible while it runs, survives a page refresh\n> Notes from Dana: last time we tried this synchronously it timed out at ~4k rows.\n\nhow would you structure this? i mostly care about where the state lives and how we get resumability without building a whole job system","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"flip the `new_search_ranker` flag default to on for internal orgs only","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"flip the `new_search_ranker` flag default to on for internal orgs only","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"convert the ImageCache completion-handler API to async/await. keep the old methods as deprecated shims so callers can move gradually","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"audit the terraform in infra/prod for things that cost money and shouldn't — idle NAT gateways, oversized RDS, gp2 volumes, that kind of thing. don't change anything yet, just tell me","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"release notes for 2.4.0, user-facing tone, group into new / improved / fixed","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"kafka consumer for the order-events topic that dedupes on (order_id, revision) — we're getting replays after rebalance and downstream is double-charging","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"drag to reorder the playlist rows, with the little grip icon, and it should feel right on touch too","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"audit the terraform in infra/prod for things that cost money and shouldn't — idle NAT gateways, oversized RDS, gp2 volumes, that kind of thing. don't change anything yet, just tell me","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"release notes for 2.4.0, user-facing tone, group into new / improved / fixed","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"kafka consumer for the order-events topic that dedupes on (order_id, revision) — we're getting replays after rebalance and downstream is double-charging","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"drag to reorder the playlist rows, with the little grip icon, and it should feel right on touch too","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"timeout in config/http.yml is 5s, needs to be 30s for the reporting client","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"sketch the data model for multi-tenant workspaces. users can belong to several, roles are per workspace, and billing hangs off the workspace not the user","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} +{"prompt":"sketch the data model for multi-tenant workspaces. users can belong to several, roles are per workspace, and billing hangs off the workspace not the user","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"```\nFATAL: sqlx: scan error on column index 3, name \"deleted_at\": converting NULL to time.Time is unsupported\n\ngoroutine 1 [running]:\ngithub.com/hollowpoint/api/internal/store.(*ProjectStore).List(0xc0001a4020, {0x1049fe0, 0xc0000260a0}, {0xc000132030, 0x1a})\n\t/src/internal/store/project.go:118 +0x3c8\ngithub.com/hollowpoint/api/internal/handler.(*Handler).ListProjects(0xc00013a000, {0x1051e40, 0xc000180000}, 0xc000186000)\n\t/src/internal/handler/project.go:64 +0x9c\nnet/http.HandlerFunc.ServeHTTP(...)\n```\n\nthis only started after friday's deploy and only on the staging db. nothing in the migration touched deleted_at that i can see","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} -{"prompt":"document the /v3/subscriptions endpoints — request/response shapes, the four error codes, and the proration behavior. it's already built, i just never wrote it down","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"kubernetes to nomad, is it worth it? if yes i want a migration doc i can take to the platform review on thursday","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"cobra subcommand `snap prune` — takes --older-than, --dry-run, --keep-last N, prints what it would delete in a table","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"the focus ring doesn't show on the icon buttons in the toolbar. keyboard users can't tell where they are","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"rename `flush` to `commit` on the WriteBuffer type and everywhere it's called. there's a bunch of call sites, some in the python bindings","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"break the checkout rewrite into two week chunks","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"figure out where the leak is in the ingest worker, rss climbs ~200mb/hr and never comes back down. then write up a short postmortem for the incident channel","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.85,"slice":"mixed","lang":"en"} -{"prompt":"dataloader for the `author` field on Post so we stop N+1ing the users table in graphql","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"add wal/ to gitignore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"core","lang":"en"} -{"prompt":"toast/notification system for the web app — queue them, max 3 visible, auto dismiss after 5s unless it's an error, pause the timer on hover","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"runbook for on-call when the dunning worker backs up. include how to tell if it's stripe or us, the queue depth query, and the safe way to drain","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"why do we have two caches in the request path (the lru in resolver.ts and the redis one in cache/client.ts)? is one of them dead weight","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"architect a plugin system for the CLI. third parties should be able to add subcommands without us shipping their code — thinking wasm or subprocess protocol, talk me through both","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"redis token bucket rate limiter as express middleware, per api key, 1000/min with burst 50, return the standard RateLimit-* headers","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} +{"prompt":"document the /v3/subscriptions endpoints — request/response shapes, the four error codes, and the proration behavior. it's already built, i just never wrote it down","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"kubernetes to nomad, is it worth it? if yes i want a migration doc i can take to the platform review on thursday","purpose":"planning","secondary":"review","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"cobra subcommand `snap prune` — takes --older-than, --dry-run, --keep-last N, prints what it would delete in a table","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the focus ring doesn't show on the icon buttons in the toolbar. keyboard users can't tell where they are","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"rename `flush` to `commit` on the WriteBuffer type and everywhere it's called. there's a bunch of call sites, some in the python bindings","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"break the checkout rewrite into two week chunks","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"figure out where the leak is in the ingest worker, rss climbs ~200mb/hr and never comes back down. then write up a short postmortem for the incident channel","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"dataloader for the `author` field on Post so we stop N+1ing the users table in graphql","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"add wal/ to gitignore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"toast/notification system for the web app — queue them, max 3 visible, auto dismiss after 5s unless it's an error, pause the timer on hover","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"runbook for on-call when the dunning worker backs up. include how to tell if it's stripe or us, the queue depth query, and the safe way to drain","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"why do we have two caches in the request path (the lru in resolver.ts and the redis one in cache/client.ts)? is one of them dead weight","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"architect a plugin system for the CLI. third parties should be able to add subcommands without us shipping their code — thinking wasm or subprocess protocol, talk me through both","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"redis token bucket rate limiter as express middleware, per api key, 1000/min with burst 50, return the standard RateLimit-* headers","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"wrong default port in cmd/serve.go, should be 8081 not 8080","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"split internal/scheduler/scheduler.go up, it's 2100 lines. i'd guess three files: the loop, the lease code, and the metrics. no behavior change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"es normal que `latestSnapshot()` devuelva nil cuando la lista está vacía? me rompe la vista pero no sé si el bug está en la vista o en el store","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"es"} -{"prompt":"dark mode. we have hardcoded hex all over the css, want proper tokens and a data-theme switch that respects prefers-color-scheme with a manual override","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"translate docs/getting-started.md to spanish, keep code blocks and CLI flags in english","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} +{"prompt":"es normal que `latestSnapshot()` devuelva nil cuando la lista está vacía? me rompe la vista pero no sé si el bug está en la vista o en el store","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"es"} +{"prompt":"dark mode. we have hardcoded hex all over the css, want proper tokens and a data-theme switch that respects prefers-color-scheme with a manual override","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"translate docs/getting-started.md to spanish, keep code blocks and CLI flags in english","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"OTA update strategy for ~4000 esp32 units in the field, half of them on flaky cellular. dual bank A/B, rollback on watchdog, staged rollout by cohort. want the design before i touch the bootloader","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"remove the console.logs i left in the payments folder","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"presence service over websockets — who's viewing which doc, heartbeat every 15s, tombstone after 45s of silence, and it has to work with three api replicas behind the lb","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"read through packages/pipeline/src/stages and tell me what invariants the stage runner assumes. i'm about to add a stage and i don't want to violate something implicit","purpose":"review","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"CrashLoopBackOff on the collector pods since we cut over to the new node pool:\n\n```\n$ kubectl logs otel-collector-7c9f8d4b6-2xk4v --previous\n2026-07-29T18:02:11.884Z\tinfo\tservice/telemetry.go:84\tSetting up own telemetry...\n2026-07-29T18:02:11.891Z\tinfo\texporter@v0.108.0/exporter.go:275\tDeprecated component. Will be removed in future releases.\n2026-07-29T18:02:11.902Z\terror\tservice/collector.go:112\tfailed to build pipelines\t{\"error\": \"failed to create \\\"otlp\\\" exporter: rpc error: code = Unavailable desc = connection error: desc = \\\"transport: Error while dialing: dial tcp 10.4.19.22:4317: i/o timeout\\\"\"}\nError: cannot start pipelines: failed to build pipelines\n2026/07/29 18:02:11 collector server run finished with error\n```\n\n```\n$ kubectl get events --field-selector involvedObject.name=otel-collector-7c9f8d4b6-2xk4v\n2m Warning BackOff Back-off restarting failed container collector\n```\n\nthe gateway it's dialing is up, i can curl it from a debug pod in the same namespace. netpol looks unchanged","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"pasted-context","lang":"en"} +{"prompt":"remove the console.logs i left in the payments folder","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"presence service over websockets — who's viewing which doc, heartbeat every 15s, tombstone after 45s of silence, and it has to work with three api replicas behind the lb","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"read through packages/pipeline/src/stages and tell me what invariants the stage runner assumes. i'm about to add a stage and i don't want to violate something implicit","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"CrashLoopBackOff on the collector pods since we cut over to the new node pool:\n\n```\n$ kubectl logs otel-collector-7c9f8d4b6-2xk4v --previous\n2026-07-29T18:02:11.884Z\tinfo\tservice/telemetry.go:84\tSetting up own telemetry...\n2026-07-29T18:02:11.891Z\tinfo\texporter@v0.108.0/exporter.go:275\tDeprecated component. Will be removed in future releases.\n2026-07-29T18:02:11.902Z\terror\tservice/collector.go:112\tfailed to build pipelines\t{\"error\": \"failed to create \\\"otlp\\\" exporter: rpc error: code = Unavailable desc = connection error: desc = \\\"transport: Error while dialing: dial tcp 10.4.19.22:4317: i/o timeout\\\"\"}\nError: cannot start pipelines: failed to build pipelines\n2026/07/29 18:02:11 collector server run finished with error\n```\n\n```\n$ kubectl get events --field-selector involvedObject.name=otel-collector-7c9f8d4b6-2xk4v\n2m Warning BackOff Back-off restarting failed container collector\n```\n\nthe gateway it's dialing is up, i can curl it from a debug pod in the same namespace. netpol looks unchanged","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} {"prompt":"empty state for the saved-searches list — illustration slot, headline, one sentence, primary button. also write the copy, i'm bad at that","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} -{"prompt":"we keep going in circles on whether auth belongs in the gateway or in each service. write both options up properly with tradeoffs and then pick one and defend it","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"fix the off by one in `windowSlice` — it's dropping the last element when step divides len exactly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"doc comments on the public surface of the KeenSync swift package. every public type and method, DocC style, with a code sample on the two entry points","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"S3 multipart upload service: presign the parts, client uploads direct, we assemble on complete, abort incompletes older than 24h with a lifecycle rule + a reconciler for the db rows","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"thoughts?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"virtualized data table in react — 50k rows, sticky header, column resize, row selection with shift-click ranges. no ag-grid, we don't want the license","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"replace our homegrown logger with slog everywhere. keep the same fields on the output so the datadog parsers don't break","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"regression: search returns nothing for two-word queries since we shipped the analyzer change. single words fine. phrases in quotes fine. bare two words -> zero hits","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"milestones for automating SOC2 evidence collection before the october audit","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"we keep going in circles on whether auth belongs in the gateway or in each service. write both options up properly with tradeoffs and then pick one and defend it","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"fix the off by one in `windowSlice` — it's dropping the last element when step divides len exactly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"doc comments on the public surface of the KeenSync swift package. every public type and method, DocC style, with a code sample on the two entry points","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"S3 multipart upload service: presign the parts, client uploads direct, we assemble on complete, abort incompletes older than 24h with a lifecycle rule + a reconciler for the db rows","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"virtualized data table in react — 50k rows, sticky header, column resize, row selection with shift-click ranges. no ag-grid, we don't want the license","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"replace our homegrown logger with slog everywhere. keep the same fields on the output so the datadog parsers don't break","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"regression: search returns nothing for two-word queries since we shipped the analyzer change. single words fine. phrases in quotes fine. bare two words -> zero hits","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"milestones for automating SOC2 evidence collection before the october audit","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"add cdn.plumbline.dev to the allowed CORS origins","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"idempotency keys on POST /payments — 24h window, same key + same body returns the cached response, same key + different body is a 422","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"CONTRIBUTING.md. we use conventional commits, pnpm, changesets, and PRs need one approval + green CI. also mention the dev container","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"review this diff before i push:\n\n```diff\n--- a/internal/session/store.go\n+++ b/internal/session/store.go\n@@ -41,17 +41,22 @@ func (s *Store) Get(ctx context.Context, id string) (*Session, error) {\n-\ts.mu.RLock()\n-\tdefer s.mu.RUnlock()\n-\tsess, ok := s.cache[id]\n-\tif ok && !sess.Expired(time.Now()) {\n-\t\treturn sess, nil\n-\t}\n+\tif sess, ok := s.cache[id]; ok && !sess.Expired(time.Now()) {\n+\t\treturn sess, nil\n+\t}\n+\ts.mu.Lock()\n+\tdefer s.mu.Unlock()\n \trow := s.db.QueryRowContext(ctx, getSessionSQL, id)\n \tvar sess Session\n \tif err := row.Scan(&sess.ID, &sess.UserID, &sess.ExpiresAt); err != nil {\n \t\treturn nil, err\n \t}\n \ts.cache[id] = &sess\n \treturn &sess, nil\n }\n```\n\nthe point was to avoid taking the lock on the hot path","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} -{"prompt":"HUD for the arena mode — health bar top left, ammo bottom right, killfeed that stacks up to 5 entries and fades. unity, ui toolkit","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"port the completion-handler network layer in Networking/ to Swift Concurrency. behavior identical, tests should pass untouched","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} +{"prompt":"HUD for the arena mode — health bar top left, ammo bottom right, killfeed that stacks up to 5 entries and fades. unity, ui toolkit","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"port the completion-handler network layer in Networking/ to Swift Concurrency. behavior identical, tests should pass untouched","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"phased rollout plan for the new ranking model behind the `ranker_v3` flag — 1% internal, then 5%, guardrail metrics at each step and the abort criteria","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"grpc server-streaming endpoint for tail-ing build logs, with a resume token so a reconnecting client doesn't re-read from the top","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"eslintrc still uses `ecmaFeatures.jsx`, that's been deprecated forever, update it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.15,"slice":"core","lang":"en"} +{"prompt":"eslintrc still uses `ecmaFeatures.jsx`, that's been deprecated forever, update it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"is this migration backwards compatible with the currently deployed api? we do rolling deploys so old and new run together for ~4 minutes","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"internal announcement for the v1 API deprecation. going to #eng and #customer-success, so two versions, one technical one not","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"picking the payment-flow bug back up. card declines show the generic \"something went wrong\" instead of the issuer message, but only for 3DS cards. i traced it as far as the webhook handler and got lost","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"swipe actions on the inbox rows — archive on left swipe, delete needs a confirm on full swipe. iOS 18+, swiftui","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} +{"prompt":"internal announcement for the v1 API deprecation. going to #eng and #customer-success, so two versions, one technical one not","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"picking the payment-flow bug back up. card declines show the generic \"something went wrong\" instead of the issuer message, but only for 3DS cards. i traced it as far as the webhook handler and got lost","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"swipe actions on the inbox rows — archive on left swipe, delete needs a confirm on full swipe. iOS 18+, swiftui","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"consolidate config loading. right now we read env in 6 places with different defaults. one Config struct, parsed once at startup, injected","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"feature flag evaluation service — rules on user attrs, percentage rollouts with sticky bucketing by user id, sdk polls a snapshot every 30s and falls back to last known on failure","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"just fix it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"changelog entry for the flag-cache change plus bump the package version to 0.9.3","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.25,"slice":"mixed","lang":"en"} +{"prompt":"changelog entry for the flag-cache change plus bump the package version to 0.9.3","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.2,"slice":"mixed","lang":"en"} {"prompt":"ANR reports on the Play console, all in `HomeViewModel.observeFeed`. 0.4% of sessions, mostly older Samsungs. attaching nothing useful because the traces are all Binder frames","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"modularization plan for the android app. one gradle module now, 90s incremental builds. want a target structure and the order to carve things out in without a big-bang refactor","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"wire up the theme switcher to persist in localStorage and not flash white on reload","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"here's the TODO block i left at the top of ingest/normalize.py, work through it:\n\n```python\n# TODO(marla, 2026-04): cleanup pass, none of this changes behavior\n# - _coerce_ts, _coerce_ts2 and parse_when are all doing the same thing\n# with different fallbacks. pick one, keep the union of the formats.\n# - the vendor branches (lines 210-410) are copy-paste x5. table drive it.\n# - NormalizeError vs BadRecord vs ValueError raised interchangeably.\n# one error type, with a `field` and `reason`.\n# - `_ctx` dict threaded through 9 functions. make it a dataclass.\n# - drop the py3.8 compat shims at the bottom, we're on 3.12 everywhere\n```\n\ntests in tests/test_normalize.py should stay green as-is","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"explain what happens when two clients call `acquireLease` at the same millisecond in the etcd path. is the fencing token actually monotonic there","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"sqlite FTS5 search in the notes CLI — index title and body, prefix matching, snippet with highlights in the terminal output","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} +{"prompt":"wire up the theme switcher to persist in localStorage and not flash white on reload","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"here's the TODO block i left at the top of ingest/normalize.py, work through it:\n\n```python\n# TODO(marla, 2026-04): cleanup pass, none of this changes behavior\n# - _coerce_ts, _coerce_ts2 and parse_when are all doing the same thing\n# with different fallbacks. pick one, keep the union of the formats.\n# - the vendor branches (lines 210-410) are copy-paste x5. table drive it.\n# - NormalizeError vs BadRecord vs ValueError raised interchangeably.\n# one error type, with a `field` and `reason`.\n# - `_ctx` dict threaded through 9 functions. make it a dataclass.\n# - drop the py3.8 compat shims at the bottom, we're on 3.12 everywhere\n```\n\ntests in tests/test_normalize.py should stay green as-is","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"explain what happens when two clients call `acquireLease` at the same millisecond in the etcd path. is the fencing token actually monotonic there","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"sqlite FTS5 search in the notes CLI — index title and body, prefix matching, snippet with highlights in the terminal output","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"the date on the export filename is coming out as 2026-30-07. format string's wrong somewhere in exporters/csv.ts","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"docstrings für alle public functions in analytics/cohorts.py, numpy style, mit den units bei den return values. code bleibt wie er ist","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"de"} +{"prompt":"docstrings für alle public functions in analytics/cohorts.py, numpy style, mit den units bei den return values. code bleibt wie er ist","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"de"} {"prompt":"print stylesheet for the invoice view. hide the nav and the action bar, black on white, page breaks between line item groups","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"we're about to delete packages/legacy-charts. check nothing still imports it, including the docs site and the two example apps, and tell me what breaks","purpose":"review","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} +{"prompt":"we're about to delete packages/legacy-charts. check nothing still imports it, including the docs site and the two example apps, and tell me what breaks","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"design the feature store for the churn models — offline in bigquery, online in dynamo, point-in-time correctness for training, and a story for backfilling a new feature","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"nil check around `resp.Body` in the health prober, it panics when the server closes early","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"i2c driver for the BME280 on the nrf52840 — burst read the calibration block once, then compensated temp/pressure/humidity, blocking api is fine for now","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"pull the shared request/response types out of apps/api and apps/web into a packages/contracts workspace so they stop drifting","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"summarize this thread into something i can paste in the design doc:\n\n```\nDana 10:02\nok so the crux is whether the plan change takes effect immediately or at period end\nRui 10:03\nstripe does it immediately with proration by default\nRui 10:03\nbut our invoices are generated by our own job, not stripe's, so the proration lines have to come from us\nDana 10:05\nright. and finance wants the credit to show as a separate line, not folded into the next charge\nJo 10:07\nheads up we also have the annual->monthly downgrade case, legal said no refunds so that one has to be at period end\nDana 10:08\nso: upgrades immediate w/ proration credit line, downgrades deferred to period end. monthly<->monthly?\nRui 10:09\nimmediate both ways for monthly, the amounts are small\nJo 10:11\nand the seat count changes are always immediate, that's already shipped\nDana 10:12\nagreed. someone write this down before we forget it again\n```","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"pasted-context","lang":"en"} -{"prompt":"frame time spikes to 40ms every couple of seconds in the forest level. profiler points at GC. i'd bet allocations in the projectile pool but i can't see where","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} +{"prompt":"pull the shared request/response types out of apps/api and apps/web into a packages/contracts workspace so they stop drifting","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"summarize this thread into something i can paste in the design doc:\n\n```\nDana 10:02\nok so the crux is whether the plan change takes effect immediately or at period end\nRui 10:03\nstripe does it immediately with proration by default\nRui 10:03\nbut our invoices are generated by our own job, not stripe's, so the proration lines have to come from us\nDana 10:05\nright. and finance wants the credit to show as a separate line, not folded into the next charge\nJo 10:07\nheads up we also have the annual->monthly downgrade case, legal said no refunds so that one has to be at period end\nDana 10:08\nso: upgrades immediate w/ proration credit line, downgrades deferred to period end. monthly<->monthly?\nRui 10:09\nimmediate both ways for monthly, the amounts are small\nJo 10:11\nand the seat count changes are always immediate, that's already shipped\nDana 10:12\nagreed. someone write this down before we forget it again\n```","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"pasted-context","lang":"en"} +{"prompt":"frame time spikes to 40ms every couple of seconds in the forest level. profiler points at GC. i'd bet allocations in the projectile pool but i can't see where","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"onboarding carousel, 4 slides, dots, skip in the corner, swipe or tap-through, and it remembers if you've seen it","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"rate my api design before i build it: POST /batches to create, PUT /batches/{id}/items to add, POST /batches/{id}/commit to run. is the commit-as-POST thing going to bite me","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"rate my api design before i build it: POST /batches to create, PUT /batches/{id}/items to add, POST /batches/{id}/commit to run. is the commit-as-POST thing going to bite me","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"go.mod says 1.21, bump to 1.23 and update the CI matrix to match","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"training data loader for the tabular churn model. parquet on gcs, shuffle buffer, handles the class imbalance by weighting not resampling, deterministic given a seed","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"sticky first column AND sticky header on the comparison table without breaking the horizontal scroll shadow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"how do we test the whole payment flow end to end without hitting stripe for real. i want a strategy, not code yet — fixtures vs their test mode vs a fake we own","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} +{"prompt":"training data loader for the tabular churn model. parquet on gcs, shuffle buffer, handles the class imbalance by weighting not resampling, deterministic given a seed","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"sticky first column AND sticky header on the comparison table without breaking the horizontal scroll shadow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"how do we test the whole payment flow end to end without hitting stripe for real. i want a strategy, not code yet — fixtures vs their test mode vs a fake we own","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"unify the error types in the crate. right now there's ParseError, IoError and a `String` variant in three enums that all get boxed into anyhow at the boundary. one thiserror enum please","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"what's the blast radius if we turn on `strict_tenant_isolation` in prod? which code paths read it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"写一下 packages/queue 的 README，说明重试策略、死信队列怎么处理、还有本地怎么起 worker","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"zh"} -{"prompt":"504s from the /reports endpoint about 2% of the time, always the same customer, always around :00. their dataset isn't the biggest one either","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} +{"prompt":"what's the blast radius if we turn on `strict_tenant_isolation` in prod? which code paths read it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"写一下 packages/queue 的 README，说明重试策略、死信队列怎么处理、还有本地怎么起 worker","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"zh"} +{"prompt":"504s from the /reports endpoint about 2% of the time, always the same customer, always around :00. their dataset isn't the biggest one either","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"menu bar app UI for the timer — popover with the current task, start/stop, and today's total. keep it native looking, no electron vibes","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"vapor route POST /v1/devices/register — validates the APNs token, upserts by (user, token), returns 200 on repeat instead of a dup error","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"collapse the two nearly identical endpoints /search and /search/advanced into one. the advanced one is a superset, so keep both routes working but one handler","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"ADR for the decision we already made to use outbox-pattern instead of 2pc between orders and inventory. context, decision, consequences, the usual shape","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"vapor route POST /v1/devices/register — validates the APNs token, upserts by (user, token), returns 200 on repeat instead of a dup error","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"collapse the two nearly identical endpoints /search and /search/advanced into one. the advanced one is a superset, so keep both routes working but one handler","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"ADR for the decision we already made to use outbox-pattern instead of 2pc between orders and inventory. context, decision, consequences, the usual shape","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"review the auth flow in services/identity and then just go ahead and patch the small stuff you find — missing constant-time compares, that sort of thing","purpose":"review","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"increase the pgbouncer default_pool_size to 40","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"the marketing page hero shifts down ~40px right after fonts load. CLS is 0.19 in the field data. web fonts are self hosted with font-display swap already","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"dead code sweep in web/src — anything not reachable from the router or the two entry points. list it first then delete","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"implement the outbox publisher and document the message envelope in docs/events.md while you're in there","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"what does the `--reconcile-window` flag actually change at runtime, the help text is one line and useless","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"chart component: grouped bars, up to 6 series, legend toggles series on click, tooltip follows the nearest bar. recharts is already in the bundle","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"migration strategy off redux-toolkit onto zustand for the web app, incrementally, both coexisting for a while. which slices go first and how do we keep devtools working","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"jest is unhappy, no idea why, this passed yesterday:\n\n```\n FAIL src/hooks/useDebouncedQuery.test.tsx\n ● useDebouncedQuery › cancels the in-flight request when the term changes\n\n expect(jest.fn()).toHaveBeenCalledTimes(1)\n\n Expected number of calls: 1\n Received number of calls: 2\n\n 42 | await act(() => jest.advanceTimersByTimeAsync(300))\n 43 |\n > 44 | expect(abortSpy).toHaveBeenCalledTimes(1)\n | ^\n 45 | expect(fetchMock).toHaveBeenCalledWith('/api/search?q=heron')\n\n at Object. (src/hooks/useDebouncedQuery.test.tsx:44:22)\n\n ● useDebouncedQuery › does not fire for terms under 2 chars\n\n Exceeded timeout of 5000 ms for a test.\n\n Test Suites: 1 failed, 23 passed, 24 total\n Tests: 2 failed, 118 passed, 120 total\n```\n\nonly thing that changed in the repo is a react 19.2 bump","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"the marketing page hero shifts down ~40px right after fonts load. CLS is 0.19 in the field data. web fonts are self hosted with font-display swap already","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"dead code sweep in web/src — anything not reachable from the router or the two entry points. list it first then delete","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"implement the outbox publisher and document the message envelope in docs/events.md while you're in there","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"what does the `--reconcile-window` flag actually change at runtime, the help text is one line and useless","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"chart component: grouped bars, up to 6 series, legend toggles series on click, tooltip follows the nearest bar. recharts is already in the bundle","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"migration strategy off redux-toolkit onto zustand for the web app, incrementally, both coexisting for a while. which slices go first and how do we keep devtools working","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"jest is unhappy, no idea why, this passed yesterday:\n\n```\n FAIL src/hooks/useDebouncedQuery.test.tsx\n ● useDebouncedQuery › cancels the in-flight request when the term changes\n\n expect(jest.fn()).toHaveBeenCalledTimes(1)\n\n Expected number of calls: 1\n Received number of calls: 2\n\n 42 | await act(() => jest.advanceTimersByTimeAsync(300))\n 43 |\n > 44 | expect(abortSpy).toHaveBeenCalledTimes(1)\n | ^\n 45 | expect(fetchMock).toHaveBeenCalledWith('/api/search?q=heron')\n\n at Object. (src/hooks/useDebouncedQuery.test.tsx:44:22)\n\n ● useDebouncedQuery › does not fire for terms under 2 chars\n\n Exceeded timeout of 5000 ms for a test.\n\n Test Suites: 1 failed, 23 passed, 24 total\n Tests: 2 failed, 118 passed, 120 total\n```\n\nonly thing that changed in the repo is a react 19.2 bump","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} {"prompt":"onboarding doc for new backend devs — how to get the stack up, the three services that matter, where the seeds are, and the gotcha about the local cert","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"db trigger + audit table so every update to `contracts` records old/new jsonb, who, and when. postgres 16","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} +{"prompt":"db trigger + audit table so every update to `contracts` records old/new jsonb, who, and when. postgres 16","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"spring boot batch job, reads the nightly bank file from sftp, matches transactions, writes exceptions to a report table. restartable from the last committed chunk","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"swap the spinner on the deploy button for an inline progress bar with the step name","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"least risky order for these three: 1) react 19 upgrade 2) webpack -> vite 3) carve the design system into its own package. three weeks before the a11y audit and i'd rather not be mid-migration during it","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} +{"prompt":"swap the spinner on the deploy button for an inline progress bar with the step name","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"least risky order for these three: 1) react 19 upgrade 2) webpack -> vite 3) carve the design system into its own package. three weeks before the a11y audit and i'd rather not be mid-migration during it","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"dependabot opened this and i just want it dealt with:\n\n```\nBumps tar-fs from 2.1.1 to 2.1.2\n\n GHSA-pq67-2wwv-3xjx — Link Following and Path Traversal in tar-fs\n Severity: High (7.5)\n Patched versions: >=2.1.2, >=3.0.7\n\n Dependency path:\n my-app > @cloudflare/wrangler > tar-fs\n\n 1 vulnerability found in package-lock.json\n```\n\nit's a transitive dep of a devDependency so nothing ships, but CI's red and i want it green","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"pasted-context","lang":"en"} -{"prompt":"explique-moi comment fonctionne le cache de permissions dans authz/resolver.go, notamment quand est-ce qu'il est invalidé après un changement de rôle","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"fr"} -{"prompt":"move the tests next to the code they test. currently everything's in a top level tests/ mirror and it's a pain to navigate. update the pytest config too","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"spring animation on the card when it enters — subtle, no bounce past the target, and it should respect reduce-motion","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} +{"prompt":"explique-moi comment fonctionne le cache de permissions dans authz/resolver.go, notamment quand est-ce qu'il est invalidé après un changement de rôle","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"fr"} +{"prompt":"move the tests next to the code they test. currently everything's in a top level tests/ mirror and it's a pain to navigate. update the pytest config too","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"spring animation on the card when it enters — subtle, no bounce past the target, and it should respect reduce-motion","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"docker build passes but the container exits immediately in prod and there's nothing in the logs. works with docker run locally. same image digest","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"write it up","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"introduce a repository interface between the handlers and sqlx so we can fake the db in tests. no query changes, just the seam","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"check the Dockerfile against current best practice — multistage, non-root, layer caching, and whether we're shipping the build toolchain to prod","purpose":"review","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"the openapi spec has these paths stubbed with descriptions but no implementation. build them:\n\n```yaml\n /v1/exports:\n post:\n summary: Request an export\n requestBody:\n content:\n application/json:\n schema:\n type: object\n required: [dataset, format]\n properties:\n dataset: { type: string, enum: [contacts, deals, activity] }\n format: { type: string, enum: [csv, jsonl, parquet] }\n since: { type: string, format: date-time }\n responses:\n '202': { description: Accepted, returns export id and status url }\n '429': { description: One export at a time per workspace }\n /v1/exports/{id}:\n get:\n responses:\n '200': { description: status pending|running|done|failed, plus download url when done }\n '404': { description: Unknown or expired }\n```\n\nfastapi, the download url should be a presigned r2 link good for 1h","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"check the Dockerfile against current best practice — multistage, non-root, layer caching, and whether we're shipping the build toolchain to prod","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the openapi spec has these paths stubbed with descriptions but no implementation. build them:\n\n```yaml\n /v1/exports:\n post:\n summary: Request an export\n requestBody:\n content:\n application/json:\n schema:\n type: object\n required: [dataset, format]\n properties:\n dataset: { type: string, enum: [contacts, deals, activity] }\n format: { type: string, enum: [csv, jsonl, parquet] }\n since: { type: string, format: date-time }\n responses:\n '202': { description: Accepted, returns export id and status url }\n '429': { description: One export at a time per workspace }\n /v1/exports/{id}:\n get:\n responses:\n '200': { description: status pending|running|done|failed, plus download url when done }\n '404': { description: Unknown or expired }\n```\n\nfastapi, the download url should be a presigned r2 link good for 1h","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"tidy the css into modules per component, we have one 4000 line app.css and specificity wars every time someone touches it. visual output should be pixel identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"summarize what changed between v1.8.0 and v1.9.0 for the customer-facing notes. git log is noisy, filter out the chores","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"segfault on the STM32 build after about 6 hours of uptime, always in the sensor task. stack is only 2k so i suspect overflow but the guard pattern is intact","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} +{"prompt":"summarize what changed between v1.8.0 and v1.9.0 for the customer-facing notes. git log is noisy, filter out the chores","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"segfault on the STM32 build after about 6 hours of uptime, always in the sensor task. stack is only 2k so i suspect overflow but the guard pattern is intact","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"responsive grid for the pricing cards — 1 col mobile, 2 tablet, 4 desktop, the \"popular\" one taller and centered on mobile. tailwind","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"does the ingest path handle backpressure at all? if kafka slows down does the http handler block or do we drop","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"fix the broken \"Docs\" link in the footer, it 404s, should point to /docs/latest","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"core","lang":"en"} -{"prompt":"plan the move to per-tenant schemas and then get the first migration + the tenant resolver landed so we have something to look at","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.85,"slice":"mixed","lang":"en"} -{"prompt":"our error copy is a mess. do a pass over all user-facing strings in src/errors/messages.ts — plain language, say what to do next, no \"an error occurred\"","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"ci is green on my machine and red on github. gradle:\n\n```\n> Task :app:kaptGenerateStubsDebugKotlin FAILED\ne: /home/runner/work/vellum/vellum/app/src/main/java/dev/vellum/di/AppModule.kt:31:5 [Dagger/MissingBinding] dev.vellum.sync.SyncScheduler cannot be provided without an @Provides-annotated method.\n\n dev.vellum.sync.SyncScheduler is requested at\n dev.vellum.di.AppComponent.syncScheduler()\n\nFAILURE: Build failed with an exception.\n* What went wrong:\nExecution failed for task ':app:kaptGenerateStubsDebugKotlin'.\n> A failure occurred while executing org.jetbrains.kotlin.gradle.internal.KaptExecution\n > Process 'Gradle Worker Daemon 3' finished with non-zero exit value 1\n\n* Try:\n> Run with --stacktrace option to get the stack trace.\n\nBUILD FAILED in 3m 41s\n```\n\nSyncScheduler has an @Inject constructor. it builds fine locally with the same gradle version","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.65,"slice":"pasted-context","lang":"en"} -{"prompt":"rename the `tenant_id` column to `workspace_id` across the schema, models, queries and the two views. behavior stays the same, it's a naming cleanup we agreed on months ago","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} +{"prompt":"does the ingest path handle backpressure at all? if kafka slows down does the http handler block or do we drop","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"fix the broken \"Docs\" link in the footer, it 404s, should point to /docs/latest","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"plan the move to per-tenant schemas and then get the first migration + the tenant resolver landed so we have something to look at","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"our error copy is a mess. do a pass over all user-facing strings in src/errors/messages.ts — plain language, say what to do next, no \"an error occurred\"","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"ci is green on my machine and red on github. gradle:\n\n```\n> Task :app:kaptGenerateStubsDebugKotlin FAILED\ne: /home/runner/work/vellum/vellum/app/src/main/java/dev/vellum/di/AppModule.kt:31:5 [Dagger/MissingBinding] dev.vellum.sync.SyncScheduler cannot be provided without an @Provides-annotated method.\n\n dev.vellum.sync.SyncScheduler is requested at\n dev.vellum.di.AppComponent.syncScheduler()\n\nFAILURE: Build failed with an exception.\n* What went wrong:\nExecution failed for task ':app:kaptGenerateStubsDebugKotlin'.\n> A failure occurred while executing org.jetbrains.kotlin.gradle.internal.KaptExecution\n > Process 'Gradle Worker Daemon 3' finished with non-zero exit value 1\n\n* Try:\n> Run with --stacktrace option to get the stack trace.\n\nBUILD FAILED in 3m 41s\n```\n\nSyncScheduler has an @Inject constructor. it builds fine locally with the same gradle version","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"rename the `tenant_id` column to `workspace_id` across the schema, models, queries and the two views. behavior stays the same, it's a naming cleanup we agreed on months ago","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"dead simple: hook the search input up to the existing /api/search endpoint with 250ms debounce and show the results in the dropdown we already have","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"postmortem doc for the july 14 outage. i have the timeline in my notes, need it in the standard format with contributing factors and action items","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"is the retry logic in sync/uploader.ts safe if two tabs run it at once? there's a shared indexeddb queue","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the count in the header says 12 but the list shows 11 items. one of them is soft deleted i think","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"s'il te plaît ajoute un endpoint GET /v1/webhooks/{id}/deliveries avec pagination par curseur, et le filtre status=failed","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"fr"} -{"prompt":"QA filed these against the settings redesign, all layout, want them all handled:\n\n```\nBUG-4412 Long workspace names overflow the breadcrumb instead of truncating (repro: 60 char name)\nBUG-4413 \"Danger zone\" section has 48px top margin on desktop, 8px on mobile — looks unintentional\nBUG-4415 Toggle labels wrap to two lines at 375px width and the row height doesn't grow, text clips\nBUG-4416 Save bar overlaps the last form field when the keyboard is up on iOS safari\nBUG-4419 Avatar upload dropzone loses its dashed border on drag-over (should highlight, not vanish)\nBUG-4421 Tab underline animates from the wrong side when you jump from tab 1 to tab 3\n```\n\nfigma is unchanged, these are all implementation drift","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} -{"prompt":"swap `==` for `===` in utils/compare.js, there are like four spots","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.15,"slice":"boundary","lang":"en"} -{"prompt":"decouple the email sending from OrderService. it shouldn't know about templates or smtp — events out, a subscriber does the sending","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} +{"prompt":"postmortem doc for the july 14 outage. i have the timeline in my notes, need it in the standard format with contributing factors and action items","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"is the retry logic in sync/uploader.ts safe if two tabs run it at once? there's a shared indexeddb queue","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the count in the header says 12 but the list shows 11 items. one of them is soft deleted i think","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"s'il te plaît ajoute un endpoint GET /v1/webhooks/{id}/deliveries avec pagination par curseur, et le filtre status=failed","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"fr"} +{"prompt":"QA filed these against the settings redesign, all layout, want them all handled:\n\n```\nBUG-4412 Long workspace names overflow the breadcrumb instead of truncating (repro: 60 char name)\nBUG-4413 \"Danger zone\" section has 48px top margin on desktop, 8px on mobile — looks unintentional\nBUG-4415 Toggle labels wrap to two lines at 375px width and the row height doesn't grow, text clips\nBUG-4416 Save bar overlaps the last form field when the keyboard is up on iOS safari\nBUG-4419 Avatar upload dropzone loses its dashed border on drag-over (should highlight, not vanish)\nBUG-4421 Tab underline animates from the wrong side when you jump from tab 1 to tab 3\n```\n\nfigma is unchanged, these are all implementation drift","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"swap `==` for `===` in utils/compare.js, there are like four spots","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"decouple the email sending from OrderService. it shouldn't know about templates or smtp — events out, a subscriber does the sending","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"blog post about the 8x speedup we got on the tile renderer. technical audience, include the flamegraph before/after and the one trick that actually mattered","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"cursor keeps jumping to the end of the input when i type in the middle. controlled component, value comes from a reducer","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"GitHub Actions workflow that builds the multi-arch image, signs it with cosign, pushes to ghcr, and only deploys on tags matching v*","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"cursor keeps jumping to the end of the input when i type in the middle. controlled component, value comes from a reducer","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"GitHub Actions workflow that builds the multi-arch image, signs it with cosign, pushes to ghcr, and only deploys on tags matching v*","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"give the modal a proper redesign — bigger, two column on desktop — and while you're in there pull the form field boilerplate into a shared hook, it's duplicated in five modals","purpose":"frontendImpl","secondary":"refactor","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"der cronjob läuft doppelt seit dem deploy gestern. zwei pods, jeder feuert. leader election ist eingebaut aber offenbar greift sie nicht","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"de"} +{"prompt":"der cronjob läuft doppelt seit dem deploy gestern. zwei pods, jeder feuert. leader election ist eingebaut aber offenbar greift sie nicht","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} {"prompt":"explain the state machine in booking/reducer.ts to me like i'm new. which transitions are legal and where's the one that lets you get stuck","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"extract the vendor-specific bits of the payout code behind an interface so adding wise next quarter isn't another if-else. no behavior change today","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"extract the vendor-specific bits of the payout code behind an interface so adding wise next quarter isn't another if-else. no behavior change today","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"quiero un plan por fases para meter observabilidad de verdad: traces en los 6 servicios, métricas RED, y logs correlacionados. presupuesto ajustado así que dime qué hacemos primero","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"es"} -{"prompt":"add `engines: { node: \">=22\" }` to package.json","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"core","lang":"en"} -{"prompt":"pipeline is emitting duplicate rows in the daily fact table, roughly 0.3% of records, started three days ago. upstream swears nothing changed. dbt incremental with a merge on a surrogate key","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"test coverage on the billing module is 41%. tell me which uncovered paths actually matter and which are noise, don't write tests yet","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"the view doesn't update when the model changes. @Observable on the class, the property is a plain var, list is bound to it. worked before i moved it into a child view","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"netcode approach for an 8 player lobby, fast paced, shooting. rollback vs lockstep vs server authoritative with client prediction — argue it out and recommend one for our scale","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"changelog: \"Fixed an issue where exports over 10MB failed silently\"","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.15,"slice":"core","lang":"en"} -{"prompt":"env var in the Dockerfile is spelled DATABSE_URL, fix it and check nothing else references the typo'd name","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.15,"slice":"core","lang":"en"} -{"prompt":"background job that reconciles our subscription state against stripe nightly and reports drift. read only, no mutations, output to a slack channel","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"このPRのdiffを見て、ロック順序が逆になっていないか確認してほしい。デッドロックの可能性が気になってる","purpose":"review","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"ja"} +{"prompt":"add `engines: { node: \">=22\" }` to package.json","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"pipeline is emitting duplicate rows in the daily fact table, roughly 0.3% of records, started three days ago. upstream swears nothing changed. dbt incremental with a merge on a surrogate key","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"test coverage on the billing module is 41%. tell me which uncovered paths actually matter and which are noise, don't write tests yet","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the view doesn't update when the model changes. @Observable on the class, the property is a plain var, list is bound to it. worked before i moved it into a child view","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"netcode approach for an 8 player lobby, fast paced, shooting. rollback vs lockstep vs server authoritative with client prediction — argue it out and recommend one for our scale","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"changelog: \"Fixed an issue where exports over 10MB failed silently\"","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"env var in the Dockerfile is spelled DATABSE_URL, fix it and check nothing else references the typo'd name","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"background job that reconciles our subscription state against stripe nightly and reports drift. read only, no mutations, output to a slack channel","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"このPRのdiffを見て、ロック順序が逆になっていないか確認してほしい。デッドロックの可能性が気になってる","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"} {"prompt":"loading state for the feed — the cards should reserve their final height so nothing jumps when data lands","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"same rename job as the last one but for the mobile repo: `Workspace` -> `Team` in models, api client, strings, and the two xcstrings files. behavior identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"same rename job as the last one but for the mobile repo: `Workspace` -> `Team` in models, api client, strings, and the two xcstrings files. behavior identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"figure out why the auth callback 500s for google-workspace accounts but not gmail ones, and then add a note in the auth docs about whatever the gotcha turns out to be","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"quick one — the pluralization on \"1 items selected\"","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"quick one — the pluralization on \"1 items selected\"","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} {"prompt":"prometheus exporter for the queue depths, one gauge per queue with a `queue` label, plus a histogram for job duration. wire it into the existing /metrics handler","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the thing from yesterday","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"design a rate-limit-aware sync scheduler for the desktop client. it has to be polite to our api, catch up fast after being offline for a week, and not thundering-herd us at 9am when everyone opens their laptop","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"hover state on the table rows is barely visible in dark mode, bump the contrast a notch","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.15,"slice":"boundary","lang":"en"} -{"prompt":"walk the whole request lifecycle for a POST /v1/orders from the edge worker down to the db commit and tell me every place a partial failure can leave state inconsistent","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"design a rate-limit-aware sync scheduler for the desktop client. it has to be polite to our api, catch up fast after being offline for a week, and not thundering-herd us at 9am when everyone opens their laptop","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"hover state on the table rows is barely visible in dark mode, bump the contrast a notch","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"walk the whole request lifecycle for a POST /v1/orders from the edge worker down to the db commit and tell me every place a partial failure can leave state inconsistent","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"keyboard shortcut overlay, cmd+/ toggles it, grouped by section, and it should list the shortcuts from the same registry the handlers use so it can't drift","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"sed-able? probably not. `getUserById` is called from 60-odd places and half of them then immediately map to a DTO. i want a `getUserDTO` and the call sites cleaned up, but the wire output must be byte identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"openapi descriptions are all empty strings. fill them in for every path, param and schema field in api/openapi.yaml — accurate prose, don't invent behavior, read the handlers","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"connections to the pooler drop every ~5 min under load, clients see \"server closed the connection unexpectedly\". pooler logs show nothing at that timestamp, tcp keepalives are on","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"sed-able? probably not. `getUserById` is called from 60-odd places and half of them then immediately map to a DTO. i want a `getUserDTO` and the call sites cleaned up, but the wire output must be byte identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"openapi descriptions are all empty strings. fill them in for every path, param and schema field in api/openapi.yaml — accurate prose, don't invent behavior, read the handlers","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"connections to the pooler drop every ~5 min under load, clients see \"server closed the connection unexpectedly\". pooler logs show nothing at that timestamp, tcp keepalives are on","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"spec out how we'd support self-hosted installs. licensing, telemetry that's opt-in, how upgrades work without our control plane, what we refuse to support. write it as a doc for the leadership review","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"cache the compiled templates. right now we parse on every render and it shows in the p99","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.45,"slice":"boundary","lang":"en"} -{"prompt":"review this for me and write up a short summary the rest of the team can read — packages/scheduler, specifically whether the priority queue is fair or if low-priority jobs can starve forever","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"pull the magic numbers in the physics step into named constants at the top. don't change any values","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"make the empty dashboard less depressing","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"cli tool that diffs two openapi specs and exits nonzero on breaking changes. removed paths, narrowed enums, required params added, type changes. rust, and the output should be readable in a PR comment","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"update docs/deploy.md — the helm values changed names in the 3.0 chart and half the commands in there are wrong now","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"why is this useEffect running twice on mount in dev, is that strict mode or did i mess up the deps","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} +{"prompt":"cache the compiled templates. right now we parse on every render and it shows in the p99","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"review this for me and write up a short summary the rest of the team can read — packages/scheduler, specifically whether the priority queue is fair or if low-priority jobs can starve forever","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"pull the magic numbers in the physics step into named constants at the top. don't change any values","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"make the empty dashboard less depressing","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"cli tool that diffs two openapi specs and exits nonzero on breaking changes. removed paths, narrowed enums, required params added, type changes. rust, and the output should be readable in a PR comment","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"update docs/deploy.md — the helm values changed names in the 3.0 chart and half the commands in there are wrong now","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"why is this useEffect running twice on mount in dev, is that strict mode or did i mess up the deps","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"- laravel 8, php 8.0, 220k lines\n- no tests to speak of (37 of them, 12 fail)\n- half the business logic is in blade templates\n- upgrading to 11 is blocked on three abandoned packages\n\ni need a plan. what order, what we can do incrementally, and what we absolutely have to freeze while it happens","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"pull the order calculation out of the blade template into a service class, same rendered totals for every fixture we have","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"could you replace the abandoned mailer package with laravel's own mail, keeping the same templates and headers","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the app is running with APP_DEBUG=true in production","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"requests to the reports page take 30s and the query log shows 4000 queries","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"would you read through app/Http/Controllers/OrderController.php and tell me what it actually does? it's 1800 lines and i've been asked to change it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"pull the order calculation out of the blade template into a service class, same rendered totals for every fixture we have","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"could you replace the abandoned mailer package with laravel's own mail, keeping the same templates and headers","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"the app is running with APP_DEBUG=true in production","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"requests to the reports page take 30s and the query log shows 4000 queries","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"would you read through app/Http/Controllers/OrderController.php and tell me what it actually does? it's 1800 lines and i've been asked to change it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"write the architecture-as-it-is doc for this codebase — the real request flow, where business logic lives, and the landmines","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"characterization tests around the order calculation before we touch it, capturing current behavior including the weird cases","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the admin panel's tables are unusable on anything narrower than 1400px","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"our models have 40 accessors that hit the database, so a list page does n+1 by design. eager load properly, identical rendered pages","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"characterization tests around the order calculation before we touch it, capturing current behavior including the weird cases","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"the admin panel's tables are unusable on anything narrower than 1400px","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"our models have 40 accessors that hit the database, so a list page does n+1 by design. eager load properly, identical rendered pages","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} {"prompt":"plan the strangler approach for extracting the checkout out of the monolith into a service, with both live during the transition","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"the session driver is `file` on three load balanced servers with no shared storage","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the session driver is `file` on three load balanced servers with no shared storage","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"bun: edge function that validates a jwt, looks up the tenant from kv, and proxies to the right regional origin, all under 20ms","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the edge function's kv reads aren't cached so every request pays 30ms","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"edge functions work locally and fail in production with a module resolution error that mentions node built-ins","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"our shared validation library imports node:crypto which doesn't exist at the edge. make it runtime-agnostic, same validation results","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"edge functions work locally and fail in production with a module resolution error that mentions node built-ins","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"our shared validation library imports node:crypto which doesn't exist at the edge. make it runtime-agnostic, same validation results","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"map out what belongs at the edge versus the origin for us — auth, rate limits, a/b assignment, personalization — with the tradeoffs","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain how our edge function handles a cold start and what the p99 looks like as a result","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"docs for our edge middleware — what headers it sets, what it reads, and the order it runs relative to the cdn cache","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"a/b assignment at the edge with a stable cookie, and the variant exposed as a header the origin can vary on","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"edge ml: run the defect classifier on the device, int8 quantized, under 40ms on the coral tpu, with a fallback to cloud when confidence is low","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"the quantized model's accuracy dropped from 0.94 to 0.71 and i don't know which layer is the problem","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"the confidence threshold for cloud fallback is 0.5, way too low","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"inspection ui on the device's touchscreen: live camera, the detection overlay, pass/fail with a big obvious result, and a manual override","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"sounds good, go","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"here's the report from the factory floor, pasting verbatim:\n\n\"Line 3, second shift. The inspection station started passing parts it should reject at\naround 22:00. Operators noticed at 23:40 and switched to manual. About 4,000 parts went\nthrough in that window, we've quarantined them all.\n\nThe screen showed 'PASS' with a confidence of 0.99 on everything including an obviously\ncracked part we tested deliberately. Rebooting the station fixed it.\n\nThe station log around that time:\n 22:01:14 camera: frame timeout, retrying\n 22:01:14 camera: frame timeout, retrying\n 22:01:15 camera: reinitialized\n 22:01:15 infer: result=PASS conf=0.9987\n 22:01:16 infer: result=PASS conf=0.9987\n (repeats identically every ~1s for 98 minutes)\"\n\nidentical confidence to four decimal places for 98 minutes","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"detect a stuck camera — frame hash comparison and a timestamp check — and fail the station closed rather than passing everything","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the station has no watchdog on the inference loop at all","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"explain how our edge function handles a cold start and what the p99 looks like as a result","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"docs for our edge middleware — what headers it sets, what it reads, and the order it runs relative to the cdn cache","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"a/b assignment at the edge with a stable cookie, and the variant exposed as a header the origin can vary on","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"edge ml: run the defect classifier on the device, int8 quantized, under 40ms on the coral tpu, with a fallback to cloud when confidence is low","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the quantized model's accuracy dropped from 0.94 to 0.71 and i don't know which layer is the problem","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the confidence threshold for cloud fallback is 0.5, way too low","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"inspection ui on the device's touchscreen: live camera, the detection overlay, pass/fail with a big obvious result, and a manual override","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"here's the report from the factory floor, pasting verbatim:\n\n\"Line 3, second shift. The inspection station started passing parts it should reject at\naround 22:00. Operators noticed at 23:40 and switched to manual. About 4,000 parts went\nthrough in that window, we've quarantined them all.\n\nThe screen showed 'PASS' with a confidence of 0.99 on everything including an obviously\ncracked part we tested deliberately. Rebooting the station fixed it.\n\nThe station log around that time:\n 22:01:14 camera: frame timeout, retrying\n 22:01:14 camera: frame timeout, retrying\n 22:01:15 camera: reinitialized\n 22:01:15 infer: result=PASS conf=0.9987\n 22:01:16 infer: result=PASS conf=0.9987\n (repeats identically every ~1s for 98 minutes)\"\n\nidentical confidence to four decimal places for 98 minutes","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"detect a stuck camera — frame hash comparison and a timestamp check — and fail the station closed rather than passing everything","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the station has no watchdog on the inference loop at all","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"review every failure mode in the inspection station and tell me which ones fail open","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"write the incident report for the factory quality team, and the operator-facing note about what the new failure behavior looks like","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"write the incident report for the factory quality team, and the operator-facing note about what the new failure behavior looks like","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"plan the station's health monitoring — what we report to the central system, the heartbeat, and the alerts that would have caught this in 60 seconds","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"station status dashboard for the plant: stations as tiles, throughput, reject rate, and a stale-data indicator per station","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the reject rate tile shows a percentage of nothing when a station is idle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"station status dashboard for the plant: stations as tiles, throughput, reject rate, and a stale-data indicator per station","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the reject rate tile shows a percentage of nothing when a station is idle","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"our station code has the camera handling, inference and the ui in one 2000 line python file with globals. separate them behind interfaces, identical behavior on the test rig","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"model deployment to the stations: signed model bundles, staged rollout by line, and an automatic rollback if the reject rate shifts","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"the model version isn't recorded with each inspection result so we can't tell which model passed a part","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"explain how a station decides it has the right model version, and what happens if the download is interrupted","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"documentation for the model bundle format and the deployment protocol, for whoever maintains this after me","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"one line's stations disagree on the same part by about 8% of the time, same model version","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"model deployment to the stations: signed model bundles, staged rollout by line, and an automatic rollback if the reject rate shifts","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the model version isn't recorded with each inspection result so we can't tell which model passed a part","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"explain how a station decides it has the right model version, and what happens if the download is interrupted","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"documentation for the model bundle format and the deployment protocol, for whoever maintains this after me","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"one line's stations disagree on the same part by about 8% of the time, same model version","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"plan the labeling pipeline — how operators flag a misclassification, how it gets into the training set, and how we avoid poisoning it","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"operator feedback capture: a 'this was wrong' button that saves the frame, the prediction and the operator's verdict","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"labeling review tool: the flagged frames in a grid, the model's prediction, and a confirm/reject with keyboard shortcuts for speed","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"flagged frames upload at full resolution over the plant's saturated uplink","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"operator feedback capture: a 'this was wrong' button that saves the frame, the prediction and the operator's verdict","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"labeling review tool: the flagged frames in a grid, the model's prediction, and a confirm/reject with keyboard shortcuts for speed","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"flagged frames upload at full resolution over the plant's saturated uplink","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} {"prompt":"plan the retraining loop then implement the dataset assembly step","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"work out why the stations disagree and then write it up for the quality report","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"next task","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"work out why the stations disagree and then write it up for the quality report","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"i need the plan for distributed training. we're at the point where a run takes 30 hours on one 8xA100 node and we have four nodes available. data parallel with fsdp probably, but our dataloader is the bottleneck already at one node and i don't know what breaks at four. include the checkpointing and how we resume a failed run","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"fsdp setup for the training script, activation checkpointing on the transformer blocks, and mixed precision with a loss scaler that doesn't blow up","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"training run dashboard: loss curves per run, gpu utilization, throughput, and a compare-runs mode","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the learning rate in the config is 3e-4 but the code multiplies by world size, so it's 12e-4 on 4 gpus and nobody realized","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"our dataloader, the eval loader and the inference preprocessing each implement tokenization slightly differently. one path, and confirm the token ids match on a sample","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"training hangs at the start of epoch 2 on multi-node, single node is fine, and the nccl logs just stop","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"read our checkpointing and tell me whether a resumed run is genuinely equivalent to an uninterrupted one, including the dataloader state","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"write the training infrastructure doc: launching a run, the config layout, checkpoint conventions, and how to debug a hang","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"sharded dataloader that gives each rank a distinct slice, resumable mid-epoch, with no sample seen twice per epoch","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"gpu utilization is 45% and the trace shows the gpus waiting on the host","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the number of dataloader workers is 2","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"plan the experiment tracking — what we log, how we name runs, and how someone finds the run that produced a deployed model six months later","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"fsdp setup for the training script, activation checkpointing on the transformer blocks, and mixed precision with a loss scaler that doesn't blow up","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"training run dashboard: loss curves per run, gpu utilization, throughput, and a compare-runs mode","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the learning rate in the config is 3e-4 but the code multiplies by world size, so it's 12e-4 on 4 gpus and nobody realized","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"our dataloader, the eval loader and the inference preprocessing each implement tokenization slightly differently. one path, and confirm the token ids match on a sample","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"training hangs at the start of epoch 2 on multi-node, single node is fine, and the nccl logs just stop","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"read our checkpointing and tell me whether a resumed run is genuinely equivalent to an uninterrupted one, including the dataloader state","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"write the training infrastructure doc: launching a run, the config layout, checkpoint conventions, and how to debug a hang","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"sharded dataloader that gives each rank a distinct slice, resumable mid-epoch, with no sample seen twice per epoch","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"gpu utilization is 45% and the trace shows the gpus waiting on the host","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"plan the experiment tracking — what we log, how we name runs, and how someone finds the run that produced a deployed model six months later","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"run comparison view: hyperparameters diffed, metric curves overlaid, and the git sha per run","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"explain how we currently determine which code produced a checkpoint, because i suspect the answer is 'we don't'","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"model card template for our internal models: data, training setup, eval results, known failure modes, and the intended use","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"our three training entrypoints share 80% of their setup with divergent argument names. one entrypoint with subcommands, same runs reproducible from the old configs","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"eval harness that runs the standard suite on a checkpoint and writes results next to it, comparable across runs","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"eval numbers differ by 0.3% between runs on the same checkpoint","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"分散学習のジョブが 4 ノードで止まる。まず原因の切り分け方針を教えてほしい","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"ja"} -{"prompt":"sveltekit: the dashboard needs streamed data so the shell renders instantly and the slow widgets fill in","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"our load functions fetch overlapping data so a page hits the api 6 times. consolidate, same data available to the same components","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"hydration mismatch warning on the dashboard, only in production builds","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the loading spinner is centered in the viewport rather than in the widget","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"plan the migration from our stores-everywhere state to runes, incrementally, without a big bang rewrite","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"moving on then","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"explain how we currently determine which code produced a checkpoint, because i suspect the answer is 'we don't'","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"model card template for our internal models: data, training setup, eval results, known failure modes, and the intended use","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"our three training entrypoints share 80% of their setup with divergent argument names. one entrypoint with subcommands, same runs reproducible from the old configs","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"eval harness that runs the standard suite on a checkpoint and writes results next to it, comparable across runs","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"eval numbers differ by 0.3% between runs on the same checkpoint","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"分散学習のジョブが 4 ノードで止まる。まず原因の切り分け方針を教えてほしい","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"ja"} +{"prompt":"sveltekit: the dashboard needs streamed data so the shell renders instantly and the slow widgets fill in","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"our load functions fetch overlapping data so a page hits the api 6 times. consolidate, same data available to the same components","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"hydration mismatch warning on the dashboard, only in production builds","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the loading spinner is centered in the viewport rather than in the widget","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"plan the migration from our stores-everywhere state to runes, incrementally, without a big bang rewrite","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"so the php monolith's database is the real problem. 340 tables, no foreign keys anywhere (they were 'too slow' in 2016), enum columns with values the app doesn't know about, and three tables with a `data` blob holding json that different parts of the app parse differently. i want a plan to get to something sane that doesn't require stopping feature work for a year","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"add the missing foreign keys, one table at a time, with a script that finds and reports orphan rows first","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"add the missing foreign keys, one table at a time, with a script that finds and reports orphan rows first","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the orphan check script takes 40 minutes because it's doing a query per row","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"three parts of the app parse the `settings.data` json blob with different assumptions about missing keys. one accessor with explicit defaults, same effective settings for every existing row","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"some rows in the orders table reference customers that don't exist and the app renders 'Unknown' for them","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"read the schema and tell me which tables are actually unused, based on the code not the row counts","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"write the data dictionary for the 40 tables that matter, with what each column really means including the enum values that aren't in the code","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"database health page for us internally: table sizes, index usage, and the tables with no primary key","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"three parts of the app parse the `settings.data` json blob with different assumptions about missing keys. one accessor with explicit defaults, same effective settings for every existing row","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"some rows in the orders table reference customers that don't exist and the app renders 'Unknown' for them","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"read the schema and tell me which tables are actually unused, based on the code not the row counts","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"write the data dictionary for the 40 tables that matter, with what each column really means including the enum values that aren't in the code","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"database health page for us internally: table sizes, index usage, and the tables with no primary key","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"the app's migration table and the actual schema have diverged, 12 migrations recorded as run that clearly weren't","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"plan how we introduce a repository layer so the 400 places doing raw queries can be migrated gradually","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the db user the app connects as is root","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"explain how the app handles a query failure today — i've seen empty arrays returned where an exception should be","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"query timeout and error handling at the connection level so a db failure surfaces as an error not silently empty data","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"our error pages show the sql query and the stack trace to end users on 500s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"plan how we introduce a repository layer so the 400 places doing raw queries can be migrated gradually","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"the db user the app connects as is root","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"explain how the app handles a query failure today — i've seen empty arrays returned where an exception should be","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"query timeout and error handling at the connection level so a db failure surfaces as an error not silently empty data","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"our error pages show the sql query and the stack trace to end users on 500s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} {"prompt":"error page design: friendly message, a reference code, and a report-this action, no internals","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"plan the test strategy for a codebase with no tests — what we cover first, characterization vs unit, and a coverage target that isn't a lie","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"review the 12 failing tests and tell me which are testing broken behavior vs broken tests","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"testing guide for this codebase, given the constraints — how to test something that touches 6 globals","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"eso, adelante","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"es"} +{"prompt":"plan the test strategy for a codebase with no tests — what we cover first, characterization vs unit, and a coverage target that isn't a lie","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"review the 12 failing tests and tell me which are testing broken behavior vs broken tests","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"testing guide for this codebase, given the constraints — how to test something that touches 6 globals","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} {"prompt":"would you propose how we handle real-time collaboration presence at our scale? 40k concurrent users, most in rooms of 2-5 but a few in rooms of 500. currently one redis pubsub channel per room and the big rooms are melting a node. i want options with the tradeoffs and a recommendation","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"presence with batched broadcasts — coalesce updates into 200ms windows per room, and a different strategy above 50 participants","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"presence with batched broadcasts — coalesce updates into 200ms windows per room, and a different strategy above 50 participants","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"presence avatars with a +N overflow, and it shouldn't reflow the toolbar when people join and leave constantly","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"presence heartbeat is every 2 seconds per client, make it 15","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"we track presence in redis and also in an in-memory map per node, and they disagree after a node restart. one source of truth","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"one node's memory climbs steadily and only that node, and it's always the one that's been up longest","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain the fan-out cost of a presence update in a 500 person room as the code stands","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"capacity planning doc for the realtime layer: connections per node, memory per connection, and the limits we've measured","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"presence heartbeat is every 2 seconds per client, make it 15","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"we track presence in redis and also in an in-memory map per node, and they disagree after a node restart. one source of truth","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"one node's memory climbs steadily and only that node, and it's always the one that's been up longest","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain the fan-out cost of a presence update in a 500 person room as the code stands","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"capacity planning doc for the realtime layer: connections per node, memory per connection, and the limits we've measured","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} {"prompt":"connection limits per node with graceful rejection and a client that retries against a different node","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"clients rejected for capacity retry against the same node forever","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"clients rejected for capacity retry against the same node forever","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"realtime connection health widget for internal use: connections per node, message rates, and rooms over 100 participants","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the connection count metric is a gauge that only ever goes up","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the connection count metric is a gauge that only ever goes up","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"plan how we roll out a realtime deploy without disconnecting everyone at once","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"check what our client does on an unexpected disconnect — reconnect backoff, state resync, and whether it can thundering-herd us","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"client reconnection guidance for our sdk consumers: the backoff we expect, resuming state, and what we guarantee about missed events","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"check what our client does on an unexpected disconnect — reconnect backoff, state resync, and whether it can thundering-herd us","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"client reconnection guidance for our sdk consumers: the backoff we expect, resuming state, and what we guarantee about missed events","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"graceful drain on deploy: stop accepting new connections, tell existing clients to reconnect elsewhere, then exit","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"our reconnect logic is implemented separately in the web client, the ios sdk and the android sdk, with different backoff. one specified behavior, implemented consistently","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"after a deploy the reconnect storm takes 4 minutes to settle and error rates spike","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"sure, next","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"our reconnect logic is implemented separately in the web client, the ios sdk and the android sdk, with different backoff. one specified behavior, implemented consistently","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"after a deploy the reconnect storm takes 4 minutes to settle and error rates spike","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"pasting the profiler output from the laravel app because i genuinely cannot see what's slow:\n\nRequest: GET /admin/orders?status=pending (14.2s)\n\n Database (4,118 queries, 11.8s)\n SELECT * FROM orders WHERE status = ? 1 x 82ms\n SELECT * FROM customers WHERE id = ? 412 x 2.1s\n SELECT * FROM order_items WHERE order_id = ? 412 x 2.4s\n SELECT * FROM products WHERE id = ? 2,180 x 4.9s\n SELECT * FROM addresses WHERE customer_id = ? 412 x 1.4s\n SELECT setting_value FROM settings WHERE key = ? 701 x 0.9s\n\n Views (1.9s)\n orders.index 1.9s\n\n Memory peak: 412 MB\n\n701 queries for settings on one page is what's really bothering me","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} -{"prompt":"settings should be loaded once per request and cached, not queried per access","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"eager load the order page's relations properly and paginate it, same rendered rows","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"query count assertions in our tests for the five heaviest pages, so an n+1 fails CI","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the admin orders page loads all orders regardless of the pagination param","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"orders list ui with server-side pagination, a status filter, and a total count that isn't a full table scan","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"review the other admin pages for the same settings-per-access pattern","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"performance notes for the codebase: the settings gotcha, the eager loading conventions, and how to check query counts locally","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"settings should be loaded once per request and cached, not queried per access","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"eager load the order page's relations properly and paginate it, same rendered rows","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"query count assertions in our tests for the five heaviest pages, so an n+1 fails CI","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the admin orders page loads all orders regardless of the pagination param","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"orders list ui with server-side pagination, a status filter, and a total count that isn't a full table scan","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"review the other admin pages for the same settings-per-access pattern","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"performance notes for the codebase: the settings gotcha, the eager loading conventions, and how to check query counts locally","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"plan the caching layer for the monolith — what's cacheable, where the invalidation hooks go, and how we avoid the stale-settings class of bug","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"settings cache invalidation on write, across all app servers, with a version key rather than a broadcast","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"settings cache invalidation on write, across all app servers, with a version key rather than a broadcast","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"settings changes take up to 10 minutes to appear on some servers","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"settings admin page grouped by area with a search, and a note saying when changes take effect","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the settings page saves each field with its own request as you tab through","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"explain what happens if two admins edit different settings at the same time, given how the form submits","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"internal doc listing every setting, its effect, its default, and whether changing it is safe at peak","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"our settings access happens through a global helper, a facade and direct queries. one accessor, same values returned","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"plan the php 8.4 upgrade then start on the deprecation fixes","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"explain the settings loading path then document it in the readme","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} -{"prompt":"that'll do, just the small bit","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"the settings page saves each field with its own request as you tab through","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"explain what happens if two admins edit different settings at the same time, given how the form submits","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"internal doc listing every setting, its effect, its default, and whether changing it is safe at peak","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"our settings access happens through a global helper, a facade and direct queries. one accessor, same values returned","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"plan the php 8.4 upgrade then start on the deprecation fixes","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"explain the settings loading path then document it in the readme","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} {"prompt":"…circling back on the service mesh question. we have 14 go services doing http between themselves with hand-rolled retries and no mTLS. istio, linkerd, or just a shared library. i want the plan including what we get for free vs what we'd still have to build, and the operational cost of running a mesh with our team size","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"grpc between the catalog and pricing services replacing the http calls, with deadlines propagated and the interceptors for tracing and auth","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"service dependency graph view: services as nodes, call volume as edge weight, and the error rate as color","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the grpc keepalive is off so idle connections get killed by the lb","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"our 14 services each have their own main.go with 200 lines of near-identical setup — logging, metrics, tracing, health, graceful shutdown. one bootstrap library, same runtime behavior per service","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"one service's p99 spikes to 8 seconds whenever another unrelated service deploys","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"does a deadline actually propagate through all our hops, or does someone create a fresh context somewhere? trace it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"service catalog documentation: each service's purpose, owner, dependencies, and the SLO it commits to","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"service dependency graph view: services as nodes, call volume as edge weight, and the error rate as color","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the grpc keepalive is off so idle connections get killed by the lb","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"our 14 services each have their own main.go with 200 lines of near-identical setup — logging, metrics, tracing, health, graceful shutdown. one bootstrap library, same runtime behavior per service","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"one service's p99 spikes to 8 seconds whenever another unrelated service deploys","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"does a deadline actually propagate through all our hops, or does someone create a fresh context somewhere? trace it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"service catalog documentation: each service's purpose, owner, dependencies, and the SLO it commits to","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"mTLS between services with certs from our internal ca, rotated automatically, and a mode where we log violations before enforcing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"one service can't reach another after enabling mTLS and the error is just 'connection reset'","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the ca cert in the config expires in 3 weeks","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"one service can't reach another after enabling mTLS and the error is just 'connection reset'","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the ca cert in the config expires in 3 weeks","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} {"prompt":"plan how we roll out mTLS enforcement service by service without an outage, including the rollback per step","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"gutenberg block for our embed — attributes for the resource id and display mode, an inspector panel, and a server-rendered preview","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the block editor shows 'This block has encountered an error' after a post is saved and reloaded","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"our plugin's admin page enqueues jquery-ui globally and breaks other plugins","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"plugin settings screen using the wp components library instead of our hand-rolled forms, matching core's look","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"we write directly to wp_options with serialized arrays in 30 places. use a settings api wrapper, same stored values","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"gutenberg block for our embed — attributes for the resource id and display mode, an inspector panel, and a server-rendered preview","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"the block editor shows 'This block has encountered an error' after a post is saved and reloaded","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"our plugin's admin page enqueues jquery-ui globally and breaks other plugins","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"plugin settings screen using the wp components library instead of our hand-rolled forms, matching core's look","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"we write directly to wp_options with serialized arrays in 30 places. use a settings api wrapper, same stored values","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"map out the plan for supporting the block themes / full site editing properly, our plugin assumes classic themes throughout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"review our plugin for anything that would break on a multisite install","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"plugin readme.txt for the wordpress directory, with the sections they require and an honest feature list","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"rest api endpoints for the plugin registered properly with permission callbacks, not admin-ajax","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"our ajax endpoints have no nonce check on two of them","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"no_std rust firmware: the sensor driver needs an async interface over the embassy executor, with a timeout that doesn't block the whole executor","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the device hard faults after about 12 hours and the fault handler doesn't give me a useful pc","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"keep going","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"from #eng-oncall last night, nobody's picked it up:\n\n[02:14] alarm: api-gateway 5xx rate 12%\n[02:15] hana: looking\n[02:19] hana: it's the catalog service, grpc UNAVAILABLE from the gateway\n[02:21] hana: catalog pods are all Running, health checks green, its own metrics look fine\n[02:24] hana: catalog can reach the db, i exec'd in and curled its own /healthz, 200\n[02:26] hana: gateway logs: \"rpc error: code = Unavailable desc = last connection error: connection closed before server preface received\"\n[02:31] hana: restarted the gateway pods, error rate back to 0\n[02:33] hana: no idea what that was, going back to bed\n\ni'd like to actually understand this one before it happens again","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"grpc client connection management with proper name resolution refresh, so the gateway picks up new catalog pods without a restart","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the gateway resolves the catalog service once at startup","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"review our grpc client setup across all services for the same resolve-once problem","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"plugin readme.txt for the wordpress directory, with the sections they require and an honest feature list","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"rest api endpoints for the plugin registered properly with permission callbacks, not admin-ajax","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"our ajax endpoints have no nonce check on two of them","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"no_std rust firmware: the sensor driver needs an async interface over the embassy executor, with a timeout that doesn't block the whole executor","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the device hard faults after about 12 hours and the fault handler doesn't give me a useful pc","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"from #eng-oncall last night, nobody's picked it up:\n\n[02:14] alarm: api-gateway 5xx rate 12%\n[02:15] hana: looking\n[02:19] hana: it's the catalog service, grpc UNAVAILABLE from the gateway\n[02:21] hana: catalog pods are all Running, health checks green, its own metrics look fine\n[02:24] hana: catalog can reach the db, i exec'd in and curled its own /healthz, 200\n[02:26] hana: gateway logs: \"rpc error: code = Unavailable desc = last connection error: connection closed before server preface received\"\n[02:31] hana: restarted the gateway pods, error rate back to 0\n[02:33] hana: no idea what that was, going back to bed\n\ni'd like to actually understand this one before it happens again","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"grpc client connection management with proper name resolution refresh, so the gateway picks up new catalog pods without a restart","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the gateway resolves the catalog service once at startup","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"review our grpc client setup across all services for the same resolve-once problem","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"our five grpc clients are constructed differently, three with a hand-built dialer. one client factory with the right defaults, same endpoints and interceptors","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"runbook entry for grpc UNAVAILABLE, including the resolution staleness cause we just found","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"plan the load balancing approach for grpc — client-side with a resolver, or a proxy, given we're not adopting a mesh yet","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"runbook entry for grpc UNAVAILABLE, including the resolution staleness cause we just found","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"plan the load balancing approach for grpc — client-side with a resolver, or a proxy, given we're not adopting a mesh yet","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"gateway health page showing per-upstream connection state and the last resolution time","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the health page's upstream list is hardcoded","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"requests fail during a rolling deploy of any downstream service, for about 15 seconds each time","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain what our readiness probe actually checks, and whether a pod can be ready while unable to serve","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"readiness that reflects dependency health without cascading — unready if our own db is gone, ready if a downstream is degraded","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the health page's upstream list is hardcoded","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"requests fail during a rolling deploy of any downstream service, for about 15 seconds each time","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"explain what our readiness probe actually checks, and whether a pod can be ready while unable to serve","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"readiness that reflects dependency health without cascading — unready if our own db is gone, ready if a downstream is degraded","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} {"prompt":"write the service ownership and on-call doc — which team owns which service and what the escalation is at 2am","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"plan the retry and timeout policy across the mesh — who retries, budgets, and how we avoid retry amplification","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"our services retry at every layer so one slow call becomes 27 requests. implement a retry budget, and document the resulting behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"a single slow downstream causes a full outage rather than degraded service","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the retry count is 5 with no backoff","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"degraded-mode ui: when pricing is unavailable, show the catalog without prices and a clear note rather than an error page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"our services retry at every layer so one slow call becomes 27 requests. implement a retry budget, and document the resulting behavior","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"a single slow downstream causes a full outage rather than degraded service","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the retry count is 5 with no backoff","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"degraded-mode ui: when pricing is unavailable, show the catalog without prices and a clear note rather than an error page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"plan the mesh adoption then implement the mTLS pilot on two services","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"diagnose the grpc UNAVAILABLE thing and then write the postmortem","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"the firmware. we're on a stm32l4 with 256k flash and 64k ram, and we're at 240k flash. the feature list for next year needs another 60k. options: a bigger part (bom cost, and a redesign), compress assets, drop the usb stack, or actually optimize. write me the analysis with real numbers from the current map file","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"shrink the binary — panic strings are eating 18k, and the formatting machinery pulls in a lot. get us under 200k without losing diagnostics entirely","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"the release profile has debug assertions and overflow checks on","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"defmt logging over rtt replacing our current uart printf, with the strings interned so they don't live in flash","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the device stops responding to i2c after a specific sensor error, and only a power cycle recovers it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"explain our interrupt priorities and whether the sensor isr can be preempted by the radio isr mid-transaction","purpose":"review","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"firmware architecture doc: the task layout, the interrupt priorities, the memory map, and the power states","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"power management: sleep between samples, wake on the accelerometer interrupt, and get average current under 40µA","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"measured current is 2.1mA in sleep, expecting 40µA, so something is keeping a peripheral clock on","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"the sample interval is 1s, spec says 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"our peripheral init is spread through main and three modules, each enabling clocks and never disabling them. centralize it, same peripherals functional","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"diagnose the grpc UNAVAILABLE thing and then write the postmortem","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"the firmware. we're on a stm32l4 with 256k flash and 64k ram, and we're at 240k flash. the feature list for next year needs another 60k. options: a bigger part (bom cost, and a redesign), compress assets, drop the usb stack, or actually optimize. write me the analysis with real numbers from the current map file","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"shrink the binary — panic strings are eating 18k, and the formatting machinery pulls in a lot. get us under 200k without losing diagnostics entirely","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the release profile has debug assertions and overflow checks on","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"defmt logging over rtt replacing our current uart printf, with the strings interned so they don't live in flash","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the device stops responding to i2c after a specific sensor error, and only a power cycle recovers it","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"explain our interrupt priorities and whether the sensor isr can be preempted by the radio isr mid-transaction","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"firmware architecture doc: the task layout, the interrupt priorities, the memory map, and the power states","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"power management: sleep between samples, wake on the accelerometer interrupt, and get average current under 40µA","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"measured current is 2.1mA in sleep, expecting 40µA, so something is keeping a peripheral clock on","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the sample interval is 1s, spec says 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"our peripheral init is spread through main and three modules, each enabling clocks and never disabling them. centralize it, same peripherals functional","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"plan the ota update for these devices given 256k flash and no room for two full images","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"review the bootloader's image validation — signature, version rollback protection, and what it does with a corrupt image","purpose":"review","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"production test firmware that exercises every peripheral and outputs a pass/fail per test for the factory jig","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"manufacturing test procedure doc for the contract manufacturer, step by step, with the expected outputs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"factory jig ui on a raspberry pi touchscreen: scan the serial, run tests, big pass/fail, and log the result","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the jig ui's pass indication is a small green text label, make it fill the screen","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"about 1 in 200 units fails the radio test at the factory and passes on a retest","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"wir sind bei 240k von 256k Flash. plan mir bitte, wie wir Platz schaffen, mit konkreten Zahlen aus der Map-Datei","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"de"} +{"prompt":"review the bootloader's image validation — signature, version rollback protection, and what it does with a corrupt image","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"production test firmware that exercises every peripheral and outputs a pass/fail per test for the factory jig","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"manufacturing test procedure doc for the contract manufacturer, step by step, with the expected outputs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"factory jig ui on a raspberry pi touchscreen: scan the serial, run tests, big pass/fail, and log the result","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"the jig ui's pass indication is a small green text label, make it fill the screen","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"about 1 in 200 units fails the radio test at the factory and passes on a retest","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"wir sind bei 240k von 256k Flash. plan mir bitte, wie wir Platz schaffen, mit konkreten Zahlen aus der Map-Datei","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} {"prompt":"provisioning at the factory: burn a unique key per device into the protected flash region, recorded in our db against the serial","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"check whether a provisioned key can be read back out over swd or the debug uart","purpose":"review","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"readout protection isn't enabled on the production build","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"device management page: fleet list with firmware version, last seen, battery, and a filter for devices that haven't reported in a week","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"battery percentage shows 100% for devices that have never reported","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"onwards, next thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"so we sell a wordpress plugin and a saas, and the plugin talks to the saas. the plugin's version distribution is horrifying — people are running versions from 2022 against our current api. i want the plan for how we handle that: api versioning per plugin version, forced updates, or a compatibility shim, and what we do about the 8% who will never update","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"check whether a provisioned key can be read back out over swd or the debug uart","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"readout protection isn't enabled on the production build","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"device management page: fleet list with firmware version, last seen, battery, and a filter for devices that haven't reported in a week","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"battery percentage shows 100% for devices that have never reported","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"so we sell a wordpress plugin and a saas, and the plugin talks to the saas. the plugin's version distribution is horrifying — people are running versions from 2022 against our current api. i want the plan for how we handle that: api versioning per plugin version, forced updates, or a compatibility shim, and what we do about the 8% who will never update","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"version negotiation on the api — the plugin sends its version, we respond with the compatible shape, and we log which versions are still in use","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"plugin version dashboard: distribution across our installs, and which api features each version uses","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the plugin sends its version in a header we never read","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"plugin version dashboard: distribution across our installs, and which api features each version uses","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"the plugin sends its version in a header we never read","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"our api has three response shapes for the same resource depending on which plugin version asks, implemented as if-branches through the serializer. move to explicit versioned serializers, byte-identical output per version","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"installs on plugin 2.1 started getting 500s yesterday and we didn't change anything for that version","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"installs on plugin 2.1 started getting 500s yesterday and we didn't change anything for that version","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"tell me which of our api endpoints would break a 2022-era plugin today, from reading the code","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"compatibility policy doc for plugin users: which plugin versions we support, for how long, and what happens when yours falls out","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"compatibility policy doc for plugin users: which plugin versions we support, for how long, and what happens when yours falls out","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"in-plugin update nag that's informative rather than annoying, dismissible, and escalating in urgency as the version ages","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the update nag shows on every admin page load","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"plan the plugin's own update mechanism — we're not in the wp directory, so we serve updates ourselves and it's fragile","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"update server endpoint that wordpress's updater understands, with the version metadata and a signed package url","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the update nag shows on every admin page load","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"plan the plugin's own update mechanism — we're not in the wp directory, so we serve updates ourselves and it's fragile","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"update server endpoint that wordpress's updater understands, with the version metadata and a signed package url","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"some installs report an update available every page load even after updating","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"review our update flow for whether someone could serve a malicious package by mitm-ing the update check","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"changelog for the plugin, user-facing, for the last four releases, since we've been writing 'bug fixes'","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"license key activation in the plugin, tolerant of an offline site, with a clear state when it can't reach us","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the license check runs synchronously on every page load and adds 300ms when our api is slow","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"explain what the plugin does when our api is unreachable — degrade, cache, or break","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"ok, next please","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"license key activation in the plugin, tolerant of an offline site, with a clear state when it can't reach us","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the license check runs synchronously on every page load and adds 300ms when our api is slow","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"explain what the plugin does when our api is unreachable — degrade, cache, or break","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"here's the slack thread from the customer's dev channel, they gave us access:\n\n[10:02] their-dev: your plugin is adding 1.8s to our TTFB\n[10:04] their-dev: query monitor says 340 queries from acme-connect\n[10:05] their-dev: they're all SELECT option_value FROM wp_options WHERE option_name = 'acme_cache_...'\n[10:09] their-dev: also you have 12,000 rows in wp_options with the acme_ prefix, none autoloaded thankfully\n[10:11] their-dev: wait, 400 of them ARE autoloaded, that's 2MB of autoload data\n[10:14] their-dev: we're on a shared host, this is why our admin is unusable\n[10:15] their-dev: please fix or we'll have to drop the plugin\n\nthis is our third complaint like this","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"replace the wp_options cache with the transients api used correctly, or a custom table, and clean up the 12k rows we've left behind","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"our cache writes use add_option with autoload defaulting to yes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"cleanup routine that removes our orphaned options on update, batched so it doesn't time out on a shared host","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"plugin diagnostics screen: our cache size, row counts, and a cleanup button, so a site owner can see what we're using","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"replace the wp_options cache with the transients api used correctly, or a custom table, and clean up the 12k rows we've left behind","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"our cache writes use add_option with autoload defaulting to yes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"cleanup routine that removes our orphaned options on update, batched so it doesn't time out on a shared host","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"plugin diagnostics screen: our cache size, row counts, and a cleanup button, so a site owner can see what we're using","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"review everywhere our plugin writes to the database and tell me what it costs a site with 50k posts","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"write the reply to the customer's dev — specific about what we found, what we're changing, and a workaround for right now","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"plan the plugin's performance work — a budget for what we add to TTFB, and a test on a representative shared host","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"performance test harness that runs our plugin on a seeded wordpress with 50k posts and reports query counts and timings","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the perf harness's seeded site has 12 posts","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"our plugin hooks init, admin_init and wp_loaded and does the same work in each because someone wasn't sure which fires. pick the right one, same behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the plugin's work runs on frontend requests too, where none of it is needed","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"explain which of our hooks fire on a frontend request versus admin, and what we do in each","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"performance section for the plugin docs: what we do on each request, our caching, and how to diagnose a slowdown","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"background sync via wp-cron with a proper lock so two overlapping runs can't both process the same batch","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"wp-cron never fires on sites with DISABLE_WP_CRON and we don't tell anyone","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the perf harness's seeded site has 12 posts","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"our plugin hooks init, admin_init and wp_loaded and does the same work in each because someone wasn't sure which fires. pick the right one, same behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"the plugin's work runs on frontend requests too, where none of it is needed","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"explain which of our hooks fire on a frontend request versus admin, and what we do in each","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"performance section for the plugin docs: what we do on each request, our caching, and how to diagnose a slowdown","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"background sync via wp-cron with a proper lock so two overlapping runs can't both process the same batch","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"wp-cron never fires on sites with DISABLE_WP_CRON and we don't tell anyone","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"sync status panel with the last run, next scheduled run, and a warning if wp-cron looks disabled","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"figure out the plan for a proper background job system in the plugin, since wp-cron isn't reliable, then build the queue table","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"have a look at the options usage and clean up what's obviously wrong","purpose":"review","secondary":"refactor","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} -{"prompt":"ok now the other bit","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"figure out the plan for a proper background job system in the plugin, since wp-cron isn't reliable, then build the queue table","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"have a look at the options usage and clean up what's obviously wrong","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} {"prompt":"propose how we do canary deployments for the go services. we have 14 of them, k8s, argo cd, and no traffic splitting today — a deploy is a rolling update and we find out from customers. i want the design including the metrics we'd gate on and what happens to in-flight grpc streams during a rollback","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"canary analysis job comparing error rate and latency between the canary and stable pods, with a verdict the rollout controller reads","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"deploy view: rollout progress, canary metrics side by side with stable, and a promote/abort","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the canary weight is 50% which defeats the purpose","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"the canary passes analysis and then errors spike after promotion","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain what metrics our canary analysis actually looks at and whether they'd catch a bug affecting 2% of requests","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"deployment guide for service owners: how a canary works, what gates it, and how to roll back manually if the automation fails","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"feature-flag-gated rollout as an alternative to traffic splitting for the services where it fits better","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"canary analysis job comparing error rate and latency between the canary and stable pods, with a verdict the rollout controller reads","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"deploy view: rollout progress, canary metrics side by side with stable, and a promote/abort","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the canary weight is 50% which defeats the purpose","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"the canary passes analysis and then errors spike after promotion","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"explain what metrics our canary analysis actually looks at and whether they'd catch a bug affecting 2% of requests","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"deployment guide for service owners: how a canary works, what gates it, and how to roll back manually if the automation fails","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"feature-flag-gated rollout as an alternative to traffic splitting for the services where it fits better","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} {"prompt":"rollbacks leave the old replicaset scaled up and we pay for double capacity for days","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the rollout's progressDeadlineSeconds is 600 and our slowest service takes 12 minutes to become ready","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the rollout's progressDeadlineSeconds is 600 and our slowest service takes 12 minutes to become ready","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"plan how we test a rollback for real, in staging, on a schedule, so we know it works before we need it","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"review whether a rollback can leave the database schema ahead of the code, and what breaks if it does","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"migration compatibility checks in CI — flag any migration that the previous release's code couldn't tolerate","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"write the expand-contract migration guide with worked examples for the three cases people get wrong","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"review whether a rollback can leave the database schema ahead of the code, and what breaks if it does","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"migration compatibility checks in CI — flag any migration that the previous release's code couldn't tolerate","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"write the expand-contract migration guide with worked examples for the three cases people get wrong","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"release dashboard: what version each service is running per environment, and how far behind stable each is","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the version shown is the chart version not the image tag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"design the canary system then implement the metrics comparison","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"alright, last one for today","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"the version shown is the chart version not the image tag","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"design the canary system then implement the metrics comparison","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} {"prompt":"svelte 5: build the comment thread component. nested replies up to 3 deep, collapse long chains, optimistic insert when you post, runes not stores","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"airflow dag for the nightly Bramble refresh: extract from clickhouse, three transforms in sequence, publish to duckdb, alert on sla miss past 6am","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"docs for the /ingest websocket protocol. frame types, the handshake, backoff expectations on the client side. it's built, it's just tribal knowledge right now","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"training loss goes to nan around step 3k, every time, same step give or take 50. lr is 3e-4 with warmup, grad clip at 1.0, bf16. i've tried lowering the lr and it just moves the cliff later","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"should we build the notification fan-out on temporal or just do it with pg + a poller? want the tradeoffs written down, we'll decide friday","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"drop the `deprecated_` prefix from the two helpers in lib/dates.py, nothing external imports them","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.15,"slice":"boundary","lang":"en"} -{"prompt":"is our jwt verification actually checking `aud`? i see the audience in the config but i can't find where it's compared","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"airflow dag for the nightly Bramble refresh: extract from clickhouse, three transforms in sequence, publish to duckdb, alert on sla miss past 6am","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"docs for the /ingest websocket protocol. frame types, the handshake, backoff expectations on the client side. it's built, it's just tribal knowledge right now","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"training loss goes to nan around step 3k, every time, same step give or take 50. lr is 3e-4 with warmup, grad clip at 1.0, bf16. i've tried lowering the lr and it just moves the cliff later","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"should we build the notification fan-out on temporal or just do it with pg + a poller? want the tradeoffs written down, we'll decide friday","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"drop the `deprecated_` prefix from the two helpers in lib/dates.py, nothing external imports them","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"is our jwt verification actually checking `aud`? i see the audience in the config but i can't find where it's compared","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} {"prompt":"the three env parsing helpers in cmd/ all do the same thing with slightly different error messages. one helper, keep the strictest behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"ok so thinking out loud here. we have a ClickHouse cluster that's fine for the dashboards but the ad-hoc queries analysts run are killing it, and finance wants a semantic layer so nobody hand-writes revenue definitions again. options as i see them: cube.dev in front, or dbt metrics + a thin api, or just give them a read replica and stop worrying. i don't know enough about the tradeoffs. can you write this up properly with a recommendation, including what we'd have to own operationally in each case","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"kill the `--legacy-json` flag, nothing uses it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"phoenix liveview: the presence list flickers empty for a frame on reconnect and users notice","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"cassandra -> scylla, worth the migration for us? write me something i can circulate. we're at 12TB, read heavy, p99 matters more than throughput","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"flutter: bottom nav with 4 tabs, keeps its own navigator stack per tab, and the badge on the third tab reads from the unread count provider","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"explain vs summarize, i want the summarize version: what does packages/foxglove actually do, three paragraphs, for the wiki page a PM will read","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"boundary","lang":"en"} -{"prompt":"nats jetstream consumer for the `orders.*` subjects with a durable name, max deliver 5, and a dlq subject for the poison messages","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"read internal/halyard/lease.go and tell me if the ttl renewal can race with expiry. no changes, i just want to know if my worry is real","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"raise the alert threshold on QueueDepthHigh from 500 to 2000, it pages constantly and nobody acts on it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.15,"slice":"core","lang":"en"} -{"prompt":"hoist the duplicated pagination logic out of the six list resolvers into one helper. same page sizes, same cursor encoding, don't change the wire format","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"angular: the reactive form marks itself dirty on init because we patchValue before subscribing. users get the unsaved-changes prompt on a page they never touched","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} +{"prompt":"ok so thinking out loud here. we have a ClickHouse cluster that's fine for the dashboards but the ad-hoc queries analysts run are killing it, and finance wants a semantic layer so nobody hand-writes revenue definitions again. options as i see them: cube.dev in front, or dbt metrics + a thin api, or just give them a read replica and stop worrying. i don't know enough about the tradeoffs. can you write this up properly with a recommendation, including what we'd have to own operationally in each case","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"kill the `--legacy-json` flag, nothing uses it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"phoenix liveview: the presence list flickers empty for a frame on reconnect and users notice","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"cassandra -> scylla, worth the migration for us? write me something i can circulate. we're at 12TB, read heavy, p99 matters more than throughput","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"flutter: bottom nav with 4 tabs, keeps its own navigator stack per tab, and the badge on the third tab reads from the unread count provider","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain vs summarize, i want the summarize version: what does packages/foxglove actually do, three paragraphs, for the wiki page a PM will read","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"nats jetstream consumer for the `orders.*` subjects with a durable name, max deliver 5, and a dlq subject for the poison messages","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"read internal/halyard/lease.go and tell me if the ttl renewal can race with expiry. no changes, i just want to know if my worry is real","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"raise the alert threshold on QueueDepthHigh from 500 to 2000, it pages constantly and nobody acts on it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"hoist the duplicated pagination logic out of the six list resolvers into one helper. same page sizes, same cursor encoding, don't change the wire format","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"angular: the reactive form marks itself dirty on init because we patchValue before subscribing. users get the unsaved-changes prompt on a page they never touched","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"readme for the driftwood python package. what it does, install from our internal index, the one-liner usage, and a note that the 0.x api will break","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"bevy: sprite batching for the tilemap. 200x200 tiles, currently one entity per tile and it dies at 60fps","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"bevy: sprite batching for the tilemap. 200x200 tiles, currently one entity per tile and it dies at 60fps","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} {"prompt":"design the multi-region story for Larkspur. active-passive is fine, but i need the failover to be under 5 min and i don't want to lose writes. postgres, one primary in us-east","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"prisma schema + migration for the new `webhook_endpoints` table — url, secret (encrypted at rest), event filter array, per-endpoint enabled flag, fk to workspace with cascade","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"prisma schema + migration for the new `webhook_endpoints` table — url, secret (encrypted at rest), event filter array, per-endpoint enabled flag, fk to workspace with cascade","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"pasted from the review comment thread, want your take on whether they're right:\n\n```\n@rmk commented on src/queue/worker.ts line 88\n\n> const jobs = await redis.lrange(key, 0, batchSize - 1)\n> await redis.ltrim(key, batchSize, -1)\n> for (const raw of jobs) {\n> await handle(JSON.parse(raw))\n> }\n\nthis isn't atomic — if the process dies between lrange and ltrim you\nreprocess, and if it dies after ltrim you lose the batch entirely.\nalso the sequential await in the loop means one slow job blocks the\nwhole batch, which defeats the point of batching.\n\nsuggest either a lua script for the pop, or move to a proper\nreliable-queue pattern with a processing list.\n\n@dtl replied\nwe're at-least-once anyway so the reprocess case is fine, and jobs are\nidempotent. the loss case i agree is bad.\n```\n\nis dtl's defense sound? and is the sequential loop actually a problem given our job mix","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"pull the tailwind config out into the shared preset so all three apps stop having slightly different spacing scales","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"fix the s in \"recieve\" — it's in the email template subject line","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"core","lang":"en"} -{"prompt":"map view for the delivery tracker. mapbox, cluster the pins over 50, draw the route polyline, recenter button that doesn't fight with user panning","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"plan out the offline-first rewrite of the field app and then get the local sqlite schema + the sync queue skeleton in place so i can see it working","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.85,"slice":"mixed","lang":"en"} +{"prompt":"pull the tailwind config out into the shared preset so all three apps stop having slightly different spacing scales","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"fix the s in \"recieve\" — it's in the email template subject line","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"map view for the delivery tracker. mapbox, cluster the pins over 50, draw the route polyline, recenter button that doesn't fight with user panning","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"plan out the offline-first rewrite of the field app and then get the local sqlite schema + the sync queue skeleton in place so i can see it working","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} {"prompt":"temporal workflow for the KYC pipeline: three external vendor calls, each can take days, human review activity in the middle, and the whole thing has to be resumable after a deploy","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"why so slow","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"release notes 4.1, and please mention the breaking change to the `--out` flag prominently, people are going to get bitten","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"zig: replace the recursive descent in the config parser with an explicit stack. it stack-overflows on deeply nested files. same accepted grammar","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"the docker healthcheck says healthy while the app is still doing migrations, so traffic hits a 503 for ~20s every deploy","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"why so slow","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"release notes 4.1, and please mention the breaking change to the `--out` flag prominently, people are going to get bitten","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"zig: replace the recursive descent in the config parser with an explicit stack. it stack-overflows on deeply nested files. same accepted grammar","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the docker healthcheck says healthy while the app is still doing migrations, so traffic hits a 503 for ~20s every deploy","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"hook the export button to the new /v1/exports endpoint, show the progress toast, and download when it's done","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"audit our GitHub Actions for supply chain hygiene — unpinned actions, secrets in pull_request_target, missing permissions blocks. report only, i'll fix","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"audit our GitHub Actions for supply chain hygiene — unpinned actions, secrets in pull_request_target, missing permissions blocks. report only, i'll fix","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"duckdb query in the CLI that gives me p50/p95/p99 latency per endpoint per day from the parquet logs. add it as `latency` subcommand","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"ansible role name is `postgres_setup`, standard is verb-less nouns, make it `postgresql` and update the two playbooks that include it","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"milestones + owners for getting the design system to 1.0. 34 components, 19 done, and we need docs and a11y sign-off on each. quarter boundary is in 7 weeks","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"one line: the retry count in workers/sync.ts should be 5 not 3","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"core","lang":"en"} -{"prompt":"an dieser stelle brauche ich eine erklärung: wie entscheidet der scheduler in services/thistle welche jobs zuerst laufen? ich sehe zwei sortierungen und weiß nicht welche gewinnt","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"de"} -{"prompt":"vue 3: the virtual list keeps its scroll position when you filter, so you end up staring at blank space. should reset to top on filter change but keep position on refetch","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"changelog + a short migration note for consumers of the `signalbox` sdk, the event payload gained a required field","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"ansible role name is `postgres_setup`, standard is verb-less nouns, make it `postgresql` and update the two playbooks that include it","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"milestones + owners for getting the design system to 1.0. 34 components, 19 done, and we need docs and a11y sign-off on each. quarter boundary is in 7 weeks","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"one line: the retry count in workers/sync.ts should be 5 not 3","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"an dieser stelle brauche ich eine erklärung: wie entscheidet der scheduler in services/thistle welche jobs zuerst laufen? ich sehe zwei sortierungen und weiß nicht welche gewinnt","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"de"} +{"prompt":"vue 3: the virtual list keeps its scroll position when you filter, so you end up staring at blank space. should reset to top on filter change but keep position on refetch","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"changelog + a short migration note for consumers of the `signalbox` sdk, the event payload gained a required field","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"godot: inventory grid ui, drag items between slots, stack counts, right click splits the stack. 8x4 grid, gamepad navigable too","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"OTEL spans through the whole checkout path — worker at the edge, the two go services, and the python risk scorer. propagate traceparent, don't lose the link across the queue hop","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"OTEL spans through the whole checkout path — worker at the edge, the two go services, and the python risk scorer. propagate traceparent, don't lose the link across the queue hop","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"someone left a mess in the terraform, here's terraform plan, and i genuinely can't tell if this is safe to apply:\n\n```\n # aws_db_instance.primary will be updated in-place\n ~ resource \"aws_db_instance\" \"primary\" {\n ~ allocated_storage = 200 -> 500\n ~ backup_retention_period = 7 -> 14\n ~ instance_class = \"db.r6g.xlarge\" -> \"db.r6g.2xlarge\"\n ~ parameter_group_name = \"pg16-tuned-v2\" -> \"pg16-tuned-v3\"\n id = \"harborview-prod\"\n }\n\n # aws_db_parameter_group.pg16_tuned_v3 will be created\n + resource \"aws_db_parameter_group\" \"pg16_tuned_v3\" {\n + family = \"postgres16\"\n + parameter {\n + apply_method = \"immediate\"\n + name = \"max_connections\"\n + value = \"800\"\n }\n + parameter {\n + apply_method = \"pending-reboot\"\n + name = \"shared_buffers\"\n + value = \"{DBInstanceClassMemory/16384}\"\n }\n }\n\n # aws_security_group_rule.db_from_bastion will be destroyed\n - resource \"aws_security_group_rule\" \"db_from_bastion\" {\n - cidr_blocks = [\"10.2.0.0/24\"] -> null\n - from_port = 5432 -> null\n }\n\nPlan: 1 to add, 1 to change, 1 to destroy.\n```\n\nwhich of these forces a reboot and is the sg rule removal going to lock us out mid-apply","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"make the settings sheet dismissable by swiping down, it only closes via the X right now","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"consolidate the four almost-identical Dockerfiles into one with build args. images should come out the same size and contents","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} +{"prompt":"make the settings sheet dismissable by swiping down, it only closes via the X right now","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"consolidate the four almost-identical Dockerfiles into one with build args. images should come out the same size and contents","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"sketch out how we'd do incremental static regeneration for the 400k product pages without paying for 400k builds. next app router, on cloudflare","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"requests to the risk scorer time out at exactly 60s under load, but the scorer itself logs a 1.2s response. envoy is in the path","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"doc comments on every exported func in pkg/tanager. godoc style, and the package doc should explain the two-phase commit thing because nobody gets it from the code","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"add a `--json` output mode to every subcommand. one shared encoder, stable field names, and stderr stays human readable","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the copy button on code blocks copies the line numbers too","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.25,"slice":"boundary","lang":"en"} -{"prompt":"compare our current approach (polling the api every 30s) with SSE and with websockets for the live order board. i mostly want to know what breaks at 5k concurrent viewers","purpose":"review","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"rails: the counter cache on `comments_count` drifts. we do a raw update in one migration and a bulk delete in the moderation job, neither touches the cache. want it fixed properly and a rake task to recompute","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"astro: content collection for the docs, sidebar generated from frontmatter order, and a version switcher that swaps the whole tree","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"necesitamos documentar el flujo de autenticación para el equipo nuevo — diagrama en mermaid, los cuatro endpoints, y qué pasa cuando el refresh token expira. el código no se toca","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"es"} -{"prompt":"sqlalchemy 1.x style queries all over the repo, move to 2.0 select() style. behavior and emitted sql should match, tests are the contract","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"cloudflare worker that signs image transform urls and proxies to r2, with a 1 year cache and a purge hook on upload","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"roadmap-ish: what would it take to get cold start under 200ms for the lambda-backed api. current is 1.4s worst case. i want options ranked by effort","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"the mobile menu doesn't close when you tap a link, you have to hit the X","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"look at the two implementations of ULID generation we somehow have (pkg/ids and web/src/lib/ulid.ts) and tell me if they'd ever produce colliding or out-of-order ids across processes","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"pytorch dataloader is the bottleneck, gpu util sits at 30%. num_workers is 8, pin_memory on, decoding jpegs on cpu. 4090, images are 1024px","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"requests to the risk scorer time out at exactly 60s under load, but the scorer itself logs a 1.2s response. envoy is in the path","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"doc comments on every exported func in pkg/tanager. godoc style, and the package doc should explain the two-phase commit thing because nobody gets it from the code","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"add a `--json` output mode to every subcommand. one shared encoder, stable field names, and stderr stays human readable","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the copy button on code blocks copies the line numbers too","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"compare our current approach (polling the api every 30s) with SSE and with websockets for the live order board. i mostly want to know what breaks at 5k concurrent viewers","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"rails: the counter cache on `comments_count` drifts. we do a raw update in one migration and a bulk delete in the moderation job, neither touches the cache. want it fixed properly and a rake task to recompute","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"astro: content collection for the docs, sidebar generated from frontmatter order, and a version switcher that swaps the whole tree","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"necesitamos documentar el flujo de autenticación para el equipo nuevo — diagrama en mermaid, los cuatro endpoints, y qué pasa cuando el refresh token expira. el código no se toca","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} +{"prompt":"sqlalchemy 1.x style queries all over the repo, move to 2.0 select() style. behavior and emitted sql should match, tests are the contract","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"cloudflare worker that signs image transform urls and proxies to r2, with a 1 year cache and a purge hook on upload","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"roadmap-ish: what would it take to get cold start under 200ms for the lambda-backed api. current is 1.4s worst case. i want options ranked by effort","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the mobile menu doesn't close when you tap a link, you have to hit the X","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"look at the two implementations of ULID generation we somehow have (pkg/ids and web/src/lib/ulid.ts) and tell me if they'd ever produce colliding or out-of-order ids across processes","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"pytorch dataloader is the bottleneck, gpu util sits at 30%. num_workers is 8, pin_memory on, decoding jpegs on cpu. 4090, images are 1024px","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"keyboard-only pass on the checkout flow: tab order, focus trap in the modal, escape closes, and the error summary gets focus on submit failure","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"write the FAQ section for the self-hosting docs. i'll give you the questions support gets most: can i use my own s3, why does it need two containers, how do i rotate the encryption key, is there an air-gapped mode","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} +{"prompt":"write the FAQ section for the self-hosting docs. i'll give you the questions support gets most: can i use my own s3, why does it need two containers, how do i rotate the encryption key, is there an air-gapped mode","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"elixir: genserver that owns the rate limit buckets, ets backed, and survives restart without letting everyone through at once","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"same as the last cleanup — inline the single-use `buildQueryParams` wrapper and delete it. it's only called from one place and it obscures more than it helps","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.25,"slice":"boundary","lang":"en"} -{"prompt":"plan the api versioning scheme (we have none) and then implement the routing + deprecation header middleware for it","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.75,"slice":"mixed","lang":"en"} -{"prompt":"playwright suite times out on CI about a third of the time. the failing test is never the same one. 4 workers, chromium only, the app is served from a preview build","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} +{"prompt":"same as the last cleanup — inline the single-use `buildQueryParams` wrapper and delete it. it's only called from one place and it obscures more than it helps","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"plan the api versioning scheme (we have none) and then implement the routing + deprecation header middleware for it","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"playwright suite times out on CI about a third of the time. the failing test is never the same one. 4 workers, chromium only, the app is served from a preview build","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"sort out the theme tokens","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"raspberry pi: mqtt bridge that reads the CAN bus, decodes the six PGNs we care about, and publishes to the broker with a 1hz rate cap per signal","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"second pair of eyes on the schema before i migrate:\n\n```sql\ncreate table membership (\n id bigserial primary key,\n workspace_id bigint not null references workspace(id),\n user_id bigint not null references app_user(id),\n role text not null check (role in ('owner','admin','member','guest')),\n invited_by bigint references app_user(id),\n invited_at timestamptz not null default now(),\n accepted_at timestamptz,\n removed_at timestamptz,\n unique (workspace_id, user_id)\n);\n\ncreate index on membership (user_id);\ncreate index on membership (workspace_id, role);\n```\n\nthings i'm unsure about: the unique constraint means a removed member can never be re-invited, right? and do i actually need both indexes given the unique already gives me one on (workspace_id, user_id)","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} -{"prompt":"bump the eslint config package to 9.2 and run the codemod for the flat config rename","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.25,"slice":"core","lang":"en"} -{"prompt":"figure out the tab bar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"we're going to open source the parser. plan the extraction: what stays private, license headers, how we keep the internal fork in sync, CI for external contributors, and the first release checklist","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} +{"prompt":"second pair of eyes on the schema before i migrate:\n\n```sql\ncreate table membership (\n id bigserial primary key,\n workspace_id bigint not null references workspace(id),\n user_id bigint not null references app_user(id),\n role text not null check (role in ('owner','admin','member','guest')),\n invited_by bigint references app_user(id),\n invited_at timestamptz not null default now(),\n accepted_at timestamptz,\n removed_at timestamptz,\n unique (workspace_id, user_id)\n);\n\ncreate index on membership (user_id);\ncreate index on membership (workspace_id, role);\n```\n\nthings i'm unsure about: the unique constraint means a removed member can never be re-invited, right? and do i actually need both indexes given the unique already gives me one on (workspace_id, user_id)","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"bump the eslint config package to 9.2 and run the codemod for the flat config rename","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"figure out the tab bar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"we're going to open source the parser. plan the extraction: what stays private, license headers, how we keep the internal fork in sync, CI for external contributors, and the first release checklist","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"kotlin: replace the nested when-expression state handling in PaymentReducer with a sealed interface + exhaustive dispatch. identical transitions, the tests shouldn't need edits","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"safari only: the sticky footer jumps up when the on-screen keyboard opens and covers the input we just focused","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"docs page comparing our three storage backends (local, s3, r2) — capabilities table, config snippets, and which one we recommend for what","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"boundary","lang":"en"} +{"prompt":"safari only: the sticky footer jumps up when the on-screen keyboard opens and covers the input we just focused","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"docs page comparing our three storage backends (local, s3, r2) — capabilities table, config snippets, and which one we recommend for what","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"settings page skeleton with the sections stubbed: profile, notifications, api keys, danger zone. just layout and nav for now, no data","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"server-side cursor pagination for the /activity feed. keyset on (created_at, id) desc, opaque base64 cursor, and it has to be stable when new events land mid-scroll","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"is there a reason `parseAmount` returns a float? asking before i change it to a decimal type and break something i can't see","purpose":"review","secondary":null,"mixed":false,"difficulty":0.45,"slice":"boundary","lang":"en"} +{"prompt":"server-side cursor pagination for the /activity feed. keyset on (created_at, id) desc, opaque base64 cursor, and it has to be stable when new events land mid-scroll","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"is there a reason `parseAmount` returns a float? asking before i change it to a decimal type and break something i can't see","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"the sql in dashboards/queries.py is embedded in f-strings with `.format()`. move them to .sql files loaded at import, parameterized properly. output must be identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"npm audit noise aside, this is real, and i just want it patched:\n\n```\n$ npm run lint\n\n> mossbank@2.3.1 lint\n> eslint . --max-warnings=0\n\n/repo/src/upload/presign.ts\n 41:11 error 'crypto' is imported but never used @typescript-eslint/no-unused-vars\n 58:5 error Unsafe usage of optional chaining no-unsafe-optional-chaining\n 59:20 error Expected a `string` but received `any` @typescript-eslint/no-unsafe-argument\n\n/repo/src/upload/index.ts\n 12:1 error Import in body of module; reorder to top import/first\n\n✖ 4 problems (4 errors, 0 warnings)\nERROR: \"lint\" exited with 1.\n```\n\nthe optional chaining one is on `parts?.length - 1` which is genuinely wrong, the rest are mechanical","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"pasted-context","lang":"en"} {"prompt":"profile the tile renderer hot loop and tell me where the time goes. don't optimize yet, i want to understand it first","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"design the permissions model for Owlet. resources nest (org > project > dataset), roles are inheritable, and there's a share-by-link case that doesn't fit rbac cleanly. write it up before i code myself into a corner","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"line 214 of ingest.go, the ctx should be the request ctx not context.Background()","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"onboarding checklist widget — 5 steps, checkmarks animate in, collapses to a progress pill once complete, and it should remember dismissal per user","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"grafana dashboards as code with jsonnet. one dashboard per service from a shared library, and the alert rules alongside","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"memory grows unbounded in the websocket gateway over ~12h and then k8s OOMKills it. 8k connections steady state. i've got heap profiles but they mostly show []byte and i don't know who's holding them","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"spell out what our SLOs should be for the public api and write the doc. we have no numbers today, just vibes and a status page","purpose":"planning","secondary":"writing","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"make the diff view in the PR page collapse unchanged hunks with a \"show 42 more lines\" affordance","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} +{"prompt":"design the permissions model for Owlet. resources nest (org > project > dataset), roles are inheritable, and there's a share-by-link case that doesn't fit rbac cleanly. write it up before i code myself into a corner","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"line 214 of ingest.go, the ctx should be the request ctx not context.Background()","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"onboarding checklist widget — 5 steps, checkmarks animate in, collapses to a progress pill once complete, and it should remember dismissal per user","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"grafana dashboards as code with jsonnet. one dashboard per service from a shared library, and the alert rules alongside","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"memory grows unbounded in the websocket gateway over ~12h and then k8s OOMKills it. 8k connections steady state. i've got heap profiles but they mostly show []byte and i don't know who's holding them","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"spell out what our SLOs should be for the public api and write the doc. we have no numbers today, just vibes and a status page","purpose":"planning","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"make the diff view in the PR page collapse unchanged hunks with a \"show 42 more lines\" affordance","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"何が原因でこのテストだけ CI で落ちるのか調べてほしい。ローカルでは通る。タイムゾーンかもしれないけど確証がない","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"ja"} -{"prompt":"dedupe the two http clients. one has retries and the other has tracing, i want one that has both, and every caller moved over","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"swagger says the field is optional, the handler 400s without it. which one's the bug? i genuinely don't know what the intended contract is","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"nix flake for the dev env: go 1.23, node 22, protoc with the two plugins, and postgres 16 for the test harness. has to work on darwin and linux","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"quick copy fix — the empty state says \"No results found for your search\" even when the user hasn't searched yet","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"dedupe the two http clients. one has retries and the other has tracing, i want one that has both, and every caller moved over","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"swagger says the field is optional, the handler 400s without it. which one's the bug? i genuinely don't know what the intended contract is","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"nix flake for the dev env: go 1.23, node 22, protoc with the two plugins, and postgres 16 for the test harness. has to work on darwin and linux","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"quick copy fix — the empty state says \"No results found for your search\" even when the user hasn't searched yet","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"PR description for the branch, plus i want a one-paragraph summary i can paste into the release notes later","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"svelte transitions on the sidebar are janky on low-end android. currently animating width, i assume that's the problem but i want it smooth without changing the layout behavior","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"let's decide the caching strategy for the product api. i've written notes below, turn them into a real design with numbers:\n- catalog changes maybe 200 times a day, reads are ~4k rps\n- prices change more often, and staleness on price is a legal problem not just a ux one\n- we have redis already but no cdn in front of the api\n- multi-tenant, and tenant A must never see tenant B's cached page\n- there's a bulk endpoint that returns up to 500 products, which i suspect ruins any naive per-key cache\nwhat's the layering, what are the TTLs, and how do we invalidate on price change without a stampede","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"rust: the borrow checker is fighting me in the arena allocator and i can't tell if my design is wrong or i just need a lifetime annotation. cannot borrow `*self` as mutable more than once","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"explain the sharding function in pkg/ferrite/shard.go and whether adding a 5th shard rebalances everything or just moves 1/5th","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"supabase edge function for stripe webhooks. verify the signature, handle the 6 event types we care about, upsert into subscriptions, idempotent on event id","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"our error codes are documented in three places and all three disagree. pick the code as truth, write one canonical table in docs/errors.md, and note which of the other two docs to delete","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"extract the retry/backoff bits from every service into a shared package. there are 5 slightly different implementations, keep the most conservative jitter","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"svelte transitions on the sidebar are janky on low-end android. currently animating width, i assume that's the problem but i want it smooth without changing the layout behavior","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"let's decide the caching strategy for the product api. i've written notes below, turn them into a real design with numbers:\n- catalog changes maybe 200 times a day, reads are ~4k rps\n- prices change more often, and staleness on price is a legal problem not just a ux one\n- we have redis already but no cdn in front of the api\n- multi-tenant, and tenant A must never see tenant B's cached page\n- there's a bulk endpoint that returns up to 500 products, which i suspect ruins any naive per-key cache\nwhat's the layering, what are the TTLs, and how do we invalidate on price change without a stampede","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"rust: the borrow checker is fighting me in the arena allocator and i can't tell if my design is wrong or i just need a lifetime annotation. cannot borrow `*self` as mutable more than once","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain the sharding function in pkg/ferrite/shard.go and whether adding a 5th shard rebalances everything or just moves 1/5th","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"supabase edge function for stripe webhooks. verify the signature, handle the 6 event types we care about, upsert into subscriptions, idempotent on event id","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"our error codes are documented in three places and all three disagree. pick the code as truth, write one canonical table in docs/errors.md, and note which of the other two docs to delete","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"extract the retry/backoff bits from every service into a shared package. there are 5 slightly different implementations, keep the most conservative jitter","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"set log level to info in prod, someone left it on debug and we're paying for it","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"storybook stories for the 9 form components, including the error and disabled states, and a controls panel for the props that matter","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"clickhouse: the materialized view stopped updating three weeks ago and nobody noticed. inserts to the source table still land, the mv is just empty for that period","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"write up the tradeoff between doing tenant isolation with RLS vs separate schemas vs separate databases, for our size (2k tenants, biggest is 40% of the data). recommendation at the end","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"storybook stories for the 9 form components, including the error and disabled states, and a controls panel for the props that matter","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"clickhouse: the materialized view stopped updating three weeks ago and nobody noticed. inserts to the source table still land, the mv is just empty for that period","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"write up the tradeoff between doing tenant isolation with RLS vs separate schemas vs separate databases, for our size (2k tenants, biggest is 40% of the data). recommendation at the end","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} {"prompt":"add ETag + If-None-Match support to the config endpoint so the agents stop pulling 2MB every 30 seconds","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"rename everything called `blob` in the storage layer to `object` — types, methods, table columns, the metrics names. it's a naming thing, nothing behavioral","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"is it a problem that we call `time.Now()` inside the comparison instead of passing a clock? asking about testability more than correctness","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"rename everything called `blob` in the storage layer to `object` — types, methods, table columns, the metrics names. it's a naming thing, nothing behavioral","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"is it a problem that we call `time.Now()` inside the comparison instead of passing a clock? asking about testability more than correctness","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"changelog for the last 40 commits, grouped, skip the dependabot ones","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"dark mode looks fine everywhere except the pdf preview pane which is blinding white. invert or frame it, your call, but it needs to stop being a flashbang","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"load test says we fall over at 900 rps, and i want to know why before i throw instances at it. attaching the k6 summary and the pod metrics from the run:\n\n```\n ✗ status is 200\n ↳ 91% — ✓ 41205 / ✗ 3897\n\n http_req_duration..............: avg=1.42s min=41ms med=812ms max=30.01s p(95)=4.88s p(99)=21.4s\n http_req_failed................: 8.63% 3897 out of 45102\n http_reqs......................: 45102 901.2/s\n iteration_duration.............: avg=2.21s\n vus............................: 400 min=400 max=400\n\n checks.........................: 91.36%\n```\n\n```\nNAME CPU(cores) MEMORY(bytes)\nquill-api-6b8f9c7d4-2vk9x 980m 412Mi\nquill-api-6b8f9c7d4-8jd2p 1010m 398Mi\npgbouncer-5f7c8b9d6-xk4mn 120m 88Mi\n```\n\ncpu limit is 1000m per pod. is that just \"add pods\" or is something pathological","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"pasted-context","lang":"en"} +{"prompt":"dark mode looks fine everywhere except the pdf preview pane which is blinding white. invert or frame it, your call, but it needs to stop being a flashbang","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"load test says we fall over at 900 rps, and i want to know why before i throw instances at it. attaching the k6 summary and the pod metrics from the run:\n\n```\n ✗ status is 200\n ↳ 91% — ✓ 41205 / ✗ 3897\n\n http_req_duration..............: avg=1.42s min=41ms med=812ms max=30.01s p(95)=4.88s p(99)=21.4s\n http_req_failed................: 8.63% 3897 out of 45102\n http_reqs......................: 45102 901.2/s\n iteration_duration.............: avg=2.21s\n vus............................: 400 min=400 max=400\n\n checks.........................: 91.36%\n```\n\n```\nNAME CPU(cores) MEMORY(bytes)\nquill-api-6b8f9c7d4-2vk9x 980m 412Mi\nquill-api-6b8f9c7d4-8jd2p 1010m 398Mi\npgbouncer-5f7c8b9d6-xk4mn 120m 88Mi\n```\n\ncpu limit is 1000m per pod. is that just \"add pods\" or is something pathological","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} {"prompt":"小さい修正: `retry_after` の単位が秒じゃなくてミリ秒になってる。api のレスポンス側を秒に直して","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"ja"} -{"prompt":"audit the js bundle. what's the biggest thing in there that we don't need, and is moment still being pulled in by something","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"audit the js bundle. what's the biggest thing in there that we don't need, and is moment still being pulled in by something","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"dagster asset graph for the recommendations pipeline. four assets, partitioned daily, backfill-safe, and the last one writes to the feature table the api reads","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"flatten the inheritance in the exporter classes. BaseExporter -> AbstractFileExporter -> CsvExporter is two levels too many for what it does, composition instead","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"notification banner in the mac app — slides down from the titlebar, auto hides, click takes you to the relevant row. appkit not swiftui, the rest of that window is appkit","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"outline the plan for cutting our AWS bill 30% and then actually do the two easiest items on it","purpose":"planning","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"outline the plan for cutting our AWS bill 30% and then actually do the two easiest items on it","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"the docs build is fine but every internal link in the generated site has /docs/docs/ doubled up","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"write the release blog post for 5.0. big items: the new query planner, plugin api, and we finally dropped node 18. tone should be confident but not breathless","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"server side: soft delete with a 30 day grace period on documents. cascade to comments and attachments logically but not physically, and a restore endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"gimme the rundown on lib/cinderblock, i inherited it and there's no readme","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"spacing on the invoice line items is inconsistent — some rows 8px, some 12px. make them all 10px","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.15,"slice":"boundary","lang":"en"} -{"prompt":"reorganize the monorepo. currently apps/, packages/, and a `shared/` that's neither. i want a target layout and the moves done with git history preserved where possible","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"our chart legend truncates series names with no tooltip so users see \"Enterprise – Nor…\" and \"Enterprise – Nort…\" and can't tell them apart","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"vou precisar de um plano de migração dos jobs do sidekiq pro solid_queue. temos 40 workers, alguns com retry customizado, e não podemos parar a fila","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"pt"} -{"prompt":"intermittent 401s from the mobile client, maybe 1 in 200 requests, and retrying works. clock skew? token cache? i can't reproduce it on demand","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"write the release blog post for 5.0. big items: the new query planner, plugin api, and we finally dropped node 18. tone should be confident but not breathless","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"server side: soft delete with a 30 day grace period on documents. cascade to comments and attachments logically but not physically, and a restore endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"gimme the rundown on lib/cinderblock, i inherited it and there's no readme","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"spacing on the invoice line items is inconsistent — some rows 8px, some 12px. make them all 10px","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"reorganize the monorepo. currently apps/, packages/, and a `shared/` that's neither. i want a target layout and the moves done with git history preserved where possible","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"our chart legend truncates series names with no tooltip so users see \"Enterprise – Nor…\" and \"Enterprise – Nort…\" and can't tell them apart","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"vou precisar de um plano de migração dos jobs do sidekiq pro solid_queue. temos 40 workers, alguns com retry customizado, e não podemos parar a fila","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"pt"} +{"prompt":"intermittent 401s from the mobile client, maybe 1 in 200 requests, and retrying works. clock skew? token cache? i can't reproduce it on demand","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"openapi -> typescript client generation as part of the build, and check the generated file in so diffs are visible in PRs","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"what's the difference between `sync` and `syncNow` in the swift package, and which one should i be calling from the background task","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"add the missing type hints to analytics/*.py and write proper docstrings while you're at it. mypy strict should pass after","purpose":"writing","secondary":"refactor","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"just make the button blue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"vague-eval","lang":"en"} +{"prompt":"what's the difference between `sync` and `syncNow` in the swift package, and which one should i be calling from the background task","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"add the missing type hints to analytics/*.py and write proper docstrings while you're at it. mypy strict should pass after","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"just make the button blue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} {"prompt":"command palette for the web app — fuzzy search over commands and recent docs, cmd+k, arrow nav, and it should feel instant with 3k items","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"spike doc: can we serve the ML model from the edge? 40MB onnx, 30ms budget, and we'd need the tokenizer there too. tell me if it's plausible and what the shape would be","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"rewrite the git history? no. but do move the four `utils.ts` files into one `lib/` with named modules, nothing else","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} +{"prompt":"rewrite the git history? no. but do move the four `utils.ts` files into one `lib/` with named modules, nothing else","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"the CSV export writes \\r\\n on linux and \\n on mac because we use the platform default. pick \\r\\n always, excel users are the ones who care","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"grpc health checking + graceful shutdown in the go services. drain in-flight, stop accepting, deregister from consul, 15s max","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the last 4 releases each broke something in the mobile client and i want to know if the api contract is the problem or the client's assumptions are. read both sides and tell me","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} +{"prompt":"the last 4 releases each broke something in the mobile client and i want to know if the api contract is the problem or the client's assumptions are. read both sides and tell me","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"docs for the CLI's config file. every key, the type, the default, the env var equivalent, and precedence order. generate it from the struct tags if you can, otherwise by hand","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"app crashes on launch on iPad only, portrait only:\n\n```\n*** Terminating app due to uncaught exception 'NSInternalInconsistencyException',\nreason: 'Attempting to load the view of a view controller while it is deallocating\nis not allowed and may result in undefined behavior ()'\n\n0 CoreFoundation __exceptionPreprocess + 172\n1 libobjc.A.dylib objc_exception_throw + 56\n2 Foundation -[NSAssertionHandler handleFailureInMethod:...] + 216\n3 UIKitCore -[UIViewController loadViewIfRequired] + 1244\n4 UIKitCore -[UIViewController view] + 28\n5 SwiftUI SplitViewHost.updateHostedViews() + 412\n6 Sandpiper SidebarContainer.body.getter + 88\n7 Sandpiper RootScene.body.getter + 204\n```\n\nnothing in RootScene changed this release, but we did move the sidebar selection into an @Observable model","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"long press on a message opens the reaction picker, six emoji + a plus, and the picker should flip above the bubble if it's near the bottom","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"figure out the right way to do zero-downtime column type changes on our biggest table (bigint -> uuid on 400M rows) and write the runbook for it","purpose":"planning","secondary":"writing","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"the `Deploy` button is enabled while a deploy is in flight, so people double-click it and we get two deploys","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"batch insert path for the metrics writer. currently one insert per point, want batches of 500 or 200ms whichever first, with backpressure to the caller","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"does the code in workers/reaper.ts actually handle the case where the row was already deleted by another worker, or is it relying on the delete being idempotent by luck","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"clean up the imports across web/src — there's a mix of relative and alias paths, sometimes in the same file. standardize on the @/ alias","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"summarize this incident channel into a timeline i can put in the postmortem:\n\n```\n14:02 robb pages went off, api error rate 40%\n14:03 robb looking\n14:05 ani grafana shows db connections maxed, 800/800\n14:06 robb nothing deployed since 11:40\n14:08 ani there's a query doing a seq scan on events, 40s, hundreds of them\n14:09 ani it's the new /reports/export endpoint. shipped at 11:40.\n14:11 robb killing the long runners\n14:12 robb connections down to 300, error rate falling\n14:14 ani error rate back to baseline\n14:16 robb we should feature flag that endpoint off\n14:19 ani flag off, deployed\n14:31 ani confirmed stable for 15m. the missing index is on events(workspace_id, created_at)\n14:52 robb index created concurrently, took 8 min\n15:05 ani re-enabled the endpoint at 10%, latency looks fine\n15:40 ani 100%, closing this out\n```","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} -{"prompt":"settings screen on watchOS. three rows, a toggle, and it has to sync with the phone app's defaults","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"zod schemas for all 22 api responses, generated from the openapi if possible, and used at the fetch boundary so bad payloads fail loudly","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"look at how we handle the case where a user is deleted while they have an active session. i suspect nothing handles it and i'd like to know before a customer finds out","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"app crashes on launch on iPad only, portrait only:\n\n```\n*** Terminating app due to uncaught exception 'NSInternalInconsistencyException',\nreason: 'Attempting to load the view of a view controller while it is deallocating\nis not allowed and may result in undefined behavior ()'\n\n0 CoreFoundation __exceptionPreprocess + 172\n1 libobjc.A.dylib objc_exception_throw + 56\n2 Foundation -[NSAssertionHandler handleFailureInMethod:...] + 216\n3 UIKitCore -[UIViewController loadViewIfRequired] + 1244\n4 UIKitCore -[UIViewController view] + 28\n5 SwiftUI SplitViewHost.updateHostedViews() + 412\n6 Sandpiper SidebarContainer.body.getter + 88\n7 Sandpiper RootScene.body.getter + 204\n```\n\nnothing in RootScene changed this release, but we did move the sidebar selection into an @Observable model","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"long press on a message opens the reaction picker, six emoji + a plus, and the picker should flip above the bubble if it's near the bottom","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"figure out the right way to do zero-downtime column type changes on our biggest table (bigint -> uuid on 400M rows) and write the runbook for it","purpose":"planning","secondary":"writing","mixed":true,"difficulty":1,"slice":"mixed","lang":"en"} +{"prompt":"the `Deploy` button is enabled while a deploy is in flight, so people double-click it and we get two deploys","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"batch insert path for the metrics writer. currently one insert per point, want batches of 500 or 200ms whichever first, with backpressure to the caller","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"does the code in workers/reaper.ts actually handle the case where the row was already deleted by another worker, or is it relying on the delete being idempotent by luck","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"clean up the imports across web/src — there's a mix of relative and alias paths, sometimes in the same file. standardize on the @/ alias","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"summarize this incident channel into a timeline i can put in the postmortem:\n\n```\n14:02 robb pages went off, api error rate 40%\n14:03 robb looking\n14:05 ani grafana shows db connections maxed, 800/800\n14:06 robb nothing deployed since 11:40\n14:08 ani there's a query doing a seq scan on events, 40s, hundreds of them\n14:09 ani it's the new /reports/export endpoint. shipped at 11:40.\n14:11 robb killing the long runners\n14:12 robb connections down to 300, error rate falling\n14:14 ani error rate back to baseline\n14:16 robb we should feature flag that endpoint off\n14:19 ani flag off, deployed\n14:31 ani confirmed stable for 15m. the missing index is on events(workspace_id, created_at)\n14:52 robb index created concurrently, took 8 min\n15:05 ani re-enabled the endpoint at 10%, latency looks fine\n15:40 ani 100%, closing this out\n```","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"settings screen on watchOS. three rows, a toggle, and it has to sync with the phone app's defaults","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"zod schemas for all 22 api responses, generated from the openapi if possible, and used at the fetch boundary so bad payloads fail loudly","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"look at how we handle the case where a user is deleted while they have an active session. i suspect nothing handles it and i'd like to know before a customer finds out","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} {"prompt":"everything's broken again","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"phased plan to get the frontend off jQuery. 60 pages, some of them are just forms, a few have real interactivity. we can't do a big bang and we ship weekly","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"shorten the truncation on the breadcrumb from 30 chars to 20","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"core","lang":"en"} -{"prompt":"swap our custom debounce for the one in the utils package, it's the same implementation and one of them has a bug with leading edge","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} +{"prompt":"shorten the truncation on the breadcrumb from 30 chars to 20","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"swap our custom debounce for the one in the utils package, it's the same implementation and one of them has a bug with leading edge","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"sse endpoint for build logs with heartbeat comments every 20s so proxies don't kill it, plus last-event-id resume","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"gantt-ish view for the deploy pipeline stages — horizontal bars, live durations ticking, failed stages in red with the error inline","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"help text for `roundhouse migrate --help` is a wall of text. rewrite it: one line summary, grouped flags, two examples at the bottom","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"restore from the nightly backup produced a db that's 40% smaller than prod and i can't figure out what's missing. pg_dump/pg_restore, custom format, and the restore reported no errors","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"review the migration in db/migrations/0142_split_addresses.sql for anything that'll lock the table longer than a second","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"picking up the search relevance work from last sprint. plan the eval harness — golden queries, judgments, the metric, and how it gates a model change in CI","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the api key input shows the full key after save. mask it except the last 4","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.25,"slice":"boundary","lang":"en"} -{"prompt":"gradle: split the `core` module's build.gradle.kts, it configures 6 things that belong in convention plugins. build outputs identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"background upload with progress on android — workmanager, resumable, survives process death, and notification with a cancel action","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"tooltip on the disabled submit button explaining why it's disabled, because right now people just click it repeatedly","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"readme is out of date in like six places and there's a section about a feature we removed. rewrite it top to bottom against what the code actually does now","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"the pagination is off by a page somewhere between the api and the ui. api says total 240, page size 25, ui renders 9 page buttons and the last one is empty","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"walk me through what happens on `kelpstack up` from the first line of main to a running stack. i want the sequence, not a code review","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} +{"prompt":"gantt-ish view for the deploy pipeline stages — horizontal bars, live durations ticking, failed stages in red with the error inline","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"help text for `roundhouse migrate --help` is a wall of text. rewrite it: one line summary, grouped flags, two examples at the bottom","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"restore from the nightly backup produced a db that's 40% smaller than prod and i can't figure out what's missing. pg_dump/pg_restore, custom format, and the restore reported no errors","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"review the migration in db/migrations/0142_split_addresses.sql for anything that'll lock the table longer than a second","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"picking up the search relevance work from last sprint. plan the eval harness — golden queries, judgments, the metric, and how it gates a model change in CI","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the api key input shows the full key after save. mask it except the last 4","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"gradle: split the `core` module's build.gradle.kts, it configures 6 things that belong in convention plugins. build outputs identical","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"background upload with progress on android — workmanager, resumable, survives process death, and notification with a cancel action","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"tooltip on the disabled submit button explaining why it's disabled, because right now people just click it repeatedly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"readme is out of date in like six places and there's a section about a feature we removed. rewrite it top to bottom against what the code actually does now","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the pagination is off by a page somewhere between the api and the ui. api says total 240, page size 25, ui renders 9 page buttons and the last one is empty","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"walk me through what happens on `kelpstack up` from the first line of main to a running stack. i want the sequence, not a code review","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"worker pool with graceful resize — grow to 64 under load, shrink to 8 idle, no dropped jobs during a resize, and expose the current size as a gauge","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"design the schema and access patterns for storing 2 years of per-minute sensor readings from 30k devices. we're on postgres now and it's already groaning at 3 months","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"reduce the motion on the page transitions, someone complained it makes them queasy and honestly they're right","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.35,"slice":"boundary","lang":"en"} -{"prompt":"s'assurer que le lock est bien relâché en cas d'exception dans jobs/reaper.py — j'ai un doute sur le try/finally","purpose":"review","secondary":null,"mixed":false,"difficulty":0.45,"slice":"boundary","lang":"fr"} -{"prompt":"collapse the 11 boolean flags on the User model into a `preferences` jsonb with a typed accessor layer. same defaults, same behavior, migration included","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"commit message. it's a fix for the double-charge thing plus a test","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"design the schema and access patterns for storing 2 years of per-minute sensor readings from 30k devices. we're on postgres now and it's already groaning at 3 months","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"reduce the motion on the page transitions, someone complained it makes them queasy and honestly they're right","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"s'assurer que le lock est bien relâché en cas d'exception dans jobs/reaper.py — j'ai un doute sur le try/finally","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"fr"} +{"prompt":"collapse the 11 boolean flags on the User model into a `preferences` jsonb with a typed accessor layer. same defaults, same behavior, migration included","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"commit message. it's a fix for the double-charge thing plus a test","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"cron entry is `0 */4 * * *` but the job needs to run at 2am and 2pm only","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"user reports: \"the app logs me out randomly.\" i have three reports, all android, all on wifi->cellular transitions as far as i can tell. no server side session expiry in the logs at those times","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"user reports: \"the app logs me out randomly.\" i have three reports, all android, all on wifi->cellular transitions as far as i can tell. no server side session expiry in the logs at those times","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"tree view for the file browser, lazy load children, keyboard nav, and multi-select with shift/cmd. it'll hold maybe 20k nodes at the extreme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"webhook signature verification helper published as a tiny package for our customers, plus the docs page showing it in node, python and ruby","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"assess whether we can drop the redis dependency entirely. it's used for sessions, the rate limiter, and one cache. tell me what each would cost us to move","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the thing with the flags","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"assess whether we can drop the redis dependency entirely. it's used for sessions, the rate limiter, and one cache. tell me what each would cost us to move","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} {"prompt":"translate the error messages in i18n/en.json to de and fr. tone should be formal-ish for de, and keep the placeholders intact","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"cut the bundle: code split the admin routes, they're 300kb of the 480kb main chunk and 2% of users see them","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"im starting the tenant offboarding feature. plan it first — data export, hard delete after 30 days, the legal hold exception, and how we prove deletion happened","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"set `strict: true` in tsconfig and fix the fallout. there'll be a few hundred errors, work through them without changing runtime behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.75,"slice":"boundary","lang":"en"} -{"prompt":"the avatar images 404 for users who signed up before march. i think the url template changed and we never backfilled","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.45,"slice":"boundary","lang":"en"} +{"prompt":"cut the bundle: code split the admin routes, they're 300kb of the 480kb main chunk and 2% of users see them","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"im starting the tenant offboarding feature. plan it first — data export, hard delete after 30 days, the legal hold exception, and how we prove deletion happened","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"set `strict: true` in tsconfig and fix the fallout. there'll be a few hundred errors, work through them without changing runtime behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the avatar images 404 for users who signed up before march. i think the url template changed and we never backfilled","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"GET /v1/usage with from/to, group_by=day|hour, and a `metric` filter. reads from the rollup table, falls back to raw for today, and caps the range at 90 days","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"tell me whether the code in packages/pellet/src/merge.ts is a correct CRDT merge or just something that looks like one. i wrote it 8 months ago and i no longer trust myself","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"polish pass on the invoice pdf template — alignment on the totals column, the logo is 4px off center, and the footer legal text should be 8pt gray","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"one paragraph for the docs homepage that says what this product does without any marketing words. i've rewritten it four times and hate all of them","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} +{"prompt":"polish pass on the invoice pdf template — alignment on the totals column, the logo is 4px off center, and the footer legal text should be 8pt gray","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"one paragraph for the docs homepage that says what this product does without any marketing words. i've rewritten it four times and hate all of them","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"the deploy workflow needs GH_TOKEN swapped for the new PAT secret name DEPLOY_PAT","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"kmp: move the networking and models into the shared module for ios and android, keeping both apps' current behavior exactly","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"so the kmp question. we have an android app in kotlin and an ios app in swift with the same 40 api calls and the same models written twice, and they've drifted enough that two bugs last month were 'the ios one does it differently'. i want the plan: what we share, what we don't, and how much build pain we're signing up for","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"shared repository layer in kmp with ktor, coroutines exposed to swift as async, and a sqldelight cache","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"shared repository layer in kmp with ktor, coroutines exposed to swift as async, and a sqldelight cache","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} {"prompt":"the ios build takes 9 minutes because the kmp framework rebuilds every time","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the shared module's version is pinned to a kotlin version older than the android app's","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"explain how our shared coroutine scopes get cancelled from the swift side, i don't trust that they do","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"write the shared module's readme: what belongs in it, what doesn't, how to add a model, and the swift interop gotchas","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the shared module's version is pinned to a kotlin version older than the android app's","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"explain how our shared coroutine scopes get cancelled from the swift side, i don't trust that they do","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"write the shared module's readme: what belongs in it, what doesn't, how to add a model, and the swift interop gotchas","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"the ios app crashes with a kotlin exception that surfaces as NSGenericException with no useful message","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"error mapping from the shared layer into idiomatic errors on each platform, so swift gets a typed error not a generic throw","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"postgis: nearest-neighbour query for 'stores within 20km, sorted by distance', fast at 400k stores","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the distance query uses ST_Distance on geometry not geography so the results are wrong by a few percent depending on latitude","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"error mapping from the shared layer into idiomatic errors on each platform, so swift gets a typed error not a generic throw","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"postgis: nearest-neighbour query for 'stores within 20km, sorted by distance', fast at 400k stores","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the distance query uses ST_Distance on geometry not geography so the results are wrong by a few percent depending on latitude","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"store locator map: clustered pins, a list synced to the viewport, and 'use my location' with a graceful denial path","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the locator returns stores in the wrong hemisphere for users with negative longitudes","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the locator returns stores in the wrong hemisphere for users with negative longitudes","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"plan the territory management feature — polygons per sales rep, overlap detection, and assignment of an address to a territory at scale","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"our geometry columns use three different srids across tables and we transform ad hoc in queries. normalize on 4326 with the transforms at the edges, same query results","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"review our spatial indexes and tell me which queries aren't using them","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"geospatial data doc: our srids, the units we store distances in, and the conventions for lat/lng ordering because everyone gets it backwards","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"review our spatial indexes and tell me which queries aren't using them","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"geospatial data doc: our srids, the units we store distances in, and the conventions for lat/lng ordering because everyone gets it backwards","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"territory polygon editor: draw, edit vertices, snap to boundaries, and warn on overlap with another territory","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"webgl: the product configurator needs to load a 40mb gltf without freezing the tab, with a progressive reveal","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the three.js scene leaks memory when you switch products, about 30mb each time","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the configurator renders at devicePixelRatio 3 on phones and melts them","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"asset pipeline for the 3d models: draco compression, ktx2 textures, and lods generated at build time","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"our three material setups are duplicated per product type with copy-pasted shader code. one material system with parameters, visually identical renders","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"webgl: the product configurator needs to load a 40mb gltf without freezing the tab, with a progressive reveal","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the three.js scene leaks memory when you switch products, about 30mb each time","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the configurator renders at devicePixelRatio 3 on phones and melts them","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"asset pipeline for the 3d models: draco compression, ktx2 textures, and lods generated at build time","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"our three material setups are duplicated per product type with copy-pasted shader code. one material system with parameters, visually identical renders","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"map out how we'd support ar viewing on top of the configurator, ios and android, and what the model requirements become","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"sure keep going","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"here's what the analytics show for the configurator and it's making me rethink the whole thing:\n\nSessions reaching configurator: 41,200\n Model load started: 41,200\n Model load completed: 26,900 (65%)\n First interaction (rotate/zoom): 19,400 (47%)\n Changed a variant: 11,100 (27%)\n Added to cart: 2,900 (7%)\n\nMedian time to model loaded: 8.4s\n p75: 14.1s\n p90: 31.0s\n\nDrop-off before load completes, by connection type:\n 4g: 48%\n wifi: 19%\n 3g/slow: 81%\n\nDevice: 62% mobile\n\na third of people never see the thing at all. i want the plan for what we do about this","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"static hero render as the initial view with the interactive model loading behind it, so the page is useful in a second","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"prerendered turntable images per variant, generated at build time, as the low-bandwidth fallback","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"we load all variants' textures upfront, load only the selected one","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"static hero render as the initial view with the interactive model loading behind it, so the page is useful in a second","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"prerendered turntable images per variant, generated at build time, as the low-bandwidth fallback","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"we load all variants' textures upfront, load only the selected one","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"connection-aware quality selection using the network information api with a manual override","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"review the configurator's asset loading order and tell me what's on the critical path that shouldn't be","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"write the asset authoring guidelines for the 3d team: polygon budgets, texture sizes, and the naming convention the pipeline expects","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the loading indicator shows 0% until the whole file arrives","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"plan the performance budget for the configurator page and how we enforce it as the 3d team adds models","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"asset size checks in CI that fail the build when a model exceeds the budget, with the report saying which mesh grew","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"one product's model is 40mb and the others are 3mb, and nobody noticed for two months","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"review the configurator's asset loading order and tell me what's on the critical path that shouldn't be","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"write the asset authoring guidelines for the 3d team: polygon budgets, texture sizes, and the naming convention the pipeline expects","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the loading indicator shows 0% until the whole file arrives","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"plan the performance budget for the configurator page and how we enforce it as the 3d team adds models","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"asset size checks in CI that fail the build when a model exceeds the budget, with the report saying which mesh grew","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"one product's model is 40mb and the others are 3mb, and nobody noticed for two months","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"variant switching ui: swatches, an active indicator, and the change should apply without a visible reload of the scene","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"switching variants resets the camera position","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"explain how our variant state maps to the cart line item, and whether a shared url reproduces the exact configuration","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"shareable configuration urls that encode the variant state compactly and survive a variant being discontinued","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"switching variants resets the camera position","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"explain how our variant state maps to the cart line item, and whether a shared url reproduces the exact configuration","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"shareable configuration urls that encode the variant state compactly and survive a variant being discontinued","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} {"prompt":"our configurator state lives in a react context, a url param and a zustand store, all partially. one source of truth, same behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"shared configuration links from six months ago render the wrong product","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"documentation of the configuration url format for the marketing team who want to link to preset configs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"plan the configurator's accessibility — it's a canvas, so what does keyboard and screen reader support even look like","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"find the memory leak in the scene switching and then note the pattern in the frontend guidelines","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"next up","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"shared configuration links from six months ago render the wrong product","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"documentation of the configuration url format for the marketing team who want to link to preset configs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"plan the configurator's accessibility — it's a canvas, so what does keyboard and screen reader support even look like","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"find the memory leak in the scene switching and then note the pattern in the frontend guidelines","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"the routing data situation. we buy road network data, load it into postgis, and build a routing graph nightly. the load takes 11 hours and the graph build another 4, so a data update is a two-day operation and we've stopped doing them monthly. i want the plan to get this to something we can run weekly, including whether we should be using a purpose-built routing engine instead","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"parallel loader for the road network by tile, with each tile's load independent and resumable","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the loader inserts row by row with autocommit","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"parallel loader for the road network by tile, with each tile's load independent and resumable","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the loader inserts row by row with autocommit","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"data load progress view: tiles by state, throughput, and an estimated completion that isn't a lie","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"our geometry simplification runs at load time in the loader and again in the tile server with different tolerances. pick one, do it once, same rendered tiles","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the graph build produces a graph with 400 disconnected components and last month it was 12","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"read the graph build and tell me how it decides two road segments connect, because i suspect it's coordinate equality","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"write the data update runbook: the steps, the validation gates, and how to roll back to the previous graph","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"graph validation gates — connectivity, a set of known routes that must still resolve, and travel time sanity checks","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"routes across one metro area got 40% longer after the last data update and nobody caught it for a week","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"vector tile server for the road network with caching, so the map isn't rendering from raw geometry","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"tiles at zoom 14+ take 3 seconds each","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the tile cache has no max age so a data update doesn't invalidate anything","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"plan how we serve historical graph versions so a route computed last month can be reproduced for a dispute","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain how we version the routing graph today and whether an old route can be recomputed identically","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"routing api documentation: the parameters, what the returned geometry represents, the travel time model, and the accuracy caveats","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"isochrone endpoint — reachable area in 15/30/45 minutes as polygons, cached per origin grid cell","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"isochrone polygons have self-intersections that break the client's rendering","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"isochrone overlay on the map with three bands, semi-transparent, and a legend","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"die Isochronen-Farben sind fast identisch, mach sie unterscheidbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"de"} -{"prompt":"our coordinate parsing accepts lat,lng in one endpoint and lng,lat in another, matching neither convention consistently. standardize, and add a compatibility period","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"check whether our address geocoder can return a result in the wrong country for an ambiguous input","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"geocoding with a country bias, a confidence score, and a clear 'we're not sure' state rather than a wrong answer","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"address input with autocomplete, a map pin the user can drag to correct it, and the corrected coordinate saved","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"vale, sigamos","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"es"} -{"prompt":"ok the mobile release process is killing us. two apps, two stores, manual version bumps in four places, screenshots regenerated by hand, and release notes written twice. every release takes a day of someone's time and we ship monthly because of it. i want the plan for automating this end to end, including the bits the stores won't let us automate","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the graph build produces a graph with 400 disconnected components and last month it was 12","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"read the graph build and tell me how it decides two road segments connect, because i suspect it's coordinate equality","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"write the data update runbook: the steps, the validation gates, and how to roll back to the previous graph","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"graph validation gates — connectivity, a set of known routes that must still resolve, and travel time sanity checks","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"routes across one metro area got 40% longer after the last data update and nobody caught it for a week","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"vector tile server for the road network with caching, so the map isn't rendering from raw geometry","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"tiles at zoom 14+ take 3 seconds each","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the tile cache has no max age so a data update doesn't invalidate anything","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"plan how we serve historical graph versions so a route computed last month can be reproduced for a dispute","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"explain how we version the routing graph today and whether an old route can be recomputed identically","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"routing api documentation: the parameters, what the returned geometry represents, the travel time model, and the accuracy caveats","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"isochrone endpoint — reachable area in 15/30/45 minutes as polygons, cached per origin grid cell","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"isochrone polygons have self-intersections that break the client's rendering","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"isochrone overlay on the map with three bands, semi-transparent, and a legend","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"die Isochronen-Farben sind fast identisch, mach sie unterscheidbar","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"de"} +{"prompt":"our coordinate parsing accepts lat,lng in one endpoint and lng,lat in another, matching neither convention consistently. standardize, and add a compatibility period","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"check whether our address geocoder can return a result in the wrong country for an ambiguous input","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"geocoding with a country bias, a confidence score, and a clear 'we're not sure' state rather than a wrong answer","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"address input with autocomplete, a map pin the user can drag to correct it, and the corrected coordinate saved","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"ok the mobile release process is killing us. two apps, two stores, manual version bumps in four places, screenshots regenerated by hand, and release notes written twice. every release takes a day of someone's time and we ship monthly because of it. i want the plan for automating this end to end, including the bits the stores won't let us automate","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"release automation: version derived from the tag, build and upload to both stores, and the release notes pulled from the changelog","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the version is defined in build.gradle, Info.plist, a constants file and the api's minimum-version check, independently","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"screenshot generation from ui tests, all locales and device sizes, with the status bar faked consistently","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"generated screenshots show the debug banner","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"release dashboard: what's in flight per store, the review status, the staged rollout percentage, and crash rate on the new version","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the crash-free rate shown is for all versions combined","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the version is defined in build.gradle, Info.plist, a constants file and the api's minimum-version check, independently","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"screenshot generation from ui tests, all locales and device sizes, with the status bar faked consistently","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"generated screenshots show the debug banner","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"release dashboard: what's in flight per store, the review status, the staged rollout percentage, and crash rate on the new version","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the crash-free rate shown is for all versions combined","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"builds succeed locally and fail in CI with a provisioning profile error that changes every few weeks","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"explain how our CI gets its signing certificates and what happens when one expires","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"mobile release runbook, with the manual steps clearly marked and the store-review turnaround expectations","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"staged rollout automation — start at 5%, hold on a crash rate regression, and promote on a schedule if healthy","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the rollout promoted to 100% despite a crash rate 4x the previous version","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"explain how our CI gets its signing certificates and what happens when one expires","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"mobile release runbook, with the manual steps clearly marked and the store-review turnaround expectations","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"staged rollout automation — start at 5%, hold on a crash rate regression, and promote on a schedule if healthy","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the rollout promoted to 100% despite a crash rate 4x the previous version","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"plan the minimum-supported-version policy — how we force an upgrade, the warning period, and what an unsupported client sees","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"force-upgrade gate in the app driven by a server response, with a soft warning period first","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"force-upgrade gate in the app driven by a server response, with a soft warning period first","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"force-upgrade screen with the store link, what's new, and no way to dismiss it","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"the force-upgrade check runs after the auth call, so unsupported clients see an auth error first","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"review our minimum version enforcement — can a client skip it by not calling the endpoint that returns the gate","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"user-facing copy for the upgrade prompts, soft and hard variants, that doesn't sound like a threat","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"crash reporting with the symbols uploaded automatically per build, so we're not looking at hex addresses","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"symbols aren't uploaded for the last three releases so all our crashes are unsymbolicated","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"keep it up","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"here's the crash cluster that appeared with 4.2, i can't reproduce it and the reports are thin:\n\nCrashlytics issue: 8f21a — 2,140 users, 4,880 crashes, all on 4.2.0\nFatal Exception: kotlin.UninitializedPropertyAccessException\nlateinit property syncCoordinator has not been initialized\n\n at com.acme.field.sync.SyncService.onStartCommand(SyncService.kt:64)\n at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:4712)\n at android.os.Handler.dispatchMessage(Handler.java:106)\n\nDevice breakdown: 94% Android 14+, no single manufacturer\nMemory state: 71% of crashes report \"low memory\" true\nForeground: 8% (so mostly background)\nTime since app start: median 4.2 hours\n\n4.2 moved the sync service to a foreground service","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"make the sync service resilient to process death — reinitialize its dependencies in onStartCommand rather than relying on application state","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"symbols aren't uploaded for the last three releases so all our crashes are unsymbolicated","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"here's the crash cluster that appeared with 4.2, i can't reproduce it and the reports are thin:\n\nCrashlytics issue: 8f21a — 2,140 users, 4,880 crashes, all on 4.2.0\nFatal Exception: kotlin.UninitializedPropertyAccessException\nlateinit property syncCoordinator has not been initialized\n\n at com.acme.field.sync.SyncService.onStartCommand(SyncService.kt:64)\n at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:4712)\n at android.os.Handler.dispatchMessage(Handler.java:106)\n\nDevice breakdown: 94% Android 14+, no single manufacturer\nMemory state: 71% of crashes report \"low memory\" true\nForeground: 8% (so mostly background)\nTime since app start: median 4.2 hours\n\n4.2 moved the sync service to a foreground service","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"make the sync service resilient to process death — reinitialize its dependencies in onStartCommand rather than relying on application state","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"our lateinit-in-application pattern appears in 12 services and every one of them is this bug waiting to happen. move to proper injection with lazy resolution, same behavior when the process is alive","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the service is started with startService not startForegroundService in one path","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"review every entry point into the app for whether it assumes Application.onCreate already ran with our state intact","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"write the android process lifecycle notes for the team — what survives process death, what doesn't, and the patterns we use","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the service is started with startService not startForegroundService in one path","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"review every entry point into the app for whether it assumes Application.onCreate already ran with our state intact","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"write the android process lifecycle notes for the team — what survives process death, what doesn't, and the patterns we use","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"plan the background work strategy properly — what's a foreground service, what's workmanager, and what we do about the OEMs that kill everything","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"sync notification for the foreground service that's informative rather than a permanent 'Syncing' with no detail","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the foreground notification says 'Acme is running' which users find creepy","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"background sync stops entirely on some xiaomi devices after a day","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"sync notification for the foreground service that's informative rather than a permanent 'Syncing' with no detail","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the foreground notification says 'Acme is running' which users find creepy","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"background sync stops entirely on some xiaomi devices after a day","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"device-specific battery optimization guidance surfaced in the app, only on the affected manufacturers, with a deep link to the setting","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"explain how our sync decides it's been too long since the last successful run, and whether the user is ever told","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain how our sync decides it's been too long since the last successful run, and whether the user is ever told","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"stale-data warning in the app when sync hasn't succeeded in 24 hours, with a manual sync action","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"support doc for field users whose data isn't syncing: the three things to check, in order","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"support doc for field users whose data isn't syncing: the three things to check, in order","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"sync telemetry so we can see, per device, when sync last succeeded and why it failed","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"sync health view per customer: devices, last successful sync, and the failure reason distribution","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"sync health view per customer: devices, last successful sync, and the failure reason distribution","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"the last-sync timestamp is the attempt time not the success time","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"plan the offline conflict resolution for field data, then implement the merge for the simple field types","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"look at the sync service and clean up the initialization mess","purpose":"review","secondary":"refactor","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"next thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"look at the sync service and clean up the initialization mess","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"propose how we do multi-language support in the shared kmp module. the strings currently live in android resources and a swift Localizable file, translated separately, and the two apps say different things for the same error. i want one source with the platform formatting still working properly","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"shared string resources in kmp generating both android xml and swift string catalogs from one source","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"shared string resources in kmp generating both android xml and swift string catalogs from one source","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"our error messages are built in the shared layer for some cases and per-platform for others, so the same failure reads differently. one message catalog, consistent copy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"plurals break in polish because we generate a simple one/other from the shared source","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the generated swift strings file isn't added to the xcode project so new strings silently fall back to the key","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"review our string generation for whether a missing translation fails the build or ships as the key","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"localization guide for the shared module: adding a string, plurals, placeholders, and how translations flow in","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"date and number formatting in the shared layer using the platform locale, with the results verified against the platform's own formatters","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"dates in the shared layer format as US style on both platforms regardless of locale","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"plurals break in polish because we generate a simple one/other from the shared source","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"the generated swift strings file isn't added to the xcode project so new strings silently fall back to the key","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"review our string generation for whether a missing translation fails the build or ships as the key","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"localization guide for the shared module: adding a string, plurals, placeholders, and how translations flow in","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"date and number formatting in the shared layer using the platform locale, with the results verified against the platform's own formatters","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"dates in the shared layer format as US style on both platforms regardless of locale","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"settings screen for language override, per app, defaulting to the system language","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the language list shows locale codes not language names","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"plan how we handle right-to-left in both apps given the shared layer knows nothing about layout direction","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"explain how the shared module gets the current locale on each platform, and what happens when the user changes it while the app is running","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"translation contribution guide for our external translators: the file format, the placeholder rules, and the context notes we provide","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"pseudo-locale build for both apps to catch hardcoded strings and layout overflow before translation","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the pseudo-locale build shows 140 hardcoded strings in the ios app","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"figure out the shared strings approach then implement the generator","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"that's enough, just finish the small thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"the language list shows locale codes not language names","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"plan how we handle right-to-left in both apps given the shared layer knows nothing about layout direction","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"explain how the shared module gets the current locale on each platform, and what happens when the user changes it while the app is running","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"translation contribution guide for our external translators: the file format, the placeholder rules, and the context notes we provide","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"pseudo-locale build for both apps to catch hardcoded strings and layout overflow before translation","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the pseudo-locale build shows 140 hardcoded strings in the ios app","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"figure out the shared strings approach then implement the generator","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"the claims batch. spring batch, 40 steps, runs nightly, takes 6 hours and if step 31 fails we restart the whole thing because the restart logic was never finished. i'd like the plan for making it properly restartable and getting the runtime down, with an honest read on whether spring batch is still the right tool","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"restartable steps with proper checkpointing so a failure at step 31 resumes at 31, not step 1","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"restartable steps with proper checkpointing so a failure at step 31 resumes at 31, not step 1","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"batch monitoring page: steps with status and duration, the failed step highlighted, and a restart-from-here action","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the chunk size is 1 for every reader","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"our 40 steps each build their own datasource and transaction manager. one configuration, same transactional behavior per step","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the batch fails about twice a month with a lock timeout on the claims table and always around 3am","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"could you explain what step 24 does? it's called ProcessAdjustments, it's 900 lines, and the person who wrote it left in 2019","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"document the nightly batch: what each step does, its inputs and outputs, the dependencies between them, and what breaks downstream if one is skipped","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"claim status transitions as an explicit state machine with the allowed transitions declared, replacing the scattered if-chains","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"a claim can go from Paid back to Pending through one code path and nobody knows if that's intentional","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"claims queue for adjusters: assigned claims, sortable by age and value, with the sla clock visible per claim","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the sla clock counts weekends","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"our 40 steps each build their own datasource and transaction manager. one configuration, same transactional behavior per step","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the batch fails about twice a month with a lock timeout on the claims table and always around 3am","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"could you explain what step 24 does? it's called ProcessAdjustments, it's 900 lines, and the person who wrote it left in 2019","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"document the nightly batch: what each step does, its inputs and outputs, the dependencies between them, and what breaks downstream if one is skipped","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"claim status transitions as an explicit state machine with the allowed transitions declared, replacing the scattered if-chains","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"a claim can go from Paid back to Pending through one code path and nobody knows if that's intentional","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"claims queue for adjusters: assigned claims, sortable by age and value, with the sla clock visible per claim","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the sla clock counts weekends","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"would you plan the claims api we'd expose to broker partners? read and submit, with the document upload, and the authorization model given brokers act on behalf of policyholders","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"document upload for claims with virus scanning, a page count limit, and the file associated to the claim atomically","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"uploaded documents occasionally attach to the wrong claim when an adjuster has two tabs open","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"review our claim authorization — can a broker see a claim for a policy they don't represent","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"broker api documentation: authentication, the claim submission payload, the document upload flow, and the status values with their meanings","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"imap client: idle support so new mail arrives without polling, and it must survive a server that drops the idle connection every 5 minutes","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"the client re-downloads the whole mailbox when the uidvalidity changes, which some servers do daily","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"the imap fetch requests full bodies for the message list","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"message list ui: threaded, unread emphasis, a snippet from the body, and it stays smooth at 50k messages","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"our mime parsing handles multipart in the list view and again in the reader with different assumptions about nesting. one parser, same rendered messages","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"plan the offline mail store — what we sync, the eviction policy, and how a search covers messages we haven't downloaded","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"explain how our threading algorithm works and why it splits some conversations — i suspect it's References vs In-Reply-To","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"document upload for claims with virus scanning, a page count limit, and the file associated to the claim atomically","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"uploaded documents occasionally attach to the wrong claim when an adjuster has two tabs open","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"review our claim authorization — can a broker see a claim for a policy they don't represent","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"broker api documentation: authentication, the claim submission payload, the document upload flow, and the status values with their meanings","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"imap client: idle support so new mail arrives without polling, and it must survive a server that drops the idle connection every 5 minutes","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the client re-downloads the whole mailbox when the uidvalidity changes, which some servers do daily","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the imap fetch requests full bodies for the message list","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"message list ui: threaded, unread emphasis, a snippet from the body, and it stays smooth at 50k messages","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"our mime parsing handles multipart in the list view and again in the reader with different assumptions about nesting. one parser, same rendered messages","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"plan the offline mail store — what we sync, the eviction policy, and how a search covers messages we haven't downloaded","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"explain how our threading algorithm works and why it splits some conversations — i suspect it's References vs In-Reply-To","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} {"prompt":"here's the bug report from the accessibility audit of the benefits application form, this is a legal requirement for us:\n\nSeverity: Blocker (WCAG 2.2 AA)\n1. The 14-step form has no way to know which step you're on with a screen reader — the step\n indicator is a set of divs with color only.\n2. Validation errors appear at the top of the page as a plain div; focus stays where it was\n and nothing is announced.\n3. The \"date of birth\" field is three separate inputs with a single visual label and no\n programmatic association.\n4. The session times out after 20 minutes with no warning; users with cognitive\n disabilities are losing 40 minutes of work.\n5. Required fields are indicated by red text only.\n6. The \"upload evidence\" control is a styled div with a click handler.\n\nRemediation required before the service can go live.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"session timeout warning at 2 minutes remaining, with an extend action, announced to assistive tech","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"session timeout warning at 2 minutes remaining, with an extend action, announced to assistive tech","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"required fields need a text indicator not just red","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"error summary component that receives focus on submit, lists the errors as links to the fields, and is announced","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the date of birth should be one fieldset with a legend and three labelled inputs","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"server-side session extension endpoint, and the draft saved on every step so a timeout doesn't lose the form","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"error summary component that receives focus on submit, lists the errors as links to the fields, and is announced","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the date of birth should be one fieldset with a legend and three labelled inputs","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"server-side session extension endpoint, and the draft saved on every step so a timeout doesn't lose the form","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"our form components are a mix of native inputs and styled divs with click handlers, inconsistently. move everything to native elements, same visual design","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"plan the accessibility remediation for the whole service, prioritized by the audit severity, with the go-live date in mind","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"review the remaining 12 form steps for the same patterns the audit found in the first two","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"accessibility statement for the service, in the format the regulator requires, honest about the known issues and their fix dates","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"step indicator that's a proper ordered list with the current step marked programmatically, and 'Step 4 of 14' as text","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"form draft autosave every 20 seconds and on step change, resumable from any device the user logs in from","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"plan the accessibility remediation for the whole service, prioritized by the audit severity, with the go-live date in mind","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"review the remaining 12 form steps for the same patterns the audit found in the first two","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"accessibility statement for the service, in the format the regulator requires, honest about the known issues and their fix dates","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"step indicator that's a proper ordered list with the current step marked programmatically, and 'Step 4 of 14' as text","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"form draft autosave every 20 seconds and on step change, resumable from any device the user logs in from","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"drafts save but resuming lands on step 1 with the data present, which is confusing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the autosave indicator says 'Saving...' permanently after the first save","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"explain how the form's conditional steps work — which answers skip which steps, from the code, because the spec and the behavior disagree","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"content guide for the form: reading level target, how we phrase questions, and the error message patterns","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the autosave indicator says 'Saving...' permanently after the first save","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"explain how the form's conditional steps work — which answers skip which steps, from the code, because the spec and the behavior disagree","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"content guide for the form: reading level target, how we phrase questions, and the error message patterns","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"plan how we test this form with actual assistive technology as part of CI or at least a release gate","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"automated accessibility checks on all 14 steps with the form filled at each stage, since half the issues only appear in an error state","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the a11y checks run on the empty form only and pass","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"plan the remediation and then fix the error summary as the first piece","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"work out why drafts resume on step 1 and then update the service manual","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} -{"prompt":"next one","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"automated accessibility checks on all 14 steps with the form filled at each stage, since half the issues only appear in an error state","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the a11y checks run on the empty form only and pass","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"plan the remediation and then fix the error summary as the first piece","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"work out why drafts resume on step 1 and then update the service manual","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} {"prompt":"would you propose the architecture for the eligibility rules engine? the rules come from legislation, change a few times a year, and have to be applied as of the date of the claim not the date we process it. also caseworkers need to be able to explain to a claimant exactly why they got the answer they got","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"rules engine with rules versioned by effective date, evaluated against the claim date, producing a trace of which rules fired","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"decision explanation screen: the outcome, then each rule that contributed with the claimant's values shown against the threshold","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the explanation shows rule ids not descriptions","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"our eligibility logic exists in the java service and again in a spreadsheet the policy team maintains, and they disagree on two thresholds. make the code derive from a single declared ruleset, and report which decisions change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"claims submitted before a rule change but processed after get the new rules applied","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"read the eligibility code and tell me which rules are hardcoded constants versus configurable","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"write the rules documentation mapping each legislative clause to the implementing rule, for the policy team to verify","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"rules test harness with cases derived from the legislation's own worked examples, run in CI","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"three of the legislation's worked examples produce a different answer in our engine","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"rules admin ui for the policy team: view the active ruleset, the thresholds and their effective dates, read only for now","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the effective dates display in the ui as timestamps with a timezone","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"rules engine with rules versioned by effective date, evaluated against the claim date, producing a trace of which rules fired","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"decision explanation screen: the outcome, then each rule that contributed with the claimant's values shown against the threshold","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the explanation shows rule ids not descriptions","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"our eligibility logic exists in the java service and again in a spreadsheet the policy team maintains, and they disagree on two thresholds. make the code derive from a single declared ruleset, and report which decisions change","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"claims submitted before a rule change but processed after get the new rules applied","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"read the eligibility code and tell me which rules are hardcoded constants versus configurable","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"write the rules documentation mapping each legislative clause to the implementing rule, for the policy team to verify","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"rules test harness with cases derived from the legislation's own worked examples, run in CI","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"three of the legislation's worked examples produce a different answer in our engine","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"rules admin ui for the policy team: view the active ruleset, the thresholds and their effective dates, read only for now","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the effective dates display in the ui as timestamps with a timezone","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"plan how a rule change gets from legislation to production — who authors, who verifies, how it's tested, and the audit trail","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"check whether a decision can be recomputed identically six months later, including the rules and reference data as they were","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"appeals process doc from the system's perspective: what we store, how a decision is reviewed, and what a reversal does to the record","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"decision recomputation endpoint that replays a claim against any ruleset version and diffs the outcome","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"recomputing an old decision uses today's reference data, which makes the whole thing pointless","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"続きをお願いします。次はルールのバージョン管理の実装から","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"} -{"prompt":"letter generation for decisions — the outcome, the reasons, the appeal rights, in plain language and in the claimant's preferred language and format","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the generated letters are 6 pages because we include every rule considered rather than the ones that mattered","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"letter templates rewritten in plain language at the reading level our content standards require, with the legal content intact","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"check whether a decision can be recomputed identically six months later, including the rules and reference data as they were","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"appeals process doc from the system's perspective: what we store, how a decision is reviewed, and what a reversal does to the record","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"decision recomputation endpoint that replays a claim against any ruleset version and diffs the outcome","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"recomputing an old decision uses today's reference data, which makes the whole thing pointless","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"letter generation for decisions — the outcome, the reasons, the appeal rights, in plain language and in the claimant's preferred language and format","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the generated letters are 6 pages because we include every rule considered rather than the ones that mattered","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"letter templates rewritten in plain language at the reading level our content standards require, with the legal content intact","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"letter preview for caseworkers with the merge fields resolved, before it goes out","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"unresolved merge fields print as {{claimant_name}} in the posted letters","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"unresolved merge fields print as {{claimant_name}} in the posted letters","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"our letter templates are duplicated per channel (post, email, portal) with the content drifting. one content source, three renderings","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"ok go on","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"the email client's search. currently it's a LIKE query against the locally cached bodies, which means it's slow, misses anything not downloaded, and can't do anything structured like from:x has:attachment. i want the plan — local index, server-side search via imap, or both — and how they combine into one result list that doesn't confuse people","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"local full text index over downloaded messages, incremental on sync, with the structured operators parsed into filters","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"search ui with the query parsed into visible chips so people can see how we interpreted it, and results that stream in","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"search treats a quoted phrase as separate words","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"our search operator parsing exists in the local search and the server search path with different syntax support. one parser, and document which operators each backend can honor","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"results from the server search and the local index interleave with duplicates and different ordering","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain how our index handles a message being deleted on the server — does the index entry go, and when","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"search syntax help for users: the operators we support, what's searched locally vs on the server, and the limits","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"the email client's search. currently it's a LIKE query against the locally cached bodies, which means it's slow, misses anything not downloaded, and can't do anything structured like from:x has:attachment. i want the plan — local index, server-side search via imap, or both — and how they combine into one result list that doesn't confuse people","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"local full text index over downloaded messages, incremental on sync, with the structured operators parsed into filters","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"search ui with the query parsed into visible chips so people can see how we interpreted it, and results that stream in","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"search treats a quoted phrase as separate words","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"our search operator parsing exists in the local search and the server search path with different syntax support. one parser, and document which operators each backend can honor","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"results from the server search and the local index interleave with duplicates and different ordering","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"explain how our index handles a message being deleted on the server — does the index entry go, and when","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"search syntax help for users: the operators we support, what's searched locally vs on the server, and the limits","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"attachment search — index the text of pdfs and office documents locally, with a size cap and a way to skip encrypted ones","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"indexing attachments pegs the cpu for 20 minutes after a big sync","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"indexing attachments pegs the cpu for 20 minutes after a big sync","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"the index runs at normal priority and makes the app unusable while it works","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"plan the index storage budget — how big it gets for a 100k message mailbox and what we evict first","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"storage settings screen: what the app is using, split by messages, attachments and index, with an option to reduce it","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"the storage figure doesn't include the index, so it under-reports by 40%","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"review our sync strategy for a mailbox with 200k messages — what we download, in what order, and when the user can start using it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"documentation of the local store schema and the sync state machine, for whoever picks this up next","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"priority sync — newest 2000 messages and anything in the inbox first, the rest in the background","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the initial sync downloads oldest-first so a new user sees 2009 emails for an hour","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"plan the multi-account support — separate stores, a unified inbox, and per-account settings that don't leak","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"unified inbox view merging accounts with the account indicated per row, and per-account filters","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"replying from the unified inbox sometimes sends from the wrong account","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"review our sync strategy for a mailbox with 200k messages — what we download, in what order, and when the user can start using it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"documentation of the local store schema and the sync state machine, for whoever picks this up next","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"priority sync — newest 2000 messages and anything in the inbox first, the rest in the background","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the initial sync downloads oldest-first so a new user sees 2009 emails for an hour","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"plan the multi-account support — separate stores, a unified inbox, and per-account settings that don't leak","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"unified inbox view merging accounts with the account indicated per row, and per-account filters","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"replying from the unified inbox sometimes sends from the wrong account","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"our account state is held in a singleton that the compose screen reads, which is the multi-account bug waiting to happen. pass the account explicitly everywhere, same behavior with one account","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"check whether a draft composed under one account can be sent under another after an account switch","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"keep going please","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"check whether a draft composed under one account can be sent under another after an account switch","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} {"prompt":"here's the mail server interop matrix we built by testing, and it's the reason i want to talk about strategy:\n\n IDLE CONDSTORE QRESYNC MOVE SEARCH(FUZZY) THREAD\n gmail y y y y n y\n outlook365 y y n y n n\n fastmail y y y y y y\n dovecot 2.3 y y y y n y\n courier y n n n n n\n exchange 2016 y n n y n n\n yahoo y n n n n n\n cpanel/dovecot y y n y n y\n\nour code currently assumes CONDSTORE and falls back badly when it's absent — full resync.\ni want the plan for capability-driven behavior with a graceful path for the worst servers","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"capability detection and per-server strategy selection, with the fallback path for no-CONDSTORE servers doing an incremental resync not a full one","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"our sync code branches on server hostname in four places to work around specific servers. replace with capability checks, same behavior per server in the matrix","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"capability detection and per-server strategy selection, with the fallback path for no-CONDSTORE servers doing an incremental resync not a full one","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"our sync code branches on server hostname in four places to work around specific servers. replace with capability checks, same behavior per server in the matrix","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the capability list is fetched before login so we miss capabilities only advertised after authentication","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"server compatibility documentation: which features work per provider, and what a user on a limited server should expect","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"review our error handling when a server rejects a command we thought it supported","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"account setup with autodiscovery from the domain, falling back to a manual form with sensible guesses prefilled","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"server compatibility documentation: which features work per provider, and what a user on a limited server should expect","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"review our error handling when a server rejects a command we thought it supported","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"account setup with autodiscovery from the domain, falling back to a manual form with sensible guesses prefilled","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"setup wizard that explains what's happening at each step and doesn't ask for the port number unless it has to","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the manual setup form defaults to port 143 with no tls","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"account setup fails for one provider with 'authentication failed' when the real problem is an app password requirement","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"provider-specific setup help surfaced at the point of failure, for the six providers that need app passwords","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the manual setup form defaults to port 143 with no tls","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"account setup fails for one provider with 'authentication failed' when the real problem is an app password requirement","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"provider-specific setup help surfaced at the point of failure, for the six providers that need app passwords","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"plan our oauth support for the providers that offer it, so people stop needing app passwords","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain what we do with a stored password today and whether it's in the platform keychain or our own file","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain what we do with a stored password today and whether it's in the platform keychain or our own file","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"security documentation for the mail client: where credentials live, what's encrypted, and what a device compromise exposes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"oauth token refresh in the background before expiry, with a clear re-auth prompt when the refresh token dies","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"oauth token refresh in the background before expiry, with a clear re-auth prompt when the refresh token dies","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"oauth accounts silently stop syncing after 6 months with no prompt","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"our credential storage has a keychain path and a plaintext fallback for when the keychain is unavailable. remove the fallback, and handle the unavailable case properly","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"design the capability abstraction then implement the CONDSTORE fallback","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"explain the sync state machine and then write it up properly","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"one last thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"our credential storage has a keychain path and a plaintext fallback for when the keychain is unavailable. remove the fallback, and handle the unavailable case properly","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"design the capability abstraction then implement the CONDSTORE fallback","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"explain the sync state machine and then write it up properly","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} {"prompt":"propose how we structure the caseworker audit trail. every view, edit and decision, attributable, and it has to satisfy both the data protection requirement (claimants can ask who looked at their case) and the internal fraud team's needs. currently we log nothing on reads","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"read auditing on the claim endpoints with the caseworker identity and the reason, without adding a write to the hot path","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"who-accessed-my-case report for a claimant subject access request, generated as a pdf","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the audit report includes internal system accounts which means nothing to a claimant","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"audit search for the fraud team: by caseworker, by claim, by time window, with an export","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the audit search times out for windows longer than a week","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"review whether a caseworker can view a claim outside their region, and whether we'd know","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the audit report includes internal system accounts which means nothing to a claimant","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"audit search for the fraud team: by caseworker, by claim, by time window, with an export","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the audit search times out for windows longer than a week","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"review whether a caseworker can view a claim outside their region, and whether we'd know","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"audit trail documentation for the data protection officer: what's recorded, retention, who can query it, and the gaps","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"anomaly detection over the audit log — a caseworker viewing an unusual number of claims, or claims outside their caseload","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the anomaly detector flags the entire night shift because their pattern differs from days","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"our access logging is in a filter for the api and a manual call in the batch jobs, and the batch ones don't log at all. one mechanism, coverage everywhere","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"anomaly detection over the audit log — a caseworker viewing an unusual number of claims, or claims outside their caseload","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the anomaly detector flags the entire night shift because their pattern differs from days","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"our access logging is in a filter for the api and a manual call in the batch jobs, and the batch ones don't log at all. one mechanism, coverage everywhere","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} {"prompt":"plan the audit log's retention and archival — 7 years, and it grows at 40gb a month","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"audit records for one week in march are missing entirely","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain what happens if the audit write fails — does the operation proceed","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"audit integrity — hash chaining so tampering is detectable, with the verification job","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"internal doc on the audit log's integrity guarantees and how to verify a range","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"the audit table has no index on the caseworker id","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"audit records for one week in march are missing entirely","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain what happens if the audit write fails — does the operation proceed","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"audit integrity — hash chaining so tampering is detectable, with the verification job","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"internal doc on the audit log's integrity guarantees and how to verify a range","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the audit table has no index on the caseworker id","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} {"prompt":"design the audit architecture then build the read-logging middleware","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"alright, stopping after this","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"- matching engine, limit + market orders\n- price-time priority\n- must be deterministic and replayable from the order log\n- target 50k orders/sec on one core\n- and the risk checks have to happen before the order enters the book\n\nwrite the design first, i don't want anyone writing rust until we agree","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"order book with price-time priority, an intrusive list per price level, and no allocation on the hot path","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"order book depth view: bids and asks, aggregated by level, updating live without the rows jumping around","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the tick size is hardcoded 0.01 for every market","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"our order validation happens in the api and again in the engine with different rounding on the price. one validation, and tell me which orders would now be rejected","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"replaying the order log produces a different final book state than the live run, about one in ten replays","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"read the matching loop and tell me whether a self-trade is possible for an account with orders on both sides","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"matching engine specification doc: the order types, the priority rules, the exact tie-breaking, and what's guaranteed about determinism","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"pre-trade risk checks — balance, position limits, and a max order value — evaluated before the order reaches the book, with a rejection reason","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"an account can go negative on balance if two orders fill in the same batch","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"the position limit check reads a cached balance that's up to 500ms stale","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"order book with price-time priority, an intrusive list per price level, and no allocation on the hot path","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"order book depth view: bids and asks, aggregated by level, updating live without the rows jumping around","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the tick size is hardcoded 0.01 for every market","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"our order validation happens in the api and again in the engine with different rounding on the price. one validation, and tell me which orders would now be rejected","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"replaying the order log produces a different final book state than the live run, about one in ten replays","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"read the matching loop and tell me whether a self-trade is possible for an account with orders on both sides","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"matching engine specification doc: the order types, the priority rules, the exact tie-breaking, and what's guaranteed about determinism","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"pre-trade risk checks — balance, position limits, and a max order value — evaluated before the order reaches the book, with a rejection reason","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"an account can go negative on balance if two orders fill in the same batch","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the position limit check reads a cached balance that's up to 500ms stale","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} {"prompt":"trade history screen with filters, csv export, and the fee breakdown per fill","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"plan the settlement side — how a fill becomes a balance change, the ledger entries, and how we reconcile with the custody provider daily","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"explain how fees are computed and where they're recorded, because the trade history and the statement disagree by a small amount","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"fee schedule documentation: maker/taker, the volume tiers, when a tier change takes effect, and the rounding","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"explain how fees are computed and where they're recorded, because the trade history and the statement disagree by a small amount","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"fee schedule documentation: maker/taker, the volume tiers, when a tier change takes effect, and the rounding","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"music metadata ingestion from three suppliers, each with a different schema, deduped by isrc with a fallback to fuzzy matching on title+artist+duration","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the dedupe merges two genuinely different recordings that share a title and duration","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the dedupe merges two genuinely different recordings that share a title and duration","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"the isrc comparison is case sensitive and one supplier sends lowercase","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"catalog browse ui: artist, album, track hierarchy with the artwork, and it should feel instant on a slow connection","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"our three supplier parsers each normalize artist names differently, which is why the same artist appears four times. one normalizer, and report the merges it would cause","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"catalog browse ui: artist, album, track hierarchy with the artwork, and it should feel instant on a slow connection","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"our three supplier parsers each normalize artist names differently, which is why the same artist appears four times. one normalizer, and report the merges it would cause","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"plan the metadata authority model — when suppliers disagree on a track's release date, whose wins, and how an editor overrides it permanently","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"review our matching logic and tell me the false-merge rate we'd expect on a catalog of 40 million recordings","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"metadata schema documentation: our canonical model, how each supplier's fields map in, and the precedence rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"editor tool for merging and splitting artist records, with a preview of the affected tracks and an undo","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"here's the supplier delivery report, this is our biggest data quality headache and i cant see the pattern:\n\nDelivery 2026-07-29 (Supplier B, 412,880 recordings)\n Accepted: 388,201\n Rejected — missing ISRC: 18,004\n Rejected — invalid duration: 4,112 (duration = 0 or > 86400)\n Rejected — no artist: 1,880\n Rejected — encoding error: 683\n Merged into existing: 204,118\n Created new: 184,083\n\nOf the 204,118 merges:\n by ISRC exact: 181,004\n by fuzzy (title+artist+dur): 23,114 <- these worry me\n\nSpot check of 50 fuzzy merges: 6 were wrong (12%)\n\nof the 6 wrong: 4 were live versions merged into the studio recording, 2 were covers\nmerged into the original","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"fuzzy matching that treats live/remix/cover markers as blocking signals rather than noise to strip","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the title normalizer strips '(Live)' and '(Remix)' before comparing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"human review queue for low-confidence merges with the two candidates side by side and audio previews","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"plan how we measure and improve match quality — a labeled set, precision/recall targets, and a regression gate on the matcher","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"match quality evaluation harness against a labeled set, reporting precision and recall per match strategy","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"review our rejection reasons and tell me which of the 18k missing-ISRC rejections we could have matched anyway","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"supplier delivery report doc: the fields we require, the validation rules, and what our rejection codes mean","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"unmerge capability — reverse a bad merge and restore both records with their original supplier data intact","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"unmerging loses the supplier fields that only existed on the absorbed record","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"delivery dashboard per supplier: volume, acceptance rate, and the rejection reason breakdown over time","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the acceptance rate chart includes merges as rejections","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"explain how a supplier's correction to a previously delivered track propagates — does it update the merged record or create a new one","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"metadata schema documentation: our canonical model, how each supplier's fields map in, and the precedence rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"editor tool for merging and splitting artist records, with a preview of the affected tracks and an undo","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"here's the supplier delivery report, this is our biggest data quality headache and i cant see the pattern:\n\nDelivery 2026-07-29 (Supplier B, 412,880 recordings)\n Accepted: 388,201\n Rejected — missing ISRC: 18,004\n Rejected — invalid duration: 4,112 (duration = 0 or > 86400)\n Rejected — no artist: 1,880\n Rejected — encoding error: 683\n Merged into existing: 204,118\n Created new: 184,083\n\nOf the 204,118 merges:\n by ISRC exact: 181,004\n by fuzzy (title+artist+dur): 23,114 <- these worry me\n\nSpot check of 50 fuzzy merges: 6 were wrong (12%)\n\nof the 6 wrong: 4 were live versions merged into the studio recording, 2 were covers\nmerged into the original","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"fuzzy matching that treats live/remix/cover markers as blocking signals rather than noise to strip","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the title normalizer strips '(Live)' and '(Remix)' before comparing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"human review queue for low-confidence merges with the two candidates side by side and audio previews","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"plan how we measure and improve match quality — a labeled set, precision/recall targets, and a regression gate on the matcher","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"match quality evaluation harness against a labeled set, reporting precision and recall per match strategy","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"review our rejection reasons and tell me which of the 18k missing-ISRC rejections we could have matched anyway","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"supplier delivery report doc: the fields we require, the validation rules, and what our rejection codes mean","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"unmerge capability — reverse a bad merge and restore both records with their original supplier data intact","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"unmerging loses the supplier fields that only existed on the absorbed record","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"delivery dashboard per supplier: volume, acceptance rate, and the rejection reason breakdown over time","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the acceptance rate chart includes merges as rejections","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"explain how a supplier's correction to a previously delivered track propagates — does it update the merged record or create a new one","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"plan the rights and territory data model — who can play what where, with the windows, since this drives the whole product","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"rights evaluation at play time: territory, window, and the licence type, with a trace of why something was blocked","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"tracks appear in search but fail at play time with a generic error in three territories","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"unavailable tracks should be shown greyed with a reason rather than hidden or erroring","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"our rights check runs in the catalog api, the playback api and the recommendation job with three interpretations of an open-ended window. one implementation, and report which tracks change availability","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"design the rights model then implement the territory evaluation","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"figure out why the fuzzy merges go wrong and then write the supplier guidance note","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"rights evaluation at play time: territory, window, and the licence type, with a trace of why something was blocked","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"tracks appear in search but fail at play time with a generic error in three territories","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"unavailable tracks should be shown greyed with a reason rather than hidden or erroring","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"our rights check runs in the catalog api, the playback api and the recommendation job with three interpretations of an open-ended window. one implementation, and report which tracks change availability","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"design the rights model then implement the territory evaluation","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"figure out why the fuzzy merges go wrong and then write the supplier guidance note","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"the workflow builder. users drag nodes onto a canvas to automate things, and it's our most-loved and most-broken feature. state is a mess, undo doesn't work reliably, and a workflow with 60 nodes drops to 5fps. i want the plan for a rebuild that keeps the saved workflows working","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"canvas rendering that stays smooth at 200 nodes — virtualize what's offscreen, and don't rerender the world on a drag","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"undo/redo over the workflow graph as an explicit command stack, covering node moves, edge changes and property edits","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the delete key deletes the selected node even when focus is in a text field","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"our workflow state lives in a react context, a ref for the canvas positions, and localstorage for the draft, and they desync. one store, same saved output","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"dragging a node sometimes teleports it to 0,0 and only after you've zoomed","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"read the graph serialization and tell me whether an old saved workflow can express something the new editor can't represent","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"workflow format documentation: the node schema, edge semantics, versioning, and what a third party would need to generate one","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"workflow execution engine: topological order, per-node retry, and a run log with the input and output of each node","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"a workflow with a cycle hangs the executor instead of being rejected","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"cycle detection at save time with the offending path highlighted on the canvas","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the run log stores every node's full output, including 40mb payloads","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"canvas rendering that stays smooth at 200 nodes — virtualize what's offscreen, and don't rerender the world on a drag","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"undo/redo over the workflow graph as an explicit command stack, covering node moves, edge changes and property edits","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the delete key deletes the selected node even when focus is in a text field","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"our workflow state lives in a react context, a ref for the canvas positions, and localstorage for the draft, and they desync. one store, same saved output","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"dragging a node sometimes teleports it to 0,0 and only after you've zoomed","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"read the graph serialization and tell me whether an old saved workflow can express something the new editor can't represent","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"workflow format documentation: the node schema, edge semantics, versioning, and what a third party would need to generate one","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"workflow execution engine: topological order, per-node retry, and a run log with the input and output of each node","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"a workflow with a cycle hangs the executor instead of being rejected","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"cycle detection at save time with the offending path highlighted on the canvas","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"the run log stores every node's full output, including 40mb payloads","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"plan the versioning of workflows — users edit a live workflow and we run it mid-edit, which is obviously wrong","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"published versus draft workflow versions, with runs pinned to the version that was live when they started","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"editing a workflow while a run is in progress changes the run's behavior halfway through","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain what our executor does when a node's config references a field that no longer exists on the trigger payload","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"editing a workflow while a run is in progress changes the run's behavior halfway through","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"explain what our executor does when a node's config references a field that no longer exists on the trigger payload","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"run history view: runs with status and duration, expandable to the per-node timeline with inputs and outputs","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"user documentation for the workflow builder: the node types, how data flows between them, and the three gotchas people always hit","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"expression language for node inputs — reference upstream outputs, simple transforms, no arbitrary code, with autocomplete from the actual upstream schema","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"expression autocomplete suggests fields that don't exist on the current trigger","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the expression editor is a plain text input with no syntax highlighting or validation","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"expression reference doc: the syntax, the available functions, the type rules, and what happens on a null","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"user documentation for the workflow builder: the node types, how data flows between them, and the three gotchas people always hit","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"expression language for node inputs — reference upstream outputs, simple transforms, no arbitrary code, with autocomplete from the actual upstream schema","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"expression autocomplete suggests fields that don't exist on the current trigger","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the expression editor is a plain text input with no syntax highlighting or validation","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"expression reference doc: the syntax, the available functions, the type rules, and what happens on a null","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"our expression evaluation happens client side for the preview and server side at run time, with different function sets. one implementation shared, same results in preview and run","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"check whether an expression can reach data from another user's workflow through a shared helper","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"ok next thing please","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"check whether an expression can reach data from another user's workflow through a shared helper","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} {"prompt":"withdrawals. right now a withdrawal is a row in a table and a manual approval in an admin screen, and one person can approve their own. i want the design for something we can defend in an audit: limits, multi-party approval above a threshold, address allowlists with a time delay, and a full trail","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"withdrawal approval workflow with two-person approval over a threshold, and the requester barred from approving","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"withdrawal approval workflow with two-person approval over a threshold, and the requester barred from approving","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"withdrawal queue for the ops team: pending requests, the approval state, the risk flags, and an approve/reject with a required note","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the approve button is enabled for the requester","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"address allowlist with a 24 hour delay before a new address can be used, and an email notification when one is added","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the allowlist delay is bypassed if the address was ever used before, even years ago on a different account","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"review our withdrawal path for anywhere a single compromised account could move funds without a second party","purpose":"review","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"withdrawal controls documentation for the auditor: the limits, the approval matrix, the delays, and what's logged","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"our balance checks happen at request time and again at execution with a gap of minutes, and nothing holds the funds in between. implement a hold, same accepted withdrawals","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"a withdrawal executed after the balance had been spent elsewhere, taking the account negative","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"withdrawal limits per account per day, configurable per tier, enforced across all channels including the api","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the daily limit resets at midnight utc which is mid-afternoon for our biggest market","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the approve button is enabled for the requester","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"address allowlist with a 24 hour delay before a new address can be used, and an email notification when one is added","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the allowlist delay is bypassed if the address was ever used before, even years ago on a different account","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"review our withdrawal path for anywhere a single compromised account could move funds without a second party","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"withdrawal controls documentation for the auditor: the limits, the approval matrix, the delays, and what's logged","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"our balance checks happen at request time and again at execution with a gap of minutes, and nothing holds the funds in between. implement a hold, same accepted withdrawals","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"a withdrawal executed after the balance had been spent elsewhere, taking the account negative","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"withdrawal limits per account per day, configurable per tier, enforced across all channels including the api","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the daily limit resets at midnight utc which is mid-afternoon for our biggest market","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"user-facing withdrawal screen with the limits shown, the address allowlist state, and a clear explanation of the delay","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"plan the reconciliation between our ledger and the custody provider — daily, automated, with a defined process when it doesn't balance","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"explain what our system does today if the custody provider reports a balance lower than our ledger","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"reconciliation break procedure doc: how we investigate, who's informed, and what we freeze while it's open","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"automated daily reconciliation with a break report and withdrawals paused automatically on an unexplained discrepancy","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"reconciliation reports a break every day that turns out to be in-flight transfers, so everyone ignores the report","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"nuestro cálculo de comisiones difiere entre el ledger y el extracto del cliente. quiero el análisis primero, sin cambiar nada","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"es"} -{"prompt":"reconciliation dashboard: balances by asset, our ledger vs custody, the break amount, and the aging of open breaks","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the break amount displays with 8 decimal places for fiat","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"our asset precision is a per-asset constant in one service and a database column in another, and they disagree for two assets","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"plan the reconciliation between our ledger and the custody provider — daily, automated, with a defined process when it doesn't balance","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"explain what our system does today if the custody provider reports a balance lower than our ledger","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"reconciliation break procedure doc: how we investigate, who's informed, and what we freeze while it's open","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"automated daily reconciliation with a break report and withdrawals paused automatically on an unexplained discrepancy","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"reconciliation reports a break every day that turns out to be in-flight transfers, so everyone ignores the report","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"nuestro cálculo de comisiones difiere entre el ledger y el extracto del cliente. quiero el análisis primero, sin cambiar nada","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"es"} +{"prompt":"reconciliation dashboard: balances by asset, our ledger vs custody, the break amount, and the aging of open breaks","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the break amount displays with 8 decimal places for fiat","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"our asset precision is a per-asset constant in one service and a database column in another, and they disagree for two assets","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"statement generation per account per month, immutable once issued, matching the ledger exactly","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"statements for one month show a closing balance that doesn't match the next month's opening","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"keep at it then","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"here's what our biggest customer sent about the workflow builder, i want to work through all of it:\n\n\"Feedback after 6 months of heavy use (we have 340 workflows):\n\n1. There's no way to see which workflows use a given integration. When we rotated our\n Slack token, 40 workflows broke and we found them one at a time.\n2. No folders or tags. 340 workflows in one alphabetical list.\n3. A workflow that errors just... stops. No notification unless someone checks.\n4. We can't test a workflow without triggering it for real. We've sent test invoices to\n actual customers twice.\n5. Copy/paste between workflows doesn't exist, so we rebuild the same 6 nodes constantly.\n6. Version history would save us. Someone edited a workflow last week and we can't tell what changed.\n\nWe love this feature, which is why the gaps hurt.\"","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"reverse dependency lookup — which workflows reference a given integration, credential or subworkflow","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"statements for one month show a closing balance that doesn't match the next month's opening","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"here's what our biggest customer sent about the workflow builder, i want to work through all of it:\n\n\"Feedback after 6 months of heavy use (we have 340 workflows):\n\n1. There's no way to see which workflows use a given integration. When we rotated our\n Slack token, 40 workflows broke and we found them one at a time.\n2. No folders or tags. 340 workflows in one alphabetical list.\n3. A workflow that errors just... stops. No notification unless someone checks.\n4. We can't test a workflow without triggering it for real. We've sent test invoices to\n actual customers twice.\n5. Copy/paste between workflows doesn't exist, so we rebuild the same 6 nodes constantly.\n6. Version history would save us. Someone edited a workflow last week and we can't tell what changed.\n\nWe love this feature, which is why the gaps hurt.\"","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"reverse dependency lookup — which workflows reference a given integration, credential or subworkflow","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"workflow list with folders, tags, search, and a filter by the integration used","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"failure notifications per workflow with a per-workflow recipient setting, and a digest rather than one email per failure","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"there's no notification setting at all for workflow failures","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"test mode that runs a workflow with mocked outbound calls, showing what would have been sent per node","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"test run panel showing the mocked calls with their payloads, and a clear banner that nothing was actually sent","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"there's no notification setting at all for workflow failures","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"test mode that runs a workflow with mocked outbound calls, showing what would have been sent per node","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"test run panel showing the mocked calls with their payloads, and a clear banner that nothing was actually sent","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"copy and paste of node selections between workflows, preserving the internal edges and warning about broken references","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"workflow version history with a diff view and a restore, and the author recorded per version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"version diff for a graph is meaningless as a text diff, we need a structural one","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"review our credential storage and tell me whether rotating one requires editing every workflow that uses it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"credentials referenced by id rather than embedded, so a rotation updates one record, and migrate the existing embedded ones","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"reusable subworkflows so the same six nodes aren't rebuilt everywhere, with a versioned reference","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"write the reply to that customer, item by item, honest about what's coming and what isn't","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"plan the workflow organization features — folders, tags, ownership, and permissions per workflow","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"explain what happens today when two people edit the same workflow at once","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"workflow version history with a diff view and a restore, and the author recorded per version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"version diff for a graph is meaningless as a text diff, we need a structural one","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"review our credential storage and tell me whether rotating one requires editing every workflow that uses it","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"credentials referenced by id rather than embedded, so a rotation updates one record, and migrate the existing embedded ones","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"reusable subworkflows so the same six nodes aren't rebuilt everywhere, with a versioned reference","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"plan the workflow organization features — folders, tags, ownership, and permissions per workflow","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"explain what happens today when two people edit the same workflow at once","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"concurrent edit protection — a lock or a merge, but not the current silent last-write-wins","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"design the subworkflow feature then build the reference resolution","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"review the executor and tidy the retry duplication","purpose":"review","secondary":"refactor","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"and finally","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"propose how we expose the workflow engine as an api so customers can trigger and monitor runs programmatically. includes the trigger, run status, cancelling, and how a long-running workflow reports progress. also rate limits, because someone will loop it","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"run trigger endpoint with an idempotency key, returning a run id, plus status and cancel endpoints","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"cancelling a run leaves the currently executing node running to completion with no way to tell","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"api reference for the run api: triggering, the status values, cancellation semantics, and the rate limits","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"the trigger endpoint has no rate limit at all","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"webhook triggers with signature verification, a per-workflow secret, and replay protection","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"webhook trigger setup ui: the url, the secret with a reveal, a test-send, and the last received payload","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"review whether a workflow triggered by webhook can be made to run as a different user's workflow","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"run trigger endpoint with an idempotency key, returning a run id, plus status and cancel endpoints","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"cancelling a run leaves the currently executing node running to completion with no way to tell","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"api reference for the run api: triggering, the status values, cancellation semantics, and the rate limits","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the trigger endpoint has no rate limit at all","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"webhook triggers with signature verification, a per-workflow secret, and replay protection","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"webhook trigger setup ui: the url, the secret with a reveal, a test-send, and the last received payload","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"review whether a workflow triggered by webhook can be made to run as a different user's workflow","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"scheduled triggers with a timezone per workflow and correct behavior across dst","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"scheduled workflows skip a run on the spring dst transition and run twice in autumn","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"our trigger scheduling uses a cron library in the api and a different one in the worker, which is why the next-run time shown is wrong. one library, same schedules","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the next-run time shown in the ui is an hour off half the year","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"scheduled workflows skip a run on the spring dst transition and run twice in autumn","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"our trigger scheduling uses a cron library in the api and a different one in the worker, which is why the next-run time shown is wrong. one library, same schedules","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"the next-run time shown in the ui is an hour off half the year","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"plan the concurrency controls — a workflow that's already running when the next trigger fires, and per-account parallelism limits","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"a workflow triggered every minute that takes two minutes stacks up until the queue is hours behind","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"a workflow triggered every minute that takes two minutes stacks up until the queue is hours behind","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"concurrency setting per workflow: allow overlap, skip if running, or queue with a max depth","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"explain how our worker pool is shared across accounts and whether one account can starve the others","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"documentation on execution limits: run duration cap, node count, payload size, and concurrency per plan","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"explain how our worker pool is shared across accounts and whether one account can starve the others","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"documentation on execution limits: run duration cap, node count, payload size, and concurrency per plan","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"design the concurrency model then implement the per-account fairness","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"stop after this one","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"bazel migration. we have a 900k line monorepo on a homegrown make + npm setup, ci is 40 minutes, and nobody can build the whole thing locally. i want the plan with a realistic estimate and the option of not doing it","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"bazel build files for the three go services, with a remote cache configured and the ci reading from it","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the remote cache is write-enabled from developer machines","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"build times are worse with bazel than without for incremental local builds and i can't work out why","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"our build scripts have 40 environment variables that leak into build outputs, which is why nothing caches. make the builds hermetic, same artifacts produced","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"read our ci config and tell me what's actually being cached today and what's re-downloaded every run","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"build system docs: how to build a target, the cache, what hermetic means for us, and how to debug a cache miss","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"build insights dashboard: cache hit rate, slowest targets, and which targets rebuild most often","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"affected-targets detection so a PR only builds and tests what it touches","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"a one-line readme change rebuilds everything","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the affected-targets step falls back to 'build everything' whenever it errors, silently","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"plan the developer environment — one command to a working setup, and how we keep it working as the repo grows","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"rails: tenant scoping enforced at the model layer so a missing where clause can't leak across accounts","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"our 90 models each rely on the developer remembering to scope by account. introduce a default scope with an explicit escape hatch, and audit every query for a behavior change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"one endpoint returns another account's records when a specific filter combination is used","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"the tenant id comes from a request header with no verification against the session","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"review every place we read the current account and tell me which ones could be influenced by user input","purpose":"review","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"multi-tenancy documentation for the team: how scoping works, the escape hatches and when they're allowed, and the review checklist","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"account switcher for users who belong to several accounts, with the current account unmistakable","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"switching accounts leaves the previous account's data in the sidebar until you navigate","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"bazel build files for the three go services, with a remote cache configured and the ci reading from it","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"build times are worse with bazel than without for incremental local builds and i can't work out why","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"our build scripts have 40 environment variables that leak into build outputs, which is why nothing caches. make the builds hermetic, same artifacts produced","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"read our ci config and tell me what's actually being cached today and what's re-downloaded every run","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"build system docs: how to build a target, the cache, what hermetic means for us, and how to debug a cache miss","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"build insights dashboard: cache hit rate, slowest targets, and which targets rebuild most often","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"affected-targets detection so a PR only builds and tests what it touches","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"a one-line readme change rebuilds everything","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the affected-targets step falls back to 'build everything' whenever it errors, silently","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"plan the developer environment — one command to a working setup, and how we keep it working as the repo grows","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"rails: tenant scoping enforced at the model layer so a missing where clause can't leak across accounts","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"our 90 models each rely on the developer remembering to scope by account. introduce a default scope with an explicit escape hatch, and audit every query for a behavior change","purpose":"backendImpl","secondary":"review","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"one endpoint returns another account's records when a specific filter combination is used","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the tenant id comes from a request header with no verification against the session","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"review every place we read the current account and tell me which ones could be influenced by user input","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"multi-tenancy documentation for the team: how scoping works, the escape hatches and when they're allowed, and the review checklist","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"account switcher for users who belong to several accounts, with the current account unmistakable","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"switching accounts leaves the previous account's data in the sidebar until you navigate","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"watchos: complication showing today's step count and a ring, updated efficiently within the budget","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"healthkit background delivery for step updates, with the app handling being woken and doing minimal work","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the complication shows yesterday's data until you open the app","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the step goal is hardcoded 10000","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"healthkit background delivery for step updates, with the app handling being woken and doing minimal work","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the complication shows yesterday's data until you open the app","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the step goal is hardcoded 10000","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"…so the health data sync. the watch collects, the phone aggregates, our server stores it, and the numbers disagree at every layer. the watch says 8,400 steps, the phone says 8,100, our server says 7,900, and the user screenshots all three and asks which is right. i want the plan for a single defensible number, including what we do about retroactive corrections from healthkit","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"aggregation that reconciles healthkit's anchored queries properly, handling deletions and retroactive edits without double counting","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"our step totals are computed on the watch, on the phone, and server side with different bucketing. one computation, and tell me how much historical data changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"our totals include steps from both the phone and the watch for the same period","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"aggregation that reconciles healthkit's anchored queries properly, handling deletions and retroactive edits without double counting","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"our step totals are computed on the watch, on the phone, and server side with different bucketing. one computation, and tell me how much historical data changes","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"our totals include steps from both the phone and the watch for the same period","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"the anchor is stored in user defaults so a reinstall re-imports everything","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"explain how healthkit's source priority works for us and which device wins for a given sample type","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"write the data accuracy explainer for users: where the numbers come from, why devices differ, and which one we show","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain how healthkit's source priority works for us and which device wins for a given sample type","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"write the data accuracy explainer for users: where the numbers come from, why devices differ, and which one we show","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"activity detail screen: the day's chart by hour, the source device per segment, and a total that matches the health app","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the hourly chart's last bar includes the whole remaining day so it's always tallest","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the hourly chart's last bar includes the whole remaining day so it's always tallest","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"plan the privacy story for health data — what leaves the device, what we store, and how we support users who want local-only","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"local-only mode where nothing health-related is uploaded, with the features that depend on the server clearly disabled","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"in local-only mode the weekly summary still uploads","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"check every network call the app makes for whether it carries health data, and list them","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"privacy policy section on health data, specific about the categories, the purposes, and the retention","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"onboarding for the health permissions that explains why we want each one, per permission, before the system prompt","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"we request all healthkit read permissions at once including ones we never use","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"plan the trends feature — week over week, month over month, with a statement about a change only when it's meaningful and not noise","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"trend computation with a significance threshold, so we don't tell someone they improved 2% when that's within their normal variation","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"local-only mode where nothing health-related is uploaded, with the features that depend on the server clearly disabled","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"in local-only mode the weekly summary still uploads","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"check every network call the app makes for whether it carries health data, and list them","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"privacy policy section on health data, specific about the categories, the purposes, and the retention","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"onboarding for the health permissions that explains why we want each one, per permission, before the system prompt","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"we request all healthkit read permissions at once including ones we never use","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"plan the trends feature — week over week, month over month, with a statement about a change only when it's meaningful and not noise","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"trend computation with a significance threshold, so we don't tell someone they improved 2% when that's within their normal variation","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"trends screen: a sparkline per metric with the change stated in plain language, and nothing shown when there isn't enough data","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"design the health data model then implement the aggregation service","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"find out why the totals double count and then write the user-facing explanation","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"next up then","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"here's the ci timing breakdown, this is the thing i want to fix this quarter:\n\nPipeline: main (median 38m 12s over last 200 runs)\n\n setup / checkout 1m 04s\n install deps (npm) 4m 51s cache hit rate 22%\n install deps (bundler) 2m 18s cache hit rate 61%\n build web 6m 40s\n build admin 5m 12s\n rubocop 1m 44s\n eslint 2m 09s\n rspec (unit) 9m 30s (4 parallel jobs)\n rspec (system) 14m 02s (4 parallel jobs, 38 flaky-retries last week)\n jest 3m 21s\n docker build + push 4m 55s\n\n (several run in parallel; critical path is deps -> build web -> rspec system)\n\nthe npm cache hit rate of 22% is suspicious and the system specs are half our time","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"fix the npm cache key so it isn't invalidated by unrelated changes, and prove the hit rate improves","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the cache key includes the git sha","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"design the health data model then implement the aggregation service","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"find out why the totals double count and then write the user-facing explanation","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"here's the ci timing breakdown, this is the thing i want to fix this quarter:\n\nPipeline: main (median 38m 12s over last 200 runs)\n\n setup / checkout 1m 04s\n install deps (npm) 4m 51s cache hit rate 22%\n install deps (bundler) 2m 18s cache hit rate 61%\n build web 6m 40s\n build admin 5m 12s\n rubocop 1m 44s\n eslint 2m 09s\n rspec (unit) 9m 30s (4 parallel jobs)\n rspec (system) 14m 02s (4 parallel jobs, 38 flaky-retries last week)\n jest 3m 21s\n docker build + push 4m 55s\n\n (several run in parallel; critical path is deps -> build web -> rspec system)\n\nthe npm cache hit rate of 22% is suspicious and the system specs are half our time","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"fix the npm cache key so it isn't invalidated by unrelated changes, and prove the hit rate improves","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"split the system specs across 16 parallel jobs with balanced timing based on historical durations","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"our system specs each log in through the ui, which is 3 seconds per test times 400 tests. use a session helper, same coverage","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"38 flaky retries a week in the system specs, mostly on pages with an ajax load","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"review our system specs for hardcoded sleeps and tell me how much time they account for","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"ci guide for the team: what runs when, how to reproduce a failure locally, and the rule about not merging on a retry","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"our system specs each log in through the ui, which is 3 seconds per test times 400 tests. use a session helper, same coverage","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"38 flaky retries a week in the system specs, mostly on pages with an ajax load","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"review our system specs for hardcoded sleeps and tell me how much time they account for","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"ci guide for the team: what runs when, how to reproduce a failure locally, and the rule about not merging on a retry","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"flaky test tracking — record retries per test, surface the top offenders weekly, and auto-quarantine anything over a threshold","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"quarantined tests stay quarantined forever because nobody looks at the list","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"quarantined tests stay quarantined forever because nobody looks at the list","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"test health dashboard: flakiest tests, slowest tests, and the quarantine list with an age per entry","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the dashboard's flake rate is computed over all time so a fixed test stays red forever","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"plan how we get feedback on a PR in under 5 minutes, even if the full suite still takes 20","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"fast-feedback job that runs the tests touching the changed files first, reporting before the full suite finishes","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain how our test-to-file mapping is derived, because i suspect it's a filename convention and misses a lot","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"our rubocop and eslint configs disagree about line length and someone changes one every few months. reconcile them and document the decision","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"docker build layer caching so a code change doesn't reinstall gems","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the dockerfile copies Gemfile.lock after the app code","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"ci が 38 分かかっていて、system spec が半分を占めている。まず改善計画を出してほしい","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"} +{"prompt":"the dashboard's flake rate is computed over all time so a fixed test stays red forever","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"plan how we get feedback on a PR in under 5 minutes, even if the full suite still takes 20","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"fast-feedback job that runs the tests touching the changed files first, reporting before the full suite finishes","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"explain how our test-to-file mapping is derived, because i suspect it's a filename convention and misses a lot","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"our rubocop and eslint configs disagree about line length and someone changes one every few months. reconcile them and document the decision","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"docker build layer caching so a code change doesn't reinstall gems","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"the dockerfile copies Gemfile.lock after the app code","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"ci が 38 分かかっていて、system spec が半分を占めている。まず改善計画を出してほしい","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"ja"} {"prompt":"plan the seed data strategy for tests — factories vs fixtures, and how we stop tests depending on each other's data","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"tests fail when run in a different order, about 20 of them","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"our factories create 12 associated records each so a simple test inserts 40 rows. trim them to the minimum, same assertions passing","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"database cleaning between tests uses truncation on 90 tables every test","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"review whether our tests could pass while the app is broken — specifically the ones that mock the thing they're testing","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"yeah keep going","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"propose how we do per-account customization without forking the codebase. enterprise customers want custom fields, custom statuses, and one wants a whole extra approval step. currently we've been adding if-account-is-X branches and there are 40 of them","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"custom fields per account — definition, storage, validation, and exposure through the api and exports","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"custom field builder ui: field type, label, required, options for selects, and a preview of the form","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"custom field values are stored as strings so a number field sorts alphabetically","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"the 40 if-account-is-X branches need to become configuration. enumerate them first, then replace, with each account's behavior unchanged","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"one account's custom status appears in another account's filter dropdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"read the account-specific branches and tell me which are genuinely customer-specific versus a feature we never generalized","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"customization documentation: what's configurable per account, what isn't, and the process for requesting something new","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"custom statuses per account with the workflow transitions configurable, and the reporting still working across accounts","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"cross-account reports break when one account renames a status","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"database cleaning between tests uses truncation on 90 tables every test","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"review whether our tests could pass while the app is broken — specifically the ones that mock the thing they're testing","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"propose how we do per-account customization without forking the codebase. enterprise customers want custom fields, custom statuses, and one wants a whole extra approval step. currently we've been adding if-account-is-X branches and there are 40 of them","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"custom fields per account — definition, storage, validation, and exposure through the api and exports","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"custom field builder ui: field type, label, required, options for selects, and a preview of the form","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"custom field values are stored as strings so a number field sorts alphabetically","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"the 40 if-account-is-X branches need to become configuration. enumerate them first, then replace, with each account's behavior unchanged","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"one account's custom status appears in another account's filter dropdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"read the account-specific branches and tell me which are genuinely customer-specific versus a feature we never generalized","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"customization documentation: what's configurable per account, what isn't, and the process for requesting something new","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"custom statuses per account with the workflow transitions configurable, and the reporting still working across accounts","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"cross-account reports break when one account renames a status","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"status configuration screen: the statuses, their order, the allowed transitions as a matrix, and a warning about records in a status you're removing","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"you can delete a status that records are currently in","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"you can delete a status that records are currently in","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} {"prompt":"plan how custom fields flow into our warehouse without a schema change per customer","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain how custom field permissions work — can a viewer see a field marked sensitive","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"api documentation for custom fields: discovery, the value types, and how they appear in list and detail responses","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"explain how custom field permissions work — can a viewer see a field marked sensitive","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"api documentation for custom fields: discovery, the value types, and how they appear in list and detail responses","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"custom field values in the api typed properly rather than all strings, with the definitions discoverable","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"our export code has a hardcoded column list so custom fields never appear in exports","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"check whether a custom field named the same as a system field shadows it anywhere","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"alright, next","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"our export code has a hardcoded column list so custom fields never appear in exports","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"check whether a custom field named the same as a system field shadows it anywhere","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"the rails app's background jobs. sidekiq, 40 job classes, and the queue configuration has grown organically so we have queues called 'default', 'high', 'urgent', 'critical' and 'now', which tells you everything. i want the plan: proper queue design, priorities that mean something, and per-queue capacity","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"queue restructuring by latency requirement rather than vague urgency, with each job class assigned deliberately","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the 'critical' queue has one worker and 'default' has 20","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"a slow job class in the shared queue delays password reset emails by 20 minutes at peak","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the 'critical' queue has one worker and 'default' has 20","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"a slow job class in the shared queue delays password reset emails by 20 minutes at peak","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} {"prompt":"job monitoring page: per-queue latency, per-job-class duration percentiles, and the failure rate","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"review our jobs for ones that aren't idempotent, since sidekiq retries them","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"job authoring guide: which queue, idempotency requirements, argument rules, and the timeout expectations","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"review our jobs for ones that aren't idempotent, since sidekiq retries them","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"job authoring guide: which queue, idempotency requirements, argument rules, and the timeout expectations","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"per-account job concurrency so one large customer's bulk import doesn't starve everyone else","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"one customer's import enqueued 400k jobs and the whole queue was theirs for 6 hours","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the import enqueues one job per row","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"plan the move from sidekiq to solid_queue, or a defensible decision not to, given we're on rails 8 now","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain how our job retries interact with the api's idempotency keys — can a retried job re-charge someone","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"one customer's import enqueued 400k jobs and the whole queue was theirs for 6 hours","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"the import enqueues one job per row","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"plan the move from sidekiq to solid_queue, or a defensible decision not to, given we're on rails 8 now","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"explain how our job retries interact with the api's idempotency keys — can a retried job re-charge someone","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"job failure alerting per job class with a threshold, rather than the current all-or-nothing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"job failure alerts go to a channel nobody watches","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"job failure alerts go to a channel nobody watches","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"runbook for the queues: how to tell what's backed up, how to drain safely, and which jobs are safe to discard","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"our jobs pass activerecord objects as arguments in 8 classes, which breaks on retry after a delete. move to ids, same behavior for live records","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"jobs fail with RecordNotFound after a record is deleted, and retry 25 times before giving up","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"check whether any of our jobs can enqueue themselves in a loop","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"here's the diff for the tenant scoping change, please look before i merge because if this is wrong it's a data leak:\n\n@@ -1,12 +1,29 @@\n class ApplicationRecord < ActiveRecord::Base\n self.abstract_class = true\n+\n+ def self.acts_as_tenanted\n+ default_scope do\n+ if Current.account\n+ where(account_id: Current.account.id)\n+ else\n+ all\n+ end\n+ end\n+\n+ belongs_to :account\n+ before_validation { self.account ||= Current.account }\n+ end\n end\n\n@@ -4,6 +4,7 @@\n class Invoice < ApplicationRecord\n+ acts_as_tenanted\n belongs_to :customer\n has_many :line_items\n end\n\nthe `else all` branch is what worries me — that's every background job, every console session, and the admin tool","purpose":"review","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"make the unscoped case fail loudly rather than returning everything, with an explicit opt-out for the places that genuinely need it","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Current.account isn't set in any of our background jobs","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"account context propagated into jobs from the enqueuing request, so a job runs scoped to the right account","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"our jobs pass activerecord objects as arguments in 8 classes, which breaks on retry after a delete. move to ids, same behavior for live records","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"jobs fail with RecordNotFound after a record is deleted, and retry 25 times before giving up","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"check whether any of our jobs can enqueue themselves in a loop","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"here's the diff for the tenant scoping change, please look before i merge because if this is wrong it's a data leak:\n\n@@ -1,12 +1,29 @@\n class ApplicationRecord < ActiveRecord::Base\n self.abstract_class = true\n+\n+ def self.acts_as_tenanted\n+ default_scope do\n+ if Current.account\n+ where(account_id: Current.account.id)\n+ else\n+ all\n+ end\n+ end\n+\n+ belongs_to :account\n+ before_validation { self.account ||= Current.account }\n+ end\n end\n\n@@ -4,6 +4,7 @@\n class Invoice < ApplicationRecord\n+ acts_as_tenanted\n belongs_to :customer\n has_many :line_items\n end\n\nthe `else all` branch is what worries me — that's every background job, every console session, and the admin tool","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"make the unscoped case fail loudly rather than returning everything, with an explicit opt-out for the places that genuinely need it","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"Current.account isn't set in any of our background jobs","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"account context propagated into jobs from the enqueuing request, so a job runs scoped to the right account","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"plan the rollout of tenant scoping across the 90 models, incrementally, with a way to detect an unscoped query in production before it leaks","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"query instrumentation that logs any query against a tenanted table without an account condition, in production, without blocking","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"the instrumentation logs 40k unscoped queries an hour, mostly from the admin tool","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"tenant scoping test helper that runs a spec twice with two accounts and asserts no cross-visibility","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"write the tenancy design doc explaining the scoping mechanism, the escape hatches, and the review rule for new models","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"internal tool showing which models are tenanted and which aren't, generated from the code","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"review the admin tool specifically — it deliberately runs unscoped, so what stops an admin action from writing to the wrong account","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"admin actions require an explicit account selection, shown persistently, and every write is audited with it","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the admin's selected account is stored in the session and persists across a logout","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"query instrumentation that logs any query against a tenanted table without an account condition, in production, without blocking","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the instrumentation logs 40k unscoped queries an hour, mostly from the admin tool","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"tenant scoping test helper that runs a spec twice with two accounts and asserts no cross-visibility","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"write the tenancy design doc explaining the scoping mechanism, the escape hatches, and the review rule for new models","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"internal tool showing which models are tenanted and which aren't, generated from the code","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"review the admin tool specifically — it deliberately runs unscoped, so what stops an admin action from writing to the wrong account","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"admin actions require an explicit account selection, shown persistently, and every write is audited with it","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"the admin's selected account is stored in the session and persists across a logout","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"plan how we'd offer a per-account database for the two customers who are asking, without maintaining two architectures","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"explain what our current architecture assumes about there being one database, and what would have to change","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"deployment architecture doc covering the shared and dedicated options, for the sales engineering team to use with prospects","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"design the scoping mechanism then implement it for the invoice models","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"review the scoping change and fix anything obviously unsafe","purpose":"review","secondary":"quickFix","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"that's me done, last bit","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"explain what our current architecture assumes about there being one database, and what would have to change","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"deployment architecture doc covering the shared and dedicated options, for the sales engineering team to use with prospects","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"design the scoping mechanism then implement it for the invoice models","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"review the scoping change and fix anything obviously unsafe","purpose":"review","secondary":"quickFix","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} {"prompt":"could you plan our live-ops setup for the mobile game? we want to run limited-time events, tune economy values, and A/B test the tutorial without shipping a build. currently everything is baked into the client and a change means a two week store review","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"remote config service for the game — values fetched at launch, cached, with a version so we can tell which config a session ran","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"live-ops console: active events, the config values with their defaults, and a diff preview before publishing","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the config fetch blocks the loading screen with no timeout","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"live-ops console: active events, the config values with their defaults, and a diff preview before publishing","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the config fetch blocks the loading screen with no timeout","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"our economy values are scattered across 30 scriptableobjects, prefabs and a few hardcoded constants. get them all into one config source, same balance in the test scenarios","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"a config change intended for one region applied globally and the economy was broken for four hours","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"would you explain how a config value reaches the gameplay code — i want to know if a mid-session change can take effect and cause inconsistency","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"live-ops runbook: publishing a config change, the staged rollout, how to verify it landed, and the rollback","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"limited-time event scheduling with start and end in the player's timezone, and a grace period for players mid-session at the end","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the event countdown in the ui goes negative after the event ends","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"event ui: banner on the home screen, the reward track, progress, and a clear 'ends in' that's honest about timezones","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"players in some timezones get the event 12 hours late and complain about missing rewards","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"a config change intended for one region applied globally and the economy was broken for four hours","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"would you explain how a config value reaches the gameplay code — i want to know if a mid-session change can take effect and cause inconsistency","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"live-ops runbook: publishing a config change, the staged rollout, how to verify it landed, and the rollback","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"limited-time event scheduling with start and end in the player's timezone, and a grace period for players mid-session at the end","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the event countdown in the ui goes negative after the event ends","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"event ui: banner on the home screen, the reward track, progress, and a clear 'ends in' that's honest about timezones","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"players in some timezones get the event 12 hours late and complain about missing rewards","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"please plan the analytics we need to actually tune the economy — what events, at what granularity, and the queries we'd run to answer 'is this event healthy'","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"economy telemetry: every currency grant and spend with the source, batched and sent reliably even if the app is killed","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"economy telemetry: every currency grant and spend with the source, batched and sent reliably even if the app is killed","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"our currency spend events are emitted from 40 call sites with inconsistent source labels. one emission point, and map the historical labels","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"total currency granted exceeds total spent plus balances by about 4%, which shouldn't be possible","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"review our telemetry for events that could be spoofed by a modified client, and which of our economy decisions depend on them","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"event taxonomy doc for the game: every telemetry event, its properties, when it fires, and who owns it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"economy dashboard: sources and sinks per currency per day, a net flow chart, and the top spend categories","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the sinks chart is stacked but the colors are recycled so two categories look identical","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"our retention query defines day-1 retention as 'played again within 24h' in one dashboard and 'played on the next calendar day' in another. pick one, document it, and say which numbers change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the retention numbers in our weekly report don't match the ones in the publisher's dashboard","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"explain what our cohort definition does with players who install and never open the game","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"metric definitions doc for the whole team: dau, retention, arpdau, conversion, each with the exact sql behind it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"here's the query plan for our slowest dashboard tile, i've been staring at it for an hour:\n\nGroupAggregate (cost=2841190.12..2914882.44 rows=412 width=48) (actual time=18422.114..18980.221 rows=390 loops=1)\n Group Key: d.day, p.platform\n -> Sort (cost=2841190.12..2860112.88 rows=7569104 width=32) (actual time=18410.882..18804.119 rows=7568112 loops=1)\n Sort Key: d.day, p.platform\n Sort Method: external merge Disk: 412880kB\n -> Hash Join (cost=88214.00..1980112.44 rows=7569104 width=32) (actual time=412.118..12088.441 rows=7568112 loops=1)\n Hash Cond: (s.player_id = p.player_id)\n -> Seq Scan on sessions s (cost=0.00..1412880.04 rows=7569104 width=24) (actual time=0.041..8104.882 rows=7568112 loops=1)\n Filter: ((started_at >= '2026-07-01'::date) AND (started_at < '2026-08-01'::date))\n Rows Removed by Filter: 84120044\n -> Hash (cost=71204.00..71204.00 rows=1360800 width=16) (actual time=411.002..411.003 rows=1360800 loops=1)\n -> Seq Scan on players p (cost=0.00..71204.00 rows=1360800 width=16)\nPlanning Time: 0.884 ms\nExecution Time: 19012.440 ms","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"index on sessions(started_at) and a rewrite so the aggregate doesn't spill 400mb to disk","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"work_mem is 4MB on the analytics role","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"total currency granted exceeds total spent plus balances by about 4%, which shouldn't be possible","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"review our telemetry for events that could be spoofed by a modified client, and which of our economy decisions depend on them","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"event taxonomy doc for the game: every telemetry event, its properties, when it fires, and who owns it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"economy dashboard: sources and sinks per currency per day, a net flow chart, and the top spend categories","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the sinks chart is stacked but the colors are recycled so two categories look identical","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"our retention query defines day-1 retention as 'played again within 24h' in one dashboard and 'played on the next calendar day' in another. pick one, document it, and say which numbers change","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"the retention numbers in our weekly report don't match the ones in the publisher's dashboard","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain what our cohort definition does with players who install and never open the game","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"metric definitions doc for the whole team: dau, retention, arpdau, conversion, each with the exact sql behind it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"here's the query plan for our slowest dashboard tile, i've been staring at it for an hour:\n\nGroupAggregate (cost=2841190.12..2914882.44 rows=412 width=48) (actual time=18422.114..18980.221 rows=390 loops=1)\n Group Key: d.day, p.platform\n -> Sort (cost=2841190.12..2860112.88 rows=7569104 width=32) (actual time=18410.882..18804.119 rows=7568112 loops=1)\n Sort Key: d.day, p.platform\n Sort Method: external merge Disk: 412880kB\n -> Hash Join (cost=88214.00..1980112.44 rows=7569104 width=32) (actual time=412.118..12088.441 rows=7568112 loops=1)\n Hash Cond: (s.player_id = p.player_id)\n -> Seq Scan on sessions s (cost=0.00..1412880.04 rows=7569104 width=24) (actual time=0.041..8104.882 rows=7568112 loops=1)\n Filter: ((started_at >= '2026-07-01'::date) AND (started_at < '2026-08-01'::date))\n Rows Removed by Filter: 84120044\n -> Hash (cost=71204.00..71204.00 rows=1360800 width=16) (actual time=411.002..411.003 rows=1360800 loops=1)\n -> Seq Scan on players p (cost=0.00..71204.00 rows=1360800 width=16)\nPlanning Time: 0.884 ms\nExecution Time: 19012.440 ms","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"index on sessions(started_at) and a rewrite so the aggregate doesn't spill 400mb to disk","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"daily pre-aggregated sessions table so the dashboard doesn't scan raw sessions, refreshed incrementally","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"dashboard tiles that load independently with a skeleton each, so one slow tile doesn't hold the page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"review the other dashboard queries for the same full-month scan of raw sessions","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"write the analytics query guidelines: use the aggregates, when a raw scan is acceptable, and the row limits we enforce","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"dashboard tiles that load independently with a skeleton each, so one slow tile doesn't hold the page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"review the other dashboard queries for the same full-month scan of raw sessions","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"write the analytics query guidelines: use the aggregates, when a raw scan is acceptable, and the row limits we enforce","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"plan how we stop the analytics workload from affecting production — a replica, a separate warehouse, or query limits","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"a badly written dashboard query took the production database to 100% cpu for 8 minutes","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"our 30 dashboard queries each embed the same date-dimension logic with slightly different week boundaries. one date dimension table, and report which weeks shift","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the week starts on sunday in three queries and monday in the rest","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"explain how our incremental aggregate handles late-arriving sessions from offline play","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"aggregate refresh that handles late data by reprocessing a trailing 7 day window","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"yesterday's numbers change slightly every time you reload the dashboard","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"data freshness indicator on each dashboard tile so people know how current the number is","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"the freshness indicator shows the query time not the data time","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"a badly written dashboard query took the production database to 100% cpu for 8 minutes","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"our 30 dashboard queries each embed the same date-dimension logic with slightly different week boundaries. one date dimension table, and report which weeks shift","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"the week starts on sunday in three queries and monday in the rest","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"explain how our incremental aggregate handles late-arriving sessions from offline play","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"aggregate refresh that handles late data by reprocessing a trailing 7 day window","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"yesterday's numbers change slightly every time you reload the dashboard","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"data freshness indicator on each dashboard tile so people know how current the number is","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the freshness indicator shows the query time not the data time","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"plan the semantic layer — one place where a metric is defined, consumed by the dashboards and the notebooks alike","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"plan the analytics warehouse move then build the session aggregation","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"figure out why yesterday's numbers drift and then write it up for the analysts","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"onward then","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"figure out why yesterday's numbers drift and then write it up for the analysts","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} {"prompt":"our spa's interaction latency is terrible and i can't get a clear picture. clicking a row in the main table takes 800ms to show anything, typing in the filter drops frames, and the profiler is a wall of react internals. i want the plan for actually diagnosing and fixing this, with a way to measure it in the field not just on my laptop","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"field performance measurement — INP and long task attribution reported per interaction type, so we know which interactions are slow for real users","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the row click handler does a synchronous json parse of a 4mb payload","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"our table rerenders every row on every keystroke in the filter because the row component takes a new callback each render. memoize properly, same rendered output","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"typing in the filter drops to 8fps once the table has 500 rows","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"review our data fetching for waterfalls — i think the detail panel waits for three sequential requests","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"frontend performance guidelines: our interaction budget, the patterns that break it, and how to profile before you optimize","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"row detail panel that shows immediately from data we already have and fills in the rest","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the detail panel refetches data it already received in the list response","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"performance regression checks in CI using a scripted interaction trace, failing on a budget breach","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"field performance measurement — INP and long task attribution reported per interaction type, so we know which interactions are slow for real users","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"the row click handler does a synchronous json parse of a 4mb payload","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"our table rerenders every row on every keystroke in the filter because the row component takes a new callback each render. memoize properly, same rendered output","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"typing in the filter drops to 8fps once the table has 500 rows","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"review our data fetching for waterfalls — i think the detail panel waits for three sequential requests","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"frontend performance guidelines: our interaction budget, the patterns that break it, and how to profile before you optimize","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"row detail panel that shows immediately from data we already have and fills in the rest","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the detail panel refetches data it already received in the list response","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"performance regression checks in CI using a scripted interaction trace, failing on a budget breach","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the perf check runs on an unthrottled cpu so it never catches anything","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"plan the bundle diet — we ship 2.8mb of javascript and i suspect half of it is three date libraries and an icon set","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"our app imports three date libraries because different teams added their own. standardize on one, identical formatted output everywhere","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the icon library is imported wholesale so all 1400 icons ship","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"the icon library is imported wholesale so all 1400 icons ship","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"code splitting by route with prefetch on hover for the likely next routes","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the bundle analyzer shows a 400kb chunk with no obvious source","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"explain which of our dependencies pull in polyfills for browsers we don't support","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"bundle budget documentation: the per-route limits, how they're enforced, and what to do when you need to exceed one","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"the bundle analyzer shows a 400kb chunk with no obvious source","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"explain which of our dependencies pull in polyfills for browsers we don't support","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"bundle budget documentation: the per-route limits, how they're enforced, and what to do when you need to exceed one","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"bundle size tracking per PR with a comment showing the delta per chunk","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the size report compares against the wrong base branch so every PR looks like it adds 2mb","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the size report compares against the wrong base branch so every PR looks like it adds 2mb","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"pouvez-vous auditer notre bundle et me dire ce qui pourrait être supprimé sans rien casser ? juste une analyse","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"fr"} {"prompt":"plan how we handle the 8000-row table people keep pasting into the filter — virtualization, server-side filtering, or telling them not to","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"server-side filtering and sorting for the main table, with the client keeping the current ux including the instant-feeling filter","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the filter debounce is 0 so every keystroke is a request","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"sure, carry on","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"would you propose the design for player support tooling? our support team can currently see nothing — they ask players for screenshots. i want them to see a player's account, recent sessions, purchases, currency history, and be able to grant a compensation reward, all audited, and with no way to see another player's data by accident","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"player lookup by id, email or receipt, returning the account summary with the recent activity","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"player detail screen for support: account, device, recent sessions, purchases, and the currency ledger, dense and scannable","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the player search matches on a partial email so support sees a list of other players","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"server-side filtering and sorting for the main table, with the client keeping the current ux including the instant-feeling filter","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"the filter debounce is 0 so every keystroke is a request","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"would you propose the design for player support tooling? our support team can currently see nothing — they ask players for screenshots. i want them to see a player's account, recent sessions, purchases, currency history, and be able to grant a compensation reward, all audited, and with no way to see another player's data by accident","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"player lookup by id, email or receipt, returning the account summary with the recent activity","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"player detail screen for support: account, device, recent sessions, purchases, and the currency ledger, dense and scannable","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the player search matches on a partial email so support sees a list of other players","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"compensation grants with a reason code, an amount cap per agent, and a full audit entry","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"an agent granted 40,000 gems instead of 400 and there's no cap or confirmation","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} {"prompt":"review the support tool's authorization — what can an agent do that they shouldn't, and is any of it only hidden in the ui","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"support playbook for the top ten player issues, with the exact tool actions for each and the escalation path","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"support playbook for the top ten player issues, with the exact tool actions for each and the escalation path","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"purchase verification against the store receipts so support can confirm a claimed purchase actually happened","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"receipt verification fails for purchases older than 90 days and support treats that as 'no purchase'","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"purchase history view with the store's status, our fulfillment status, and the two reconciled","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the fulfillment status shows 'pending' for everything older than a week","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"purchase history view with the store's status, our fulfillment status, and the two reconciled","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the fulfillment status shows 'pending' for everything older than a week","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"plan the account recovery flow for players who lost their device and never linked an account, which is 30% of our players","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"account linking prompt in the game that's persuasive without being annoying, shown at a natural moment","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"explain how a guest account's progress is identified today, and what happens if two devices claim the same guest id","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"account recovery documentation for support: what evidence we accept, the risks, and what we never do","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"guest to linked account migration that merges progress deterministically, with the conflict rules decided rather than arbitrary","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"linking an account wipes the guest progress for some players and keeps it for others","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"our progress merge logic exists in the client and the server with different precedence, so which one wins depends on who runs it. one implementation server side","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"account linking prompt in the game that's persuasive without being annoying, shown at a natural moment","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"explain how a guest account's progress is identified today, and what happens if two devices claim the same guest id","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"account recovery documentation for support: what evidence we accept, the risks, and what we never do","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"guest to linked account migration that merges progress deterministically, with the conflict rules decided rather than arbitrary","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"linking an account wipes the guest progress for some players and keeps it for others","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"our progress merge logic exists in the client and the server with different precedence, so which one wins depends on who runs it. one implementation server side","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} {"prompt":"pasting the crash breakdown from the last release, unity 6, and i genuinely don't know where to start:\n\nVersion 3.9.0 — 4.1% crash rate (was 0.8% on 3.8.2)\n\n #1 41% NullReferenceException InventoryView.OnItemSelected (InventoryView.cs:212)\n #2 22% UnityEngine.UnityException \"CompareBaseObjectsInternal can only be called from the main thread\"\n AssetLoader.OnDownloadComplete (AssetLoader.cs:88)\n #3 14% OutOfMemoryException TextureCache.Insert (TextureCache.cs:141)\n #4 9% IndexOutOfRangeException RewardTrack.GetTier (RewardTrack.cs:64)\n #5 6% Native crash (SIGSEGV) libunity.so — no symbols\n\nDevice skew: #3 is 94% devices with <=3GB RAM. #2 is spread evenly.\n3.9.0 added the addressables migration and the new reward track.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"the addressables download callback marshals back to the main thread before touching any unity object","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"texture cache with a memory budget derived from the device's available ram rather than a constant","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the texture cache budget is 512mb on every device","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"RewardTrack.GetTier indexes past the end when a player's progress exceeds the configured tiers","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"review the addressables migration for other places we assume a callback is on the main thread","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"write the release retro for 3.9.0 — what got through, why our testing missed it, and what we're changing","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"plan the low-memory device strategy — a quality tier we detect and apply, and what we drop at each level","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"device tier detection with asset variants per tier, and the tier overridable in settings","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"graphics settings screen with the detected tier shown and an explanation of what each option changes","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"our asset loading has an addressables path and a legacy Resources path, both live, and some assets load twice. finish the migration, same assets available","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"memory grows across scene loads and never comes back on android","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"explain what our scene unloading actually releases, and what we're holding references to that keeps assets alive","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"asset pipeline documentation: the addressables groups, the tier variants, and the build steps that produce them","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"plan the pre-release testing that would have caught a 4% crash rate — device farm coverage and a soak test","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"automated soak test on a device farm: 30 minutes of scripted play across the tiers, failing on a crash or a memory ceiling","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the soak test runs on three flagship devices and none under 6gb ram","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"check whether our crash reporting captures native crashes with symbols for the android builds","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"design the tier system then implement the detection","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"next one please","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"the addressables download callback marshals back to the main thread before touching any unity object","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"texture cache with a memory budget derived from the device's available ram rather than a constant","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the texture cache budget is 512mb on every device","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"RewardTrack.GetTier indexes past the end when a player's progress exceeds the configured tiers","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"review the addressables migration for other places we assume a callback is on the main thread","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"write the release retro for 3.9.0 — what got through, why our testing missed it, and what we're changing","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"plan the low-memory device strategy — a quality tier we detect and apply, and what we drop at each level","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"device tier detection with asset variants per tier, and the tier overridable in settings","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"graphics settings screen with the detected tier shown and an explanation of what each option changes","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"our asset loading has an addressables path and a legacy Resources path, both live, and some assets load twice. finish the migration, same assets available","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"memory grows across scene loads and never comes back on android","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"explain what our scene unloading actually releases, and what we're holding references to that keeps assets alive","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"asset pipeline documentation: the addressables groups, the tier variants, and the build steps that produce them","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"plan the pre-release testing that would have caught a 4% crash rate — device farm coverage and a soak test","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"automated soak test on a device farm: 30 minutes of scripted play across the tiers, failing on a crash or a memory ceiling","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"check whether our crash reporting captures native crashes with symbols for the android builds","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"design the tier system then implement the detection","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"i'd like the plan for our in-app purchase pipeline. currently the client tells the server 'i bought thing X' and the server believes it. i want proper receipt validation for both stores, server-authoritative fulfillment, handling of refunds and chargebacks, and a story for the purchases that are stuck in limbo right now","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"server-side receipt validation for both stores with the fulfillment recorded before the client is told it succeeded","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the client grants the item locally before the server confirms","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"server-side receipt validation for both stores with the fulfillment recorded before the client is told it succeeded","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the client grants the item locally before the server confirms","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"purchase flow ui: a pending state that's honest, a retry for a failed fulfillment, and a support path when it stays stuck","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"some players are charged and never receive the item, about 40 a day","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"some players are charged and never receive the item, about 40 a day","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"our purchase handling has separate code paths for ios and android with different retry and idempotency behavior. one flow with store-specific adapters, same outcomes per store","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"review the purchase path for whether a replayed receipt can grant an item twice","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"purchase and fulfillment documentation for the support and finance teams, including what a refund does to a player's inventory","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"refund handling — the store notifies us, we revoke the item if possible and flag the account if the balance is already spent","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"refunded players keep the currency and we have no record of the refund at all","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"stuck purchase recovery job that retries pending fulfillments and reports the ones it can't resolve","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the recovery job's report goes to a log file nobody reads","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"purchase reconciliation view: store-reported transactions against our fulfillments, with the mismatches listed","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"plan how we handle store price changes and regional pricing without a client update","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"prices in the shop ui are hardcoded per product rather than read from the store","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"explain how our shop decides which products to show, and whether a product not available in a region is hidden or errors","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"shop screen with prices from the store, localized currency, and unavailable products hidden rather than failing on tap","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"review the purchase path for whether a replayed receipt can grant an item twice","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"purchase and fulfillment documentation for the support and finance teams, including what a refund does to a player's inventory","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"refund handling — the store notifies us, we revoke the item if possible and flag the account if the balance is already spent","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"refunded players keep the currency and we have no record of the refund at all","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"stuck purchase recovery job that retries pending fulfillments and reports the ones it can't resolve","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the recovery job's report goes to a log file nobody reads","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"purchase reconciliation view: store-reported transactions against our fulfillments, with the mismatches listed","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"plan how we handle store price changes and regional pricing without a client update","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"prices in the shop ui are hardcoded per product rather than read from the store","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"explain how our shop decides which products to show, and whether a product not available in a region is hidden or errors","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"shop screen with prices from the store, localized currency, and unavailable products hidden rather than failing on tap","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"design the purchase pipeline then implement receipt validation for one store","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"look at the purchase code and clean up the duplicated store handling","purpose":"review","secondary":"refactor","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"and stop there","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"look at the purchase code and clean up the duplicated store handling","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"- reverse proxy, we own it, ~90k rps peak\n- currently one process, epoll, single threaded\n- need tls termination, h2 upstream, and per-route timeouts\n- want to go multi-threaded with SO_REUSEPORT\n- must not drop connections on reload\n\nwrite the design, don't touch code yet","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"multi-threaded accept with SO_REUSEPORT, per-thread event loops, and no shared mutable state on the request path","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"zero-downtime reload — new config, new listeners, drain the old workers with a deadline","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"the reload drops in-flight requests because we close listeners before draining","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the accept backlog is 128","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"our buffer management uses a global pool with a mutex, which is the contention point at 90k rps. per-thread pools, identical behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"read the connection handling and tell me under what circumstances we'd leak a file descriptor","purpose":"review","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"proxy configuration reference: the route syntax, the timeout semantics, header handling, and the reload behavior","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"fd usage climbs steadily under load and we hit the limit after about 6 hours","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"per-route timeouts — connect, header, body and total — configurable and enforced independently","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the total timeout resets whenever a byte arrives, so a slow drip never times out","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"proxy admin ui: routes, upstream health, connection counts per worker, and the active config version","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"multi-threaded accept with SO_REUSEPORT, per-thread event loops, and no shared mutable state on the request path","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} +{"prompt":"zero-downtime reload — new config, new listeners, drain the old workers with a deadline","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the reload drops in-flight requests because we close listeners before draining","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"the accept backlog is 128","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"our buffer management uses a global pool with a mutex, which is the contention point at 90k rps. per-thread pools, identical behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"read the connection handling and tell me under what circumstances we'd leak a file descriptor","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"proxy configuration reference: the route syntax, the timeout semantics, header handling, and the reload behavior","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"fd usage climbs steadily under load and we hit the limit after about 6 hours","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"per-route timeouts — connect, header, body and total — configurable and enforced independently","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the total timeout resets whenever a byte arrives, so a slow drip never times out","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"proxy admin ui: routes, upstream health, connection counts per worker, and the active config version","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"so the dns resolver. we run our own for internal service discovery, it's 4000 lines of c from 2019, and it caches negatively for the full ttl which is why a new service takes 5 minutes to be reachable. i want the plan: fix it, replace it, or put something in front of it","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"negative caching with a much shorter ttl and a bypass for names in our internal zone","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the negative cache ttl comes from the SOA minimum which is 3600 for our zone","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"our cache eviction is a linear scan of 200k entries on insert","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"resolution latency spikes to 400ms every few minutes with no change in query volume","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"review our resolver's handling of a truncated response — do we retry over tcp or return partial results","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"internal dns documentation: the zones, the ttls, how service records are created, and the propagation expectations","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"resolver metrics: query rate by type, cache hit rate, upstream latency, and the negative cache size","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"negative caching with a much shorter ttl and a bypass for names in our internal zone","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the negative cache ttl comes from the SOA minimum which is 3600 for our zone","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"our cache eviction is a linear scan of 200k entries on insert","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"resolution latency spikes to 400ms every few minutes with no change in query volume","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"review our resolver's handling of a truncated response — do we retry over tcp or return partial results","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"internal dns documentation: the zones, the ttls, how service records are created, and the propagation expectations","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"resolver metrics: query rate by type, cache hit rate, upstream latency, and the negative cache size","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"crm: the pipeline board needs drag between stages with an optimistic move, and the deal value totals per column updating live","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"dragging a deal to a new stage sometimes snaps back after a second","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the column totals sum the deal value including deals marked lost","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"dragging a deal to a new stage sometimes snaps back after a second","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the column totals sum the deal value including deals marked lost","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"our deal list, board and report each compute the weighted value differently. one calculation, and report which deals change value","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"ok go","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"i keep coming back to the crm's data model problem. a 'contact' can belong to multiple 'companies', a 'deal' can have several contacts with roles, and activities attach to any of them. right now contact has a company_id and everything else is a mess of join tables added ad hoc. i want the model designed properly plus the migration, because reporting is currently impossible","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"contact-company relationships as a proper many-to-many with a role and a primary flag, migrated from the current company_id","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"i keep coming back to the crm's data model problem. a 'contact' can belong to multiple 'companies', a 'deal' can have several contacts with roles, and activities attach to any of them. right now contact has a company_id and everything else is a mess of join tables added ad hoc. i want the model designed properly plus the migration, because reporting is currently impossible","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"contact-company relationships as a proper many-to-many with a role and a primary flag, migrated from the current company_id","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"contact detail page showing all associated companies with roles, and the activity timeline merged across them","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the contact page shows one company because it reads the old column","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"activities are polymorphic through a subject_type string that has four spellings for 'Deal'. normalize, and confirm every activity still resolves to its subject","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"some activities show on no record at all, they're orphaned but still counted in the activity metrics","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"explain how our deduplication of contacts works on import, because we have four records for one person with the same email","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"data model documentation for the crm: the entities, the relationships, and what each id field actually references","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"contact merge with a preview of what's kept, the activities combined, and an undo window","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"merging contacts loses the custom field values from the non-primary record","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"duplicate detection ui: suggested duplicate pairs with the differences highlighted and a merge or dismiss","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the duplicate suggestions include a pair we already dismissed, every day","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"plan the reporting layer given the new model — pipeline reports, activity reports, and forecasting, without the queries taking 20 seconds","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"forecast calculation with weighted pipeline, close date, and a comparison against the quota per rep","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the forecast changes when you reload because deals with no close date get today's date","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"forecast view per rep and rolled up, with the commit/best-case/pipeline split and a note on how each is derived","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"review the forecast query and tell me whether a deal can be counted in two stages","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"forecast methodology doc for the sales leadership: what each number means and the assumptions behind it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"design the activity model then implement the timeline query","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"figure out where the orphaned activities come from and then write the data cleanup note","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"here's what i measured on the proxy under load, and it's not what i expected:\n\nwrk -t8 -c400 -d60s --latency http://proxy/api/health\n\n Thread Stats Avg Stdev Max +/- Stdev\n Latency 4.21ms 28.14ms 1.02s 98.81%\n Req/Sec 11.02k 2.41k 18.90k 71.02%\n Latency Distribution\n 50% 1.02ms\n 75% 1.41ms\n 90% 2.18ms\n 99% 88.12ms\n 99.9% 912.40ms\n 5,281,442 requests in 60.00s, 1.02GB read\n Socket errors: connect 0, read 0, write 0, timeout 41\n\n perf top during the run:\n 22.1% [kernel] __inet_lookup_established\n 14.8% proxy buf_pool_acquire\n 11.2% [kernel] _raw_spin_lock\n 8.4% proxy route_match\n\np50 is fine, p99.9 is a second. buf_pool_acquire and spin_lock together are 26%","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"route matching with a compiled trie instead of the current linear list of prefix comparisons, same routing decisions","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"route_match walks 140 routes in order for every request","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"latency histogram exported from the proxy itself, per route, so we don't need wrk to see a tail","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"review our metrics export path — i suspect it takes a lock on the request path","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"performance notes for the proxy: the hot path, the invariants that keep it fast, and how to benchmark a change","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"plan the observability for the proxy — what we can afford to measure on the request path and what has to be sampled","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"request sampling with a trace id propagated, at a rate configurable at runtime without a reload","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"enabling tracing at 100% takes the proxy from 90k to 12k rps","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the sample rate is read from a global int with no atomics","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"activities are polymorphic through a subject_type string that has four spellings for 'Deal'. normalize, and confirm every activity still resolves to its subject","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"some activities show on no record at all, they're orphaned but still counted in the activity metrics","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain how our deduplication of contacts works on import, because we have four records for one person with the same email","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"data model documentation for the crm: the entities, the relationships, and what each id field actually references","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"contact merge with a preview of what's kept, the activities combined, and an undo window","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"merging contacts loses the custom field values from the non-primary record","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"duplicate detection ui: suggested duplicate pairs with the differences highlighted and a merge or dismiss","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the duplicate suggestions include a pair we already dismissed, every day","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"plan the reporting layer given the new model — pipeline reports, activity reports, and forecasting, without the queries taking 20 seconds","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"forecast calculation with weighted pipeline, close date, and a comparison against the quota per rep","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the forecast changes when you reload because deals with no close date get today's date","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"forecast view per rep and rolled up, with the commit/best-case/pipeline split and a note on how each is derived","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"review the forecast query and tell me whether a deal can be counted in two stages","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"forecast methodology doc for the sales leadership: what each number means and the assumptions behind it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"design the activity model then implement the timeline query","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"figure out where the orphaned activities come from and then write the data cleanup note","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"here's what i measured on the proxy under load, and it's not what i expected:\n\nwrk -t8 -c400 -d60s --latency http://proxy/api/health\n\n Thread Stats Avg Stdev Max +/- Stdev\n Latency 4.21ms 28.14ms 1.02s 98.81%\n Req/Sec 11.02k 2.41k 18.90k 71.02%\n Latency Distribution\n 50% 1.02ms\n 75% 1.41ms\n 90% 2.18ms\n 99% 88.12ms\n 99.9% 912.40ms\n 5,281,442 requests in 60.00s, 1.02GB read\n Socket errors: connect 0, read 0, write 0, timeout 41\n\n perf top during the run:\n 22.1% [kernel] __inet_lookup_established\n 14.8% proxy buf_pool_acquire\n 11.2% [kernel] _raw_spin_lock\n 8.4% proxy route_match\n\np50 is fine, p99.9 is a second. buf_pool_acquire and spin_lock together are 26%","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"route matching with a compiled trie instead of the current linear list of prefix comparisons, same routing decisions","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"route_match walks 140 routes in order for every request","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"latency histogram exported from the proxy itself, per route, so we don't need wrk to see a tail","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"review our metrics export path — i suspect it takes a lock on the request path","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"performance notes for the proxy: the hot path, the invariants that keep it fast, and how to benchmark a change","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"plan the observability for the proxy — what we can afford to measure on the request path and what has to be sampled","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"request sampling with a trace id propagated, at a rate configurable at runtime without a reload","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"enabling tracing at 100% takes the proxy from 90k to 12k rps","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the sample rate is read from a global int with no atomics","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} {"prompt":"upstream health checking with passive detection from real traffic plus active probes, and ejection with a recovery path","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"an upstream that's ejected never comes back until a reload","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"explain our load balancing across upstreams and whether it accounts for connection count or just round robins","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"operations guide for the proxy: reload, drain, the metrics that matter, and the three failure modes we've seen","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"plan how we test the proxy — a load test in ci, a config fuzzer, and a soak that would catch the fd leak","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"config parser fuzzing with a corpus of our real configs, run in ci","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the fuzzer found a stack overflow on deeply nested route blocks","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"unser Proxy verliert File Descriptors unter Last. wie gehe ich bei der Analyse vor?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"de"} +{"prompt":"an upstream that's ejected never comes back until a reload","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain our load balancing across upstreams and whether it accounts for connection count or just round robins","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"operations guide for the proxy: reload, drain, the metrics that matter, and the three failure modes we've seen","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"plan how we test the proxy — a load test in ci, a config fuzzer, and a soak that would catch the fd leak","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"config parser fuzzing with a corpus of our real configs, run in ci","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the fuzzer found a stack overflow on deeply nested route blocks","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"unser Proxy verliert File Descriptors unter Last. wie gehe ich bei der Analyse vor?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} {"prompt":"connection tracking view in the admin ui: per worker, state breakdown, and the oldest connection age","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the admin ui polls every 500ms and the polling itself shows up in the metrics","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"the admin ui polls every 500ms and the polling itself shows up in the metrics","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} {"prompt":"our config parsing and validation happen in two passes with different error messages for the same problem. one pass, same configs accepted","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"review the tls setup — cipher suites, session resumption, and whether we're doing anything that costs us handshake performance","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"tls session resumption with a shared ticket key rotated hourly across the fleet","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"handshake cpu is 40% of our total, and resumption is apparently not working","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"carry on with it","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"review the tls setup — cipher suites, session resumption, and whether we're doing anything that costs us handshake performance","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"tls session resumption with a shared ticket key rotated hourly across the fleet","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"handshake cpu is 40% of our total, and resumption is apparently not working","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the ci runners. we run github actions self-hosted on ec2, statically sized at 20 instances, which is idle at night and a queue during the day. i want the plan for autoscaling on k8s with ephemeral runners, including the docker-in-docker problem and how we keep build caches useful when every runner is new","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"ephemeral runner controller that scales on queue depth, one job per pod, with the pod cleaned up after","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"runner dashboard: queue depth, runners by state, time-to-pickup, and the cost per hour","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the scale-down waits 30 minutes after the queue empties","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"jobs sit queued for 4 minutes even when there's capacity","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"our runner image is built by a shell script that apt-installs 40 packages at container start. bake them into the image, same tools available","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"read the runner setup and tell me what a malicious workflow from a fork could reach","purpose":"review","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"runner infrastructure documentation: the scaling behavior, the image contents, the cache setup, and how to debug a stuck job","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"shared build cache backed by s3 with per-repo prefixes, so ephemeral runners still get warm caches","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the cache is written by every job so the last one wins and the cache is always the wrong branch's","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the cache bucket has no lifecycle policy and it's at 14TB","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"plan the isolation for fork PRs — they need to run tests but must not reach our secrets or the cache","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"separate runner pool for fork PRs with no secret access, read-only cache, and no cluster credentials","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"fork PRs run on the trusted pool if the author is a repo collaborator, which includes 40 people","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain what our runner pods can reach on the cluster network today","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"ci security policy doc: what workflows can access, the approval requirement for fork runs, and the secret scoping rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"network policy locking runner pods to the internet and the cache bucket only","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the runner service account has cluster-admin","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"our workflows inject secrets as environment variables at the job level so every step sees them. scope them per step, same steps working","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"plan the cost work — we spend $14k a month on ci and i can't tell which repos or workflows are responsible","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"ephemeral runner controller that scales on queue depth, one job per pod, with the pod cleaned up after","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"runner dashboard: queue depth, runners by state, time-to-pickup, and the cost per hour","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the scale-down waits 30 minutes after the queue empties","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"jobs sit queued for 4 minutes even when there's capacity","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"our runner image is built by a shell script that apt-installs 40 packages at container start. bake them into the image, same tools available","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"read the runner setup and tell me what a malicious workflow from a fork could reach","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"runner infrastructure documentation: the scaling behavior, the image contents, the cache setup, and how to debug a stuck job","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"shared build cache backed by s3 with per-repo prefixes, so ephemeral runners still get warm caches","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the cache is written by every job so the last one wins and the cache is always the wrong branch's","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"the cache bucket has no lifecycle policy and it's at 14TB","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"plan the isolation for fork PRs — they need to run tests but must not reach our secrets or the cache","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"separate runner pool for fork PRs with no secret access, read-only cache, and no cluster credentials","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"fork PRs run on the trusted pool if the author is a repo collaborator, which includes 40 people","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"explain what our runner pods can reach on the cluster network today","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"ci security policy doc: what workflows can access, the approval requirement for fork runs, and the secret scoping rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"network policy locking runner pods to the internet and the cache bucket only","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the runner service account has cluster-admin","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"our workflows inject secrets as environment variables at the job level so every step sees them. scope them per step, same steps working","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"plan the cost work — we spend $14k a month on ci and i can't tell which repos or workflows are responsible","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"ci cost attribution per repo and workflow from the runner pod lifetimes and instance pricing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"cost breakdown view: by repo, by workflow, with the trend and the biggest movers this month","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"one scheduled workflow runs every 5 minutes on a large instance and does nothing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"one scheduled workflow runs every 5 minutes on a large instance and does nothing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} {"prompt":"review our workflows for jobs running on larger instances than they need","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"here's the sales team's list of complaints about the crm ui, from a meeting this morning:\n\n\"1. The deal list loses my filters every time I open a deal and come back.\n 2. I can't see which of my deals haven't been touched in two weeks without exporting to a spreadsheet.\n 3. Logging a call takes 6 clicks. Six. I do this 40 times a day.\n 4. The company page doesn't show the deals for that company, I have to search.\n 5. Bulk editing 20 deals means opening 20 tabs.\n 6. On my phone the whole thing is unusable, and I'm in a car all day.\n 7. When two of us edit a deal, one of us loses. No warning.\"\n\ni want to work through these","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"filters and sort persisted in the url and restored on back navigation, so state survives a round trip to a detail page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"quick-log-call action from the deal row — one click, a note field, saves without leaving the list","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"a stale-deals view: filter by last activity date, with a saved view people can pin","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the company page needs the deals section, it's just missing","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"bulk edit for deals: select rows, choose fields, preview the change count, apply","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"here's the sales team's list of complaints about the crm ui, from a meeting this morning:\n\n\"1. The deal list loses my filters every time I open a deal and come back.\n 2. I can't see which of my deals haven't been touched in two weeks without exporting to a spreadsheet.\n 3. Logging a call takes 6 clicks. Six. I do this 40 times a day.\n 4. The company page doesn't show the deals for that company, I have to search.\n 5. Bulk editing 20 deals means opening 20 tabs.\n 6. On my phone the whole thing is unusable, and I'm in a car all day.\n 7. When two of us edit a deal, one of us loses. No warning.\"\n\ni want to work through these","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"filters and sort persisted in the url and restored on back navigation, so state survives a round trip to a detail page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"quick-log-call action from the deal row — one click, a note field, saves without leaving the list","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"a stale-deals view: filter by last activity date, with a saved view people can pin","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the company page needs the deals section, it's just missing","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"bulk edit for deals: select rows, choose fields, preview the change count, apply","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"bulk edit endpoint with per-record results and a partial success response","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"optimistic concurrency on deal updates so a second editor gets a conflict rather than silently overwriting","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"conflict ui when a deal changed under you: show both versions field by field and let the user choose","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"plan the mobile experience for reps in the field — what they actually need, and whether that's a responsive web app or a native one","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"our list view is 1400 lines with the filtering, selection, bulk actions and rendering all in one component. split it, identical behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the deal list is 340kb of javascript on its own","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"the mobile layout renders the desktop table with a horizontal scrollbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"explain how our saved views are stored and whether one can be shared with a colleague","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"saved views shareable within a team, with an owner and a copy-to-mine action","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the deal list is 340kb of javascript on its own","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"the mobile layout renders the desktop table with a horizontal scrollbar","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"explain how our saved views are stored and whether one can be shared with a colleague","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"saved views shareable within a team, with an owner and a copy-to-mine action","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"release notes for the crm update covering all seven of the sales team's items, written for salespeople not engineers","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"activity logging is slow enough that reps double-click and create two activities","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"review the deal update endpoint for what it does when two updates arrive within a millisecond","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"review the deal update endpoint for what it does when two updates arrive within a millisecond","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"design the mobile app scope then build the offline activity queue","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"look at the list component and clean it up where it's obviously redundant","purpose":"review","secondary":"refactor","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"propose how we do email integration for the crm. reps want their sent and received email logged against the contact automatically, and they use gmail and outlook roughly 50/50. i need the design including the privacy question of how much of a rep's inbox we're touching","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"gmail integration that syncs only messages matching known contacts, incremental via the history api","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"email timeline on the contact with threads collapsed, the rep's own messages distinguished, and attachments listed","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the email sync requests full mailbox read scope","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"our gmail and outlook adapters normalize a thread differently so the same conversation looks different per provider. one thread model, consistent display","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"personal emails between two colleagues who are both contacts get logged and shown to the whole team","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"review our email sync for what it stores and who in the org can read a synced message","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"privacy documentation for the email integration: the scopes, what's stored, who sees it, and how a rep excludes a thread","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"look at the list component and clean it up where it's obviously redundant","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"propose how we do email integration for the crm. reps want their sent and received email logged against the contact automatically, and they use gmail and outlook roughly 50/50. i need the design including the privacy question of how much of a rep's inbox we're touching","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"gmail integration that syncs only messages matching known contacts, incremental via the history api","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"email timeline on the contact with threads collapsed, the rep's own messages distinguished, and attachments listed","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the email sync requests full mailbox read scope","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"our gmail and outlook adapters normalize a thread differently so the same conversation looks different per provider. one thread model, consistent display","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"personal emails between two colleagues who are both contacts get logged and shown to the whole team","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"review our email sync for what it stores and who in the org can read a synced message","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"privacy documentation for the email integration: the scopes, what's stored, who sees it, and how a rep excludes a thread","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"per-thread and per-domain exclusion rules a rep can set, applied before anything is stored","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"exclusion rules apply going forward but don't remove what's already synced","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} {"prompt":"email settings screen: what's synced, the exclusions, and a disconnect that clearly states what happens to existing data","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"plan the send-from-crm feature — replying from the contact page, with the message appearing in the rep's own sent folder","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"send via the rep's provider so the message lands in their sent folder and threads correctly","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"sent messages don't thread with the original because we generate a new message-id and drop the references header","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"compose ui inside the crm with templates, merge fields, and a preview with the fields resolved","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"unresolved merge fields send as {{first_name}}","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"explain how our token refresh for the email providers works when a rep changes their password","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"send via the rep's provider so the message lands in their sent folder and threads correctly","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"sent messages don't thread with the original because we generate a new message-id and drop the references header","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"compose ui inside the crm with templates, merge fields, and a preview with the fields resolved","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"unresolved merge fields send as {{first_name}}","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"explain how our token refresh for the email providers works when a rep changes their password","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"design the email sync then implement the gmail adapter","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"and that's it for now","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"sms gateway: multi-carrier routing with per-carrier throughput limits, delivery receipts reconciled back to the message, and a failover when a carrier starts erroring","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"sms gateway: multi-carrier routing with per-carrier throughput limits, delivery receipts reconciled back to the message, and a failover when a carrier starts erroring","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"the messaging gateway. three carriers, each with a different api and its own idea of what a delivery receipt means, and our routing is a hardcoded if-chain on country code. i want the plan for proper routing with cost and quality inputs, plus how we handle a carrier being down at 3am without a human","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"message status timeline in the console: accepted, submitted to carrier, delivered or failed, with the carrier's own status shown alongside ours","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the per-carrier rate limit is a single global counter","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"our three carrier adapters each map status codes to our internal states differently, so 'delivered' means three things. one mapping table, and report which historical messages would be classified differently","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"about 2% of messages sit in 'submitted' forever with no receipt ever arriving","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain how our retry interacts with carrier-side deduplication — can a retried message be delivered twice","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"messaging api documentation: the status lifecycle, what each status guarantees, the retry behavior, and the receipt webhook","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"delivery receipt reconciliation job that closes out messages with no receipt after the carrier's stated window, marking them unknown rather than delivered","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the reconciler marks unknown messages as delivered so our delivery rate looks great and is a lie","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"supervision tree for the carrier connections so one carrier's adapter crashing doesn't take the others down","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"one carrier adapter crashing takes the whole gateway down for 20 seconds","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"review our genserver state — i think the message queue is held in process memory and lost on a crash","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"figma plugin: read the selected frames and export our design tokens as json in the format our build expects","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the plugin ui needs a token list with a diff against what's currently in the repo, and an export button per group","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"message status timeline in the console: accepted, submitted to carrier, delivered or failed, with the carrier's own status shown alongside ours","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the per-carrier rate limit is a single global counter","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"our three carrier adapters each map status codes to our internal states differently, so 'delivered' means three things. one mapping table, and report which historical messages would be classified differently","purpose":"refactor","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"about 2% of messages sit in 'submitted' forever with no receipt ever arriving","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"explain how our retry interacts with carrier-side deduplication — can a retried message be delivered twice","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"messaging api documentation: the status lifecycle, what each status guarantees, the retry behavior, and the receipt webhook","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"delivery receipt reconciliation job that closes out messages with no receipt after the carrier's stated window, marking them unknown rather than delivered","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the reconciler marks unknown messages as delivered so our delivery rate looks great and is a lie","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"supervision tree for the carrier connections so one carrier's adapter crashing doesn't take the others down","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"one carrier adapter crashing takes the whole gateway down for 20 seconds","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"review our genserver state — i think the message queue is held in process memory and lost on a crash","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"figma plugin: read the selected frames and export our design tokens as json in the format our build expects","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the plugin ui needs a token list with a diff against what's currently in the repo, and an export button per group","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"the plugin exports color values as rgba floats and our build wants hex","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"the plugin hangs on files with more than about 2000 layers","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"plan the design-to-code handoff properly — tokens, component naming, and how a designer knows what's already built","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"our token naming in figma and in code differ, so the export needs a mapping file that's maintained by hand. align the names in both, no visual change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"explain how the plugin authenticates to our repo, i want to know if a designer's token is being stored in the plugin","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"plugin usage docs for designers: what it exports, what it can't, and the naming rules it depends on","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"the plugin hangs on files with more than about 2000 layers","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"plan the design-to-code handoff properly — tokens, component naming, and how a designer knows what's already built","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"our token naming in figma and in code differ, so the export needs a mapping file that's maintained by hand. align the names in both, no visual change","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain how the plugin authenticates to our repo, i want to know if a designer's token is being stored in the plugin","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"plugin usage docs for designers: what it exports, what it can't, and the naming rules it depends on","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"postgres ha: patroni with three nodes, synchronous replication to one, and the failover tested rather than assumed","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"we have one postgres, nightly backups to s3, and no replica. that's the whole story. i want the plan for something we can stand behind, with the rpo and rto per option and what each costs","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"the backup job hasn't succeeded in 11 days and nothing alerted","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"the backup job hasn't succeeded in 11 days and nothing alerted","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"here's the failover test result from last night, and it did not go well:\n\n21:04 killed primary (db-01) with kill -9 on postgres\n21:04 patroni detected leader loss\n21:05 db-02 promoted to leader (11s) ✓\n21:05 app error rate 100% — connections still pointing at db-01\n21:07 pgbouncer still routing to db-01, no reconfiguration happened\n21:09 manually restarted pgbouncer, app recovered\n21:09 total outage: 5m 12s (target: 30s)\n21:14 db-01 restarted, rejoined as replica\n21:14 db-01 has 4 transactions db-02 doesn't (async replica was behind)\n21:15 patroni ran pg_rewind, those 4 transactions are gone\n\nthe 4 lost transactions are the part i can't accept. two were payments.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"synchronous commit to at least one replica so a promoted leader can't be missing committed transactions","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"synchronous_commit is 'local' on the primary","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"pgbouncer reconfiguration on failover so connections follow the new leader without a manual restart","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"review our connection path end to end and tell me every component that needs to know the leader changed","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"write the failover runbook based on what actually happened, including the pgbouncer step and the data loss check","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"plan the failover testing cadence — monthly, in staging with production-like traffic, with a defined pass criteria","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"synchronous commit to at least one replica so a promoted leader can't be missing committed transactions","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"synchronous_commit is 'local' on the primary","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"pgbouncer reconfiguration on failover so connections follow the new leader without a manual restart","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"review our connection path end to end and tell me every component that needs to know the leader changed","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"write the failover runbook based on what actually happened, including the pgbouncer step and the data loss check","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"plan the failover testing cadence — monthly, in staging with production-like traffic, with a defined pass criteria","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"database status page for us internally: replication lag per replica, the current leader, and the last failover","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the lag figure is in bytes and nobody knows whether 4MB is bad","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"our app has the database host in 6 places — env vars, a config file, two secrets and a hardcoded default. one source, same connections","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"after the failover, two services reconnected to the old primary as it came back up as a replica and started getting read-only errors","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain what our application does on a read-only error from the database — retry, fail, or crash","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"connection handling that detects a read-only primary and re-resolves the leader rather than erroring for minutes","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"backup verification — restore the latest backup to a scratch instance nightly and assert on a known row and the row counts","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the restore test passes on an empty backup because it only checks the exit code","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"backup and recovery documentation: what we back up, the rpo, the restore procedure with commands, and the verification","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the lag figure is in bytes and nobody knows whether 4MB is bad","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"our app has the database host in 6 places — env vars, a config file, two secrets and a hardcoded default. one source, same connections","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"after the failover, two services reconnected to the old primary as it came back up as a replica and started getting read-only errors","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"explain what our application does on a read-only error from the database — retry, fail, or crash","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"connection handling that detects a read-only primary and re-resolves the leader rather than erroring for minutes","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"backup verification — restore the latest backup to a scratch instance nightly and assert on a known row and the row counts","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the restore test passes on an empty backup because it only checks the exit code","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"backup and recovery documentation: what we back up, the rpo, the restore procedure with commands, and the verification","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"plan the point-in-time recovery setup with wal archiving, and how far back we can go","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"wal archiving to s3 with the archive command monitored so a failure is loud","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"archive_command is 'cp' to a local disk that filled up","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"archive_command is 'cp' to a local disk that filled up","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"plan the ha architecture then implement the pgbouncer failover handling","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"work out how we lost those four transactions and then write the incident report","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"work out how we lost those four transactions and then write the incident report","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"voice calls. we want to add programmable voice on top of the sms gateway — inbound routing to a sip endpoint or a webhook-driven ivr, recording, and transcription. i want the design including where media flows and what we do and don't want to be in the path of","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"inbound call routing driven by a per-number webhook that returns instructions, with a timeout and a sensible default action","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"call flow builder ui: blocks for play, gather, dial and record, connected, with a test-call action","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the webhook timeout is 30 seconds so the caller hears silence","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"calls occasionally connect with one-way audio and the logs show nothing wrong","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"review our sip signalling for whether we're leaking internal ip addresses in the sdp","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"voice api documentation: the webhook contract, the instruction verbs, the call status callbacks, and the recording availability timing","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"call recording with consent handling per jurisdiction, stored encrypted, with an announced beep where required","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"recordings are stored unencrypted in a public-read bucket","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"our recording consent flag is checked in the api and again in the media server with different logic. one check, and report which numbers change behavior","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"call detail view: the timeline of events, the recording player, the transcript, and the cost breakdown","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the recording player loads the whole file before playing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"plan the call quality monitoring — mos estimation, jitter and loss per leg, and how we tell whether a bad call was us or the carrier","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"per-leg quality metrics collected from the media server and attached to the call record","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain how we attribute a bad call to a leg today, and whether we have the data to do it at all","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"voice troubleshooting guide for our support team: the symptoms, what each metric means, and when to escalate to the carrier","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"inbound call routing driven by a per-number webhook that returns instructions, with a timeout and a sensible default action","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"call flow builder ui: blocks for play, gather, dial and record, connected, with a test-call action","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"the webhook timeout is 30 seconds so the caller hears silence","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"calls occasionally connect with one-way audio and the logs show nothing wrong","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"review our sip signalling for whether we're leaking internal ip addresses in the sdp","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"voice api documentation: the webhook contract, the instruction verbs, the call status callbacks, and the recording availability timing","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"call recording with consent handling per jurisdiction, stored encrypted, with an announced beep where required","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"recordings are stored unencrypted in a public-read bucket","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"our recording consent flag is checked in the api and again in the media server with different logic. one check, and report which numbers change behavior","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"call detail view: the timeline of events, the recording player, the transcript, and the cost breakdown","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the recording player loads the whole file before playing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"plan the call quality monitoring — mos estimation, jitter and loss per leg, and how we tell whether a bad call was us or the carrier","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"per-leg quality metrics collected from the media server and attached to the call record","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain how we attribute a bad call to a leg today, and whether we have the data to do it at all","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"voice troubleshooting guide for our support team: the symptoms, what each metric means, and when to escalate to the carrier","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"quality dashboard: mos distribution, calls by carrier, and the worst calls with a drill-in","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"音声通話の片方向音声が時々発生する。まず原因の切り分けをお願いしたい","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"ja"} -{"prompt":"number provisioning — search available numbers by area, purchase, configure, and release, with the carrier apis abstracted","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"number management ui: owned numbers, their configuration, monthly cost, and a search-and-buy flow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"released numbers stay billable for a month because we don't tell the carrier","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the number search shows numbers that are no longer available by the time you click buy","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"review our number configuration for whether one customer can point a number they don't own at their webhook","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"number provisioning documentation: what's available where, the regulatory requirements per country, and the porting process","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"here's the carrier's incident report and our own numbers side by side, and i want to understand the discrepancy before i respond to them:\n\nCARRIER SAYS (14:00–16:00 UTC):\n Messages received from you: 412,004\n Accepted: 411,880\n Rejected (invalid destination): 124\n Delivered: 398,220 (96.7%)\n Failed (handset unreachable): 13,660\n\nWE SAY (same window):\n Messages submitted: 438,910\n Accepted by carrier: 411,880\n No response / timeout: 27,030 <- we retried these\n Delivery receipts received: 366,004\n Still pending: 45,876\n\nso 27k of ours got no response, we retried them, and the carrier's accepted count matches our\naccepted count exactly. and we're missing 32k delivery receipts.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"receipt ingestion that can't drop a receipt — persist first, process asynchronously, with a dead letter for unparseable ones","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"our receipt endpoint returns 200 before persisting","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"retry-on-timeout that uses a client-generated id the carrier honors, so a retry can't create a duplicate submission","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"review our submission retry logic for whether a timeout followed by a success means we sent twice","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"write the response to the carrier laying out the discrepancy with our numbers, specific and non-accusatory","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"reconciliation report comparing our submission log to the carrier's daily file, with the differences categorized","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"plan how we detect a carrier silently dropping messages within minutes rather than at the monthly reconciliation","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"音声通話の片方向音声が時々発生する。まず原因の切り分けをお願いしたい","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"} +{"prompt":"number provisioning — search available numbers by area, purchase, configure, and release, with the carrier apis abstracted","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"number management ui: owned numbers, their configuration, monthly cost, and a search-and-buy flow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"released numbers stay billable for a month because we don't tell the carrier","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"the number search shows numbers that are no longer available by the time you click buy","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"review our number configuration for whether one customer can point a number they don't own at their webhook","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"number provisioning documentation: what's available where, the regulatory requirements per country, and the porting process","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"here's the carrier's incident report and our own numbers side by side, and i want to understand the discrepancy before i respond to them:\n\nCARRIER SAYS (14:00–16:00 UTC):\n Messages received from you: 412,004\n Accepted: 411,880\n Rejected (invalid destination): 124\n Delivered: 398,220 (96.7%)\n Failed (handset unreachable): 13,660\n\nWE SAY (same window):\n Messages submitted: 438,910\n Accepted by carrier: 411,880\n No response / timeout: 27,030 <- we retried these\n Delivery receipts received: 366,004\n Still pending: 45,876\n\nso 27k of ours got no response, we retried them, and the carrier's accepted count matches our\naccepted count exactly. and we're missing 32k delivery receipts.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"receipt ingestion that can't drop a receipt — persist first, process asynchronously, with a dead letter for unparseable ones","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"our receipt endpoint returns 200 before persisting","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"retry-on-timeout that uses a client-generated id the carrier honors, so a retry can't create a duplicate submission","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"review our submission retry logic for whether a timeout followed by a success means we sent twice","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"write the response to the carrier laying out the discrepancy with our numbers, specific and non-accusatory","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"reconciliation report comparing our submission log to the carrier's daily file, with the differences categorized","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"plan how we detect a carrier silently dropping messages within minutes rather than at the monthly reconciliation","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"carrier health monitoring: acceptance rate, receipt latency, and delivery rate per carrier per minute, with alerts on a shift","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"the delivery rate alert has a one hour window so we notice an outage 40 minutes in","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"carrier comparison view: cost, delivery rate and receipt latency side by side per destination country","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"carrier comparison view: cost, delivery rate and receipt latency side by side per destination country","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"automatic carrier failover when the acceptance rate drops, with a manual pin so ops can override","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the failover flapped between two carriers every 30 seconds for an hour","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"explain how our routing decision is made per message and whether it's reproducible after the fact","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"routing decisions recorded per message so we can explain to a customer why their message went via a particular carrier","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"routing documentation for customers: how we pick a route, what they can control, and what we guarantee about delivery","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"our cost calculation exists in the routing decision and again in the billing job with different rate tables. one rate source, and report which messages are priced differently","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"customers are billed a different amount than the cost we showed at send time","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"plan the routing engine then implement the carrier scoring","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"review the receipt handler and fix anything obviously broken","purpose":"review","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"next then","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"the failover flapped between two carriers every 30 seconds for an hour","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"explain how our routing decision is made per message and whether it's reproducible after the fact","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"routing decisions recorded per message so we can explain to a customer why their message went via a particular carrier","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"routing documentation for customers: how we pick a route, what they can control, and what we guarantee about delivery","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"our cost calculation exists in the routing decision and again in the billing job with different rate tables. one rate source, and report which messages are priced differently","purpose":"refactor","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"customers are billed a different amount than the cost we showed at send time","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"plan the routing engine then implement the carrier scoring","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"review the receipt handler and fix anything obviously broken","purpose":"review","secondary":"quickFix","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} {"prompt":"the design system's figma-to-code loop. designers change a component in figma, tell us in slack, and someone updates the code a week later, so the two have been out of sync since february. i want the plan for closing this loop, including whether we generate code from figma (i suspect not) and how we detect drift","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"drift detection comparing the figma component properties against our code's prop types, reported weekly","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"drift report ui: components with differences, the figma value against the code value, and a link to both","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the drift report lists every component because the naming conventions differ between figma and code","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"our figma component names use Title Case With Spaces and our code uses PascalCase, so nothing matches. establish one convention and rename on both sides","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"explain how our token export handles a figma variable that references another variable","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"design system contribution process doc: how a designer proposes a change, who reviews, and how it reaches production","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"token resolution for aliased figma variables, flattened to concrete values in the export with the alias recorded","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"aliased tokens export as the literal string '{color.brand.500}'","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"drift detection comparing the figma component properties against our code's prop types, reported weekly","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"drift report ui: components with differences, the figma value against the code value, and a link to both","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"the drift report lists every component because the naming conventions differ between figma and code","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"our figma component names use Title Case With Spaces and our code uses PascalCase, so nothing matches. establish one convention and rename on both sides","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"explain how our token export handles a figma variable that references another variable","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"design system contribution process doc: how a designer proposes a change, who reviews, and how it reaches production","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"token resolution for aliased figma variables, flattened to concrete values in the export with the alias recorded","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"aliased tokens export as the literal string '{color.brand.500}'","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"plan how we version the design system's figma library alongside the code package, so a designer knows which version their file uses","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"visual regression tests comparing our built components against reference renders exported from figma","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the visual comparison fails on everything because figma renders text with different antialiasing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"review our component library for components that exist in code but not in figma, and vice versa","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"component inventory doc listing what exists where, with the gaps called out for both teams","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"plugin that annotates a figma file with which components are implemented in code and at what version","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"the annotation overlays sit on top of the designs and can't be hidden","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"visual regression tests comparing our built components against reference renders exported from figma","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"the visual comparison fails on everything because figma renders text with different antialiasing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"review our component library for components that exist in code but not in figma, and vice versa","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"component inventory doc listing what exists where, with the gaps called out for both teams","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"plugin that annotates a figma file with which components are implemented in code and at what version","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"the annotation overlays sit on top of the designs and can't be hidden","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"design the drift detection then implement the token comparison","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"explain the token pipeline and then document it for the design team","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"one more","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"explain the token pipeline and then document it for the design team","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} {"prompt":"propose the design for our multi-tenant postgres at the next order of magnitude. we're at 4000 tenants in one database, 2TB, and the biggest tenant is 8% of it. i want to know when we have to shard, what the intermediate steps are (partitioning, moving the big tenants out), and the signals that tell us it's time","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"partition the three biggest tables by tenant hash, online, with the application unaware","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"tenant size dashboard: rows and bytes per tenant per table, with the growth rate and the top 20 by size","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"the size query does a full table scan per tenant and takes 40 minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"queries that were fast are now slow after partitioning, specifically the ones that don't filter by tenant","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"our cross-tenant admin queries don't filter by tenant, which is now a partition scan. rewrite them to be partition-aware or explicitly accept the cost, documented","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"read our queries and tell me which ones would still work if the tables were on separate databases","purpose":"review","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"database scaling documentation: the current architecture, the partitioning scheme, the signals for the next step, and what shards would mean","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"tenant move procedure — copy a tenant's rows to another database, verify, cut over with a short write pause, and clean up","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"the tenant move verification compares row counts only, so a mangled column would pass","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"a tenant move left rows in both databases and the app read from both depending on the request","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"explain how our connection routing would decide which database a tenant lives in, if we had more than one","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"tenant size dashboard: rows and bytes per tenant per table, with the growth rate and the top 20 by size","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"the size query does a full table scan per tenant and takes 40 minutes","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"queries that were fast are now slow after partitioning, specifically the ones that don't filter by tenant","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"our cross-tenant admin queries don't filter by tenant, which is now a partition scan. rewrite them to be partition-aware or explicitly accept the cost, documented","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"read our queries and tell me which ones would still work if the tables were on separate databases","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"database scaling documentation: the current architecture, the partitioning scheme, the signals for the next step, and what shards would mean","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"tenant move procedure — copy a tenant's rows to another database, verify, cut over with a short write pause, and clean up","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"the tenant move verification compares row counts only, so a mangled column would pass","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"a tenant move left rows in both databases and the app read from both depending on the request","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"explain how our connection routing would decide which database a tenant lives in, if we had more than one","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} {"prompt":"plan the vacuum and bloat management at this size — autovacuum is falling behind on the biggest tables","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"autovacuum tuning per table with the big ones given more aggressive settings, and monitoring for when it falls behind","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"the events table has 40% dead tuples and autovacuum hasn't run on it in 9 days","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"database maintenance runbook: bloat, vacuum, reindexing, and the safe windows for each","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"bloat monitoring with an alert when a table's dead tuple ratio crosses a threshold","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"design the partitioning then implement it for the events table","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"that's the last of it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Sketch an offline-sync architecture for our Android field-inspection app using Room, WorkManager, and conflict-aware retries.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Outline the Redis-to-KeyDB migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Design our shader asset pipeline","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Break the monolith extraction into milestones","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"We need an RFC for moving tenant analytics out of the Rails request path. Cover a Kafka ingestion layer, ClickHouse storage, late-event handling, tenant isolation, replay strategy, operational ownership, and a phased rollout that keeps the existing PostgreSQL reports available until parity is proven. Keep this at the design level; no implementation yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"core","lang":"en"} -{"prompt":"Produce a monitoring strategy for the Nomad jobs that run our nightly pricing imports, including SLIs, alert thresholds, dashboards, and ownership.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Map a safe roadmap for replacing the STM32 bootloader without bricking deployed greenhouse controllers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"core","lang":"en"} -{"prompt":"Propose the data model and ingestion stages for a lakehouse that receives Parquet exports from six regional billing systems.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"Lay out a navigation design for splitting the SwiftUI app's single NavigationStack into independent tab histories.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Draft a threat model for the partner-login flow. It uses OIDC, account linking by verified email, refresh-token rotation, and a support-only impersonation feature. Identify trust boundaries, likely abuse cases, audit requirements, and mitigations, then sequence the security work into reviewable milestones. This is for an architecture meeting, so don't edit the code.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"core","lang":"en"} -{"prompt":"Necesito un plan para migrar los cron jobs de Celery a Temporal sin detener los informes mensuales.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"es"} -{"prompt":"Create a rollout plan for partitioning the audit_events table by month, including backfill, dual writes, validation, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.81,"slice":"core","lang":"en"} -{"prompt":"Architect a stable plugin API for the Borealis CLI so third-party commands can survive internal package changes.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"en"} -{"prompt":"Put together a deprecation strategy for our public gRPC v1 surface, including compatibility windows and client migration checkpoints.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Implement cursor pagination in /events","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.37,"slice":"core","lang":"en"} -{"prompt":"Wire S3 multipart uploads","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Add idempotency keys to checkout","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} -{"prompt":"Build the protobuf decoder","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.47,"slice":"core","lang":"en"} -{"prompt":"Finish the Rust worker in crates/thumbnailer so it leases jobs from NATS JetStream, renews leases during long ffmpeg runs, writes results to MinIO, and sends failed jobs to a bounded dead-letter stream. Preserve at-least-once delivery and add focused integration tests using the existing testcontainers setup.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Create a Django management command that detects overlapping subscription periods and emits a repair CSV without modifying production data.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} +{"prompt":"autovacuum tuning per table with the big ones given more aggressive settings, and monitoring for when it falls behind","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"the events table has 40% dead tuples and autovacuum hasn't run on it in 9 days","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"database maintenance runbook: bloat, vacuum, reindexing, and the safe windows for each","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"bloat monitoring with an alert when a table's dead tuple ratio crosses a threshold","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"design the partitioning then implement it for the events table","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Sketch an offline-sync architecture for our Android field-inspection app using Room, WorkManager, and conflict-aware retries.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Outline the Redis-to-KeyDB migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Design our shader asset pipeline","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Break the monolith extraction into milestones","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"We need an RFC for moving tenant analytics out of the Rails request path. Cover a Kafka ingestion layer, ClickHouse storage, late-event handling, tenant isolation, replay strategy, operational ownership, and a phased rollout that keeps the existing PostgreSQL reports available until parity is proven. Keep this at the design level; no implementation yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Produce a monitoring strategy for the Nomad jobs that run our nightly pricing imports, including SLIs, alert thresholds, dashboards, and ownership.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Map a safe roadmap for replacing the STM32 bootloader without bricking deployed greenhouse controllers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Propose the data model and ingestion stages for a lakehouse that receives Parquet exports from six regional billing systems.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Lay out a navigation design for splitting the SwiftUI app's single NavigationStack into independent tab histories.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Draft a threat model for the partner-login flow. It uses OIDC, account linking by verified email, refresh-token rotation, and a support-only impersonation feature. Identify trust boundaries, likely abuse cases, audit requirements, and mitigations, then sequence the security work into reviewable milestones. This is for an architecture meeting, so don't edit the code.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Necesito un plan para migrar los cron jobs de Celery a Temporal sin detener los informes mensuales.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"es"} +{"prompt":"Create a rollout plan for partitioning the audit_events table by month, including backfill, dual writes, validation, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Architect a stable plugin API for the Borealis CLI so third-party commands can survive internal package changes.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Put together a deprecation strategy for our public gRPC v1 surface, including compatibility windows and client migration checkpoints.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement cursor pagination in /events","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Wire S3 multipart uploads","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add idempotency keys to checkout","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Build the protobuf decoder","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Finish the Rust worker in crates/thumbnailer so it leases jobs from NATS JetStream, renews leases during long ffmpeg runs, writes results to MinIO, and sends failed jobs to a bounded dead-letter stream. Preserve at-least-once delivery and add focused integration tests using the existing testcontainers setup.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create a Django management command that detects overlapping subscription periods and emits a repair CSV without modifying production data.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Teach the Go gateway to validate DPoP proofs before exchanging mobile access tokens.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Introduce a schema migration for nullable warehouse_id on shipments, backfill it from route assignments, then enforce the foreign key.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Extend the Python parser to accept multiline HCL attributes while retaining comments and source spans.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} +{"prompt":"Introduce a schema migration for nullable warehouse_id on shipments, backfill it from route assignments, then enforce the foreign key.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Extend the Python parser to accept multiline HCL attributes while retaining comments and source spans.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Build a rate-limited GitHub webhook consumer in Kotlin that verifies signatures, deduplicates deliveries, and persists installation events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Add a --since flag to the log-surgeon CLI and accept both RFC 3339 timestamps and durations such as 45m.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"PostgreSQL の advisory lock を使って、同じ請求書が二重生成されないように worker を実装して。","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"ja"} -{"prompt":"Make the GraphQL resolver batch product availability lookups through the existing DataLoader.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} +{"prompt":"Add a --since flag to the log-surgeon CLI and accept both RFC 3339 timestamps and durations such as 45m.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"PostgreSQL の advisory lock を使って、同じ請求書が二重生成されないように worker を実装して。","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"ja"} +{"prompt":"Make the GraphQL resolver batch product availability lookups through the existing DataLoader.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Implement reservoir sampling for unbounded telemetry streams in pkg/sample, with deterministic seeded tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Build the empty-state card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.28,"slice":"core","lang":"en"} -{"prompt":"Style the account switcher","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.32,"slice":"core","lang":"en"} -{"prompt":"Add swipe-to-archive in SwiftUI","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Animate the boss health bar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"The operations dashboard needs a dense responsive table for 10k-row incident searches. Build the React view with TanStack Table virtualization, sticky service and severity columns, keyboard-accessible sorting, saved column visibility, and a compact mobile fallback. Match the tokens in ui/theme.css and include Storybook states for loading, empty, partial data, and a failed refresh.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Implement the Compose screen for pairing a BLE soil sensor, including scanning, permission prompts, signal strength, and connection progress.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Turn the plain invoice form into a two-column layout with inline validation and a persistent totals panel.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} -{"prompt":"Create a macOS menu-bar popover showing current VPN route, latency, and a reconnect button using SwiftUI.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Give the Godot inventory grid drag previews, valid-drop highlighting, and a snap-back animation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Rework the Vue onboarding screen so progress remains visible, each step has a clear title, and validation errors don't shift the buttons around.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Add a high-contrast theme to the terminal emulator settings screen and expose it in the appearance picker.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"Bitte baue den Jetpack-Compose-Dialog für das Löschen eines Workspace, inklusive Warntext, Texteingabe zur Bestätigung und Loading-State.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"core","lang":"de"} -{"prompt":"Build a timeline view for model-training runs with zooming, hover details, and colored spans for queued, provisioning, and active states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Make the Astro docs sidebar collapsible while retaining focus order and the active section indicator.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Bump esbuild to 0.25.5","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"core","lang":"en"} -{"prompt":"Flip enable_delta_cache on","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"Correct the misspelled env var","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Hide the beta badge","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"core","lang":"en"} -{"prompt":"Change the health-check timeout in deploy/api.yaml from 2s to 5s; startup has always taken about three seconds on the ARM nodes.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.15,"slice":"core","lang":"en"} -{"prompt":"Replace the stale support URL in SettingsFooter.tsx with https://support.example.net/help.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} +{"prompt":"Build the empty-state card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Style the account switcher","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Add swipe-to-archive in SwiftUI","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Animate the boss health bar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"The operations dashboard needs a dense responsive table for 10k-row incident searches. Build the React view with TanStack Table virtualization, sticky service and severity columns, keyboard-accessible sorting, saved column visibility, and a compact mobile fallback. Match the tokens in ui/theme.css and include Storybook states for loading, empty, partial data, and a failed refresh.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement the Compose screen for pairing a BLE soil sensor, including scanning, permission prompts, signal strength, and connection progress.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Turn the plain invoice form into a two-column layout with inline validation and a persistent totals panel.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Create a macOS menu-bar popover showing current VPN route, latency, and a reconnect button using SwiftUI.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Give the Godot inventory grid drag previews, valid-drop highlighting, and a snap-back animation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Rework the Vue onboarding screen so progress remains visible, each step has a clear title, and validation errors don't shift the buttons around.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add a high-contrast theme to the terminal emulator settings screen and expose it in the appearance picker.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Bitte baue den Jetpack-Compose-Dialog für das Löschen eines Workspace, inklusive Warntext, Texteingabe zur Bestätigung und Loading-State.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"de"} +{"prompt":"Build a timeline view for model-training runs with zooming, hover details, and colored spans for queued, provisioning, and active states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Make the Astro docs sidebar collapsible while retaining focus order and the active section indicator.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Bump esbuild to 0.25.5","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Flip enable_delta_cache on","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Correct the misspelled env var","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Hide the beta badge","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Change the health-check timeout in deploy/api.yaml from 2s to 5s; startup has always taken about three seconds on the ARM nodes.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Replace the stale support URL in SettingsFooter.tsx with https://support.example.net/help.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Set retries: 4 for the image-import GitHub Actions step.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Fix the off-by-one in pagesRemaining: it should subtract currentPage + 1 because currentPage is zero-based.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.18,"slice":"core","lang":"en"} -{"prompt":"Update the iOS deployment target from 17.0 to 17.2 in Package.swift.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.13,"slice":"core","lang":"en"} +{"prompt":"Fix the off-by-one in pagesRemaining: it should subtract currentPage + 1 because currentPage is zero-based.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Update the iOS deployment target from 17.0 to 17.2 in Package.swift.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Point the staging Helm values at registry.internal/ledger:v3.8.1 instead of v3.8.0.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Rename the local variable resposne to response in webhook_test.go.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"core","lang":"en"} -{"prompt":"Corrige la couleur du bouton Annuler: utilise var(--neutral-600), pas le rouge destructif.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"core","lang":"fr"} -{"prompt":"Swap the two reversed GPIO pin constants for the status LEDs in board_rev_c.h.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"core","lang":"en"} -{"prompt":"Remove the accidental console.log from src/hooks/useSession.ts.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"core","lang":"en"} -{"prompt":"Rename OrderDTO across the repository","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Extract the retry policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"Split BillingService by responsibility","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Deduplicate the date parsers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Our TypeScript SDK has three nearly identical request builders under packages/client/src. Consolidate their header, query serialization, timeout, and error-mapping logic behind one internal helper without changing the generated public methods or emitted requests. Keep tree-shaking intact and use the existing golden HTTP tests to demonstrate behavioral equivalence.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Consolidate the duplicated SwiftUI toolbar code from ProjectView and ArchiveView into a shared modifier, preserving appearance and shortcuts.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.48,"slice":"core","lang":"en"} -{"prompt":"Move SQL construction out of the HTTP handlers into the existing repository layer with no response changes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Decouple the Unreal matchmaking subsystem from the concrete EOS client so tests can inject a fake.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Simplify the nested feature-flag conditionals in pricing_rules.py while retaining every current branch and exception.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Clean up the Terraform module boundaries: move IAM policy assembly into modules/identity, preserve the resulting plan, and remove duplicate locals.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Reorganize the parser's token kinds into separate declaration and literal modules without changing its API or snapshots.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Quero separar o SessionManager em armazenamento, renovação e validação, mantendo exatamente o comportamento atual.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"pt-BR"} -{"prompt":"Flatten the inheritance hierarchy under src/devices/drivers and replace the abstract base hooks with composition; device behavior must remain identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} +{"prompt":"Rename the local variable resposne to response in webhook_test.go.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Corrige la couleur du bouton Annuler: utilise var(--neutral-600), pas le rouge destructif.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"fr"} +{"prompt":"Swap the two reversed GPIO pin constants for the status LEDs in board_rev_c.h.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Remove the accidental console.log from src/hooks/useSession.ts.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename OrderDTO across the repository","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Extract the retry policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Split BillingService by responsibility","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Deduplicate the date parsers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Our TypeScript SDK has three nearly identical request builders under packages/client/src. Consolidate their header, query serialization, timeout, and error-mapping logic behind one internal helper without changing the generated public methods or emitted requests. Keep tree-shaking intact and use the existing golden HTTP tests to demonstrate behavioral equivalence.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Consolidate the duplicated SwiftUI toolbar code from ProjectView and ArchiveView into a shared modifier, preserving appearance and shortcuts.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Move SQL construction out of the HTTP handlers into the existing repository layer with no response changes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Decouple the Unreal matchmaking subsystem from the concrete EOS client so tests can inject a fake.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Simplify the nested feature-flag conditionals in pricing_rules.py while retaining every current branch and exception.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Clean up the Terraform module boundaries: move IAM policy assembly into modules/identity, preserve the resulting plan, and remove duplicate locals.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Reorganize the parser's token kinds into separate declaration and literal modules without changing its API or snapshots.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Quero separar o SessionManager em armazenamento, renovação e validação, mantendo exatamente o comportamento atual.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"pt"} +{"prompt":"Flatten the inheritance hierarchy under src/devices/drivers and replace the abstract base hooks with composition; device behavior must remain identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Separate command parsing from terminal I/O in the Nimbus CLI so the parser can be reused by the language server.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Why does checkout deadlock?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Trace the WASM memory leak","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Investigate flaky BLE pairing tests","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Find the missing frames","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Since yesterday's rollout, roughly one in twenty invoice finalizations returns 409 even though the client sends a fresh idempotency key. There are no duplicate rows, and retries sometimes succeed on a different pod. Diagnose the race using the Go service, Redis lock wrapper, and PostgreSQL transaction boundaries; add instrumentation locally if it helps, but first identify the actual cause.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"en"} -{"prompt":"Diagnose why sourcekit-lsp stops returning completions after Package.swift gains a local binary target.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Work out why the Kubernetes HPA reports unknown CPU for only the canary deployment.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Figure out why our ONNX model produces different logits on Core ML and Linux CPU for the same fixture.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.84,"slice":"core","lang":"en"} +{"prompt":"Why does checkout deadlock?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Trace the WASM memory leak","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Investigate flaky BLE pairing tests","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Find the missing frames","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Since yesterday's rollout, roughly one in twenty invoice finalizations returns 409 even though the client sends a fresh idempotency key. There are no duplicate rows, and retries sometimes succeed on a different pod. Diagnose the race using the Go service, Redis lock wrapper, and PostgreSQL transaction boundaries; add instrumentation locally if it helps, but first identify the actual cause.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Diagnose why sourcekit-lsp stops returning completions after Package.swift gains a local binary target.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Work out why the Kubernetes HPA reports unknown CPU for only the canary deployment.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Figure out why our ONNX model produces different logits on Core ML and Linux CPU for the same fixture.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Determine what is corrupting the final block of large ChaCha20-encrypted backup files.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"We have a React hydration warning only when the user's locale is ar-EG and the first page includes RelativeTime. Find the mismatch and explain why it is locale-specific.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Track down the 200 ms periodic stall in the ESP32 audio capture loop; DMA overruns appear only with Wi-Fi enabled.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"en"} -{"prompt":"Find why Gradle configuration cache misses whenever :app:bundleRelease follows :tools:generateLicenses.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"分析一下为什么 Rust service 在高并发下偶尔返回空的 JSON body，日志里没有 panic。","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"zh-CN"} -{"prompt":"Debug the intermittent freeze when the Godot client switches from lobby audio to spatial voice chat.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"Audit the OAuth callback handler","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Explain this arena allocator","purpose":"review","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"Review the migration diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Assess our CSP settings","purpose":"review","secondary":null,"mixed":false,"difficulty":0.48,"slice":"core","lang":"en"} -{"prompt":"Read services/payments/reconcile.go and evaluate whether its lease and transaction ordering can ever process a settlement twice. I only want an evidence-based assessment of the current code, including the relevant call paths and invariants; don't modify anything.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Compare the two proposed protobuf schemas in docs/events-v2.md for compatibility, evolvability, and decoding cost.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Walk me through how the compiler lowers async functions in src/lowering/coroutines.rs.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Check whether this Terraform module grants broader KMS access than the ECS tasks actually require.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Tell me what guarantees the current SQLite write-ahead-log wrapper makes during an app crash.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.56,"slice":"core","lang":"en"} +{"prompt":"We have a React hydration warning only when the user's locale is ar-EG and the first page includes RelativeTime. Find the mismatch and explain why it is locale-specific.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Track down the 200 ms periodic stall in the ESP32 audio capture loop; DMA overruns appear only with Wi-Fi enabled.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Find why Gradle configuration cache misses whenever :app:bundleRelease follows :tools:generateLicenses.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"分析一下为什么 Rust service 在高并发下偶尔返回空的 JSON body，日志里没有 panic。","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"Debug the intermittent freeze when the Godot client switches from lobby audio to spatial voice chat.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Audit the OAuth callback handler","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Explain this arena allocator","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Review the migration diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Assess our CSP settings","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Read services/payments/reconcile.go and evaluate whether its lease and transaction ordering can ever process a settlement twice. I only want an evidence-based assessment of the current code, including the relevant call paths and invariants; don't modify anything.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Compare the two proposed protobuf schemas in docs/events-v2.md for compatibility, evolvability, and decoding cost.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Walk me through how the compiler lowers async functions in src/lowering/coroutines.rs.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Check whether this Terraform module grants broader KMS access than the ECS tasks actually require.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Tell me what guarantees the current SQLite write-ahead-log wrapper makes during an app crash.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Evaluate the accessibility of the existing Compose checkout screen from its semantics tree and UI tests. List concrete issues, severity, and affected controls, but leave the implementation untouched.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Verify whether the new C++ ring buffer implementation is actually lock-free on ARM64, based on its atomics and memory ordering.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"en"} +{"prompt":"Verify whether the new C++ ring buffer implementation is actually lock-free on ARM64, based on its atomics and memory ordering.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Explícame qué hace el middleware TenantScope y dónde obtiene el tenant actual; no cambies código.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} -{"prompt":"Inspect the OpenAPI-generated Java client for unsafe logging of credentials or request bodies.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Document the backup restore command","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Write the 2.7 release notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"Summarize this pull request","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Draft a commit message","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.18,"slice":"core","lang":"en"} -{"prompt":"We need a proper README for tools/schema-sentry. Explain installation through cargo-binstall, the validate and diff subcommands, exit codes, GitHub Actions usage, the suppression file format, and how to troubleshoot generated-code false positives. Include concise examples based on the fixtures already in the repository and keep the tone practical.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Turn the notes in docs/adr-drafts/session-cookies.txt into a concise ADR with context, decision, alternatives, and consequences.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.47,"slice":"core","lang":"en"} -{"prompt":"Prepare a PR description for the PostgreSQL connection-pool changes, including rollout risk and the benchmarks in bench/results.md.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Update the contributor guide prose to explain the pnpm workspace bootstrap and local Supabase setup.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"core","lang":"en"} -{"prompt":"Produce KDoc for the public methods on BluetoothSession without narrating obvious getters.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.34,"slice":"core","lang":"en"} -{"prompt":"Compose a migration guide for users moving from Nimbus config v1 to v2, with before-and-after YAML and a section on removed keys.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} -{"prompt":"日本語でこの Swift package の導入手順を書いて。README の Installation セクションとして使いたい。","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"ja"} -{"prompt":"Translate the CLI error catalog into plain language suitable for support engineers, retaining command names and error codes.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"Add a changelog entry describing the new webhook retry semantics and the one backward-incompatible timeout change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"Design the implementation approach for adding passkey login to our existing session service; the deliverable is an engineering plan, not a patch.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.76,"slice":"boundary","lang":"en"} -{"prompt":"Before anyone writes code, specify how the React dashboard should support user-defined widgets, persistence, drag layout, and versioned widget contracts.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.79,"slice":"boundary","lang":"en"} -{"prompt":"Give me a migration strategy—not SQL—for moving vector embeddings from pgvector to Qdrant while searches stay online.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.81,"slice":"boundary","lang":"en"} -{"prompt":"Architect the rename of customer_id to account_id across events, storage, and public APIs, with compatibility stages and rollback gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.85,"slice":"boundary","lang":"en"} -{"prompt":"Erstelle einen technischen Plan für den neuen Rust-Ingestion-Service; bitte noch keinen Code implementieren.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"de"} -{"prompt":"Implement the examples shown in docs/webhooks.md as executable TypeScript samples; the prose is already final.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"boundary","lang":"en"} -{"prompt":"Turn the API proposal in RFC-019 into working Go handlers, validators, and repository methods.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"boundary","lang":"en"} -{"prompt":"Apply the already-approved PostgreSQL partitioning design in migrations/ and the archive worker.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.75,"slice":"boundary","lang":"en"} -{"prompt":"Code the server-side half of the new theme sync feature; the UI team only needs the preferences endpoint and schema.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Create the CLI subcommand described in DESIGN.md, including config parsing and machine-readable JSON output.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"Increase the modal's corner radius to 16px and nothing else.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.12,"slice":"boundary","lang":"en"} -{"prompt":"Make the disabled Save button visibly distinct using the existing neutral tokens.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.17,"slice":"boundary","lang":"en"} -{"prompt":"Put a small connection-status dot beside each device name in the SwiftUI list.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.24,"slice":"boundary","lang":"en"} -{"prompt":"Shift the mobile breakpoint layout so the filter chips wrap above the search field.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.25,"slice":"boundary","lang":"en"} -{"prompt":"Add a subtle pressed state to the Compose numeric keypad without touching its input logic.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.24,"slice":"boundary","lang":"en"} -{"prompt":"Rename getUsr to getUser in this file only.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"boundary","lang":"en"} -{"prompt":"Change the sidebar width constant from 280 to 296.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"boundary","lang":"en"} -{"prompt":"Correct the OpenAPI description for expiresAt; it's seconds since epoch, not milliseconds.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Set the button label to “Retry upload” instead of “Try again”.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"en"} -{"prompt":"Fix the known null check in UserBadge: compare avatarUrl, not displayName.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"boundary","lang":"en"} -{"prompt":"Rename Workspace to Organization throughout the app, API client, tests, and fixtures without changing behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Replace the term blacklist with denylist across source symbols, configuration keys, and compatibility aliases; existing configs must keep working.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Extract the 40-line inline formatter from renderReport into a named helper, keeping output byte-for-byte identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.37,"slice":"boundary","lang":"en"} -{"prompt":"Consolidate ApiError and NetworkError under one internal hierarchy, with no changes to public error codes or messages.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Move the feature flags into a dedicated package and update imports repository-wide; don't alter defaults or evaluation behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"Why does this supposedly read-only endpoint sometimes increment revision_number? Trace the cause.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Explain why the Android app crashes after rotation on the payment sheet and find the responsible lifecycle path.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Is there a reason the Rust parser returns a different AST only in release mode? Please investigate.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.76,"slice":"boundary","lang":"en"} -{"prompt":"What's making the first WebSocket message disappear whenever compression is negotiated?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"Walk through why CI hangs after all tests print as passed; something is still holding the process open.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.64,"slice":"boundary","lang":"en"} -{"prompt":"Why does the existing cache wrapper use singleflight around misses? Nothing is broken; I want to understand its concurrency model.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.48,"slice":"boundary","lang":"en"} -{"prompt":"Explain why this migration uses NOT VALID before validating the foreign key separately.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Summarize what changed in this diff for me, but don't produce release notes or edit any files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.34,"slice":"boundary","lang":"en"} -{"prompt":"Tell me whether the current Swift actor isolation around ImageCache is sound; there is no reported failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.61,"slice":"boundary","lang":"en"} -{"prompt":"Read the README proposal and judge whether it accurately describes what the code currently does.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.42,"slice":"boundary","lang":"en"} -{"prompt":"Write an explanation of the token-refresh flow for the API handbook; don't change the implementation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"boundary","lang":"en"} -{"prompt":"Document the GraphQL mutation's validation rules and error payloads from the existing resolver code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.44,"slice":"boundary","lang":"en"} -{"prompt":"Create an onboarding summary of how jobs move through the queue based on workers/dispatch.py.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Phrase the rationale for using two-phase deletion as an ADR; the design is already decided.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"boundary","lang":"en"} -{"prompt":"Rédige une explication courte de l'API de pagination pour notre guide développeur, avec un exemple curl.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.34,"slice":"boundary","lang":"fr"} +{"prompt":"Inspect the OpenAPI-generated Java client for unsafe logging of credentials or request bodies.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Document the backup restore command","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Write the 2.7 release notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Summarize this pull request","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Draft a commit message","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"We need a proper README for tools/schema-sentry. Explain installation through cargo-binstall, the validate and diff subcommands, exit codes, GitHub Actions usage, the suppression file format, and how to troubleshoot generated-code false positives. Include concise examples based on the fixtures already in the repository and keep the tone practical.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Turn the notes in docs/adr-drafts/session-cookies.txt into a concise ADR with context, decision, alternatives, and consequences.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Prepare a PR description for the PostgreSQL connection-pool changes, including rollout risk and the benchmarks in bench/results.md.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Update the contributor guide prose to explain the pnpm workspace bootstrap and local Supabase setup.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Produce KDoc for the public methods on BluetoothSession without narrating obvious getters.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Compose a migration guide for users moving from Nimbus config v1 to v2, with before-and-after YAML and a section on removed keys.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"日本語でこの Swift package の導入手順を書いて。README の Installation セクションとして使いたい。","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"ja"} +{"prompt":"Translate the CLI error catalog into plain language suitable for support engineers, retaining command names and error codes.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Add a changelog entry describing the new webhook retry semantics and the one backward-incompatible timeout change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Design the implementation approach for adding passkey login to our existing session service; the deliverable is an engineering plan, not a patch.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Before anyone writes code, specify how the React dashboard should support user-defined widgets, persistence, drag layout, and versioned widget contracts.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Give me a migration strategy—not SQL—for moving vector embeddings from pgvector to Qdrant while searches stay online.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Architect the rename of customer_id to account_id across events, storage, and public APIs, with compatibility stages and rollback gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"boundary","lang":"en"} +{"prompt":"Erstelle einen technischen Plan für den neuen Rust-Ingestion-Service; bitte noch keinen Code implementieren.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"de"} +{"prompt":"Implement the examples shown in docs/webhooks.md as executable TypeScript samples; the prose is already final.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Turn the API proposal in RFC-019 into working Go handlers, validators, and repository methods.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Apply the already-approved PostgreSQL partitioning design in migrations/ and the archive worker.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Code the server-side half of the new theme sync feature; the UI team only needs the preferences endpoint and schema.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the CLI subcommand described in DESIGN.md, including config parsing and machine-readable JSON output.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Increase the modal's corner radius to 16px and nothing else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Make the disabled Save button visibly distinct using the existing neutral tokens.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Put a small connection-status dot beside each device name in the SwiftUI list.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Shift the mobile breakpoint layout so the filter chips wrap above the search field.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Add a subtle pressed state to the Compose numeric keypad without touching its input logic.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Rename getUsr to getUser in this file only.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Change the sidebar width constant from 280 to 296.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Correct the OpenAPI description for expiresAt; it's seconds since epoch, not milliseconds.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Set the button label to “Retry upload” instead of “Try again”.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fix the known null check in UserBadge: compare avatarUrl, not displayName.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename Workspace to Organization throughout the app, API client, tests, and fixtures without changing behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Replace the term blacklist with denylist across source symbols, configuration keys, and compatibility aliases; existing configs must keep working.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Extract the 40-line inline formatter from renderReport into a named helper, keeping output byte-for-byte identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Consolidate ApiError and NetworkError under one internal hierarchy, with no changes to public error codes or messages.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Move the feature flags into a dedicated package and update imports repository-wide; don't alter defaults or evaluation behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Why does this supposedly read-only endpoint sometimes increment revision_number? Trace the cause.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Explain why the Android app crashes after rotation on the payment sheet and find the responsible lifecycle path.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Is there a reason the Rust parser returns a different AST only in release mode? Please investigate.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"What's making the first WebSocket message disappear whenever compression is negotiated?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Walk through why CI hangs after all tests print as passed; something is still holding the process open.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Why does the existing cache wrapper use singleflight around misses? Nothing is broken; I want to understand its concurrency model.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Explain why this migration uses NOT VALID before validating the foreign key separately.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Summarize what changed in this diff for me, but don't produce release notes or edit any files.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Tell me whether the current Swift actor isolation around ImageCache is sound; there is no reported failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Read the README proposal and judge whether it accurately describes what the code currently does.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Write an explanation of the token-refresh flow for the API handbook; don't change the implementation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Document the GraphQL mutation's validation rules and error payloads from the existing resolver code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Create an onboarding summary of how jobs move through the queue based on workers/dispatch.py.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Phrase the rationale for using two-phase deletion as an ADR; the design is already decided.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Rédige une explication courte de l'API de pagination pour notre guide développeur, avec un exemple curl.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"fr"} {"prompt":"Plan and implement tenant-scoped API keys, including schema changes, rotation, audit events, rollout stages, and tests.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"Design and build a SwiftUI command palette for the macOS editor, with keyboard navigation and fuzzy search.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"Lay out the migration and then add exactly-once-ish processing for Stripe subscription webhooks using our existing inbox table.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.86,"slice":"mixed","lang":"en"} -{"prompt":"Implement the new backup verifier and write an operator-facing section for the runbook explaining its exit codes.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"Add the protobuf compatibility checker, then review the current event schemas and report every violation it finds.","purpose":"backendImpl","secondary":"review","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} +{"prompt":"Design and build a SwiftUI command palette for the macOS editor, with keyboard navigation and fuzzy search.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Lay out the migration and then add exactly-once-ish processing for Stripe subscription webhooks using our existing inbox table.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Implement the new backup verifier and write an operator-facing section for the runbook explaining its exit codes.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Add the protobuf compatibility checker, then review the current event schemas and report every violation it finds.","purpose":"backendImpl","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Build the resumable upload endpoint and document its request headers and failure responses in the API guide.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Create the React trace waterfall and explain the new keyboard interactions in docs/accessibility.md.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.66,"slice":"mixed","lang":"en"} -{"prompt":"Implement the iOS medication schedule editor, then audit the completed screen for VoiceOver and Dynamic Type issues.","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Change the default batch size to 500 and add a short changelog note about the new default.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.22,"slice":"mixed","lang":"en"} -{"prompt":"Fix the known CSS typo in --surface-elevated and update the screenshot-baseline note.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.18,"slice":"mixed","lang":"en"} +{"prompt":"Create the React trace waterfall and explain the new keyboard interactions in docs/accessibility.md.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Implement the iOS medication schedule editor, then audit the completed screen for VoiceOver and Dynamic Type issues.","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Change the default batch size to 500 and add a short changelog note about the new default.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.2,"slice":"mixed","lang":"en"} +{"prompt":"Fix the known CSS typo in --surface-elevated and update the screenshot-baseline note.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.1,"slice":"mixed","lang":"en"} {"prompt":"Split the monolithic SyncCoordinator without behavior changes, then document the resulting module boundaries for contributors.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Rename LegacyAccount across the codebase and review the final diff for accidental wire-format changes.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.66,"slice":"mixed","lang":"en"} -{"prompt":"Find and fix the intermittent deadlock in the Java ingestion worker, then add a troubleshooting note to its runbook.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.82,"slice":"mixed","lang":"en"} -{"prompt":"Diagnose the Metal rendering artifacts and, once understood, clean up the duplicated texture-upload paths without changing other behavior.","purpose":"debugging","secondary":"refactor","mixed":true,"difficulty":0.86,"slice":"mixed","lang":"en"} -{"prompt":"Review the current secrets-handling code and turn your findings into a security-audit document under docs/audits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed PostgreSQL schema, then implement the approved indexes and constraints if the design is sound.","purpose":"review","secondary":"backendImpl","mixed":true,"difficulty":0.74,"slice":"mixed","lang":"en"} -{"prompt":"Walk through the current Compose navigation, then produce an onboarding note explaining deep links and back-stack ownership.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.57,"slice":"mixed","lang":"en"} -{"prompt":"Write the migration guide and add a compatibility shim for clients still sending page instead of cursor.","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.64,"slice":"mixed","lang":"en"} -{"prompt":"Prepare release notes for the new dashboard filters and implement the missing reset-all button shown in the design.","purpose":"writing","secondary":"frontendImpl","mixed":true,"difficulty":0.52,"slice":"mixed","lang":"en"} -{"prompt":"Document how the allocator works and restructure its internal free-list helpers so the explanation maps cleanly to the code, preserving behavior.","purpose":"writing","secondary":"refactor","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Picking up the authorization overhaul. Notes from the platform channel:\n\n- service tokens currently share the user JWT verifier\n- partner traffic will arrive through Envoy with an SPIFFE identity\n- batch jobs run in three clusters and may be disconnected for 20 minutes\n- security wants token revocation under five minutes\n- mobile sessions must remain unchanged\n- we cannot coordinate a flag day with the reporting team\n\nConstraints from SEC-284:\n1. Keys live in regional KMS instances.\n2. Every impersonation decision is queryable for seven years.\n3. EU credentials cannot be validated through a US control plane.\n4. Existing tokens must remain valid during transition.\n\nPlease turn this into a staged architecture and migration plan. Include trust boundaries, token formats, key distribution, revocation, audit storage, failure modes, compatibility phases, observability, and explicit rollback gates. No code in this pass.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"pasted-context","lang":"en"} -{"prompt":"Here is the whiteboard dump from yesterday's storage meeting:\n\nCurrent: one 14 TB PostgreSQL primary, two async replicas, pgBackRest nightly, logical replication feeding analytics.\nGrowth: events table +220 GB/month; attachments metadata +40 GB/month.\nPain: vacuum spikes, analytics slots fall behind, restores take 11 hours.\nRequirements:\n- restore a single tenant within 30 minutes\n- retain immutable audit rows for 7 years\n- no more than 45 seconds of write unavailability\n- engineers must still query recent events with SQL\n- finance quarter-end cannot move\n\nIdeas mentioned: monthly partitions, Citus, separate audit cluster, S3/Parquet archive, dual-write service. Nobody agreed on an option.\n\nDevelop a decision document and migration roadmap. Compare the alternatives, recommend one, define validation checkpoints and rollback, and identify which assumptions need measurement before implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"pasted-context","lang":"en"} -{"prompt":"Ticket PAY-611:\n\nPOST /v2/payouts should support an optional destination_override used only by treasury operators.\n\nAcceptance notes pasted from Slack:\n- verify operator role through the existing Cedar authorizer\n- destination must belong to the same legal entity\n- store both requested and resolved destinations\n- require Idempotency-Key\n- emit payout.destination_overridden after commit\n- return the ordinary payout resource; don't expose internal policy details\n- rejected overrides use code destination_not_allowed\n- existing clients and non-override payouts cannot change\n\nRelevant files:\nservices/payouts/http/create.ts\nservices/payouts/domain/payout.ts\nservices/payouts/repo/postgres.ts\npackages/events/payout.proto\n\nImplement the endpoint behavior, schema migration, event emission, and tests. Follow the transaction/outbox pattern already used by payout cancellation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"TODO copied from crates/harbor-sync/src/worker.rs:\n\n// A lease is valid for 30 seconds.\n// 1. claim up to config.batch_size rows with SKIP LOCKED\n// 2. mark claimed_by and lease_until in the same transaction\n// 3. upload blobs concurrently, max eight in flight\n// 4. renew leases while an upload is active\n// 5. commit remote etag only if this worker still owns the lease\n// 6. retry 429 and 5xx with jitter; never retry 4xx except 408\n// 7. after ten attempts, move metadata to dead_jobs\n\nThe existing skeleton has claim_jobs and finish_job signatures plus a reqwest client, but process_batch is empty. Metrics already exist for claimed, completed, retried, and lease_lost.\n\nFill in the worker implementation and add database-backed concurrency tests proving two workers cannot finalize the same job.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.83,"slice":"pasted-context","lang":"en"} -{"prompt":"Design handoff from Figma, copied into the issue:\n\nScreen: Fleet / Vehicle detail / Energy\nDesktop 1440:\n- header remains sticky below global nav\n- left column 360 px with charge card and connector metadata\n- right column fills remaining width with 24-hour consumption chart\n- warning banner appears between header and columns when battery health < 70%\nTablet: columns become 5/7 ratio\nMobile < 720: chart first, card second, banner stays first\nStates: live, stale (>5 min), offline, no samples, loading\nInteractions: range tabs, chart tooltip, keyboard arrow traversal, reconnect CTA\nTokens: use --space-* and semantic status colors; no raw hex\n\nBuild this view in apps/fleet/src/routes/VehicleEnergy.tsx using the existing ECharts wrapper and component library. Add Storybook stories for every listed state.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"pasted-context","lang":"en"} -{"prompt":"From IOS-932:\n\nThe recorder screen currently has only a red circle and elapsed text. Product comments:\n“Make it feel calm, not medical.”\n“Users must be able to tell paused from recording without relying on color.”\n“Keep controls reachable one-handed.”\n\nRequired layout:\n- waveform occupies upper 40%\n- status label and elapsed time centered\n- primary record/pause control at bottom, 64 pt minimum\n- secondary discard and finish actions flank it\n- safe-area behavior on iPhone SE through Pro Max\n- Dynamic Type through accessibility sizes\n- reduced-motion mode replaces waveform interpolation with discrete bars\n- VoiceOver announces state changes, not every timer tick\n\nImplement RecorderView and its visual states in SwiftUI. The recorder engine and state model already exist; do not rewrite audio capture.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Issue UI-1842 context:\n\nCurrent component:\n\n\nQA notes:\n- at 200% browser zoom, clear button overlaps the final two characters\n- Windows high-contrast mode hides the magnify icon\n- focus ring gets clipped inside the data-grid toolbar\n- Escape should clear only when nonempty\n- RTL screenshot has icon and clear button on the wrong sides\n\nExpected snapshots:\nsearch-empty.png\nsearch-value.png\nsearch-focus.png\nsearch-rtl.png\nsearch-high-contrast.png\n\nPlease update packages/ui/src/SearchField.tsx and its CSS to handle these visual and interaction states. Retain the public props and add focused component tests for keyboard clearing and RTL placement.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} -{"prompt":"Release checklist excerpt:\n\n[ ] api image points at 4.19.3\n[x] worker image points at 4.19.3\n[x] migration image points at 4.19.3\n[x] chart appVersion is 4.19.3\n[x] changelog generated\n\nCI output:\nhelm template deploy/charts/atlas -f deploy/environments/prod.yaml\ncontainer image mismatch: expected registry.corp/atlas-api:4.19.3\nactual registry.corp/atlas-api:4.19.2\nsource: deploy/environments/prod.yaml:17\n\nThe release manager confirmed there is no special API rollback pin; this value was simply missed in the bump. Change that one image tag to 4.19.3 and leave all other values alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"pasted-context","lang":"en"} -{"prompt":"Bug ticket with known resolution:\n\nObserved label in Settings > Storage:\n“Keep downloads for 30 day”\n\nCopy review:\nUse plural “days”. This string is not parameterized; the duration is fixed at 30 for this release. Translations are handled in a separate localization job.\n\nFiles found by search:\napps/desktop/src/settings/storage/RetentionRow.tsx:88\napps/desktop/src/settings/storage/__snapshots__/RetentionRow.test.tsx.snap:14\n\nExpected:\n“Keep downloads for 30 days”\n\nPlease make the copy correction and update the corresponding snapshot. Do not alter the retention calculation, localization catalogs, or layout.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"pasted-context","lang":"en"} -{"prompt":"CI failure after the dependency refresh:\n\nWarning: Input 'cache-dependency-path' points to a missing file: ui/package-lock.json\nDetected package manager: pnpm\nWorkspace lockfile: ./pnpm-lock.yaml\nAction: actions/setup-node@v4\nWorkflow: .github/workflows/web.yml\n\nRelevant YAML:\n- uses: actions/setup-node@v4\n with:\n node-version: 22\n cache: pnpm\n cache-dependency-path: ui/package-lock.json\n\nThe repository switched from npm to a root pnpm workspace last week. The correct cache dependency is pnpm-lock.yaml; no per-package lockfiles remain. Update that single workflow value so dependency caching works again. Don't change Node versions or workflow steps.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.11,"slice":"pasted-context","lang":"en"} -{"prompt":"Notes from code archaeology:\n\npackages/net/src/httpClient.ts owns timeout, auth headers, retries, JSON decoding\npackages/sync/src/request.ts copies timeout, auth headers, retries, JSON decoding\napps/desktop/src/lib/fetcher.ts copies auth headers and JSON decoding, then wraps errors differently\n\nConstraints:\n- public exports cannot move\n- browser and Node bundles must stay separate\n- error names/messages are snapshot-tested\n- retry timing is covered by fake-clock tests\n- desktop adds one X-Client header\n- generated SDK code is out of scope\n\nThere is no intended behavior change. Extract a shared internal request core, leave thin environment adapters in place, remove duplication, and keep all existing snapshots and wire-level tests passing.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.75,"slice":"pasted-context","lang":"en"} -{"prompt":"Refactoring brief copied from ENG-309:\n\nOld names:\nWorkspaceMember\nworkspace_member_id\nworkspace.membership.created\n/workspaces/{id}/members\n\nNew product terminology:\nOrganizationMember\norganization_member_id\norganization.membership.created\n/organizations/{id}/members\n\nCompatibility requirements:\n- existing REST paths remain available for two releases\n- old event names continue to decode\n- database columns are NOT renamed in this change\n- SDK aliases should be deprecated, not removed\n- metrics dashboards still query workspace_* labels\n- behavior and authorization rules stay identical\n\nPerform the terminology restructure across domain types, internal packages, API aliases, generated fixtures, and tests. Keep compatibility adapters explicit and avoid unrelated formatting.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Cleanup list from the emulator maintainers:\n\nsrc/cpu/opcodes_load.cpp: decodeLoad and decodeStore each contain the same addressing-mode switch\nsrc/cpu/opcodes_math.cpp: decodeAdd repeats six of those cases\nsrc/cpu/disassemble.cpp has a fourth copy that emits text instead of instructions\n\nImportant invariants:\n- cycle counts cannot change\n- illegal opcode behavior remains byte-for-byte identical\n- disassembly strings are golden-tested\n- the hot execution path must not allocate\n- C++17 only; no std::variant in this target\n\nConsolidate address decoding into a reusable, allocation-free helper and update the callers. This is structural cleanup only; preserve emulator output, timing metadata, and error behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.72,"slice":"pasted-context","lang":"en"} -{"prompt":"Production log tail:\n\n2026-07-29T18:41:02.114Z pod=checkout-7b9 req=8fa reserve inventory sku=JUNO-4 qty=1 ok\n2026-07-29T18:41:02.129Z pod=checkout-7b9 req=8fa begin payment intent pi_883\n2026-07-29T18:41:32.131Z pod=checkout-7b9 req=8fa context deadline exceeded\n2026-07-29T18:41:32.133Z pod=checkout-7b9 req=8fa release inventory affected=1\n2026-07-29T18:41:33.004Z webhook=payment_succeeded intent=pi_883 order lookup=none\n2026-07-29T18:46:02.201Z sweeper intent=pi_883 marked_orphan=true\n\nThis started after enabling HTTP/2 to the payment provider. p95 is unchanged, but about 0.3% of intents finish just after our 30-second deadline and customers get charged without orders. Determine why our reconciliation path cannot recover these and identify the safest fix. Add a regression test once the cause is established.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Failing test output from the ARM runner:\n\n---- ring::tests::wraparound_concurrent stdout ----\nthread 'producer-2' panicked at src/ring.rs:188: assertion failed: sequence >= last_sequence\nleft: 4294967295\nright: 0\nseed=9811442 capacity=1024 operations=900000\n\nx86_64 Linux: 10,000 passes\nApple Silicon: 3 failures in 2,000 passes\nRaspberry Pi 5: 41 failures in 2,000 passes\nDebug builds have not failed.\n\nThe queue uses AtomicU32 sequence counters, Acquire loads, and Release stores. A recent optimization replaced wrapping_sub with a signed cast in slot_ready. Investigate whether the failures come from counter wraparound, memory ordering, or the optimization. Explain the evidence and fix the actual defect with a deterministic regression test.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Browser console and request trace:\n\nWarning: Text content did not match. Server: “in 1 day” Client: “tomorrow”\nComponent stack: RelativeDeadline > DeploymentRow > DeploymentsTable\nLocale: en-GB\nServer timezone: UTC\nBrowser timezone: Europe/London\nTimestamp: 2026-03-29T00:30:00Z\n\nSSR HTML data-now=\"1774744200000\"\nHydration begins 1.8 seconds later.\n\nIt reproduces only around daylight-saving transitions and only for rows inside the first 48 hours. Passing suppressHydrationWarning hides it but leaves the text visibly changing. Find the underlying source of nondeterminism in src/time/relativeDeadline.ts and the server loader. Implement a robust correction and add fixtures for both DST boundaries.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Security review request pasted from the ticket:\n\nScope:\nservices/auth/src/tokenExchange.ts\nservices/auth/src/jwksCache.ts\npackages/crypto/src/dpop.ts\ninfra/envoy/auth-filter.yaml\n\nQuestions from the reviewer:\n- Can an access token issued to mobile be replayed by the partner gateway?\n- Is jti uniqueness enforced or merely logged?\n- What happens while the issuer's JWKS endpoint is unreachable?\n- Does the forwarded client certificate header have a trusted provenance?\n- Are audience aliases widening access unexpectedly?\n\nOut of scope: changing code, rotating keys, or editing deployment configuration.\n\nRead the current implementation and configuration, trace each trust decision, and produce findings with severity, evidence, and exploit preconditions. Clearly distinguish confirmed issues from defense-in-depth suggestions.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"PR diff excerpt:\n\n- await db.query('DELETE FROM sessions WHERE user_id = $1', [id])\n+ await db.transaction(async tx => {\n+ await tx.query('UPDATE users SET deleted_at = now() WHERE id = $1', [id])\n+ await tx.query('INSERT INTO erasure_jobs(user_id) VALUES($1)', [id])\n+ })\n\nRelated worker:\nSELECT user_id FROM erasure_jobs\nWHERE completed_at IS NULL\nORDER BY created_at\nLIMIT 100\nFOR UPDATE SKIP LOCKED\n\nProduct requirement says login must stop immediately, personal data may be erased asynchronously, and repeated deletion requests must be harmless. Please review the existing diff and worker path for correctness, privacy gaps, idempotency, and transaction races. Do not modify the branch; return concrete review comments with file references.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"pasted-context","lang":"en"} -{"prompt":"Raw notes for the release announcement:\n\nv5.4 “Kestrel”\n- query planner now prunes time partitions before expanding views\n- import command supports zstd CSV streams\n- macOS client can pin saved searches\n- deprecated v1 token endpoint remains available but logs warnings\n- fixed crash on empty GeoJSON geometry collections\n- config rename: cache.maxItems -> cache.capacity; old key works until 6.0\n- benchmark: dashboard p95 820 ms -> 310 ms on demo dataset\n- known issue: first launch may briefly show an empty recent-project list\n- contributors: Mei L., Arjun S., Noa K., Iris P.\n\nTurn these into polished release notes with sections for highlights, compatibility, fixes, known issues, and acknowledgements. Avoid marketing hype and preserve the exact deprecation timeline.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"pasted-context","lang":"en"} -{"prompt":"README scratchpad from tools/packet-lens:\n\nPurpose: inspect our framed TCP protocol without running Wireshark dissectors.\nInstall: cargo install packet-lens\nInputs: pcap file, stdin hex, or live interface with privileges\nCommands: decode, filter, stats\nUseful flags: --schema, --direction, --json, --strict\nExit 0 decoded all frames; 2 malformed input; 3 schema mismatch; 4 capture permission\nSchemas live in ~/.config/packet-lens/schemas and can include another file.\nExamples in fixtures/demo-v3.pcap and fixtures/bad-checksum.hex.\nWarning: --json may contain customer payloads.\n\nWrite a complete README from this material. Include quick start, command examples, schema lookup behavior, exit codes, security warning, troubleshooting, and a short development section based on Cargo.toml targets.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.48,"slice":"pasted-context","lang":"en"} -{"prompt":"continue the architecture thing","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.62,"slice":"vague-eval","lang":"en"} -{"prompt":"finish yesterday's worker","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"tiny config thing pls","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"vague-eval","lang":"en"} -{"prompt":"clean up that module","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.44,"slice":"vague-eval","lang":"en"} -{"prompt":"something's off in prod","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"vague-eval","lang":"en"} -{"prompt":"take a look at the auth code","purpose":"review","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"thoughts on this implementation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.46,"slice":"vague-eval","lang":"en"} -{"prompt":"write up what we changed","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.32,"slice":"vague-eval","lang":"en"} -{"prompt":"need words for the release","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.28,"slice":"vague-eval","lang":"en"} -{"prompt":"Plan the ROS 2 migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Outline our feature-store architecture","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Design crash-safe OTA updates","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.83,"slice":"core","lang":"en"} -{"prompt":"Sequence the CockroachDB cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Our collaborative CAD editor needs offline branches, peer-to-peer exchange on factory networks, and eventual synchronization through the cloud. Write an architecture proposal covering operation representation, merge semantics, tombstone retention, large binary assets, identity, encryption, partial replication, and recovery from divergent histories. Compare CRDT and operation-log approaches, then recommend staged validation work without implementing the editor.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} +{"prompt":"Rename LegacyAccount across the codebase and review the final diff for accidental wire-format changes.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Find and fix the intermittent deadlock in the Java ingestion worker, then add a troubleshooting note to its runbook.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Diagnose the Metal rendering artifacts and, once understood, clean up the duplicated texture-upload paths without changing other behavior.","purpose":"debugging","secondary":"refactor","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Review the current secrets-handling code and turn your findings into a security-audit document under docs/audits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed PostgreSQL schema, then implement the approved indexes and constraints if the design is sound.","purpose":"review","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Walk through the current Compose navigation, then produce an onboarding note explaining deep links and back-stack ownership.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Write the migration guide and add a compatibility shim for clients still sending page instead of cursor.","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Prepare release notes for the new dashboard filters and implement the missing reset-all button shown in the design.","purpose":"writing","secondary":"frontendImpl","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Document how the allocator works and restructure its internal free-list helpers so the explanation maps cleanly to the code, preserving behavior.","purpose":"writing","secondary":"refactor","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Picking up the authorization overhaul. Notes from the platform channel:\n\n- service tokens currently share the user JWT verifier\n- partner traffic will arrive through Envoy with an SPIFFE identity\n- batch jobs run in three clusters and may be disconnected for 20 minutes\n- security wants token revocation under five minutes\n- mobile sessions must remain unchanged\n- we cannot coordinate a flag day with the reporting team\n\nConstraints from SEC-284:\n1. Keys live in regional KMS instances.\n2. Every impersonation decision is queryable for seven years.\n3. EU credentials cannot be validated through a US control plane.\n4. Existing tokens must remain valid during transition.\n\nPlease turn this into a staged architecture and migration plan. Include trust boundaries, token formats, key distribution, revocation, audit storage, failure modes, compatibility phases, observability, and explicit rollback gates. No code in this pass.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Here is the whiteboard dump from yesterday's storage meeting:\n\nCurrent: one 14 TB PostgreSQL primary, two async replicas, pgBackRest nightly, logical replication feeding analytics.\nGrowth: events table +220 GB/month; attachments metadata +40 GB/month.\nPain: vacuum spikes, analytics slots fall behind, restores take 11 hours.\nRequirements:\n- restore a single tenant within 30 minutes\n- retain immutable audit rows for 7 years\n- no more than 45 seconds of write unavailability\n- engineers must still query recent events with SQL\n- finance quarter-end cannot move\n\nIdeas mentioned: monthly partitions, Citus, separate audit cluster, S3/Parquet archive, dual-write service. Nobody agreed on an option.\n\nDevelop a decision document and migration roadmap. Compare the alternatives, recommend one, define validation checkpoints and rollback, and identify which assumptions need measurement before implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Ticket PAY-611:\n\nPOST /v2/payouts should support an optional destination_override used only by treasury operators.\n\nAcceptance notes pasted from Slack:\n- verify operator role through the existing Cedar authorizer\n- destination must belong to the same legal entity\n- store both requested and resolved destinations\n- require Idempotency-Key\n- emit payout.destination_overridden after commit\n- return the ordinary payout resource; don't expose internal policy details\n- rejected overrides use code destination_not_allowed\n- existing clients and non-override payouts cannot change\n\nRelevant files:\nservices/payouts/http/create.ts\nservices/payouts/domain/payout.ts\nservices/payouts/repo/postgres.ts\npackages/events/payout.proto\n\nImplement the endpoint behavior, schema migration, event emission, and tests. Follow the transaction/outbox pattern already used by payout cancellation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"TODO copied from crates/harbor-sync/src/worker.rs:\n\n// A lease is valid for 30 seconds.\n// 1. claim up to config.batch_size rows with SKIP LOCKED\n// 2. mark claimed_by and lease_until in the same transaction\n// 3. upload blobs concurrently, max eight in flight\n// 4. renew leases while an upload is active\n// 5. commit remote etag only if this worker still owns the lease\n// 6. retry 429 and 5xx with jitter; never retry 4xx except 408\n// 7. after ten attempts, move metadata to dead_jobs\n\nThe existing skeleton has claim_jobs and finish_job signatures plus a reqwest client, but process_batch is empty. Metrics already exist for claimed, completed, retried, and lease_lost.\n\nFill in the worker implementation and add database-backed concurrency tests proving two workers cannot finalize the same job.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Design handoff from Figma, copied into the issue:\n\nScreen: Fleet / Vehicle detail / Energy\nDesktop 1440:\n- header remains sticky below global nav\n- left column 360 px with charge card and connector metadata\n- right column fills remaining width with 24-hour consumption chart\n- warning banner appears between header and columns when battery health < 70%\nTablet: columns become 5/7 ratio\nMobile < 720: chart first, card second, banner stays first\nStates: live, stale (>5 min), offline, no samples, loading\nInteractions: range tabs, chart tooltip, keyboard arrow traversal, reconnect CTA\nTokens: use --space-* and semantic status colors; no raw hex\n\nBuild this view in apps/fleet/src/routes/VehicleEnergy.tsx using the existing ECharts wrapper and component library. Add Storybook stories for every listed state.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"From IOS-932:\n\nThe recorder screen currently has only a red circle and elapsed text. Product comments:\n“Make it feel calm, not medical.”\n“Users must be able to tell paused from recording without relying on color.”\n“Keep controls reachable one-handed.”\n\nRequired layout:\n- waveform occupies upper 40%\n- status label and elapsed time centered\n- primary record/pause control at bottom, 64 pt minimum\n- secondary discard and finish actions flank it\n- safe-area behavior on iPhone SE through Pro Max\n- Dynamic Type through accessibility sizes\n- reduced-motion mode replaces waveform interpolation with discrete bars\n- VoiceOver announces state changes, not every timer tick\n\nImplement RecorderView and its visual states in SwiftUI. The recorder engine and state model already exist; do not rewrite audio capture.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Issue UI-1842 context:\n\nCurrent component:\n\n\nQA notes:\n- at 200% browser zoom, clear button overlaps the final two characters\n- Windows high-contrast mode hides the magnify icon\n- focus ring gets clipped inside the data-grid toolbar\n- Escape should clear only when nonempty\n- RTL screenshot has icon and clear button on the wrong sides\n\nExpected snapshots:\nsearch-empty.png\nsearch-value.png\nsearch-focus.png\nsearch-rtl.png\nsearch-high-contrast.png\n\nPlease update packages/ui/src/SearchField.tsx and its CSS to handle these visual and interaction states. Retain the public props and add focused component tests for keyboard clearing and RTL placement.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Release checklist excerpt:\n\n[ ] api image points at 4.19.3\n[x] worker image points at 4.19.3\n[x] migration image points at 4.19.3\n[x] chart appVersion is 4.19.3\n[x] changelog generated\n\nCI output:\nhelm template deploy/charts/atlas -f deploy/environments/prod.yaml\ncontainer image mismatch: expected registry.corp/atlas-api:4.19.3\nactual registry.corp/atlas-api:4.19.2\nsource: deploy/environments/prod.yaml:17\n\nThe release manager confirmed there is no special API rollback pin; this value was simply missed in the bump. Change that one image tag to 4.19.3 and leave all other values alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Bug ticket with known resolution:\n\nObserved label in Settings > Storage:\n“Keep downloads for 30 day”\n\nCopy review:\nUse plural “days”. This string is not parameterized; the duration is fixed at 30 for this release. Translations are handled in a separate localization job.\n\nFiles found by search:\napps/desktop/src/settings/storage/RetentionRow.tsx:88\napps/desktop/src/settings/storage/__snapshots__/RetentionRow.test.tsx.snap:14\n\nExpected:\n“Keep downloads for 30 days”\n\nPlease make the copy correction and update the corresponding snapshot. Do not alter the retention calculation, localization catalogs, or layout.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"CI failure after the dependency refresh:\n\nWarning: Input 'cache-dependency-path' points to a missing file: ui/package-lock.json\nDetected package manager: pnpm\nWorkspace lockfile: ./pnpm-lock.yaml\nAction: actions/setup-node@v4\nWorkflow: .github/workflows/web.yml\n\nRelevant YAML:\n- uses: actions/setup-node@v4\n with:\n node-version: 22\n cache: pnpm\n cache-dependency-path: ui/package-lock.json\n\nThe repository switched from npm to a root pnpm workspace last week. The correct cache dependency is pnpm-lock.yaml; no per-package lockfiles remain. Update that single workflow value so dependency caching works again. Don't change Node versions or workflow steps.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Notes from code archaeology:\n\npackages/net/src/httpClient.ts owns timeout, auth headers, retries, JSON decoding\npackages/sync/src/request.ts copies timeout, auth headers, retries, JSON decoding\napps/desktop/src/lib/fetcher.ts copies auth headers and JSON decoding, then wraps errors differently\n\nConstraints:\n- public exports cannot move\n- browser and Node bundles must stay separate\n- error names/messages are snapshot-tested\n- retry timing is covered by fake-clock tests\n- desktop adds one X-Client header\n- generated SDK code is out of scope\n\nThere is no intended behavior change. Extract a shared internal request core, leave thin environment adapters in place, remove duplication, and keep all existing snapshots and wire-level tests passing.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Refactoring brief copied from ENG-309:\n\nOld names:\nWorkspaceMember\nworkspace_member_id\nworkspace.membership.created\n/workspaces/{id}/members\n\nNew product terminology:\nOrganizationMember\norganization_member_id\norganization.membership.created\n/organizations/{id}/members\n\nCompatibility requirements:\n- existing REST paths remain available for two releases\n- old event names continue to decode\n- database columns are NOT renamed in this change\n- SDK aliases should be deprecated, not removed\n- metrics dashboards still query workspace_* labels\n- behavior and authorization rules stay identical\n\nPerform the terminology restructure across domain types, internal packages, API aliases, generated fixtures, and tests. Keep compatibility adapters explicit and avoid unrelated formatting.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Cleanup list from the emulator maintainers:\n\nsrc/cpu/opcodes_load.cpp: decodeLoad and decodeStore each contain the same addressing-mode switch\nsrc/cpu/opcodes_math.cpp: decodeAdd repeats six of those cases\nsrc/cpu/disassemble.cpp has a fourth copy that emits text instead of instructions\n\nImportant invariants:\n- cycle counts cannot change\n- illegal opcode behavior remains byte-for-byte identical\n- disassembly strings are golden-tested\n- the hot execution path must not allocate\n- C++17 only; no std::variant in this target\n\nConsolidate address decoding into a reusable, allocation-free helper and update the callers. This is structural cleanup only; preserve emulator output, timing metadata, and error behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Production log tail:\n\n2026-07-29T18:41:02.114Z pod=checkout-7b9 req=8fa reserve inventory sku=JUNO-4 qty=1 ok\n2026-07-29T18:41:02.129Z pod=checkout-7b9 req=8fa begin payment intent pi_883\n2026-07-29T18:41:32.131Z pod=checkout-7b9 req=8fa context deadline exceeded\n2026-07-29T18:41:32.133Z pod=checkout-7b9 req=8fa release inventory affected=1\n2026-07-29T18:41:33.004Z webhook=payment_succeeded intent=pi_883 order lookup=none\n2026-07-29T18:46:02.201Z sweeper intent=pi_883 marked_orphan=true\n\nThis started after enabling HTTP/2 to the payment provider. p95 is unchanged, but about 0.3% of intents finish just after our 30-second deadline and customers get charged without orders. Determine why our reconciliation path cannot recover these and identify the safest fix. Add a regression test once the cause is established.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Failing test output from the ARM runner:\n\n---- ring::tests::wraparound_concurrent stdout ----\nthread 'producer-2' panicked at src/ring.rs:188: assertion failed: sequence >= last_sequence\nleft: 4294967295\nright: 0\nseed=9811442 capacity=1024 operations=900000\n\nx86_64 Linux: 10,000 passes\nApple Silicon: 3 failures in 2,000 passes\nRaspberry Pi 5: 41 failures in 2,000 passes\nDebug builds have not failed.\n\nThe queue uses AtomicU32 sequence counters, Acquire loads, and Release stores. A recent optimization replaced wrapping_sub with a signed cast in slot_ready. Investigate whether the failures come from counter wraparound, memory ordering, or the optimization. Explain the evidence and fix the actual defect with a deterministic regression test.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Browser console and request trace:\n\nWarning: Text content did not match. Server: “in 1 day” Client: “tomorrow”\nComponent stack: RelativeDeadline > DeploymentRow > DeploymentsTable\nLocale: en-GB\nServer timezone: UTC\nBrowser timezone: Europe/London\nTimestamp: 2026-03-29T00:30:00Z\n\nSSR HTML data-now=\"1774744200000\"\nHydration begins 1.8 seconds later.\n\nIt reproduces only around daylight-saving transitions and only for rows inside the first 48 hours. Passing suppressHydrationWarning hides it but leaves the text visibly changing. Find the underlying source of nondeterminism in src/time/relativeDeadline.ts and the server loader. Implement a robust correction and add fixtures for both DST boundaries.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Security review request pasted from the ticket:\n\nScope:\nservices/auth/src/tokenExchange.ts\nservices/auth/src/jwksCache.ts\npackages/crypto/src/dpop.ts\ninfra/envoy/auth-filter.yaml\n\nQuestions from the reviewer:\n- Can an access token issued to mobile be replayed by the partner gateway?\n- Is jti uniqueness enforced or merely logged?\n- What happens while the issuer's JWKS endpoint is unreachable?\n- Does the forwarded client certificate header have a trusted provenance?\n- Are audience aliases widening access unexpectedly?\n\nOut of scope: changing code, rotating keys, or editing deployment configuration.\n\nRead the current implementation and configuration, trace each trust decision, and produce findings with severity, evidence, and exploit preconditions. Clearly distinguish confirmed issues from defense-in-depth suggestions.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"PR diff excerpt:\n\n- await db.query('DELETE FROM sessions WHERE user_id = $1', [id])\n+ await db.transaction(async tx => {\n+ await tx.query('UPDATE users SET deleted_at = now() WHERE id = $1', [id])\n+ await tx.query('INSERT INTO erasure_jobs(user_id) VALUES($1)', [id])\n+ })\n\nRelated worker:\nSELECT user_id FROM erasure_jobs\nWHERE completed_at IS NULL\nORDER BY created_at\nLIMIT 100\nFOR UPDATE SKIP LOCKED\n\nProduct requirement says login must stop immediately, personal data may be erased asynchronously, and repeated deletion requests must be harmless. Please review the existing diff and worker path for correctness, privacy gaps, idempotency, and transaction races. Do not modify the branch; return concrete review comments with file references.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Raw notes for the release announcement:\n\nv5.4 “Kestrel”\n- query planner now prunes time partitions before expanding views\n- import command supports zstd CSV streams\n- macOS client can pin saved searches\n- deprecated v1 token endpoint remains available but logs warnings\n- fixed crash on empty GeoJSON geometry collections\n- config rename: cache.maxItems -> cache.capacity; old key works until 6.0\n- benchmark: dashboard p95 820 ms -> 310 ms on demo dataset\n- known issue: first launch may briefly show an empty recent-project list\n- contributors: Mei L., Arjun S., Noa K., Iris P.\n\nTurn these into polished release notes with sections for highlights, compatibility, fixes, known issues, and acknowledgements. Avoid marketing hype and preserve the exact deprecation timeline.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} +{"prompt":"README scratchpad from tools/packet-lens:\n\nPurpose: inspect our framed TCP protocol without running Wireshark dissectors.\nInstall: cargo install packet-lens\nInputs: pcap file, stdin hex, or live interface with privileges\nCommands: decode, filter, stats\nUseful flags: --schema, --direction, --json, --strict\nExit 0 decoded all frames; 2 malformed input; 3 schema mismatch; 4 capture permission\nSchemas live in ~/.config/packet-lens/schemas and can include another file.\nExamples in fixtures/demo-v3.pcap and fixtures/bad-checksum.hex.\nWarning: --json may contain customer payloads.\n\nWrite a complete README from this material. Include quick start, command examples, schema lookup behavior, exit codes, security warning, troubleshooting, and a short development section based on Cargo.toml targets.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"tiny config thing pls","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"vague-eval","lang":"en"} +{"prompt":"clean up that module","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"something's off in prod","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"take a look at the auth code","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"thoughts on this implementation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"write up what we changed","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"need words for the release","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Plan the ROS 2 migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Outline our feature-store architecture","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Design crash-safe OTA updates","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Sequence the CockroachDB cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Our collaborative CAD editor needs offline branches, peer-to-peer exchange on factory networks, and eventual synchronization through the cloud. Write an architecture proposal covering operation representation, merge semantics, tombstone retention, large binary assets, identity, encryption, partial replication, and recovery from divergent histories. Compare CRDT and operation-log approaches, then recommend staged validation work without implementing the editor.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} {"prompt":"Develop a roadmap for moving fraud-model inference from synchronous Python workers to NVIDIA Triton while preserving fallback behavior.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Propose how the multiplayer server should divide ownership of physics, inventory, chat, and persistence across shards.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"core","lang":"en"} -{"prompt":"Lay out a recovery strategy for our self-hosted GitLab installation, including RPO, RTO, restore drills, and object-storage loss.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Frame an RFC for introducing regional read replicas to the patient-directory service under data-residency constraints.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"core","lang":"en"} -{"prompt":"Chart the milestones for replacing custom iOS deep-link routing with NavigationStack while supporting old notification payloads.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"请设计一个从 Airflow 迁移到 Dagster 的方案，包含资产建模、回填、并行运行、验证和回滚，不要写代码。","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"zh-CN"} -{"prompt":"Specify an observability model for GPU training jobs spanning Kubernetes scheduling, data loading, checkpointing, and distributed collectives.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"en"} +{"prompt":"Propose how the multiplayer server should divide ownership of physics, inventory, chat, and persistence across shards.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Lay out a recovery strategy for our self-hosted GitLab installation, including RPO, RTO, restore drills, and object-storage loss.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Frame an RFC for introducing regional read replicas to the patient-directory service under data-residency constraints.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Chart the milestones for replacing custom iOS deep-link routing with NavigationStack while supporting old notification payloads.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"请设计一个从 Airflow 迁移到 Dagster 的方案，包含资产建模、回填、并行运行、验证和回滚，不要写代码。","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"zh"} +{"prompt":"Specify an observability model for GPU training jobs spanning Kubernetes scheduling, data loading, checkpointing, and distributed collectives.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Prepare a phased strategy for rotating every device certificate in our industrial gateway fleet without physical access.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Recommend a package-boundary design for sharing validation logic between the Kotlin server and Android client.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Implement roaring bitmap intersections","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Add the webhook outbox","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Build a TOML linter","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.56,"slice":"core","lang":"en"} -{"prompt":"Persist resumable import checkpoints","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} +{"prompt":"Recommend a package-boundary design for sharing validation logic between the Kotlin server and Android client.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement roaring bitmap intersections","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add the webhook outbox","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Build a TOML linter","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Persist resumable import checkpoints","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Implement a Go service that accepts signed build attestations, validates their Fulcio certificate chain and Rekor inclusion proof, stores normalized provenance, and exposes lookup by artifact digest. Include replay protection, bounded request bodies, structured failure codes, and integration tests with locally generated fixtures.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Teach the Elixir notification worker to collapse duplicate alerts within a tenant-specific five-minute window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.56,"slice":"core","lang":"en"} -{"prompt":"Create a ClickHouse materialized view for hourly API latency percentiles, split by region and route template.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.51,"slice":"core","lang":"en"} +{"prompt":"Teach the Elixir notification worker to collapse duplicate alerts within a tenant-specific five-minute window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Create a ClickHouse materialized view for hourly API latency percentiles, split by region and route template.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Extend the Zig firmware flasher to verify erased pages before programming and resume after a USB disconnect.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Introduce per-organization quotas to the Python vector-indexing queue using the existing weighted scheduler.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Write the Swift actor that serializes HealthKit export batches and retries only transient HKError cases.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Support conditional writes in the DynamoDB repository with an explicit version-conflict domain error.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"core","lang":"en"} -{"prompt":"Ajoute le décodage des réponses CBOR au client Rust, avec limites de profondeur et tests de données malformées.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"fr"} -{"prompt":"Implement a kubectl plugin that lists pods by projected monthly cost and can emit CSV or JSON.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Add optimistic concurrency to the Java shipment repository using the existing revision column.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.48,"slice":"core","lang":"en"} -{"prompt":"Build the latency heatmap","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.48,"slice":"core","lang":"en"} -{"prompt":"Animate card-stack dismissal","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Create the watchOS complication","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.56,"slice":"core","lang":"en"} -{"prompt":"Style the consent banner","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.31,"slice":"core","lang":"en"} +{"prompt":"Introduce per-organization quotas to the Python vector-indexing queue using the existing weighted scheduler.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Write the Swift actor that serializes HealthKit export batches and retries only transient HKError cases.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Support conditional writes in the DynamoDB repository with an explicit version-conflict domain error.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Ajoute le décodage des réponses CBOR au client Rust, avec limites de profondeur et tests de données malformées.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"fr"} +{"prompt":"Implement a kubectl plugin that lists pods by projected monthly cost and can emit CSV or JSON.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add optimistic concurrency to the Java shipment repository using the existing revision column.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Build the latency heatmap","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Animate card-stack dismissal","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Create the watchOS complication","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Style the consent banner","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Build a SvelteKit dependency graph explorer with pan and zoom, collapsible package groups, edge highlighting, accessible keyboard traversal, and a details drawer. It should handle several thousand nodes using the existing canvas renderer while keeping controls and selection state represented in the DOM for assistive technology.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Implement the SwiftUI sleep-trend screen with weekly charts, goal bands, annotations, and empty states for missing HealthKit permissions.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Give the Blender add-on panel a searchable material list, thumbnail grid, and clear active-item treatment.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Turn the bare React Native scanner screen into a guided flow with framing overlay, torch control, and haptic success state.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Design the CSS and markup for a print-friendly laboratory report that paginates tables without splitting result rows.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Render live MIDI velocity as responsive bars in the Electron mixer, with reduced-motion support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} -{"prompt":"Add a compact split-view layout to the iPad document browser with draggable column sizing.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"この Jetpack Compose の天気画面に、時間ごとの予報カルーセルと雨量グラフを追加して。","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"ja"} -{"prompt":"Build a terminal-style command history panel for the web IDE, including filtering, copy actions, and status icons.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} -{"prompt":"Create Unreal UMG widgets for the squad lobby, ready states, voice indicators, and host controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Bump grpc-go to 1.74.2","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.11,"slice":"core","lang":"en"} -{"prompt":"Enable use_native_picker","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Fix the README heading typo","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"core","lang":"en"} -{"prompt":"Remove the extra divider","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"core","lang":"en"} -{"prompt":"Change the retention default in config/defaults.toml from 14 days to the approved 21 days.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.13,"slice":"core","lang":"en"} -{"prompt":"Point the benchmark workflow at ubuntu-24.04-arm instead of the retired runner label.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.12,"slice":"core","lang":"en"} -{"prompt":"Set aria-live to polite on the upload status element; assertive is interrupting screen readers.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.15,"slice":"core","lang":"en"} -{"prompt":"Correct the mask in adc_config.h from 0x0F00 to 0xF000; the field occupies bits 12–15.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"core","lang":"en"} -{"prompt":"Replace staging.example.org with preview.example.org in the Playwright base URL.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} +{"prompt":"Implement the SwiftUI sleep-trend screen with weekly charts, goal bands, annotations, and empty states for missing HealthKit permissions.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Give the Blender add-on panel a searchable material list, thumbnail grid, and clear active-item treatment.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Turn the bare React Native scanner screen into a guided flow with framing overlay, torch control, and haptic success state.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Design the CSS and markup for a print-friendly laboratory report that paginates tables without splitting result rows.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Render live MIDI velocity as responsive bars in the Electron mixer, with reduced-motion support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add a compact split-view layout to the iPad document browser with draggable column sizing.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"この Jetpack Compose の天気画面に、時間ごとの予報カルーセルと雨量グラフを追加して。","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"ja"} +{"prompt":"Build a terminal-style command history panel for the web IDE, including filtering, copy actions, and status icons.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Create Unreal UMG widgets for the squad lobby, ready states, voice indicators, and host controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Bump grpc-go to 1.74.2","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Enable use_native_picker","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Fix the README heading typo","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Remove the extra divider","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Change the retention default in config/defaults.toml from 14 days to the approved 21 days.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Point the benchmark workflow at ubuntu-24.04-arm instead of the retired runner label.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Set aria-live to polite on the upload status element; assertive is interrupting screen readers.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Correct the mask in adc_config.h from 0x0F00 to 0xF000; the field occupies bits 12–15.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Replace staging.example.org with preview.example.org in the Playwright base URL.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Increase max_open_files to 4096 in the Loki production values.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Use Locale.ROOT for the known case-folding call in HeaderNames.java.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.16,"slice":"core","lang":"en"} -{"prompt":"Update the App Store copyright year to 2026.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Ändere den falschen Port in docker-compose.dev.yml von 5433 auf 5432.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"core","lang":"de"} -{"prompt":"Drop the duplicate import from packages/chart/src/scale.ts.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"core","lang":"en"} -{"prompt":"Split the telemetry package","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Rename BlobRef repository-wide","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.48,"slice":"core","lang":"en"} -{"prompt":"Extract a clock abstraction","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Deduplicate our protobuf visitors","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"The inference gateway has separate but nearly identical batching loops for CUDA, ROCm, and CPU. Pull queueing, deadline calculation, cancellation, and metrics into a backend-neutral coordinator while retaining device-specific execution adapters. Preserve batch composition, timing behavior, exported types, and every existing benchmark scenario.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Move the business-day calculations out of InvoiceViewModel into the shared calendar domain package without altering displayed dates.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Replace the inheritance tree for game status effects with composable modifiers, keeping serialization and gameplay behavior compatible.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Consolidate the four GitHub Actions release workflows around one reusable workflow with equivalent triggers and permissions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Separate CSV tokenization, type inference, and row validation in ingest/csv_reader.py without changing accepted files.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Untangle BluetoothScanner from the Android Activity lifecycle by injecting the required platform callbacks; behavior must remain the same.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} +{"prompt":"Use Locale.ROOT for the known case-folding call in HeaderNames.java.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Update the App Store copyright year to 2026.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Ändere den falschen Port in docker-compose.dev.yml von 5433 auf 5432.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"de"} +{"prompt":"Drop the duplicate import from packages/chart/src/scale.ts.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Split the telemetry package","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} +{"prompt":"Rename BlobRef repository-wide","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Extract a clock abstraction","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Deduplicate our protobuf visitors","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"The inference gateway has separate but nearly identical batching loops for CUDA, ROCm, and CPU. Pull queueing, deadline calculation, cancellation, and metrics into a backend-neutral coordinator while retaining device-specific execution adapters. Preserve batch composition, timing behavior, exported types, and every existing benchmark scenario.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Move the business-day calculations out of InvoiceViewModel into the shared calendar domain package without altering displayed dates.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Replace the inheritance tree for game status effects with composable modifiers, keeping serialization and gameplay behavior compatible.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Consolidate the four GitHub Actions release workflows around one reusable workflow with equivalent triggers and permissions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Separate CSV tokenization, type inference, and row validation in ingest/csv_reader.py without changing accepted files.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Untangle BluetoothScanner from the Android Activity lifecycle by injecting the required platform callbacks; behavior must remain the same.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Restructure the Terraform network module so route tables are defined per topology rather than copied per environment, preserving plans.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Separa el procesamiento de comandos del transporte WebSocket sin cambiar mensajes, códigos de error ni orden de eventos.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"es"} -{"prompt":"Flatten the nested Rust error enums behind one internal context type while leaving public variants and Display output unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Move common geometry math from the editor tools into engine/math, preserving floating-point results and serialization.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Why do checkpoints vanish?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Investigate the purple frames","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Trace this allocator crash","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Find the duplicate notifications","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} +{"prompt":"Separa el procesamiento de comandos del transporte WebSocket sin cambiar mensajes, códigos de error ni orden de eventos.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"es"} +{"prompt":"Flatten the nested Rust error enums behind one internal context type while leaving public variants and Display output unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Move common geometry math from the editor tools into engine/math, preserving floating-point results and serialization.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Why do checkpoints vanish?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate the purple frames","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Trace this allocator crash","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find the duplicate notifications","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Our distributed PyTorch job completes forward and backward passes but hangs before the second optimizer step on exactly eight H100 nodes. Four nodes work, NCCL debug output stops after an all-reduce, and removing gradient accumulation hides the problem. Diagnose the collective mismatch or scheduling issue and build a minimal reproducer from the training loop.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Determine why the macOS network extension loses DNS routes after waking from sleep even though the tunnel remains connected.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"Track down why Kafka consumer lag oscillates every ten minutes after adding cooperative rebalancing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Work out why SQLite reports database disk image is malformed only after importing a large encrypted archive on Android.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"en"} +{"prompt":"Determine why the macOS network extension loses DNS routes after waking from sleep even though the tunnel remains connected.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Track down why Kafka consumer lag oscillates every ten minutes after adding cooperative rebalancing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Work out why SQLite reports database disk image is malformed only after importing a large encrypted archive on Android.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Diagnose the sporadic NaNs entering our Kalman filter when the drone transitions from GPS to optical flow.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Explain and locate the source of the 30-second pause before systemd stops our Rust daemon.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Figure out why Safari submits the checkout form twice when Face ID autofills the card number.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Identify what makes the compiler emit invalid DWARF only for generic async closures.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"Descubra por que o ESP32 reinicia quando BLE advertising e leitura do sensor I2C acontecem juntos.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"pt-BR"} -{"prompt":"Debug the missing audio channels in exported DaVinci Resolve timeline XML.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} +{"prompt":"Explain and locate the source of the 30-second pause before systemd stops our Rust daemon.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Figure out why Safari submits the checkout form twice when Face ID autofills the card number.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Identify what makes the compiler emit invalid DWARF only for generic async closures.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Descubra por que o ESP32 reinicia quando BLE advertising e leitura do sensor I2C acontecem juntos.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"pt"} +{"prompt":"Debug the missing audio channels in exported DaVinci Resolve timeline XML.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Review the Wasm sandbox","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Explain this query planner","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Audit the certificate verifier","purpose":"review","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Assess the retry semantics","purpose":"review","secondary":null,"mixed":false,"difficulty":0.47,"slice":"core","lang":"en"} -{"prompt":"Review src/storage/compactor.rs for data-loss risks around segment replacement, fsync ordering, and crash recovery. Trace the relevant invariants through its manifest code and tests, and report concrete findings only; do not edit the implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.81,"slice":"core","lang":"en"} -{"prompt":"Walk through how the current iOS app resolves universal links when the user is signed out.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"Compare our two candidate vector quantization implementations for memory use, recall implications, and SIMD portability.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Check whether the Helm chart's RBAC rules obey least privilege for leader election and secret reloads.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Tell me what assumptions the current terrain chunk serializer makes about endianness and schema versions.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Evaluate the PR's new lock-free slab allocator for ABA hazards and unsafe lifetime assumptions.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Inspect the dbt models for accidental fan-out joins that could inflate monthly recurring revenue.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"解释一下现有的 Raft snapshot 安装流程，包括锁的顺序和失败恢复，不要修改代码。","purpose":"review","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"zh-CN"} -{"prompt":"Read the Swift concurrency changes and judge whether Sendable annotations are justified rather than merely suppressing warnings.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Document the model registry","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.36,"slice":"core","lang":"en"} -{"prompt":"Draft the incident summary","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"Write upgrade notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.28,"slice":"core","lang":"en"} -{"prompt":"Summarize the compiler rewrite","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Create a contributor guide for the emulator core covering toolchain setup, ROM fixtures, deterministic timing tests, trace comparison, fuzz targets, and the policy for copyrighted test data. Base commands on the repository's Makefile and explain which suites require physical hardware.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} +{"prompt":"Explain this query planner","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Audit the certificate verifier","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Assess the retry semantics","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Review src/storage/compactor.rs for data-loss risks around segment replacement, fsync ordering, and crash recovery. Trace the relevant invariants through its manifest code and tests, and report concrete findings only; do not edit the implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Walk through how the current iOS app resolves universal links when the user is signed out.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Compare our two candidate vector quantization implementations for memory use, recall implications, and SIMD portability.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Check whether the Helm chart's RBAC rules obey least privilege for leader election and secret reloads.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Tell me what assumptions the current terrain chunk serializer makes about endianness and schema versions.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Evaluate the PR's new lock-free slab allocator for ABA hazards and unsafe lifetime assumptions.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Inspect the dbt models for accidental fan-out joins that could inflate monthly recurring revenue.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"解释一下现有的 Raft snapshot 安装流程，包括锁的顺序和失败恢复，不要修改代码。","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"Read the Swift concurrency changes and judge whether Sendable annotations are justified rather than merely suppressing warnings.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Document the model registry","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Draft the incident summary","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Write upgrade notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Summarize the compiler rewrite","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Create a contributor guide for the emulator core covering toolchain setup, ROM fixtures, deterministic timing tests, trace comparison, fuzz targets, and the policy for copyrighted test data. Base commands on the repository's Makefile and explain which suites require physical hardware.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Prepare a postmortem from incidents/2026-07-cache-stampede.md with impact, timeline, contributing factors, corrective actions, and lessons learned.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Turn the protobuf comments in telemetry/v4 into a public API reference with field semantics and compatibility warnings.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.47,"slice":"core","lang":"en"} -{"prompt":"Compose a PR description for the Metal renderer optimization, incorporating benchmark tables and visual-regression results.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} +{"prompt":"Turn the protobuf comments in telemetry/v4 into a public API reference with field semantics and compatibility warnings.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Compose a PR description for the Metal renderer optimization, incorporating benchmark tables and visual-regression results.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Update the operations handbook with instructions for draining a Temporal worker during regional maintenance.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Produce an ADR explaining why the project selected DuckDB over SQLite for local analytical queries.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"Rédige les notes de version 3.2 à partir du changelog, avec une section dédiée aux changements incompatibles.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"core","lang":"fr"} -{"prompt":"Add useful doc comments to the exported Go tracing interfaces, including ownership and concurrency expectations.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding page explaining how feature flags move from proposal to permanent removal in this repository.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"Specify the work needed for a new GraphQL subscriptions service, but stop at architecture and delivery phases.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.76,"slice":"boundary","lang":"en"} -{"prompt":"Map out how to implement the redesigned editor canvas; I need milestones and technical decisions, not UI code.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"Draft the migration approach for renaming every public metric without breaking dashboards or alerts.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Work through a design for the server-side document renderer before anyone starts coding it.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"新しい課金 API の実装計画を作って。コードはまだ変更せず、移行段階と互換性を中心にして。","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","lang":"ja"} -{"prompt":"Implement the endpoints exactly as specified in docs/device-enrollment-api.md.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"Convert the README's Python cache example into the actual reusable package under src/cache.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"boundary","lang":"en"} -{"prompt":"Apply ADR-27 by introducing separate command and query database pools in the service.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"Build the server implementation behind the already-designed /v3/search contract.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Make the CLI behavior described in the usage guide real, including stdin support and exit status 12.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"Increase the avatar size to 36px in the member list.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Color the selected map marker with the existing accent token.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.16,"slice":"boundary","lang":"en"} -{"prompt":"Add a two-line clamp to notification previews and show an ellipsis.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"Move the search icon inside the rounded input while preserving all behavior.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"Give the paused timer a striped visual treatment so state isn't communicated by color alone.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.25,"slice":"boundary","lang":"en"} -{"prompt":"Rename tmp to buffer in decodeFrame.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"boundary","lang":"en"} -{"prompt":"Update the misleading API comment: timeout is milliseconds, not seconds.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"boundary","lang":"en"} -{"prompt":"Set the known-bad animation duration from 3000ms to 300ms.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"boundary","lang":"en"} -{"prompt":"Change “Syncronizing” to “Synchronizing” in SyncBanner.swift.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"en"} -{"prompt":"Fix the established modulo error: shardIndex must use shardCount, not shardCount - 1.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.16,"slice":"boundary","lang":"en"} -{"prompt":"Rename PredictionResult to InferenceResult across all packages without changing JSON field names or behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Extract the inline SQL from seven handlers into named repository queries while preserving generated statements.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.61,"slice":"boundary","lang":"en"} -{"prompt":"Consolidate the duplicate API documentation generators behind one renderer; generated Markdown must remain byte-identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Split DeviceManager into discovery, connection, and persistence collaborators with no observable changes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Replace internal references to masterClock with timelineClock repository-wide while keeping serialized project files compatible.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"Why is the documented 429 response arriving as a 500 in production? Trace the discrepancy.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"Explain why our generated API example crashes the Rust client and identify what's wrong.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.61,"slice":"boundary","lang":"en"} -{"prompt":"The docs say refresh tokens are single-use, but replays sometimes succeed. Investigate the implementation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"What's causing the README's installation command to produce an unusable binary on Alpine?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Find why the OpenAPI-generated pagination client skips the second page despite correct server links.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"Read the current endpoint code and explain its actual error contract; don't create documentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.44,"slice":"boundary","lang":"en"} -{"prompt":"Tell me whether docs/auth.md accurately reflects the token validator's behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.43,"slice":"boundary","lang":"en"} -{"prompt":"Evaluate the proposed API guide for security-sensitive omissions without editing its prose.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} -{"prompt":"Walk me through what this undocumented /internal/replay route currently does.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.48,"slice":"boundary","lang":"en"} -{"prompt":"Compare the REST contract described in README.md with the handlers and list every mismatch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Document the existing batch API, including limits, partial failures, and idempotency behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"boundary","lang":"en"} -{"prompt":"Write a developer guide for the webhook signature verifier based on its current implementation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"boundary","lang":"en"} -{"prompt":"Produce an API reference for the Rust crate's public server types; no implementation changes.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.47,"slice":"boundary","lang":"en"} -{"prompt":"Turn the route handlers into a prose walkthrough for new backend engineers.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Escribe una guía de migración para los clientes de /v1/jobs a /v2/jobs, con ejemplos de requests y errores.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.44,"slice":"boundary","lang":"es"} -{"prompt":"Plan and implement regional failover for the session store, including consistency decisions, rollout, metrics, and integration tests.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.92,"slice":"mixed","lang":"en"} -{"prompt":"Design and build the Android tablet layout for dispatch operators, covering navigation, adaptive panes, and accessibility.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.78,"slice":"mixed","lang":"en"} -{"prompt":"Architect the migration from REST polling to WebTransport and implement a guarded prototype behind realtime_transport_v2.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.88,"slice":"mixed","lang":"en"} -{"prompt":"Implement the certificate-enrollment service and write its public API documentation with curl examples.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Build the Parquet compactor, then review the existing lakehouse manifests for files it cannot safely process.","purpose":"backendImpl","secondary":"review","mixed":true,"difficulty":0.77,"slice":"mixed","lang":"en"} +{"prompt":"Produce an ADR explaining why the project selected DuckDB over SQLite for local analytical queries.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Rédige les notes de version 3.2 à partir du changelog, avec une section dédiée aux changements incompatibles.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"fr"} +{"prompt":"Add useful doc comments to the exported Go tracing interfaces, including ownership and concurrency expectations.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding page explaining how feature flags move from proposal to permanent removal in this repository.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Specify the work needed for a new GraphQL subscriptions service, but stop at architecture and delivery phases.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Map out how to implement the redesigned editor canvas; I need milestones and technical decisions, not UI code.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Draft the migration approach for renaming every public metric without breaking dashboards or alerts.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Work through a design for the server-side document renderer before anyone starts coding it.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"新しい課金 API の実装計画を作って。コードはまだ変更せず、移行段階と互換性を中心にして。","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"ja"} +{"prompt":"Implement the endpoints exactly as specified in docs/device-enrollment-api.md.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Convert the README's Python cache example into the actual reusable package under src/cache.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Apply ADR-27 by introducing separate command and query database pools in the service.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Build the server implementation behind the already-designed /v3/search contract.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Make the CLI behavior described in the usage guide real, including stdin support and exit status 12.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Increase the avatar size to 36px in the member list.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Color the selected map marker with the existing accent token.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Add a two-line clamp to notification previews and show an ellipsis.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Move the search icon inside the rounded input while preserving all behavior.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Give the paused timer a striped visual treatment so state isn't communicated by color alone.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Rename tmp to buffer in decodeFrame.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Update the misleading API comment: timeout is milliseconds, not seconds.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Set the known-bad animation duration from 3000ms to 300ms.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Change “Syncronizing” to “Synchronizing” in SyncBanner.swift.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fix the established modulo error: shardIndex must use shardCount, not shardCount - 1.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename PredictionResult to InferenceResult across all packages without changing JSON field names or behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Extract the inline SQL from seven handlers into named repository queries while preserving generated statements.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Consolidate the duplicate API documentation generators behind one renderer; generated Markdown must remain byte-identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Split DeviceManager into discovery, connection, and persistence collaborators with no observable changes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Replace internal references to masterClock with timelineClock repository-wide while keeping serialized project files compatible.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Why is the documented 429 response arriving as a 500 in production? Trace the discrepancy.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Explain why our generated API example crashes the Rust client and identify what's wrong.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"The docs say refresh tokens are single-use, but replays sometimes succeed. Investigate the implementation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"What's causing the README's installation command to produce an unusable binary on Alpine?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Find why the OpenAPI-generated pagination client skips the second page despite correct server links.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Read the current endpoint code and explain its actual error contract; don't create documentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Tell me whether docs/auth.md accurately reflects the token validator's behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Evaluate the proposed API guide for security-sensitive omissions without editing its prose.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Walk me through what this undocumented /internal/replay route currently does.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Compare the REST contract described in README.md with the handlers and list every mismatch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Document the existing batch API, including limits, partial failures, and idempotency behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Write a developer guide for the webhook signature verifier based on its current implementation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Produce an API reference for the Rust crate's public server types; no implementation changes.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Turn the route handlers into a prose walkthrough for new backend engineers.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Escribe una guía de migración para los clientes de /v1/jobs a /v2/jobs, con ejemplos de requests y errores.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"es"} +{"prompt":"Plan and implement regional failover for the session store, including consistency decisions, rollout, metrics, and integration tests.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Design and build the Android tablet layout for dispatch operators, covering navigation, adaptive panes, and accessibility.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Architect the migration from REST polling to WebTransport and implement a guarded prototype behind realtime_transport_v2.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Implement the certificate-enrollment service and write its public API documentation with curl examples.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Build the Parquet compactor, then review the existing lakehouse manifests for files it cannot safely process.","purpose":"backendImpl","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Add SAML metadata refresh and prepare an operator runbook for certificate rollover failures.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Implement the Vue workflow canvas and document its keyboard shortcuts in the user guide.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.67,"slice":"mixed","lang":"en"} -{"prompt":"Build the macOS permissions screen, then audit its completed accessibility hierarchy and focus behavior.","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} +{"prompt":"Implement the Vue workflow canvas and document its keyboard shortcuts in the user guide.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Build the macOS permissions screen, then audit its completed accessibility hierarchy and focus behavior.","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Bump the schema version to 18 and add a release-note entry about the already-supported field.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.2,"slice":"mixed","lang":"en"} -{"prompt":"Correct the feature flag key in staging and update the deployment checklist line that names it.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.17,"slice":"mixed","lang":"en"} -{"prompt":"Consolidate the three serializers without output changes and document the new extension point for plugin authors.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.67,"slice":"mixed","lang":"en"} -{"prompt":"Rename the public Swift protocol across modules, preserving source compatibility, then inspect the generated interface for leaks.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Diagnose the unexplained index corruption, repair the defect, and write a concise incident report from the evidence.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.89,"slice":"mixed","lang":"en"} -{"prompt":"Find why the React timeline janks during zoom, then simplify the rendering pipeline without changing its visuals.","purpose":"debugging","secondary":"refactor","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Audit the current payment API implementation and turn the findings into a formal security review document.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Assess the two caching proposals, choose the safer one, and implement it in the Go gateway.","purpose":"review","secondary":"backendImpl","mixed":true,"difficulty":0.73,"slice":"mixed","lang":"en"} -{"prompt":"Explain the existing editor state model, then create an onboarding document with diagrams and terminology.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.57,"slice":"mixed","lang":"en"} -{"prompt":"Write the deprecation guide and add server warnings for requests still using the legacy query parameter.","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.55,"slice":"mixed","lang":"en"} +{"prompt":"Correct the feature flag key in staging and update the deployment checklist line that names it.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.2,"slice":"mixed","lang":"en"} +{"prompt":"Consolidate the three serializers without output changes and document the new extension point for plugin authors.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Rename the public Swift protocol across modules, preserving source compatibility, then inspect the generated interface for leaks.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Diagnose the unexplained index corruption, repair the defect, and write a concise incident report from the evidence.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Find why the React timeline janks during zoom, then simplify the rendering pipeline without changing its visuals.","purpose":"debugging","secondary":"refactor","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Audit the current payment API implementation and turn the findings into a formal security review document.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the two caching proposals, choose the safer one, and implement it in the Go gateway.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Explain the existing editor state model, then create an onboarding document with diagrams and terminology.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Write the deprecation guide and add server warnings for requests still using the legacy query parameter.","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} {"prompt":"Prepare the UI release notes and implement the missing dark-mode state shown in the approved screenshots.","purpose":"writing","secondary":"frontendImpl","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} -{"prompt":"Document the plugin loader and reorganize its internal discovery helpers to match the documented phases without behavior changes.","purpose":"writing","secondary":"refactor","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"Architecture notes from the ML platform sync:\n\nCurrent path:\ntraining job -> writes checkpoint to regional S3 -> emits Kafka event -> registry worker extracts metadata -> PostgreSQL row becomes visible\n\nProblems:\n- duplicate events create conflicting versions\n- a 40 GB checkpoint may take 18 minutes to copy across regions\n- regulated projects cannot leave their home region\n- UI assumes model versions are sequential integers\n- serving needs an immutable digest before deployment\n\nProposed ideas: content-addressed manifests, per-region registries, global metadata catalog, asynchronous replication, signed promotion records.\n\nCreate a target architecture and staged migration plan. Address identity, deduplication, residency, replication states, backward compatibility for version numbers, failure recovery, observability, and rollback. Call out decisions requiring experiments; do not implement anything yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"pasted-context","lang":"en"} -{"prompt":"Field notes for replacing our PLC update process:\n\nFleet: 46,000 controllers, three hardware revisions, intermittent LTE, no secure element on rev A.\nCurrent updater: downloads a full 28 MB image over HTTP, validates CRC32, writes the inactive flash bank, reboots immediately.\nRequirements:\n- signed firmware and downgrade prevention\n- staged rollout by site and hardware revision\n- delta updates when safe\n- power-loss recovery\n- emergency rollback without technician visits\n- rev A must remain supported for two years\n- factory network allows only outbound HTTPS\n\nSeveral teams suggested TUF, Uptane, or a custom signed manifest. Produce a decision record and rollout roadmap comparing those approaches. Include bootloader implications, key hierarchy, recovery states, telemetry, validation gates, and rev A limitations. No firmware changes in this phase.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"pasted-context","lang":"en"} -{"prompt":"Story DATA-448 copied from Linear:\n\nWe receive newline-delimited JSON files containing up to 80 million click events. Implement `lake ingest clicks` with these guarantees:\n- stream input from local disk or stdin; never load the full file\n- validate event_id, occurred_at, tenant_id, url, and optional campaign_id\n- deduplicate within the file using bounded memory\n- partition Parquet output by tenant and UTC date\n- write atomically through a staging directory\n- emit a JSON summary with accepted, rejected, duplicate, and output file counts\n- invalid rows go to a companion NDJSON file with line number and reason\n- Ctrl-C leaves no visible partial partition\n\nThe repository already has Arrow builders and an external-sort helper. Implement the command and end-to-end tests using generated fixtures.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Protocol task from NET-723:\n\nFrame format:\nmagic[2] = 0xB7 0x51\nversion[1]\nflags[1]\nstream_id[4] little-endian\npayload_length[3] little-endian\nheader_crc16[2]\npayload[n]\npayload_crc32c[4]\n\nConstraints:\n- input arrives in arbitrary chunks\n- maximum payload is negotiated, hard ceiling 16 MiB\n- unknown versions are skipped only when length is trustworthy\n- corrupted headers resynchronize on magic without quadratic scanning\n- payload can be exposed as borrowed slices when contiguous\n- decoder reports byte offsets for every error\n\nImplement the incremental parser in crates/wire/src/frame_decoder.rs. Add property tests for chunk boundaries, corruption recovery, oversized frames, and false magic bytes inside payloads.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"UX ticket pasted from Notion:\n\nFeature: compare experiment runs\nPrimary user: ML engineer deciding which checkpoint to promote\nDesktop layout:\n- left rail: searchable run list with multi-select, max five\n- main: metric chart with synchronized crosshair\n- lower panel: parameter diff table grouped by category\n- top bar: dataset selector, smoothing control, share link\nResponsive behavior:\n- under 900 px, run list becomes a sheet\n- parameter table becomes stacked cards under 600 px\nStates: no project, no runs, one selected, 2–5 selected, incompatible datasets, loading, stream disconnected\nAccessibility: chart has tabular alternative; colors also use dash patterns\n\nBuild the React route at apps/lab/routes/CompareRuns.tsx using the existing chart primitives and design tokens. Add representative Storybook stories and interaction tests.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.74,"slice":"pasted-context","lang":"en"} -{"prompt":"Android design handoff:\n\nScreen: Warehouse pick route\nHeader: route number, completion ratio, overflow menu\nBody: vertically ordered stop cards; active stop expanded with item photos, bin locations, quantities, and scan CTA\nCompleted stops collapse and show a check icon\nException stop uses warning icon plus reason text\nBottom: sticky “Next stop” button; replaced by “Finish route” at 100%\n\nInteraction notes:\n- scanner may update quantities while the screen is visible\n- animate expansion but honor reduced motion\n- TalkBack traversal follows route order\n- landscape tablet shows stop list left and active details right\n- offline banner must not cover the header\n\nImplement this in Jetpack Compose using PickRouteViewModel. Include previews for active, complete, exception, offline, and tablet states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Game UI brief from the combat team:\n\nHUD element: elemental status wheel\nSlots: fire, frost, shock, poison, bleed, curse\nEach slot shows buildup 0–100%, flashes at threshold, then displays remaining duration.\nController navigation must allow inspecting a slot without moving character focus.\nAt 4K, wheel remains 180 logical pixels; at ultrawide it stays anchored near health.\nColor-blind modes replace hue-only distinctions with symbols and fill patterns.\nWhen more than three effects trigger simultaneously, prioritize shortest duration for labels.\nAnimations must stop when gameplay is paused.\n\nCreate the Unreal UMG widget, binding layer, animations, and visual test map. Gameplay status calculation already exists and is out of scope.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"pasted-context","lang":"en"} -{"prompt":"Maintenance ticket:\n\nDependabot PR bumped `com.squareup.okhttp3:okhttp` from 4.12.0 to 5.1.0.\nThe Android app is not ready for OkHttp 5 because our event-listener adapter uses removed APIs. The approved release train stays on the latest 4.x patch, 4.12.0.\n\nCurrent libs.versions.toml:\n[versions]\nokhttp = \"5.1.0\"\n\n[libraries]\nokhttp-core = { module = \"com.squareup.okhttp3:okhttp\", version.ref = \"okhttp\" }\nokhttp-logging = { module = \"com.squareup.okhttp3:logging-interceptor\", version.ref = \"okhttp\" }\n\nChange the version back to 4.12.0. Do not modify adapter code or other dependency versions; this is only correcting the accidental merge.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"pasted-context","lang":"en"} -{"prompt":"Known UI defect from QA:\n\nScreenshot baseline: settings-notifications-dark.png\nExpected separator: rgba token `var(--border-subtle)`\nActual CSS:\n.notification-row + .notification-row {\n border-top: 1px solid var(--text-muted);\n}\n\nDesign confirms this is a token typo, not a redesign. The muted text token produces a high-contrast line in dark mode; light mode happens to look acceptable.\n\nChange the border token to `var(--border-subtle)` in NotificationSettings.css and update the dark-mode screenshot snapshot if required. Leave spacing, border width, and all other colors unchanged.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"pasted-context","lang":"en"} -{"prompt":"Deployment failure:\n\nError: UPGRADE FAILED: cannot patch \"ledger-worker\" with kind Deployment: Deployment.apps \"ledger-worker\" is invalid: spec.template.spec.containers[0].resources.requests: Invalid value: \"1500m\": must be less than or equal to cpu limit of 1000m\n\nValues diff:\nworker:\n resources:\n requests:\n cpu: 1500m\n memory: 2Gi\n limits:\n cpu: 2000m\n memory: 2Gi\n\nRendered manifest still shows cpu limit 1000m because templates/worker.yaml reads `.Values.worker.resource.limits.cpu` with singular `resource`.\n\nThe chart schema and every values file use `resources`. Correct that one template path to `.Values.worker.resources.limits.cpu`. Do not change requested resources or production values.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.13,"slice":"pasted-context","lang":"en"} -{"prompt":"Cleanup notes from the Swift package:\n\nSources/SyncKit/CloudSyncEngine.swift handles scheduling, network reachability, upload/download orchestration, merge policy, progress publication, and persistence checkpoints.\nTests already cover all public behavior through SyncEngineProtocol.\nDesired internal pieces:\n- SyncScheduler\n- TransferCoordinator\n- ConflictResolver\n- CheckpointStore adapter\n\nConstraints:\n- keep SyncEngineProtocol unchanged\n- callbacks remain delivered on MainActor\n- preserve cancellation timing and progress ordering\n- no changes to stored checkpoint format\n- avoid exposing new public symbols\n\nRestructure CloudSyncEngine around these collaborators and move existing logic rather than rewriting algorithms. The public API, event sequence, persisted data, and tests should behave identically.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.73,"slice":"pasted-context","lang":"en"} -{"prompt":"Repository rename brief:\n\nCurrent term `DatasetRevision` appears in:\n- Python domain and API models\n- TypeScript SDK types\n- protobuf messages\n- BigQuery table descriptions\n- dashboard metric labels\n- CLI output snapshots\n\nNew term: `DatasetVersion`\n\nCompatibility rules:\n- protobuf field numbers and wire names remain unchanged\n- JSON continues accepting `revision_id` for two releases\n- CLI column header stays REVISION until the next major version\n- database tables are untouched\n- metrics keep old label names\n- generated clients expose deprecated aliases\n\nPerform the codebase-wide terminology restructuring while preserving behavior and external compatibility. Update internal tests to prefer the new names, and keep compatibility coverage for every old entry point.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Duplication report:\n\ncmd/export.go parses filters, creates a query, streams rows, writes progress\ncmd/archive.go parses the same filters, creates nearly the same query, streams rows, writes progress, then deletes\njobs/nightly_export.go builds those filters programmatically and copies the query loop\n\nBehavioral constraints:\n- CLI output and progress cadence cannot change\n- archive deletes only after a fully successful write\n- nightly jobs use a fake clock in tests\n- cancellation must close rows immediately\n- exported file ordering is stable and snapshot-tested\n\nExtract shared filter parsing and streaming infrastructure with narrow adapters for export, archive, and nightly jobs. Preserve SQL, ordering, cancellation, progress output, and transactional deletion semantics.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.71,"slice":"pasted-context","lang":"en"} -{"prompt":"Training log excerpt:\n\nstep=18340 loss=2.718 scale=8192 grad_norm=1.24 overflow=false\nstep=18341 loss=2.701 scale=8192 grad_norm=1.19 overflow=false\nstep=18342 loss=nan scale=8192 grad_norm=nan overflow=false\nrank=3 attention_logits min=-inf max=71.2\nrank=0 attention_logits min=-84.5 max=69.8\ncheckpoint resumed_from=step_18000 optimizer_loaded=true scheduler_loaded=true\n\nFacts:\n- failure occurs only with sequence length 32768\n- bfloat16 training is stable\n- fp16 fails on one of eight ranks after 200–600 steps\n- disabling FlashAttention eliminates it but doubles memory\n- input batches contain no NaNs\n\nInvestigate why overflow detection misses this failure and whether masking, FlashAttention, or distributed state divergence is responsible. Produce a minimal regression and fix the root cause.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.92,"slice":"pasted-context","lang":"en"} -{"prompt":"macOS crash report excerpt:\n\nException Type: EXC_BAD_ACCESS (SIGSEGV)\nThread 19 Crashed: com.example.preview.renderer\n0 libswiftCore.dylib swift_release + 32\n1 CanvasKit RenderSession.deinit + 148\n2 CanvasKit MetalPreview.stop() + 404\n3 CanvasKit closure #2 in MetalPreview.handleMemoryPressure() + 96\n\nThread 0:\nMetalPreviewView.updateNSView -> renderer.replaceDocument(newDocument)\n\nReproduction:\n1. Open a 600 MB project.\n2. Switch documents rapidly.\n3. Trigger simulated critical memory pressure.\n4. Crash occurs about one in six attempts.\n\nRenderSession is actor-isolated, but the CVDisplayLink callback captures an unmanaged pointer. Determine the ownership race, fix it without leaking display links, and add a stress test or deterministic harness.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.88,"slice":"pasted-context","lang":"en"} -{"prompt":"Gateway logs during the outage:\n\n12:03:14 upstream=inventory-3 status=503 retry=0 latency=2001ms\n12:03:16 upstream=inventory-3 status=503 retry=1 latency=2002ms\n12:03:18 upstream=inventory-8 status=200 retry=2 latency=84ms\n12:03:18 circuit=inventory state=open failures=5\n12:03:19 request rejected circuit_open\n12:03:49 circuit=inventory state=half_open probes=10\n12:03:49 upstream=inventory-3 status=503 probe=true\n12:03:49 circuit=inventory state=open failures=1\n\nOnly one inventory pod was unhealthy, but the gateway rejected roughly 70% of requests for eight minutes. Service discovery listed twelve endpoints. Inspect the load-balancer, retry, and circuit-breaker interaction to explain how a single pod poisoned the shared circuit. Implement the appropriate isolation and a regression test.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Code-review packet from SEC-391:\n\nNew files:\ninternal/plugins/loader.go\ninternal/plugins/manifest.go\ninternal/plugins/sandbox_linux.go\n\nPlugin flow:\n1. Read manifest from user-supplied archive.\n2. Extract to cache directory.\n3. Verify SHA-256 from registry response.\n4. Launch executable with JSON-RPC over stdio.\n5. Pass selected environment variables and workspace path.\n\nReviewer concerns:\n- archive traversal and symlinks\n- digest verification occurs after extraction\n- inherited file descriptors\n- environment allowlist defaults\n- cache replacement races\n- executable permissions\n\nReview the current branch for exploitable paths and sandbox escapes. Report severity, exact code path, attacker prerequisites, and recommended mitigation. Do not make changes; this is an assessment for the security gate.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Schema proposal excerpt:\n\nCREATE TABLE device_readings (\n tenant_id uuid NOT NULL,\n device_id uuid NOT NULL,\n observed_at timestamptz NOT NULL,\n metric_id smallint NOT NULL,\n value double precision,\n quality smallint NOT NULL,\n PRIMARY KEY (tenant_id, device_id, observed_at, metric_id)\n) PARTITION BY RANGE (observed_at);\n\nExpected volume: 4 billion rows/year.\nQueries:\n- latest 50 readings for one device\n- hourly aggregates for a tenant and metric\n- delete one tenant within 24 hours\n- retain raw data 90 days, aggregates 5 years\n\nReview this design for partition pruning, index size, hot partitions, deletion cost, null semantics, and TimescaleDB alternatives. No DDL changes requested; return findings and suggested experiments.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} +{"prompt":"Document the plugin loader and reorganize its internal discovery helpers to match the documented phases without behavior changes.","purpose":"writing","secondary":"refactor","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Architecture notes from the ML platform sync:\n\nCurrent path:\ntraining job -> writes checkpoint to regional S3 -> emits Kafka event -> registry worker extracts metadata -> PostgreSQL row becomes visible\n\nProblems:\n- duplicate events create conflicting versions\n- a 40 GB checkpoint may take 18 minutes to copy across regions\n- regulated projects cannot leave their home region\n- UI assumes model versions are sequential integers\n- serving needs an immutable digest before deployment\n\nProposed ideas: content-addressed manifests, per-region registries, global metadata catalog, asynchronous replication, signed promotion records.\n\nCreate a target architecture and staged migration plan. Address identity, deduplication, residency, replication states, backward compatibility for version numbers, failure recovery, observability, and rollback. Call out decisions requiring experiments; do not implement anything yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Field notes for replacing our PLC update process:\n\nFleet: 46,000 controllers, three hardware revisions, intermittent LTE, no secure element on rev A.\nCurrent updater: downloads a full 28 MB image over HTTP, validates CRC32, writes the inactive flash bank, reboots immediately.\nRequirements:\n- signed firmware and downgrade prevention\n- staged rollout by site and hardware revision\n- delta updates when safe\n- power-loss recovery\n- emergency rollback without technician visits\n- rev A must remain supported for two years\n- factory network allows only outbound HTTPS\n\nSeveral teams suggested TUF, Uptane, or a custom signed manifest. Produce a decision record and rollout roadmap comparing those approaches. Include bootloader implications, key hierarchy, recovery states, telemetry, validation gates, and rev A limitations. No firmware changes in this phase.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Story DATA-448 copied from Linear:\n\nWe receive newline-delimited JSON files containing up to 80 million click events. Implement `lake ingest clicks` with these guarantees:\n- stream input from local disk or stdin; never load the full file\n- validate event_id, occurred_at, tenant_id, url, and optional campaign_id\n- deduplicate within the file using bounded memory\n- partition Parquet output by tenant and UTC date\n- write atomically through a staging directory\n- emit a JSON summary with accepted, rejected, duplicate, and output file counts\n- invalid rows go to a companion NDJSON file with line number and reason\n- Ctrl-C leaves no visible partial partition\n\nThe repository already has Arrow builders and an external-sort helper. Implement the command and end-to-end tests using generated fixtures.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Protocol task from NET-723:\n\nFrame format:\nmagic[2] = 0xB7 0x51\nversion[1]\nflags[1]\nstream_id[4] little-endian\npayload_length[3] little-endian\nheader_crc16[2]\npayload[n]\npayload_crc32c[4]\n\nConstraints:\n- input arrives in arbitrary chunks\n- maximum payload is negotiated, hard ceiling 16 MiB\n- unknown versions are skipped only when length is trustworthy\n- corrupted headers resynchronize on magic without quadratic scanning\n- payload can be exposed as borrowed slices when contiguous\n- decoder reports byte offsets for every error\n\nImplement the incremental parser in crates/wire/src/frame_decoder.rs. Add property tests for chunk boundaries, corruption recovery, oversized frames, and false magic bytes inside payloads.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"UX ticket pasted from Notion:\n\nFeature: compare experiment runs\nPrimary user: ML engineer deciding which checkpoint to promote\nDesktop layout:\n- left rail: searchable run list with multi-select, max five\n- main: metric chart with synchronized crosshair\n- lower panel: parameter diff table grouped by category\n- top bar: dataset selector, smoothing control, share link\nResponsive behavior:\n- under 900 px, run list becomes a sheet\n- parameter table becomes stacked cards under 600 px\nStates: no project, no runs, one selected, 2–5 selected, incompatible datasets, loading, stream disconnected\nAccessibility: chart has tabular alternative; colors also use dash patterns\n\nBuild the React route at apps/lab/routes/CompareRuns.tsx using the existing chart primitives and design tokens. Add representative Storybook stories and interaction tests.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Android design handoff:\n\nScreen: Warehouse pick route\nHeader: route number, completion ratio, overflow menu\nBody: vertically ordered stop cards; active stop expanded with item photos, bin locations, quantities, and scan CTA\nCompleted stops collapse and show a check icon\nException stop uses warning icon plus reason text\nBottom: sticky “Next stop” button; replaced by “Finish route” at 100%\n\nInteraction notes:\n- scanner may update quantities while the screen is visible\n- animate expansion but honor reduced motion\n- TalkBack traversal follows route order\n- landscape tablet shows stop list left and active details right\n- offline banner must not cover the header\n\nImplement this in Jetpack Compose using PickRouteViewModel. Include previews for active, complete, exception, offline, and tablet states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Game UI brief from the combat team:\n\nHUD element: elemental status wheel\nSlots: fire, frost, shock, poison, bleed, curse\nEach slot shows buildup 0–100%, flashes at threshold, then displays remaining duration.\nController navigation must allow inspecting a slot without moving character focus.\nAt 4K, wheel remains 180 logical pixels; at ultrawide it stays anchored near health.\nColor-blind modes replace hue-only distinctions with symbols and fill patterns.\nWhen more than three effects trigger simultaneously, prioritize shortest duration for labels.\nAnimations must stop when gameplay is paused.\n\nCreate the Unreal UMG widget, binding layer, animations, and visual test map. Gameplay status calculation already exists and is out of scope.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Maintenance ticket:\n\nDependabot PR bumped `com.squareup.okhttp3:okhttp` from 4.12.0 to 5.1.0.\nThe Android app is not ready for OkHttp 5 because our event-listener adapter uses removed APIs. The approved release train stays on the latest 4.x patch, 4.12.0.\n\nCurrent libs.versions.toml:\n[versions]\nokhttp = \"5.1.0\"\n\n[libraries]\nokhttp-core = { module = \"com.squareup.okhttp3:okhttp\", version.ref = \"okhttp\" }\nokhttp-logging = { module = \"com.squareup.okhttp3:logging-interceptor\", version.ref = \"okhttp\" }\n\nChange the version back to 4.12.0. Do not modify adapter code or other dependency versions; this is only correcting the accidental merge.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Known UI defect from QA:\n\nScreenshot baseline: settings-notifications-dark.png\nExpected separator: rgba token `var(--border-subtle)`\nActual CSS:\n.notification-row + .notification-row {\n border-top: 1px solid var(--text-muted);\n}\n\nDesign confirms this is a token typo, not a redesign. The muted text token produces a high-contrast line in dark mode; light mode happens to look acceptable.\n\nChange the border token to `var(--border-subtle)` in NotificationSettings.css and update the dark-mode screenshot snapshot if required. Leave spacing, border width, and all other colors unchanged.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Deployment failure:\n\nError: UPGRADE FAILED: cannot patch \"ledger-worker\" with kind Deployment: Deployment.apps \"ledger-worker\" is invalid: spec.template.spec.containers[0].resources.requests: Invalid value: \"1500m\": must be less than or equal to cpu limit of 1000m\n\nValues diff:\nworker:\n resources:\n requests:\n cpu: 1500m\n memory: 2Gi\n limits:\n cpu: 2000m\n memory: 2Gi\n\nRendered manifest still shows cpu limit 1000m because templates/worker.yaml reads `.Values.worker.resource.limits.cpu` with singular `resource`.\n\nThe chart schema and every values file use `resources`. Correct that one template path to `.Values.worker.resources.limits.cpu`. Do not change requested resources or production values.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Cleanup notes from the Swift package:\n\nSources/SyncKit/CloudSyncEngine.swift handles scheduling, network reachability, upload/download orchestration, merge policy, progress publication, and persistence checkpoints.\nTests already cover all public behavior through SyncEngineProtocol.\nDesired internal pieces:\n- SyncScheduler\n- TransferCoordinator\n- ConflictResolver\n- CheckpointStore adapter\n\nConstraints:\n- keep SyncEngineProtocol unchanged\n- callbacks remain delivered on MainActor\n- preserve cancellation timing and progress ordering\n- no changes to stored checkpoint format\n- avoid exposing new public symbols\n\nRestructure CloudSyncEngine around these collaborators and move existing logic rather than rewriting algorithms. The public API, event sequence, persisted data, and tests should behave identically.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Repository rename brief:\n\nCurrent term `DatasetRevision` appears in:\n- Python domain and API models\n- TypeScript SDK types\n- protobuf messages\n- BigQuery table descriptions\n- dashboard metric labels\n- CLI output snapshots\n\nNew term: `DatasetVersion`\n\nCompatibility rules:\n- protobuf field numbers and wire names remain unchanged\n- JSON continues accepting `revision_id` for two releases\n- CLI column header stays REVISION until the next major version\n- database tables are untouched\n- metrics keep old label names\n- generated clients expose deprecated aliases\n\nPerform the codebase-wide terminology restructuring while preserving behavior and external compatibility. Update internal tests to prefer the new names, and keep compatibility coverage for every old entry point.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Duplication report:\n\ncmd/export.go parses filters, creates a query, streams rows, writes progress\ncmd/archive.go parses the same filters, creates nearly the same query, streams rows, writes progress, then deletes\njobs/nightly_export.go builds those filters programmatically and copies the query loop\n\nBehavioral constraints:\n- CLI output and progress cadence cannot change\n- archive deletes only after a fully successful write\n- nightly jobs use a fake clock in tests\n- cancellation must close rows immediately\n- exported file ordering is stable and snapshot-tested\n\nExtract shared filter parsing and streaming infrastructure with narrow adapters for export, archive, and nightly jobs. Preserve SQL, ordering, cancellation, progress output, and transactional deletion semantics.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Training log excerpt:\n\nstep=18340 loss=2.718 scale=8192 grad_norm=1.24 overflow=false\nstep=18341 loss=2.701 scale=8192 grad_norm=1.19 overflow=false\nstep=18342 loss=nan scale=8192 grad_norm=nan overflow=false\nrank=3 attention_logits min=-inf max=71.2\nrank=0 attention_logits min=-84.5 max=69.8\ncheckpoint resumed_from=step_18000 optimizer_loaded=true scheduler_loaded=true\n\nFacts:\n- failure occurs only with sequence length 32768\n- bfloat16 training is stable\n- fp16 fails on one of eight ranks after 200–600 steps\n- disabling FlashAttention eliminates it but doubles memory\n- input batches contain no NaNs\n\nInvestigate why overflow detection misses this failure and whether masking, FlashAttention, or distributed state divergence is responsible. Produce a minimal regression and fix the root cause.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"macOS crash report excerpt:\n\nException Type: EXC_BAD_ACCESS (SIGSEGV)\nThread 19 Crashed: com.example.preview.renderer\n0 libswiftCore.dylib swift_release + 32\n1 CanvasKit RenderSession.deinit + 148\n2 CanvasKit MetalPreview.stop() + 404\n3 CanvasKit closure #2 in MetalPreview.handleMemoryPressure() + 96\n\nThread 0:\nMetalPreviewView.updateNSView -> renderer.replaceDocument(newDocument)\n\nReproduction:\n1. Open a 600 MB project.\n2. Switch documents rapidly.\n3. Trigger simulated critical memory pressure.\n4. Crash occurs about one in six attempts.\n\nRenderSession is actor-isolated, but the CVDisplayLink callback captures an unmanaged pointer. Determine the ownership race, fix it without leaking display links, and add a stress test or deterministic harness.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Gateway logs during the outage:\n\n12:03:14 upstream=inventory-3 status=503 retry=0 latency=2001ms\n12:03:16 upstream=inventory-3 status=503 retry=1 latency=2002ms\n12:03:18 upstream=inventory-8 status=200 retry=2 latency=84ms\n12:03:18 circuit=inventory state=open failures=5\n12:03:19 request rejected circuit_open\n12:03:49 circuit=inventory state=half_open probes=10\n12:03:49 upstream=inventory-3 status=503 probe=true\n12:03:49 circuit=inventory state=open failures=1\n\nOnly one inventory pod was unhealthy, but the gateway rejected roughly 70% of requests for eight minutes. Service discovery listed twelve endpoints. Inspect the load-balancer, retry, and circuit-breaker interaction to explain how a single pod poisoned the shared circuit. Implement the appropriate isolation and a regression test.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Code-review packet from SEC-391:\n\nNew files:\ninternal/plugins/loader.go\ninternal/plugins/manifest.go\ninternal/plugins/sandbox_linux.go\n\nPlugin flow:\n1. Read manifest from user-supplied archive.\n2. Extract to cache directory.\n3. Verify SHA-256 from registry response.\n4. Launch executable with JSON-RPC over stdio.\n5. Pass selected environment variables and workspace path.\n\nReviewer concerns:\n- archive traversal and symlinks\n- digest verification occurs after extraction\n- inherited file descriptors\n- environment allowlist defaults\n- cache replacement races\n- executable permissions\n\nReview the current branch for exploitable paths and sandbox escapes. Report severity, exact code path, attacker prerequisites, and recommended mitigation. Do not make changes; this is an assessment for the security gate.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Schema proposal excerpt:\n\nCREATE TABLE device_readings (\n tenant_id uuid NOT NULL,\n device_id uuid NOT NULL,\n observed_at timestamptz NOT NULL,\n metric_id smallint NOT NULL,\n value double precision,\n quality smallint NOT NULL,\n PRIMARY KEY (tenant_id, device_id, observed_at, metric_id)\n) PARTITION BY RANGE (observed_at);\n\nExpected volume: 4 billion rows/year.\nQueries:\n- latest 50 readings for one device\n- hourly aggregates for a tenant and metric\n- delete one tenant within 24 hours\n- retain raw data 90 days, aggregates 5 years\n\nReview this design for partition pruning, index size, hot partitions, deletion cost, null semantics, and TimescaleDB alternatives. No DDL changes requested; return findings and suggested experiments.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} {"prompt":"Notes gathered for the API migration guide:\n\nOld endpoint: POST /v1/render\nNew flow:\n1. POST /v2/render-jobs\n2. poll GET /v2/render-jobs/{id} or supply webhook_url\n3. download result_url before its 15-minute expiry\n\nCompatibility details:\n- v1 accepts inline templates; v2 requires template_id\n- v2 idempotency uses Idempotency-Key\n- synchronous validation errors remain HTTP 422\n- processing failures appear in job.error\n- maximum input grows from 5 MB to 25 MB\n- v1 shuts down on 2027-01-15\n- SDK support begins in Java 6.8, Python 4.2, JS 9.1\n\nWrite the customer-facing migration guide with before-and-after examples, error handling, polling and webhook patterns, version requirements, and the exact deprecation date.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} -{"prompt":"Raw incident notes:\n\nImpact: EU search indexing delayed 3h 42m; searches returned stale documents but no data was lost.\nTrigger: Terraform apply replaced the Kafka private endpoint before new DNS records propagated.\nDetection: customer support ticket at 09:18; internal lag alert fired at 09:41 because threshold was too high.\nResponse: restarted consumers twice, then network team identified NXDOMAIN responses.\nRecovery: restored old endpoint, flushed node-local DNS caches, replayed retained events.\nContributors: shared module coupled endpoint replacement to subnet tag change; runbook assumed SERVFAIL, not NXDOMAIN; dashboard aggregated all regions.\nActions discussed: regional lag alerts, create-before-destroy, DNS preflight, synthetic consumer.\n\nTurn this into a blameless postmortem with timeline, root cause, contributing factors, detection gaps, recovery, and clearly owned corrective-action placeholders.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.46,"slice":"pasted-context","lang":"en"} -{"prompt":"map this out somehow","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} +{"prompt":"Raw incident notes:\n\nImpact: EU search indexing delayed 3h 42m; searches returned stale documents but no data was lost.\nTrigger: Terraform apply replaced the Kafka private endpoint before new DNS records propagated.\nDetection: customer support ticket at 09:18; internal lag alert fired at 09:41 because threshold was too high.\nResponse: restarted consumers twice, then network team identified NXDOMAIN responses.\nRecovery: restored old endpoint, flushed node-local DNS caches, replayed retained events.\nContributors: shared module coupled endpoint replacement to subnet tag change; runbook assumed SERVFAIL, not NXDOMAIN; dashboard aggregated all regions.\nActions discussed: regional lag alerts, create-before-destroy, DNS preflight, synthetic consumer.\n\nTurn this into a blameless postmortem with timeline, root cause, contributing factors, detection gaps, recovery, and clearly owned corrective-action placeholders.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"map this out somehow","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"build the ingest bit","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"make the screen nicer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.37,"slice":"vague-eval","lang":"en"} -{"prompt":"one small tweak","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.13,"slice":"vague-eval","lang":"en"} -{"prompt":"untangle yesterday's code","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"vague-eval","lang":"en"} -{"prompt":"prod is being weird","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"vague-eval","lang":"en"} -{"prompt":"check over the new thing","purpose":"review","secondary":null,"mixed":false,"difficulty":0.46,"slice":"vague-eval","lang":"en"} -{"prompt":"what do you think of this","purpose":"review","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"need docs for it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.32,"slice":"vague-eval","lang":"en"} -{"prompt":"summarize the work so far","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.31,"slice":"vague-eval","lang":"en"} -{"prompt":"Sketch a migration strategy for moving tenant preferences from Redis hashes into Postgres JSONB, including rollout phases, dual-write timing, backfill verification, rollback signals, and how older mobile clients remain compatible. I only need the design and milestone breakdown for now.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"en"} -{"prompt":"Before touching the notification service, outline how idempotency keys should flow through the API, SQS queue, and worker retries. Include tradeoffs between storing keys in DynamoDB and Postgres; deliver a design, not code.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.76,"slice":"boundary","lang":"en"} -{"prompt":"Add cursor pagination to `/v2/audit-events`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.36,"slice":"core","lang":"en"} -{"prompt":"Picking up the intermittent checkout failure. Here is the useful tail from `payments-api`:\n\n```text\n2026-07-29T18:42:09.114Z INFO charge.start cart=crt_8f21 attempt=1\n2026-07-29T18:42:09.306Z INFO stripe.intent status=requires_confirmation pi=pi_19a\n2026-07-29T18:42:39.311Z WARN request context deadline exceeded route=/v1/checkout\n2026-07-29T18:42:39.313Z ERROR rollback failed err='sql: transaction has already been committed or rolled back'\n2026-07-29T18:42:39.314Z INFO charge.retry_scheduled delay=5s\n2026-07-29T18:42:44.512Z INFO stripe.intent status=succeeded pi=pi_19a\n2026-07-29T18:42:44.519Z ERROR order insert duplicate key value violates unique constraint orders_payment_intent_key\n```\n\nIt only happens under moderate load and customers sometimes receive a charge but no confirmation screen. Trace the likely control-flow failure and determine why the retry is attempting the order insert after the request transaction is gone.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Build the SwiftUI `StorageBreakdownView` from the existing Figma measurements in `DesignTokens.swift`: segmented capacity bar, category legend, dynamic type support, and the compact layout used below 390 points.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Design and implement a distributed rate limiter for the Go gateway. Start by writing a short design covering token-bucket semantics, Redis failure behavior, tenant-level overrides, observability, and safe rollout. Then add the middleware, Lua script, configuration plumbing, and focused tests. Treat the design as the primary deliverable because the team must be able to challenge the operational choices before accepting the code.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.91,"slice":"mixed","lang":"en"} -{"prompt":"Flip `ENABLE_V2_EXPORTS` to true","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"Extract the duplicated JWT claim parsing from `admin_auth.go` and `customer_auth.go` into one internal helper. Keep accepted algorithms, errors, logs, and claim validation exactly as they are.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Expose the OpenAPI schema through `/internal/schema.json` using the spec already embedded in the binary; add ETag handling and tests for conditional GETs.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.43,"slice":"boundary","lang":"en"} -{"prompt":"make the dashboard less sad","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.34,"slice":"vague-eval","lang":"en"} -{"prompt":"Find out why `ArchiveCoordinator` crashes on the second background sync with `Fatal error: Attempted to read an unowned reference`. The first sync always completes and I do not know which object is being released early.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Walk me through how `LeaseManager.acquire()` prevents two workers from owning the same shard. Pay special attention to the fencing token and tell me whether the transaction boundaries are safe. Do not modify anything.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.56,"slice":"core","lang":"en"} -{"prompt":"Ticket text copied from Linear:\n\n```text\nENG-4812 — release communication for regional failover\nStatus: engineering complete\nAudience: customer SREs and internal support\nWhat changed:\n- API traffic can fail over from `us-east-1` to `us-west-2`\n- websocket sessions reconnect rather than migrate\n- customer allowlists may need the new west-region egress ranges\n- no payload or authentication changes\nKnown limitation: exports already running during a failover restart from their last durable checkpoint\nSupport macro must avoid saying zero downtime\nLinks: runbook OPS-77, dashboard `Global Routing / Customer Impact`\n```\n\nTurn this into concise release notes plus a migration advisory for customers with strict IP allowlists. Keep it factual, avoid marketing language, and do not invent availability guarantees.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.48,"slice":"pasted-context","lang":"en"} -{"prompt":"Move the unread badge three pixels left and align it optically with the avatar; no other changes to `ConversationRow.tsx`.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.16,"slice":"boundary","lang":"en"} -{"prompt":"Document the local development flow for the Rust indexing service, including starting Redpanda, loading the sample corpus, running one worker, and inspecting a failed message.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.34,"slice":"core","lang":"en"} -{"prompt":"Create the `/v1/service-accounts` endpoint with validation, authorization, and integration tests, then add a short API reference section showing the request, response, and two common error cases.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Map out an incremental replacement of our homegrown iOS navigation coordinator with `NavigationStack`. Cover deep links, state restoration, modal ownership, test migration, and fallback checkpoints without changing source files yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Rename the local variable `usr` to `user` in `InviteHandler.ts`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"boundary","lang":"en"} -{"prompt":"Teach the Python CLI's `sync` command to resume multipart uploads from its SQLite checkpoint table and reject checkpoints belonging to a different source file.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Tighten the modal's corner radius","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Bump `grpcio-tools` from 1.74.0 to 1.74.1","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"Change `UserStore` to `IdentityStore` across the Kotlin modules, filenames, tests, and Dagger bindings. This is naming cleanup only; runtime behavior and public JSON fields must stay identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"boundary","lang":"en"} -{"prompt":"Separate `InvoiceService` into calculation, persistence, and delivery collaborators without changing its public methods or the ordering of emitted events.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Fresh ticket plus acceptance notes:\n\n```text\nBILL-992 webhook reconciliation\nWhen our provider returns 202, it may deliver `invoice.settled` more than once and out of order with `invoice.updated`.\n\nCurrent tables:\nwebhook_receipts(provider_id unique, received_at, body)\ninvoices(id, account_id, state, amount_due, version)\n\nAcceptance:\n- HTTP handler acknowledges valid signatures within 250 ms\n- processing occurs asynchronously\n- duplicate provider IDs have no effect\n- an older invoice version cannot overwrite a newer one\n- poison events move to `billing-webhooks-dlq` after 8 attempts\n- expose counters for duplicate, stale, applied, and dead-lettered events\n- retain raw receipts for 30 days\n\nExisting entry point: `cmd/billing-api/webhooks.go`\n```\n\nImplement the handler, queue consumer, persistence operations, retry policy, and integration tests against Postgres.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Work out why scrolling `TimelineView` eventually pins one CPU core on iOS 18. Instruments points at repeated `GeometryReader` updates, but I cannot tell what is feeding the layout loop.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Finish the command palette UI and add a short keyboard-navigation section to the contributor guide. The palette needs grouped results, an empty state, arrow-key selection, and reduced-motion behavior; the guide should explain the implemented shortcuts and focus rules.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.66,"slice":"mixed","lang":"en"} -{"prompt":"Why does `SessionRepository` hash the refresh token twice before storing it? Explain the existing rationale from call sites and tests; nothing appears broken, so please do not edit code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Rewrite the README setup section so a new Android engineer can run the app with the mock GraphQL server and a local OAuth callback.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Since upgrading Tokio, this test hangs instead of failing:\n\n```text\n$ cargo test lease_expiry_releases_slot -- --nocapture\nrunning 1 test\ntest lease_expiry_releases_slot ... worker acquired slot 3\nclock advanced by 31s\nwaiting for expiry notification\n```\n\nThe test uses `#[tokio::test(start_paused = true)]`, and the relevant task calls `interval.tick().await` before selecting on a cancellation token. Determine why virtual time no longer advances to the expected notification and identify whether the production loop or only the test setup is flawed.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"finish the sync thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"Propose an event model for collaborative document cursors. Include ordering guarantees, disconnect cleanup, fan-out limits, multi-region implications, and a staged path from the current single-node WebSocket hub.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"Wire `POST /devices/{id}/rotate-key` to the HSM client, record the new key version atomically, and return a conflict when another rotation is in progress.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"PR excerpt for inspection:\n\n```diff\n func (s *Store) Claim(ctx context.Context, id string, owner string) error {\n- _, err := s.db.ExecContext(ctx, `UPDATE jobs SET owner=$1 WHERE id=$2 AND owner IS NULL`, owner, id)\n- return err\n+ tx, err := s.db.BeginTx(ctx, nil)\n+ if err != nil { return err }\n+ defer tx.Rollback()\n+ var current *string\n+ err = tx.QueryRowContext(ctx, `SELECT owner FROM jobs WHERE id=$1`, id).Scan(¤t)\n+ if err != nil { return err }\n+ if current != nil { return ErrClaimed }\n+ _, err = tx.ExecContext(ctx, `UPDATE jobs SET owner=$1 WHERE id=$2`, owner, id)\n+ if err != nil { return err }\n+ return tx.Commit()\n }\n```\n\nThe author says the transaction closes a race. Review whether that is true under Postgres `READ COMMITTED`, call out any scan or locking issues, and explain what two concurrent callers can observe. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"pasted-context","lang":"en"} -{"prompt":"Schreibe eine kurze ADR für die Entscheidung, Refresh-Tokens in Postgres statt in Redis zu speichern. Bitte Alternativen, Konsequenzen und Rollback erwähnen; keinen Code ändern.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"boundary","lang":"de"} -{"prompt":"Give the Android media picker a two-column tablet layout, retained selection indicators, and a bottom action bar that respects gesture insets.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} -{"prompt":"Trace the current file-import pipeline, explain where MIME detection and decompression happen, and turn the findings into an onboarding note under `docs/importer.md`. Do not alter runtime code.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.58,"slice":"mixed","lang":"en"} +{"prompt":"make the screen nicer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"one small tweak","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"untangle yesterday's code","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"prod is being weird","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"check over the new thing","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"what do you think of this","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"need docs for it","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"summarize the work so far","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Sketch a migration strategy for moving tenant preferences from Redis hashes into Postgres JSONB, including rollout phases, dual-write timing, backfill verification, rollback signals, and how older mobile clients remain compatible. I only need the design and milestone breakdown for now.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Before touching the notification service, outline how idempotency keys should flow through the API, SQS queue, and worker retries. Include tradeoffs between storing keys in DynamoDB and Postgres; deliver a design, not code.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add cursor pagination to `/v2/audit-events`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Picking up the intermittent checkout failure. Here is the useful tail from `payments-api`:\n\n```text\n2026-07-29T18:42:09.114Z INFO charge.start cart=crt_8f21 attempt=1\n2026-07-29T18:42:09.306Z INFO stripe.intent status=requires_confirmation pi=pi_19a\n2026-07-29T18:42:39.311Z WARN request context deadline exceeded route=/v1/checkout\n2026-07-29T18:42:39.313Z ERROR rollback failed err='sql: transaction has already been committed or rolled back'\n2026-07-29T18:42:39.314Z INFO charge.retry_scheduled delay=5s\n2026-07-29T18:42:44.512Z INFO stripe.intent status=succeeded pi=pi_19a\n2026-07-29T18:42:44.519Z ERROR order insert duplicate key value violates unique constraint orders_payment_intent_key\n```\n\nIt only happens under moderate load and customers sometimes receive a charge but no confirmation screen. Trace the likely control-flow failure and determine why the retry is attempting the order insert after the request transaction is gone.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Build the SwiftUI `StorageBreakdownView` from the existing Figma measurements in `DesignTokens.swift`: segmented capacity bar, category legend, dynamic type support, and the compact layout used below 390 points.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Design and implement a distributed rate limiter for the Go gateway. Start by writing a short design covering token-bucket semantics, Redis failure behavior, tenant-level overrides, observability, and safe rollout. Then add the middleware, Lua script, configuration plumbing, and focused tests. Treat the design as the primary deliverable because the team must be able to challenge the operational choices before accepting the code.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Flip `ENABLE_V2_EXPORTS` to true","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Extract the duplicated JWT claim parsing from `admin_auth.go` and `customer_auth.go` into one internal helper. Keep accepted algorithms, errors, logs, and claim validation exactly as they are.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Expose the OpenAPI schema through `/internal/schema.json` using the spec already embedded in the binary; add ETag handling and tests for conditional GETs.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"make the dashboard less sad","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Find out why `ArchiveCoordinator` crashes on the second background sync with `Fatal error: Attempted to read an unowned reference`. The first sync always completes and I do not know which object is being released early.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Walk me through how `LeaseManager.acquire()` prevents two workers from owning the same shard. Pay special attention to the fencing token and tell me whether the transaction boundaries are safe. Do not modify anything.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Ticket text copied from Linear:\n\n```text\nENG-4812 — release communication for regional failover\nStatus: engineering complete\nAudience: customer SREs and internal support\nWhat changed:\n- API traffic can fail over from `us-east-1` to `us-west-2`\n- websocket sessions reconnect rather than migrate\n- customer allowlists may need the new west-region egress ranges\n- no payload or authentication changes\nKnown limitation: exports already running during a failover restart from their last durable checkpoint\nSupport macro must avoid saying zero downtime\nLinks: runbook OPS-77, dashboard `Global Routing / Customer Impact`\n```\n\nTurn this into concise release notes plus a migration advisory for customers with strict IP allowlists. Keep it factual, avoid marketing language, and do not invent availability guarantees.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} +{"prompt":"Move the unread badge three pixels left and align it optically with the avatar; no other changes to `ConversationRow.tsx`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Document the local development flow for the Rust indexing service, including starting Redpanda, loading the sample corpus, running one worker, and inspecting a failed message.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Create the `/v1/service-accounts` endpoint with validation, authorization, and integration tests, then add a short API reference section showing the request, response, and two common error cases.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Map out an incremental replacement of our homegrown iOS navigation coordinator with `NavigationStack`. Cover deep links, state restoration, modal ownership, test migration, and fallback checkpoints without changing source files yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Rename the local variable `usr` to `user` in `InviteHandler.ts`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Teach the Python CLI's `sync` command to resume multipart uploads from its SQLite checkpoint table and reject checkpoints belonging to a different source file.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Tighten the modal's corner radius","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Bump `grpcio-tools` from 1.74.0 to 1.74.1","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Change `UserStore` to `IdentityStore` across the Kotlin modules, filenames, tests, and Dagger bindings. This is naming cleanup only; runtime behavior and public JSON fields must stay identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Separate `InvoiceService` into calculation, persistence, and delivery collaborators without changing its public methods or the ordering of emitted events.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Fresh ticket plus acceptance notes:\n\n```text\nBILL-992 webhook reconciliation\nWhen our provider returns 202, it may deliver `invoice.settled` more than once and out of order with `invoice.updated`.\n\nCurrent tables:\nwebhook_receipts(provider_id unique, received_at, body)\ninvoices(id, account_id, state, amount_due, version)\n\nAcceptance:\n- HTTP handler acknowledges valid signatures within 250 ms\n- processing occurs asynchronously\n- duplicate provider IDs have no effect\n- an older invoice version cannot overwrite a newer one\n- poison events move to `billing-webhooks-dlq` after 8 attempts\n- expose counters for duplicate, stale, applied, and dead-lettered events\n- retain raw receipts for 30 days\n\nExisting entry point: `cmd/billing-api/webhooks.go`\n```\n\nImplement the handler, queue consumer, persistence operations, retry policy, and integration tests against Postgres.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Work out why scrolling `TimelineView` eventually pins one CPU core on iOS 18. Instruments points at repeated `GeometryReader` updates, but I cannot tell what is feeding the layout loop.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Finish the command palette UI and add a short keyboard-navigation section to the contributor guide. The palette needs grouped results, an empty state, arrow-key selection, and reduced-motion behavior; the guide should explain the implemented shortcuts and focus rules.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does `SessionRepository` hash the refresh token twice before storing it? Explain the existing rationale from call sites and tests; nothing appears broken, so please do not edit code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Rewrite the README setup section so a new Android engineer can run the app with the mock GraphQL server and a local OAuth callback.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Since upgrading Tokio, this test hangs instead of failing:\n\n```text\n$ cargo test lease_expiry_releases_slot -- --nocapture\nrunning 1 test\ntest lease_expiry_releases_slot ... worker acquired slot 3\nclock advanced by 31s\nwaiting for expiry notification\n```\n\nThe test uses `#[tokio::test(start_paused = true)]`, and the relevant task calls `interval.tick().await` before selecting on a cancellation token. Determine why virtual time no longer advances to the expected notification and identify whether the production loop or only the test setup is flawed.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"finish the sync thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Propose an event model for collaborative document cursors. Include ordering guarantees, disconnect cleanup, fan-out limits, multi-region implications, and a staged path from the current single-node WebSocket hub.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Wire `POST /devices/{id}/rotate-key` to the HSM client, record the new key version atomically, and return a conflict when another rotation is in progress.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"PR excerpt for inspection:\n\n```diff\n func (s *Store) Claim(ctx context.Context, id string, owner string) error {\n- _, err := s.db.ExecContext(ctx, `UPDATE jobs SET owner=$1 WHERE id=$2 AND owner IS NULL`, owner, id)\n- return err\n+ tx, err := s.db.BeginTx(ctx, nil)\n+ if err != nil { return err }\n+ defer tx.Rollback()\n+ var current *string\n+ err = tx.QueryRowContext(ctx, `SELECT owner FROM jobs WHERE id=$1`, id).Scan(¤t)\n+ if err != nil { return err }\n+ if current != nil { return ErrClaimed }\n+ _, err = tx.ExecContext(ctx, `UPDATE jobs SET owner=$1 WHERE id=$2`, owner, id)\n+ if err != nil { return err }\n+ return tx.Commit()\n }\n```\n\nThe author says the transaction closes a race. Review whether that is true under Postgres `READ COMMITTED`, call out any scan or locking issues, and explain what two concurrent callers can observe. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Schreibe eine kurze ADR für die Entscheidung, Refresh-Tokens in Postgres statt in Redis zu speichern. Bitte Alternativen, Konsequenzen und Rollback erwähnen; keinen Code ändern.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"de"} +{"prompt":"Give the Android media picker a two-column tablet layout, retained selection indicators, and a bottom action bar that respects gesture insets.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Trace the current file-import pipeline, explain where MIME detection and decompression happen, and turn the findings into an onboarding note under `docs/importer.md`. Do not alter runtime code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Set the Helm chart's default replica count to 3","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Benenne `LegacyClock` im gesamten Repository in `MonotonicClock` um, einschließlich Swift package products und Tests. Das Verhalten und die öffentliche API abgesehen vom Namen sollen unverändert bleiben.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"de"} -{"prompt":"Consolidate the three protobuf timestamp conversion utilities into `internal/timewire` while preserving their exact rounding, error, and zero-value behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.47,"slice":"core","lang":"en"} -{"prompt":"Diagnose the duplicate toast after login","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"Explain how `SnapshotReader` chooses between the base SSTable and delta files, including what happens when a compaction manifest is incomplete.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Draft a troubleshooting page for common `forge deploy` failures: expired device code, dirty workspace, missing environment mapping, and a rollout that times out.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"boundary","lang":"en"} -{"prompt":"Plan the deprecation of the XML ingestion endpoint, covering usage discovery, customer communication, shadow parsing, parity metrics, and the date-based removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Issue report copied from the web team:\n\n```text\nTitle: filters panel redesign for search results\nRoute: `/catalog/search`\nDesktop: fixed 288px left rail, results stay fluid\nTablet: filters open as a modal sheet\nMobile: full-screen panel with sticky Apply button\nStates needed: loading skeleton, no facets, selected chips wrapping to two lines, 100+ values with internal search\nAccessibility: focus returns to Filters trigger after close; counts must not be announced twice; Escape closes modal variants\nTokens: use `surface-raised`, `space-300`, `radius-200`; no raw hex values\nExisting files: `SearchFilters.tsx`, `FacetGroup.tsx`, `search.css`\nOut of scope: changing query semantics or facet API\n```\n\nImplement the responsive UI and component tests. Preserve the current URL synchronization behavior.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"pasted-context","lang":"en"} -{"prompt":"Implement `PUT /profiles/{id}/timezone` so it validates IANA names, updates the profile version, and emits `profile.timezone_changed` in the same transaction.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Pin `actions/cache` to `v4.2.4`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Adjust the account switcher so long organization names ellipsize before the chevron rather than pushing it outside the menu.","purpose":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.28,"slice":"mixed","lang":"en"} -{"prompt":"Replace nested conditionals in `resolvePermissions` with named predicates and a flat decision flow. The returned permissions and audit reasons must not change.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.48,"slice":"core","lang":"en"} -{"prompt":"Cambie el nombre local `data` a `invoicePayload` solo en `InvoiceMapper.ts`; no cambies tipos ni comportamiento.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"boundary","lang":"es"} -{"prompt":"Investigate why the macOS menu-bar helper sometimes launches two status items after wake. There is only one login item registered, and I do not yet know whether restoration or our app delegate is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Summarize the behavior of `RetryBudget` for a reviewer who has not worked on the gateway, using the implementation and tests as the source of truth.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.32,"slice":"core","lang":"en"} -{"prompt":"Lay out a capacity plan for growing the metrics ingestion path from 80k to 500k samples per second. Cover Kafka partitioning, ClickHouse shard sizing, backpressure, cardinality controls, cost checkpoints, and load-test milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"core","lang":"en"} -{"prompt":"Add support for Ed25519 host keys to the Rust SSH config parser, including OpenSSH fixture coverage and useful errors for malformed base64.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Polish `EmptyWorkspaceView` with the existing illustration, a constrained text column, primary and secondary actions, and correct dark-mode colors.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"Remove the extra comma in `settings.json`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} -{"prompt":"Merge the duplicated pagination state machines used by `MembersTable` and `ApiKeysTable` without changing navigation, loading states, or query parameters.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"I cannot explain this parser result:\n\n```text\ninput: 2026-03-29 02:30 Europe/Paris\nactual: 2026-03-29T03:30:00+02:00\nexpect: InvalidLocalTime\n\ninput: 2026-10-25 02:30 Europe/Paris\nactual: 2026-10-25T02:30:00+01:00\nexpect: AmbiguousLocalTime\n```\n\n`LocalTimestamp.parse` first builds a `LocalDateTime`, calls `zone.rules.getOffset`, and only checks `isDaylightSavings` afterward. The same fixtures pass with fixed-offset zones. Determine why the gap and overlap are being normalized instead of rejected, and locate the incorrect API assumption. Please diagnose before proposing changes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"pasted-context","lang":"en"} -{"prompt":"Correct the typo `recieved_at` in the new, unreleased migration file and its matching model field.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.14,"slice":"boundary","lang":"en"} -{"prompt":"Describe how the current feature-flag evaluator resolves account, organization, and global rules when their variants disagree. Cite the relevant functions, but make no edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.48,"slice":"core","lang":"en"} -{"prompt":"Clean up the protocol layer by moving frame encoding out of `Connection`, splitting read and write state, and keeping byte-for-byte wire output plus all public errors unchanged. Also write a short maintainer note describing the new module boundaries.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Plan a safe migration from integer user IDs to UUIDv7 across Postgres, Kafka events, caches, and public APIs. Include compatibility columns, backfill sequencing, verification queries, dual-read removal criteria, and rollback points.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Add `/health/ready` to the worker process","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.26,"slice":"core","lang":"en"} -{"prompt":"Make the selected tab underline animate between destinations using Compose, while respecting the system animator-duration setting.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"just fix the little spacing thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.18,"slice":"vague-eval","lang":"en"} -{"prompt":"Restructure the TypeScript SDK so transport, authentication, and generated resources no longer import through the package barrel. Preserve exports, bundle shape, and runtime behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Determine whether the unexpected logout is caused by refresh-token rotation or by the app clearing Keychain on upgrade. Instrument the relevant paths, reproduce with an upgraded install, and implement the appropriate correction once the cause is proven.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.82,"slice":"mixed","lang":"en"} -{"prompt":"Why is `MAX_BATCH_BYTES` checked before compression instead of after it? Review commit-adjacent code and tests to explain the intended semantics; do not change it.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.44,"slice":"boundary","lang":"en"} -{"prompt":"Figure out why the WASM worker returns stale autocomplete results when two requests arrive within the same animation frame.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} +{"prompt":"Benenne `LegacyClock` im gesamten Repository in `MonotonicClock` um, einschließlich Swift package products und Tests. Das Verhalten und die öffentliche API abgesehen vom Namen sollen unverändert bleiben.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} +{"prompt":"Consolidate the three protobuf timestamp conversion utilities into `internal/timewire` while preserving their exact rounding, error, and zero-value behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose the duplicate toast after login","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Explain how `SnapshotReader` chooses between the base SSTable and delta files, including what happens when a compaction manifest is incomplete.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft a troubleshooting page for common `forge deploy` failures: expired device code, dirty workspace, missing environment mapping, and a rollout that times out.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Plan the deprecation of the XML ingestion endpoint, covering usage discovery, customer communication, shadow parsing, parity metrics, and the date-based removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Issue report copied from the web team:\n\n```text\nTitle: filters panel redesign for search results\nRoute: `/catalog/search`\nDesktop: fixed 288px left rail, results stay fluid\nTablet: filters open as a modal sheet\nMobile: full-screen panel with sticky Apply button\nStates needed: loading skeleton, no facets, selected chips wrapping to two lines, 100+ values with internal search\nAccessibility: focus returns to Filters trigger after close; counts must not be announced twice; Escape closes modal variants\nTokens: use `surface-raised`, `space-300`, `radius-200`; no raw hex values\nExisting files: `SearchFilters.tsx`, `FacetGroup.tsx`, `search.css`\nOut of scope: changing query semantics or facet API\n```\n\nImplement the responsive UI and component tests. Preserve the current URL synchronization behavior.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Implement `PUT /profiles/{id}/timezone` so it validates IANA names, updates the profile version, and emits `profile.timezone_changed` in the same transaction.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Pin `actions/cache` to `v4.2.4`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Adjust the account switcher so long organization names ellipsize before the chevron rather than pushing it outside the menu.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Replace nested conditionals in `resolvePermissions` with named predicates and a flat decision flow. The returned permissions and audit reasons must not change.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Cambie el nombre local `data` a `invoicePayload` solo en `InvoiceMapper.ts`; no cambies tipos ni comportamiento.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"es"} +{"prompt":"Investigate why the macOS menu-bar helper sometimes launches two status items after wake. There is only one login item registered, and I do not yet know whether restoration or our app delegate is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Summarize the behavior of `RetryBudget` for a reviewer who has not worked on the gateway, using the implementation and tests as the source of truth.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Lay out a capacity plan for growing the metrics ingestion path from 80k to 500k samples per second. Cover Kafka partitioning, ClickHouse shard sizing, backpressure, cardinality controls, cost checkpoints, and load-test milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add support for Ed25519 host keys to the Rust SSH config parser, including OpenSSH fixture coverage and useful errors for malformed base64.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Polish `EmptyWorkspaceView` with the existing illustration, a constrained text column, primary and secondary actions, and correct dark-mode colors.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Remove the extra comma in `settings.json`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Merge the duplicated pagination state machines used by `MembersTable` and `ApiKeysTable` without changing navigation, loading states, or query parameters.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"I cannot explain this parser result:\n\n```text\ninput: 2026-03-29 02:30 Europe/Paris\nactual: 2026-03-29T03:30:00+02:00\nexpect: InvalidLocalTime\n\ninput: 2026-10-25 02:30 Europe/Paris\nactual: 2026-10-25T02:30:00+01:00\nexpect: AmbiguousLocalTime\n```\n\n`LocalTimestamp.parse` first builds a `LocalDateTime`, calls `zone.rules.getOffset`, and only checks `isDaylightSavings` afterward. The same fixtures pass with fixed-offset zones. Determine why the gap and overlap are being normalized instead of rejected, and locate the incorrect API assumption. Please diagnose before proposing changes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Correct the typo `recieved_at` in the new, unreleased migration file and its matching model field.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Describe how the current feature-flag evaluator resolves account, organization, and global rules when their variants disagree. Cite the relevant functions, but make no edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Clean up the protocol layer by moving frame encoding out of `Connection`, splitting read and write state, and keeping byte-for-byte wire output plus all public errors unchanged. Also write a short maintainer note describing the new module boundaries.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Plan a safe migration from integer user IDs to UUIDv7 across Postgres, Kafka events, caches, and public APIs. Include compatibility columns, backfill sequencing, verification queries, dual-read removal criteria, and rollback points.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add `/health/ready` to the worker process","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Make the selected tab underline animate between destinations using Compose, while respecting the system animator-duration setting.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"just fix the little spacing thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Restructure the TypeScript SDK so transport, authentication, and generated resources no longer import through the package barrel. Preserve exports, bundle shape, and runtime behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Determine whether the unexpected logout is caused by refresh-token rotation or by the app clearing Keychain on upgrade. Instrument the relevant paths, reproduce with an upgraded install, and implement the appropriate correction once the cause is proven.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Why is `MAX_BATCH_BYTES` checked before compression instead of after it? Review commit-adjacent code and tests to explain the intended semantics; do not change it.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Figure out why the WASM worker returns stale autocomplete results when two requests arrive within the same animation frame.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Create an operator runbook for draining a NATS JetStream consumer, replaying a dead-letter subject, and confirming that lag has recovered.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"The architecture note currently says:\n\n```text\nPhase A: both legacy and new credential validators run; legacy decides the response\nPhase B: new validator decides, legacy runs for comparison\nPhase C: remove legacy\nMismatch events include tenant ID, credential kind, old result, new result\nOpen questions:\n- whether to persist mismatch samples\n- how to handle tenants with custom clock skew\n- which error details are safe in metrics\n- mobile clients before 7.3 retry only on HTTP 401\nConstraints:\n- no forced logout during rollout\n- security requires an immediate rollback switch\n- support needs per-tenant visibility\n```\n\nTurn these notes into a complete implementation-free migration plan for replacing the credential validator. Define gates, metrics, rollback triggers, client compatibility work, and ownership by phase.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Give the app a proper onboarding screen","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Summarize `docs/security/session-model.md` into a one-page threat overview for the mobile team, and separately flag any claims that the implementation does not appear to support.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.61,"slice":"mixed","lang":"en"} -{"prompt":"Outline how to split the monolithic Rails billing application into deployable domains over four quarters, with dependency mapping, extraction order, staffing assumptions, and measurable exit criteria.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"boundary","lang":"en"} -{"prompt":"Implement a Bloom-filter-backed negative cache for missing artifact IDs in the registry service, including rotation and false-positive metrics.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Turn the pasted engineering notes into an ADR choosing between SQLite WAL and append-only JSON for the offline queue. Preserve the unresolved questions rather than pretending they are decided.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Move `RequestSigner` and its fixtures into `internal/signing` without altering package exports or signatures.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} -{"prompt":"Investigate rising memory in the image proxy; RSS grows about 40 MB per hour even when request volume is flat, and heap profiles do not account for most of it.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.83,"slice":"boundary","lang":"en"} -{"prompt":"Implement retention enforcement for object versions in the S3-compatible storage service. The worker must honor legal holds, batch deletions, checkpoint progress, and remain safe under duplicate queue delivery.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Remove the deprecated flag from `config.example.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Build a responsive compare-products table with a sticky first column, collapsible specification groups, keyboard-readable differences, and horizontal overflow cues.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Troque `timeoutMs` por `requestTimeoutMs` em todos os pacotes, testes e exemplos. É só uma mudança de nome; mantenha exatamente os mesmos defaults e comportamento.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.49,"slice":"boundary","lang":"pt"} -{"prompt":"Explain whether `QuotaReservation.release()` can decrement usage below zero when its caller retries after a timeout. Review the transaction and tests only; no bug has been observed.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Plan and implement resumable CSV imports for the admin API. First define the checkpoint model, idempotency contract, failure states, observability, and rollout phases. Then add upload-session endpoints, chunk validation, a queue-backed parser, persisted progress, cancellation, and integration tests. Prioritize the plan because imports can contain millions of rows and we need to review recovery behavior before enabling the feature.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.94,"slice":"mixed","lang":"en"} -{"prompt":"Design a caching strategy for personalized feed pages that balances freshness, fan-out cost, deletion compliance, and regional failover. Provide decision records and an adoption sequence, not implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.87,"slice":"core","lang":"en"} -{"prompt":"Add a gRPC method that streams current device health and resumes from a caller-provided sequence number.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"Restyle the iOS share extension to use the app's typography, show upload progress, and present retry actions without exceeding extension memory limits.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Set `minSdk` to 26","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"Unify the four error-to-HTTP mappings behind one table-driven function. Keep every status code, response body, log level, and metric name stable.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Report from CI:\n\n```text\nFAIL TestRebalanceDoesNotLoseOffsets (31.82s)\nconsumer_test.go:418: expected committed offset 991, got 987\nseed=731992\nbroker-1 assigned [orders-3 orders-7]\nbroker-2 heartbeat timeout after 9001ms\ncoordinator generation changed 42 -> 43\nworker A: flush offsets map[orders-3:991 orders-7:552]\nworker B: loaded offsets map[orders-3:987 orders-7:552]\n```\n\nThe failure appears about once in 300 runs and started after batching offset commits. Reproduce or reason through the generation transition, identify why partition 3 can reload the older value, and determine whether the client, mock broker, or commit ordering is at fault.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.88,"slice":"pasted-context","lang":"en"} -{"prompt":"Write the changelog entry for the new audit-log filters, including the renamed query parameter and the compatibility window.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.27,"slice":"boundary","lang":"en"} -{"prompt":"Audit the current Terraform module for the private EKS cluster. Explain its trust boundaries, public exposure, encryption settings, and any overly broad IAM grants without changing resources.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Add the account-lockout endpoint and document its request contract, authorization rules, response codes, and audit event for integrators.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.64,"slice":"mixed","lang":"en"} +{"prompt":"The architecture note currently says:\n\n```text\nPhase A: both legacy and new credential validators run; legacy decides the response\nPhase B: new validator decides, legacy runs for comparison\nPhase C: remove legacy\nMismatch events include tenant ID, credential kind, old result, new result\nOpen questions:\n- whether to persist mismatch samples\n- how to handle tenants with custom clock skew\n- which error details are safe in metrics\n- mobile clients before 7.3 retry only on HTTP 401\nConstraints:\n- no forced logout during rollout\n- security requires an immediate rollback switch\n- support needs per-tenant visibility\n```\n\nTurn these notes into a complete implementation-free migration plan for replacing the credential validator. Define gates, metrics, rollback triggers, client compatibility work, and ownership by phase.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Give the app a proper onboarding screen","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Summarize `docs/security/session-model.md` into a one-page threat overview for the mobile team, and separately flag any claims that the implementation does not appear to support.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Outline how to split the monolithic Rails billing application into deployable domains over four quarters, with dependency mapping, extraction order, staffing assumptions, and measurable exit criteria.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement a Bloom-filter-backed negative cache for missing artifact IDs in the registry service, including rotation and false-positive metrics.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Turn the pasted engineering notes into an ADR choosing between SQLite WAL and append-only JSON for the offline queue. Preserve the unresolved questions rather than pretending they are decided.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Move `RequestSigner` and its fixtures into `internal/signing` without altering package exports or signatures.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Investigate rising memory in the image proxy; RSS grows about 40 MB per hour even when request volume is flat, and heap profiles do not account for most of it.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement retention enforcement for object versions in the S3-compatible storage service. The worker must honor legal holds, batch deletions, checkpoint progress, and remain safe under duplicate queue delivery.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Remove the deprecated flag from `config.example.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build a responsive compare-products table with a sticky first column, collapsible specification groups, keyboard-readable differences, and horizontal overflow cues.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Troque `timeoutMs` por `requestTimeoutMs` em todos os pacotes, testes e exemplos. É só uma mudança de nome; mantenha exatamente os mesmos defaults e comportamento.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"pt"} +{"prompt":"Explain whether `QuotaReservation.release()` can decrement usage below zero when its caller retries after a timeout. Review the transaction and tests only; no bug has been observed.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Plan and implement resumable CSV imports for the admin API. First define the checkpoint model, idempotency contract, failure states, observability, and rollout phases. Then add upload-session endpoints, chunk validation, a queue-backed parser, persisted progress, cancellation, and integration tests. Prioritize the plan because imports can contain millions of rows and we need to review recovery behavior before enabling the feature.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Design a caching strategy for personalized feed pages that balances freshness, fan-out cost, deletion compliance, and regional failover. Provide decision records and an adoption sequence, not implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add a gRPC method that streams current device health and resumes from a caller-provided sequence number.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Restyle the iOS share extension to use the app's typography, show upload progress, and present retry actions without exceeding extension memory limits.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Set `minSdk` to 26","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Unify the four error-to-HTTP mappings behind one table-driven function. Keep every status code, response body, log level, and metric name stable.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Report from CI:\n\n```text\nFAIL TestRebalanceDoesNotLoseOffsets (31.82s)\nconsumer_test.go:418: expected committed offset 991, got 987\nseed=731992\nbroker-1 assigned [orders-3 orders-7]\nbroker-2 heartbeat timeout after 9001ms\ncoordinator generation changed 42 -> 43\nworker A: flush offsets map[orders-3:991 orders-7:552]\nworker B: loaded offsets map[orders-3:987 orders-7:552]\n```\n\nThe failure appears about once in 300 runs and started after batching offset commits. Reproduce or reason through the generation transition, identify why partition 3 can reload the older value, and determine whether the client, mock broker, or commit ordering is at fault.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Write the changelog entry for the new audit-log filters, including the renamed query parameter and the compatibility window.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Audit the current Terraform module for the private EKS cluster. Explain its trust boundaries, public exposure, encryption settings, and any overly broad IAM grants without changing resources.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add the account-lockout endpoint and document its request contract, authorization rules, response codes, and audit event for integrators.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} {"prompt":"Draft a roadmap for replacing Jenkins with GitHub Actions across 46 repositories. Include inventory, reusable workflow design, secret migration, canary repositories, rollback, ownership, and retirement criteria.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Store webhook signing secrets in Vault and teach the rotation job to accept both active versions during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Rework the macOS preferences window into a three-column `NavigationSplitView` with searchable settings and state restoration.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"do the cleanup we talked about","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.42,"slice":"vague-eval","lang":"en"} -{"prompt":"Why does `BillingRepository.save()` issue an update before attempting the insert? Nothing is failing; I want an explanation of the existing concurrency strategy and its tradeoffs.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose and correct the cold-start crash shown on Android 15 when encrypted preferences are first opened. Establish whether the keystore alias, backup restoration, or process initialization order is responsible, add a regression test, and implement the smallest proven fix.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"Produce a concise PR description for the existing diff in `feature/export-v3`, with sections for behavior changes, migration impact, testing, and rollback.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.28,"slice":"boundary","lang":"en"} -{"prompt":"Find the cause of occasional NaNs in the Metal particle simulation after the app returns from the background.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Create a contributor guide for adding a new SQL dialect to the formatter, covering lexer fixtures, precedence tables, snapshots, and fuzz tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"We want to replace the in-process scheduler. Notes from the spike:\n\n```text\nCandidates: Temporal, Restate, homegrown Postgres leases\nWorkload: 12M scheduled actions/day; 99.9% under 15 minutes; longest 180 days\nNeeds: per-tenant pause, exact audit trail, at-least-once execution, cancellation, replay in staging\nConstraints: no public cloud control plane; two regions active/passive; Java and Go workers\nCurrent pain: leader failover can delay jobs 8 minutes; schema deploys lock the schedule table\nUnknowns: Temporal operational load, Restate maturity for long timers, data migration cost\nDecision needed by Q4 planning\n```\n\nDevelop an architecture decision plan: evaluation criteria, prototypes, load tests, migration options, operational ownership, and a recommendation process. Do not choose a vendor without evidence.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"pasted-context","lang":"en"} -{"prompt":"Add the missing ARIA label to the icon-only refresh button","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.12,"slice":"core","lang":"en"} -{"prompt":"Write a design for offline-first edits in the field-inspection app, then implement the local operation log and sync engine once the conflict rules are explicit. Cover deletes, attachment uploads, clock skew, user-visible conflicts, storage limits, and migration from the current last-write-wins cache.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.95,"slice":"mixed","lang":"en"} -{"prompt":"Propose the data model and rollout milestones for organization-scoped API tokens, including permission inheritance, revocation propagation, auditability, and legacy token compatibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.82,"slice":"boundary","lang":"en"} -{"prompt":"Teach the DNS controller to coalesce duplicate reconciliation keys and apply exponential backoff without starving newly created zones.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Add loading skeletons to the profile cards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.22,"slice":"core","lang":"en"} -{"prompt":"Update the copyright year to 2026","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} -{"prompt":"Reshape the compiler's AST visitor into separate expression and declaration visitors while preserving emitted bytecode and diagnostics byte-for-byte.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Review comment from the incident channel:\n\n```text\nMina 09:12: cache hit ratio dropped from 91% to 34% right after deploy\nOwen 09:14: no eviction spike, Redis memory is flat\nMina 09:16: keys sampled after deploy include `catalog:v3:{tenant}:item:{id}`\nOwen 09:17: request logs still show lookup namespace `catalog:v2`\nMina 09:19: rollback restores hit ratio within five minutes\n```\n\nRelated diff moved key construction into `CacheNamespace` and introduced a schema version constant. Determine why reads and writes appear to use different versions, locate how the old namespace survives, and explain why rollback recovers gradually rather than instantly.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"pasted-context","lang":"en"} -{"prompt":"Change the button text from `Save changes` to `Save` on the profile form.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.08,"slice":"boundary","lang":"en"} -{"prompt":"Explain the ownership rules around `UnsafeBufferView` and whether callers can retain its pointer after the closure returns.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Implement conflict-safe slug changes and add a migration note for API clients that currently cache project URLs. The server work should reserve aliases atomically and redirect old slugs for 90 days; the note should spell out status codes and cache invalidation.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.75,"slice":"mixed","lang":"en"} -{"prompt":"Define a phased observability strategy for the edge proxy: common telemetry schema, tail sampling, cardinality budgets, SLO ownership, storage estimates, and adoption milestones across teams.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.87,"slice":"core","lang":"en"} -{"prompt":"Implement snapshot compaction for the embedded key-value engine, preserving reads during compaction and recovering safely after power loss.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.88,"slice":"core","lang":"en"} -{"prompt":"Create a Compose screen for pairing a sensor over BLE, including discovery states, permissions, progress, recoverable errors, and accessibility semantics.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"continue the crash stuff","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.51,"slice":"vague-eval","lang":"en"} -{"prompt":"Why does the allocator round 33-byte requests to 64 bytes? Inspect the size-class table and explain the existing choice; there is no reported failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.46,"slice":"boundary","lang":"en"} -{"prompt":"Track down the corrupted thumbnails, then implement the proven repair and write a short incident follow-up. Reports are limited to HEIC files imported through the share extension, but we do not yet know whether decoding, orientation, or disk caching is responsible.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.82,"slice":"mixed","lang":"en"} -{"prompt":"Turn the current parser behavior into a reference page describing supported duration literals, precedence, rounding, and error messages.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why connection draining occasionally lasts the full 30-minute hard timeout even after every visible request has completed.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Write release notes for version 4.8.0 using the merged PR titles, grouping changes into operators, SDK users, fixes, and deprecations.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"Planning notes from yesterday:\n\n```text\nGoal: move audit events from primary Postgres to ClickHouse\nVolume now: 18k events/sec, 14 TB retained\nQueries: tenant + time range, actor lookup, event-type aggregations\nCompliance: EU tenants stay in EU; erasure requests within 30 days\nCurrent writers are Ruby, Go, and Java\nPotential path: Kafka dual-publish, backfill monthly partitions, compare sampled queries\nRisks: ordering differs across producers, late events, schema drift, ClickHouse mutations are expensive\nMust retain old export API through migration\n```\n\nProduce a detailed migration roadmap with schema governance, capacity tests, dual-write verification, backfill sequencing, erasure handling, API compatibility, rollback checkpoints, and ownership. No implementation yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"pasted-context","lang":"en"} -{"prompt":"Give the calendar range picker a visible hover preview and clear start/end focus styling.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.36,"slice":"core","lang":"en"} -{"prompt":"Restructure the async image pipeline and document its new extension points. Keep caching, cancellation, priority, and rendering behavior unchanged; the prose should help plugin authors implement custom decoders.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Architect a tenant-isolation model for our shared Kafka platform, including topic ownership, quotas, encryption keys, schema access, noisy-neighbor controls, and incident containment.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"boundary","lang":"en"} -{"prompt":"Implement an incremental Merkle-tree verifier for backup chunks, with bounded memory and resumable progress.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Translate the deployment guide into Japanese while leaving commands, environment variables, and product names unchanged.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.34,"slice":"core","lang":"en"} -{"prompt":"Collapse the duplicate state adapters in `Sources/SyncCore` behind one generic wrapper without changing concurrency guarantees.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Find why our ONNX classifier produces different top labels on ARM64 and x86 for the same quantized model.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.84,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional outbox delivery to the account service, including cleanup, retry jitter, and a lag metric.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Change `LOG_LEVL` to `LOG_LEVEL` in `.env.example`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"core","lang":"en"} -{"prompt":"Implement the watchOS hydration summary card with gauge, trend caption, complication-consistent colors, and large-text fallback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"設定画面の `Notifcations` を `Notifications` に直して。文字列キーや挙動は変更しないで。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"ja"} -{"prompt":"Assess whether loading plugin manifests with `serde_yaml` allows aliases to cause excessive memory use. Explain the reachable input path and existing limits; do not patch it.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Tidy the checkout header spacing and consolidate its duplicated mobile/desktop CSS while preserving the rendered layout except for the specified eight-pixel gap correction.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.42,"slice":"mixed","lang":"en"} -{"prompt":"Develop a migration plan for moving secrets from Kubernetes Secrets to External Secrets Operator, including tenancy, refresh behavior, bootstrap credentials, disaster recovery, and staged namespace adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.84,"slice":"core","lang":"en"} -{"prompt":"Create a parser for OCI image references that handles digest-only forms, IPv6 registries, default tags, and precise validation errors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} +{"prompt":"Store webhook signing secrets in Vault and teach the rotation job to accept both active versions during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Rework the macOS preferences window into a three-column `NavigationSplitView` with searchable settings and state restoration.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Why does `BillingRepository.save()` issue an update before attempting the insert? Nothing is failing; I want an explanation of the existing concurrency strategy and its tradeoffs.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Diagnose and correct the cold-start crash shown on Android 15 when encrypted preferences are first opened. Establish whether the keystore alias, backup restoration, or process initialization order is responsible, add a regression test, and implement the smallest proven fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Produce a concise PR description for the existing diff in `feature/export-v3`, with sections for behavior changes, migration impact, testing, and rollback.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Find the cause of occasional NaNs in the Metal particle simulation after the app returns from the background.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create a contributor guide for adding a new SQL dialect to the formatter, covering lexer fixtures, precedence tables, snapshots, and fuzz tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"We want to replace the in-process scheduler. Notes from the spike:\n\n```text\nCandidates: Temporal, Restate, homegrown Postgres leases\nWorkload: 12M scheduled actions/day; 99.9% under 15 minutes; longest 180 days\nNeeds: per-tenant pause, exact audit trail, at-least-once execution, cancellation, replay in staging\nConstraints: no public cloud control plane; two regions active/passive; Java and Go workers\nCurrent pain: leader failover can delay jobs 8 minutes; schema deploys lock the schedule table\nUnknowns: Temporal operational load, Restate maturity for long timers, data migration cost\nDecision needed by Q4 planning\n```\n\nDevelop an architecture decision plan: evaluation criteria, prototypes, load tests, migration options, operational ownership, and a recommendation process. Do not choose a vendor without evidence.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Add the missing ARIA label to the icon-only refresh button","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Write a design for offline-first edits in the field-inspection app, then implement the local operation log and sync engine once the conflict rules are explicit. Cover deletes, attachment uploads, clock skew, user-visible conflicts, storage limits, and migration from the current last-write-wins cache.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Propose the data model and rollout milestones for organization-scoped API tokens, including permission inheritance, revocation propagation, auditability, and legacy token compatibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Teach the DNS controller to coalesce duplicate reconciliation keys and apply exponential backoff without starving newly created zones.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add loading skeletons to the profile cards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Update the copyright year to 2026","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Reshape the compiler's AST visitor into separate expression and declaration visitors while preserving emitted bytecode and diagnostics byte-for-byte.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Review comment from the incident channel:\n\n```text\nMina 09:12: cache hit ratio dropped from 91% to 34% right after deploy\nOwen 09:14: no eviction spike, Redis memory is flat\nMina 09:16: keys sampled after deploy include `catalog:v3:{tenant}:item:{id}`\nOwen 09:17: request logs still show lookup namespace `catalog:v2`\nMina 09:19: rollback restores hit ratio within five minutes\n```\n\nRelated diff moved key construction into `CacheNamespace` and introduced a schema version constant. Determine why reads and writes appear to use different versions, locate how the old namespace survives, and explain why rollback recovers gradually rather than instantly.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Change the button text from `Save changes` to `Save` on the profile form.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Explain the ownership rules around `UnsafeBufferView` and whether callers can retain its pointer after the closure returns.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement conflict-safe slug changes and add a migration note for API clients that currently cache project URLs. The server work should reserve aliases atomically and redirect old slugs for 90 days; the note should spell out status codes and cache invalidation.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Define a phased observability strategy for the edge proxy: common telemetry schema, tail sampling, cardinality budgets, SLO ownership, storage estimates, and adoption milestones across teams.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement snapshot compaction for the embedded key-value engine, preserving reads during compaction and recovering safely after power loss.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Create a Compose screen for pairing a sensor over BLE, including discovery states, permissions, progress, recoverable errors, and accessibility semantics.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Why does the allocator round 33-byte requests to 64 bytes? Inspect the size-class table and explain the existing choice; there is no reported failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down the corrupted thumbnails, then implement the proven repair and write a short incident follow-up. Reports are limited to HEIC files imported through the share extension, but we do not yet know whether decoding, orientation, or disk caching is responsible.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Turn the current parser behavior into a reference page describing supported duration literals, precedence, rounding, and error messages.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Investigate why connection draining occasionally lasts the full 30-minute hard timeout even after every visible request has completed.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write release notes for version 4.8.0 using the merged PR titles, grouping changes into operators, SDK users, fixes, and deprecations.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Planning notes from yesterday:\n\n```text\nGoal: move audit events from primary Postgres to ClickHouse\nVolume now: 18k events/sec, 14 TB retained\nQueries: tenant + time range, actor lookup, event-type aggregations\nCompliance: EU tenants stay in EU; erasure requests within 30 days\nCurrent writers are Ruby, Go, and Java\nPotential path: Kafka dual-publish, backfill monthly partitions, compare sampled queries\nRisks: ordering differs across producers, late events, schema drift, ClickHouse mutations are expensive\nMust retain old export API through migration\n```\n\nProduce a detailed migration roadmap with schema governance, capacity tests, dual-write verification, backfill sequencing, erasure handling, API compatibility, rollback checkpoints, and ownership. No implementation yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Give the calendar range picker a visible hover preview and clear start/end focus styling.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Restructure the async image pipeline and document its new extension points. Keep caching, cancellation, priority, and rendering behavior unchanged; the prose should help plugin authors implement custom decoders.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Architect a tenant-isolation model for our shared Kafka platform, including topic ownership, quotas, encryption keys, schema access, noisy-neighbor controls, and incident containment.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement an incremental Merkle-tree verifier for backup chunks, with bounded memory and resumable progress.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Translate the deployment guide into Japanese while leaving commands, environment variables, and product names unchanged.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Collapse the duplicate state adapters in `Sources/SyncCore` behind one generic wrapper without changing concurrency guarantees.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Find why our ONNX classifier produces different top labels on ARM64 and x86 for the same quantized model.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add transactional outbox delivery to the account service, including cleanup, retry jitter, and a lag metric.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Change `LOG_LEVL` to `LOG_LEVEL` in `.env.example`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Implement the watchOS hydration summary card with gauge, trend caption, complication-consistent colors, and large-text fallback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"設定画面の `Notifcations` を `Notifications` に直して。文字列キーや挙動は変更しないで。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"ja"} +{"prompt":"Assess whether loading plugin manifests with `serde_yaml` allows aliases to cause excessive memory use. Explain the reachable input path and existing limits; do not patch it.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Tidy the checkout header spacing and consolidate its duplicated mobile/desktop CSS while preserving the rendered layout except for the specified eight-pixel gap correction.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Develop a migration plan for moving secrets from Kubernetes Secrets to External Secrets Operator, including tenancy, refresh behavior, bootstrap credentials, disaster recovery, and staged namespace adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Create a parser for OCI image references that handles digest-only forms, IPv6 registries, default tags, and precise validation errors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Style the livestream chat composer for compact landscape, safe-area insets, attachment previews, and disabled-send feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Raise the request timeout from 10s to 15s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"core","lang":"en"} +{"prompt":"Raise the request timeout from 10s to 15s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Split `GameSession` into input, simulation, and replication modules. Preserve deterministic replays, network packet order, and all public APIs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Failure captured from an ESP32 test rig:\n\n```text\nboot: reset_reason=RTC_WDT\nsensor task started stack=4096\nwifi connected rssi=-61\nsample #18431 adc=2178\nsample #18432 adc=2180\nE queue: send timeout depth=64\nW uploader: retry in 2000ms\nE queue: send timeout depth=64\nGuru Meditation Error: Core 1 panic'ed (LoadProhibited)\nEXCVADDR: 0x00000014\nBacktrace: 0x400d91fe:0x3ffd2c20 0x400d4a77:0x3ffd2c50 0x400d51c1:0x3ffd2c80\n```\n\nThe panic occurs only after Wi-Fi drops for several minutes while sampling continues. Decode the likely failing path using the map file and determine whether queue saturation, a stale upload buffer, or watchdog recovery leads to the invalid load.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.85,"slice":"pasted-context","lang":"en"} -{"prompt":"Explain why the serializer writes map keys in lexical order even though MessagePack permits arbitrary ordering. Base the answer on existing tests and compatibility code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.39,"slice":"boundary","lang":"en"} -{"prompt":"Prepare an API guide for the existing batch-inference endpoint with request limits, NDJSON examples, streaming responses, cancellation, and error handling.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Plan the new plugin sandbox and then implement its capability checks. The design must cover filesystem scopes, outbound network policy, process spawning, audit logs, backward compatibility, and escape testing; after reviewable design notes, add the Rust enforcement layer and adversarial tests.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.96,"slice":"mixed","lang":"en"} -{"prompt":"Outline a six-month roadmap for making the desktop client fully accessible, with audit baselines, component ownership, keyboard milestones, screen-reader testing, and release gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.81,"slice":"core","lang":"en"} -{"prompt":"Implement a bounded work-stealing scheduler for the image transcoder and expose queue-depth metrics per priority.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"en"} -{"prompt":"Create the tvOS episode details screen with parallax artwork, focus transitions, metadata, and a prominent resume action.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"make it work like before","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.56,"slice":"vague-eval","lang":"en"} -{"prompt":"Extract the SQL statement builder from `Repository` and remove duplicate placeholder logic, with generated queries and observable behavior unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"Identify why the new WebSocket client leaks goroutines during reconnect storms, implement the correction after confirming the ownership bug, and document the lifecycle invariant near the relevant package.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.82,"slice":"mixed","lang":"en"} -{"prompt":"Review the new authentication proposal for replay resistance, downgrade paths, key rotation, and recovery risks. Return written findings only, not an alternative implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.78,"slice":"boundary","lang":"en"} -{"prompt":"Debug the blank first frame in our Vulkan renderer; it appears only with triple buffering and validation layers report no errors.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"Document the binary cache file format, including header fields, alignment, checksums, version negotiation, and forward-compatible readers.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.51,"slice":"core","lang":"en"} -{"prompt":"Existing cleanup proposal:\n\n```text\npackages:\n- `core/http`: owns client, retries, auth, JSON helpers\n- `core/sync`: imports http internals for retry classification\n- `features/export`: imports both packages and duplicates error mapping\n- `features/import`: has a second JSON helper with different date handling\n\nDesired boundaries:\n- transport has no feature imports\n- sync decides retry policy through a public error category\n- generated API types remain where they are\n- package exports must not break downstream plugins\n- bundle size must not grow\n- no runtime behavior changes in this effort\n\nCandidate moves:\n1. extract `core/transport`\n2. move error taxonomy to `core/contracts`\n3. consolidate JSON helper later\n```\n\nCarry out the structural cleanup across the TypeScript workspace, preserving exports, serialization, retry decisions, and test behavior. Do not fold in feature changes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Center the empty-state illustration on iPad","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.13,"slice":"core","lang":"en"} -{"prompt":"Redesign the settings screen and update its UI testing guide. Implement searchable sections, deep-link highlighting, responsive columns, and VoiceOver order, then document stable identifiers and navigation patterns for test authors.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.73,"slice":"mixed","lang":"en"} -{"prompt":"Break down a transition from per-service databases to a shared analytical event lake, with ownership rules, schema evolution, replay, privacy deletion, cost controls, and quarterly milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"boundary","lang":"en"} -{"prompt":"Add optimistic concurrency to document updates using weak ETags and return the current representation on conflict.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Write a README for the new `packet-inspect` CLI, covering installation, capture filters, JSON output, privileges, and examples.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"Move all clock access in the scheduler behind the existing `Clock` protocol without changing timing behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.53,"slice":"core","lang":"en"} -{"prompt":"Investigate why a seemingly valid migration deadlocks with the live cleanup worker but succeeds when run during maintenance.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.79,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed download URLs with tenant-scoped keys, maximum lifetimes, revocation, and an audit record.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Disable the obsolete `legacySearch` experiment","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Build a multiplayer lobby browser with region tabs, latency indicators, filters, controller navigation, and an animated join state.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Arregla el padding del botón flotante: debe usar `space-400` en vez de `space-300`, sin tocar su posición ni animación.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.11,"slice":"boundary","lang":"es"} -{"prompt":"Read the existing Raft snapshot installation path and tell me how it handles an interrupted transfer, stale terms, and checksum failures. No modifications.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Simplify the permissions package by consolidating role expansion, while also writing a design note for the proposed follow-up move to attribute-based access control. Runtime authorization must stay identical in this change.","purpose":"refactor","secondary":"planning","mixed":true,"difficulty":0.74,"slice":"mixed","lang":"en"} -{"prompt":"Prepare an architecture plan for serving ML embeddings from multiple model versions, including routing, warmup, cache keys, rollback, GPU capacity, and result reproducibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"core","lang":"en"} -{"prompt":"Implement a PostgreSQL logical-replication consumer that checkpoints LSNs and tolerates duplicate change records after restart.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.85,"slice":"boundary","lang":"en"} -{"prompt":"Refresh the web audio recorder with a live waveform, permission states, elapsed time, discard confirmation, and reduced-motion support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Pin Rust to 1.90.0 in `rust-toolchain.toml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Decouple protobuf decoding from `TelemetryReceiver` and preserve accepted messages, rejection reasons, and metric labels exactly.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Customer report and traces:\n\n```text\nDevice: Pixel 10, Android 16\nApp: 9.2.0 production\nSteps: open Downloads, enable airplane mode, tap a completed item\nExpected: local playback\nActual: spinner forever\n\nPlayerState: source=LOCAL status=PREPARING\nMediaStore lookup: content://media/external/video/media/812\nopenFileDescriptor: success fd=94\nDRM session: requesting license url=https://license.example/v2\nConnectivity: NONE\nOfflineLicenseStore lookup asset=mv_728 result=HIT expires=2026-08-12\nPlayerState after 60s: PREPARING\n```\n\nOffline playback worked in 9.1. Determine why a network license request still starts despite the stored offline license and which state transition leaves the player spinning rather than surfacing an error.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.76,"slice":"pasted-context","lang":"en"} -{"prompt":"Summarize the existing OAuth callback implementation for a security review, including state validation, PKCE, cookie handling, and redirect allowlisting.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"boundary","lang":"en"} -{"prompt":"Evaluate `Cache::get_or_insert` for deadlocks and duplicate computation under concurrent misses. Explain concrete interleavings from the current Rust code; no edits requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Plan and implement encrypted local backups for the desktop app. First settle key derivation, key storage, archive format, corruption detection, rotation, recovery, compatibility, and rollout. Then build export/import flows and tests using the approved design, with planning treated as the primary outcome.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.95,"slice":"mixed","lang":"en"} -{"prompt":"Design the retirement path for our v1 GraphQL schema, covering field usage telemetry, persisted queries, mobile release lag, deprecation messaging, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.83,"slice":"core","lang":"en"} -{"prompt":"Implement per-tenant concurrency limits in the job runner without allowing a busy tenant to block others.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Create a SwiftUI subscription paywall with monthly/yearly options, trial messaging, StoreKit loading and error states, legal links, and dynamic type.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"update that config","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.21,"slice":"vague-eval","lang":"en"} -{"prompt":"Rename `Blacklist` to `Blocklist` throughout code, database identifiers, metrics, and public SDK symbols while maintaining compatibility aliases and unchanged enforcement behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"Analyze the sporadic incorrect totals in the revenue dashboard, identify whether late events, currency conversion, or materialized-view refresh is responsible, then implement the verified correction and add a regression test.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.86,"slice":"mixed","lang":"en"} -{"prompt":"Explain the proposed `Lease V2` design's safety properties and compare them with the existing implementation. Return review findings and open questions only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"Trace why our Python worker acknowledges some Celery tasks before the database transaction commits, causing rare lost updates after process termination.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"Write a migration guide from SDK 2.x callbacks to SDK 3.x async iterators, with before-and-after examples and cancellation notes.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Ticket imported from Jira:\n\n```text\nINFRA-2201: rotate internal service certificates without restarts\nToday:\n- cert-manager writes PEM files into projected volumes\n- Go services read certificates only during startup\n- Envoy sidecars reload automatically\n- some JVM services use JKS copied by an init container\nRequirements:\n- rotation completes before the old certificate's final 12 hours\n- connections using the old cert may drain for 10 minutes\n- rollback to previous material within 5 minutes\n- alert on stale serial number per instance\n- no coordinated fleet restart\nQuestions: shared reload library or service-specific hooks? How do JVM stores update atomically?\n```\n\nProduce a cross-language rollout design and milestone plan. Include file watching, atomic replacement, connection draining, observability, canaries, rollback, and ownership; do not implement it.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Apply the new color tokens to the desktop sidebar and ensure selected, hovered, inactive, and high-contrast states remain distinct.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"Add the export worker described in `ADR-42`, then update the operator runbook with queue controls, expected metrics, replay steps, and failure modes.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.78,"slice":"mixed","lang":"en"} -{"prompt":"Lay out the design for a privacy-safe analytics pipeline on mobile, including consent state, local buffering, event schemas, deletion, sampling, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"boundary","lang":"en"} +{"prompt":"Failure captured from an ESP32 test rig:\n\n```text\nboot: reset_reason=RTC_WDT\nsensor task started stack=4096\nwifi connected rssi=-61\nsample #18431 adc=2178\nsample #18432 adc=2180\nE queue: send timeout depth=64\nW uploader: retry in 2000ms\nE queue: send timeout depth=64\nGuru Meditation Error: Core 1 panic'ed (LoadProhibited)\nEXCVADDR: 0x00000014\nBacktrace: 0x400d91fe:0x3ffd2c20 0x400d4a77:0x3ffd2c50 0x400d51c1:0x3ffd2c80\n```\n\nThe panic occurs only after Wi-Fi drops for several minutes while sampling continues. Decode the likely failing path using the map file and determine whether queue saturation, a stale upload buffer, or watchdog recovery leads to the invalid load.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Explain why the serializer writes map keys in lexical order even though MessagePack permits arbitrary ordering. Base the answer on existing tests and compatibility code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Prepare an API guide for the existing batch-inference endpoint with request limits, NDJSON examples, streaming responses, cancellation, and error handling.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Plan the new plugin sandbox and then implement its capability checks. The design must cover filesystem scopes, outbound network policy, process spawning, audit logs, backward compatibility, and escape testing; after reviewable design notes, add the Rust enforcement layer and adversarial tests.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":1.0,"slice":"mixed","lang":"en"} +{"prompt":"Outline a six-month roadmap for making the desktop client fully accessible, with audit baselines, component ownership, keyboard milestones, screen-reader testing, and release gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement a bounded work-stealing scheduler for the image transcoder and expose queue-depth metrics per priority.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create the tvOS episode details screen with parallax artwork, focus transitions, metadata, and a prominent resume action.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"make it work like before","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Extract the SQL statement builder from `Repository` and remove duplicate placeholder logic, with generated queries and observable behavior unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Identify why the new WebSocket client leaks goroutines during reconnect storms, implement the correction after confirming the ownership bug, and document the lifecycle invariant near the relevant package.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Review the new authentication proposal for replay resistance, downgrade paths, key rotation, and recovery risks. Return written findings only, not an alternative implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Debug the blank first frame in our Vulkan renderer; it appears only with triple buffering and validation layers report no errors.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Document the binary cache file format, including header fields, alignment, checksums, version negotiation, and forward-compatible readers.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Existing cleanup proposal:\n\n```text\npackages:\n- `core/http`: owns client, retries, auth, JSON helpers\n- `core/sync`: imports http internals for retry classification\n- `features/export`: imports both packages and duplicates error mapping\n- `features/import`: has a second JSON helper with different date handling\n\nDesired boundaries:\n- transport has no feature imports\n- sync decides retry policy through a public error category\n- generated API types remain where they are\n- package exports must not break downstream plugins\n- bundle size must not grow\n- no runtime behavior changes in this effort\n\nCandidate moves:\n1. extract `core/transport`\n2. move error taxonomy to `core/contracts`\n3. consolidate JSON helper later\n```\n\nCarry out the structural cleanup across the TypeScript workspace, preserving exports, serialization, retry decisions, and test behavior. Do not fold in feature changes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Center the empty-state illustration on iPad","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Redesign the settings screen and update its UI testing guide. Implement searchable sections, deep-link highlighting, responsive columns, and VoiceOver order, then document stable identifiers and navigation patterns for test authors.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Break down a transition from per-service databases to a shared analytical event lake, with ownership rules, schema evolution, replay, privacy deletion, cost controls, and quarterly milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add optimistic concurrency to document updates using weak ETags and return the current representation on conflict.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Write a README for the new `packet-inspect` CLI, covering installation, capture filters, JSON output, privileges, and examples.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Move all clock access in the scheduler behind the existing `Clock` protocol without changing timing behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why a seemingly valid migration deadlocks with the live cleanup worker but succeeds when run during maintenance.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement signed download URLs with tenant-scoped keys, maximum lifetimes, revocation, and an audit record.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Disable the obsolete `legacySearch` experiment","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Build a multiplayer lobby browser with region tabs, latency indicators, filters, controller navigation, and an animated join state.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Arregla el padding del botón flotante: debe usar `space-400` en vez de `space-300`, sin tocar su posición ni animación.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"es"} +{"prompt":"Read the existing Raft snapshot installation path and tell me how it handles an interrupted transfer, stale terms, and checksum failures. No modifications.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Simplify the permissions package by consolidating role expansion, while also writing a design note for the proposed follow-up move to attribute-based access control. Runtime authorization must stay identical in this change.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Prepare an architecture plan for serving ML embeddings from multiple model versions, including routing, warmup, cache keys, rollback, GPU capacity, and result reproducibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement a PostgreSQL logical-replication consumer that checkpoints LSNs and tolerates duplicate change records after restart.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Refresh the web audio recorder with a live waveform, permission states, elapsed time, discard confirmation, and reduced-motion support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Pin Rust to 1.90.0 in `rust-toolchain.toml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Decouple protobuf decoding from `TelemetryReceiver` and preserve accepted messages, rejection reasons, and metric labels exactly.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Customer report and traces:\n\n```text\nDevice: Pixel 10, Android 16\nApp: 9.2.0 production\nSteps: open Downloads, enable airplane mode, tap a completed item\nExpected: local playback\nActual: spinner forever\n\nPlayerState: source=LOCAL status=PREPARING\nMediaStore lookup: content://media/external/video/media/812\nopenFileDescriptor: success fd=94\nDRM session: requesting license url=https://license.example/v2\nConnectivity: NONE\nOfflineLicenseStore lookup asset=mv_728 result=HIT expires=2026-08-12\nPlayerState after 60s: PREPARING\n```\n\nOffline playback worked in 9.1. Determine why a network license request still starts despite the stored offline license and which state transition leaves the player spinning rather than surfacing an error.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Summarize the existing OAuth callback implementation for a security review, including state validation, PKCE, cookie handling, and redirect allowlisting.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Evaluate `Cache::get_or_insert` for deadlocks and duplicate computation under concurrent misses. Explain concrete interleavings from the current Rust code; no edits requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Plan and implement encrypted local backups for the desktop app. First settle key derivation, key storage, archive format, corruption detection, rotation, recovery, compatibility, and rollout. Then build export/import flows and tests using the approved design, with planning treated as the primary outcome.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":1,"slice":"mixed","lang":"en"} +{"prompt":"Design the retirement path for our v1 GraphQL schema, covering field usage telemetry, persisted queries, mobile release lag, deprecation messaging, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement per-tenant concurrency limits in the job runner without allowing a busy tenant to block others.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create a SwiftUI subscription paywall with monthly/yearly options, trial messaging, StoreKit loading and error states, legal links, and dynamic type.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Rename `Blacklist` to `Blocklist` throughout code, database identifiers, metrics, and public SDK symbols while maintaining compatibility aliases and unchanged enforcement behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Analyze the sporadic incorrect totals in the revenue dashboard, identify whether late events, currency conversion, or materialized-view refresh is responsible, then implement the verified correction and add a regression test.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Explain the proposed `Lease V2` design's safety properties and compare them with the existing implementation. Return review findings and open questions only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Trace why our Python worker acknowledges some Celery tasks before the database transaction commits, causing rare lost updates after process termination.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write a migration guide from SDK 2.x callbacks to SDK 3.x async iterators, with before-and-after examples and cancellation notes.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Ticket imported from Jira:\n\n```text\nINFRA-2201: rotate internal service certificates without restarts\nToday:\n- cert-manager writes PEM files into projected volumes\n- Go services read certificates only during startup\n- Envoy sidecars reload automatically\n- some JVM services use JKS copied by an init container\nRequirements:\n- rotation completes before the old certificate's final 12 hours\n- connections using the old cert may drain for 10 minutes\n- rollback to previous material within 5 minutes\n- alert on stale serial number per instance\n- no coordinated fleet restart\nQuestions: shared reload library or service-specific hooks? How do JVM stores update atomically?\n```\n\nProduce a cross-language rollout design and milestone plan. Include file watching, atomic replacement, connection draining, observability, canaries, rollback, and ownership; do not implement it.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Apply the new color tokens to the desktop sidebar and ensure selected, hovered, inactive, and high-contrast states remain distinct.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Add the export worker described in `ADR-42`, then update the operator runbook with queue controls, expected metrics, replay steps, and failure modes.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Lay out the design for a privacy-safe analytics pipeline on mobile, including consent state, local buffering, event schemas, deletion, sampling, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Build a streaming JSON tokenizer that reports byte offsets and handles tokens split across arbitrary input chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Draft the pull request summary for the existing database failover work, emphasizing operational behavior, test evidence, and rollback.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Extract shared zoom and pan math from the macOS and iPad canvases without changing gesture feel or coordinate rounding.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Why are users seeing a 403 only on the second page of search results? The cause is unknown; investigate the signed continuation token and gateway logs.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Implement time-windowed deduplication for telemetry packets received through both Wi-Fi and LoRa gateways.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Bump the chart app version to `2.7.1`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Design the React Native delivery-tracking screen with a live route, status timeline, courier card, offline banner, and accessible map alternatives.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Aktualisiere in `docker-compose.yml` nur das Postgres-Image von `17.4` auf `17.5`. Sonst nichts ändern.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"boundary","lang":"de"} -{"prompt":"Assess the current backup restore code for path traversal, symlink handling, decompression bombs, and partial-write cleanup. Report findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"Create the API key usage endpoint and then write its reference docs. Include daily aggregation, pagination, retention boundaries, authorization tests, response examples, and the meaning of delayed usage data.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Plan a zero-downtime move from RabbitMQ classic queues to quorum queues, covering ordering, dead lettering, capacity, producer compatibility, canaries, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"core","lang":"en"} -{"prompt":"Add a subcommand that verifies Sigstore bundles offline using a supplied trust root and emits machine-readable results.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Build the AR object-placement coaching overlay with plane guidance, tracking-loss feedback, placement reticle, and reduced-motion fallback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"make the docs decent","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.34,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace repeated service-name strings with the existing `ServiceID` type across the monorepo. Preserve serialization and public values exactly.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} +{"prompt":"Extract shared zoom and pan math from the macOS and iPad canvases without changing gesture feel or coordinate rounding.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Why are users seeing a 403 only on the second page of search results? The cause is unknown; investigate the signed continuation token and gateway logs.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Implement time-windowed deduplication for telemetry packets received through both Wi-Fi and LoRa gateways.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Bump the chart app version to `2.7.1`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Design the React Native delivery-tracking screen with a live route, status timeline, courier card, offline banner, and accessible map alternatives.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Aktualisiere in `docker-compose.yml` nur das Postgres-Image von `17.4` auf `17.5`. Sonst nichts ändern.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"de"} +{"prompt":"Assess the current backup restore code for path traversal, symlink handling, decompression bombs, and partial-write cleanup. Report findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the API key usage endpoint and then write its reference docs. Include daily aggregation, pagination, retention boundaries, authorization tests, response examples, and the meaning of delayed usage data.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan a zero-downtime move from RabbitMQ classic queues to quorum queues, covering ordering, dead lettering, capacity, producer compatibility, canaries, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add a subcommand that verifies Sigstore bundles offline using a supplied trust root and emits machine-readable results.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Build the AR object-placement coaching overlay with plane guidance, tracking-loss feedback, placement reticle, and reduced-motion fallback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"make the docs decent","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace repeated service-name strings with the existing `ServiceID` type across the monorepo. Preserve serialization and public values exactly.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Determine why scheduled reports sometimes run twice around daylight-saving transitions, implement a fix after proving the time-zone assumption, and add a short operator note about skipped or repeated local times.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Read `AuthorizationPolicy.evaluate` and explain whether a deny rule always overrides inherited grants. No failing behavior has been reported and no changes are requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.47,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why the Linux agent stops forwarding logs after its journald cursor file is truncated.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Produce a concise architecture overview of the current notification platform for new engineers, based on the repository and deployment manifests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.49,"slice":"core","lang":"en"} -{"prompt":"Review packet from the risk team:\n\n```text\nChange: new endpoint `POST /v2/payouts/{id}/approve`\nCaller: operations web app through API gateway\nAuthorization proposal: `payout:approve` scope plus operator role\nRequest includes expected payout version and an optional note\nResponse can be 202, 409, 422\nApproval enqueues execution immediately\nAudit event currently stores operator ID and payout ID, not before/after values\nNo dual control below $10,000\nGateway retries POST once on upstream reset\nOpen questions: replay protection, compromised operator session, note sensitivity, threshold configuration\n```\n\nPerform a security and correctness review of the proposed flow. Identify replay, authorization, audit, concurrency, and retry risks, and state what evidence or design changes are needed. Do not implement anything.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.83,"slice":"pasted-context","lang":"en"} -{"prompt":"Align the tooltip arrow with its anchor","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.12,"slice":"core","lang":"en"} -{"prompt":"Plan the permissions editor and implement its UI after defining interaction rules. Cover inherited versus direct grants, bulk changes, unsaved navigation, large role lists, keyboard access, error recovery, and an incremental rollout behind `rbacEditorV2`.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.84,"slice":"mixed","lang":"en"} -{"prompt":"Propose a migration design for replacing cron-based billing jobs with event-driven workflows, including correctness invariants, replay, backfills, ownership, and staged cutover.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"boundary","lang":"en"} -{"prompt":"Implement row-level security policies for project records and update the connection pool to set tenant context safely.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Document why the cache uses stale-while-revalidate for entitlement checks and describe its bounded inconsistency window.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"Split the 2,000-line `AppCoordinator` into feature coordinators while preserving deep links, restoration, and navigation behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Find why the admin UI renders old feature-flag values after a successful save even though a hard refresh shows the update.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Implement adaptive bitrate selection for the audio streamer using buffer health, throughput samples, and hysteresis.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Change the default locale to `en-GB`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"Create the kiosk check-in flow with large touch targets, language selection, badge scanning, timeout warnings, and a privacy reset between visitors.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Corrige apenas `dependancies` para `dependencies` no README.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"pt"} -{"prompt":"Explain what guarantees `WriteBatch.commit()` provides if fsync succeeds for the log but updating the manifest fails. Review existing recovery code only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Refine the visual diff viewer and document its keyboard controls. Add synchronized scrolling, intraline highlights, collapsed unchanged regions, high-contrast colors, and a guide for navigation and copying hunks.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} +{"prompt":"Read `AuthorizationPolicy.evaluate` and explain whether a deny rule always overrides inherited grants. No failing behavior has been reported and no changes are requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Investigate why the Linux agent stops forwarding logs after its journald cursor file is truncated.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Produce a concise architecture overview of the current notification platform for new engineers, based on the repository and deployment manifests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Review packet from the risk team:\n\n```text\nChange: new endpoint `POST /v2/payouts/{id}/approve`\nCaller: operations web app through API gateway\nAuthorization proposal: `payout:approve` scope plus operator role\nRequest includes expected payout version and an optional note\nResponse can be 202, 409, 422\nApproval enqueues execution immediately\nAudit event currently stores operator ID and payout ID, not before/after values\nNo dual control below $10,000\nGateway retries POST once on upstream reset\nOpen questions: replay protection, compromised operator session, note sensitivity, threshold configuration\n```\n\nPerform a security and correctness review of the proposed flow. Identify replay, authorization, audit, concurrency, and retry risks, and state what evidence or design changes are needed. Do not implement anything.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Align the tooltip arrow with its anchor","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Plan the permissions editor and implement its UI after defining interaction rules. Cover inherited versus direct grants, bulk changes, unsaved navigation, large role lists, keyboard access, error recovery, and an incremental rollout behind `rbacEditorV2`.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Propose a migration design for replacing cron-based billing jobs with event-driven workflows, including correctness invariants, replay, backfills, ownership, and staged cutover.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement row-level security policies for project records and update the connection pool to set tenant context safely.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Document why the cache uses stale-while-revalidate for entitlement checks and describe its bounded inconsistency window.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Split the 2,000-line `AppCoordinator` into feature coordinators while preserving deep links, restoration, and navigation behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Find why the admin UI renders old feature-flag values after a successful save even though a hard refresh shows the update.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Implement adaptive bitrate selection for the audio streamer using buffer health, throughput samples, and hysteresis.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Change the default locale to `en-GB`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Create the kiosk check-in flow with large touch targets, language selection, badge scanning, timeout warnings, and a privacy reset between visitors.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Corrige apenas `dependancies` para `dependencies` no README.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"pt"} +{"prompt":"Explain what guarantees `WriteBatch.commit()` provides if fsync succeeds for the log but updating the manifest fails. Review existing recovery code only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Refine the visual diff viewer and document its keyboard controls. Add synchronized scrolling, intraline highlights, collapsed unchanged regions, high-contrast colors, and a guide for navigation and copying hunks.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Write an adoption roadmap for passkeys across web, iOS, and Android, including account recovery, device loss, progressive enrollment, legacy login, support readiness, and risk gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Add server-side filtering by status and owner to the deployments endpoint, with stable ordering and query validation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.48,"slice":"core","lang":"en"} +{"prompt":"Add server-side filtering by status and owner to the deployments endpoint, with stable ordering and query validation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Build a macOS inspector panel for selected vector layers with editable geometry, constraints, blend mode, and undo-aware controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Consolidate `LegacyDateParser` and `IsoDateParser` behind one strategy interface, retaining every accepted format and error message.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"Consolidate `LegacyDateParser` and `IsoDateParser` behind one strategy interface, retaining every accepted format and error message.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Investigate the flaky iOS background-upload cancellation, fix the proven race, and update the troubleshooting guide with the observable symptoms and diagnostic logs support should collect.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Summarize the current database connection lifecycle for the operations handbook, using pool initialization, request middleware, and shutdown code as evidence.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"boundary","lang":"en"} -{"prompt":"Track down why our Redis Lua script occasionally returns a negative remaining quota under concurrent requests.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} +{"prompt":"Summarize the current database connection lifecycle for the operations handbook, using pool initialization, request middleware, and shutdown code as evidence.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down why our Redis Lua script occasionally returns a negative remaining quota under concurrent requests.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Create a glossary for the domain terms used in the claims engine, based on models, validation messages, and existing ADRs.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Pasted design and code excerpt:\n\n```text\nClaim lifecycle: pending -> owned -> completed | abandoned\nLease duration: 30s\nHeartbeat: every 10s\n```\n\n```go\nfunc (q *Queue) Heartbeat(ctx context.Context, id, worker string) error {\n res, err := q.db.ExecContext(ctx, `\n UPDATE jobs SET lease_until = now() + interval '30 seconds'\n WHERE id = $1 AND owner = $2 AND state = 'owned'`, id, worker)\n if err != nil { return err }\n n, _ := res.RowsAffected()\n if n == 0 { return ErrLeaseLost }\n return nil\n}\n\nfunc (q *Queue) Complete(ctx context.Context, id string) error {\n _, err := q.db.ExecContext(ctx,\n `UPDATE jobs SET state='completed' WHERE id=$1`, id)\n return err\n}\n```\n\nReview whether a worker that lost and later regained connectivity can complete work now owned by another worker. Explain the exact race and any missing fencing checks, but do not change code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"pasted-context","lang":"en"} -{"prompt":"Use `radius-lg` instead of `12px` on the alert card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"Implement organization deletion and write the customer-facing data-removal note. The backend must coordinate soft deletion, retention holds, object storage cleanup, search-index erasure, retries, and audit records; the note should accurately state timing and exceptions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.89,"slice":"mixed","lang":"en"} -{"prompt":"Define an architecture and milestone plan for moving the game simulation from a single authoritative process to regional shards without breaking deterministic replays.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"boundary","lang":"en"} -{"prompt":"Implement a DNS-over-HTTPS resolver cache with TTL clamping, negative caching, request coalescing, and cancellation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"Écris une page de dépannage pour les échecs de synchronisation hors ligne, avec les logs à collecter, les causes connues et les étapes de récupération.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"fr"} +{"prompt":"Pasted design and code excerpt:\n\n```text\nClaim lifecycle: pending -> owned -> completed | abandoned\nLease duration: 30s\nHeartbeat: every 10s\n```\n\n```go\nfunc (q *Queue) Heartbeat(ctx context.Context, id, worker string) error {\n res, err := q.db.ExecContext(ctx, `\n UPDATE jobs SET lease_until = now() + interval '30 seconds'\n WHERE id = $1 AND owner = $2 AND state = 'owned'`, id, worker)\n if err != nil { return err }\n n, _ := res.RowsAffected()\n if n == 0 { return ErrLeaseLost }\n return nil\n}\n\nfunc (q *Queue) Complete(ctx context.Context, id string) error {\n _, err := q.db.ExecContext(ctx,\n `UPDATE jobs SET state='completed' WHERE id=$1`, id)\n return err\n}\n```\n\nReview whether a worker that lost and later regained connectivity can complete work now owned by another worker. Explain the exact race and any missing fencing checks, but do not change code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"Use `radius-lg` instead of `12px` on the alert card","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Implement organization deletion and write the customer-facing data-removal note. The backend must coordinate soft deletion, retention holds, object storage cleanup, search-index erasure, retries, and audit records; the note should accurately state timing and exceptions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Define an architecture and milestone plan for moving the game simulation from a single authoritative process to regional shards without breaking deterministic replays.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement a DNS-over-HTTPS resolver cache with TTL clamping, negative caching, request coalescing, and cancellation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Écris une page de dépannage pour les échecs de synchronisation hors ligne, avec les logs à collecter, les causes connues et les étapes de récupération.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"fr"} {"prompt":"Reorganize the Gradle convention plugins by concern and preserve every applied compiler option, dependency constraint, and published plugin ID.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Determine why `useSearchResults` issues three requests on initial render after React 19 migration; the intended source is not known yet.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"Add a SQLite-backed cache to the geocoder CLI with expiry, size limits, and a `cache clear` command.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.56,"slice":"core","lang":"en"} -{"prompt":"Delete the unused trailing slash in `PUBLIC_URL`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"core","lang":"en"} -{"prompt":"Implement the tablet inventory grid with barcode focus mode, sortable columns, stock warnings, and keyboard selection.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Remplace `colourGray700` par `colorGray700` uniquement dans le nouveau fichier de thème; ne fais pas de renommage global.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"boundary","lang":"fr"} -{"prompt":"Inspect the current OpenTelemetry setup and explain where trace context is lost between the HTTP handler, Kafka producer, and consumer. Do not modify instrumentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Build the accessibility settings panel and produce a short testing checklist. Include text scaling preview, contrast choices, motion reduction, screen-reader labels, persisted preferences, and manual verification steps.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.67,"slice":"mixed","lang":"en"} -{"prompt":"Lay out a disaster-recovery strategy for the artifact registry, including RPO/RTO tiers, cross-region replication, metadata reconstruction, restore drills, and failure ownership.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"core","lang":"en"} -{"prompt":"Implement certificate transparency log ingestion with checkpoint verification, batch persistence, and safe recovery after a partial tree update.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.86,"slice":"core","lang":"en"} -{"prompt":"Refresh the desktop activity feed with grouped dates, virtualized rows, live updates, and a stable scroll position when new items arrive.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"continue yesterday's architecture","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"Move retry classification out of the HTTP client into `RetryPolicy` while keeping attempt counts, delays, exceptions, and logs unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.64,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose the slow first query after every PostgreSQL failover, implement a correction once the connection or plan-cache cause is established, and write a brief runbook note for identifying the condition.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.86,"slice":"mixed","lang":"en"} -{"prompt":"Explain the existing choice to keep protobuf unknown fields during command forwarding and assess its compatibility implications. No edits requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} -{"prompt":"Find out why SwiftData occasionally saves two copies of a newly created notebook when iCloud sync resumes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"Write a maintainers' guide to the release train, including branch cuts, schema freezes, mobile submission timing, hotfixes, and rollback communication.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"Notes attached to the review request:\n\n```text\nModule: `pricing/rules`\nPublic entry: `Evaluate(cart, customer, clock)`\nRule order currently comes from YAML\nRules may add adjustments or mark the cart ineligible\nA new `exclusive` flag stops later rules after a match\nDiscount totals are rounded after every rule\nTests cover one exclusive rule but not two overlapping exclusives\nCallers cache the compiled rule list for 15 minutes\nReload swaps an atomic pointer\nOpen questions:\n- can an exclusive eligibility rule suppress tax adjustments?\n- is YAML order part of the public contract?\n- what happens to in-flight evaluations during reload?\n```\n\nReview the current implementation and proposal. Explain ordering, rounding, exclusivity, reload consistency, and compatibility risks. Do not write code or rewrite the design.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"pasted-context","lang":"en"} -{"prompt":"Make the search field match the toolbar height","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.12,"slice":"core","lang":"en"} -{"prompt":"Implement SCIM group synchronization and write the administrator setup guide. Support pagination, incremental updates, member removals, idempotent retries, tenant isolation, and audit events; document credentials, expected propagation time, troubleshooting, and limitations.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.84,"slice":"mixed","lang":"en"} -{"prompt":"Prepare a design and phased roadmap for replacing polling with server-sent events in the operations console, without implementing it yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.75,"slice":"boundary","lang":"en"} -{"prompt":"Implement a B-tree page verifier that detects invalid child ranges, cycles, checksum errors, and unreachable pages.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.81,"slice":"core","lang":"en"} -{"prompt":"Rédige les notes de version pour la version 6.2 à partir de `CHANGELOG.d`, en séparant changements visibles, corrections et dépréciations.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.32,"slice":"core","lang":"fr"} -{"prompt":"Consolidate the two GraphQL error normalizers while retaining extension fields, ordering, and client-visible messages.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.51,"slice":"core","lang":"en"} -{"prompt":"Investigate why the CUDA batcher occasionally sends a tensor with shape `[0, 768]` after request cancellation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.76,"slice":"boundary","lang":"en"} +{"prompt":"Determine why `useSearchResults` issues three requests on initial render after React 19 migration; the intended source is not known yet.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add a SQLite-backed cache to the geocoder CLI with expiry, size limits, and a `cache clear` command.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Delete the unused trailing slash in `PUBLIC_URL`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Implement the tablet inventory grid with barcode focus mode, sortable columns, stock warnings, and keyboard selection.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Remplace `colourGray700` par `colorGray700` uniquement dans le nouveau fichier de thème; ne fais pas de renommage global.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"fr"} +{"prompt":"Inspect the current OpenTelemetry setup and explain where trace context is lost between the HTTP handler, Kafka producer, and consumer. Do not modify instrumentation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Build the accessibility settings panel and produce a short testing checklist. Include text scaling preview, contrast choices, motion reduction, screen-reader labels, persisted preferences, and manual verification steps.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Lay out a disaster-recovery strategy for the artifact registry, including RPO/RTO tiers, cross-region replication, metadata reconstruction, restore drills, and failure ownership.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement certificate transparency log ingestion with checkpoint verification, batch persistence, and safe recovery after a partial tree update.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Refresh the desktop activity feed with grouped dates, virtualized rows, live updates, and a stable scroll position when new items arrive.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Move retry classification out of the HTTP client into `RetryPolicy` while keeping attempt counts, delays, exceptions, and logs unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose the slow first query after every PostgreSQL failover, implement a correction once the connection or plan-cache cause is established, and write a brief runbook note for identifying the condition.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Explain the existing choice to keep protobuf unknown fields during command forwarding and assess its compatibility implications. No edits requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Find out why SwiftData occasionally saves two copies of a newly created notebook when iCloud sync resumes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write a maintainers' guide to the release train, including branch cuts, schema freezes, mobile submission timing, hotfixes, and rollback communication.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Notes attached to the review request:\n\n```text\nModule: `pricing/rules`\nPublic entry: `Evaluate(cart, customer, clock)`\nRule order currently comes from YAML\nRules may add adjustments or mark the cart ineligible\nA new `exclusive` flag stops later rules after a match\nDiscount totals are rounded after every rule\nTests cover one exclusive rule but not two overlapping exclusives\nCallers cache the compiled rule list for 15 minutes\nReload swaps an atomic pointer\nOpen questions:\n- can an exclusive eligibility rule suppress tax adjustments?\n- is YAML order part of the public contract?\n- what happens to in-flight evaluations during reload?\n```\n\nReview the current implementation and proposal. Explain ordering, rounding, exclusivity, reload consistency, and compatibility risks. Do not write code or rewrite the design.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Make the search field match the toolbar height","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Implement SCIM group synchronization and write the administrator setup guide. Support pagination, incremental updates, member removals, idempotent retries, tenant isolation, and audit events; document credentials, expected propagation time, troubleshooting, and limitations.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Prepare a design and phased roadmap for replacing polling with server-sent events in the operations console, without implementing it yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement a B-tree page verifier that detects invalid child ranges, cycles, checksum errors, and unreachable pages.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Rédige les notes de version pour la version 6.2 à partir de `CHANGELOG.d`, en séparant changements visibles, corrections et dépréciations.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"fr"} +{"prompt":"Consolidate the two GraphQL error normalizers while retaining extension fields, ordering, and client-visible messages.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why the CUDA batcher occasionally sends a tensor with shape `[0, 768]` after request cancellation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Add chunked uploads to the artifact CLI with checksum verification, resume tokens, and concurrent part limits.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Set the docs site port to 4321","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"core","lang":"en"} -{"prompt":"Build the web-based query plan viewer with expandable nodes, cost heatmaps, pan and zoom, search, and accessible text equivalents.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Troca somente `cacheTtl: 300` para `cacheTtl: 600` em `config/production.yml`; não altere os outros ambientes.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"boundary","lang":"pt"} -{"prompt":"Walk through the current firmware update state machine and explain how it recovers from power loss during each flash-bank transition.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Finish the analytics dashboard visuals and produce a short metric-definition appendix. Implement comparison ranges, drill-down drawers, responsive charts, empty states, and color-safe series; document exactly how each displayed KPI is computed.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Design a shared feature-store architecture for fraud, ranking, and support models. Cover offline/online consistency, feature ownership, point-in-time correctness, freshness tiers, backfills, schema evolution, regional availability, and a phased migration from team-owned Redis tables. Deliver an architecture proposal only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"core","lang":"en"} -{"prompt":"Outline the rollout for signed OTA firmware updates across 180,000 intermittently connected devices. Include key rotation, staged cohorts, downgrade protection, interrupted flashes, health gates, and recovery through the factory image; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"boundary","lang":"en"} -{"prompt":"Add zstd support to the trace ingester","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Inference incident excerpt:\n\n```text\nmodel=churn-v17 runtime=onnxruntime-gpu\nbatch=128 input_checksum=69f204\nnode-a output_checksum=5c1ab8 top1=retain score=0.5031\nnode-b output_checksum=b70de2 top1=churn score=0.5028\nnode-a gpu=A10 driver=580.65 cuda=13.0\nnode-b gpu=L4 driver=580.65 cuda=13.0\npreprocessor image=features:2026.07.28\nORT graph optimization=all\nTensor `account_age_days`: min=-1 max=4412 dtype=float32\nTensor `recent_sessions`: min=0 max=32767 dtype=int16\nWARNING Cast_91 saturating conversion differs from reference evaluator\n```\n\nBoth nodes use the same model artifact and input checksum, but about 0.4% of borderline predictions disagree. Determine whether preprocessing, numeric kernels, or graph optimization causes the divergence and identify what evidence would isolate it.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Build the in-game squad HUD with health rings, voice activity, status effects, controller focus, and a compact spectator variant.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Plan and implement a short-lived credential broker for CI jobs. Begin with a design covering workload identity, policy evaluation, token lifetimes, audit trails, revocation, regional failure, and migration from static repository secrets. After the design is reviewable, add the Go service, Kubernetes authentication, provider adapters, metrics, and integration tests. Treat the security model and rollout plan as the primary outcome.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.96,"slice":"mixed","lang":"en"} -{"prompt":"Set `shuffle_buffer` to 50000","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Separate feature extraction from model invocation in `ScoringPipeline` while preserving tensor names, batching, timeouts, metrics, and prediction output exactly.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Expose the active model metadata at `/internal/model-info`, including artifact digest, feature-schema version, and load timestamp, with tests for the JSON contract.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.42,"slice":"boundary","lang":"en"} -{"prompt":"make the battle screen cooler","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.44,"slice":"vague-eval","lang":"en"} -{"prompt":"Find why the STM32 bootloader jumps into the application with an invalid stack pointer only after a watchdog reset.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Explain how `ShardPlanner` balances hot embeddings across GPU replicas and whether its scoring function can strand capacity. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Raw notes from the platform channel:\n\n```text\nTopic: model rollback procedure\nCurrent deployment: 10% shadow, 5% serving canary, then regional ramp\nArtifacts live in `ml-artifacts-prod`; manifests are signed\nRollback means switching the routing alias, not deleting the bad version\nFeature schema can advance independently, but only one version backward is guaranteed\nOnline cache entries include model version but not preprocessor digest\nDashboards: `Inference / Quality`, `Inference / Saturation`\nOn-call concern: quality labels arrive 4-12 hours late\nSupport concern: customers ask which predictions used the reverted version\nCompliance requires preserving decision lineage for 7 years\n```\n\nTurn this into an operator runbook for rolling back a model release. Include decision criteria, exact verification categories, delayed-label handling, cache considerations, lineage checks, and post-rollback communication.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.59,"slice":"pasted-context","lang":"en"} -{"prompt":"Nudge the minimap legend below the safe-area inset","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.14,"slice":"boundary","lang":"en"} -{"prompt":"Write the integration guide for publishing custom metrics through the edge agent, including supported types, label limits, buffering, retries, and sample configuration.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"Implement the dataset snapshot endpoint with filtering, signed download URLs, and retention enforcement, then document its request parameters, asynchronous states, examples, and failure responses for SDK authors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Map out a migration from Jenkins-hosted game builds to ephemeral Buildkite agents, covering asset caches, console SDK isolation, signing, capacity spikes, observability, and rollback milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"core","lang":"en"} -{"prompt":"Change `max_retrys` to `max_retries` in the unreleased config schema.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"boundary","lang":"en"} -{"prompt":"Implement deterministic replay files for the physics server with versioned inputs, checksums, and divergence reporting.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Polish the crafting inventory grid","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.31,"slice":"core","lang":"en"} -{"prompt":"Bump `prometheus-operator` to `v0.85.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"Rename `MasterNode` to `CoordinatorNode` across the scheduler, protobufs, dashboards, and tests while preserving wire compatibility and runtime behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.68,"slice":"boundary","lang":"en"} -{"prompt":"Split the monolithic `TrainingJobController` into validation, scheduling, status, and cleanup collaborators without changing its Kubernetes API behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Work item copied from the infrastructure backlog:\n\n```text\nNET-304 — reconcile BGP advertisements from Kubernetes Services\nInput: Services labeled `edge.example.com/advertise=true`\nOutput: prefixes announced through two route reflectors\nRules:\n- only LoadBalancer IPs from configured pools\n- withdraw within 20s after Service deletion\n- duplicate events are expected\n- retain last accepted router generation in Postgres\n- reject an update that would advertise more than 256 prefixes per tenant\n- dry-run mode emits proposed changes but touches no routers\n- expose reconcile duration, rejected prefix count, and router generation lag\nFailure policy: retry transient gRPC failures; configuration errors go to status conditions\n```\n\nImplement the controller, persistence, router client calls, status updates, limits, metrics, and integration tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.88,"slice":"pasted-context","lang":"en"} -{"prompt":"Investigate why Unreal Engine streaming levels intermittently remain invisible after their assets report loaded.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Create the GPU allocation heatmap and write a short legend explaining capacity, reservations, fragmentation, and unavailable devices. The view needs zoom, time-range selection, accessible values, and a useful empty state.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.67,"slice":"mixed","lang":"en"} -{"prompt":"Why does the telemetry collector quantize timestamps to 8-millisecond buckets? Explain the existing behavior from code and tests; nothing is broken.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"Draft a setup page for running the emulator farm locally with fake devices and a MinIO-backed artifact store.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"After moving the agent to cgroup v2, this integration test started hanging:\n\n```text\n=== RUN TestMemoryPressureTriggersEviction\nfixture: limit=256MiB high=192MiB\nworkload: allocated 220MiB\nmemory.events before: high 0 oom 0 oom_kill 0\nwaiting for watcher notification...\ncontext deadline exceeded after 45s\nmemory.current=230776832\nmemory.high=201326592\nmemory.events after: high 184 oom 0 oom_kill 0\nwatcher epoll fd=17 events=0\n```\n\nDetermine why the kernel counter changes without our watcher waking. I do not know whether the bug is event subscription, file descriptor setup, or an incorrect assumption carried over from cgroup v1.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.81,"slice":"boundary","lang":"en"} -{"prompt":"finish the controller stuff","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"Propose a storage design for petabyte-scale training checkpoints, including chunking, deduplication, consistency, lifecycle rules, regional recovery, and cost checkpoints.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"core","lang":"en"} -{"prompt":"Add support for loading GGUF tensor metadata without materializing tensor contents.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.56,"slice":"core","lang":"en"} -{"prompt":"Change request under review:\n\n```diff\n func selectReplica(key string, replicas []Replica) Replica {\n- return replicas[xxhash.Sum64String(key)%uint64(len(replicas))]\n+ best := replicas[0]\n+ bestScore := uint64(0)\n+ for _, r := range replicas {\n+ score := xxhash.Sum64String(key + r.ID)\n+ if score > bestScore {\n+ best, bestScore = r, score\n+ }\n+ }\n+ return best\n }\n```\n\nThe author says rendezvous hashing will reduce cache churn during scaling. Review this implementation for correctness, distribution, empty-input behavior, stable identifiers, and what happens when replica weights differ. Do not edit the patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.68,"slice":"pasted-context","lang":"en"} -{"prompt":"编写一份故障排查文档，说明 GPU worker 无法注册时要检查的证书、NVIDIA runtime、网络策略和日志。不要修改代码。","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"zh"} -{"prompt":"Build the spectator timeline with event markers, scrub previews, bookmarks, and controller-friendly navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Review the existing autoscaler decision code, explain its stabilization windows, and turn the explanation into an operator-facing page with worked scale-up and scale-down examples.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.62,"slice":"mixed","lang":"en"} -{"prompt":"Pin the base image digest in `worker.Dockerfile`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"把 `WorkerPool` 在整个仓库中改名为 `ExecutorPool`，包括文件名、测试和指标前缀；除了名称以外，行为必须保持不变。","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"zh"} -{"prompt":"Consolidate the CUDA capability checks used by the trainer and serving runtime without altering device eligibility.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Diagnose the missing final audio buffer","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.48,"slice":"core","lang":"en"} -{"prompt":"Explain how the rollout controller decides a canary is healthy when latency improves but the error budget worsens.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Write an API reference for the existing model-evaluation endpoint, including multipart uploads, metric selection, asynchronous status polling, limits, and result retention.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"boundary","lang":"en"} -{"prompt":"Plan a transition from mutable model tags to immutable content-addressed references. Cover registry compatibility, CI changes, cache behavior, lineage, rollout gates, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"en"} -{"prompt":"Backlog item:\n\n```text\nUI-771: fleet health overview\nHeader metrics: online, degraded, offline, updating\nMain chart: device count by state over selected range\nTable: fleet, firmware, last contact, health, rollout cohort\nFilters: region, hardware revision, firmware channel, customer\nScale: 250k rows total; server pagination already exists\nLive updates: websocket patches can arrive out of order\nResponsive: table becomes cards below 720px\nAccessibility: chart needs text summary; status cannot rely on color\nError states: stale data banner, socket reconnecting, initial load failure\nUse design tokens from `packages/fleet-theme`\n```\n\nImplement the dashboard views and interaction states. Do not change the fleet API.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Implement `/v1/models/{id}/card.md` by rendering stored model metadata and evaluation results into deterministic Markdown with caching.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"boundary","lang":"en"} -{"prompt":"Increase the watchdog threshold to 12 seconds","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"core","lang":"en"} -{"prompt":"Fix the clipped squad names and extract the shared truncation rule used by the lobby and scoreboard. Preserve all other layout behavior.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.38,"slice":"mixed","lang":"en"} -{"prompt":"Flatten the rule-evaluation branches into named stages without changing prediction scores or rejection reasons.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Corrige `enviroment` a `environment` solamente en `deploy/values-dev.yaml`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"es"} +{"prompt":"Set the docs site port to 4321","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the web-based query plan viewer with expandable nodes, cost heatmaps, pan and zoom, search, and accessible text equivalents.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Troca somente `cacheTtl: 300` para `cacheTtl: 600` em `config/production.yml`; não altere os outros ambientes.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"pt"} +{"prompt":"Walk through the current firmware update state machine and explain how it recovers from power loss during each flash-bank transition.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Finish the analytics dashboard visuals and produce a short metric-definition appendix. Implement comparison ranges, drill-down drawers, responsive charts, empty states, and color-safe series; document exactly how each displayed KPI is computed.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Design a shared feature-store architecture for fraud, ranking, and support models. Cover offline/online consistency, feature ownership, point-in-time correctness, freshness tiers, backfills, schema evolution, regional availability, and a phased migration from team-owned Redis tables. Deliver an architecture proposal only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Outline the rollout for signed OTA firmware updates across 180,000 intermittently connected devices. Include key rotation, staged cohorts, downgrade protection, interrupted flashes, health gates, and recovery through the factory image; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add zstd support to the trace ingester","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Inference incident excerpt:\n\n```text\nmodel=churn-v17 runtime=onnxruntime-gpu\nbatch=128 input_checksum=69f204\nnode-a output_checksum=5c1ab8 top1=retain score=0.5031\nnode-b output_checksum=b70de2 top1=churn score=0.5028\nnode-a gpu=A10 driver=580.65 cuda=13.0\nnode-b gpu=L4 driver=580.65 cuda=13.0\npreprocessor image=features:2026.07.28\nORT graph optimization=all\nTensor `account_age_days`: min=-1 max=4412 dtype=float32\nTensor `recent_sessions`: min=0 max=32767 dtype=int16\nWARNING Cast_91 saturating conversion differs from reference evaluator\n```\n\nBoth nodes use the same model artifact and input checksum, but about 0.4% of borderline predictions disagree. Determine whether preprocessing, numeric kernels, or graph optimization causes the divergence and identify what evidence would isolate it.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Build the in-game squad HUD with health rings, voice activity, status effects, controller focus, and a compact spectator variant.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Plan and implement a short-lived credential broker for CI jobs. Begin with a design covering workload identity, policy evaluation, token lifetimes, audit trails, revocation, regional failure, and migration from static repository secrets. After the design is reviewable, add the Go service, Kubernetes authentication, provider adapters, metrics, and integration tests. Treat the security model and rollout plan as the primary outcome.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":1,"slice":"mixed","lang":"en"} +{"prompt":"Set `shuffle_buffer` to 50000","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Separate feature extraction from model invocation in `ScoringPipeline` while preserving tensor names, batching, timeouts, metrics, and prediction output exactly.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Expose the active model metadata at `/internal/model-info`, including artifact digest, feature-schema version, and load timestamp, with tests for the JSON contract.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"make the battle screen cooler","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Find why the STM32 bootloader jumps into the application with an invalid stack pointer only after a watchdog reset.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Explain how `ShardPlanner` balances hot embeddings across GPU replicas and whether its scoring function can strand capacity. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Raw notes from the platform channel:\n\n```text\nTopic: model rollback procedure\nCurrent deployment: 10% shadow, 5% serving canary, then regional ramp\nArtifacts live in `ml-artifacts-prod`; manifests are signed\nRollback means switching the routing alias, not deleting the bad version\nFeature schema can advance independently, but only one version backward is guaranteed\nOnline cache entries include model version but not preprocessor digest\nDashboards: `Inference / Quality`, `Inference / Saturation`\nOn-call concern: quality labels arrive 4-12 hours late\nSupport concern: customers ask which predictions used the reverted version\nCompliance requires preserving decision lineage for 7 years\n```\n\nTurn this into an operator runbook for rolling back a model release. Include decision criteria, exact verification categories, delayed-label handling, cache considerations, lineage checks, and post-rollback communication.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Nudge the minimap legend below the safe-area inset","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Write the integration guide for publishing custom metrics through the edge agent, including supported types, label limits, buffering, retries, and sample configuration.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement the dataset snapshot endpoint with filtering, signed download URLs, and retention enforcement, then document its request parameters, asynchronous states, examples, and failure responses for SDK authors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Map out a migration from Jenkins-hosted game builds to ephemeral Buildkite agents, covering asset caches, console SDK isolation, signing, capacity spikes, observability, and rollback milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Change `max_retrys` to `max_retries` in the unreleased config schema.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Implement deterministic replay files for the physics server with versioned inputs, checksums, and divergence reporting.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Polish the crafting inventory grid","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump `prometheus-operator` to `v0.85.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Rename `MasterNode` to `CoordinatorNode` across the scheduler, protobufs, dashboards, and tests while preserving wire compatibility and runtime behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Split the monolithic `TrainingJobController` into validation, scheduling, status, and cleanup collaborators without changing its Kubernetes API behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Work item copied from the infrastructure backlog:\n\n```text\nNET-304 — reconcile BGP advertisements from Kubernetes Services\nInput: Services labeled `edge.example.com/advertise=true`\nOutput: prefixes announced through two route reflectors\nRules:\n- only LoadBalancer IPs from configured pools\n- withdraw within 20s after Service deletion\n- duplicate events are expected\n- retain last accepted router generation in Postgres\n- reject an update that would advertise more than 256 prefixes per tenant\n- dry-run mode emits proposed changes but touches no routers\n- expose reconcile duration, rejected prefix count, and router generation lag\nFailure policy: retry transient gRPC failures; configuration errors go to status conditions\n```\n\nImplement the controller, persistence, router client calls, status updates, limits, metrics, and integration tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Investigate why Unreal Engine streaming levels intermittently remain invisible after their assets report loaded.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the GPU allocation heatmap and write a short legend explaining capacity, reservations, fragmentation, and unavailable devices. The view needs zoom, time-range selection, accessible values, and a useful empty state.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the telemetry collector quantize timestamps to 8-millisecond buckets? Explain the existing behavior from code and tests; nothing is broken.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Draft a setup page for running the emulator farm locally with fake devices and a MinIO-backed artifact store.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"After moving the agent to cgroup v2, this integration test started hanging:\n\n```text\n=== RUN TestMemoryPressureTriggersEviction\nfixture: limit=256MiB high=192MiB\nworkload: allocated 220MiB\nmemory.events before: high 0 oom 0 oom_kill 0\nwaiting for watcher notification...\ncontext deadline exceeded after 45s\nmemory.current=230776832\nmemory.high=201326592\nmemory.events after: high 184 oom 0 oom_kill 0\nwatcher epoll fd=17 events=0\n```\n\nDetermine why the kernel counter changes without our watcher waking. I do not know whether the bug is event subscription, file descriptor setup, or an incorrect assumption carried over from cgroup v1.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"finish the controller stuff","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Propose a storage design for petabyte-scale training checkpoints, including chunking, deduplication, consistency, lifecycle rules, regional recovery, and cost checkpoints.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add support for loading GGUF tensor metadata without materializing tensor contents.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Change request under review:\n\n```diff\n func selectReplica(key string, replicas []Replica) Replica {\n- return replicas[xxhash.Sum64String(key)%uint64(len(replicas))]\n+ best := replicas[0]\n+ bestScore := uint64(0)\n+ for _, r := range replicas {\n+ score := xxhash.Sum64String(key + r.ID)\n+ if score > bestScore {\n+ best, bestScore = r, score\n+ }\n+ }\n+ return best\n }\n```\n\nThe author says rendezvous hashing will reduce cache churn during scaling. Review this implementation for correctness, distribution, empty-input behavior, stable identifiers, and what happens when replica weights differ. Do not edit the patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"编写一份故障排查文档，说明 GPU worker 无法注册时要检查的证书、NVIDIA runtime、网络策略和日志。不要修改代码。","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"zh"} +{"prompt":"Build the spectator timeline with event markers, scrub previews, bookmarks, and controller-friendly navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Review the existing autoscaler decision code, explain its stabilization windows, and turn the explanation into an operator-facing page with worked scale-up and scale-down examples.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Pin the base image digest in `worker.Dockerfile`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"把 `WorkerPool` 在整个仓库中改名为 `ExecutorPool`，包括文件名、测试和指标前缀；除了名称以外，行为必须保持不变。","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"Consolidate the CUDA capability checks used by the trainer and serving runtime without altering device eligibility.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose the missing final audio buffer","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Explain how the rollout controller decides a canary is healthy when latency improves but the error budget worsens.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Write an API reference for the existing model-evaluation endpoint, including multipart uploads, metric selection, asynchronous status polling, limits, and result retention.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Plan a transition from mutable model tags to immutable content-addressed references. Cover registry compatibility, CI changes, cache behavior, lineage, rollout gates, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Backlog item:\n\n```text\nUI-771: fleet health overview\nHeader metrics: online, degraded, offline, updating\nMain chart: device count by state over selected range\nTable: fleet, firmware, last contact, health, rollout cohort\nFilters: region, hardware revision, firmware channel, customer\nScale: 250k rows total; server pagination already exists\nLive updates: websocket patches can arrive out of order\nResponsive: table becomes cards below 720px\nAccessibility: chart needs text summary; status cannot rely on color\nError states: stale data banner, socket reconnecting, initial load failure\nUse design tokens from `packages/fleet-theme`\n```\n\nImplement the dashboard views and interaction states. Do not change the fleet API.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Implement `/v1/models/{id}/card.md` by rendering stored model metadata and evaluation results into deterministic Markdown with caching.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Increase the watchdog threshold to 12 seconds","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fix the clipped squad names and extract the shared truncation rule used by the lobby and scoreboard. Preserve all other layout behavior.","purpose":"refactor","secondary":"frontendImpl","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Flatten the rule-evaluation branches into named stages without changing prediction scores or rejection reasons.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Corrige `enviroment` a `environment` solamente en `deploy/values-dev.yaml`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"es"} {"prompt":"Investigate why the ARM inference service becomes 30% slower after several model hot-swaps but recovers on restart.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Summarize the existing anti-cheat event pipeline for the privacy review, including collection, enrichment, retention, and human access.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Develop a capacity roadmap for expanding our Kafka telemetry cluster from three to twelve regions. Include partition ownership, replication traffic, failure domains, quotas, cost gates, and load-test milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"core","lang":"en"} -{"prompt":"Implement WebAssembly plugin execution in the edge agent with memory, fuel, syscall, and output limits.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.88,"slice":"core","lang":"en"} -{"prompt":"Create the model-comparison screen with side-by-side metrics, confidence intervals, slice filters, and accessible chart summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Remove the duplicate colon in the alert title","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"core","lang":"en"} -{"prompt":"Merge the two ECS task-definition builders while preserving JSON output, environment ordering, and deployment behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Trainer output from the failed run:\n\n```text\nstep=18420 loss=2.481 grad_norm=1.91 lr=0.000031\nstep=18421 loss=2.476 grad_norm=1.88 lr=0.000031\nrank=3 NCCL WARN Watchdog caught collective operation timeout\nWorkNCCL(SeqNum=77219, OpType=ALLREDUCE, Timeout(ms)=600000)\nrank=0 dataloader batch=18422 ready=true\nrank=1 dataloader batch=18422 ready=true\nrank=2 dataloader batch=18422 ready=true\nrank=3 dataloader batch=18422 ready=false\nrank=3 worker stderr: PIL.UnidentifiedImageError asset/93/88201.avif\nrank=3 exception handler skipped batch and continued\n```\n\nTraining hangs rather than failing after one corrupt image. Determine how rank 3 diverges from the collective schedule and why the exception handler does not keep distributed steps aligned.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.83,"slice":"pasted-context","lang":"en"} -{"prompt":"Change the dashboard label from `GPU's` to `GPUs`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"en"} -{"prompt":"Assess how the current enclave attestation verifier handles certificate expiry, nonce reuse, and an unknown measurement. No code changes.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Reorganize the Terraform provider into resource-specific packages while preserving schema, state upgrades, diagnostics, and generated documentation; also write a maintainer note describing the new package boundaries.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"Plan the replacement of our proprietary metrics format with OpenTelemetry Protocol, including semantic mappings, dual emission, cardinality validation, SDK migration, and retirement gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"core","lang":"en"} -{"prompt":"Add a retention worker for expired experiment assignments with legal-hold exclusions and idempotent batches.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Build the game-server region picker with latency probes, recommended-region highlighting, party constraints, and keyboard navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"do the infra bit","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace raw device IDs with the `DeviceKey` value type across the firmware service while preserving JSON, SQL, and protobuf representations.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"Find the cause of corrupted save games after cloud conflict resolution, implement the smallest verified fix, and add a troubleshooting note explaining recovery options for support.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.84,"slice":"mixed","lang":"en"} -{"prompt":"Why does the batch scheduler reserve two CPU cores for every GPU task? Review the existing placement rationale and utilization tradeoffs; nothing is malfunctioning.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.51,"slice":"boundary","lang":"en"} -{"prompt":"Track down the intermittent 90-second pause in the DNS controller reconcile loop.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Write release notes for the new quantized model runtime, calling out supported hardware, accuracy caveats, fallback behavior, and upgrade steps.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"Architecture scratchpad:\n\n```text\nGoal: isolate user-submitted Python training code\nCurrent: containers run in a shared Kubernetes node pool\nThreats: kernel escape, credential theft, lateral network movement, data exfiltration, resource abuse\nCandidate isolation: gVisor, Kata, Firecracker workers\nNeeds: NVIDIA GPUs for 30% of jobs; local NVMe cache; startup under 45s\nTenants select approved base images but can pip install at runtime\nTraining data arrives through signed object-store URLs\nNo inbound connectivity required\nLogs and checkpoints must survive worker termination\nCompliance wants per-job network and filesystem evidence\n```\n\nProduce an implementation-free isolation architecture and evaluation plan. Include threat assumptions, prototype benchmarks, GPU constraints, network policy, credential delivery, observability, rollout cohorts, and kill criteria.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"pasted-context","lang":"en"} -{"prompt":"Give the firmware updater a proper progress timeline","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Turn the existing data-retention implementation into an administrator guide, and separately review whether the documented guarantees match deletion workers, backups, and analytics exports.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Outline the architecture and rollout for multi-cluster service discovery across Kubernetes regions, without changing manifests or controllers yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"boundary","lang":"en"} +{"prompt":"Summarize the existing anti-cheat event pipeline for the privacy review, including collection, enrichment, retention, and human access.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Develop a capacity roadmap for expanding our Kafka telemetry cluster from three to twelve regions. Include partition ownership, replication traffic, failure domains, quotas, cost gates, and load-test milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement WebAssembly plugin execution in the edge agent with memory, fuel, syscall, and output limits.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Create the model-comparison screen with side-by-side metrics, confidence intervals, slice filters, and accessible chart summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remove the duplicate colon in the alert title","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Merge the two ECS task-definition builders while preserving JSON output, environment ordering, and deployment behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Trainer output from the failed run:\n\n```text\nstep=18420 loss=2.481 grad_norm=1.91 lr=0.000031\nstep=18421 loss=2.476 grad_norm=1.88 lr=0.000031\nrank=3 NCCL WARN Watchdog caught collective operation timeout\nWorkNCCL(SeqNum=77219, OpType=ALLREDUCE, Timeout(ms)=600000)\nrank=0 dataloader batch=18422 ready=true\nrank=1 dataloader batch=18422 ready=true\nrank=2 dataloader batch=18422 ready=true\nrank=3 dataloader batch=18422 ready=false\nrank=3 worker stderr: PIL.UnidentifiedImageError asset/93/88201.avif\nrank=3 exception handler skipped batch and continued\n```\n\nTraining hangs rather than failing after one corrupt image. Determine how rank 3 diverges from the collective schedule and why the exception handler does not keep distributed steps aligned.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Change the dashboard label from `GPU's` to `GPUs`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Assess how the current enclave attestation verifier handles certificate expiry, nonce reuse, and an unknown measurement. No code changes.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Reorganize the Terraform provider into resource-specific packages while preserving schema, state upgrades, diagnostics, and generated documentation; also write a maintainer note describing the new package boundaries.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan the replacement of our proprietary metrics format with OpenTelemetry Protocol, including semantic mappings, dual emission, cardinality validation, SDK migration, and retirement gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add a retention worker for expired experiment assignments with legal-hold exclusions and idempotent batches.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Build the game-server region picker with latency probes, recommended-region highlighting, party constraints, and keyboard navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Replace raw device IDs with the `DeviceKey` value type across the firmware service while preserving JSON, SQL, and protobuf representations.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find the cause of corrupted save games after cloud conflict resolution, implement the smallest verified fix, and add a troubleshooting note explaining recovery options for support.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Why does the batch scheduler reserve two CPU cores for every GPU task? Review the existing placement rationale and utilization tradeoffs; nothing is malfunctioning.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Track down the intermittent 90-second pause in the DNS controller reconcile loop.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write release notes for the new quantized model runtime, calling out supported hardware, accuracy caveats, fallback behavior, and upgrade steps.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Architecture scratchpad:\n\n```text\nGoal: isolate user-submitted Python training code\nCurrent: containers run in a shared Kubernetes node pool\nThreats: kernel escape, credential theft, lateral network movement, data exfiltration, resource abuse\nCandidate isolation: gVisor, Kata, Firecracker workers\nNeeds: NVIDIA GPUs for 30% of jobs; local NVMe cache; startup under 45s\nTenants select approved base images but can pip install at runtime\nTraining data arrives through signed object-store URLs\nNo inbound connectivity required\nLogs and checkpoints must survive worker termination\nCompliance wants per-job network and filesystem evidence\n```\n\nProduce an implementation-free isolation architecture and evaluation plan. Include threat assumptions, prototype benchmarks, GPU constraints, network policy, credential delivery, observability, rollout cohorts, and kill criteria.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1,"slice":"pasted-context","lang":"en"} +{"prompt":"Give the firmware updater a proper progress timeline","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Turn the existing data-retention implementation into an administrator guide, and separately review whether the documented guarantees match deletion workers, backups, and analytics exports.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Outline the architecture and rollout for multi-cluster service discovery across Kubernetes regions, without changing manifests or controllers yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Implement a lock-free ring buffer for the audio capture path with overflow counters and deterministic tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Produce a field guide for interpreting the device agent's LED error patterns and serial diagnostic codes.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.32,"slice":"core","lang":"en"} -{"prompt":"Move optimizer construction out of `Trainer` into a factory without changing parameter groups, defaults, checkpoint keys, or training results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Investigate why the sidecar sometimes reports healthy while its Envoy admin endpoint is no longer responding.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"boundary","lang":"en"} -{"prompt":"Add atomic lease renewal to the batch coordinator and reject renewals from stale worker generations.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Set `replicaCount` to 5 in production","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"Create the embedded-device provisioning wizard with QR scanning, Wi-Fi setup, certificate enrollment, retry states, and offline guidance.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Renombra `tmpModel` a `candidateModel` solo en `Evaluator.kt`; no cambies ninguna lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"boundary","lang":"es"} -{"prompt":"Review the checkpoint loader for unsafe pickle execution and explain which artifact sources can reach it. Report findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Add the model-lineage endpoint and write its API documentation. Include parent artifacts, datasets, code revisions, pagination, authorization, retention gaps, JSON examples, and error cases.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Design a staged migration from node-local container caches to a regional registry mirror, including eviction, integrity, outage behavior, bandwidth estimates, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"en"} -{"prompt":"Implement HLS segment encryption with rotating keys and deterministic IV derivation in the streaming packager.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"Build the match-results ceremony with rank transitions, reward reveals, skip behavior, and reduced-motion alternatives.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"continue the weird crash work","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"Extract environment detection from the deployment CLI and keep every flag, precedence rule, prompt, and exit code unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why the feature generator produces duplicate rows after a Spark executor retry, implement the proven correction, and document the idempotency invariant beside the job configuration.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.86,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposal to store experiment assignments in browser local storage. Cover tampering, privacy, cross-device behavior, expiration, and compatibility; return review comments only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Determine why packet loss jumps when the embedded gateway rotates its TLS certificate.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Draft the operator handbook section for pausing, resuming, and cancelling distributed training jobs safely.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} -{"prompt":"Migration notes:\n\n```text\nCurrent state:\n- 420 Prometheus servers scrape about 2.8M targets\n- Thanos sidecars upload 2-hour blocks\n- global queries fan out through three query tiers\nPain:\n- rule evaluation differs by region\n- compactors compete for object-store bandwidth\n- tenant attribution is incomplete\nProposal: centralize ingestion through remote write and shard by tenant\nConstraints:\n- agents cannot all upgrade in one quarter\n- recording rule names are customer-visible\n- historical queries must span old and new stores\n- maximum tolerated metrics loss is 30 seconds\n- finance needs projected storage and egress by phase\n```\n\nTurn this into a multi-quarter migration roadmap with compatibility, capacity testing, dual-query verification, rule migration, cost gates, rollback, and ownership. Do not implement changes.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"pasted-context","lang":"en"} -{"prompt":"Add keyboard navigation to the shader graph editor","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Restructure the rollout controller and document its extension API. Preserve rollout ordering, retries, status conditions, and metrics while creating stable hooks for custom health analysis.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.78,"slice":"mixed","lang":"en"} -{"prompt":"Architect a privacy-preserving federated learning workflow for mobile keyboards, covering secure aggregation, consent, poisoning defenses, update eligibility, model rollback, and rollout milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"boundary","lang":"en"} -{"prompt":"Implement incremental Parquet footer scanning over object-store range requests with bounded concurrency.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new board to the Zephyr firmware repository, including devicetree, Kconfig, flashing, and hardware tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"Consolidate the three game-event serializers behind a versioned codec while keeping replay bytes identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Find why read replicas occasionally return an older feature vector after the writer confirms commit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.76,"slice":"boundary","lang":"en"} -{"prompt":"Add automatic certificate renewal to the MQTT broker with overlapping trust and connection draining.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} +{"prompt":"Produce a field guide for interpreting the device agent's LED error patterns and serial diagnostic codes.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Move optimizer construction out of `Trainer` into a factory without changing parameter groups, defaults, checkpoint keys, or training results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Investigate why the sidecar sometimes reports healthy while its Envoy admin endpoint is no longer responding.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add atomic lease renewal to the batch coordinator and reject renewals from stale worker generations.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Set `replicaCount` to 5 in production","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Create the embedded-device provisioning wizard with QR scanning, Wi-Fi setup, certificate enrollment, retry states, and offline guidance.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Renombra `tmpModel` a `candidateModel` solo en `Evaluator.kt`; no cambies ninguna lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"es"} +{"prompt":"Review the checkpoint loader for unsafe pickle execution and explain which artifact sources can reach it. Report findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add the model-lineage endpoint and write its API documentation. Include parent artifacts, datasets, code revisions, pagination, authorization, retention gaps, JSON examples, and error cases.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Design a staged migration from node-local container caches to a regional registry mirror, including eviction, integrity, outage behavior, bandwidth estimates, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement HLS segment encryption with rotating keys and deterministic IV derivation in the streaming packager.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Build the match-results ceremony with rank transitions, reward reveals, skip behavior, and reduced-motion alternatives.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Extract environment detection from the deployment CLI and keep every flag, precedence rule, prompt, and exit code unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose why the feature generator produces duplicate rows after a Spark executor retry, implement the proven correction, and document the idempotency invariant beside the job configuration.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposal to store experiment assignments in browser local storage. Cover tampering, privacy, cross-device behavior, expiration, and compatibility; return review comments only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Determine why packet loss jumps when the embedded gateway rotates its TLS certificate.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Draft the operator handbook section for pausing, resuming, and cancelling distributed training jobs safely.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Migration notes:\n\n```text\nCurrent state:\n- 420 Prometheus servers scrape about 2.8M targets\n- Thanos sidecars upload 2-hour blocks\n- global queries fan out through three query tiers\nPain:\n- rule evaluation differs by region\n- compactors compete for object-store bandwidth\n- tenant attribution is incomplete\nProposal: centralize ingestion through remote write and shard by tenant\nConstraints:\n- agents cannot all upgrade in one quarter\n- recording rule names are customer-visible\n- historical queries must span old and new stores\n- maximum tolerated metrics loss is 30 seconds\n- finance needs projected storage and egress by phase\n```\n\nTurn this into a multi-quarter migration roadmap with compatibility, capacity testing, dual-query verification, rule migration, cost gates, rollback, and ownership. Do not implement changes.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"pasted-context","lang":"en"} +{"prompt":"Add keyboard navigation to the shader graph editor","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Restructure the rollout controller and document its extension API. Preserve rollout ordering, retries, status conditions, and metrics while creating stable hooks for custom health analysis.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Architect a privacy-preserving federated learning workflow for mobile keyboards, covering secure aggregation, consent, poisoning defenses, update eligibility, model rollback, and rollout milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement incremental Parquet footer scanning over object-store range requests with bounded concurrency.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new board to the Zephyr firmware repository, including devicetree, Kconfig, flashing, and hardware tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Consolidate the three game-event serializers behind a versioned codec while keeping replay bytes identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why read replicas occasionally return an older feature vector after the writer confirms commit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add automatic certificate renewal to the MQTT broker with overlapping trust and connection draining.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Change the typo `frametime_ms` to `frame_time_ms` in the new dashboard query.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Build the training-run detail page with live logs, metric charts, resource usage, artifacts, cancellation, and reconnect recovery.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"設定ファイルの `batch_sze` を `batch_size` に直して。まだ未リリースなので互換処理は不要です。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"boundary","lang":"ja"} -{"prompt":"Evaluate whether the eBPF network observer can miss short-lived connections during map rotation. Explain the current synchronization approach; no patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Correct the cramped mobile leaderboard header and consolidate its duplicated breakpoint styles. Only the documented spacing and wrapping defects should change.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.43,"slice":"mixed","lang":"en"} -{"prompt":"Develop a deprecation plan for the legacy inference protocol, covering client inventory, adapters, shadow traffic, parity metrics, customer notices, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.81,"slice":"core","lang":"en"} -{"prompt":"Implement a streaming tar extractor that rejects path traversal, sparse-file abuse, and size-limit violations.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"boundary","lang":"en"} -{"prompt":"Style the vehicle damage overlay with directional indicators, severity animation, color-blind-safe modes, and ultrawide support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Disable `ENABLE_OLD_MATCHMAKER`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"core","lang":"en"} -{"prompt":"Split the data-loader package into sampling, decoding, augmentation, and collation modules while preserving batches for a fixed seed.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Failure from the hardware-in-loop suite:\n\n```text\ncase=power_cycle_during_slot_swap iteration=418\nactive_slot=A pending_slot=B\nbootloader wrote B metadata crc=0x72a1\nrelay power-off at +14ms\nrelay power-on after 3000ms\nboot reason=brownout\nslot A valid=true generation=91\nslot B valid=true generation=92 confirmed=false\nselected slot=B\napplication heartbeat missing\nreset after 30s\nselected slot=B\napplication heartbeat missing\nexpected fallback to A after 1 failed boot\n```\n\nThe bootloader keeps selecting the unconfirmed image instead of falling back. Determine whether the attempt counter, metadata commit order, or brownout reset classification prevents the failure from being recorded.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.85,"slice":"pasted-context","lang":"en"} -{"prompt":"Explain why the event schema includes both `device_time` and `received_time`, and how downstream jobs are expected to use each.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Create a reference page for the existing checkpoint manifest format with field definitions, compatibility rules, integrity checks, and examples.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Plan the device-twin service and implement its first storage layer. The design should settle desired versus reported state, version conflicts, offline retention, fan-out, authorization, and migration from retained MQTT messages; then add the schema, repository, reconciliation primitives, and integration tests.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.93,"slice":"mixed","lang":"en"} -{"prompt":"Outline a roadmap for making game replays portable across engine upgrades, including versioned state, deterministic validation, compatibility windows, and archival tests.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"core","lang":"en"} -{"prompt":"Implement cache-aware routing for embedding requests using model version, tenant, and GPU memory pressure.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Create the incident-map view with clustered sites, live severity updates, timeline playback, and non-map accessibility fallback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Move the packet checksum functions into `wire/checksum` across firmware and simulator targets, preserving generated bytes and timing behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"Investigate the intermittent model-registry 409 responses during concurrent uploads, fix the verified transaction race, and add an operator note distinguishing safe retries from conflicting artifacts.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"Why does the deployment agent retain the previous two manifests on disk? Explain the existing recovery behavior and storage tradeoff; no failure is reported.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.42,"slice":"boundary","lang":"en"} -{"prompt":"Trace the source of nondeterministic particle positions in replay verification after the compiler upgrade.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"Write a migration guide from handwritten Kubernetes manifests to the new Helm chart, with value mappings and rollback instructions.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"Planning fragment from an internal RFC:\n\n```text\nWe need online feature joins under 12 ms p99.\nSources: account DB CDC, session Kafka stream, daily warehouse aggregates\nEntity keys: account, device, household\nFreshness: sessions under 30s; account attributes under 5m; aggregates under 30h\nMissing values must be distinguishable from source lag\nModel requests include an explicit feature-set version\nPotential stores: Redis Cluster, ScyllaDB, custom RocksDB service\nPeak: 240k reads/sec, 18k writes/sec\nMulti-region active-active required for reads\nDeletion requests must propagate within 24h\n```\n\nProduce an architecture evaluation and rollout plan. Define benchmarks, consistency semantics, schema ownership, deletion verification, failure behavior, cost comparison, and migration gates without implementing a store.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"pasted-context","lang":"en"} -{"prompt":"Give the patch notes screen readable typography","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.31,"slice":"core","lang":"en"} -{"prompt":"Write a design for the internal package registry and then implement immutable publishing plus provenance verification. Cover namespaces, authorization, retention, replication, compromise recovery, compatibility, and staged client adoption before building the service paths.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.95,"slice":"mixed","lang":"en"} -{"prompt":"Plan the extraction of matchmaking from the game monolith, including state ownership, party consistency, regional routing, shadow decisions, and rollout milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"boundary","lang":"en"} -{"prompt":"Add durable consumer offsets to the CAN bus gateway so it resumes uploads after power loss.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Turn the existing admission-controller behavior into user documentation covering policies, exemptions, dry runs, and rejection messages.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"core","lang":"en"} -{"prompt":"Combine the three image-normalization implementations while preserving pixel output for every fixture.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Investigate why the Linux game server reports a stable tick rate while clients observe periodic 200 ms freezes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"boundary","lang":"en"} -{"prompt":"Implement tenant-aware compaction scheduling in the time-series database with fairness and I/O budgets.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Pin the Node exporter chart to `4.49.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Build the drone mission planner canvas with waypoints, altitude editing, no-fly-zone warnings, undo, and touch support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"Ändere nur `scrape_interval: 30s` auf `15s` in `clusters/staging/prometheus.yaml`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"boundary","lang":"de"} -{"prompt":"Inspect the shader cache loader for malformed-offset reads and explain whether downloaded cache files are trusted before validation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Implement the cluster-cost export endpoint and write its consumer documentation. Include attribution windows, delayed billing data, pagination, currency, permissions, examples, and known reconciliation gaps.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Create a disaster-recovery plan for the model registry, including artifact integrity, metadata restoration, cross-region lag, signing keys, restore drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"core","lang":"en"} -{"prompt":"Add cooperative cancellation to the C++ asset compiler without leaving partial cache entries.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Implement the warehouse robot status board with floor zones, battery warnings, blocked-path states, and wall-display scaling.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"do the model screen","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"Extract snapshot retention from `CheckpointManager` into a policy object while keeping deletion order and recovery behavior identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose the intermittent NCCL initialization failure on mixed A100 and H100 nodes, implement the proven scheduling or runtime correction, and write a troubleshooting section listing the decisive logs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.88,"slice":"mixed","lang":"en"} -{"prompt":"Assess whether the proposed device enrollment flow resists cloned QR codes and replayed bootstrap tokens. Provide review findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.69,"slice":"boundary","lang":"en"} -{"prompt":"Find why the log shipper occasionally rereads a rotated file from byte zero and duplicates several gigabytes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Write the release announcement for firmware 3.14, including rollout schedule, compatibility, visible changes, and recovery steps.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.34,"slice":"core","lang":"en"} -{"prompt":"Incident review material:\n\n```text\nService: feature-cache\nImpact: recommendation requests fell back to defaults for 11 minutes\nTimeline:\n14:02 deploy began in eu-central\n14:04 new pods failed readiness `schema generation 84 unavailable`\n14:05 autoscaler doubled old pods due latency\n14:07 registry request rate limited at 429\n14:09 rollout paused automatically\n14:11 on-call increased registry quota\n14:13 new pods became ready\nContributing notes:\n- image startup downloads the schema synchronously\n- readiness timeout is 90s\n- schema artifacts are immutable\n- node-local cache is disabled on spot pools\n- no alert exists for registry throttling by consumer\n```\n\nProduce a blameless incident report with impact, contributing factors, detection gaps, corrective actions, owners as placeholders, and measurable follow-up criteria. Do not invent a single root cause beyond the evidence.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.56,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a compact mode to the server browser","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} -{"prompt":"Design and implement certificate-based device enrollment. First document manufacturing trust, bootstrap identities, rotation, revocation, offline enrollment, compromised batches, auditability, and rollout. Then build the enrollment endpoints, signing integration, persistence, and conformance tests.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.96,"slice":"mixed","lang":"en"} -{"prompt":"Propose a phased architecture for replacing nightly warehouse retraining with continuous training, including data gates, evaluation, promotion, rollback, and cost limits.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"boundary","lang":"en"} -{"prompt":"Implement a priority-aware admission queue for GPU inference with tenant quotas and deadline expiry.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Rédige un guide pour créer et valider un nouveau scénario de charge dans `benchmarks/scenarios`, avec exemples de configuration.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.36,"slice":"core","lang":"fr"} -{"prompt":"Restructure the embedded logging package into formatting, buffering, and transport layers with byte-identical serial output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Investigate why the multiplayer relay accepts a session token for several seconds after explicit revocation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"Add garbage collection for abandoned multipart model uploads with retention metrics and legal-hold exemptions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Remove the stale `beta` suffix from the CLI help","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"core","lang":"en"} +{"prompt":"Build the training-run detail page with live logs, metric charts, resource usage, artifacts, cancellation, and reconnect recovery.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"設定ファイルの `batch_sze` を `batch_size` に直して。まだ未リリースなので互換処理は不要です。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"ja"} +{"prompt":"Evaluate whether the eBPF network observer can miss short-lived connections during map rotation. Explain the current synchronization approach; no patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Correct the cramped mobile leaderboard header and consolidate its duplicated breakpoint styles. Only the documented spacing and wrapping defects should change.","purpose":"frontendImpl","secondary":"refactor","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Develop a deprecation plan for the legacy inference protocol, covering client inventory, adapters, shadow traffic, parity metrics, customer notices, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement a streaming tar extractor that rejects path traversal, sparse-file abuse, and size-limit violations.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Style the vehicle damage overlay with directional indicators, severity animation, color-blind-safe modes, and ultrawide support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Disable `ENABLE_OLD_MATCHMAKER`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Split the data-loader package into sampling, decoding, augmentation, and collation modules while preserving batches for a fixed seed.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Failure from the hardware-in-loop suite:\n\n```text\ncase=power_cycle_during_slot_swap iteration=418\nactive_slot=A pending_slot=B\nbootloader wrote B metadata crc=0x72a1\nrelay power-off at +14ms\nrelay power-on after 3000ms\nboot reason=brownout\nslot A valid=true generation=91\nslot B valid=true generation=92 confirmed=false\nselected slot=B\napplication heartbeat missing\nreset after 30s\nselected slot=B\napplication heartbeat missing\nexpected fallback to A after 1 failed boot\n```\n\nThe bootloader keeps selecting the unconfirmed image instead of falling back. Determine whether the attempt counter, metadata commit order, or brownout reset classification prevents the failure from being recorded.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Explain why the event schema includes both `device_time` and `received_time`, and how downstream jobs are expected to use each.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Create a reference page for the existing checkpoint manifest format with field definitions, compatibility rules, integrity checks, and examples.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Plan the device-twin service and implement its first storage layer. The design should settle desired versus reported state, version conflicts, offline retention, fan-out, authorization, and migration from retained MQTT messages; then add the schema, repository, reconciliation primitives, and integration tests.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":1.0,"slice":"mixed","lang":"en"} +{"prompt":"Outline a roadmap for making game replays portable across engine upgrades, including versioned state, deterministic validation, compatibility windows, and archival tests.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement cache-aware routing for embedding requests using model version, tenant, and GPU memory pressure.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the incident-map view with clustered sites, live severity updates, timeline playback, and non-map accessibility fallback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Move the packet checksum functions into `wire/checksum` across firmware and simulator targets, preserving generated bytes and timing behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate the intermittent model-registry 409 responses during concurrent uploads, fix the verified transaction race, and add an operator note distinguishing safe retries from conflicting artifacts.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the deployment agent retain the previous two manifests on disk? Explain the existing recovery behavior and storage tradeoff; no failure is reported.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Trace the source of nondeterministic particle positions in replay verification after the compiler upgrade.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Write a migration guide from handwritten Kubernetes manifests to the new Helm chart, with value mappings and rollback instructions.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Planning fragment from an internal RFC:\n\n```text\nWe need online feature joins under 12 ms p99.\nSources: account DB CDC, session Kafka stream, daily warehouse aggregates\nEntity keys: account, device, household\nFreshness: sessions under 30s; account attributes under 5m; aggregates under 30h\nMissing values must be distinguishable from source lag\nModel requests include an explicit feature-set version\nPotential stores: Redis Cluster, ScyllaDB, custom RocksDB service\nPeak: 240k reads/sec, 18k writes/sec\nMulti-region active-active required for reads\nDeletion requests must propagate within 24h\n```\n\nProduce an architecture evaluation and rollout plan. Define benchmarks, consistency semantics, schema ownership, deletion verification, failure behavior, cost comparison, and migration gates without implementing a store.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Give the patch notes screen readable typography","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Write a design for the internal package registry and then implement immutable publishing plus provenance verification. Cover namespaces, authorization, retention, replication, compromise recovery, compatibility, and staged client adoption before building the service paths.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Plan the extraction of matchmaking from the game monolith, including state ownership, party consistency, regional routing, shadow decisions, and rollout milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add durable consumer offsets to the CAN bus gateway so it resumes uploads after power loss.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Turn the existing admission-controller behavior into user documentation covering policies, exemptions, dry runs, and rejection messages.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Combine the three image-normalization implementations while preserving pixel output for every fixture.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why the Linux game server reports a stable tick rate while clients observe periodic 200 ms freezes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement tenant-aware compaction scheduling in the time-series database with fairness and I/O budgets.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Pin the Node exporter chart to `4.49.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the drone mission planner canvas with waypoints, altitude editing, no-fly-zone warnings, undo, and touch support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Ändere nur `scrape_interval: 30s` auf `15s` in `clusters/staging/prometheus.yaml`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"de"} +{"prompt":"Inspect the shader cache loader for malformed-offset reads and explain whether downloaded cache files are trusted before validation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Implement the cluster-cost export endpoint and write its consumer documentation. Include attribution windows, delayed billing data, pagination, currency, permissions, examples, and known reconciliation gaps.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Create a disaster-recovery plan for the model registry, including artifact integrity, metadata restoration, cross-region lag, signing keys, restore drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add cooperative cancellation to the C++ asset compiler without leaving partial cache entries.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement the warehouse robot status board with floor zones, battery warnings, blocked-path states, and wall-display scaling.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"do the model screen","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Extract snapshot retention from `CheckpointManager` into a policy object while keeping deletion order and recovery behavior identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose the intermittent NCCL initialization failure on mixed A100 and H100 nodes, implement the proven scheduling or runtime correction, and write a troubleshooting section listing the decisive logs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Assess whether the proposed device enrollment flow resists cloned QR codes and replayed bootstrap tokens. Provide review findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why the log shipper occasionally rereads a rotated file from byte zero and duplicates several gigabytes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write the release announcement for firmware 3.14, including rollout schedule, compatibility, visible changes, and recovery steps.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Incident review material:\n\n```text\nService: feature-cache\nImpact: recommendation requests fell back to defaults for 11 minutes\nTimeline:\n14:02 deploy began in eu-central\n14:04 new pods failed readiness `schema generation 84 unavailable`\n14:05 autoscaler doubled old pods due latency\n14:07 registry request rate limited at 429\n14:09 rollout paused automatically\n14:11 on-call increased registry quota\n14:13 new pods became ready\nContributing notes:\n- image startup downloads the schema synchronously\n- readiness timeout is 90s\n- schema artifacts are immutable\n- node-local cache is disabled on spot pools\n- no alert exists for registry throttling by consumer\n```\n\nProduce a blameless incident report with impact, contributing factors, detection gaps, corrective actions, owners as placeholders, and measurable follow-up criteria. Do not invent a single root cause beyond the evidence.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"Add a compact mode to the server browser","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Design and implement certificate-based device enrollment. First document manufacturing trust, bootstrap identities, rotation, revocation, offline enrollment, compromised batches, auditability, and rollout. Then build the enrollment endpoints, signing integration, persistence, and conformance tests.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":1.0,"slice":"mixed","lang":"en"} +{"prompt":"Propose a phased architecture for replacing nightly warehouse retraining with continuous training, including data gates, evaluation, promotion, rollback, and cost limits.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement a priority-aware admission queue for GPU inference with tenant quotas and deadline expiry.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Rédige un guide pour créer et valider un nouveau scénario de charge dans `benchmarks/scenarios`, avec exemples de configuration.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"fr"} +{"prompt":"Restructure the embedded logging package into formatting, buffering, and transport layers with byte-identical serial output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Investigate why the multiplayer relay accepts a session token for several seconds after explicit revocation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add garbage collection for abandoned multipart model uploads with retention metrics and legal-hold exemptions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Remove the stale `beta` suffix from the CLI help","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Create the data-labeling workspace with keyboard shortcuts, annotation history, confidence controls, and conflict indicators.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"`traning_jobs_total` を `training_jobs_total` に修正して。新しい未公開メトリクスなので互換エイリアスは不要。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"boundary","lang":"ja"} -{"prompt":"Review the OTA manifest parser for integer overflows, duplicate component names, and signature-verification ordering. Do not implement fixes.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"Build the experiment audit endpoint and produce its API guide. Support actor, model, date, and action filters; stable pagination; retention boundaries; authorization tests; JSON examples; and an explanation of delayed events.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Design an authorization architecture for enterprise workspaces with organization roles, project grants, temporary elevation, service accounts, and policy simulation. Cover evaluation semantics, auditability, cache invalidation, emergency access, migration from the current role table, and rollout gates. Deliver an RFC, not implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"core","lang":"en"} -{"prompt":"Before changing the login service, outline a migration from session cookies to sender-constrained tokens. Include browser compatibility, key lifecycle, refresh behavior, compromised-device recovery, gradual enrollment, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"boundary","lang":"en"} -{"prompt":"Add PKCE validation to the OAuth callback","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.51,"slice":"core","lang":"en"} -{"prompt":"CI failure from the release branch:\n\n```text\nworkflow=publish-web run=9918472 attempt=2\njob=build-static runner=ubuntu-26.04\nnode=24.4.1 pnpm=10.14.0\ncache restored key=next-4b8102\nnext build: compiled successfully\ncollecting page data...\nError: ENOENT: no such file or directory, open '.next/server/app/(legal)/terms/page_client-reference-manifest.js'\nroute groups found: (app), (legal), (marketing)\nretry with cache disabled: PASS\nretry with same cache: FAIL\ncache archive includes `.next/server/app/(legal)` but excludes files matching `*client-reference-manifest*`\n```\n\nDetermine why the restored incremental cache expects a manifest that the cache action excluded and whether the cache key or Next.js build reuse is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Build the React `AccessRequestDrawer` with requested scopes, justification, expiry, approver timeline, loading states, and keyboard-safe focus management.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Plan and implement passkey authentication for the customer portal. Start with a design covering registration, discoverable credentials, cross-device flows, account recovery, attestation policy, existing MFA, session binding, browser support, observability, and rollout. Then add WebAuthn endpoints, credential storage, UI integration primitives, and conformance tests. The security and recovery design is the primary deliverable.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.98,"slice":"mixed","lang":"en"} -{"prompt":"Enable `STRICT_CSP_REPORTING`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"Extract duplicated permission checks from the REST and GraphQL middleware into one evaluator while preserving decisions, errors, logs, and latency metrics.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Implement `/internal/jwks/status` with active key IDs, activation times, expiry, and last successful publication.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.47,"slice":"boundary","lang":"en"} -{"prompt":"make login feel premium","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.42,"slice":"vague-eval","lang":"en"} -{"prompt":"Find why Safari occasionally loops between `/login` and `/callback` after a successful identity-provider response.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Explain how `PolicyEngine.evaluate` resolves an explicit deny against a project grant inherited through two groups. Do not modify code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Security launch notes:\n\n```text\nFeature: administrator session controls\nAvailable actions: list active sessions, revoke one, revoke all except current\nSession metadata: approximate location, browser family, created time, last activity\nLocation is derived from IP and may be wrong\nRevocation propagates through Redis pubsub; fallback TTL is 15 minutes\nService-account sessions do not appear in this UI\nSupport must not claim revocation is instantaneous\nAudit events: session.revoked and sessions.revoked_all\nMobile clients before 8.4 may show one failed refresh before returning to login\n```\n\nTurn this into administrator-facing documentation with clear limitations, privacy wording, action descriptions, audit behavior, and troubleshooting for delayed revocation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.48,"slice":"pasted-context","lang":"en"} -{"prompt":"Align the SSO provider logo with the input labels","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.13,"slice":"boundary","lang":"en"} -{"prompt":"Write a deployment guide for configuring OIDC through Helm, including issuer discovery, client secrets, redirect URLs, scopes, and validation checks.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} -{"prompt":"Implement the SCIM bearer-token rotation endpoint with overlap, revocation, audit events, and authorization tests, then document the request contract and safe rotation sequence for administrators.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Map out a staged migration from repository-level GitHub Actions workflows to centrally governed reusable workflows, including exceptions, versioning, adoption metrics, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.84,"slice":"core","lang":"en"} -{"prompt":"Rename `authzRes` to `authorizationResult` in `PolicyRoute.ts`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"boundary","lang":"en"} -{"prompt":"Teach the token service to rotate refresh-token families atomically and detect reuse of an invalidated ancestor.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Polish the MFA method cards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.31,"slice":"core","lang":"en"} -{"prompt":"Bump `@simplewebauthn/server` to `13.2.2`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"Rename `WhitelistMatcher` to `AllowlistMatcher` across source, tests, metrics, and dashboards while preserving configuration compatibility and behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.64,"slice":"boundary","lang":"en"} -{"prompt":"Split `IdentityProviderService` into discovery, metadata validation, provisioning, and persistence components without changing its API contract.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Ticket copied from the security backlog:\n\n```text\nAUTH-1827 — service account token exchange\nEndpoint: POST `/v2/token/exchange`\nInput: signed workload assertion plus requested audience\nRequirements:\n- validate issuer against tenant configuration\n- allow only configured audiences\n- maximum resulting lifetime 15 minutes\n- no refresh token\n- assertion IDs are single use for 20 minutes\n- tolerate 60 seconds of clock skew\n- emit audit event with issuer, subject, audience, and decision\n- private claims must not enter logs\n- expose accepted, rejected-by-reason, and replay metrics\n- support EdDSA and ES256; reject algorithm confusion\n```\n\nImplement the exchange endpoint, replay store, policy validation, audit event, metrics, and adversarial tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Investigate why the React app loses its CSRF token after returning from the payment provider in a new tab.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Create the role-comparison table and write a brief legend for inherited, direct, denied, and unavailable permissions. Include sticky headers, filtering, and screen-reader summaries.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.67,"slice":"mixed","lang":"en"} -{"prompt":"Why does the login gateway preserve the original URL in a signed cookie instead of a query parameter? Explain the existing choice; nothing is broken.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Rewrite the local setup section for running Keycloak, Mailpit, and the portal through Docker Compose.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.32,"slice":"core","lang":"en"} -{"prompt":"The authentication suite became flaky after enabling parallel tests:\n\n```text\nFAIL TestRefreshReuseRevokesFamily\nexpected status=401 actual=200\nfamily=fam_7ce current_generation=4\nrequest A token_generation=3 started=12:00:01.113\nrequest B token_generation=4 started=12:00:01.114\nrequest A reuse marker inserted at=12:00:01.128\nrequest B replacement issued generation=5 at=12:00:01.131\nrequest A family revoked at=12:00:01.139\nrequest B response sent at=12:00:01.142\n```\n\nDetermine whether the observed 200 is a test-ordering issue or a real race where a replacement escapes after reuse detection. Trace the transaction boundaries and revocation visibility.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.83,"slice":"boundary","lang":"en"} -{"prompt":"finish the SSO thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} -{"prompt":"Propose an authorization model for customer-managed automation bots, including delegation, scope boundaries, approval, expiry, revocation, and audit queries.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.87,"slice":"core","lang":"en"} +{"prompt":"`traning_jobs_total` を `training_jobs_total` に修正して。新しい未公開メトリクスなので互換エイリアスは不要。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"ja"} +{"prompt":"Review the OTA manifest parser for integer overflows, duplicate component names, and signature-verification ordering. Do not implement fixes.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Build the experiment audit endpoint and produce its API guide. Support actor, model, date, and action filters; stable pagination; retention boundaries; authorization tests; JSON examples; and an explanation of delayed events.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Design an authorization architecture for enterprise workspaces with organization roles, project grants, temporary elevation, service accounts, and policy simulation. Cover evaluation semantics, auditability, cache invalidation, emergency access, migration from the current role table, and rollout gates. Deliver an RFC, not implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Before changing the login service, outline a migration from session cookies to sender-constrained tokens. Include browser compatibility, key lifecycle, refresh behavior, compromised-device recovery, gradual enrollment, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add PKCE validation to the OAuth callback","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"CI failure from the release branch:\n\n```text\nworkflow=publish-web run=9918472 attempt=2\njob=build-static runner=ubuntu-26.04\nnode=24.4.1 pnpm=10.14.0\ncache restored key=next-4b8102\nnext build: compiled successfully\ncollecting page data...\nError: ENOENT: no such file or directory, open '.next/server/app/(legal)/terms/page_client-reference-manifest.js'\nroute groups found: (app), (legal), (marketing)\nretry with cache disabled: PASS\nretry with same cache: FAIL\ncache archive includes `.next/server/app/(legal)` but excludes files matching `*client-reference-manifest*`\n```\n\nDetermine why the restored incremental cache expects a manifest that the cache action excluded and whether the cache key or Next.js build reuse is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Build the React `AccessRequestDrawer` with requested scopes, justification, expiry, approver timeline, loading states, and keyboard-safe focus management.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Plan and implement passkey authentication for the customer portal. Start with a design covering registration, discoverable credentials, cross-device flows, account recovery, attestation policy, existing MFA, session binding, browser support, observability, and rollout. Then add WebAuthn endpoints, credential storage, UI integration primitives, and conformance tests. The security and recovery design is the primary deliverable.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":1,"slice":"mixed","lang":"en"} +{"prompt":"Enable `STRICT_CSP_REPORTING`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Extract duplicated permission checks from the REST and GraphQL middleware into one evaluator while preserving decisions, errors, logs, and latency metrics.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement `/internal/jwks/status` with active key IDs, activation times, expiry, and last successful publication.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"make login feel premium","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Find why Safari occasionally loops between `/login` and `/callback` after a successful identity-provider response.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Explain how `PolicyEngine.evaluate` resolves an explicit deny against a project grant inherited through two groups. Do not modify code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Security launch notes:\n\n```text\nFeature: administrator session controls\nAvailable actions: list active sessions, revoke one, revoke all except current\nSession metadata: approximate location, browser family, created time, last activity\nLocation is derived from IP and may be wrong\nRevocation propagates through Redis pubsub; fallback TTL is 15 minutes\nService-account sessions do not appear in this UI\nSupport must not claim revocation is instantaneous\nAudit events: session.revoked and sessions.revoked_all\nMobile clients before 8.4 may show one failed refresh before returning to login\n```\n\nTurn this into administrator-facing documentation with clear limitations, privacy wording, action descriptions, audit behavior, and troubleshooting for delayed revocation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} +{"prompt":"Align the SSO provider logo with the input labels","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Write a deployment guide for configuring OIDC through Helm, including issuer discovery, client secrets, redirect URLs, scopes, and validation checks.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Implement the SCIM bearer-token rotation endpoint with overlap, revocation, audit events, and authorization tests, then document the request contract and safe rotation sequence for administrators.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Map out a staged migration from repository-level GitHub Actions workflows to centrally governed reusable workflows, including exceptions, versioning, adoption metrics, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Rename `authzRes` to `authorizationResult` in `PolicyRoute.ts`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Teach the token service to rotate refresh-token families atomically and detect reuse of an invalidated ancestor.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Polish the MFA method cards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump `@simplewebauthn/server` to `13.2.2`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename `WhitelistMatcher` to `AllowlistMatcher` across source, tests, metrics, and dashboards while preserving configuration compatibility and behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Split `IdentityProviderService` into discovery, metadata validation, provisioning, and persistence components without changing its API contract.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Ticket copied from the security backlog:\n\n```text\nAUTH-1827 — service account token exchange\nEndpoint: POST `/v2/token/exchange`\nInput: signed workload assertion plus requested audience\nRequirements:\n- validate issuer against tenant configuration\n- allow only configured audiences\n- maximum resulting lifetime 15 minutes\n- no refresh token\n- assertion IDs are single use for 20 minutes\n- tolerate 60 seconds of clock skew\n- emit audit event with issuer, subject, audience, and decision\n- private claims must not enter logs\n- expose accepted, rejected-by-reason, and replay metrics\n- support EdDSA and ES256; reject algorithm confusion\n```\n\nImplement the exchange endpoint, replay store, policy validation, audit event, metrics, and adversarial tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Investigate why the React app loses its CSRF token after returning from the payment provider in a new tab.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the role-comparison table and write a brief legend for inherited, direct, denied, and unavailable permissions. Include sticky headers, filtering, and screen-reader summaries.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Why does the login gateway preserve the original URL in a signed cookie instead of a query parameter? Explain the existing choice; nothing is broken.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Rewrite the local setup section for running Keycloak, Mailpit, and the portal through Docker Compose.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"The authentication suite became flaky after enabling parallel tests:\n\n```text\nFAIL TestRefreshReuseRevokesFamily\nexpected status=401 actual=200\nfamily=fam_7ce current_generation=4\nrequest A token_generation=3 started=12:00:01.113\nrequest B token_generation=4 started=12:00:01.114\nrequest A reuse marker inserted at=12:00:01.128\nrequest B replacement issued generation=5 at=12:00:01.131\nrequest A family revoked at=12:00:01.139\nrequest B response sent at=12:00:01.142\n```\n\nDetermine whether the observed 200 is a test-ordering issue or a real race where a replacement escapes after reuse detection. Trace the transaction boundaries and revocation visibility.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"finish the SSO thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Propose an authorization model for customer-managed automation bots, including delegation, scope boundaries, approval, expiry, revocation, and audit queries.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Add detached JWS verification to the webhook CLI","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"PR excerpt:\n\n```diff\n async function requireAdmin(req, res, next) {\n- const user = await loadUser(req.session.userId)\n- if (!user.roles.includes('admin')) return res.sendStatus(403)\n+ const claims = decodeJwt(req.headers.authorization.slice(7))\n+ if (claims.role !== 'admin') return res.sendStatus(403)\n next()\n }\n```\n\nThe author says this removes a database lookup. Review the change for signature verification, claim freshness, tenant scoping, token source assumptions, error handling, and differences between the session role list and JWT role field. Do not patch it.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Schreibe eine kurze Administrator-Dokumentation zur bestehenden Notfallzugriffs-Funktion, einschließlich Aktivierung, Ablauf, Audit-Events und Einschränkungen. Keine Codeänderungen.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"boundary","lang":"de"} -{"prompt":"Build the responsive security-events explorer with saved filters, expandable payloads, virtualized rows, and accessible severity indicators.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Review how the current GitHub Actions release workflow signs artifacts, then turn the findings into a maintainer runbook with verification and recovery steps.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"Set the session cookie's `SameSite` value to `Lax`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.09,"slice":"core","lang":"en"} -{"prompt":"Benenne `TokenMgr` repositoryweit in `TokenManager` um; öffentliche JSON-Felder, Datenbankspalten und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"de"} -{"prompt":"Consolidate the browser and mobile redirect-URI validators while preserving every accepted URI and rejection message.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Diagnose the missing logout audit event","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Explain how the session cache prevents a revoked account from remaining active until cookie expiry.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Create API documentation for the existing token introspection endpoint, including authentication, response fields, inactive tokens, caching, and rate limits.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Schreibe eine kurze Administrator-Dokumentation zur bestehenden Notfallzugriffs-Funktion, einschließlich Aktivierung, Ablauf, Audit-Events und Einschränkungen. Keine Codeänderungen.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"de"} +{"prompt":"Build the responsive security-events explorer with saved filters, expandable payloads, virtualized rows, and accessible severity indicators.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Review how the current GitHub Actions release workflow signs artifacts, then turn the findings into a maintainer runbook with verification and recovery steps.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Set the session cookie's `SameSite` value to `Lax`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Benenne `TokenMgr` repositoryweit in `TokenManager` um; öffentliche JSON-Felder, Datenbankspalten und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"de"} +{"prompt":"Consolidate the browser and mobile redirect-URI validators while preserving every accepted URI and rejection message.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose the missing logout audit event","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Explain how the session cache prevents a revoked account from remaining active until cookie expiry.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Create API documentation for the existing token introspection endpoint, including authentication, response fields, inactive tokens, caching, and rate limits.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Plan the migration from long-lived deploy keys to GitHub OIDC federation across CI, cloud providers, package registries, and emergency workflows.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Frontend ticket:\n\n```text\nPage: `/settings/security/sessions`\nDesktop: sortable table with device, approximate location, last active, created, actions\nMobile: stacked cards; revoke action remains visible\nCurrent session gets a `This device` badge and cannot be revoked individually\nStates: initial skeleton, no other sessions, revoke pending, revoke failed, bulk revoke confirmation\nLive behavior: websocket removes revoked sessions; events may arrive twice\nAccessibility: confirmation names the device; focus returns to heading after removal\nPrivacy: tooltip must explain approximate location\nExisting hooks: `useSessions`, `useRevokeSession`\n```\n\nImplement the page and interaction tests without changing session APIs.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"pasted-context","lang":"en"} -{"prompt":"Implement `/v1/auth/recovery-codes/regenerate` with recent-authentication enforcement, atomic invalidation, and audit logging.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Remove the extra slash from the callback URL","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"core","lang":"en"} -{"prompt":"Fix the two-pixel jump when the password-strength bar appears and extract its duplicated height token into the shared form styles.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.37,"slice":"mixed","lang":"en"} -{"prompt":"Replace scattered login-state booleans with one explicit state machine while preserving transitions, analytics, and rendered behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Cambia `usrScope` por `userScope` solo en `AccessCheck.ts`; no modifiques la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"es"} -{"prompt":"Investigate why Firefox sometimes submits the WebAuthn registration form twice after a platform-authenticator prompt.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Summarize the current account-recovery flow for a threat-model review, using the implementation and tests as sources.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"Develop a roadmap for centralizing authorization policy across twelve services. Include semantic inventory, compatibility tests, shadow decisions, latency budgets, ownership, and rollback gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"core","lang":"en"} -{"prompt":"Implement signed build provenance generation and verification in the release orchestrator.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Create the React access-policy editor with nested conditions, validation, test simulation, undo, and keyboard navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"Correct `authorizaton` in the CLI help","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"core","lang":"en"} -{"prompt":"Merge the duplicated token-claim normalization paths while retaining claim values, errors, and compatibility with older issuers.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Gateway logs from the incident:\n\n```text\nrequest_id=19f route=/admin/export user=usr_88\nsession cache hit account_state=active cached_at=13:41:02\naccount disabled in primary at=13:41:05\nrevocation event published partition=7 offset=9912\nconsumer-a applied offset=9912 at=13:41:06\nconsumer-b rebalance generation=44\nrequest_id=1a0 route=/admin/export user=usr_88 node=consumer-b\nsession cache hit account_state=active cached_at=13:40:59\nresponse=200 at=13:41:18\nconsumer-b resumed partition=7 offset=9908 at=13:41:21\n```\n\nA disabled administrator retained access on one node for 16 seconds. Determine why rebalance and cache invalidation ordering allowed this and whether the fallback TTL meets the intended revocation guarantee.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Rename the local constant `secert` to `secret`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"boundary","lang":"en"} -{"prompt":"Assess whether the current password reset flow leaks account existence through timing, response bodies, email behavior, or rate-limit headers. No edits requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Restructure the authentication SDK into transport, token storage, refresh, and session modules, then write a maintainer note describing their boundaries. Preserve public exports and behavior.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.78,"slice":"mixed","lang":"en"} -{"prompt":"Plan the deprecation of SMS as an account-recovery factor, covering enrollment gaps, regional constraints, support escalation, customer communication, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"en"} -{"prompt":"Add tenant-scoped signing-key rotation with overlapping verification windows and generation fencing.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"Build the mobile approval queue with scope summaries, expiry warnings, batch actions, and swipe alternatives.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} +{"prompt":"Frontend ticket:\n\n```text\nPage: `/settings/security/sessions`\nDesktop: sortable table with device, approximate location, last active, created, actions\nMobile: stacked cards; revoke action remains visible\nCurrent session gets a `This device` badge and cannot be revoked individually\nStates: initial skeleton, no other sessions, revoke pending, revoke failed, bulk revoke confirmation\nLive behavior: websocket removes revoked sessions; events may arrive twice\nAccessibility: confirmation names the device; focus returns to heading after removal\nPrivacy: tooltip must explain approximate location\nExisting hooks: `useSessions`, `useRevokeSession`\n```\n\nImplement the page and interaction tests without changing session APIs.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Implement `/v1/auth/recovery-codes/regenerate` with recent-authentication enforcement, atomic invalidation, and audit logging.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remove the extra slash from the callback URL","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fix the two-pixel jump when the password-strength bar appears and extract its duplicated height token into the shared form styles.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.3,"slice":"mixed","lang":"en"} +{"prompt":"Replace scattered login-state booleans with one explicit state machine while preserving transitions, analytics, and rendered behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Cambia `usrScope` por `userScope` solo en `AccessCheck.ts`; no modifiques la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"es"} +{"prompt":"Investigate why Firefox sometimes submits the WebAuthn registration form twice after a platform-authenticator prompt.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Summarize the current account-recovery flow for a threat-model review, using the implementation and tests as sources.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Develop a roadmap for centralizing authorization policy across twelve services. Include semantic inventory, compatibility tests, shadow decisions, latency budgets, ownership, and rollback gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement signed build provenance generation and verification in the release orchestrator.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create the React access-policy editor with nested conditions, validation, test simulation, undo, and keyboard navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Correct `authorizaton` in the CLI help","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Merge the duplicated token-claim normalization paths while retaining claim values, errors, and compatibility with older issuers.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Gateway logs from the incident:\n\n```text\nrequest_id=19f route=/admin/export user=usr_88\nsession cache hit account_state=active cached_at=13:41:02\naccount disabled in primary at=13:41:05\nrevocation event published partition=7 offset=9912\nconsumer-a applied offset=9912 at=13:41:06\nconsumer-b rebalance generation=44\nrequest_id=1a0 route=/admin/export user=usr_88 node=consumer-b\nsession cache hit account_state=active cached_at=13:40:59\nresponse=200 at=13:41:18\nconsumer-b resumed partition=7 offset=9908 at=13:41:21\n```\n\nA disabled administrator retained access on one node for 16 seconds. Determine why rebalance and cache invalidation ordering allowed this and whether the fallback TTL meets the intended revocation guarantee.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Rename the local constant `secert` to `secret`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Assess whether the current password reset flow leaks account existence through timing, response bodies, email behavior, or rate-limit headers. No edits requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Restructure the authentication SDK into transport, token storage, refresh, and session modules, then write a maintainer note describing their boundaries. Preserve public exports and behavior.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan the deprecation of SMS as an account-recovery factor, covering enrollment gaps, regional constraints, support escalation, customer communication, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add tenant-scoped signing-key rotation with overlapping verification windows and generation fencing.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Build the mobile approval queue with scope summaries, expiry warnings, batch actions, and swipe alternatives.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"do the auth screen","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `AuthCtx` with `AuthContext` throughout the web app without changing provider behavior or exported compatibility aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why emailed magic links sometimes expire immediately, implement the correction after proving the clock or encoding issue, and add a support note for identifying affected links.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.77,"slice":"mixed","lang":"en"} -{"prompt":"Why does the CI signer upload the public certificate before the artifact? Explain the existing recovery and verification ordering; no failure is reported.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.47,"slice":"boundary","lang":"en"} -{"prompt":"Track down the memory leak in the SAML metadata refresher after repeated certificate rotations.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Write release notes for organization-level MFA enforcement, including exemptions, rollout timing, admin actions, and user-visible errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"core","lang":"en"} -{"prompt":"Architecture notes from the identity working group:\n\n```text\nGoal: support customer-owned identity domains\nVerification candidates: DNS TXT, HTTPS well-known file\nOne domain can belong to only one organization\nSubdomains may be claimed separately only with explicit parent policy\nVerified domains enable automatic user discovery and optional forced SSO\nDomains must be rechecked after nameserver changes\nDeletion should not instantly free a domain for another tenant\nSupport needs a reversible dispute process\nAudit must record verification attempts without storing resolver secrets\n```\n\nProduce an architecture and rollout plan covering ownership semantics, verification, caching, revalidation, takeover prevention, disputes, forced SSO safety, and migration gates. No implementation yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"Give the security dashboard a useful empty state","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.32,"slice":"core","lang":"en"} -{"prompt":"Turn the current administrator impersonation implementation into documentation, and separately review whether its audit, expiry, and notification behavior supports the claims in that document.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Outline a phased design for moving browser sessions from Redis to a globally replicated store, without changing code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.84,"slice":"boundary","lang":"en"} -{"prompt":"Implement policy-decision caching with dependency-aware invalidation and bounded stale-deny behavior.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.81,"slice":"core","lang":"en"} -{"prompt":"Create an operator guide for rotating SAML certificates without breaking active logins.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"Move nonce validation out of the callback handler into a dedicated verifier while preserving all accepted flows and errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Investigate why the GitHub Actions deploy job occasionally uses credentials from the previous environment.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","lang":"en"} -{"prompt":"Add replay-resistant device authorization grants with polling throttles and expiry.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Set the idle session timeout to 30 minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"Create the responsive SSO configuration wizard with metadata upload, field validation, connection testing, and recovery guidance.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Corrige apenas `authentification` para `authentication` no novo título da documentação.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"pt"} -{"prompt":"Review the JWT verification path for algorithm confusion, duplicate claims, key selection, critical headers, and token-size limits. Report findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Implement the access-review export endpoint and write its API guide. Include filters, asynchronous generation, retention, signed downloads, permissions, examples, and audit behavior.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Design a migration from shared CI runners to isolated ephemeral runners, including trust tiers, image provenance, cache policy, secret delivery, capacity, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"core","lang":"en"} -{"prompt":"Implement certificate-bound API tokens with backward-compatible bearer verification during migration.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Build the account-recovery status page with step progress, alternate paths, support escalation, and privacy-safe messaging.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"continue yesterday's security work","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.58,"slice":"vague-eval","lang":"en"} -{"prompt":"Extract role-name canonicalization into one shared utility while preserving stored values and every authorization decision.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why revoked personal access tokens continue working through the GraphQL gateway, implement the verified cache fix, and document the propagation window accurately.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.82,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed OAuth device flow for phishing resistance, code entropy, polling abuse, consent clarity, and shared-device cleanup. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"Find why a successful SAML login occasionally creates a second user instead of linking the existing account.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Draft the incident-response playbook for suspected signing-key compromise, including containment, rotation, invalidation, verification, and communication.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Workflow migration brief:\n\n```text\nRepositories: 137\nCurrent: each repo owns release YAML and long-lived cloud credentials\nTarget: reusable workflow pinned by commit digest\nLanguages: Go, Node, Python, Rust\nOutputs: containers, packages, SBOMs, provenance attestations\nConstraints:\n- regulated repos require two-person approval\n- self-hosted runners exist for hardware builds\n- hotfix releases must remain possible during control-plane outage\n- teams may adopt over two quarters\n- central workflow changes cannot silently alter release semantics\n```\n\nProduce a migration roadmap with workflow contracts, compatibility testing, exception handling, credential replacement, canaries, governance, rollback, and adoption metrics.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a compact layout to the permissions table","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"Restructure the session-management package and document its extension points. Preserve cookie semantics, refresh timing, revocation behavior, and public APIs while separating storage, validation, and lifecycle concerns.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.78,"slice":"mixed","lang":"en"} -{"prompt":"Architect a multi-region key-management service for application signing keys, including quorum operations, audit, disaster recovery, rotation, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"boundary","lang":"en"} -{"prompt":"Implement a streaming parser for large SAML metadata aggregates with signature and entity limits.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new authorization action, including naming, policy tests, audit events, and UI exposure.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"Consolidate the three CSRF token stores behind one interface without changing token scope, expiry, or rotation.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Investigate why deployment approvals occasionally disappear when a pull request is rebased.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional account locking with reason codes, expiry, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Pin `cosign` to `v3.0.2`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Build the consent-history view with policy versions, acceptance timestamps, downloadable copies, and accessible expansion.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Remplace `Authorisation` par `Authorization` uniquement dans le nouveau libellé anglais; ne touche pas aux clés i18n.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"boundary","lang":"fr"} -{"prompt":"Inspect the emergency-access implementation and explain whether an approver can authorize their own request through nested group membership.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Implement organization session-policy endpoints and produce integration documentation. Cover idle and absolute timeouts, exemptions, validation, propagation, examples, and old-client behavior.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Develop a roadmap for enforcing signed commits and protected release tags across all repositories, including bots, mirrors, emergency bypass, and audit gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.87,"slice":"core","lang":"en"} -{"prompt":"Add subject-token validation and audience narrowing to the RFC 8693 exchange implementation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Create the responsive audit-event detail panel with structured fields, raw JSON, copy actions, and redaction indicators.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"fix the permission thing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace duplicated issuer URL cleanup with one canonicalizer, preserving accepted configurations and metadata cache keys.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why recovery-code regeneration sometimes leaves one old code valid, implement the proven transaction correction, and add a security advisory note for affected versions.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.83,"slice":"mixed","lang":"en"} -{"prompt":"Why does the deployment controller require a fresh approval after only a documentation commit? Explain existing path filtering and trust assumptions.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.51,"slice":"boundary","lang":"en"} -{"prompt":"Track down the occasional `invalid_state` response when two login tabs complete in reverse order.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Write a customer migration guide from API keys to OAuth client credentials, with examples, rollout advice, and troubleshooting.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Threat-model excerpt:\n\n```text\nFeature: support-assisted account recovery\nSupport agent verifies ticket ownership, then requests a recovery session\nSecond agent approves for enterprise accounts\nRecovery session lasts 20 minutes and permits password reset plus MFA replacement\nCustomer receives email after completion, not before\nAgent cannot see existing MFA secrets\nAll actions enter the audit log\nOpen concerns:\n- compromised support account\n- social engineering during active incident\n- approving agent collusion\n- customer mailbox compromise\n- replaying an expired recovery-session URL\n```\n\nReview the proposed flow. Identify trust assumptions, abuse cases, missing customer controls, audit requirements, and recovery-session safeguards. No implementation requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a loading skeleton to the device list","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.24,"slice":"core","lang":"en"} -{"prompt":"Plan and implement secure webhook signing for outbound events. First define canonicalization, key distribution, rotation, replay protection, timestamp tolerance, compatibility, and rollout; then add signing, tenant key storage, verification fixtures, and tests.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.91,"slice":"mixed","lang":"en"} -{"prompt":"Outline an architecture for privacy-preserving sign-in telemetry, covering pseudonymous identifiers, retention, sampling, regional storage, incident use, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"boundary","lang":"en"} -{"prompt":"Implement rate-limited password verification with constant-time dummy work for unknown accounts.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Replace `AuthCtx` with `AuthContext` throughout the web app without changing provider behavior or exported compatibility aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Diagnose why emailed magic links sometimes expire immediately, implement the correction after proving the clock or encoding issue, and add a support note for identifying affected links.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the CI signer upload the public certificate before the artifact? Explain the existing recovery and verification ordering; no failure is reported.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Track down the memory leak in the SAML metadata refresher after repeated certificate rotations.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write release notes for organization-level MFA enforcement, including exemptions, rollout timing, admin actions, and user-visible errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Architecture notes from the identity working group:\n\n```text\nGoal: support customer-owned identity domains\nVerification candidates: DNS TXT, HTTPS well-known file\nOne domain can belong to only one organization\nSubdomains may be claimed separately only with explicit parent policy\nVerified domains enable automatic user discovery and optional forced SSO\nDomains must be rechecked after nameserver changes\nDeletion should not instantly free a domain for another tenant\nSupport needs a reversible dispute process\nAudit must record verification attempts without storing resolver secrets\n```\n\nProduce an architecture and rollout plan covering ownership semantics, verification, caching, revalidation, takeover prevention, disputes, forced SSO safety, and migration gates. No implementation yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Give the security dashboard a useful empty state","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Turn the current administrator impersonation implementation into documentation, and separately review whether its audit, expiry, and notification behavior supports the claims in that document.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Outline a phased design for moving browser sessions from Redis to a globally replicated store, without changing code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement policy-decision caching with dependency-aware invalidation and bounded stale-deny behavior.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create an operator guide for rotating SAML certificates without breaking active logins.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Move nonce validation out of the callback handler into a dedicated verifier while preserving all accepted flows and errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why the GitHub Actions deploy job occasionally uses credentials from the previous environment.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add replay-resistant device authorization grants with polling throttles and expiry.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Set the idle session timeout to 30 minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Create the responsive SSO configuration wizard with metadata upload, field validation, connection testing, and recovery guidance.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Corrige apenas `authentification` para `authentication` no novo título da documentação.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"pt"} +{"prompt":"Review the JWT verification path for algorithm confusion, duplicate claims, key selection, critical headers, and token-size limits. Report findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement the access-review export endpoint and write its API guide. Include filters, asynchronous generation, retention, signed downloads, permissions, examples, and audit behavior.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Design a migration from shared CI runners to isolated ephemeral runners, including trust tiers, image provenance, cache policy, secret delivery, capacity, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement certificate-bound API tokens with backward-compatible bearer verification during migration.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Build the account-recovery status page with step progress, alternate paths, support escalation, and privacy-safe messaging.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Extract role-name canonicalization into one shared utility while preserving stored values and every authorization decision.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why revoked personal access tokens continue working through the GraphQL gateway, implement the verified cache fix, and document the propagation window accurately.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed OAuth device flow for phishing resistance, code entropy, polling abuse, consent clarity, and shared-device cleanup. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why a successful SAML login occasionally creates a second user instead of linking the existing account.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Draft the incident-response playbook for suspected signing-key compromise, including containment, rotation, invalidation, verification, and communication.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Workflow migration brief:\n\n```text\nRepositories: 137\nCurrent: each repo owns release YAML and long-lived cloud credentials\nTarget: reusable workflow pinned by commit digest\nLanguages: Go, Node, Python, Rust\nOutputs: containers, packages, SBOMs, provenance attestations\nConstraints:\n- regulated repos require two-person approval\n- self-hosted runners exist for hardware builds\n- hotfix releases must remain possible during control-plane outage\n- teams may adopt over two quarters\n- central workflow changes cannot silently alter release semantics\n```\n\nProduce a migration roadmap with workflow contracts, compatibility testing, exception handling, credential replacement, canaries, governance, rollback, and adoption metrics.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Add a compact layout to the permissions table","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Restructure the session-management package and document its extension points. Preserve cookie semantics, refresh timing, revocation behavior, and public APIs while separating storage, validation, and lifecycle concerns.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Architect a multi-region key-management service for application signing keys, including quorum operations, audit, disaster recovery, rotation, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement a streaming parser for large SAML metadata aggregates with signature and entity limits.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new authorization action, including naming, policy tests, audit events, and UI exposure.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Consolidate the three CSRF token stores behind one interface without changing token scope, expiry, or rotation.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why deployment approvals occasionally disappear when a pull request is rebased.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add transactional account locking with reason codes, expiry, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Pin `cosign` to `v3.0.2`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the consent-history view with policy versions, acceptance timestamps, downloadable copies, and accessible expansion.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Remplace `Authorisation` par `Authorization` uniquement dans le nouveau libellé anglais; ne touche pas aux clés i18n.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"fr"} +{"prompt":"Inspect the emergency-access implementation and explain whether an approver can authorize their own request through nested group membership.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Implement organization session-policy endpoints and produce integration documentation. Cover idle and absolute timeouts, exemptions, validation, propagation, examples, and old-client behavior.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Develop a roadmap for enforcing signed commits and protected release tags across all repositories, including bots, mirrors, emergency bypass, and audit gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add subject-token validation and audience narrowing to the RFC 8693 exchange implementation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the responsive audit-event detail panel with structured fields, raw JSON, copy actions, and redaction indicators.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"fix the permission thing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace duplicated issuer URL cleanup with one canonicalizer, preserving accepted configurations and metadata cache keys.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Diagnose why recovery-code regeneration sometimes leaves one old code valid, implement the proven transaction correction, and add a security advisory note for affected versions.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Why does the deployment controller require a fresh approval after only a documentation commit? Explain existing path filtering and trust assumptions.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Track down the occasional `invalid_state` response when two login tabs complete in reverse order.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write a customer migration guide from API keys to OAuth client credentials, with examples, rollout advice, and troubleshooting.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Threat-model excerpt:\n\n```text\nFeature: support-assisted account recovery\nSupport agent verifies ticket ownership, then requests a recovery session\nSecond agent approves for enterprise accounts\nRecovery session lasts 20 minutes and permits password reset plus MFA replacement\nCustomer receives email after completion, not before\nAgent cannot see existing MFA secrets\nAll actions enter the audit log\nOpen concerns:\n- compromised support account\n- social engineering during active incident\n- approving agent collusion\n- customer mailbox compromise\n- replaying an expired recovery-session URL\n```\n\nReview the proposed flow. Identify trust assumptions, abuse cases, missing customer controls, audit requirements, and recovery-session safeguards. No implementation requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add a loading skeleton to the device list","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Plan and implement secure webhook signing for outbound events. First define canonicalization, key distribution, rotation, replay protection, timestamp tolerance, compatibility, and rollout; then add signing, tenant key storage, verification fixtures, and tests.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Outline an architecture for privacy-preserving sign-in telemetry, covering pseudonymous identifiers, retention, sampling, regional storage, incident use, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement rate-limited password verification with constant-time dummy work for unknown accounts.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Write a reference page for the authorization decision log format, field meanings, retention, and privacy constraints.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Move SAML attribute mapping out of the login handler without changing precedence, defaults, or user provisioning.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Investigate why the production CSP report endpoint receives duplicate violations from Chromium only.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Add one-time administrator elevation tokens with approval binding and five-minute expiry.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Change the MFA grace period to 7 days","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Build the team-members page with role filters, pending invitations, bulk removal, responsive rows, and accessible confirmations.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Corrige `securty` para `security` apenas no novo nome da etapa do workflow.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"pt"} -{"prompt":"Review whether the OAuth callback logs can expose authorization codes, state tokens, or provider error descriptions. Report evidence only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Implement the API-token inventory endpoint and write its reference documentation. Include scope filtering, last-use caveats, pagination, revocation state, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.66,"slice":"mixed","lang":"en"} +{"prompt":"Investigate why the production CSP report endpoint receives duplicate violations from Chromium only.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add one-time administrator elevation tokens with approval binding and five-minute expiry.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Change the MFA grace period to 7 days","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Build the team-members page with role filters, pending invitations, bulk removal, responsive rows, and accessible confirmations.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Corrige `securty` para `security` apenas no novo nome da etapa do workflow.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"pt"} +{"prompt":"Review whether the OAuth callback logs can expose authorization codes, state tokens, or provider error descriptions. Report evidence only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement the API-token inventory endpoint and write its reference documentation. Include scope filtering, last-use caveats, pagination, revocation state, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Design a phased migration from self-signed internal certificates to a private ACME service, including bootstrap, renewal, trust rollover, outages, and retirement.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Add bounded replay storage for signed browser challenges with atomic consume semantics.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} +{"prompt":"Add bounded replay storage for signed browser challenges with atomic consume semantics.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Create the security-key management screen with device names, last-use metadata, rename, removal, and lost-key guidance.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"keep going on the UI","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.41,"slice":"vague-eval","lang":"en"} -{"prompt":"Rename `PermSet` to `PermissionSet` across packages while preserving serialized type names and public aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"Investigate the flaky CI signature verification on macOS runners, implement the verified timestamp or keychain correction, and document diagnostic steps for release engineers.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposal to put authorization scopes directly into CDN cache keys. Cover leakage, cardinality, stale grants, revocation, and correctness.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} +{"prompt":"Rename `PermSet` to `PermissionSet` across packages while preserving serialized type names and public aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Investigate the flaky CI signature verification on macOS runners, implement the verified timestamp or keychain correction, and document diagnostic steps for release engineers.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposal to put authorization scopes directly into CDN cache keys. Cover leakage, cardinality, stale grants, revocation, and correctness.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Find why group membership updates occasionally take ten minutes to affect GraphQL field authorization.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Draft a troubleshooting guide for SSO redirect loops, covering cookies, issuer mismatch, clock skew, proxies, and useful logs.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Release pipeline logs:\n\n```text\nartifact=desktop-client-8.1.0.dmg sha256=8c9e...21a\ncodesign verification=success\nnotarization status=Accepted request=7f92\nattestation subject digest=8c9e...21a\nupload multipart started artifact digest=8c9e...21a\npart 12 retry after 503\nupload completed remote digest=0d74...bc1\npromotion policy: attestation subject found=true\nchannel stable updated to remote object\nclient download checksum mismatch expected=8c9e...21a actual=0d74...bc1\n```\n\nDetermine how the promoted remote object acquired a different digest while the policy still accepted the original attestation. Trace multipart retry, finalization, and subject-to-object binding.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a copied state to the client-secret button","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.22,"slice":"core","lang":"en"} -{"prompt":"Restructure the policy compiler and document its intermediate representation. Preserve all decisions and diagnostics while separating parsing, normalization, optimization, and evaluation.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"Architect a secure delegated-administration model for resellers, including tenant boundaries, constrained roles, approval, audit, incident containment, and milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"boundary","lang":"en"} -{"prompt":"Implement Merkle-tree transparency proofs for signing-key publication.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.83,"slice":"core","lang":"en"} -{"prompt":"Create a maintainer guide for testing authentication changes across browsers, reverse proxies, and identity providers.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Extract token-expiry calculations into a shared clock-aware module without changing rounding or grace periods.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"core","lang":"en"} -{"prompt":"Investigate why the access-request badge remains stale after an approver rejects the request.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Add per-organization login rate limits with trusted-proxy-aware client keys.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Set the JWKS cache TTL to 10 minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"Build the responsive login-history page with device grouping, anomaly flags, filters, and privacy explanations.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"把新页面里的 `Permisions` 改成 `Permissions`，不要改 i18n key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"zh"} -{"prompt":"Inspect the account-linking code for session fixation, confused-deputy flows, email reassignment, and provider-subject collisions. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Implement security-event subscriptions and write the integration guide. Include event types, filtering, webhook signatures, retries, ordering, retention, and examples.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Plan a disaster-recovery strategy for identity services, including key material, session stores, provider metadata, regional failover, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"core","lang":"en"} -{"prompt":"Add deterministic policy traces with redacted inputs and stable decision-step IDs.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Create the admin invitation flow with role preview, expiry, domain warnings, resend states, and accessible validation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"do the cleanup from yesterday","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.42,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `IDPConfig` with `IdentityProviderConfig` across the codebase while preserving API field names and stored configuration.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why session revocation misses websocket connections, implement the verified lifecycle fix, and update the operator documentation with actual propagation guarantees.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.82,"slice":"mixed","lang":"en"} -{"prompt":"Explain whether a user can retain inherited access after their group is deleted. Review transaction and cache behavior only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"Track down the occasional invalid signature from the key service immediately after rotation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Write a concise architecture overview of the existing identity platform for new backend engineers.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Security review packet:\n\n```text\nFeature: shareable support-session link\nCreator: authenticated customer administrator\nRecipient: support agent\nLink grants read-only access to selected diagnostic pages for 60 minutes\nToken appears in URL fragment and is exchanged for a session cookie\nAdministrator can revoke early\nSupport identity is recorded during exchange\nLink may be opened only once\nDiagnostics can include usernames, IP addresses, and configuration values\nCurrent mockup has a Copy link button but no recipient confirmation\n```\n\nReview the design for link leakage, forwarding, one-time semantics, recipient binding, sensitive-data scope, revocation, audit, browser history, and administrator expectations. Do not implement.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Add spacing between the recovery options","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.13,"slice":"core","lang":"en"} -{"prompt":"Plan and implement organization-managed encryption keys for audit exports. Define trust, envelope encryption, rotation, access loss, validation, migration, and support boundaries first; then add the key configuration and export encryption paths.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.94,"slice":"mixed","lang":"en"} -{"prompt":"Design a phased roadmap for moving authorization checks from application code into a policy sidecar, including latency, availability, version skew, shadowing, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"boundary","lang":"en"} -{"prompt":"Implement refresh-token binding to device-held keys with migration support for existing sessions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Écris une page de référence pour les erreurs OAuth renvoyées par notre API, avec causes, sécurité et actions recommandées.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.36,"slice":"core","lang":"fr"} -{"prompt":"Consolidate the two policy-test harnesses without changing fixtures, traces, or assertion output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Investigate why Safari ignores the `Clear-Site-Data` header during logout in our embedded app flow.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Add idempotent invitation acceptance with email-change protection and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Remove the obsolete `oauth_beta` label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"core","lang":"en"} -{"prompt":"Build the policy-simulator result view with decision steps, matched rules, redacted inputs, and copyable diagnostics.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"`Authenticaton` を `Authentication` に修正して。新しい設定カードの見出しだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"ja"} -{"prompt":"Review the CI cache configuration for opportunities to poison build outputs across forks, branches, or trust levels. Report findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} +{"prompt":"Release pipeline logs:\n\n```text\nartifact=desktop-client-8.1.0.dmg sha256=8c9e...21a\ncodesign verification=success\nnotarization status=Accepted request=7f92\nattestation subject digest=8c9e...21a\nupload multipart started artifact digest=8c9e...21a\npart 12 retry after 503\nupload completed remote digest=0d74...bc1\npromotion policy: attestation subject found=true\nchannel stable updated to remote object\nclient download checksum mismatch expected=8c9e...21a actual=0d74...bc1\n```\n\nDetermine how the promoted remote object acquired a different digest while the policy still accepted the original attestation. Trace multipart retry, finalization, and subject-to-object binding.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add a copied state to the client-secret button","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Restructure the policy compiler and document its intermediate representation. Preserve all decisions and diagnostics while separating parsing, normalization, optimization, and evaluation.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Architect a secure delegated-administration model for resellers, including tenant boundaries, constrained roles, approval, audit, incident containment, and milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement Merkle-tree transparency proofs for signing-key publication.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create a maintainer guide for testing authentication changes across browsers, reverse proxies, and identity providers.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Extract token-expiry calculations into a shared clock-aware module without changing rounding or grace periods.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why the access-request badge remains stale after an approver rejects the request.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add per-organization login rate limits with trusted-proxy-aware client keys.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Set the JWKS cache TTL to 10 minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the responsive login-history page with device grouping, anomaly flags, filters, and privacy explanations.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"把新页面里的 `Permisions` 改成 `Permissions`，不要改 i18n key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"zh"} +{"prompt":"Inspect the account-linking code for session fixation, confused-deputy flows, email reassignment, and provider-subject collisions. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement security-event subscriptions and write the integration guide. Include event types, filtering, webhook signatures, retries, ordering, retention, and examples.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan a disaster-recovery strategy for identity services, including key material, session stores, provider metadata, regional failover, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add deterministic policy traces with redacted inputs and stable decision-step IDs.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the admin invitation flow with role preview, expiry, domain warnings, resend states, and accessible validation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Replace `IDPConfig` with `IdentityProviderConfig` across the codebase while preserving API field names and stored configuration.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose why session revocation misses websocket connections, implement the verified lifecycle fix, and update the operator documentation with actual propagation guarantees.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Explain whether a user can retain inherited access after their group is deleted. Review transaction and cache behavior only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Track down the occasional invalid signature from the key service immediately after rotation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write a concise architecture overview of the existing identity platform for new backend engineers.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Security review packet:\n\n```text\nFeature: shareable support-session link\nCreator: authenticated customer administrator\nRecipient: support agent\nLink grants read-only access to selected diagnostic pages for 60 minutes\nToken appears in URL fragment and is exchanged for a session cookie\nAdministrator can revoke early\nSupport identity is recorded during exchange\nLink may be opened only once\nDiagnostics can include usernames, IP addresses, and configuration values\nCurrent mockup has a Copy link button but no recipient confirmation\n```\n\nReview the design for link leakage, forwarding, one-time semantics, recipient binding, sensitive-data scope, revocation, audit, browser history, and administrator expectations. Do not implement.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add spacing between the recovery options","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Plan and implement organization-managed encryption keys for audit exports. Define trust, envelope encryption, rotation, access loss, validation, migration, and support boundaries first; then add the key configuration and export encryption paths.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Design a phased roadmap for moving authorization checks from application code into a policy sidecar, including latency, availability, version skew, shadowing, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement refresh-token binding to device-held keys with migration support for existing sessions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Écris une page de référence pour les erreurs OAuth renvoyées par notre API, avec causes, sécurité et actions recommandées.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"fr"} +{"prompt":"Consolidate the two policy-test harnesses without changing fixtures, traces, or assertion output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why Safari ignores the `Clear-Site-Data` header during logout in our embedded app flow.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add idempotent invitation acceptance with email-change protection and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remove the obsolete `oauth_beta` label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the policy-simulator result view with decision steps, matched rules, redacted inputs, and copyable diagnostics.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"`Authenticaton` を `Authentication` に修正して。新しい設定カードの見出しだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"ja"} +{"prompt":"Review the CI cache configuration for opportunities to poison build outputs across forks, branches, or trust levels. Report findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Implement administrator-consent records and write the API documentation. Include policy version, scope set, actor, expiry, revocation, pagination, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Design a double-entry ledger architecture for marketplace balances, holds, fees, refunds, disputes, and multi-currency settlement. Cover invariants, idempotency, immutable corrections, reconciliation, partitioning, audit queries, migration from mutable balance rows, and phased rollout. Produce an RFC only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"core","lang":"en"} -{"prompt":"Before implementing instant payouts, outline the end-to-end design for eligibility, funding checks, provider submission, duplicate prevention, status reconciliation, failure recovery, limits, and staged launch.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"boundary","lang":"en"} -{"prompt":"Add idempotency to `POST /v2/refunds`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Reconciliation logs from last night's close:\n\n```text\ncurrency=USD provider=stripe window=2026-07-29\ninternal gross=48199213.44 fees=1392841.18 net=46806372.26\nprovider gross=48199213.44 fees=1392841.18 net=46806372.26\nunmatched_internal=0 unmatched_provider=3\nprovider item pi_81a amount=24.00 status=refunded effective_at=23:59:58Z\nprovider item pi_91b amount=18.50 status=refunded effective_at=23:59:59Z\nprovider item pi_02c amount=90.00 status=refunded effective_at=00:00:01Z\njob shard=7 checkpoint advanced through=00:05:00Z\nnext run: unmatched_provider=0 but refund ledger entries duplicated for pi_81a and pi_91b\n```\n\nDetermine how the first run can report unmatched provider records while still advancing its checkpoint, and why the next run inserts duplicate refund entries.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Build the SwiftUI payout-details screen with status timeline, fee breakdown, destination, receipt action, pending explanation, and VoiceOver support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Plan and implement a real-time transaction-risk service. Begin with a design covering feature freshness, synchronous latency, fallback decisions, rules plus model composition, explainability, audit retention, regional failure, shadow evaluation, and rollout gates. Then add the Go decision endpoint, feature adapters, policy engine, metrics, and integration tests. Treat the risk and failure design as the primary deliverable.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.97,"slice":"mixed","lang":"en"} -{"prompt":"Set `MAX_REFUND_DAYS` to 120","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Extract duplicated money rounding from settlement and invoicing into one decimal utility while preserving every currency-specific result.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Implement `/internal/ledger/check` with trial-balance status, last verified sequence, and shard lag.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"boundary","lang":"en"} -{"prompt":"make checkout look trustworthy","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"Find why Apple Pay authorizations sometimes remain pending after the processor webhook reports success.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Explain how `PostingBatch.commit` prevents a partially balanced transaction from becoming visible. Review existing code only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Release briefing notes:\n\n```text\nFeature: partial refunds in merchant dashboard\nMerchants can refund one or more line items or enter a custom amount\nMaximum refundable amount excludes previously refunded value\nTaxes are not recalculated; refund allocation follows original tax proportions\nCard-network settlement may take 5-10 business days\nA refund cannot be cancelled after provider acceptance\nOlder API clients still receive one aggregate refunded amount\nDashboard shows pending, succeeded, or failed\nFailed refunds restore available refundable balance automatically\n```\n\nTurn this into merchant-facing release notes and a help-center article. Keep timing language qualified, explain limitations clearly, and do not imply that bank processing is controlled by us.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.47,"slice":"pasted-context","lang":"en"} -{"prompt":"Move the card-brand icon closer to the masked number","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.13,"slice":"boundary","lang":"en"} -{"prompt":"Write an operator guide for replaying payment webhooks, including filters, dry runs, idempotency, rate limits, and verification.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Implement the merchant balance endpoint with pending and available amounts, currency filtering, pagination, and authorization, then document response timing, examples, and settlement caveats.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Map out a migration from processor-specific charge tables to a provider-neutral payment-intent model, including compatibility views, backfill, dual writes, reconciliation, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"core","lang":"en"} -{"prompt":"Rename `amt` to `amount` in `FeeCalculator.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"en"} -{"prompt":"Teach the settlement worker to checkpoint each provider page and resume safely after a process restart.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Polish the invoice total section","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.29,"slice":"core","lang":"en"} -{"prompt":"Bump `opentelemetry-collector` to `0.131.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"Rename `ChargebackCase` to `DisputeCase` across services, schemas, events, and dashboards while preserving wire compatibility and runtime behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"Split `PaymentOrchestrator` into authorization, capture, refund, and provider-routing components without changing external behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Implementation ticket:\n\n```text\nPAY-4481 — reserve merchant funds for disputes\nNew states: requested, reserved, released, collected\nInputs: merchant account, dispute ID, amount, currency, reason\nRules:\n- one active reserve per dispute\n- reserve cannot exceed available merchant balance\n- partial reserve allowed when policy says so\n- release and collect are mutually exclusive terminal operations\n- every transition writes a ledger transaction and audit event atomically\n- duplicate commands return the prior result\n- provider callbacks may arrive before the create request completes\n- expose transition latency and insufficient-funds counters\nExisting packages: `ledger/postings`, `disputes/service`\n```\n\nImplement the state model, commands, ledger integration, callback handling, persistence, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"Investigate why the Grafana checkout-latency panel shows gaps while raw Prometheus queries contain samples.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Create the dispute-evidence upload UI and add a short guide explaining supported files, deadlines, upload state, and submission finality.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.66,"slice":"mixed","lang":"en"} -{"prompt":"Why does the invoice service record exchange rates at authorization time instead of settlement time? Explain the current semantics; no change requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.48,"slice":"core","lang":"en"} -{"prompt":"Rewrite the local observability setup for running Grafana, Tempo, Loki, and the demo traffic generator.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.34,"slice":"core","lang":"en"} -{"prompt":"After the tracing migration, this test intermittently times out:\n\n```text\nFAIL TestCaptureSpanLinksToAuthorization\nexpected one span link, found zero\ntrace authorization trace_id=0fa1 span_id=11ac sampled=true\nqueue message traceparent=00-0fa1-11ac-01\ncapture worker extracted trace_id=0fa1 parent=11ac\nexporter batch flush interval=5s\ncollector received capture span before authorization span\nquery by trace_id at t+2s returned capture only\nquery at t+7s returned both with link present\n```\n\nDetermine whether context propagation is wrong or the test assumes exporter ordering that is not guaranteed. Explain what evidence distinguishes ingestion delay from a missing link.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.69,"slice":"boundary","lang":"en"} -{"prompt":"finish the settlement endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"Propose an architecture for multi-currency merchant balances, including conversion timing, rate sources, rounding, exposure limits, accounting, and staged adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"core","lang":"en"} -{"prompt":"Add ISO 20022 statement parsing to the reconciliation CLI","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Code review excerpt:\n\n```diff\n func (s *Service) Refund(ctx context.Context, paymentID string, amount Money) error {\n- return s.db.WithTx(ctx, func(tx Tx) error {\n- if err := tx.InsertRefund(paymentID, amount); err != nil { return err }\n- return tx.InsertLedgerEntries(paymentID, amount)\n- })\n+ if err := s.db.InsertRefund(ctx, paymentID, amount); err != nil { return err }\n+ go s.ledger.PostRefund(context.Background(), paymentID, amount)\n+ return nil\n }\n```\n\nThe author says asynchronous posting improves latency. Review consistency, crash windows, duplicate delivery, cancellation, observability, and what callers can infer from success. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.72,"slice":"pasted-context","lang":"en"} -{"prompt":"Schreibe eine kurze Betriebsdokumentation für die bestehende manuelle Abrechnungskorrektur, einschließlich Genehmigung, Audit und Rückgängigmachung. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"boundary","lang":"de"} -{"prompt":"Build the web transaction explorer with saved queries, virtualized rows, expandable ledger entries, and accessible amount formatting.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Review how the current alert router groups payment incidents, then turn the findings into an on-call guide with grouping examples and tuning advice.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"Set the trace sampling ratio to `0.05`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"Benenne `PayoutMgr` im gesamten Repository in `PayoutManager` um; APIs, Datenbankfelder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"de"} -{"prompt":"Consolidate the three provider-error translators while preserving public error codes, retry decisions, and logs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Diagnose the duplicate settlement alert","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"Explain how the metrics gateway prevents one merchant's labels from creating unbounded cardinality.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Create API documentation for the existing payout-estimate endpoint, including fees, exchange rates, expiry, and validation errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"boundary","lang":"en"} -{"prompt":"Plan the migration from daily batch settlement to continuous settlement, covering ledger invariants, provider windows, liquidity, reconciliation, observability, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Product ticket:\n\n```text\nScreen: merchant cash-flow overview\nCards: available balance, pending balance, next payout, reserves\nChart: net inflow by day/week/month with comparison period\nTable: recent balance-affecting activity\nFilters: currency, business unit, settlement account\nStates: no transactions, delayed provider data, partial outage, loading\nMoney rules: always pair symbol with currency code when currencies are mixed\nAccessibility: chart has tabular alternative; gains/losses not color-only\nResponsive: cards become horizontal snap list below 640px\nAPI already returns minor units and ISO currency\n```\n\nImplement the dashboard and component tests without changing balance calculations.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.75,"slice":"pasted-context","lang":"en"} -{"prompt":"Implement `POST /v1/settlements/{id}/retry` with state validation, idempotency, authorization, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"boundary","lang":"en"} -{"prompt":"Remove the stale `beta` badge from payouts","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"core","lang":"en"} -{"prompt":"Fix the clipped currency code in compact rows and extract the duplicated amount-width rule into the shared table styles.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.38,"slice":"mixed","lang":"en"} -{"prompt":"Replace scattered reconciliation status flags with one explicit state enum while preserving transitions and metrics.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Cambia `txnAmt` por `transactionAmount` solo en `ReceiptMapper.ts`; no modifiques cálculos.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"es"} -{"prompt":"Investigate why the Android receipt screen occasionally shows a previous customer's billing address.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Summarize the existing fee-calculation pipeline for finance reviewers, using implementation and tests as evidence.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"Develop a capacity roadmap for retaining seven years of transaction telemetry. Include storage tiers, query SLAs, cardinality budgets, deletion exceptions, cost gates, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"core","lang":"en"} -{"prompt":"Implement transactional invoice-number allocation with per-jurisdiction sequences and gap auditability.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Create the Compose subscription-management screen with plan comparison, proration preview, payment method, confirmation, and TalkBack support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Fix `curreny` in `fees.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} -{"prompt":"Merge the duplicate histogram wrappers used by checkout and payout services without changing bucket boundaries or metric names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Production traces around the latency spike:\n\n```text\nroute=/v1/checkout p99=4.8s baseline=420ms\nspan fraud.evaluate duration=72ms\nspan payment.authorize duration=301ms\nspan ledger.reserve duration=4012ms\npostgres wait_event=Lock transactionid\nblocked pid=8124 blocker pid=7991\nblocker query='UPDATE merchant_balances SET pending=pending+$1 WHERE merchant_id=$2'\nblocker state='idle in transaction' xact_age=00:00:04.812\napplication span associated with blocker ended at +312ms\nconnection returned to pool at +313ms\n```\n\nDetermine how a connection with an open transaction returned to the pool and why the completed application span hides the remaining lock lifetime.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Rename `reciept_url` to `receipt_url` in the unreleased migration.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"boundary","lang":"en"} -{"prompt":"Assess whether `Money.allocate` distributes remainder cents fairly and deterministically across repeated calls. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.56,"slice":"core","lang":"en"} -{"prompt":"Restructure the telemetry SDK into tracing, metrics, logging, and resource packages, then write a maintainer note. Preserve public exports and emitted data.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.77,"slice":"mixed","lang":"en"} -{"prompt":"Plan the retirement of legacy card tokens, covering inventory, customer vault migration, network-token compatibility, fallback, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"core","lang":"en"} +{"prompt":"Design a double-entry ledger architecture for marketplace balances, holds, fees, refunds, disputes, and multi-currency settlement. Cover invariants, idempotency, immutable corrections, reconciliation, partitioning, audit queries, migration from mutable balance rows, and phased rollout. Produce an RFC only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Before implementing instant payouts, outline the end-to-end design for eligibility, funding checks, provider submission, duplicate prevention, status reconciliation, failure recovery, limits, and staged launch.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add idempotency to `POST /v2/refunds`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Reconciliation logs from last night's close:\n\n```text\ncurrency=USD provider=stripe window=2026-07-29\ninternal gross=48199213.44 fees=1392841.18 net=46806372.26\nprovider gross=48199213.44 fees=1392841.18 net=46806372.26\nunmatched_internal=0 unmatched_provider=3\nprovider item pi_81a amount=24.00 status=refunded effective_at=23:59:58Z\nprovider item pi_91b amount=18.50 status=refunded effective_at=23:59:59Z\nprovider item pi_02c amount=90.00 status=refunded effective_at=00:00:01Z\njob shard=7 checkpoint advanced through=00:05:00Z\nnext run: unmatched_provider=0 but refund ledger entries duplicated for pi_81a and pi_91b\n```\n\nDetermine how the first run can report unmatched provider records while still advancing its checkpoint, and why the next run inserts duplicate refund entries.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Build the SwiftUI payout-details screen with status timeline, fee breakdown, destination, receipt action, pending explanation, and VoiceOver support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Plan and implement a real-time transaction-risk service. Begin with a design covering feature freshness, synchronous latency, fallback decisions, rules plus model composition, explainability, audit retention, regional failure, shadow evaluation, and rollout gates. Then add the Go decision endpoint, feature adapters, policy engine, metrics, and integration tests. Treat the risk and failure design as the primary deliverable.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":1.0,"slice":"mixed","lang":"en"} +{"prompt":"Set `MAX_REFUND_DAYS` to 120","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Extract duplicated money rounding from settlement and invoicing into one decimal utility while preserving every currency-specific result.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Implement `/internal/ledger/check` with trial-balance status, last verified sequence, and shard lag.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"make checkout look trustworthy","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Find why Apple Pay authorizations sometimes remain pending after the processor webhook reports success.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Explain how `PostingBatch.commit` prevents a partially balanced transaction from becoming visible. Review existing code only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Release briefing notes:\n\n```text\nFeature: partial refunds in merchant dashboard\nMerchants can refund one or more line items or enter a custom amount\nMaximum refundable amount excludes previously refunded value\nTaxes are not recalculated; refund allocation follows original tax proportions\nCard-network settlement may take 5-10 business days\nA refund cannot be cancelled after provider acceptance\nOlder API clients still receive one aggregate refunded amount\nDashboard shows pending, succeeded, or failed\nFailed refunds restore available refundable balance automatically\n```\n\nTurn this into merchant-facing release notes and a help-center article. Keep timing language qualified, explain limitations clearly, and do not imply that bank processing is controlled by us.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} +{"prompt":"Move the card-brand icon closer to the masked number","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Write an operator guide for replaying payment webhooks, including filters, dry runs, idempotency, rate limits, and verification.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement the merchant balance endpoint with pending and available amounts, currency filtering, pagination, and authorization, then document response timing, examples, and settlement caveats.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Map out a migration from processor-specific charge tables to a provider-neutral payment-intent model, including compatibility views, backfill, dual writes, reconciliation, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Rename `amt` to `amount` in `FeeCalculator.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Teach the settlement worker to checkpoint each provider page and resume safely after a process restart.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Polish the invoice total section","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump `opentelemetry-collector` to `0.131.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename `ChargebackCase` to `DisputeCase` across services, schemas, events, and dashboards while preserving wire compatibility and runtime behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Split `PaymentOrchestrator` into authorization, capture, refund, and provider-routing components without changing external behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implementation ticket:\n\n```text\nPAY-4481 — reserve merchant funds for disputes\nNew states: requested, reserved, released, collected\nInputs: merchant account, dispute ID, amount, currency, reason\nRules:\n- one active reserve per dispute\n- reserve cannot exceed available merchant balance\n- partial reserve allowed when policy says so\n- release and collect are mutually exclusive terminal operations\n- every transition writes a ledger transaction and audit event atomically\n- duplicate commands return the prior result\n- provider callbacks may arrive before the create request completes\n- expose transition latency and insufficient-funds counters\nExisting packages: `ledger/postings`, `disputes/service`\n```\n\nImplement the state model, commands, ledger integration, callback handling, persistence, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Investigate why the Grafana checkout-latency panel shows gaps while raw Prometheus queries contain samples.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Create the dispute-evidence upload UI and add a short guide explaining supported files, deadlines, upload state, and submission finality.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Why does the invoice service record exchange rates at authorization time instead of settlement time? Explain the current semantics; no change requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Rewrite the local observability setup for running Grafana, Tempo, Loki, and the demo traffic generator.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"After the tracing migration, this test intermittently times out:\n\n```text\nFAIL TestCaptureSpanLinksToAuthorization\nexpected one span link, found zero\ntrace authorization trace_id=0fa1 span_id=11ac sampled=true\nqueue message traceparent=00-0fa1-11ac-01\ncapture worker extracted trace_id=0fa1 parent=11ac\nexporter batch flush interval=5s\ncollector received capture span before authorization span\nquery by trace_id at t+2s returned capture only\nquery at t+7s returned both with link present\n```\n\nDetermine whether context propagation is wrong or the test assumes exporter ordering that is not guaranteed. Explain what evidence distinguishes ingestion delay from a missing link.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"finish the settlement endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Propose an architecture for multi-currency merchant balances, including conversion timing, rate sources, rounding, exposure limits, accounting, and staged adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add ISO 20022 statement parsing to the reconciliation CLI","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Code review excerpt:\n\n```diff\n func (s *Service) Refund(ctx context.Context, paymentID string, amount Money) error {\n- return s.db.WithTx(ctx, func(tx Tx) error {\n- if err := tx.InsertRefund(paymentID, amount); err != nil { return err }\n- return tx.InsertLedgerEntries(paymentID, amount)\n- })\n+ if err := s.db.InsertRefund(ctx, paymentID, amount); err != nil { return err }\n+ go s.ledger.PostRefund(context.Background(), paymentID, amount)\n+ return nil\n }\n```\n\nThe author says asynchronous posting improves latency. Review consistency, crash windows, duplicate delivery, cancellation, observability, and what callers can infer from success. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Schreibe eine kurze Betriebsdokumentation für die bestehende manuelle Abrechnungskorrektur, einschließlich Genehmigung, Audit und Rückgängigmachung. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"de"} +{"prompt":"Build the web transaction explorer with saved queries, virtualized rows, expandable ledger entries, and accessible amount formatting.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Review how the current alert router groups payment incidents, then turn the findings into an on-call guide with grouping examples and tuning advice.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Set the trace sampling ratio to `0.05`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Benenne `PayoutMgr` im gesamten Repository in `PayoutManager` um; APIs, Datenbankfelder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} +{"prompt":"Consolidate the three provider-error translators while preserving public error codes, retry decisions, and logs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose the duplicate settlement alert","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Explain how the metrics gateway prevents one merchant's labels from creating unbounded cardinality.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Create API documentation for the existing payout-estimate endpoint, including fees, exchange rates, expiry, and validation errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Plan the migration from daily batch settlement to continuous settlement, covering ledger invariants, provider windows, liquidity, reconciliation, observability, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Product ticket:\n\n```text\nScreen: merchant cash-flow overview\nCards: available balance, pending balance, next payout, reserves\nChart: net inflow by day/week/month with comparison period\nTable: recent balance-affecting activity\nFilters: currency, business unit, settlement account\nStates: no transactions, delayed provider data, partial outage, loading\nMoney rules: always pair symbol with currency code when currencies are mixed\nAccessibility: chart has tabular alternative; gains/losses not color-only\nResponsive: cards become horizontal snap list below 640px\nAPI already returns minor units and ISO currency\n```\n\nImplement the dashboard and component tests without changing balance calculations.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Implement `POST /v1/settlements/{id}/retry` with state validation, idempotency, authorization, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remove the stale `beta` badge from payouts","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fix the clipped currency code in compact rows and extract the duplicated amount-width rule into the shared table styles.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Replace scattered reconciliation status flags with one explicit state enum while preserving transitions and metrics.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Cambia `txnAmt` por `transactionAmount` solo en `ReceiptMapper.ts`; no modifiques cálculos.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"es"} +{"prompt":"Investigate why the Android receipt screen occasionally shows a previous customer's billing address.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Summarize the existing fee-calculation pipeline for finance reviewers, using implementation and tests as evidence.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Develop a capacity roadmap for retaining seven years of transaction telemetry. Include storage tiers, query SLAs, cardinality budgets, deletion exceptions, cost gates, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement transactional invoice-number allocation with per-jurisdiction sequences and gap auditability.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create the Compose subscription-management screen with plan comparison, proration preview, payment method, confirmation, and TalkBack support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Fix `curreny` in `fees.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Merge the duplicate histogram wrappers used by checkout and payout services without changing bucket boundaries or metric names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Production traces around the latency spike:\n\n```text\nroute=/v1/checkout p99=4.8s baseline=420ms\nspan fraud.evaluate duration=72ms\nspan payment.authorize duration=301ms\nspan ledger.reserve duration=4012ms\npostgres wait_event=Lock transactionid\nblocked pid=8124 blocker pid=7991\nblocker query='UPDATE merchant_balances SET pending=pending+$1 WHERE merchant_id=$2'\nblocker state='idle in transaction' xact_age=00:00:04.812\napplication span associated with blocker ended at +312ms\nconnection returned to pool at +313ms\n```\n\nDetermine how a connection with an open transaction returned to the pool and why the completed application span hides the remaining lock lifetime.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Rename `reciept_url` to `receipt_url` in the unreleased migration.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Assess whether `Money.allocate` distributes remainder cents fairly and deterministically across repeated calls. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Restructure the telemetry SDK into tracing, metrics, logging, and resource packages, then write a maintainer note. Preserve public exports and emitted data.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan the retirement of legacy card tokens, covering inventory, customer vault migration, network-token compatibility, fallback, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Add provider-independent dispute status normalization with unknown-state preservation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Build the mobile spending-limit editor with period selection, amount validation, usage preview, and confirmation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"do the payment UI","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.42,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `TxnID` with `TransactionID` across the Go services while preserving JSON tags, database names, and protobuf fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why exported invoices occasionally omit tax registration numbers, implement the verified rendering fix, and add a support note for regenerating affected documents.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Why does the observability agent batch logs by bytes rather than event count? Explain the existing choice and tradeoffs.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.43,"slice":"boundary","lang":"en"} -{"prompt":"Track down the steady increase in Tempo ingester memory after enabling span events.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Write release notes for configurable payout schedules, including eligibility, cutoffs, holidays, and rollback to the default.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"core","lang":"en"} +{"prompt":"Build the mobile spending-limit editor with period selection, amount validation, usage preview, and confirmation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"do the payment UI","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `TxnID` with `TransactionID` across the Go services while preserving JSON tags, database names, and protobuf fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose why exported invoices occasionally omit tax registration numbers, implement the verified rendering fix, and add a support note for regenerating affected documents.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the observability agent batch logs by bytes rather than event count? Explain the existing choice and tradeoffs.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down the steady increase in Tempo ingester memory after enabling span events.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write release notes for configurable payout schedules, including eligibility, cutoffs, holidays, and rollback to the default.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Settlement redesign notes:\n\n```text\nCurrent: one settlement account per merchant and currency\nNew need: multiple bank accounts with percentage or priority routing\nConstraints:\n- percentages must total 100 for percentage mode\n- priority mode fills daily account caps in order\n- routing configuration changes take effect next settlement window\n- in-flight settlements keep their original routing snapshot\n- closed accounts must not receive new funds\n- finance requires reproducible historical calculations\n- old API clients understand only one destination\n- rollback must preserve destination decisions already made\n```\n\nProduce an implementation-free design and migration plan covering data model, versioning, validation, compatibility, auditability, rollout, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Give the observability status page a clearer hierarchy","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.34,"slice":"core","lang":"en"} -{"prompt":"Turn the existing payment retry logic into merchant documentation, then review whether the documented timing and idempotency claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Outline a phased design for moving tracing storage from Elasticsearch to ClickHouse, without implementing collectors or queries yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.85,"slice":"boundary","lang":"en"} -{"prompt":"Implement reversible ledger corrections using explicit reversal and replacement postings.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"en"} -{"prompt":"Create an operator guide for handling provider webhook backlogs without double-processing payments.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} +{"prompt":"Give the observability status page a clearer hierarchy","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Turn the existing payment retry logic into merchant documentation, then review whether the documented timing and idempotency claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Outline a phased design for moving tracing storage from Elasticsearch to ClickHouse, without implementing collectors or queries yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement reversible ledger corrections using explicit reversal and replacement postings.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create an operator guide for handling provider webhook backlogs without double-processing payments.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Move currency metadata out of `FeeService` into an immutable registry while preserving rounding and validation.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Investigate why one Prometheus remote-write shard remains hours behind while adjacent shards are current.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.69,"slice":"boundary","lang":"en"} -{"prompt":"Add idempotent provider-callback ingestion with raw-payload retention and signature status.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Set the default invoice terms to 30 days","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Create the responsive payment-method picker with card, bank, wallet, disabled states, and accessible selection.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Corrige apenas `settlemnt` para `settlement` no novo alerta.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"pt"} -{"prompt":"Review the payout CSV export for formula injection, delimiter ambiguity, encoding issues, and unredacted bank data. Findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Implement the settlement-calendar endpoint and write its API guide. Include currencies, holidays, cutoffs, time zones, estimates, examples, and data freshness.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Design a migration from direct provider API calls to an internal payment-routing platform, covering contracts, shadowing, reconciliation, failure isolation, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"core","lang":"en"} -{"prompt":"Implement bounded-cardinality exemplar attachment for high-latency payment spans.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Build the desktop trace waterfall with virtualized spans, critical-path highlighting, search, and accessible duration summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"continue the refund stuff","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} -{"prompt":"Extract provider capability detection into one registry while preserving routing decisions and fallback order.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why subscription renewals occasionally create two invoices, implement the proven locking or idempotency correction, and document how support should merge affected records.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.85,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposal to derive SLOs directly from trace data. Cover sampling bias, missing spans, tail latency, cost, and alert stability.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Find why one checkout worker stops consuming after the Kafka group rebalances.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Draft the incident runbook for a payment processor outage, including failover criteria, queue handling, customer messaging, and reconciliation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} -{"prompt":"Observability migration brief:\n\n```text\nCurrent agents: OpenTelemetry Collector 0.104 through 0.128\nTarget distribution includes custom redaction and tenant-routing processors\nFleet: 11,000 Kubernetes daemon pods plus 2,400 VM services\nConfig delivered through GitOps for clusters and SSM for VMs\nBreaking changes: deprecated logging exporter removed; queue settings renamed\nRequirements:\n- no tenant can receive another tenant's telemetry\n- rollback within 20 minutes\n- validate config before restart\n- staged rollout by environment and region\n- compare drop, retry, and export latency before promotion\n```\n\nProduce a fleet migration roadmap with compatibility shims, validation, canaries, telemetry parity, security gates, rollback, and ownership.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"Add sticky totals to the settlement table","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} +{"prompt":"Investigate why one Prometheus remote-write shard remains hours behind while adjacent shards are current.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add idempotent provider-callback ingestion with raw-payload retention and signature status.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Set the default invoice terms to 30 days","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Create the responsive payment-method picker with card, bank, wallet, disabled states, and accessible selection.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Corrige apenas `settlemnt` para `settlement` no novo alerta.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"pt"} +{"prompt":"Review the payout CSV export for formula injection, delimiter ambiguity, encoding issues, and unredacted bank data. Findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement the settlement-calendar endpoint and write its API guide. Include currencies, holidays, cutoffs, time zones, estimates, examples, and data freshness.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Design a migration from direct provider API calls to an internal payment-routing platform, covering contracts, shadowing, reconciliation, failure isolation, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement bounded-cardinality exemplar attachment for high-latency payment spans.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Build the desktop trace waterfall with virtualized spans, critical-path highlighting, search, and accessible duration summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Extract provider capability detection into one registry while preserving routing decisions and fallback order.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why subscription renewals occasionally create two invoices, implement the proven locking or idempotency correction, and document how support should merge affected records.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposal to derive SLOs directly from trace data. Cover sampling bias, missing spans, tail latency, cost, and alert stability.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why one checkout worker stops consuming after the Kafka group rebalances.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Draft the incident runbook for a payment processor outage, including failover criteria, queue handling, customer messaging, and reconciliation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Observability migration brief:\n\n```text\nCurrent agents: OpenTelemetry Collector 0.104 through 0.128\nTarget distribution includes custom redaction and tenant-routing processors\nFleet: 11,000 Kubernetes daemon pods plus 2,400 VM services\nConfig delivered through GitOps for clusters and SSM for VMs\nBreaking changes: deprecated logging exporter removed; queue settings renamed\nRequirements:\n- no tenant can receive another tenant's telemetry\n- rollback within 20 minutes\n- validate config before restart\n- staged rollout by environment and region\n- compare drop, retry, and export latency before promotion\n```\n\nProduce a fleet migration roadmap with compatibility shims, validation, canaries, telemetry parity, security gates, rollback, and ownership.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add sticky totals to the settlement table","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Restructure the reconciliation engine and document its extension interface. Preserve matching results and reports while separating ingestion, normalization, matching, and posting.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Architect a multi-region ledger with single-writer ownership per account, including transfers, failover, audit, reconciliation, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.98,"slice":"boundary","lang":"en"} -{"prompt":"Implement cryptographic receipt chaining for immutable transaction history.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new payment provider, including capabilities, sandbox tests, webhooks, reconciliation, and launch gates.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"Consolidate the checkout and invoice address validators without changing accepted inputs or errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Investigate why alert silences disappear after one Alertmanager replica restarts.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional daily spending-limit enforcement with reservation and release semantics.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Pin Grafana to `12.1.1`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Build the merchant tax-information form with country-specific fields, validation, document upload, and save recovery.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Remplace `Paiments` par `Payments` uniquement dans le nouveau titre de navigation.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"fr"} -{"prompt":"Inspect the webhook signature verifier for duplicate headers, timestamp parsing, body canonicalization, and timing leakage. Report only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Implement merchant reserve history and write the API documentation. Include transitions, balances, pagination, timestamps, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.67,"slice":"mixed","lang":"en"} -{"prompt":"Develop a roadmap for replacing static alert thresholds with multi-window burn-rate alerts, including SLO inventory, validation, training, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"Add incremental settlement-report generation with checkpoints and stable row ordering.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Create the responsive observability service map with traffic edges, error overlays, time controls, and text alternatives.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"fix the dashboard numbers","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.53,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `PaymentCtx` with `PaymentContext` across packages while preserving serialized fields and public aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why payout emails display the wrong local settlement date, implement the verified timezone fix, and add a release note for affected regions.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.74,"slice":"mixed","lang":"en"} -{"prompt":"Why does the metrics pipeline retain out-of-order samples for ten minutes before rejecting them? Explain existing behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.48,"slice":"boundary","lang":"en"} -{"prompt":"Track down missing spans between the GraphQL resolver and payment service on only retried requests.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Write a migration guide from legacy balance fields to the new ledger-backed balance API.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} -{"prompt":"Design review notes:\n\n```text\nFeature: negative merchant balances\nTrigger: refunds or disputes exceed available funds\nProposal: represent debt in the same balance account using signed amounts\nFuture deposits automatically offset debt before becoming available\nPayouts disabled while available balance is negative\nFinance may create a repayment plan outside the ledger\nConstraints:\n- statements must clearly distinguish debt from pending holds\n- old API clients assume balance is non-negative\n- accounting exports require separate liability classification\n- manual corrections must remain auditable\n- cross-currency debt cannot be netted automatically\n```\n\nReview the proposed semantics for accounting correctness, API compatibility, statements, repayment, currency isolation, and correction behavior. No implementation requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Add an empty state to the payout chart","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} +{"prompt":"Architect a multi-region ledger with single-writer ownership per account, including transfers, failover, audit, reconciliation, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement cryptographic receipt chaining for immutable transaction history.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new payment provider, including capabilities, sandbox tests, webhooks, reconciliation, and launch gates.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Consolidate the checkout and invoice address validators without changing accepted inputs or errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why alert silences disappear after one Alertmanager replica restarts.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add transactional daily spending-limit enforcement with reservation and release semantics.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Pin Grafana to `12.1.1`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the merchant tax-information form with country-specific fields, validation, document upload, and save recovery.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remplace `Paiments` par `Payments` uniquement dans le nouveau titre de navigation.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"fr"} +{"prompt":"Inspect the webhook signature verifier for duplicate headers, timestamp parsing, body canonicalization, and timing leakage. Report only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement merchant reserve history and write the API documentation. Include transitions, balances, pagination, timestamps, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Develop a roadmap for replacing static alert thresholds with multi-window burn-rate alerts, including SLO inventory, validation, training, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add incremental settlement-report generation with checkpoints and stable row ordering.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the responsive observability service map with traffic edges, error overlays, time controls, and text alternatives.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"fix the dashboard numbers","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `PaymentCtx` with `PaymentContext` across packages while preserving serialized fields and public aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose why payout emails display the wrong local settlement date, implement the verified timezone fix, and add a release note for affected regions.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the metrics pipeline retain out-of-order samples for ten minutes before rejecting them? Explain existing behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down missing spans between the GraphQL resolver and payment service on only retried requests.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write a migration guide from legacy balance fields to the new ledger-backed balance API.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Design review notes:\n\n```text\nFeature: negative merchant balances\nTrigger: refunds or disputes exceed available funds\nProposal: represent debt in the same balance account using signed amounts\nFuture deposits automatically offset debt before becoming available\nPayouts disabled while available balance is negative\nFinance may create a repayment plan outside the ledger\nConstraints:\n- statements must clearly distinguish debt from pending holds\n- old API clients assume balance is non-negative\n- accounting exports require separate liability classification\n- manual corrections must remain auditable\n- cross-currency debt cannot be netted automatically\n```\n\nReview the proposed semantics for accounting correctness, API compatibility, statements, repayment, currency isolation, and correction behavior. No implementation requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add an empty state to the payout chart","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Plan and implement customer-managed webhook endpoints. First define verification, delivery guarantees, secrets, rotation, retries, observability, deletion, and migration; then build CRUD, delivery, and test-event paths.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"Outline an architecture for real-time financial anomaly detection, including streaming state, explainability, human review, replay, and phased validation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"boundary","lang":"en"} +{"prompt":"Outline an architecture for real-time financial anomaly detection, including streaming state, explainability, human review, replay, and phased validation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Implement invoice PDF generation with deterministic layout inputs and immutable artifact versioning.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Escribe una página de referencia para los códigos de error de pagos, con causas, reintentos seguros y pasos de soporte.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"es"} -{"prompt":"Move trace resource normalization out of the collector exporter while preserving emitted attributes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Investigate why card-present refunds time out even though the terminal confirms completion.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Add atomic capture splitting across multiple fulfillment shipments.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Remove the deprecated `trace_id_128` setting","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"core","lang":"en"} +{"prompt":"Escribe una página de referencia para los códigos de error de pagos, con causas, reintentos seguros y pasos de soporte.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} +{"prompt":"Move trace resource normalization out of the collector exporter while preserving emitted attributes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why card-present refunds time out even though the terminal confirms completion.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add atomic capture splitting across multiple fulfillment shipments.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remove the deprecated `trace_id_128` setting","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"Build the invoice-preview pane with page thumbnails, zoom, download, and accessible document metadata.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"`Paymant failed` を `Payment failed` に直して。英語の新しいエラー文だけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"ja"} -{"prompt":"Review the refund authorization path for confused-deputy access, amount tampering, stale permissions, and audit completeness.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Implement reconciliation discrepancy exports and write the integration guide. Include filters, asynchronous jobs, retention, signed URLs, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Plan a disaster-recovery strategy for payment processing, including provider outages, ledger restoration, webhook replay, keys, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Add transaction-level trace correlation to ledger postings without exposing financial data in attributes.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Create the mobile refund flow with amount selection, item allocation, reason, confirmation, progress, and final states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"keep going with telemetry","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.47,"slice":"vague-eval","lang":"en"} -{"prompt":"Rename `ObsConfig` to `ObservabilityConfig` across the monorepo while preserving YAML keys and environment variables.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why successful bank transfers remain in processing after webhook delivery, implement the verified state-mapping correction, and update support documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposal to use log-derived metrics for payout success. Cover missing logs, retries, cardinality, semantics, and alert reliability.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.64,"slice":"boundary","lang":"en"} -{"prompt":"Find why the metrics agent duplicates samples after recovering its disk queue.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Draft a customer guide for interpreting pending, available, reserved, and negative balances.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.36,"slice":"core","lang":"en"} -{"prompt":"Alert incident excerpt:\n\n```text\nalert=PayoutFailureRateHigh state=firing\nquery=sum(rate(payout_failed_total[5m])) / sum(rate(payout_attempt_total[5m])) > 0.03\nregion=eu-west attempts=0 failures=0\nPrometheus result=NaN\nrule engine comparison: NaN > 0.03 returned true after migration\nnotification repeated every 2m\ninhibit rule expected to suppress when PayoutTrafficAbsent is firing\nPayoutTrafficAbsent label set includes provider=all\nfailure alert label set excludes provider\nAlertmanager inhibition equal labels=[region, provider]\n```\n\nDetermine why a no-traffic window fires the failure-rate alert and why the inhibition does not match. Separate query semantics from label-set configuration.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"pasted-context","lang":"en"} -{"prompt":"Add comparison labels to the fee chart","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.28,"slice":"core","lang":"en"} -{"prompt":"Restructure the invoice pipeline and document its renderer interface. Preserve generated PDFs while separating data assembly, localization, layout, and storage.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"Design a regulatory reporting platform for multiple jurisdictions, including source lineage, corrections, approvals, immutable submissions, and rollout milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"boundary","lang":"en"} -{"prompt":"Implement append-only audit proofs for manual ledger adjustments.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new observability exporter, including configuration, queues, retries, redaction, and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Consolidate payout date calculation across API and worker packages without changing holiday behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Investigate why exemplars vanish when metrics pass through the regional federation tier.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Add dispute-evidence retention enforcement with legal holds and deletion audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Set the invoice PDF margin to 24mm","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"Build the responsive reconciliation workspace with matched groups, discrepancy filters, manual linking, and undo.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"把 `Settelment` 改成 `Settlement`，只改新页面标题，不要改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"zh"} -{"prompt":"Inspect the manual-adjustment endpoint for amount overflow, currency mismatch, stale approvals, replay, and audit gaps. Findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} +{"prompt":"`Paymant failed` を `Payment failed` に直して。英語の新しいエラー文だけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"ja"} +{"prompt":"Review the refund authorization path for confused-deputy access, amount tampering, stale permissions, and audit completeness.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement reconciliation discrepancy exports and write the integration guide. Include filters, asynchronous jobs, retention, signed URLs, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan a disaster-recovery strategy for payment processing, including provider outages, ledger restoration, webhook replay, keys, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add transaction-level trace correlation to ledger postings without exposing financial data in attributes.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the mobile refund flow with amount selection, item allocation, reason, confirmation, progress, and final states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Rename `ObsConfig` to `ObservabilityConfig` across the monorepo while preserving YAML keys and environment variables.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Investigate why successful bank transfers remain in processing after webhook delivery, implement the verified state-mapping correction, and update support documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposal to use log-derived metrics for payout success. Cover missing logs, retries, cardinality, semantics, and alert reliability.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why the metrics agent duplicates samples after recovering its disk queue.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Draft a customer guide for interpreting pending, available, reserved, and negative balances.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Alert incident excerpt:\n\n```text\nalert=PayoutFailureRateHigh state=firing\nquery=sum(rate(payout_failed_total[5m])) / sum(rate(payout_attempt_total[5m])) > 0.03\nregion=eu-west attempts=0 failures=0\nPrometheus result=NaN\nrule engine comparison: NaN > 0.03 returned true after migration\nnotification repeated every 2m\ninhibit rule expected to suppress when PayoutTrafficAbsent is firing\nPayoutTrafficAbsent label set includes provider=all\nfailure alert label set excludes provider\nAlertmanager inhibition equal labels=[region, provider]\n```\n\nDetermine why a no-traffic window fires the failure-rate alert and why the inhibition does not match. Separate query semantics from label-set configuration.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Add comparison labels to the fee chart","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Restructure the invoice pipeline and document its renderer interface. Preserve generated PDFs while separating data assembly, localization, layout, and storage.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Design a regulatory reporting platform for multiple jurisdictions, including source lineage, corrections, approvals, immutable submissions, and rollout milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement append-only audit proofs for manual ledger adjustments.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new observability exporter, including configuration, queues, retries, redaction, and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Consolidate payout date calculation across API and worker packages without changing holiday behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Investigate why exemplars vanish when metrics pass through the regional federation tier.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add dispute-evidence retention enforcement with legal holds and deletion audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Set the invoice PDF margin to 24mm","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the responsive reconciliation workspace with matched groups, discrepancy filters, manual linking, and undo.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"把 `Settelment` 改成 `Settlement`，只改新页面标题，不要改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"zh"} +{"prompt":"Inspect the manual-adjustment endpoint for amount overflow, currency mismatch, stale approvals, replay, and audit gaps. Findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Implement payout destination verification and write its API documentation. Include challenge states, expiry, retries, lockouts, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Design an incremental compilation architecture for the Orion language server. Cover dependency invalidation, generated sources, macro expansion, cross-package caches, cancellation, memory bounds, persistence, and migration from whole-module rebuilds. Deliver a technical design and milestone plan, not code.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Before implementing IPv6-only clusters, outline the networking design for DNS, service discovery, egress translation, load balancers, observability, developer access, and dual-stack migration.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"boundary","lang":"en"} -{"prompt":"Add ARM64 relocation support to `moldump`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Compiler crash report:\n\n```text\norionc 0.19.0 target=aarch64-unknown-linux-gnu opt=2\nmodule=physics.constraints\nthread 'codegen-7' panicked at `value used after block sealed`\nfunction solveIsland blocks=418 values=7221\npass pipeline: simplify-cfg, mem2reg, inline, licm, lower-simd\nlast transformation: split critical edge bb173 -> bb241\nphi v612 inputs=[bb168:v599, bb173:v610]\nnew block bb419 predecessor=bb173 successor=bb241\nverifier before LICM=pass\nverifier after LICM=fail: phi input predecessor missing bb173\nrecompile with threads=1: pass\nrecompile with inline disabled: pass\n```\n\nDetermine whether parallel IR mutation, stale predecessor data, or critical-edge splitting leaves the phi malformed and why disabling inlining masks it.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"Build the visionOS tool palette with gaze-friendly targets, spatial placement, collapsed and expanded modes, and accessible labels.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Plan and implement a remote build-execution service for the monorepo. Begin with a design covering action digests, hermetic inputs, cache trust, worker isolation, scheduling, cancellation, logs, multi-region behavior, and rollout. Then add the scheduler, CAS integration, worker protocol, and conformance tests. Treat the architecture and trust model as the primary deliverable.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.98,"slice":"mixed","lang":"en"} -{"prompt":"Set `MAX_INLINE_DEPTH` to 12","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Extract duplicated source-span merging from the parser and type checker into one utility without changing diagnostics.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Implement `/internal/network/routes` with prefix, next hop, source, generation, and convergence age.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} -{"prompt":"make the VR menu less weird","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"Find why incremental type checking reports phantom duplicate symbols after renaming a file twice.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Explain how the compiler's borrow checker handles a value captured by both an async closure and a deferred cleanup. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Toolchain release notes draft material:\n\n```text\nVersion: Orion 0.19\nHighlights:\n- incremental builds for workspace dependencies\n- new `match` exhaustiveness diagnostics\n- experimental WebAssembly component target\n- formatter preserves trailing comments more reliably\nBreaking behavior:\n- ambiguous implicit conversions are now errors\n- deprecated `--legacy-imports` flag removed\nKnown limitation: incremental cache is ignored when compiler plugins are enabled\nMigration aid: `orion fix --implicit-conversions`\nBuild files generated by 0.19 cannot be consumed by 0.17\n```\n\nTurn this into concise release notes and an upgrade guide with compatibility warnings, examples, and rollback advice.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"pasted-context","lang":"en"} -{"prompt":"Move the floating AR close button away from the system volume indicator.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.15,"slice":"boundary","lang":"en"} -{"prompt":"Write a contributor guide for adding a new compiler optimization pass, including registration, analyses, invalidation, fixtures, and benchmarks.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} +{"prompt":"Design an incremental compilation architecture for the Orion language server. Cover dependency invalidation, generated sources, macro expansion, cross-package caches, cancellation, memory bounds, persistence, and migration from whole-module rebuilds. Deliver a technical design and milestone plan, not code.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Before implementing IPv6-only clusters, outline the networking design for DNS, service discovery, egress translation, load balancers, observability, developer access, and dual-stack migration.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add ARM64 relocation support to `moldump`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Compiler crash report:\n\n```text\norionc 0.19.0 target=aarch64-unknown-linux-gnu opt=2\nmodule=physics.constraints\nthread 'codegen-7' panicked at `value used after block sealed`\nfunction solveIsland blocks=418 values=7221\npass pipeline: simplify-cfg, mem2reg, inline, licm, lower-simd\nlast transformation: split critical edge bb173 -> bb241\nphi v612 inputs=[bb168:v599, bb173:v610]\nnew block bb419 predecessor=bb173 successor=bb241\nverifier before LICM=pass\nverifier after LICM=fail: phi input predecessor missing bb173\nrecompile with threads=1: pass\nrecompile with inline disabled: pass\n```\n\nDetermine whether parallel IR mutation, stale predecessor data, or critical-edge splitting leaves the phi malformed and why disabling inlining masks it.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Build the visionOS tool palette with gaze-friendly targets, spatial placement, collapsed and expanded modes, and accessible labels.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Plan and implement a remote build-execution service for the monorepo. Begin with a design covering action digests, hermetic inputs, cache trust, worker isolation, scheduling, cancellation, logs, multi-region behavior, and rollout. Then add the scheduler, CAS integration, worker protocol, and conformance tests. Treat the architecture and trust model as the primary deliverable.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":1.0,"slice":"mixed","lang":"en"} +{"prompt":"Set `MAX_INLINE_DEPTH` to 12","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Extract duplicated source-span merging from the parser and type checker into one utility without changing diagnostics.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement `/internal/network/routes` with prefix, next hop, source, generation, and convergence age.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"make the VR menu less weird","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Find why incremental type checking reports phantom duplicate symbols after renaming a file twice.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Explain how the compiler's borrow checker handles a value captured by both an async closure and a deferred cleanup. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Toolchain release notes draft material:\n\n```text\nVersion: Orion 0.19\nHighlights:\n- incremental builds for workspace dependencies\n- new `match` exhaustiveness diagnostics\n- experimental WebAssembly component target\n- formatter preserves trailing comments more reliably\nBreaking behavior:\n- ambiguous implicit conversions are now errors\n- deprecated `--legacy-imports` flag removed\nKnown limitation: incremental cache is ignored when compiler plugins are enabled\nMigration aid: `orion fix --implicit-conversions`\nBuild files generated by 0.19 cannot be consumed by 0.17\n```\n\nTurn this into concise release notes and an upgrade guide with compatibility warnings, examples, and rollback advice.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"Move the floating AR close button away from the system volume indicator.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Write a contributor guide for adding a new compiler optimization pass, including registration, analyses, invalidation, fixtures, and benchmarks.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Implement the build-cache inspection endpoint with digest lookup, dependency graph, and eviction metadata, then document its filters, response fields, and troubleshooting uses.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Map out a migration from per-cluster NAT gateways to a shared egress platform, including tenancy, policy, availability, cost, observability, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Rename `tok` to `token` in `ParserState.rs`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"en"} -{"prompt":"Teach the linker to emit GNU build IDs and expose them through the symbol-inspection CLI.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Tighten the HUD's depth spacing","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.18,"slice":"core","lang":"en"} -{"prompt":"Bump `tree-sitter` to `0.25.8`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Rename `MasterRouteTable` to `PrimaryRouteTable` across Terraform, controllers, tests, and dashboards while preserving resource addresses and behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.68,"slice":"boundary","lang":"en"} -{"prompt":"Split `SemanticAnalyzer` into name resolution, type inference, conformance, and diagnostics phases without changing accepted programs or errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.84,"slice":"core","lang":"en"} +{"prompt":"Rename `tok` to `token` in `ParserState.rs`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Teach the linker to emit GNU build IDs and expose them through the symbol-inspection CLI.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Tighten the HUD's depth spacing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Bump `tree-sitter` to `0.25.8`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename `MasterRouteTable` to `PrimaryRouteTable` across Terraform, controllers, tests, and dashboards while preserving resource addresses and behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Split `SemanticAnalyzer` into name resolution, type inference, conformance, and diagnostics phases without changing accepted programs or errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Networking backlog item:\n\n```text\nNET-772 — outbound domain allowlists\nTenants configure exact domains and wildcard subdomains\nGateway observes TLS SNI and HTTP CONNECT targets\nIP literals require explicit CIDR rules\nDNS answers may change while connections remain open\nRules apply per workload identity, not source IP\nConfiguration updates should converge within 30 seconds\nDenied connections emit reason codes without leaking full hostnames to shared logs\nMaximum 10,000 rules per tenant\nNeed dry-run evaluation and decision counters\nExisting dataplane: Envoy plus custom Go control plane\n```\n\nImplement rule storage, validation, compiled policy distribution, identity binding, dry-run decisions, metrics, and integration tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Investigate why the Android NDK build emits different symbol visibility depending on whether Ninja is invoked through Gradle.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Create the spatial scene hierarchy inspector and add a short legend for anchors, entities, components, and inherited visibility.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Why does the optimizer retain seemingly dead bounds checks after vectorization? Explain the existing legality constraints.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Rewrite the setup instructions for building the cross compiler and running its QEMU test targets.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"Network test failure after enabling ECMP:\n\n```text\nFAIL TestFlowStickinessDuringRouteUpdate\nflow=10.42.1.8:49211->10.80.0.4:443 proto=tcp\ninitial nexthop=gw-a hash=0x71bc\nroute generation 117 installed nexthops=[gw-a gw-b]\npacket seq=1804 observed=gw-a\npacket seq=1805 observed=gw-b\npacket seq=1806 observed=gw-b\nconntrack lookup key includes zone=0 on ingress\nroute update path lookup key includes zone=12\nexpected established flow to remain gw-a\n```\n\nDetermine whether conntrack zoning, hash reseeding, or route replacement causes an established flow to move and why only the update path sees zone 12.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"boundary","lang":"en"} -{"prompt":"finish the compiler command","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.47,"slice":"vague-eval","lang":"en"} -{"prompt":"Propose an architecture for reproducible native toolchains, including source pinning, bootstrap trust, binary comparison, signing, provenance, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"core","lang":"en"} +{"prompt":"Investigate why the Android NDK build emits different symbol visibility depending on whether Ninja is invoked through Gradle.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the spatial scene hierarchy inspector and add a short legend for anchors, entities, components, and inherited visibility.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Why does the optimizer retain seemingly dead bounds checks after vectorization? Explain the existing legality constraints.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Rewrite the setup instructions for building the cross compiler and running its QEMU test targets.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Network test failure after enabling ECMP:\n\n```text\nFAIL TestFlowStickinessDuringRouteUpdate\nflow=10.42.1.8:49211->10.80.0.4:443 proto=tcp\ninitial nexthop=gw-a hash=0x71bc\nroute generation 117 installed nexthops=[gw-a gw-b]\npacket seq=1804 observed=gw-a\npacket seq=1805 observed=gw-b\npacket seq=1806 observed=gw-b\nconntrack lookup key includes zone=0 on ingress\nroute update path lookup key includes zone=12\nexpected established flow to remain gw-a\n```\n\nDetermine whether conntrack zoning, hash reseeding, or route replacement causes an established flow to move and why only the update path sees zone 12.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Propose an architecture for reproducible native toolchains, including source pinning, bootstrap trust, binary comparison, signing, provenance, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Add DWARF v5 line-table decoding to `symview`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Patch under review:\n\n```diff\n fn resolve(name: &str, scope: &Scope) -> Option {\n- for candidate in scope.visible_symbols() {\n- if candidate.name == name { return Some(candidate.clone()) }\n- }\n- None\n+ SYMBOL_CACHE.get_or_insert((scope.id(), name.to_owned()), || {\n+ scope.visible_symbols().find(|s| s.name == name).cloned()\n+ })\n }\n```\n\nThe author says this makes completion faster. Review cache lifetime, invalidation after edits, negative entries, scope-ID reuse, concurrency, and memory growth. Do not change the patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.69,"slice":"pasted-context","lang":"en"} -{"prompt":"Schreibe eine kurze Referenz für die bestehende `netctl trace-route`-Ausgabe, einschließlich Hop-Status, Zeitüberschreitungen und JSON-Feldern. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.36,"slice":"boundary","lang":"de"} -{"prompt":"Build the browser-based flame graph with zoom, search, comparison mode, keyboard navigation, and accessible stack summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Review how compiler diagnostics are currently grouped and suppressed, then turn the findings into a plugin-author guide with examples.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.61,"slice":"mixed","lang":"en"} -{"prompt":"Set the default optimization level to `O1`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"Benenne `ModCtx` im gesamten Compiler in `ModuleContext` um; öffentliche Plugin-APIs und Verhalten bleiben kompatibel.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"de"} -{"prompt":"Consolidate x86 and ARM immediate-range validation without changing accepted instructions or diagnostics.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Diagnose the duplicated route metric","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Explain how the module loader prevents two package versions from exporting the same canonical symbol.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Create API documentation for the existing remote-cache endpoints, including action lookup, blob download, expiry, and authorization.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Plan a zero-downtime migration from iptables-based service routing to eBPF. Cover feature parity, kernel compatibility, conntrack, observability, canaries, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"UX ticket:\n\n```text\nFeature: mixed-reality object alignment\nUser selects a real-world edge, then aligns a virtual guide to it\nStates: scanning, edge detected, locked, confidence lost, manual adjustment\nControls: lock, reset, fine rotation, fine translation\nVisuals must remain legible against bright and dark environments\nHaptics confirm lock and warn on tracking loss\nVoiceOver describes confidence and selected axis\nHand tracking and controller input both supported\nDo not obscure the target edge with the control panel\nExisting scene model publishes pose and confidence at 60 Hz\n```\n\nImplement the interaction UI and tests around the existing scene model.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Implement `/v1/prefixes/validate` with overlap detection, policy limits, and normalized CIDR output.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Remove the extra comma in `targets.toml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} -{"prompt":"Fix the clipped tooltip in immersive mode and extract its duplicated safe-volume inset helper.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} -{"prompt":"Replace parser recovery booleans with one explicit recovery state while preserving emitted diagnostics and accepted malformed input.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Cambia `blkId` por `blockId` solo en `ControlFlow.swift`; no modifiques el IR.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"es"} -{"prompt":"Investigate why Metal shader compilation stalls only when source maps are enabled in debug builds.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Summarize the existing route-convergence model for SRE reviewers using controller code and tests as evidence.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Develop a capacity roadmap for moving build artifacts from 2 PB to 15 PB. Include access patterns, replication, retention, deduplication, cost gates, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"core","lang":"en"} -{"prompt":"Implement deterministic macro-expansion caching with dependency tracking and cycle detection.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Create the desktop network-topology editor with draggable nodes, typed connections, validation, undo, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Fix `dependecy` in `package.lock`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} -{"prompt":"Merge the duplicate AST walkers used by linting and symbol indexing while preserving traversal order.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} +{"prompt":"Patch under review:\n\n```diff\n fn resolve(name: &str, scope: &Scope) -> Option {\n- for candidate in scope.visible_symbols() {\n- if candidate.name == name { return Some(candidate.clone()) }\n- }\n- None\n+ SYMBOL_CACHE.get_or_insert((scope.id(), name.to_owned()), || {\n+ scope.visible_symbols().find(|s| s.name == name).cloned()\n+ })\n }\n```\n\nThe author says this makes completion faster. Review cache lifetime, invalidation after edits, negative entries, scope-ID reuse, concurrency, and memory growth. Do not change the patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Schreibe eine kurze Referenz für die bestehende `netctl trace-route`-Ausgabe, einschließlich Hop-Status, Zeitüberschreitungen und JSON-Feldern. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"de"} +{"prompt":"Build the browser-based flame graph with zoom, search, comparison mode, keyboard navigation, and accessible stack summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Review how compiler diagnostics are currently grouped and suppressed, then turn the findings into a plugin-author guide with examples.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Set the default optimization level to `O1`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Benenne `ModCtx` im gesamten Compiler in `ModuleContext` um; öffentliche Plugin-APIs und Verhalten bleiben kompatibel.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} +{"prompt":"Consolidate x86 and ARM immediate-range validation without changing accepted instructions or diagnostics.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose the duplicated route metric","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Explain how the module loader prevents two package versions from exporting the same canonical symbol.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Create API documentation for the existing remote-cache endpoints, including action lookup, blob download, expiry, and authorization.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Plan a zero-downtime migration from iptables-based service routing to eBPF. Cover feature parity, kernel compatibility, conntrack, observability, canaries, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"UX ticket:\n\n```text\nFeature: mixed-reality object alignment\nUser selects a real-world edge, then aligns a virtual guide to it\nStates: scanning, edge detected, locked, confidence lost, manual adjustment\nControls: lock, reset, fine rotation, fine translation\nVisuals must remain legible against bright and dark environments\nHaptics confirm lock and warn on tracking loss\nVoiceOver describes confidence and selected axis\nHand tracking and controller input both supported\nDo not obscure the target edge with the control panel\nExisting scene model publishes pose and confidence at 60 Hz\n```\n\nImplement the interaction UI and tests around the existing scene model.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Implement `/v1/prefixes/validate` with overlap detection, policy limits, and normalized CIDR output.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Remove the extra comma in `targets.toml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fix the clipped tooltip in immersive mode and extract its duplicated safe-volume inset helper.","purpose":"debugging","secondary":"refactor","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Replace parser recovery booleans with one explicit recovery state while preserving emitted diagnostics and accepted malformed input.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Cambia `blkId` por `blockId` solo en `ControlFlow.swift`; no modifiques el IR.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"es"} +{"prompt":"Investigate why Metal shader compilation stalls only when source maps are enabled in debug builds.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Summarize the existing route-convergence model for SRE reviewers using controller code and tests as evidence.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Develop a capacity roadmap for moving build artifacts from 2 PB to 15 PB. Include access patterns, replication, retention, deduplication, cost gates, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement deterministic macro-expansion caching with dependency tracking and cycle detection.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create the desktop network-topology editor with draggable nodes, typed connections, validation, undo, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Fix `dependecy` in `package.lock`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Merge the duplicate AST walkers used by linting and symbol indexing while preserving traversal order.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"BGP incident logs:\n\n```text\npeer=rr-west state=Established received_prefixes=18422\ncontroller generation=882 desired_prefixes=18421\nwithdraw tenant=t_91 prefix=203.0.113.0/24 generation=883\nrouter apply generation=883 success\npeer update sent withdraw=203.0.113.0/24\n30s later external looking glass still shows prefix\nsecond reflector rr-east advertised path localpref=200 generation=881\ncontroller status marks rr-east healthy last_ack=881 age=74s\nhealth threshold=90s\nroute remains reachable through rr-east for 71s\n```\n\nDetermine why the controller reports convergence after only one reflector applies the withdrawal and whether the health threshold permits stale advertisement beyond the intended window.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Rename `adress_space` to `address_space` in the unreleased schema.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"en"} -{"prompt":"Assess whether the compiler's plugin loader allows a package to shadow built-in passes or load incompatible ABI versions. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} +{"prompt":"Rename `adress_space` to `address_space` in the unreleased schema.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Assess whether the compiler's plugin loader allows a package to shadow built-in passes or load incompatible ABI versions. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Restructure the network-policy compiler into parsing, normalization, validation, and code generation, then document its internal IR. Preserve generated rules.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Plan the retirement of the legacy Make-based build, covering target parity, generated code, developer workflows, CI, release artifacts, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"core","lang":"en"} -{"prompt":"Add support for parsing Mach-O chained fixups to the binary inspection library.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Build the spatial notification center with stacked cards, depth-aware focus, dismissal gestures, and reduced-motion behavior.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"do the linker thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `NetCfg` with `NetworkConfig` across packages while preserving YAML keys, environment variables, and public APIs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why debug symbols point one line past async suspension sites, implement the verified mapping fix, and add a debugger compatibility note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.82,"slice":"mixed","lang":"en"} -{"prompt":"Why does the proxy keep drained upstream connections for 30 seconds? Explain the existing lifecycle and tradeoffs; nothing is broken.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.46,"slice":"boundary","lang":"en"} -{"prompt":"Track down the memory leak in the language server after repeatedly opening and closing large workspaces.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Write release notes for the new WebAssembly target, including supported interfaces, limitations, migration, and debugging.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Network architecture notes:\n\n```text\nGoal: private connectivity from customer VPCs to our regional API\nCloud providers: AWS first, Azure next, GCP later\nAWS candidate: PrivateLink with one endpoint service per region\nTenants may have overlapping RFC1918 ranges\nAPI must identify tenant independently of source IP\nDNS should resolve private names only inside enrolled networks\nCustomers need connection-status diagnostics\nBackend deployments must not require endpoint recreation\nAbuse controls and per-tenant quotas still apply\nSupport needs a revocation path that takes effect within five minutes\n```\n\nProduce an implementation-free architecture and rollout plan covering identity, DNS, tenancy, availability, onboarding, observability, revocation, and provider expansion.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"pasted-context","lang":"en"} -{"prompt":"Give the profiler sidebar clearer grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.33,"slice":"core","lang":"en"} -{"prompt":"Turn the existing compiler-plugin compatibility behavior into developer documentation, then review whether its stated version guarantees match the loader and tests.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Outline a phased design for replacing regional VPN gateways with WireGuard-based mesh access, without deploying anything yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"boundary","lang":"en"} -{"prompt":"Implement SSA destruction with critical-edge splitting and parallel-copy resolution.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.89,"slice":"core","lang":"en"} -{"prompt":"Create an operator guide for diagnosing asymmetric routing across the service mesh.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Move target-feature detection out of the code generator while preserving emitted instructions and errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Investigate why DNS negative responses remain cached after the authoritative record is created.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"Add generation-aware route reconciliation with stale-update rejection and retry jitter.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Set the linker thread count to 8","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Create the AR measurement history panel with unit switching, rename, delete, export, and accessible values.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Corrige apenas `complier` para `compiler` na nova mensagem de erro.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"pt"} +{"prompt":"Plan the retirement of the legacy Make-based build, covering target parity, generated code, developer workflows, CI, release artifacts, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add support for parsing Mach-O chained fixups to the binary inspection library.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Build the spatial notification center with stacked cards, depth-aware focus, dismissal gestures, and reduced-motion behavior.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"do the linker thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `NetCfg` with `NetworkConfig` across packages while preserving YAML keys, environment variables, and public APIs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose why debug symbols point one line past async suspension sites, implement the verified mapping fix, and add a debugger compatibility note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Why does the proxy keep drained upstream connections for 30 seconds? Explain the existing lifecycle and tradeoffs; nothing is broken.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Track down the memory leak in the language server after repeatedly opening and closing large workspaces.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Write release notes for the new WebAssembly target, including supported interfaces, limitations, migration, and debugging.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Network architecture notes:\n\n```text\nGoal: private connectivity from customer VPCs to our regional API\nCloud providers: AWS first, Azure next, GCP later\nAWS candidate: PrivateLink with one endpoint service per region\nTenants may have overlapping RFC1918 ranges\nAPI must identify tenant independently of source IP\nDNS should resolve private names only inside enrolled networks\nCustomers need connection-status diagnostics\nBackend deployments must not require endpoint recreation\nAbuse controls and per-tenant quotas still apply\nSupport needs a revocation path that takes effect within five minutes\n```\n\nProduce an implementation-free architecture and rollout plan covering identity, DNS, tenancy, availability, onboarding, observability, revocation, and provider expansion.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Give the profiler sidebar clearer grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Turn the existing compiler-plugin compatibility behavior into developer documentation, then review whether its stated version guarantees match the loader and tests.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Outline a phased design for replacing regional VPN gateways with WireGuard-based mesh access, without deploying anything yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement SSA destruction with critical-edge splitting and parallel-copy resolution.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create an operator guide for diagnosing asymmetric routing across the service mesh.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Move target-feature detection out of the code generator while preserving emitted instructions and errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Investigate why DNS negative responses remain cached after the authoritative record is created.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add generation-aware route reconciliation with stale-update rejection and retry jitter.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Set the linker thread count to 8","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Create the AR measurement history panel with unit switching, rename, delete, export, and accessible values.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Corrige apenas `complier` para `compiler` na nova mensagem de erro.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"pt"} {"prompt":"Review the remote build cache for cross-tenant digest confusion, poisoned results, unbounded blobs, and authorization gaps. Findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Implement compiler-diagnostic streaming and write its protocol guide. Include ordering, partial results, cancellation, versioning, examples, and client recovery.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Design a migration from static subnet allocation to an IPAM service, covering ownership, overlap detection, reservations, imports, failure modes, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"core","lang":"en"} -{"prompt":"Add incremental symbol indexing with per-file tombstones and durable checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Build the WebGPU shader playground with editor, compile diagnostics, preview, uniforms, examples, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"continue the network cleanup","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.45,"slice":"vague-eval","lang":"en"} -{"prompt":"Extract IP normalization into one shared module while preserving canonical output and all accepted inputs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why compiler cache hits sometimes return diagnostics from another feature configuration, implement the key correction, and document cache invalidation behavior.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.83,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed L4 load-balancer failover design for connection preservation, health detection, split brain, and route convergence. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"boundary","lang":"en"} -{"prompt":"Find why the parser occasionally hangs on a malformed nested generic expression.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Draft a migration guide from compiler 0.18 to 0.19 with automated fixes and compatibility warnings.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"core","lang":"en"} -{"prompt":"Routing proposal excerpt:\n\n```text\nCurrent: every cluster advertises pod CIDRs through BGP\nProposal: aggregate per availability zone to reduce table size\nCurrent prefixes: 42,000\nExpected aggregates: about 1,200\nConstraints:\n- draining a cluster must not withdraw addresses used by another cluster\n- partial zone failure should preserve healthy cluster routes\n- traffic must not blackhole during prefix ownership transfer\n- route reflectors support communities and add-path\n- observability currently reports only exact prefixes\n- rollback requires re-advertising specific pod CIDRs\n```\n\nReview the proposal for aggregation safety, ownership, failure isolation, convergence, observability, and rollback. Identify assumptions that need proof; do not implement.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a hover state to the call graph nodes","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.24,"slice":"core","lang":"en"} -{"prompt":"Plan and implement reproducible package builds. First define dependency resolution, environment normalization, timestamps, archive ordering, native toolchains, verification, and rollout; then add the build wrapper and comparison tests.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.93,"slice":"mixed","lang":"en"} -{"prompt":"Outline an architecture for regional traffic steering using latency, capacity, residency, and health, including migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"boundary","lang":"en"} +{"prompt":"Implement compiler-diagnostic streaming and write its protocol guide. Include ordering, partial results, cancellation, versioning, examples, and client recovery.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Design a migration from static subnet allocation to an IPAM service, covering ownership, overlap detection, reservations, imports, failure modes, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add incremental symbol indexing with per-file tombstones and durable checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Build the WebGPU shader playground with editor, compile diagnostics, preview, uniforms, examples, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Extract IP normalization into one shared module while preserving canonical output and all accepted inputs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why compiler cache hits sometimes return diagnostics from another feature configuration, implement the key correction, and document cache invalidation behavior.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed L4 load-balancer failover design for connection preservation, health detection, split brain, and route convergence. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Find why the parser occasionally hangs on a malformed nested generic expression.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Draft a migration guide from compiler 0.18 to 0.19 with automated fixes and compatibility warnings.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Routing proposal excerpt:\n\n```text\nCurrent: every cluster advertises pod CIDRs through BGP\nProposal: aggregate per availability zone to reduce table size\nCurrent prefixes: 42,000\nExpected aggregates: about 1,200\nConstraints:\n- draining a cluster must not withdraw addresses used by another cluster\n- partial zone failure should preserve healthy cluster routes\n- traffic must not blackhole during prefix ownership transfer\n- route reflectors support communities and add-path\n- observability currently reports only exact prefixes\n- rollback requires re-advertising specific pod CIDRs\n```\n\nReview the proposal for aggregation safety, ownership, failure isolation, convergence, observability, and rollback. Identify assumptions that need proof; do not implement.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add a hover state to the call graph nodes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Plan and implement reproducible package builds. First define dependency resolution, environment normalization, timestamps, archive ordering, native toolchains, verification, and rollout; then add the build wrapper and comparison tests.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Outline an architecture for regional traffic steering using latency, capacity, residency, and health, including migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Implement a bounded recursive-descent parser for demangling nested generic symbols.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Escribe una página de referencia para los mensajes del enlazador, con causas, ejemplos y acciones recomendadas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.36,"slice":"core","lang":"es"} -{"prompt":"Consolidate route diffing across cloud providers without changing planned network operations.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Investigate why mixed-reality anchors drift after the app resumes from background.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","lang":"en"} -{"prompt":"Add atomic package-index publication with generation manifests and rollback support.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Remove the deprecated `--old-abi` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.05,"slice":"core","lang":"en"} -{"prompt":"Build the immersive performance overlay with frame timing, thermal state, memory, collapsible details, and gaze controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"`Netwrok unavailable` を `Network unavailable` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"ja"} -{"prompt":"Review the compiler's response-file parser for argument injection, recursive includes, path traversal, and size limits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Implement network-policy simulation and write its API guide. Include hypothetical identities, dry runs, decision traces, redaction, examples, and authorization.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Plan a disaster-recovery strategy for source-code and build-artifact infrastructure, including mirrors, signing keys, caches, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"core","lang":"en"} -{"prompt":"Add deterministic source archive generation with normalized metadata and stable ordering.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} +{"prompt":"Escribe una página de referencia para los mensajes del enlazador, con causas, ejemplos y acciones recomendadas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"es"} +{"prompt":"Consolidate route diffing across cloud providers without changing planned network operations.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Investigate why mixed-reality anchors drift after the app resumes from background.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add atomic package-index publication with generation manifests and rollback support.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Remove the deprecated `--old-abi` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Build the immersive performance overlay with frame timing, thermal state, memory, collapsible details, and gaze controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"`Netwrok unavailable` を `Network unavailable` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"ja"} +{"prompt":"Review the compiler's response-file parser for argument injection, recursive includes, path traversal, and size limits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement network-policy simulation and write its API guide. Include hypothetical identities, dry runs, decision traces, redaction, examples, and authorization.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan a disaster-recovery strategy for source-code and build-artifact infrastructure, including mirrors, signing keys, caches, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add deterministic source archive generation with normalized metadata and stable ordering.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Create the mobile VPN connection screen with region selection, connection progress, failure recovery, and diagnostic export.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"fix the build graph","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.54,"slice":"vague-eval","lang":"en"} -{"prompt":"Rename `InstSel` to `InstructionSelection` across the backend while preserving pass names and plugin compatibility.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why IPv6 connections fail only after DNS64 cache refresh, implement the proven prefix-handling fix, and update troubleshooting docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.82,"slice":"mixed","lang":"en"} -{"prompt":"Explain whether the proposed compiler daemon can safely share parsed syntax trees between users. Review isolation and cache semantics only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Track down missing tail-call frames in crash symbolication for optimized ARM64 binaries.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Write a troubleshooting guide for remote build cache misses, covering digests, environment inputs, toolchains, and permissions.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Build-system incident excerpt:\n\n```text\nworkspace commit=74da21b action=compile://ui/widgets\nlocal digest=sha256:83a1\nremote cache returned result digest=sha256:83a1\noutput archive extracted successfully\nlink step error: undefined symbol `WidgetTheme::vtable`\nremote action metadata toolchain=clang-20.1 libcxx=20.1\nrequest action platform toolchain=clang-20.1 libcxx=20.2\nplatform properties included `compiler=clang-20.1` but omitted libcxx\nsame action after cache eviction: pass\ncache hit originated from macos-worker-17\nrequest ran on linux-worker-08\n```\n\nDetermine why incompatible output shared an action digest across platforms and which missing toolchain properties allowed the poisoned hit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Add selected styling to the route row","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Restructure the debugger protocol implementation and document its adapter API. Preserve wire messages while separating framing, requests, events, and session state.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"Design a global anycast ingress architecture, including route control, regional health, DDoS isolation, stateful protocols, and rollout milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"boundary","lang":"en"} -{"prompt":"Implement dominator-tree updates for incremental CFG edits.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.91,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new CPU target, including triples, ABI, registers, lowering, fixtures, and emulation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.47,"slice":"core","lang":"en"} -{"prompt":"Extract service CIDR validation from the cluster controller without changing accepted configurations.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"core","lang":"en"} -{"prompt":"Investigate why UDP flows intermittently bypass the egress policy after a node upgrade.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.76,"slice":"boundary","lang":"en"} -{"prompt":"Add signed compiler-plugin manifests with capability declarations and expiry.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Set the parser recursion limit to 512","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"Build the spatial object-properties panel with position, rotation, scale, materials, undo, and hand-friendly controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"把 `Compliation failed` 改成 `Compilation failed`，只改新提示文本。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"zh"} -{"prompt":"Inspect the network diagnostics bundle for secrets, private IP exposure, packet payloads, and unsafe file permissions. Report only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Implement build-action history and write its API documentation. Include inputs, digests, workers, cache status, pagination, retention, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Design a search architecture for a multilingual marketplace with lexical and semantic retrieval, tenant-specific catalogs, inventory freshness, filters, ranking experiments, typo tolerance, regional availability, and migration from the current Elasticsearch index. Deliver an RFC and rollout milestones, not code.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"core","lang":"en"} -{"prompt":"Before building personalized home feeds, outline the data flow, candidate generation, ranking, cold-start behavior, privacy controls, failure fallback, experimentation, and phased launch.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"boundary","lang":"en"} -{"prompt":"Add faceted counts to `/v3/catalog/search`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Search incident logs:\n\n```text\nquery='wireless headphones' tenant=shop_47 locale=en-GB\nindex generation=192 document_count=8,411,220\nrequest filter=in_stock:true sort=relevance\ncoordinator total_hits=1842 returned=0\nshard-0 hits=611 top_score=18.4\nshard-1 hits=604 top_score=17.9\nshard-2 timeout after=800ms partial_hits=627\nresponse partial=true page_token generated from shard cursors\nreranker input candidates=0 reason='require_all_shards'\nHTTP status=200 latency=824ms\nretry 3s later returned=24 partial=false\n```\n\nDetermine why a partial shard timeout turns available lexical hits into an empty result set and whether the coordinator, reranker contract, or pagination state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.83,"slice":"pasted-context","lang":"en"} -{"prompt":"Build the responsive product-gallery viewer with pinch zoom, keyboard thumbnails, video slots, fullscreen mode, and accessible media labels.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Plan and implement a recommendations platform for the storefront. Begin with a design covering event inputs, candidate sources, online features, model serving, business rules, exploration, attribution, privacy, fallbacks, and rollout. Then add the candidate API, ranking pipeline, rule hooks, metrics, and offline evaluation fixtures. Treat the architecture and experimentation model as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.97,"slice":"mixed","lang":"en"} -{"prompt":"Set `SEARCH_PAGE_SIZE` to 36","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Extract duplicated price-range normalization from search and browse while preserving query behavior and URLs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Implement `/internal/index/generations` with shard status, document count, build time, and active alias.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} -{"prompt":"make products feel more expensive","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"Find why the Android search screen occasionally displays results from the previous query after rapid typing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Explain how `HybridRanker` combines BM25 and vector scores, including normalization and tie-breaking. Do not edit code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Product launch notes:\n\n```text\nFeature: saved searches\nCustomers can save query text, filters, sort, and delivery region\nMaximum 20 saved searches per account\nOptional email alerts run daily when new matching products appear\nAlert comparison uses product creation time, not inventory-restock time\nDeleted products never appear in alerts\nChanging a saved search resets its comparison checkpoint\nMobile app 7.8 can open saved searches but cannot edit alerts\nGuest searches must be attached to an account before saving\n```\n\nTurn this into release notes and a help-center article. Clearly explain alert timing, limits, editing behavior, and old mobile-client constraints.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.44,"slice":"pasted-context","lang":"en"} -{"prompt":"Move the wishlist heart four pixels from the product image edge.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.14,"slice":"boundary","lang":"en"} -{"prompt":"Write an operator guide for rebuilding one search shard, validating parity, swapping aliases, and rolling back.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} +{"prompt":"fix the build graph","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Rename `InstSel` to `InstructionSelection` across the backend while preserving pass names and plugin compatibility.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose why IPv6 connections fail only after DNS64 cache refresh, implement the proven prefix-handling fix, and update troubleshooting docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Explain whether the proposed compiler daemon can safely share parsed syntax trees between users. Review isolation and cache semantics only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Track down missing tail-call frames in crash symbolication for optimized ARM64 binaries.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Write a troubleshooting guide for remote build cache misses, covering digests, environment inputs, toolchains, and permissions.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Build-system incident excerpt:\n\n```text\nworkspace commit=74da21b action=compile://ui/widgets\nlocal digest=sha256:83a1\nremote cache returned result digest=sha256:83a1\noutput archive extracted successfully\nlink step error: undefined symbol `WidgetTheme::vtable`\nremote action metadata toolchain=clang-20.1 libcxx=20.1\nrequest action platform toolchain=clang-20.1 libcxx=20.2\nplatform properties included `compiler=clang-20.1` but omitted libcxx\nsame action after cache eviction: pass\ncache hit originated from macos-worker-17\nrequest ran on linux-worker-08\n```\n\nDetermine why incompatible output shared an action digest across platforms and which missing toolchain properties allowed the poisoned hit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Add selected styling to the route row","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Restructure the debugger protocol implementation and document its adapter API. Preserve wire messages while separating framing, requests, events, and session state.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Design a global anycast ingress architecture, including route control, regional health, DDoS isolation, stateful protocols, and rollout milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement dominator-tree updates for incremental CFG edits.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new CPU target, including triples, ABI, registers, lowering, fixtures, and emulation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Extract service CIDR validation from the cluster controller without changing accepted configurations.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why UDP flows intermittently bypass the egress policy after a node upgrade.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add signed compiler-plugin manifests with capability declarations and expiry.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Set the parser recursion limit to 512","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the spatial object-properties panel with position, rotation, scale, materials, undo, and hand-friendly controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"把 `Compliation failed` 改成 `Compilation failed`，只改新提示文本。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"zh"} +{"prompt":"Inspect the network diagnostics bundle for secrets, private IP exposure, packet payloads, and unsafe file permissions. Report only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement build-action history and write its API documentation. Include inputs, digests, workers, cache status, pagination, retention, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Design a search architecture for a multilingual marketplace with lexical and semantic retrieval, tenant-specific catalogs, inventory freshness, filters, ranking experiments, typo tolerance, regional availability, and migration from the current Elasticsearch index. Deliver an RFC and rollout milestones, not code.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Before building personalized home feeds, outline the data flow, candidate generation, ranking, cold-start behavior, privacy controls, failure fallback, experimentation, and phased launch.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add faceted counts to `/v3/catalog/search`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Search incident logs:\n\n```text\nquery='wireless headphones' tenant=shop_47 locale=en-GB\nindex generation=192 document_count=8,411,220\nrequest filter=in_stock:true sort=relevance\ncoordinator total_hits=1842 returned=0\nshard-0 hits=611 top_score=18.4\nshard-1 hits=604 top_score=17.9\nshard-2 timeout after=800ms partial_hits=627\nresponse partial=true page_token generated from shard cursors\nreranker input candidates=0 reason='require_all_shards'\nHTTP status=200 latency=824ms\nretry 3s later returned=24 partial=false\n```\n\nDetermine why a partial shard timeout turns available lexical hits into an empty result set and whether the coordinator, reranker contract, or pagination state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Build the responsive product-gallery viewer with pinch zoom, keyboard thumbnails, video slots, fullscreen mode, and accessible media labels.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Plan and implement a recommendations platform for the storefront. Begin with a design covering event inputs, candidate sources, online features, model serving, business rules, exploration, attribution, privacy, fallbacks, and rollout. Then add the candidate API, ranking pipeline, rule hooks, metrics, and offline evaluation fixtures. Treat the architecture and experimentation model as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":1.0,"slice":"mixed","lang":"en"} +{"prompt":"Set `SEARCH_PAGE_SIZE` to 36","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Extract duplicated price-range normalization from search and browse while preserving query behavior and URLs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Implement `/internal/index/generations` with shard status, document count, build time, and active alias.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"make products feel more expensive","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Find why the Android search screen occasionally displays results from the previous query after rapid typing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Explain how `HybridRanker` combines BM25 and vector scores, including normalization and tie-breaking. Do not edit code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Product launch notes:\n\n```text\nFeature: saved searches\nCustomers can save query text, filters, sort, and delivery region\nMaximum 20 saved searches per account\nOptional email alerts run daily when new matching products appear\nAlert comparison uses product creation time, not inventory-restock time\nDeleted products never appear in alerts\nChanging a saved search resets its comparison checkpoint\nMobile app 7.8 can open saved searches but cannot edit alerts\nGuest searches must be attached to an account before saving\n```\n\nTurn this into release notes and a help-center article. Clearly explain alert timing, limits, editing behavior, and old mobile-client constraints.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"Move the wishlist heart four pixels from the product image edge.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Write an operator guide for rebuilding one search shard, validating parity, swapping aliases, and rolling back.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Implement the product-similarity endpoint with inventory filtering, pagination, and explainability fields, then document its parameters, examples, and freshness semantics.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Map out a migration from nightly full catalog indexing to CDC-driven incremental indexing, including ordering, deletes, backfills, verification, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Rename `qry` to `query` in `SearchReducer.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"en"} -{"prompt":"Teach the indexing worker to coalesce repeated updates for the same product without losing deletes.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Polish the cart summary card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.29,"slice":"core","lang":"en"} -{"prompt":"Bump `opensearch-py` to `3.0.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Rename `MasterCatalog` to `PrimaryCatalog` across services, events, dashboards, and tests while preserving external field names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.64,"slice":"boundary","lang":"en"} -{"prompt":"Split `SearchService` into query parsing, retrieval, ranking, and response assembly without changing results or latency metrics.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Backlog item from merchandising:\n\n```text\nSEARCH-2911 — pinned products in category results\nMerchandisers can pin up to 8 products per category and region\nPins may have start and end times\nOut-of-stock or unpublished products must not render\nRemaining results preserve normal ranking and must not duplicate pins\nPagination should behave as if pins occupy result positions\nPreview mode accepts a future timestamp\nEvery change records actor, before/after state, and reason\nUpdates should appear within 60 seconds\nNeed counters for invalid, suppressed, and displayed pins\n```\n\nImplement configuration storage, validation, ranking integration, pagination behavior, preview, audit events, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.85,"slice":"pasted-context","lang":"en"} -{"prompt":"Investigate why infinite scroll occasionally skips twelve products when a price update lands between pages.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Create the recommendation-reasons drawer and write a concise explanation of each reason category. Include loading, missing reasons, privacy-safe copy, and screen-reader behavior.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.64,"slice":"mixed","lang":"en"} -{"prompt":"Why does the catalog index retain unpublished documents for seven days? Explain existing recovery and compliance behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"Rewrite the local setup for running OpenSearch, Kafka, the catalog service, and sample index fixtures.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.34,"slice":"core","lang":"en"} -{"prompt":"This ranking test started failing after the ICU upgrade:\n\n```text\nquery='café grinder' locale=fr-FR\nexpected order=[p14, p08, p22]\nactual order=[p08, p14, p22]\np14 title='Moulin à café'\np08 title='Moulin cafe compact'\nanalysis before: tokens=[moulin, cafe] p14 accent_folded=true\nanalysis after: tokens=[moulin, café] p14 accent_folded=false\nindex analyzer version=icu_74\nquery analyzer version=icu_76\nscores p14=11.208 p08=11.211\n```\n\nDetermine whether analyzer version skew, accent folding, or score tie precision caused the reorder and whether production indexes require rebuilding.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.76,"slice":"boundary","lang":"en"} -{"prompt":"finish the recommendation endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} -{"prompt":"Propose a design for privacy-safe behavioral search signals, including consent, retention, aggregation, bot filtering, deletion, model use, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"core","lang":"en"} -{"prompt":"Add streaming bulk indexing to `catalogctl ingest`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Pull request excerpt:\n\n```diff\n async function search(req) {\n- const filters = parseFilters(req.query)\n- const result = await engine.search(req.query.q, filters)\n+ const cacheKey = req.query.q\n+ let result = await redis.get(cacheKey)\n+ if (!result) {\n+ result = await engine.search(req.query.q, parseFilters(req.query))\n+ await redis.setex(cacheKey, 300, JSON.stringify(result))\n+ }\n return result\n }\n```\n\nReview the cache key, tenant isolation, filters, locale, inventory freshness, serialization, stampede behavior, and invalidation. No code changes requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.68,"slice":"pasted-context","lang":"en"} -{"prompt":"Schreibe eine kurze Referenz für die bestehenden Such-Query-Parameter, einschließlich Filterkombinationen, Sortierung und Paginierung. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"de"} -{"prompt":"Build the desktop merchandising board with drag-to-rank, scheduled pins, region preview, undo, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Review the current autocomplete pipeline, explain tokenization and ranking, then turn the explanation into an integrator guide with examples.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.62,"slice":"mixed","lang":"en"} -{"prompt":"Set the autocomplete debounce to 180ms","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"Benenne `RecCtx` repositoryweit in `RecommendationContext` um; JSON-Felder, Events und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"de"} -{"prompt":"Consolidate category-path normalization across ingestion and query services without changing canonical paths.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Diagnose the duplicated suggestion row","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Explain how `Diversifier` limits products from one seller while preserving sponsored placements.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.56,"slice":"core","lang":"en"} -{"prompt":"Create API documentation for the existing autocomplete endpoint, including locale, limits, highlighting, caching, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"boundary","lang":"en"} -{"prompt":"Plan a migration from static ranking weights to a learned-to-rank model, covering training data, offline metrics, guardrails, shadowing, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"core","lang":"en"} -{"prompt":"Design ticket:\n\n```text\nPage: search results on mobile web\nHeader: query, result count, sort, filter trigger\nSelected filters appear as removable chips in horizontal scroll\nProduct grid: two columns below 480px, three above\nSponsored items require visible label before product title\nLoading next page keeps existing cards stable\nNo-results state distinguishes typo, filters too narrow, and unavailable region\nBack navigation must restore exact scroll position\nAccessibility: result count announced once; chip removal announces updated count\nPerformance target: LCP under 2.5s on mid-tier Android\n```\n\nImplement the responsive page and tests using the current search API.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.76,"slice":"pasted-context","lang":"en"} -{"prompt":"Implement `POST /v1/indexes/{id}/validate` with sampled parity checks and a machine-readable report.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"boundary","lang":"en"} -{"prompt":"Remove the extra period in the empty state","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"core","lang":"en"} -{"prompt":"Fix the uneven mobile card gap and extract the repeated responsive gutter into the grid token file.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.36,"slice":"mixed","lang":"en"} -{"prompt":"Replace ranking-stage booleans with an explicit pipeline state while preserving results, traces, and error handling.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Cambia `prodIdx` por `productIndex` solo en `CatalogSync.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"es"} +{"prompt":"Map out a migration from nightly full catalog indexing to CDC-driven incremental indexing, including ordering, deletes, backfills, verification, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Rename `qry` to `query` in `SearchReducer.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Teach the indexing worker to coalesce repeated updates for the same product without losing deletes.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Polish the cart summary card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump `opensearch-py` to `3.0.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename `MasterCatalog` to `PrimaryCatalog` across services, events, dashboards, and tests while preserving external field names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Split `SearchService` into query parsing, retrieval, ranking, and response assembly without changing results or latency metrics.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Backlog item from merchandising:\n\n```text\nSEARCH-2911 — pinned products in category results\nMerchandisers can pin up to 8 products per category and region\nPins may have start and end times\nOut-of-stock or unpublished products must not render\nRemaining results preserve normal ranking and must not duplicate pins\nPagination should behave as if pins occupy result positions\nPreview mode accepts a future timestamp\nEvery change records actor, before/after state, and reason\nUpdates should appear within 60 seconds\nNeed counters for invalid, suppressed, and displayed pins\n```\n\nImplement configuration storage, validation, ranking integration, pagination behavior, preview, audit events, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Investigate why infinite scroll occasionally skips twelve products when a price update lands between pages.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the recommendation-reasons drawer and write a concise explanation of each reason category. Include loading, missing reasons, privacy-safe copy, and screen-reader behavior.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the catalog index retain unpublished documents for seven days? Explain existing recovery and compliance behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Rewrite the local setup for running OpenSearch, Kafka, the catalog service, and sample index fixtures.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"This ranking test started failing after the ICU upgrade:\n\n```text\nquery='café grinder' locale=fr-FR\nexpected order=[p14, p08, p22]\nactual order=[p08, p14, p22]\np14 title='Moulin à café'\np08 title='Moulin cafe compact'\nanalysis before: tokens=[moulin, cafe] p14 accent_folded=true\nanalysis after: tokens=[moulin, café] p14 accent_folded=false\nindex analyzer version=icu_74\nquery analyzer version=icu_76\nscores p14=11.208 p08=11.211\n```\n\nDetermine whether analyzer version skew, accent folding, or score tie precision caused the reorder and whether production indexes require rebuilding.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"finish the recommendation endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Propose a design for privacy-safe behavioral search signals, including consent, retention, aggregation, bot filtering, deletion, model use, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add streaming bulk indexing to `catalogctl ingest`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Pull request excerpt:\n\n```diff\n async function search(req) {\n- const filters = parseFilters(req.query)\n- const result = await engine.search(req.query.q, filters)\n+ const cacheKey = req.query.q\n+ let result = await redis.get(cacheKey)\n+ if (!result) {\n+ result = await engine.search(req.query.q, parseFilters(req.query))\n+ await redis.setex(cacheKey, 300, JSON.stringify(result))\n+ }\n return result\n }\n```\n\nReview the cache key, tenant isolation, filters, locale, inventory freshness, serialization, stampede behavior, and invalidation. No code changes requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Schreibe eine kurze Referenz für die bestehenden Such-Query-Parameter, einschließlich Filterkombinationen, Sortierung und Paginierung. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"de"} +{"prompt":"Build the desktop merchandising board with drag-to-rank, scheduled pins, region preview, undo, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Review the current autocomplete pipeline, explain tokenization and ranking, then turn the explanation into an integrator guide with examples.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Set the autocomplete debounce to 180ms","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Benenne `RecCtx` repositoryweit in `RecommendationContext` um; JSON-Felder, Events und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"de"} +{"prompt":"Consolidate category-path normalization across ingestion and query services without changing canonical paths.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose the duplicated suggestion row","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Explain how `Diversifier` limits products from one seller while preserving sponsored placements.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Create API documentation for the existing autocomplete endpoint, including locale, limits, highlighting, caching, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Plan a migration from static ranking weights to a learned-to-rank model, covering training data, offline metrics, guardrails, shadowing, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Design ticket:\n\n```text\nPage: search results on mobile web\nHeader: query, result count, sort, filter trigger\nSelected filters appear as removable chips in horizontal scroll\nProduct grid: two columns below 480px, three above\nSponsored items require visible label before product title\nLoading next page keeps existing cards stable\nNo-results state distinguishes typo, filters too narrow, and unavailable region\nBack navigation must restore exact scroll position\nAccessibility: result count announced once; chip removal announces updated count\nPerformance target: LCP under 2.5s on mid-tier Android\n```\n\nImplement the responsive page and tests using the current search API.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Implement `POST /v1/indexes/{id}/validate` with sampled parity checks and a machine-readable report.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remove the extra period in the empty state","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fix the uneven mobile card gap and extract the repeated responsive gutter into the grid token file.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Replace ranking-stage booleans with an explicit pipeline state while preserving results, traces, and error handling.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Cambia `prodIdx` por `productIndex` solo en `CatalogSync.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"es"} {"prompt":"Investigate why VoiceOver focus jumps to the page header whenever more search results append.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Summarize the current synonym-management lifecycle for search operators using code and runbooks as sources.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"Develop a capacity roadmap for growing vector search from 40 million to 1.2 billion products. Include sharding, quantization, memory, recall tests, replication, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Implement snapshot-consistent catalog exports with resumable chunks and stable ordering.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Create the Compose product-comparison screen with pinned headers, difference highlighting, expandable specs, and TalkBack navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Fix `recomendation` in `features.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} -{"prompt":"Merge duplicate query-token structures used by highlighting and ranking while preserving offsets and Unicode behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Indexing failure excerpt:\n\n```text\nconsumer partition=18 offset=774120 product=p_881 version=42 op=upsert\nbulk request accepted item status=201 seq_no=99217 primary_term=8\nconsumer checkpoint committed offset=774120\nlater event offset=774118 product=p_881 version=41 op=delete\nretry queue delivered after 14m\nbulk delete status=200 seq_no=99218\nsearch result missing product=p_881 expected version=42\nexternal_versioning disabled for retry queue path\n```\n\nDetermine how an older retried delete overwrites the newer upsert and why the normal consumer's version protection is absent from the retry path.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Rename `serach_term` to `search_term` in the unreleased migration.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"en"} -{"prompt":"Assess whether the recommendation cache can expose products from another region after a customer changes delivery country. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Restructure the catalog SDK into query, browse, recommendations, and shared models, then write a maintainer note. Preserve exports and behavior.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.74,"slice":"mixed","lang":"en"} -{"prompt":"Plan the retirement of the legacy category taxonomy, covering mapping, redirects, analytics continuity, merchant feeds, search, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"core","lang":"en"} -{"prompt":"Add language-aware stemming configuration with per-category overrides and validation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Build the tablet collection editor with reorder, product search, scheduling, preview, and autosave status.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} +{"prompt":"Summarize the current synonym-management lifecycle for search operators using code and runbooks as sources.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Develop a capacity roadmap for growing vector search from 40 million to 1.2 billion products. Include sharding, quantization, memory, recall tests, replication, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement snapshot-consistent catalog exports with resumable chunks and stable ordering.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create the Compose product-comparison screen with pinned headers, difference highlighting, expandable specs, and TalkBack navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Fix `recomendation` in `features.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Merge duplicate query-token structures used by highlighting and ranking while preserving offsets and Unicode behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Indexing failure excerpt:\n\n```text\nconsumer partition=18 offset=774120 product=p_881 version=42 op=upsert\nbulk request accepted item status=201 seq_no=99217 primary_term=8\nconsumer checkpoint committed offset=774120\nlater event offset=774118 product=p_881 version=41 op=delete\nretry queue delivered after 14m\nbulk delete status=200 seq_no=99218\nsearch result missing product=p_881 expected version=42\nexternal_versioning disabled for retry queue path\n```\n\nDetermine how an older retried delete overwrites the newer upsert and why the normal consumer's version protection is absent from the retry path.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Rename `serach_term` to `search_term` in the unreleased migration.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Assess whether the recommendation cache can expose products from another region after a customer changes delivery country. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Restructure the catalog SDK into query, browse, recommendations, and shared models, then write a maintainer note. Preserve exports and behavior.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan the retirement of the legacy category taxonomy, covering mapping, redirects, analytics continuity, merchant feeds, search, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add language-aware stemming configuration with per-category overrides and validation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Build the tablet collection editor with reorder, product search, scheduling, preview, and autosave status.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"do the catalog screen","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `IdxConfig` with `IndexConfig` throughout services while preserving config keys and public APIs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why sale prices disappear from search cards before the promotion ends, implement the verified timezone fix, and add a merchant-facing note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.75,"slice":"mixed","lang":"en"} -{"prompt":"Why does the search API return an opaque page token instead of an offset? Explain the existing consistency and performance reasons.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.45,"slice":"boundary","lang":"en"} +{"prompt":"Replace `IdxConfig` with `IndexConfig` throughout services while preserving config keys and public APIs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose why sale prices disappear from search cards before the promotion ends, implement the verified timezone fix, and add a merchant-facing note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the search API return an opaque page token instead of an offset? Explain the existing consistency and performance reasons.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Track down the memory increase in the synonym compiler after every rules reload.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write release notes for regional inventory filtering, including fallback behavior and old-client compatibility.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.34,"slice":"core","lang":"en"} -{"prompt":"Recommendation design notes:\n\n```text\nSurface: cart cross-sell\nInputs: cart items, customer segment, delivery region, inventory, margin band\nHard rules: no duplicate SKU, no age-restricted item unless eligible, no unavailable item\nBusiness wants supplier diversity and at least one accessory candidate\nModel output includes score but no reason\nLatency budget: 45ms p95\nFallback: category association table updated daily\nExperiment assignment must remain stable across session\nAttribution window: 24 hours after impression\nPrivacy: do not use medical-category history\n```\n\nProduce an implementation-free design and rollout plan covering candidate generation, rules, ranking, explanations, latency, fallback, experiments, attribution, and privacy.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"Give the filter drawer clearer section spacing","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.32,"slice":"core","lang":"en"} -{"prompt":"Turn the current search freshness behavior into merchant documentation, then review whether the stated update windows match ingestion, indexing, and cache code.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.67,"slice":"mixed","lang":"en"} -{"prompt":"Outline a phased architecture for moving image similarity search from batch embeddings to near-real-time updates, without implementing it.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.87,"slice":"boundary","lang":"en"} -{"prompt":"Implement tenant-isolated vector collections with quota enforcement and atomic alias swaps.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Create an operator guide for diagnosing zero-result search spikes by locale and category.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Move result-highlighting out of `SearchController` while preserving fragments, escaping, and offsets.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Investigate why personalized ranking remains enabled after a user withdraws analytics consent.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"Add idempotent synonym-set publication with generations and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Set the maximum saved searches to 25","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Create the responsive order-history search with filters, grouped results, empty states, and accessible dates.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Corrige apenas `catagory` para `category` no novo filtro.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"pt"} -{"prompt":"Review the merchant search-preview endpoint for tenant isolation, unpublished product leakage, query abuse, and rate limits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Implement search analytics exports and write the integration guide. Include filters, anonymization, asynchronous generation, retention, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Write release notes for regional inventory filtering, including fallback behavior and old-client compatibility.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Recommendation design notes:\n\n```text\nSurface: cart cross-sell\nInputs: cart items, customer segment, delivery region, inventory, margin band\nHard rules: no duplicate SKU, no age-restricted item unless eligible, no unavailable item\nBusiness wants supplier diversity and at least one accessory candidate\nModel output includes score but no reason\nLatency budget: 45ms p95\nFallback: category association table updated daily\nExperiment assignment must remain stable across session\nAttribution window: 24 hours after impression\nPrivacy: do not use medical-category history\n```\n\nProduce an implementation-free design and rollout plan covering candidate generation, rules, ranking, explanations, latency, fallback, experiments, attribution, and privacy.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Give the filter drawer clearer section spacing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Turn the current search freshness behavior into merchant documentation, then review whether the stated update windows match ingestion, indexing, and cache code.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Outline a phased architecture for moving image similarity search from batch embeddings to near-real-time updates, without implementing it.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement tenant-isolated vector collections with quota enforcement and atomic alias swaps.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create an operator guide for diagnosing zero-result search spikes by locale and category.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Move result-highlighting out of `SearchController` while preserving fragments, escaping, and offsets.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why personalized ranking remains enabled after a user withdraws analytics consent.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add idempotent synonym-set publication with generations and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Set the maximum saved searches to 25","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Create the responsive order-history search with filters, grouped results, empty states, and accessible dates.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Corrige apenas `catagory` para `category` no novo filtro.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"pt"} +{"prompt":"Review the merchant search-preview endpoint for tenant isolation, unpublished product leakage, query abuse, and rate limits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement search analytics exports and write the integration guide. Include filters, anonymization, asynchronous generation, retention, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Design a migration from Elasticsearch scripts to a dedicated ranking service, including parity tests, latency, failure fallback, versioning, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Add incremental aggregate updates for category product counts with delete handling.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} +{"prompt":"Add incremental aggregate updates for category product counts with delete handling.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Build the desktop query-debugger with parsed clauses, filters, shard timings, ranking stages, and copyable diagnostics.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"continue with search","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.46,"slice":"vague-eval","lang":"en"} -{"prompt":"Extract locale fallback into one shared resolver while preserving language selection and cache keys.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why price-range facets disagree with visible results, implement the proven currency-normalization fix, and update the troubleshooting guide.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.78,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed click-based ranking feature for position bias, bot traffic, feedback loops, privacy, and manipulation. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Find why catalog updates stop after the Debezium connector performs a snapshot.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Draft a migration guide for merchants moving from category IDs to taxonomy paths.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.36,"slice":"core","lang":"en"} -{"prompt":"Search quality incident packet:\n\n```text\nMetric: add-to-cart rate from search down 8.4% in de-DE\nNo change in overall search traffic\nDeployment: synonym set generation 244 at 10:12 UTC\nTop affected query: `handy hülle`\nBefore tokens: [handy, hülle] synonyms=[smartphone, case]\nAfter tokens: [handy, hülle] synonyms=[mobile, cover, shell]\nNew synonym file generated from merchant vocabulary\nRule source line: `handy => mobile, cover, shell`\nGerman analyzer treats expansion as equivalent terms\nOffline NDCG check passed on global English-heavy set\nRollback restored conversion after 22 minutes\n```\n\nDetermine why the quality gate missed the regression and whether synonym direction, locale scoping, or evaluation coverage is the primary issue.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Add comparison text below the ranking chart","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.27,"slice":"core","lang":"en"} -{"prompt":"Restructure the query parser and document its extension API. Preserve syntax and errors while separating tokenization, parsing, normalization, and validation.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.77,"slice":"mixed","lang":"en"} -{"prompt":"Architect a global catalog platform with regional writes, product ownership, conflict handling, replication, search freshness, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"boundary","lang":"en"} -{"prompt":"Implement cryptographically signed index manifests with shard digests and generation history.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new ranking feature, including schemas, backfills, online serving, evaluation, and launch.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Consolidate sponsored-result insertion across web and mobile APIs without changing placement behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Investigate why search-result impression events are missing when users navigate with the browser back button.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} +{"prompt":"Extract locale fallback into one shared resolver while preserving language selection and cache keys.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why price-range facets disagree with visible results, implement the proven currency-normalization fix, and update the troubleshooting guide.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed click-based ranking feature for position bias, bot traffic, feedback loops, privacy, and manipulation. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why catalog updates stop after the Debezium connector performs a snapshot.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Draft a migration guide for merchants moving from category IDs to taxonomy paths.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Search quality incident packet:\n\n```text\nMetric: add-to-cart rate from search down 8.4% in de-DE\nNo change in overall search traffic\nDeployment: synonym set generation 244 at 10:12 UTC\nTop affected query: `handy hülle`\nBefore tokens: [handy, hülle] synonyms=[smartphone, case]\nAfter tokens: [handy, hülle] synonyms=[mobile, cover, shell]\nNew synonym file generated from merchant vocabulary\nRule source line: `handy => mobile, cover, shell`\nGerman analyzer treats expansion as equivalent terms\nOffline NDCG check passed on global English-heavy set\nRollback restored conversion after 22 minutes\n```\n\nDetermine why the quality gate missed the regression and whether synonym direction, locale scoping, or evaluation coverage is the primary issue.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Add comparison text below the ranking chart","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Restructure the query parser and document its extension API. Preserve syntax and errors while separating tokenization, parsing, normalization, and validation.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Architect a global catalog platform with regional writes, product ownership, conflict handling, replication, search freshness, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement cryptographically signed index manifests with shard digests and generation history.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new ranking feature, including schemas, backfills, online serving, evaluation, and launch.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Consolidate sponsored-result insertion across web and mobile APIs without changing placement behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Investigate why search-result impression events are missing when users navigate with the browser back button.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Add transactional product publication with catalog and search outbox events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Pin OpenSearch to `3.2.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Build the collection landing page with editorial hero, product rails, lazy loading, personalization fallback, and accessible headings.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Remplace `Recomendations` par `Recommendations` uniquement dans le nouveau titre.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"fr"} -{"prompt":"Inspect the bulk-index endpoint for decompression bombs, oversized fields, tenant spoofing, and partial-failure ambiguity. Report only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Implement search-rule history and write its API documentation. Include versions, actors, diffs, rollback, pagination, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Develop a roadmap for replacing manually curated synonyms with reviewed automated suggestions, including quality gates, human approval, rollback, and metrics.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.84,"slice":"core","lang":"en"} -{"prompt":"Add bounded result caching with inventory-aware invalidation and request coalescing.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Create the mobile visual-search flow with camera permission, crop, upload progress, editable detected objects, and results.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"fix the cards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.31,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `CatID` with `CategoryID` throughout services while preserving protobuf names and JSON fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why personalized recommendations include recently purchased products, implement the verified event-window fix, and add a support note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Why does the index builder sort products by ID before batching? Explain the current determinism and retry rationale.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.43,"slice":"boundary","lang":"en"} -{"prompt":"Track down the occasional stale filter count after an index alias swap.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Write a customer guide for search operators, phrase matching, exclusions, filters, and saved queries.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"Review request notes:\n\n```text\nFeature: semantic query rewriting\nOriginal query and detected locale sent to an LLM\nModel returns rewritten query plus up to five category hints\nPII detector runs before model request\nOriginal query retained for 30 days for evaluation\nRewriter has 120ms budget; timeout falls back to original\nGenerated hints cannot bypass explicit user filters\nResponses cached by normalized query and locale\nRollout begins at 1% of anonymous traffic\nOpen questions: prompt injection, sensitive queries, reproducibility, provider retention\n```\n\nReview privacy, safety, caching, filter integrity, observability, evaluation, and failure behavior. No implementation requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Add loading placeholders to the recommendation rail","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.24,"slice":"core","lang":"en"} -{"prompt":"Plan and implement merchant-managed search redirects. First define matching, precedence, loops, scheduling, preview, audit, and rollout; then build configuration endpoints, query integration, and tests.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.88,"slice":"mixed","lang":"en"} -{"prompt":"Outline an architecture for privacy-compliant recommendation attribution, including consent, identity stitching, retention, deletion, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"boundary","lang":"en"} -{"prompt":"Implement stable search pagination across shard rebalancing using point-in-time snapshots.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Escribe una guía para configurar feeds de catálogo, con validación, errores, reintentos y comprobación de productos.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"es"} +{"prompt":"Pin OpenSearch to `3.2.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the collection landing page with editorial hero, product rails, lazy loading, personalization fallback, and accessible headings.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remplace `Recomendations` par `Recommendations` uniquement dans le nouveau titre.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"fr"} +{"prompt":"Inspect the bulk-index endpoint for decompression bombs, oversized fields, tenant spoofing, and partial-failure ambiguity. Report only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement search-rule history and write its API documentation. Include versions, actors, diffs, rollback, pagination, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Develop a roadmap for replacing manually curated synonyms with reviewed automated suggestions, including quality gates, human approval, rollback, and metrics.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add bounded result caching with inventory-aware invalidation and request coalescing.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the mobile visual-search flow with camera permission, crop, upload progress, editable detected objects, and results.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"fix the cards","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `CatID` with `CategoryID` throughout services while preserving protobuf names and JSON fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose why personalized recommendations include recently purchased products, implement the verified event-window fix, and add a support note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Why does the index builder sort products by ID before batching? Explain the current determinism and retry rationale.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down the occasional stale filter count after an index alias swap.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write a customer guide for search operators, phrase matching, exclusions, filters, and saved queries.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Review request notes:\n\n```text\nFeature: semantic query rewriting\nOriginal query and detected locale sent to an LLM\nModel returns rewritten query plus up to five category hints\nPII detector runs before model request\nOriginal query retained for 30 days for evaluation\nRewriter has 120ms budget; timeout falls back to original\nGenerated hints cannot bypass explicit user filters\nResponses cached by normalized query and locale\nRollout begins at 1% of anonymous traffic\nOpen questions: prompt injection, sensitive queries, reproducibility, provider retention\n```\n\nReview privacy, safety, caching, filter integrity, observability, evaluation, and failure behavior. No implementation requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add loading placeholders to the recommendation rail","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Plan and implement merchant-managed search redirects. First define matching, precedence, loops, scheduling, preview, audit, and rollout; then build configuration endpoints, query integration, and tests.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Outline an architecture for privacy-compliant recommendation attribution, including consent, identity stitching, retention, deletion, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement stable search pagination across shard rebalancing using point-in-time snapshots.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Escribe una guía para configurar feeds de catálogo, con validación, errores, reintentos y comprobación de productos.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} {"prompt":"Move experiment assignment out of `RecommendationController` without changing variants or attribution.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Investigate why the iOS filter sheet loses selected brands after device rotation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"Add atomic product alias changes with redirect history and conflict detection.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Remove the obsolete `boost_v1` toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"core","lang":"en"} -{"prompt":"Build the seller catalog-health dashboard with feed status, issue groups, sample products, and remediation actions.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"`Serach results` を `Search results` に直して。新しい英語見出しだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"ja"} -{"prompt":"Review the autocomplete logging path for raw PII, session identifiers, retention mismatches, and unsafe debug fields.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Implement category-rule simulation and write the API guide. Include hypothetical products, decision traces, scheduling, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Plan a disaster-recovery strategy for catalog and search, including source restoration, index rebuilds, aliases, event replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"core","lang":"en"} -{"prompt":"Add deduplicated image-embedding generation with content hashes and retry-safe state.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Create the responsive synonym editor with grouped rules, validation, conflict warnings, preview, and undo.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"continue the ranking bug","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"Rename `RecResult` to `RecommendationResult` across packages while preserving wire types and public aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why search alerts email products outside the selected region, implement the verified checkpoint-key fix, and update help documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.78,"slice":"mixed","lang":"en"} -{"prompt":"Assess whether the proposed edge search cache preserves consent, regional inventory, pricing, and tenant isolation. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"Find why the indexer retries permanent mapping errors forever and blocks its partition.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Draft a troubleshooting guide for missing products in search, covering publication, feeds, inventory, indexing, and filters.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Data pipeline failure output:\n\n```text\njob=catalog-features date=2026-07-29\ninput products=84,291,104\noutput rows=84,290,771\nquality check missing_product_ids=333\nall missing IDs belong to seller=s_772\nsource partition seller=s_772 files=14\nSpark speculative task attempt 3 committed output part-8841\nattempt 1 later completed and cleanup removed shared temp prefix\nmanifest references part-8841 size=0\njob marked success because row-count tolerance=0.001%\nnext online load skipped zero-byte part without error\n```\n\nDetermine how speculative-attempt cleanup removed the committed output and why quality thresholds plus loader behavior allowed missing features into production.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a selected count to the filter button","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.24,"slice":"core","lang":"en"} -{"prompt":"Restructure the feature-generation pipeline and document its transform interface. Preserve outputs while separating reads, joins, transformations, validation, and publication.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Architect a marketplace-wide product identity service, including merges, splits, seller mappings, history, consistency, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed catalog-feed receipts with accepted row counts and schema digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new search locale, including analyzers, synonyms, fixtures, quality sets, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"Consolidate inventory filtering across lexical and vector retrieval without changing visible results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Investigate why the product-grid scroll position restores to the wrong row after filters change.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Add generation-fenced index cleanup so active snapshots cannot be deleted.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Set the search timeout to 900ms","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Build the mobile saved-search manager with rename, alerts, reorder, delete, and offline states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"把 `Recomend for you` 改成 `Recommended for you`，不要修改 i18n key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"zh"} -{"prompt":"Inspect the search-debug endpoint for unpublished data exposure, query injection, denial-of-service risk, and authorization gaps.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} +{"prompt":"Investigate why the iOS filter sheet loses selected brands after device rotation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add atomic product alias changes with redirect history and conflict detection.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remove the obsolete `boost_v1` toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Build the seller catalog-health dashboard with feed status, issue groups, sample products, and remediation actions.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"`Serach results` を `Search results` に直して。新しい英語見出しだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"ja"} +{"prompt":"Review the autocomplete logging path for raw PII, session identifiers, retention mismatches, and unsafe debug fields.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Implement category-rule simulation and write the API guide. Include hypothetical products, decision traces, scheduling, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan a disaster-recovery strategy for catalog and search, including source restoration, index rebuilds, aliases, event replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add deduplicated image-embedding generation with content hashes and retry-safe state.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the responsive synonym editor with grouped rules, validation, conflict warnings, preview, and undo.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Rename `RecResult` to `RecommendationResult` across packages while preserving wire types and public aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Investigate why search alerts email products outside the selected region, implement the verified checkpoint-key fix, and update help documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess whether the proposed edge search cache preserves consent, regional inventory, pricing, and tenant isolation. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why the indexer retries permanent mapping errors forever and blocks its partition.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Draft a troubleshooting guide for missing products in search, covering publication, feeds, inventory, indexing, and filters.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Data pipeline failure output:\n\n```text\njob=catalog-features date=2026-07-29\ninput products=84,291,104\noutput rows=84,290,771\nquality check missing_product_ids=333\nall missing IDs belong to seller=s_772\nsource partition seller=s_772 files=14\nSpark speculative task attempt 3 committed output part-8841\nattempt 1 later completed and cleanup removed shared temp prefix\nmanifest references part-8841 size=0\njob marked success because row-count tolerance=0.001%\nnext online load skipped zero-byte part without error\n```\n\nDetermine how speculative-attempt cleanup removed the committed output and why quality thresholds plus loader behavior allowed missing features into production.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add a selected count to the filter button","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Restructure the feature-generation pipeline and document its transform interface. Preserve outputs while separating reads, joins, transformations, validation, and publication.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Architect a marketplace-wide product identity service, including merges, splits, seller mappings, history, consistency, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1,"slice":"core","lang":"en"} +{"prompt":"Implement signed catalog-feed receipts with accepted row counts and schema digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new search locale, including analyzers, synonyms, fixtures, quality sets, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Consolidate inventory filtering across lexical and vector retrieval without changing visible results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Investigate why the product-grid scroll position restores to the wrong row after filters change.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add generation-fenced index cleanup so active snapshots cannot be deleted.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Set the search timeout to 900ms","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile saved-search manager with rename, alerts, reorder, delete, and offline states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"把 `Recomend for you` 改成 `Recommended for you`，不要修改 i18n key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"zh"} +{"prompt":"Inspect the search-debug endpoint for unpublished data exposure, query injection, denial-of-service risk, and authorization gaps.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Implement index-generation history and write its API documentation. Include aliases, build inputs, validation, activation, rollback, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Design a longitudinal clinical-record architecture that merges encounters, labs, medications, and patient corrections from multiple source systems. Cover identity, provenance, versioning, consent, late data, deletion restrictions, auditability, regional storage, and migration from source-specific tables. Deliver an RFC and rollout plan only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"core","lang":"en"} -{"prompt":"Before implementing FHIR subscriptions, outline the delivery design for filters, authorization, retry, ordering, replay, de-identification, tenant isolation, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"boundary","lang":"en"} -{"prompt":"Add conditional create support to `/Patient`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Interface-engine logs from the incident:\n\n```text\nsource=hospital_17 message_type=ORU^R01 control_id=MSG88217\nreceived_at=2026-07-29T22:14:02.114Z\npatient lookup mrn=004981 result=one_match internal_id=pt_81\nOBX-3=LOINC:718-7 OBX-5=13.8 units=g/dL status=F\ninsert observation version=1 success\nsame control_id redelivered at=22:14:06.801Z\nidempotency lookup result=miss shard=3\ninsert observation version=2 success\nlater lookup control_id=MSG88217 shard=7 result=two_rows\nrouter shard key changed from sender_facility to patient_id in deploy\n```\n\nDetermine why the retry crosses idempotency shards and creates a duplicate finalized observation, and whether routing or storage constraints should have prevented it.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Build the SwiftUI medication-history screen with grouped dates, status badges, prescriber details, refill actions, and VoiceOver-safe terminology.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Plan and implement a consent-enforcement service for clinical data access. Begin with a design covering policy sources, purpose of use, emergency overrides, patient revocation, cache invalidation, audit evidence, regional rules, failure behavior, and migration. Then add the policy API, evaluator, decision logs, and conformance tests. Treat the policy semantics and safety analysis as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.98,"slice":"mixed","lang":"en"} -{"prompt":"Set `MAX_OBSERVATIONS` to 500","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Extract duplicated FHIR date parsing from Patient and Observation mappers while preserving accepted precision and errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Implement `/internal/terminology/status` with code-system versions, load time, cache age, and failed expansions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"make the clinician screen calmer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.42,"slice":"vague-eval","lang":"en"} -{"prompt":"Find why finalized lab results occasionally revert to preliminary after an interface-engine replay.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"Explain how `PatientMatcher` weights names, birth dates, addresses, and identifiers, including its ambiguous-match behavior. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} +{"prompt":"Design a longitudinal clinical-record architecture that merges encounters, labs, medications, and patient corrections from multiple source systems. Cover identity, provenance, versioning, consent, late data, deletion restrictions, auditability, regional storage, and migration from source-specific tables. Deliver an RFC and rollout plan only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Before implementing FHIR subscriptions, outline the delivery design for filters, authorization, retry, ordering, replay, de-identification, tenant isolation, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add conditional create support to `/Patient`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Interface-engine logs from the incident:\n\n```text\nsource=hospital_17 message_type=ORU^R01 control_id=MSG88217\nreceived_at=2026-07-29T22:14:02.114Z\npatient lookup mrn=004981 result=one_match internal_id=pt_81\nOBX-3=LOINC:718-7 OBX-5=13.8 units=g/dL status=F\ninsert observation version=1 success\nsame control_id redelivered at=22:14:06.801Z\nidempotency lookup result=miss shard=3\ninsert observation version=2 success\nlater lookup control_id=MSG88217 shard=7 result=two_rows\nrouter shard key changed from sender_facility to patient_id in deploy\n```\n\nDetermine why the retry crosses idempotency shards and creates a duplicate finalized observation, and whether routing or storage constraints should have prevented it.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Build the SwiftUI medication-history screen with grouped dates, status badges, prescriber details, refill actions, and VoiceOver-safe terminology.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Plan and implement a consent-enforcement service for clinical data access. Begin with a design covering policy sources, purpose of use, emergency overrides, patient revocation, cache invalidation, audit evidence, regional rules, failure behavior, and migration. Then add the policy API, evaluator, decision logs, and conformance tests. Treat the policy semantics and safety analysis as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":1,"slice":"mixed","lang":"en"} +{"prompt":"Set `MAX_OBSERVATIONS` to 500","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Extract duplicated FHIR date parsing from Patient and Observation mappers while preserving accepted precision and errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement `/internal/terminology/status` with code-system versions, load time, cache age, and failed expansions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"make the clinician screen calmer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Find why finalized lab results occasionally revert to preliminary after an interface-engine replay.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Explain how `PatientMatcher` weights names, birth dates, addresses, and identifiers, including its ambiguous-match behavior. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Deployment notes for customer success:\n\n```text\nFeature: patient-requested record corrections\nPatients submit a request against one visible record item\nRequests can include explanation and attachments\nSubmitting does not alter the clinical record\nHealth-information management staff review and disposition requests\nApproved corrections create an addendum; original data remains visible to authorized users\nStatus values: submitted, under review, accepted, partially accepted, denied\nOrganizations configure response-time targets\nNotifications contain no clinical details\nEmergency contact and demographic edits still use existing workflows\n```\n\nTurn this into patient-facing release notes and an administrator setup guide. Use neutral language and distinguish requests from actual record changes.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} -{"prompt":"Move the allergy warning icon closer to its label","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.13,"slice":"boundary","lang":"en"} -{"prompt":"Write an operator guide for replaying quarantined HL7 messages, including validation, deduplication, dry runs, and verification.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Implement the patient-merge endpoint with authorization, preview, immutable audit events, and conflict handling, then document its contract and irreversible effects.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} +{"prompt":"Move the allergy warning icon closer to its label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Write an operator guide for replaying quarantined HL7 messages, including validation, deduplication, dry runs, and verification.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement the patient-merge endpoint with authorization, preview, immutable audit events, and conflict handling, then document its contract and irreversible effects.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Map out a migration from proprietary lab codes to LOINC, covering mapping confidence, dual coding, historical data, review queues, validation, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Rename `patId` to `patientId` in `ResultMapper.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"en"} -{"prompt":"Teach the DICOM ingestion worker to resume multipart studies and reject mixed-patient series.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Polish the appointment status card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.28,"slice":"core","lang":"en"} -{"prompt":"Bump `hapi-fhir` to `8.4.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Rename `MasterPatientIndex` to `EnterprisePatientIndex` across packages, configuration, metrics, and documentation while preserving APIs and matching behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.68,"slice":"boundary","lang":"en"} -{"prompt":"Split `ClinicalDocumentProcessor` into parsing, validation, normalization, persistence, and indexing components without changing outputs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Implementation ticket:\n\n```text\nLAB-904 — specimen chain-of-custody events\nEvents: collected, labeled, handed_off, received, aliquoted, disposed\nEach event includes specimen ID, actor, location, device time, server time, and optional note\nRules:\n- events are append-only\n- device time may be offline and out of order\n- a disposed specimen cannot receive later workflow events without supervisor override\n- duplicate scanner submissions are common\n- corrections reference the incorrect event; they never delete it\n- every override requires a reason and audit event\n- expose missing handoff and invalid transition counters\n```\n\nImplement the event model, commands, idempotency, transition checks, override flow, persistence, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Investigate why the Android barcode scanner sometimes associates a specimen with the previously opened order.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Create the specimen timeline UI and add a short legend for custody, corrections, overrides, and delayed offline events.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.66,"slice":"mixed","lang":"en"} -{"prompt":"Why does the document service preserve unknown CDA sections instead of dropping them? Explain current compatibility behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.47,"slice":"core","lang":"en"} -{"prompt":"Rewrite the local setup for running HAPI FHIR, Orthanc, Kafka, and synthetic patient fixtures.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"This validation test became flaky after parallel terminology loading:\n\n```text\nFAIL MedicationValidatorTest.rejectsInactiveCode\nsystem=http://www.nlm.nih.gov/research/umls/rxnorm code=884173\nexpected issue=code-inactive actual=valid\nloader generation=211 started=08:01:12.001\nrequest captured generation=210\ncache miss key=rxnorm:884173\nloader swapped active store generation=211 at=08:01:12.041\nlookup executed store generation=211\nrequest audit recorded terminology_generation=210\n```\n\nDetermine whether request-scoped generation pinning is broken or the test observes an unsupported consistency guarantee. The audit record and actual lookup disagree.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.77,"slice":"boundary","lang":"en"} -{"prompt":"finish the FHIR service","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"Propose an architecture for de-identifying imaging studies for research, including tag policy, pixel data, burned-in text, provenance, validation, and release controls.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Add NDJSON bulk export to the FHIR CLI","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Code review excerpt:\n\n```diff\n async function getPatient(req, res) {\n- const decision = await consent.check(req.user, req.params.id, 'treatment')\n- if (!decision.allowed) return res.sendStatus(403)\n- return res.json(await patients.load(req.params.id))\n+ const patient = await patients.load(req.params.id)\n+ consent.check(req.user, patient.id, 'treatment').catch(logger.warn)\n+ return res.json(patient)\n }\n```\n\nThe author says consent failures should not block clinical workflows. Review the security, legal, failure, audit, and data-disclosure implications. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Schreibe eine kurze Referenz für die bestehenden FHIR-Suchparameter, einschließlich Verkettung, Includes und Paginierung. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"de"} -{"prompt":"Build the desktop imaging-worklist with study thumbnails, modality filters, urgency, assignment, and keyboard navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Review the current audit-log event model, explain provenance and correction linking, then turn the findings into an integrator guide.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.63,"slice":"mixed","lang":"en"} -{"prompt":"Set the terminology cache TTL to 6 hours","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"Benenne `ObsCtx` repositoryweit in `ObservationContext` um; FHIR-Felder und Laufzeitverhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"de"} -{"prompt":"Consolidate measurement-unit normalization across lab and device ingestion without changing stored values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Diagnose the duplicated encounter card","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Explain how `ConsentCache` handles revocation while a batch export is already running.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Create API documentation for the existing clinical-note amendment endpoint, including status, provenance, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"boundary","lang":"en"} -{"prompt":"Plan the migration from nightly patient exports to event-driven exchange, covering ordering, replay, consent changes, backfills, validation, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"core","lang":"en"} -{"prompt":"Mobile design ticket:\n\n```text\nScreen: lab result detail\nHeader: test name, value, unit, reference range, finality status\nTrend chart shown only when comparable historical results exist\nReference ranges may vary by lab, age, sex, and effective date\nAbnormal markers must not rely on color\nExplanatory text must not interpret or diagnose the result\nActions: download report, ask clinic, view source organization\nStates: corrected result, preliminary result, unavailable range, loading, offline cached\nAccessibility: chart has data table and announces source plus date\n```\n\nImplement the iOS screen and UI tests using the existing result model. Do not add clinical interpretation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"pasted-context","lang":"en"} -{"prompt":"Implement `POST /v1/consents/{id}/revoke` with version checks, cache invalidation, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"boundary","lang":"en"} -{"prompt":"Remove the extra colon from the result label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"core","lang":"en"} -{"prompt":"Fix the clipped unit label and extract the repeated value-column width into the shared result styles.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.38,"slice":"mixed","lang":"en"} -{"prompt":"Replace scattered document-status booleans with one explicit state enum while preserving transitions and FHIR output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Cambia `specId` por `specimenId` solo en `ScannerState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"es"} -{"prompt":"Investigate why the clinician portal briefly shows another patient's name after using browser back.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Summarize the current record-correction workflow for compliance reviewers using code and tests as sources.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Develop a capacity roadmap for retaining diagnostic images for thirty years. Include storage tiers, retrieval SLAs, integrity checks, migrations, deletion exceptions, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"core","lang":"en"} -{"prompt":"Implement idempotent medication-dispense ingestion with source-version ordering and correction support.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Create the Compose patient-search screen with demographic filters, ambiguous matches, privacy-safe previews, and TalkBack support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Fix `medcation` in `codes.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} -{"prompt":"Merge duplicate identifier-normalization paths used by registration and patient matching while preserving results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Device telemetry from a bedside monitor integration:\n\n```text\ndevice=mon_881 firmware=5.7 gateway=gw_12\nsequence=148211 heart_rate=82 timestamp=11:24:01.200\nsequence=148212 heart_rate=0 quality=disconnected timestamp=11:24:01.400\nnetwork loss begins\nsequence=148900 heart_rate=79 timestamp=11:26:18.800 delivered after reconnect\nserver last_sequence=148212\nbatch range=148213..148900 count=688\nvalidator rejected entire batch reason='timestamp regression at item 391'\ndevice clock adjusted -42s by NTP during outage\nretry repeats forever\n```\n\nDetermine why one clock adjustment poisons the whole buffered batch and whether sequence order or device time should govern acceptance and retry behavior.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.81,"slice":"pasted-context","lang":"en"} -{"prompt":"Rename `allergie_code` to `allergy_code` in the unreleased migration.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"en"} -{"prompt":"Assess whether the research-export pseudonymization allows records from the same patient to be linked across studies unintentionally. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"Restructure the clinical SDK into resources, search, subscriptions, and shared types, then write a maintainer note. Preserve public APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Plan the retirement of a legacy HL7 v2 interface, covering partner inventory, message parity, dual delivery, acknowledgements, validation, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"core","lang":"en"} -{"prompt":"Add immutable provenance chains to transformed clinical observations.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Build the tablet care-team directory with role grouping, availability, secure contact actions, and accessible search.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} +{"prompt":"Rename `patId` to `patientId` in `ResultMapper.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Teach the DICOM ingestion worker to resume multipart studies and reject mixed-patient series.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Polish the appointment status card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump `hapi-fhir` to `8.4.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Rename `MasterPatientIndex` to `EnterprisePatientIndex` across packages, configuration, metrics, and documentation while preserving APIs and matching behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Split `ClinicalDocumentProcessor` into parsing, validation, normalization, persistence, and indexing components without changing outputs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implementation ticket:\n\n```text\nLAB-904 — specimen chain-of-custody events\nEvents: collected, labeled, handed_off, received, aliquoted, disposed\nEach event includes specimen ID, actor, location, device time, server time, and optional note\nRules:\n- events are append-only\n- device time may be offline and out of order\n- a disposed specimen cannot receive later workflow events without supervisor override\n- duplicate scanner submissions are common\n- corrections reference the incorrect event; they never delete it\n- every override requires a reason and audit event\n- expose missing handoff and invalid transition counters\n```\n\nImplement the event model, commands, idempotency, transition checks, override flow, persistence, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Investigate why the Android barcode scanner sometimes associates a specimen with the previously opened order.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the specimen timeline UI and add a short legend for custody, corrections, overrides, and delayed offline events.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Why does the document service preserve unknown CDA sections instead of dropping them? Explain current compatibility behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Rewrite the local setup for running HAPI FHIR, Orthanc, Kafka, and synthetic patient fixtures.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"This validation test became flaky after parallel terminology loading:\n\n```text\nFAIL MedicationValidatorTest.rejectsInactiveCode\nsystem=http://www.nlm.nih.gov/research/umls/rxnorm code=884173\nexpected issue=code-inactive actual=valid\nloader generation=211 started=08:01:12.001\nrequest captured generation=210\ncache miss key=rxnorm:884173\nloader swapped active store generation=211 at=08:01:12.041\nlookup executed store generation=211\nrequest audit recorded terminology_generation=210\n```\n\nDetermine whether request-scoped generation pinning is broken or the test observes an unsupported consistency guarantee. The audit record and actual lookup disagree.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"finish the FHIR service","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"vague-eval","lang":"en"} +{"prompt":"Propose an architecture for de-identifying imaging studies for research, including tag policy, pixel data, burned-in text, provenance, validation, and release controls.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add NDJSON bulk export to the FHIR CLI","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Code review excerpt:\n\n```diff\n async function getPatient(req, res) {\n- const decision = await consent.check(req.user, req.params.id, 'treatment')\n- if (!decision.allowed) return res.sendStatus(403)\n- return res.json(await patients.load(req.params.id))\n+ const patient = await patients.load(req.params.id)\n+ consent.check(req.user, patient.id, 'treatment').catch(logger.warn)\n+ return res.json(patient)\n }\n```\n\nThe author says consent failures should not block clinical workflows. Review the security, legal, failure, audit, and data-disclosure implications. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Schreibe eine kurze Referenz für die bestehenden FHIR-Suchparameter, einschließlich Verkettung, Includes und Paginierung. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"de"} +{"prompt":"Build the desktop imaging-worklist with study thumbnails, modality filters, urgency, assignment, and keyboard navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Review the current audit-log event model, explain provenance and correction linking, then turn the findings into an integrator guide.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Set the terminology cache TTL to 6 hours","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Benenne `ObsCtx` repositoryweit in `ObservationContext` um; FHIR-Felder und Laufzeitverhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"de"} +{"prompt":"Consolidate measurement-unit normalization across lab and device ingestion without changing stored values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose the duplicated encounter card","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Explain how `ConsentCache` handles revocation while a batch export is already running.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Create API documentation for the existing clinical-note amendment endpoint, including status, provenance, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Plan the migration from nightly patient exports to event-driven exchange, covering ordering, replay, consent changes, backfills, validation, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Mobile design ticket:\n\n```text\nScreen: lab result detail\nHeader: test name, value, unit, reference range, finality status\nTrend chart shown only when comparable historical results exist\nReference ranges may vary by lab, age, sex, and effective date\nAbnormal markers must not rely on color\nExplanatory text must not interpret or diagnose the result\nActions: download report, ask clinic, view source organization\nStates: corrected result, preliminary result, unavailable range, loading, offline cached\nAccessibility: chart has data table and announces source plus date\n```\n\nImplement the iOS screen and UI tests using the existing result model. Do not add clinical interpretation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Implement `POST /v1/consents/{id}/revoke` with version checks, cache invalidation, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remove the extra colon from the result label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fix the clipped unit label and extract the repeated value-column width into the shared result styles.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Replace scattered document-status booleans with one explicit state enum while preserving transitions and FHIR output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Cambia `specId` por `specimenId` solo en `ScannerState.swift`; no cambies la lógica.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"es"} +{"prompt":"Investigate why the clinician portal briefly shows another patient's name after using browser back.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Summarize the current record-correction workflow for compliance reviewers using code and tests as sources.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Develop a capacity roadmap for retaining diagnostic images for thirty years. Include storage tiers, retrieval SLAs, integrity checks, migrations, deletion exceptions, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement idempotent medication-dispense ingestion with source-version ordering and correction support.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create the Compose patient-search screen with demographic filters, ambiguous matches, privacy-safe previews, and TalkBack support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Fix `medcation` in `codes.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Merge duplicate identifier-normalization paths used by registration and patient matching while preserving results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Device telemetry from a bedside monitor integration:\n\n```text\ndevice=mon_881 firmware=5.7 gateway=gw_12\nsequence=148211 heart_rate=82 timestamp=11:24:01.200\nsequence=148212 heart_rate=0 quality=disconnected timestamp=11:24:01.400\nnetwork loss begins\nsequence=148900 heart_rate=79 timestamp=11:26:18.800 delivered after reconnect\nserver last_sequence=148212\nbatch range=148213..148900 count=688\nvalidator rejected entire batch reason='timestamp regression at item 391'\ndevice clock adjusted -42s by NTP during outage\nretry repeats forever\n```\n\nDetermine why one clock adjustment poisons the whole buffered batch and whether sequence order or device time should govern acceptance and retry behavior.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Rename `allergie_code` to `allergy_code` in the unreleased migration.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Assess whether the research-export pseudonymization allows records from the same patient to be linked across studies unintentionally. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Restructure the clinical SDK into resources, search, subscriptions, and shared types, then write a maintainer note. Preserve public APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan the retirement of a legacy HL7 v2 interface, covering partner inventory, message parity, dual delivery, acknowledgements, validation, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add immutable provenance chains to transformed clinical observations.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Build the tablet care-team directory with role grouping, availability, secure contact actions, and accessible search.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"do the patient page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `PatRef` with `PatientReference` across packages while preserving serialized field names and public aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why downloaded clinical PDFs omit addenda, implement the verified document-assembly fix, and add a support note for regenerating affected exports.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Why does the subscription service delay delivery for 30 seconds after a patient merge? Explain existing consistency behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Track down the memory leak in the DICOM thumbnail worker after processing multiframe studies.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Write release notes for configurable result-notification delays, including defaults, exceptions, and old-client behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.36,"slice":"core","lang":"en"} -{"prompt":"Consent redesign notes:\n\n```text\nCurrent: one organization-wide consent flag per patient\nNew need: permission by data category, purpose, recipient, and time range\nEmergency access may override treatment restrictions but never research restrictions\nRevocation should affect new reads within five minutes\nExisting exports may run for hours\nPatients need a human-readable history of decisions\nImported consent documents may conflict with portal choices\nSource authority differs by jurisdiction\nOld clients understand only allowed or denied\n```\n\nProduce an implementation-free data model and migration plan covering precedence, conflicts, emergency access, revocation, exports, compatibility, audit, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"pasted-context","lang":"en"} -{"prompt":"Give the imaging viewer a clearer toolbar hierarchy","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.34,"slice":"core","lang":"en"} -{"prompt":"Turn the existing patient-matching behavior into administrator documentation, then review whether confidence thresholds and manual-review claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Outline a phased architecture for moving terminology lookup from embedded files to a managed service, without implementing it yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.84,"slice":"boundary","lang":"en"} -{"prompt":"Implement version-aware FHIR resource history with deletion tombstones and pagination.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Create an operator guide for diagnosing delayed ADT messages without exposing patient data in logs.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"Move code-system expansion out of `TerminologyController` while preserving results and cache behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Investigate why revoked proxy access remains visible in one regional clinician portal.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Add generation-fenced terminology publication with atomic rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Set the imaging upload timeout to 20 minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"Create the responsive care-plan timeline with milestones, assignments, overdue states, and accessible chronology.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Corrige apenas `patint` para `patient` no novo título.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"pt"} -{"prompt":"Review the bulk FHIR import path for tenant confusion, reference spoofing, oversized bundles, and partial-commit ambiguity.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Implement clinical-document export jobs and write the integration guide. Include filters, consent checks, asynchronous states, retention, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.73,"slice":"mixed","lang":"en"} -{"prompt":"Design a migration from organization-local patient IDs to a federated identity graph, including confidence, merges, splits, privacy, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"core","lang":"en"} -{"prompt":"Add resumable DICOMweb uploads with per-instance checksums and duplicate detection.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Build the desktop terminology browser with hierarchy navigation, version comparison, mappings, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"continue the consent work","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.59,"slice":"vague-eval","lang":"en"} -{"prompt":"Extract resource-reference normalization into one utility while preserving canonical URLs and accepted forms.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why corrected lab results trigger two patient notifications, implement the verified event-deduplication fix, and update operator documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed clinical-data cache for consent revocation, emergency access, regional rules, stale demographics, and isolation. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"boundary","lang":"en"} -{"prompt":"Find why one interface-engine partition stops acknowledging messages after a malformed segment.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Draft a migration guide for partners moving from HL7 v2 results to FHIR DiagnosticReport resources.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Data-quality incident report:\n\n```text\npipeline=medication-normalization date=2026-07-29\ninput rows=22,841,992\nmapped to RxNorm=22,102,114\nunmapped=739,878 baseline=81,220\nsource facility=fac_91 accounts for 654,118 unmapped\nraw code examples: '00093-1045-98 ', '00093104598', '00093‐1045‐98'\nnormalizer strips ASCII hyphen and spaces\nnew feed contains Unicode U+2010 hyphen\nquality gate checks total row count and null medication name, not mapping rate\npipeline published generation=418 automatically\n```\n\nDetermine why normalization and quality checks missed the format change and what evidence confirms the Unicode delimiter as the cause.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"pasted-context","lang":"en"} -{"prompt":"Add source-organization text below the result","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.24,"slice":"core","lang":"en"} -{"prompt":"Restructure the de-identification pipeline and document its transform interface. Preserve outputs while separating detection, policy, transformation, validation, and release.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.83,"slice":"mixed","lang":"en"} -{"prompt":"Architect a national-scale immunization exchange with regional ownership, deduplication, consent, corrections, availability, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.98,"slice":"boundary","lang":"en"} +{"prompt":"Replace `PatRef` with `PatientReference` across packages while preserving serialized field names and public aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose why downloaded clinical PDFs omit addenda, implement the verified document-assembly fix, and add a support note for regenerating affected exports.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the subscription service delay delivery for 30 seconds after a patient merge? Explain existing consistency behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down the memory leak in the DICOM thumbnail worker after processing multiframe studies.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write release notes for configurable result-notification delays, including defaults, exceptions, and old-client behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Consent redesign notes:\n\n```text\nCurrent: one organization-wide consent flag per patient\nNew need: permission by data category, purpose, recipient, and time range\nEmergency access may override treatment restrictions but never research restrictions\nRevocation should affect new reads within five minutes\nExisting exports may run for hours\nPatients need a human-readable history of decisions\nImported consent documents may conflict with portal choices\nSource authority differs by jurisdiction\nOld clients understand only allowed or denied\n```\n\nProduce an implementation-free data model and migration plan covering precedence, conflicts, emergency access, revocation, exports, compatibility, audit, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Give the imaging viewer a clearer toolbar hierarchy","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Turn the existing patient-matching behavior into administrator documentation, then review whether confidence thresholds and manual-review claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Outline a phased architecture for moving terminology lookup from embedded files to a managed service, without implementing it yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement version-aware FHIR resource history with deletion tombstones and pagination.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create an operator guide for diagnosing delayed ADT messages without exposing patient data in logs.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Move code-system expansion out of `TerminologyController` while preserving results and cache behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why revoked proxy access remains visible in one regional clinician portal.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add generation-fenced terminology publication with atomic rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Set the imaging upload timeout to 20 minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Create the responsive care-plan timeline with milestones, assignments, overdue states, and accessible chronology.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Corrige apenas `patint` para `patient` no novo título.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.0,"slice":"core","lang":"pt"} +{"prompt":"Review the bulk FHIR import path for tenant confusion, reference spoofing, oversized bundles, and partial-commit ambiguity.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement clinical-document export jobs and write the integration guide. Include filters, consent checks, asynchronous states, retention, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Design a migration from organization-local patient IDs to a federated identity graph, including confidence, merges, splits, privacy, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add resumable DICOMweb uploads with per-instance checksums and duplicate detection.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Build the desktop terminology browser with hierarchy navigation, version comparison, mappings, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Extract resource-reference normalization into one utility while preserving canonical URLs and accepted forms.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Investigate why corrected lab results trigger two patient notifications, implement the verified event-deduplication fix, and update operator documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed clinical-data cache for consent revocation, emergency access, regional rules, stale demographics, and isolation. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why one interface-engine partition stops acknowledging messages after a malformed segment.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Draft a migration guide for partners moving from HL7 v2 results to FHIR DiagnosticReport resources.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Data-quality incident report:\n\n```text\npipeline=medication-normalization date=2026-07-29\ninput rows=22,841,992\nmapped to RxNorm=22,102,114\nunmapped=739,878 baseline=81,220\nsource facility=fac_91 accounts for 654,118 unmapped\nraw code examples: '00093-1045-98 ', '00093104598', '00093‐1045‐98'\nnormalizer strips ASCII hyphen and spaces\nnew feed contains Unicode U+2010 hyphen\nquality gate checks total row count and null medication name, not mapping rate\npipeline published generation=418 automatically\n```\n\nDetermine why normalization and quality checks missed the format change and what evidence confirms the Unicode delimiter as the cause.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"Add source-organization text below the result","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Restructure the de-identification pipeline and document its transform interface. Preserve outputs while separating detection, policy, transformation, validation, and release.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Architect a national-scale immunization exchange with regional ownership, deduplication, consent, corrections, availability, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} {"prompt":"Implement signed provenance receipts for clinical data imports.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new FHIR profile, including validation, search, examples, compatibility, and conformance tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.47,"slice":"core","lang":"en"} -{"prompt":"Consolidate patient-name formatting across portal and export services without changing displayed results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Investigate why encounter updates arrive in the portal before their associated care-team records.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.64,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional research-cohort publication with immutable criteria snapshots.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Pin Orthanc to `1.12.9`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Build the mobile consent-history view with purpose grouping, effective dates, revocation, downloads, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Remplace `Observaton` par `Observation` uniquement dans le nouveau libellé.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"fr"} -{"prompt":"Inspect the diagnostic-report download endpoint for identifier enumeration, stale authorization, range-request abuse, and cache leakage.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Implement terminology-version history and write its API documentation. Include activation, mappings, rollback, pagination, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Develop a roadmap for replacing manual chart abstraction with assisted extraction, including evaluation, human review, provenance, bias checks, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"core","lang":"en"} -{"prompt":"Add bounded event replay for patient timelines with checkpointed projections.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Create the responsive clinic-location picker with distance, availability, accessibility features, map alternative, and saved choices.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"fix the result issue","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.52,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `TermSvc` with `TerminologyService` across packages while preserving configuration and APIs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why research exports contain revoked records, implement the verified consent-checkpoint fix, and add a compliance-facing incident note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.87,"slice":"mixed","lang":"en"} -{"prompt":"Why does the patient matcher retain rejected candidate pairs? Explain the current audit and model-evaluation rationale.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.47,"slice":"boundary","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new FHIR profile, including validation, search, examples, compatibility, and conformance tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Consolidate patient-name formatting across portal and export services without changing displayed results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why encounter updates arrive in the portal before their associated care-team records.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add transactional research-cohort publication with immutable criteria snapshots.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Pin Orthanc to `1.12.9`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile consent-history view with purpose grouping, effective dates, revocation, downloads, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remplace `Observaton` par `Observation` uniquement dans le nouveau libellé.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"fr"} +{"prompt":"Inspect the diagnostic-report download endpoint for identifier enumeration, stale authorization, range-request abuse, and cache leakage.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement terminology-version history and write its API documentation. Include activation, mappings, rollback, pagination, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Develop a roadmap for replacing manual chart abstraction with assisted extraction, including evaluation, human review, provenance, bias checks, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add bounded event replay for patient timelines with checkpointed projections.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create the responsive clinic-location picker with distance, availability, accessibility features, map alternative, and saved choices.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"fix the result issue","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `TermSvc` with `TerminologyService` across packages while preserving configuration and APIs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose why research exports contain revoked records, implement the verified consent-checkpoint fix, and add a compliance-facing incident note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Why does the patient matcher retain rejected candidate pairs? Explain the current audit and model-evaluation rationale.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} {"prompt":"Track down intermittent corrupt thumbnails for compressed ultrasound studies.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write a troubleshooting guide for missing clinical documents, covering source delivery, validation, consent, indexing, and merges.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Security review packet:\n\n```text\nFeature: clinician break-glass access\nTrigger: user chooses emergency access and enters free-text reason\nScope: one patient, all treatment data, 60 minutes\nNo manager approval required before access\nPatient and privacy office receive notification within 24 hours\nRepeated use enters weekly review report\nAccess cannot reveal specially restricted research data\nSession continues if notification service is unavailable\nCurrent UI preselects the most recently viewed patient\nAudit stores reason, user, patient, time, and viewed resources\n```\n\nReview the workflow for accidental use, target binding, scope, duration, notification failure, reason quality, auditing, and abuse detection. Do not implement.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.81,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a loading skeleton to the care timeline","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Plan and implement organization-managed retention policies for clinical messages. First define legal holds, category rules, patient access, backups, deletion evidence, conflicts, and rollout; then add policy storage and enforcement jobs.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.95,"slice":"mixed","lang":"en"} -{"prompt":"Outline an architecture for near-real-time public-health reporting with corrections, provenance, de-identification, regional outages, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"boundary","lang":"en"} +{"prompt":"Write a troubleshooting guide for missing clinical documents, covering source delivery, validation, consent, indexing, and merges.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Security review packet:\n\n```text\nFeature: clinician break-glass access\nTrigger: user chooses emergency access and enters free-text reason\nScope: one patient, all treatment data, 60 minutes\nNo manager approval required before access\nPatient and privacy office receive notification within 24 hours\nRepeated use enters weekly review report\nAccess cannot reveal specially restricted research data\nSession continues if notification service is unavailable\nCurrent UI preselects the most recently viewed patient\nAudit stores reason, user, patient, time, and viewed resources\n```\n\nReview the workflow for accidental use, target binding, scope, duration, notification failure, reason quality, auditing, and abuse detection. Do not implement.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Add a loading skeleton to the care timeline","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Plan and implement organization-managed retention policies for clinical messages. First define legal holds, category rules, patient access, backups, deletion evidence, conflicts, and rollout; then add policy storage and enforcement jobs.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Outline an architecture for near-real-time public-health reporting with corrections, provenance, de-identification, regional outages, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Implement FHIR `_history` pagination with snapshot-consistent cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Escribe una guía para integrar resultados de laboratorio, con validación, códigos, correcciones y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} -{"prompt":"Move consent-purpose mapping out of the export worker without changing access decisions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Investigate why the Android app shows stale appointment availability after changing clinics.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Add atomic clinical-code mapping publication with preview and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Remove the obsolete `legacy_mrn` toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"core","lang":"en"} -{"prompt":"Build the patient-document viewer with section navigation, source metadata, addenda, print, and accessible reading order.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"`Patiet details` を `Patient details` に直して。新しい見出しだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"ja"} -{"prompt":"Review the SMART-on-FHIR launch path for audience validation, patient-context substitution, replay, and stale scopes.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"Implement consent-decision history and write its API guide. Include inputs, outcome, policy version, pagination, redaction, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Plan a disaster-recovery strategy for clinical exchange, including interfaces, queues, terminology, keys, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"core","lang":"en"} -{"prompt":"Add content-hash deduplication to imported clinical documents with provenance preservation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Create the desktop patient-merge review UI with side-by-side demographics, source evidence, conflicts, and confirmation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"continue the data cleanup","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"Rename `ClinDoc` to `ClinicalDocument` across the monorepo while preserving serialized resource names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why patient merges break old document links, implement the verified alias fix, and update migration documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed offline clinician cache for shared devices, consent revocation, encryption, stale data, and logout cleanup.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"boundary","lang":"en"} -{"prompt":"Find why the FHIR subscription worker emits updates out of version order after reconnecting.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Draft a support guide for resolving duplicate patient records without losing provenance.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Pipeline error output:\n\n```text\njob=research-export cohort=co_119 snapshot=2026-07-29T00:00Z\neligible patients=18,442\nexported patients=18,438\nmissing=4\nall missing have merge events after snapshot time\ncohort membership resolved against snapshot\npatient alias resolution queried current table\nold IDs map to new canonical IDs created after snapshot\nresource query uses snapshot and cannot find new canonical IDs\njob records missing as source_deleted and completes successfully\n```\n\nDetermine how mixing snapshot-time membership with current alias resolution loses four patients and why the completion rule misclassifies them as deleted.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Add effective-date text to the consent card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.25,"slice":"core","lang":"en"} -{"prompt":"Restructure the terminology loader and document its provider interface. Preserve lookup results while separating fetch, parse, validate, index, and activate.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"Architect a multi-region clinical terminology service with immutable versions, tenant overlays, availability, audit, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed export manifests with resource counts, policy versions, and content digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new HL7 message type, including parsing, acknowledgements, mappings, fixtures, and monitoring.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Consolidate clinical-date formatting across portal and document exports without changing displayed values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Investigate why a corrected encounter diagnosis remains in search suggestions.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Add transactionally consistent patient timeline projections with replay checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Set the subscription retry limit to 12","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Build the mobile proxy-access manager with relationship labels, expiry, revoke, invite, and accessible confirmations.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"把 `Medcation history` 改成 `Medication history`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"zh"} -{"prompt":"Inspect the research cohort query endpoint for inference attacks, overly precise counts, authorization gaps, and expensive predicates.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} +{"prompt":"Escribe una guía para integrar resultados de laboratorio, con validación, códigos, correcciones y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"es"} +{"prompt":"Move consent-purpose mapping out of the export worker without changing access decisions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why the Android app shows stale appointment availability after changing clinics.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add atomic clinical-code mapping publication with preview and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remove the obsolete `legacy_mrn` toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Build the patient-document viewer with section navigation, source metadata, addenda, print, and accessible reading order.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"`Patiet details` を `Patient details` に直して。新しい見出しだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"ja"} +{"prompt":"Review the SMART-on-FHIR launch path for audience validation, patient-context substitution, replay, and stale scopes.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement consent-decision history and write its API guide. Include inputs, outcome, policy version, pagination, redaction, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Plan a disaster-recovery strategy for clinical exchange, including interfaces, queues, terminology, keys, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add content-hash deduplication to imported clinical documents with provenance preservation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the desktop patient-merge review UI with side-by-side demographics, source evidence, conflicts, and confirmation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Rename `ClinDoc` to `ClinicalDocument` across the monorepo while preserving serialized resource names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Investigate why patient merges break old document links, implement the verified alias fix, and update migration documentation.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed offline clinician cache for shared devices, consent revocation, encryption, stale data, and logout cleanup.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why the FHIR subscription worker emits updates out of version order after reconnecting.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Draft a support guide for resolving duplicate patient records without losing provenance.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Pipeline error output:\n\n```text\njob=research-export cohort=co_119 snapshot=2026-07-29T00:00Z\neligible patients=18,442\nexported patients=18,438\nmissing=4\nall missing have merge events after snapshot time\ncohort membership resolved against snapshot\npatient alias resolution queried current table\nold IDs map to new canonical IDs created after snapshot\nresource query uses snapshot and cannot find new canonical IDs\njob records missing as source_deleted and completes successfully\n```\n\nDetermine how mixing snapshot-time membership with current alias resolution loses four patients and why the completion rule misclassifies them as deleted.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"Add effective-date text to the consent card","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Restructure the terminology loader and document its provider interface. Preserve lookup results while separating fetch, parse, validate, index, and activate.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Architect a multi-region clinical terminology service with immutable versions, tenant overlays, availability, audit, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement signed export manifests with resource counts, policy versions, and content digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new HL7 message type, including parsing, acknowledgements, mappings, fixtures, and monitoring.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Consolidate clinical-date formatting across portal and document exports without changing displayed values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why a corrected encounter diagnosis remains in search suggestions.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add transactionally consistent patient timeline projections with replay checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Set the subscription retry limit to 12","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile proxy-access manager with relationship labels, expiry, revoke, invite, and accessible confirmations.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"把 `Medcation history` 改成 `Medication history`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"zh"} +{"prompt":"Inspect the research cohort query endpoint for inference attacks, overly precise counts, authorization gaps, and expensive predicates.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Implement patient-alias history and write its API documentation. Include merges, splits, effective dates, pagination, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Design a collaborative code-review architecture with threaded comments, suggested edits, file revisions, draft state, offline updates, notifications, and conflict handling. Cover event ordering, permissions, immutable history, search, migration from the current pull-request tables, and rollout milestones. Deliver an RFC only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"core","lang":"en"} -{"prompt":"Before implementing organization-wide code search, outline indexing, authorization trimming, branch scope, freshness, ranking, query privacy, regional availability, and staged adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"boundary","lang":"en"} -{"prompt":"Add thread resolution to the review API","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Message delivery logs from the incident:\n\n```text\nworkspace=w_91 channel=c_18 message=m_882 sequence=44109\nproducer region=us-east publish offset=778221\nfanout worker-a delivered websocket session=s_17\nfanout worker-b retry reason='ack timeout'\nworker-b loaded dedupe key=w_91:m_882 result=miss\nworker-b delivered push notification\nworker-a wrote dedupe key=m_882 ttl=24h\nwebsocket client reconnect replay_from=44108\nreplay service key scope=channel:c_18:m_882 result=miss\ndelivery count observed by user=3\n```\n\nDetermine why each delivery path uses a different idempotency scope and whether the missing acknowledgement or key design is the underlying cause of triple delivery.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Build the desktop command-palette results view with grouped actions, fuzzy highlights, recent items, keyboard navigation, and accessible announcements.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Plan and implement a real-time presence service for documents, terminals, and code reviews. Start with a design covering connection identity, fan-out, idle detection, privacy, reconnect, multi-region routing, overload behavior, and rollout. Then add the gateway, presence store, subscription protocol, metrics, and integration tests. Treat the semantics and failure design as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.94,"slice":"mixed","lang":"en"} -{"prompt":"Set `MAX_REVIEWERS` to 20","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Extract duplicated line-range mapping from comments and diagnostics while preserving every mapped location.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Implement `/internal/fanout/status` with partition ownership, consumer lag, active sessions, and dropped events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"make the editor feel smarter","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"Find why inline review comments jump to the wrong function after a force push with nearby line insertions.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Explain how `RevisionMapper` relocates comments across diffs and when it deliberately marks them outdated. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Internal launch notes:\n\n```text\nFeature: shared terminal sessions\nOne user creates a session and invites workspace members\nParticipants see terminal output and may request input control\nCreator can transfer or revoke control\nAll input-control changes appear in the session audit timeline\nTerminal contents are retained according to workspace log policy\nSecrets matching configured patterns are visually redacted after receipt; redaction is not guaranteed before transport\nSession links expire after 24 hours\nMobile clients can view but cannot type\n```\n\nTurn this into user documentation and an administrator security note. Clearly distinguish visual redaction from transport protection and explain retention and control transfer.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.49,"slice":"pasted-context","lang":"en"} -{"prompt":"Move the editor breadcrumb below the window controls","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.13,"slice":"boundary","lang":"en"} -{"prompt":"Write an operator guide for replaying failed notification events without duplicating email or push delivery.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Implement workspace announcement endpoints with targeting, scheduling, read receipts, and authorization, then document their contract and delivery semantics.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Map out a migration from polling pull-request updates to a durable event stream, including cursors, retention, permissions, old clients, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"core","lang":"en"} -{"prompt":"Rename `revId` to `revisionId` in `CommentAnchor.ts`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"en"} -{"prompt":"Teach the symbol service to index unsaved editor buffers with per-session isolation and expiry.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Polish the review summary panel","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.28,"slice":"core","lang":"en"} -{"prompt":"Bump `monaco-editor` to `0.53.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Rename `MasterWorkspace` to `PrimaryWorkspace` across services, events, tests, and dashboards while preserving API fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.64,"slice":"boundary","lang":"en"} -{"prompt":"Split `NotificationService` into preference, rendering, routing, and delivery components without changing user-visible behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Ticket copied from the collaboration backlog:\n\n```text\nMSG-3304 — scheduled channel messages\nUsers choose channel, message body, and delivery time\nMaximum horizon 90 days\nEditing creates a new immutable revision\nDeletion before delivery records an audit event\nPermissions are checked at creation and again at send time\nAttachments must still exist and remain accessible at delivery\nDuplicate scheduler claims must not send twice\nWorkspace time zone is display-only; store instants in UTC\nExpose scheduled, delivered, cancelled, failed, and permission-rejected metrics\n```\n\nImplement storage, CRUD commands, scheduler claims, send-time validation, attachment checks, audit events, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Investigate why the macOS editor stops receiving diagnostics after waking from sleep.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Create the workspace notification-preferences UI and add concise explanations for mentions, threads, reviews, builds, and quiet hours.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.63,"slice":"mixed","lang":"en"} -{"prompt":"Why does the chat service retain deleted message IDs in its search tombstone index? Explain current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"Rewrite the contributor setup for running NATS, Meilisearch, the collaboration API, and a local websocket gateway.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.34,"slice":"core","lang":"en"} -{"prompt":"The review-navigation test became flaky after virtualizing diff rows:\n\n```text\nFAIL moves_to_next_unresolved_thread\nvisible range lines=880..952\ncurrent thread line=944 id=t_17\nnext unresolved line=1281 id=t_19\nscroll requested anchor=t_19\nvirtualizer estimated offset=42188\nactual rendered line after settle=1264\nsecond correction skipped reason='user_scroll_active'\nfocus remained body\nexpected focus thread=t_19\n```\n\nDetermine whether row-height estimation, scroll-state classification, or focus timing causes the missed target and why the programmatic correction is mistaken for user input.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.74,"slice":"boundary","lang":"en"} -{"prompt":"finish the messaging endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"Propose an architecture for private workspace search across messages, code, documents, and terminals, including authorization, ranking, deletion, and audit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"core","lang":"en"} -{"prompt":"Add RFC 6902 patch output to `reviewctl diff`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.56,"slice":"core","lang":"en"} -{"prompt":"Review excerpt:\n\n```diff\n async function listMessages(req) {\n- const membership = await groups.checkMember(req.user.id, req.params.channel)\n- if (!membership) throw forbidden()\n- return messages.list(req.params.channel, req.query.cursor)\n+ const cacheKey = `${req.user.id}:${req.params.channel}`\n+ const allowed = await redis.get(cacheKey) ?? await groups.checkMember(req.user.id, req.params.channel)\n+ if (!allowed) throw forbidden()\n+ redis.setex(cacheKey, 3600, 'true')\n+ return messages.list(req.params.channel, req.query.cursor)\n }\n```\n\nReview revocation, false-string handling, tenant scoping, cache writes, failures, and the one-hour lifetime. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.67,"slice":"pasted-context","lang":"en"} -{"prompt":"Schreibe eine kurze Referenz für die bestehenden Review-Status und deren Auswirkungen auf Merge und Benachrichtigungen. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.36,"slice":"boundary","lang":"de"} -{"prompt":"Build the responsive inbox with grouped notifications, unread filters, bulk actions, live insertion, and accessible announcements.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Review how the current mention parser handles names, groups, code spans, and escaped text, then produce an integrator guide with examples.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.59,"slice":"mixed","lang":"en"} -{"prompt":"Set the typing indicator timeout to 5s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Benenne `MsgCtx` repositoryweit in `MessageContext` um; JSON-Felder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"de"} -{"prompt":"Consolidate notification-recipient expansion across review and chat flows without changing recipients.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Diagnose the duplicate mention notification","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Explain how the editor's semantic-token cache handles partial document updates and overlapping requests.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Create API documentation for the existing thread subscription endpoints, including mute, watch, defaults, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"boundary","lang":"en"} +{"prompt":"Design a collaborative code-review architecture with threaded comments, suggested edits, file revisions, draft state, offline updates, notifications, and conflict handling. Cover event ordering, permissions, immutable history, search, migration from the current pull-request tables, and rollout milestones. Deliver an RFC only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Before implementing organization-wide code search, outline indexing, authorization trimming, branch scope, freshness, ranking, query privacy, regional availability, and staged adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add thread resolution to the review API","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Message delivery logs from the incident:\n\n```text\nworkspace=w_91 channel=c_18 message=m_882 sequence=44109\nproducer region=us-east publish offset=778221\nfanout worker-a delivered websocket session=s_17\nfanout worker-b retry reason='ack timeout'\nworker-b loaded dedupe key=w_91:m_882 result=miss\nworker-b delivered push notification\nworker-a wrote dedupe key=m_882 ttl=24h\nwebsocket client reconnect replay_from=44108\nreplay service key scope=channel:c_18:m_882 result=miss\ndelivery count observed by user=3\n```\n\nDetermine why each delivery path uses a different idempotency scope and whether the missing acknowledgement or key design is the underlying cause of triple delivery.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Build the desktop command-palette results view with grouped actions, fuzzy highlights, recent items, keyboard navigation, and accessible announcements.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Plan and implement a real-time presence service for documents, terminals, and code reviews. Start with a design covering connection identity, fan-out, idle detection, privacy, reconnect, multi-region routing, overload behavior, and rollout. Then add the gateway, presence store, subscription protocol, metrics, and integration tests. Treat the semantics and failure design as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":1,"slice":"mixed","lang":"en"} +{"prompt":"Set `MAX_REVIEWERS` to 20","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Extract duplicated line-range mapping from comments and diagnostics while preserving every mapped location.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement `/internal/fanout/status` with partition ownership, consumer lag, active sessions, and dropped events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"make the editor feel smarter","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Find why inline review comments jump to the wrong function after a force push with nearby line insertions.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Explain how `RevisionMapper` relocates comments across diffs and when it deliberately marks them outdated. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Internal launch notes:\n\n```text\nFeature: shared terminal sessions\nOne user creates a session and invites workspace members\nParticipants see terminal output and may request input control\nCreator can transfer or revoke control\nAll input-control changes appear in the session audit timeline\nTerminal contents are retained according to workspace log policy\nSecrets matching configured patterns are visually redacted after receipt; redaction is not guaranteed before transport\nSession links expire after 24 hours\nMobile clients can view but cannot type\n```\n\nTurn this into user documentation and an administrator security note. Clearly distinguish visual redaction from transport protection and explain retention and control transfer.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"Move the editor breadcrumb below the window controls","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Write an operator guide for replaying failed notification events without duplicating email or push delivery.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Implement workspace announcement endpoints with targeting, scheduling, read receipts, and authorization, then document their contract and delivery semantics.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Map out a migration from polling pull-request updates to a durable event stream, including cursors, retention, permissions, old clients, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Rename `revId` to `revisionId` in `CommentAnchor.ts`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Teach the symbol service to index unsaved editor buffers with per-session isolation and expiry.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Polish the review summary panel","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump `monaco-editor` to `0.53.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename `MasterWorkspace` to `PrimaryWorkspace` across services, events, tests, and dashboards while preserving API fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Split `NotificationService` into preference, rendering, routing, and delivery components without changing user-visible behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Ticket copied from the collaboration backlog:\n\n```text\nMSG-3304 — scheduled channel messages\nUsers choose channel, message body, and delivery time\nMaximum horizon 90 days\nEditing creates a new immutable revision\nDeletion before delivery records an audit event\nPermissions are checked at creation and again at send time\nAttachments must still exist and remain accessible at delivery\nDuplicate scheduler claims must not send twice\nWorkspace time zone is display-only; store instants in UTC\nExpose scheduled, delivered, cancelled, failed, and permission-rejected metrics\n```\n\nImplement storage, CRUD commands, scheduler claims, send-time validation, attachment checks, audit events, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Investigate why the macOS editor stops receiving diagnostics after waking from sleep.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the workspace notification-preferences UI and add concise explanations for mentions, threads, reviews, builds, and quiet hours.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Why does the chat service retain deleted message IDs in its search tombstone index? Explain current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Rewrite the contributor setup for running NATS, Meilisearch, the collaboration API, and a local websocket gateway.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"The review-navigation test became flaky after virtualizing diff rows:\n\n```text\nFAIL moves_to_next_unresolved_thread\nvisible range lines=880..952\ncurrent thread line=944 id=t_17\nnext unresolved line=1281 id=t_19\nscroll requested anchor=t_19\nvirtualizer estimated offset=42188\nactual rendered line after settle=1264\nsecond correction skipped reason='user_scroll_active'\nfocus remained body\nexpected focus thread=t_19\n```\n\nDetermine whether row-height estimation, scroll-state classification, or focus timing causes the missed target and why the programmatic correction is mistaken for user input.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"finish the messaging endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Propose an architecture for private workspace search across messages, code, documents, and terminals, including authorization, ranking, deletion, and audit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add RFC 6902 patch output to `reviewctl diff`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Review excerpt:\n\n```diff\n async function listMessages(req) {\n- const membership = await groups.checkMember(req.user.id, req.params.channel)\n- if (!membership) throw forbidden()\n- return messages.list(req.params.channel, req.query.cursor)\n+ const cacheKey = `${req.user.id}:${req.params.channel}`\n+ const allowed = await redis.get(cacheKey) ?? await groups.checkMember(req.user.id, req.params.channel)\n+ if (!allowed) throw forbidden()\n+ redis.setex(cacheKey, 3600, 'true')\n+ return messages.list(req.params.channel, req.query.cursor)\n }\n```\n\nReview revocation, false-string handling, tenant scoping, cache writes, failures, and the one-hour lifetime. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Schreibe eine kurze Referenz für die bestehenden Review-Status und deren Auswirkungen auf Merge und Benachrichtigungen. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"de"} +{"prompt":"Build the responsive inbox with grouped notifications, unread filters, bulk actions, live insertion, and accessible announcements.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Review how the current mention parser handles names, groups, code spans, and escaped text, then produce an integrator guide with examples.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Set the typing indicator timeout to 5s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Benenne `MsgCtx` repositoryweit in `MessageContext` um; JSON-Felder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"de"} +{"prompt":"Consolidate notification-recipient expansion across review and chat flows without changing recipients.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose the duplicate mention notification","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Explain how the editor's semantic-token cache handles partial document updates and overlapping requests.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Create API documentation for the existing thread subscription endpoints, including mute, watch, defaults, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Plan a migration from per-repository symbol indexes to a shared workspace graph, covering freshness, permissions, storage, compatibility, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Desktop product ticket:\n\n```text\nFeature: review activity timeline\nEvents: opened, commit pushed, reviewer added, comment, suggestion applied, approval, merge, close\nGroup automated events when more than five occur within one minute\nComments remain individually addressable\nFilters: participants, event type, date range\nLive events insert without moving the reader when scrolled away from top\nPermalinks restore event and expanded thread\nAccessibility: grouped events announce count and range; timestamps expose absolute time\nLarge reviews can exceed 40,000 events\n```\n\nImplement the timeline, virtualization, filters, live insertion, permalink restoration, and component tests.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.75,"slice":"pasted-context","lang":"en"} -{"prompt":"Implement `POST /v1/threads/{id}/resolve` with revision checks, permissions, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"Remove the extra space in the merge label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"core","lang":"en"} -{"prompt":"Fix the clipped unread dot and extract its duplicated offset into the shared notification badge style.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.35,"slice":"mixed","lang":"en"} -{"prompt":"Replace scattered connection booleans with one websocket lifecycle state while preserving reconnect behavior and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Cambia `msgIdx` por `messageIndex` solo en `ThreadReducer.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"es"} -{"prompt":"Investigate why copied code blocks sometimes include hidden diff markers from deleted lines.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Summarize the current notification delivery guarantees for product and SRE reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Develop a capacity roadmap for scaling websocket fan-out from 400,000 to 8 million concurrent sessions. Include partitioning, backpressure, presence, regional failure, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"core","lang":"en"} -{"prompt":"Implement durable unread cursors with per-device reconciliation and monotonic advancement.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Create the Compose code-review summary with checks, reviewers, change stats, merge controls, and TalkBack order.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Fix `notificaton` in `events.proto`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} -{"prompt":"Merge duplicate markdown-link parsers used by comments and chat while preserving offsets and rendering.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Search-index incident logs:\n\n```text\nmessage=m_911 channel=private-ops deleted_at=10:01:12Z\nprimary store tombstone committed sequence=88219\nsearch delete event published offset=41108\nindexer rejected event reason='document version conflict' current_version=91 incoming_version=90\nmessage edit event offset=41092 retried later with version=91\nindexer applied edit and restored document body\npermission filter still allows current channel members\nsearch result visible until manual reindex\n```\n\nDetermine how an older retried edit resurrects a deleted private message and whether event versioning or tombstone precedence is incorrect.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.81,"slice":"pasted-context","lang":"en"} -{"prompt":"Rename `thred_id` to `thread_id` in the unreleased migration.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"en"} -{"prompt":"Assess whether suggested edits can apply to a different revision than the one the reviewer saw. Review anchoring and precondition checks only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Restructure the editor protocol client into transport, requests, notifications, and document state, then write a maintainer note. Preserve behavior.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.75,"slice":"mixed","lang":"en"} +{"prompt":"Desktop product ticket:\n\n```text\nFeature: review activity timeline\nEvents: opened, commit pushed, reviewer added, comment, suggestion applied, approval, merge, close\nGroup automated events when more than five occur within one minute\nComments remain individually addressable\nFilters: participants, event type, date range\nLive events insert without moving the reader when scrolled away from top\nPermalinks restore event and expanded thread\nAccessibility: grouped events announce count and range; timestamps expose absolute time\nLarge reviews can exceed 40,000 events\n```\n\nImplement the timeline, virtualization, filters, live insertion, permalink restoration, and component tests.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Implement `POST /v1/threads/{id}/resolve` with revision checks, permissions, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Remove the extra space in the merge label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fix the clipped unread dot and extract its duplicated offset into the shared notification badge style.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.3,"slice":"mixed","lang":"en"} +{"prompt":"Replace scattered connection booleans with one websocket lifecycle state while preserving reconnect behavior and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Cambia `msgIdx` por `messageIndex` solo en `ThreadReducer.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"es"} +{"prompt":"Investigate why copied code blocks sometimes include hidden diff markers from deleted lines.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Summarize the current notification delivery guarantees for product and SRE reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Develop a capacity roadmap for scaling websocket fan-out from 400,000 to 8 million concurrent sessions. Include partitioning, backpressure, presence, regional failure, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement durable unread cursors with per-device reconciliation and monotonic advancement.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the Compose code-review summary with checks, reviewers, change stats, merge controls, and TalkBack order.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Fix `notificaton` in `events.proto`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Merge duplicate markdown-link parsers used by comments and chat while preserving offsets and rendering.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Search-index incident logs:\n\n```text\nmessage=m_911 channel=private-ops deleted_at=10:01:12Z\nprimary store tombstone committed sequence=88219\nsearch delete event published offset=41108\nindexer rejected event reason='document version conflict' current_version=91 incoming_version=90\nmessage edit event offset=41092 retried later with version=91\nindexer applied edit and restored document body\npermission filter still allows current channel members\nsearch result visible until manual reindex\n```\n\nDetermine how an older retried edit resurrects a deleted private message and whether event versioning or tombstone precedence is incorrect.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Rename `thred_id` to `thread_id` in the unreleased migration.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Assess whether suggested edits can apply to a different revision than the one the reviewer saw. Review anchoring and precondition checks only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Restructure the editor protocol client into transport, requests, notifications, and document state, then write a maintainer note. Preserve behavior.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Plan the retirement of legacy email-based review replies, covering usage, threading, authentication, migration communication, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Add organization-scoped custom emoji with content hashes, moderation states, and cache invalidation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Build the mobile review-thread sheet with context lines, replies, suggestions, resolution, and keyboard-safe scrolling.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"do the inbox","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.38,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `NotifPrefs` with `NotificationPreferences` across clients while preserving wire fields and public aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why quiet hours use the previous timezone after travel, implement the verified cache-key fix, and update user documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Why does the collaboration service retain membership snapshots with delivered notifications? Explain current audit and debugging rationale.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.48,"slice":"boundary","lang":"en"} -{"prompt":"Track down the increasing CPU usage in markdown rendering after long editing sessions.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Write release notes for review templates, including variables, repository defaults, permissions, and old-client behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} +{"prompt":"Add organization-scoped custom emoji with content hashes, moderation states, and cache invalidation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Build the mobile review-thread sheet with context lines, replies, suggestions, resolution, and keyboard-safe scrolling.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"do the inbox","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `NotifPrefs` with `NotificationPreferences` across clients while preserving wire fields and public aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose why quiet hours use the previous timezone after travel, implement the verified cache-key fix, and update user documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the collaboration service retain membership snapshots with delivered notifications? Explain current audit and debugging rationale.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down the increasing CPU usage in markdown rendering after long editing sessions.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Write release notes for review templates, including variables, repository defaults, permissions, and old-client behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Presence design notes:\n\n```text\nCurrent state: websocket gateway writes one Redis key per active document/user\nTTL: 60 seconds; heartbeat: 20 seconds\nNew need: show cursor, selection, active file, and idle status\nPrivacy: workspace owners may disable detailed presence\nUsers can hide presence globally\nReconnect should not briefly show two devices as two people\nA document can have 5,000 simultaneous viewers during incidents\nCross-region sessions may observe 200ms latency\nPresence must degrade before message delivery under overload\n```\n\nProduce an implementation-free design and rollout plan covering identity aggregation, payloads, privacy, scaling, regional propagation, overload, and compatibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Give the diff minimap clearer contrast","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Turn the current merge-queue behavior into user documentation, then review whether the stated ordering and retry guarantees match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Outline a phased architecture for replacing Redis presence storage with an in-memory regional service, without implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.83,"slice":"boundary","lang":"en"} -{"prompt":"Implement revision-aware comment anchoring using context hashes and fallback matching.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"Create an operator guide for diagnosing delayed push notifications across providers and regions.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Move markdown sanitization out of `MessageController` while preserving rendered output and rejection behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Investigate why review approvals remain valid after the protected branch changes required checks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"Add generation-fenced notification-template publication with preview and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Set the review comment limit to 10000","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Create the responsive channel-details panel with members, pins, files, notification settings, and accessible tabs.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Corrige apenas `mentoin` para `mention` na nova mensagem.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"pt"} -{"prompt":"Review the shared-terminal protocol for input injection, terminal escape abuse, secret leakage, authorization, and session cleanup.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"Implement channel export jobs and write the API guide. Include date filters, threads, files, retention, asynchronous states, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Design a migration from one global notification topic to tenant-partitioned delivery, including ordering, fairness, replay, migration, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.87,"slice":"core","lang":"en"} -{"prompt":"Add incremental repository-symbol graph updates with delete tombstones and checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Build the desktop thread-search view with filters, result context, keyboard preview, and stable navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"continue the review issue","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.54,"slice":"vague-eval","lang":"en"} -{"prompt":"Extract notification-channel selection into one policy module while preserving every delivery decision.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why resolved comments reappear after an offline client reconnects, implement the verified version fix, and update synchronization docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed AI review-summary feature for prompt injection, private-code retention, attribution, omissions, and user trust. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","lang":"en"} -{"prompt":"Find why one websocket partition repeatedly rebalances when traffic is otherwise stable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Draft a migration guide for moving bot integrations from legacy webhooks to app-scoped event subscriptions.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Give the diff minimap clearer contrast","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Turn the current merge-queue behavior into user documentation, then review whether the stated ordering and retry guarantees match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Outline a phased architecture for replacing Redis presence storage with an in-memory regional service, without implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement revision-aware comment anchoring using context hashes and fallback matching.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create an operator guide for diagnosing delayed push notifications across providers and regions.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Move markdown sanitization out of `MessageController` while preserving rendered output and rejection behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why review approvals remain valid after the protected branch changes required checks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add generation-fenced notification-template publication with preview and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Set the review comment limit to 10000","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Create the responsive channel-details panel with members, pins, files, notification settings, and accessible tabs.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Corrige apenas `mentoin` para `mention` na nova mensagem.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"pt"} +{"prompt":"Review the shared-terminal protocol for input injection, terminal escape abuse, secret leakage, authorization, and session cleanup.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement channel export jobs and write the API guide. Include date filters, threads, files, retention, asynchronous states, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Design a migration from one global notification topic to tenant-partitioned delivery, including ordering, fairness, replay, migration, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add incremental repository-symbol graph updates with delete tombstones and checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Build the desktop thread-search view with filters, result context, keyboard preview, and stable navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Extract notification-channel selection into one policy module while preserving every delivery decision.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Investigate why resolved comments reappear after an offline client reconnects, implement the verified version fix, and update synchronization docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed AI review-summary feature for prompt injection, private-code retention, attribution, omissions, and user trust. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Find why one websocket partition repeatedly rebalances when traffic is otherwise stable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft a migration guide for moving bot integrations from legacy webhooks to app-scoped event subscriptions.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Slack excerpt from the outage:\n\n```text\nMira 14:02: messages send but channel lists aren't updating\nDev 14:04: gateway publish latency normal, unread counts flat\nMira 14:06: event consumer lag 0 on partitions 0-62, partition 63 shows no owner\nDev 14:08: coordinator says member worker-9 owns 63\nMira 14:09: worker-9 restarted at 13:58, generation file still says 441\nDev 14:12: broker group generation is 442; heartbeats accepted but fetch requests rejected ILLEGAL_GENERATION\nMira 14:16: process only rejoins after manual pod deletion\n```\n\nDetermine how the worker can heartbeat successfully with stale fetch generation and why its automatic recovery never rejoins the group.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Add unread text to the channel header","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.24,"slice":"core","lang":"en"} +{"prompt":"Add unread text to the channel header","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"Restructure the message fan-out pipeline and document its delivery interface. Preserve recipients and ordering while separating expansion, routing, transport, and receipts.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Architect a globally distributed collaboration event log with regional writes, ordering domains, replay, retention, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"boundary","lang":"en"} -{"prompt":"Implement cryptographic audit chaining for review-state transitions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new editor command, including registration, keybindings, telemetry, accessibility, and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"Consolidate diff-line identifier generation across server and clients without changing anchors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Investigate why notification badges lag after marking all messages read on another device.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional reviewer assignment with team expansion and idempotent notifications.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Pin ProseMirror to `1.25.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Build the mobile workspace switcher with search, recent workspaces, unread counts, and offline state.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Remplace `Notifcations` par `Notifications` uniquement dans le nouveau titre.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"fr"} -{"prompt":"Inspect the code-snippet preview service for SSRF, unsafe language modes, resource exhaustion, and private URL leakage.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"Implement review-activity exports and write the integration documentation. Include filters, retention, asynchronous generation, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Develop a roadmap for replacing repository webhooks with a durable integration event bus, including compatibility, replay, tenancy, and adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.87,"slice":"core","lang":"en"} -{"prompt":"Add bounded message-reaction aggregation with duplicate-event handling.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Create the responsive keyboard-shortcuts editor with conflict detection, recording mode, reset, search, and accessibility.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"fix mentions","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.46,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `ReviewEvt` with `ReviewEvent` across packages while preserving event type names and public aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why scheduled messages use an outdated channel name in notifications, implement the snapshot fix, and update user documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Why does code search index commit metadata separately from file content? Explain the existing update and permission model.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.48,"slice":"boundary","lang":"en"} -{"prompt":"Track down the occasional blank diff after switching rapidly between review revisions.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} +{"prompt":"Architect a globally distributed collaboration event log with regional writes, ordering domains, replay, retention, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement cryptographic audit chaining for review-state transitions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new editor command, including registration, keybindings, telemetry, accessibility, and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Consolidate diff-line identifier generation across server and clients without changing anchors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Investigate why notification badges lag after marking all messages read on another device.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add transactional reviewer assignment with team expansion and idempotent notifications.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Pin ProseMirror to `1.25.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile workspace switcher with search, recent workspaces, unread counts, and offline state.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remplace `Notifcations` par `Notifications` uniquement dans le nouveau titre.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"fr"} +{"prompt":"Inspect the code-snippet preview service for SSRF, unsafe language modes, resource exhaustion, and private URL leakage.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement review-activity exports and write the integration documentation. Include filters, retention, asynchronous generation, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Develop a roadmap for replacing repository webhooks with a durable integration event bus, including compatibility, replay, tenancy, and adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add bounded message-reaction aggregation with duplicate-event handling.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the responsive keyboard-shortcuts editor with conflict detection, recording mode, reset, search, and accessibility.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"fix mentions","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `ReviewEvt` with `ReviewEvent` across packages while preserving event type names and public aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose why scheduled messages use an outdated channel name in notifications, implement the snapshot fix, and update user documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does code search index commit metadata separately from file content? Explain the existing update and permission model.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down the occasional blank diff after switching rapidly between review revisions.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Write a troubleshooting guide for missing review notifications, covering preferences, quiet hours, membership, routing, and provider failures.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Design review notes:\n\n```text\nFeature: workspace message retention overrides\nDefault retention comes from organization policy\nWorkspace administrators may choose a shorter period, never longer\nLegal holds preserve selected channels and direct messages\nDeletion must remove search documents, attachments, previews, and derived embeddings\nExport jobs started before expiry may still contain affected messages\nMobile offline caches purge on next synchronization\nAudit records keep message IDs but not content\nPolicy changes can affect billions of messages\n```\n\nReview the proposal for policy precedence, legal holds, derived data, exports, offline clients, audit, scalability, and deletion evidence. No implementation requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a loading state to the thread panel","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Plan and implement workspace data-retention policies. First define precedence, holds, exports, derived content, deletion proof, old clients, and rollout; then add policy storage and enforcement workers.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.94,"slice":"mixed","lang":"en"} -{"prompt":"Outline an architecture for cross-workspace federation with identity, trust, message delivery, moderation, audit, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"boundary","lang":"en"} -{"prompt":"Implement revision-consistent review exports with immutable commit references.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Escribe una guía para integrar bots de revisión, con permisos, eventos, reintentos, comentarios y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} -{"prompt":"Move channel-name formatting out of the notification renderer without changing delivered text.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"core","lang":"en"} -{"prompt":"Investigate why the Android app restores a draft reply into the wrong thread.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.61,"slice":"boundary","lang":"en"} -{"prompt":"Add atomic repository-subscription updates with version conflicts and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Remove the obsolete `legacy_mentions` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"core","lang":"en"} -{"prompt":"Build the review file-tree with change badges, search, collapsed directories, keyboard navigation, and sticky selection.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"`Mesage sent` を `Message sent` に直して。新しい通知文だけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"ja"} -{"prompt":"Review the workspace export endpoint for membership races, deleted-content leakage, attachment URLs, and unbounded jobs.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Implement notification-delivery history and write its API guide. Include channels, attempts, provider responses, redaction, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Plan a disaster-recovery strategy for collaboration services, including event logs, search, files, keys, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"core","lang":"en"} -{"prompt":"Add content-hash deduplication to uploaded review attachments with tenant isolation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Create the desktop merge-conflict viewer with three panes, editable result, navigation, validation, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"continue the notification cleanup","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.44,"slice":"vague-eval","lang":"en"} -{"prompt":"Rename `ThreadSub` to `ThreadSubscription` across clients while preserving wire fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why applied suggestions still appear pending, implement the verified revision-event fix, and update review documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed message-embedding search for private-channel isolation, deletion, consent, retention, and inference risks.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"boundary","lang":"en"} -{"prompt":"Find why editor completion results arrive after cancellation and replace newer suggestions.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Draft a support guide for restoring accidentally archived channels without losing thread history.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} -{"prompt":"Offline sync failure report:\n\n```text\nclient=ios version=12.4 device=d_781\nlast_cursor=workspace:w_11:seq_889120\nlocal pending ops=3\nop1 edit message=m_31 base_version=4\nop2 resolve thread=t_8 base_version=9\nop3 delete draft=d_17\nserver compaction minimum_cursor=seq_891000\nsync response=cursor_expired full_resync_required\nclient starts full resync and clears local projection\npending-op journal path is inside projection directory\njournal deleted before replay\nUI reports sync complete but all three offline actions disappear\n```\n\nDetermine why full resync deletes the pending-operation journal and which ownership boundary or sequencing assumption is wrong.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Add participant count to the presence pill","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Restructure the offline synchronization engine and document its operation interface. Preserve behavior while separating journal, transport, merge, projection, and recovery.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.83,"slice":"mixed","lang":"en"} -{"prompt":"Architect a globally distributed code-search service with repository ownership, authorization, indexing, query routing, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed review-export manifests with commit digests and event counts.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new notification type, including recipients, templates, preferences, metrics, and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Consolidate workspace-role checks across chat and review services without changing authorization decisions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Investigate why repository mentions resolve to deleted teams in autocomplete.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.61,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional message redaction with search and attachment cleanup events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Set the maximum thread depth to 12","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Build the mobile notification-center screen with sections, swipe actions, filters, pagination, and accessible timestamps.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"把 `Thred resolved` 改成 `Thread resolved`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"zh"} -{"prompt":"Inspect the comment-rendering path for unsafe HTML, malicious links, Unicode spoofing, and resource exhaustion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Implement workspace-presence history and write its API documentation. Include aggregation, privacy settings, retention, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Design a device-twin architecture for smart-building sensors, controllers, and gateways. Cover desired versus reported state, intermittent connectivity, command expiry, schema evolution, tenant isolation, fleet-wide updates, audit history, regional failure, and migration from retained MQTT messages. Deliver an RFC only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Before implementing demand-response automation, outline the control design for eligibility, schedules, opt-outs, grid signals, device safety, offline behavior, settlement evidence, and staged rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"boundary","lang":"en"} -{"prompt":"Add retained-state support to the MQTT bridge","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Gateway logs from an apartment deployment:\n\n```text\ngateway=gw_882 firmware=4.12.1 device=therm_19\nreported temperature=21.4 sequence=8811\ncloud desired setpoint=19.0 command_id=cmd_77 expires=18:42:00Z\nmqtt publish qos=1 packet_id=441\nnetwork disconnected before PUBACK\nlocal controller applied setpoint=19.0\nnetwork restored at=18:44:12Z\nclient retransmit DUP=1 packet_id=441\ncloud command worker sees command expired and records rejected\nreported state arrives setpoint=19.0 source=local_apply\nUI shows command failed but device changed\n```\n\nDetermine how application before acknowledgement creates contradictory command status and whether gateway persistence or cloud reconciliation owns the inconsistency.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.81,"slice":"pasted-context","lang":"en"} -{"prompt":"Build the SwiftUI room-control screen with temperature, mode, schedule, device health, offline states, and VoiceOver-adjustable controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Plan and implement secure remote commands for industrial gateways. Begin with a design covering command identity, signing, authorization, expiry, replay prevention, offline queues, local safety checks, acknowledgements, audit, and rollout. Then add command APIs, signature verification, durable delivery, state transitions, and conformance tests. Treat the safety and trust design as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.98,"slice":"mixed","lang":"en"} -{"prompt":"Set `HEARTBEAT_INTERVAL` to 45s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Extract duplicated device-identifier parsing from provisioning and telemetry while preserving accepted forms and errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"core","lang":"en"} -{"prompt":"Implement `/internal/fleet/health` with connected, stale, offline, updating, and quarantined counts.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"make the thermostat app friendlier","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.42,"slice":"vague-eval","lang":"en"} -{"prompt":"Find why ESP32 devices occasionally reboot when processing a large shadow-state update.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Explain how `CommandReconciler` resolves a late acknowledgement after a newer desired-state command. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Customer rollout notes:\n\n```text\nFeature: household energy budget\nUsers choose a monthly kWh target\nDashboard compares measured usage against target and prior month\nForecast requires at least seven days of complete interval data\nMissing meter intervals are shown, not estimated\nNotifications can warn at 50%, 75%, 90%, and 100%\nBudget does not limit power or control devices\nTariff cost is not included in this release\nShared household members see the same target\nData can arrive up to 48 hours late from some utilities\n```\n\nTurn this into release notes and an in-app help article. Avoid implying real-time accuracy or automatic energy control.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.44,"slice":"pasted-context","lang":"en"} -{"prompt":"Move the connectivity badge below the device name","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.13,"slice":"boundary","lang":"en"} -{"prompt":"Write an operator guide for replaying dead-lettered telemetry without duplicating meter intervals.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Implement fleet command-history endpoints with filtering, pagination, and authorization, then document states, timestamps, retries, and examples.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Map out a migration from shared device certificates to per-device identities, including manufacturing, enrollment, rotation, revocation, offline fleets, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"core","lang":"en"} -{"prompt":"Rename `devId` to `deviceId` in `PairingState.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"en"} -{"prompt":"Teach the telemetry ingester to decode CBOR batches with per-sample timestamps and partial validation errors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Polish the appliance status tiles","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.29,"slice":"core","lang":"en"} -{"prompt":"Bump Zephyr to `4.2.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"Rename `MasterGateway` to `PrimaryGateway` across firmware, cloud services, metrics, and dashboards while preserving protocol values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Split `FleetManager` into enrollment, state, commands, updates, and health collaborators without changing APIs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Implementation ticket:\n\n```text\nIOT-5810 — gateway store-and-forward telemetry\nGateway buffers samples when cloud is unreachable\nCapacity: minimum 72 hours at configured sample rate\nStorage is a ring buffer on eMMC\nEvery record includes device ID, metric ID, device timestamp, sequence, value, quality\nUpload batches are acknowledged through highest contiguous sequence per device\nPower loss must not corrupt previously committed records\nLow disk should prefer dropping low-priority diagnostics before meter data\nExpose fill percentage, oldest age, corruption count, and dropped samples\nFirmware upgrades must preserve the buffer\n```\n\nImplement the on-device format, recovery, prioritization, upload protocol, acknowledgements, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"Investigate why Android BLE provisioning stalls after Wi-Fi credentials are accepted.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Create the device-update progress UI and add a short guide explaining download, install, reboot, validation, rollback, and offline states.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.65,"slice":"mixed","lang":"en"} -{"prompt":"Why does the meter pipeline store both device and utility timestamps? Explain existing reconciliation behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.48,"slice":"core","lang":"en"} -{"prompt":"Rewrite the local setup for running Mosquitto, the device simulator, TimescaleDB, and the fleet API.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.34,"slice":"core","lang":"en"} -{"prompt":"This firmware test fails only with link-time optimization:\n\n```text\nFAIL test_boot_counter_survives_brownout\nexpected boot_count=42 actual=0\nflash slot address=0x3F000\nwrite sequence: erase, program value=42, verify pass\nbrownout injected 8ms after reset vector\nstartup reads boot_count before scheduler init\nmap file without LTO symbol `boot_counter_page` section=.noinit\nmap file with LTO symbol folded into `.bss`\nstartup clears .bss before read\nlinker script KEEP(*(.noinit*)) exists\nvariable declaration lacks used attribute\n```\n\nDetermine whether LTO removes the custom section annotation, garbage-collects the symbol, or exposes an initialization-order mistake.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"boundary","lang":"en"} -{"prompt":"finish the gateway API","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} +{"prompt":"Design review notes:\n\n```text\nFeature: workspace message retention overrides\nDefault retention comes from organization policy\nWorkspace administrators may choose a shorter period, never longer\nLegal holds preserve selected channels and direct messages\nDeletion must remove search documents, attachments, previews, and derived embeddings\nExport jobs started before expiry may still contain affected messages\nMobile offline caches purge on next synchronization\nAudit records keep message IDs but not content\nPolicy changes can affect billions of messages\n```\n\nReview the proposal for policy precedence, legal holds, derived data, exports, offline clients, audit, scalability, and deletion evidence. No implementation requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add a loading state to the thread panel","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Plan and implement workspace data-retention policies. First define precedence, holds, exports, derived content, deletion proof, old clients, and rollout; then add policy storage and enforcement workers.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Outline an architecture for cross-workspace federation with identity, trust, message delivery, moderation, audit, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement revision-consistent review exports with immutable commit references.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Escribe una guía para integrar bots de revisión, con permisos, eventos, reintentos, comentarios y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"es"} +{"prompt":"Move channel-name formatting out of the notification renderer without changing delivered text.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Investigate why the Android app restores a draft reply into the wrong thread.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add atomic repository-subscription updates with version conflicts and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remove the obsolete `legacy_mentions` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Build the review file-tree with change badges, search, collapsed directories, keyboard navigation, and sticky selection.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"`Mesage sent` を `Message sent` に直して。新しい通知文だけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"ja"} +{"prompt":"Review the workspace export endpoint for membership races, deleted-content leakage, attachment URLs, and unbounded jobs.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement notification-delivery history and write its API guide. Include channels, attempts, provider responses, redaction, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan a disaster-recovery strategy for collaboration services, including event logs, search, files, keys, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add content-hash deduplication to uploaded review attachments with tenant isolation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the desktop merge-conflict viewer with three panes, editable result, navigation, validation, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Rename `ThreadSub` to `ThreadSubscription` across clients while preserving wire fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why applied suggestions still appear pending, implement the verified revision-event fix, and update review documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed message-embedding search for private-channel isolation, deletion, consent, retention, and inference risks.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why editor completion results arrive after cancellation and replace newer suggestions.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Draft a support guide for restoring accidentally archived channels without losing thread history.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Offline sync failure report:\n\n```text\nclient=ios version=12.4 device=d_781\nlast_cursor=workspace:w_11:seq_889120\nlocal pending ops=3\nop1 edit message=m_31 base_version=4\nop2 resolve thread=t_8 base_version=9\nop3 delete draft=d_17\nserver compaction minimum_cursor=seq_891000\nsync response=cursor_expired full_resync_required\nclient starts full resync and clears local projection\npending-op journal path is inside projection directory\njournal deleted before replay\nUI reports sync complete but all three offline actions disappear\n```\n\nDetermine why full resync deletes the pending-operation journal and which ownership boundary or sequencing assumption is wrong.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Add participant count to the presence pill","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Restructure the offline synchronization engine and document its operation interface. Preserve behavior while separating journal, transport, merge, projection, and recovery.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Architect a globally distributed code-search service with repository ownership, authorization, indexing, query routing, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement signed review-export manifests with commit digests and event counts.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new notification type, including recipients, templates, preferences, metrics, and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Consolidate workspace-role checks across chat and review services without changing authorization decisions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why repository mentions resolve to deleted teams in autocomplete.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add transactional message redaction with search and attachment cleanup events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Set the maximum thread depth to 12","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile notification-center screen with sections, swipe actions, filters, pagination, and accessible timestamps.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"把 `Thred resolved` 改成 `Thread resolved`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"zh"} +{"prompt":"Inspect the comment-rendering path for unsafe HTML, malicious links, Unicode spoofing, and resource exhaustion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Implement workspace-presence history and write its API documentation. Include aggregation, privacy settings, retention, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Design a device-twin architecture for smart-building sensors, controllers, and gateways. Cover desired versus reported state, intermittent connectivity, command expiry, schema evolution, tenant isolation, fleet-wide updates, audit history, regional failure, and migration from retained MQTT messages. Deliver an RFC only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Before implementing demand-response automation, outline the control design for eligibility, schedules, opt-outs, grid signals, device safety, offline behavior, settlement evidence, and staged rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add retained-state support to the MQTT bridge","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Gateway logs from an apartment deployment:\n\n```text\ngateway=gw_882 firmware=4.12.1 device=therm_19\nreported temperature=21.4 sequence=8811\ncloud desired setpoint=19.0 command_id=cmd_77 expires=18:42:00Z\nmqtt publish qos=1 packet_id=441\nnetwork disconnected before PUBACK\nlocal controller applied setpoint=19.0\nnetwork restored at=18:44:12Z\nclient retransmit DUP=1 packet_id=441\ncloud command worker sees command expired and records rejected\nreported state arrives setpoint=19.0 source=local_apply\nUI shows command failed but device changed\n```\n\nDetermine how application before acknowledgement creates contradictory command status and whether gateway persistence or cloud reconciliation owns the inconsistency.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Build the SwiftUI room-control screen with temperature, mode, schedule, device health, offline states, and VoiceOver-adjustable controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Plan and implement secure remote commands for industrial gateways. Begin with a design covering command identity, signing, authorization, expiry, replay prevention, offline queues, local safety checks, acknowledgements, audit, and rollout. Then add command APIs, signature verification, durable delivery, state transitions, and conformance tests. Treat the safety and trust design as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":1.0,"slice":"mixed","lang":"en"} +{"prompt":"Set `HEARTBEAT_INTERVAL` to 45s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Extract duplicated device-identifier parsing from provisioning and telemetry while preserving accepted forms and errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Implement `/internal/fleet/health` with connected, stale, offline, updating, and quarantined counts.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"make the thermostat app friendlier","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Find why ESP32 devices occasionally reboot when processing a large shadow-state update.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Explain how `CommandReconciler` resolves a late acknowledgement after a newer desired-state command. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Customer rollout notes:\n\n```text\nFeature: household energy budget\nUsers choose a monthly kWh target\nDashboard compares measured usage against target and prior month\nForecast requires at least seven days of complete interval data\nMissing meter intervals are shown, not estimated\nNotifications can warn at 50%, 75%, 90%, and 100%\nBudget does not limit power or control devices\nTariff cost is not included in this release\nShared household members see the same target\nData can arrive up to 48 hours late from some utilities\n```\n\nTurn this into release notes and an in-app help article. Avoid implying real-time accuracy or automatic energy control.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} +{"prompt":"Move the connectivity badge below the device name","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Write an operator guide for replaying dead-lettered telemetry without duplicating meter intervals.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Implement fleet command-history endpoints with filtering, pagination, and authorization, then document states, timestamps, retries, and examples.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Map out a migration from shared device certificates to per-device identities, including manufacturing, enrollment, rotation, revocation, offline fleets, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Rename `devId` to `deviceId` in `PairingState.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Teach the telemetry ingester to decode CBOR batches with per-sample timestamps and partial validation errors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Polish the appliance status tiles","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump Zephyr to `4.2.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename `MasterGateway` to `PrimaryGateway` across firmware, cloud services, metrics, and dashboards while preserving protocol values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Split `FleetManager` into enrollment, state, commands, updates, and health collaborators without changing APIs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implementation ticket:\n\n```text\nIOT-5810 — gateway store-and-forward telemetry\nGateway buffers samples when cloud is unreachable\nCapacity: minimum 72 hours at configured sample rate\nStorage is a ring buffer on eMMC\nEvery record includes device ID, metric ID, device timestamp, sequence, value, quality\nUpload batches are acknowledged through highest contiguous sequence per device\nPower loss must not corrupt previously committed records\nLow disk should prefer dropping low-priority diagnostics before meter data\nExpose fill percentage, oldest age, corruption count, and dropped samples\nFirmware upgrades must preserve the buffer\n```\n\nImplement the on-device format, recovery, prioritization, upload protocol, acknowledgements, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Investigate why Android BLE provisioning stalls after Wi-Fi credentials are accepted.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the device-update progress UI and add a short guide explaining download, install, reboot, validation, rollback, and offline states.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Why does the meter pipeline store both device and utility timestamps? Explain existing reconciliation behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Rewrite the local setup for running Mosquitto, the device simulator, TimescaleDB, and the fleet API.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"This firmware test fails only with link-time optimization:\n\n```text\nFAIL test_boot_counter_survives_brownout\nexpected boot_count=42 actual=0\nflash slot address=0x3F000\nwrite sequence: erase, program value=42, verify pass\nbrownout injected 8ms after reset vector\nstartup reads boot_count before scheduler init\nmap file without LTO symbol `boot_counter_page` section=.noinit\nmap file with LTO symbol folded into `.bss`\nstartup clears .bss before read\nlinker script KEEP(*(.noinit*)) exists\nvariable declaration lacks used attribute\n```\n\nDetermine whether LTO removes the custom section annotation, garbage-collects the symbol, or exposes an initialization-order mistake.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"finish the gateway API","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"Propose an architecture for utility interval-data ingestion, including source corrections, late files, deduplication, time zones, gaps, audit, and customer-visible freshness.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Add Modbus register-map validation to `gatewayctl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Patch excerpt:\n\n```diff\n void handle_command(Command *cmd) {\n- if (!verify_signature(cmd)) return;\n- if (cmd->expires_at < rtc_now()) return;\n- apply_command(cmd);\n+ apply_command(cmd);\n+ enqueue_audit(cmd);\n }\n```\n\nThe author says the cloud already validates commands. Review trust boundaries, replay, expiry, compromised gateways, offline queues, audit ordering, and local safety. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"pasted-context","lang":"en"} -{"prompt":"Schreibe eine kurze Referenz für die bestehenden Geräte-Statuswerte und ihre Auswirkungen auf Befehle und Updates. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"boundary","lang":"de"} -{"prompt":"Build the responsive fleet map with clustering, offline indicators, filters, stale-data warnings, and a non-map accessible view.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Review the current firmware rollout state machine, explain its gates, then turn the findings into an operator runbook with examples.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.63,"slice":"mixed","lang":"en"} -{"prompt":"Set the offline threshold to 10 minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Benenne `TwinCtx` repositoryweit in `DeviceTwinContext` um; JSON-Felder und Protokollverhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"de"} -{"prompt":"Consolidate battery-state normalization across Zigbee and BLE adapters without changing reported percentages.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Diagnose the duplicate outage notification","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"Explain how the edge scheduler prioritizes safety commands over configuration updates.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.56,"slice":"core","lang":"en"} -{"prompt":"Create API documentation for the existing device-shadow endpoints, including versions, conflicts, desired state, and reported state.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"boundary","lang":"en"} -{"prompt":"Plan a migration from one global MQTT broker cluster to regional tenant-assigned clusters, including routing, sessions, retained state, failover, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Mobile design ticket:\n\n```text\nScreen: home energy dashboard\nSummary: current power, today's energy, monthly target progress\nChart: 24-hour interval usage with gaps shown explicitly\nDevice contributions listed when submeter data exists\nLive power may be delayed by up to 30 seconds\nUtility intervals may arrive 24-48 hours late\nStates: no meter linked, partial device coverage, offline gateway, delayed utility data, loading\nAccessibility: chart has tabular values and does not encode import/export only by color\nActions: change budget, view devices, download data\n```\n\nImplement the iOS dashboard and tests using the existing energy model. Do not estimate missing measurements.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"pasted-context","lang":"en"} -{"prompt":"Implement `POST /v1/devices/{id}/quarantine` with reason, expiry, command blocking, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"boundary","lang":"en"} -{"prompt":"Remove the extra degree symbol","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"core","lang":"en"} -{"prompt":"Fix the clipped signal bars and extract their repeated inset into the shared device-card styles.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.36,"slice":"mixed","lang":"en"} -{"prompt":"Replace scattered update-status booleans with one explicit firmware state enum while preserving transitions and telemetry.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Cambia `gwIdx` por `gatewayIndex` solo en `FleetReducer.swift`; no modifiques la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"es"} -{"prompt":"Investigate why the smart-lock app briefly shows the previous home's devices after switching accounts.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"Summarize the current device-certificate rotation workflow for security reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Develop a capacity roadmap for ingesting ten billion sensor samples per day. Include partitioning, compression, retention, queries, backpressure, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} +{"prompt":"Add Modbus register-map validation to `gatewayctl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Patch excerpt:\n\n```diff\n void handle_command(Command *cmd) {\n- if (!verify_signature(cmd)) return;\n- if (cmd->expires_at < rtc_now()) return;\n- apply_command(cmd);\n+ apply_command(cmd);\n+ enqueue_audit(cmd);\n }\n```\n\nThe author says the cloud already validates commands. Review trust boundaries, replay, expiry, compromised gateways, offline queues, audit ordering, and local safety. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Schreibe eine kurze Referenz für die bestehenden Geräte-Statuswerte und ihre Auswirkungen auf Befehle und Updates. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"de"} +{"prompt":"Build the responsive fleet map with clustering, offline indicators, filters, stale-data warnings, and a non-map accessible view.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Review the current firmware rollout state machine, explain its gates, then turn the findings into an operator runbook with examples.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Set the offline threshold to 10 minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Benenne `TwinCtx` repositoryweit in `DeviceTwinContext` um; JSON-Felder und Protokollverhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"de"} +{"prompt":"Consolidate battery-state normalization across Zigbee and BLE adapters without changing reported percentages.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose the duplicate outage notification","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Explain how the edge scheduler prioritizes safety commands over configuration updates.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Create API documentation for the existing device-shadow endpoints, including versions, conflicts, desired state, and reported state.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Plan a migration from one global MQTT broker cluster to regional tenant-assigned clusters, including routing, sessions, retained state, failover, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Mobile design ticket:\n\n```text\nScreen: home energy dashboard\nSummary: current power, today's energy, monthly target progress\nChart: 24-hour interval usage with gaps shown explicitly\nDevice contributions listed when submeter data exists\nLive power may be delayed by up to 30 seconds\nUtility intervals may arrive 24-48 hours late\nStates: no meter linked, partial device coverage, offline gateway, delayed utility data, loading\nAccessibility: chart has tabular values and does not encode import/export only by color\nActions: change budget, view devices, download data\n```\n\nImplement the iOS dashboard and tests using the existing energy model. Do not estimate missing measurements.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Implement `POST /v1/devices/{id}/quarantine` with reason, expiry, command blocking, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remove the extra degree symbol","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fix the clipped signal bars and extract their repeated inset into the shared device-card styles.","purpose":"frontendImpl","secondary":"refactor","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Replace scattered update-status booleans with one explicit firmware state enum while preserving transitions and telemetry.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Cambia `gwIdx` por `gatewayIndex` solo en `FleetReducer.swift`; no modifiques la lógica.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"es"} +{"prompt":"Investigate why the smart-lock app briefly shows the previous home's devices after switching accounts.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Summarize the current device-certificate rotation workflow for security reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Develop a capacity roadmap for ingesting ten billion sensor samples per day. Include partitioning, compression, retention, queries, backpressure, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Implement idempotent utility-bill ingestion with correction versions and source provenance.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Create the Compose automation editor with triggers, conditions, actions, validation, reorder, and TalkBack support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Fix `telemetery` in `metrics.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} -{"prompt":"Merge duplicate command-envelope types used by cloud and simulator while preserving encoded bytes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Grid-control incident logs:\n\n```text\nprogram=dr_2026_07_29 event_start=17:00Z event_end=18:00Z\neligible_devices=28,441 commands_sent=28,441\nacknowledged=27,901 rejected=114 unknown=426\nreconciliation at=18:05Z marked unknown as not_participating\nlate acks received at=18:07Z count=392 status=applied\nsettlement export generated at=18:06Z using not_participating state\ncustomer credits missing for 392 devices\nstate transition unknown -> applied rejected reason='event finalized'\n```\n\nDetermine why settlement finalization precedes the acknowledgement grace window and why late evidence cannot correct finalized participation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Rename `temprature_c` to `temperature_c` in the unreleased schema.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"en"} -{"prompt":"Assess whether household sharing can expose historical sensor data after a member is removed. Review cache and authorization behavior only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Restructure the gateway SDK into transport, state, commands, updates, and diagnostics, then write a maintainer note. Preserve public APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Plan the retirement of the legacy Zigbee coordinator protocol, covering device inventory, bridge firmware, dual operation, migration, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.87,"slice":"core","lang":"en"} -{"prompt":"Add immutable provenance chains to transformed meter intervals.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} +{"prompt":"Create the Compose automation editor with triggers, conditions, actions, validation, reorder, and TalkBack support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Fix `telemetery` in `metrics.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Merge duplicate command-envelope types used by cloud and simulator while preserving encoded bytes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Grid-control incident logs:\n\n```text\nprogram=dr_2026_07_29 event_start=17:00Z event_end=18:00Z\neligible_devices=28,441 commands_sent=28,441\nacknowledged=27,901 rejected=114 unknown=426\nreconciliation at=18:05Z marked unknown as not_participating\nlate acks received at=18:07Z count=392 status=applied\nsettlement export generated at=18:06Z using not_participating state\ncustomer credits missing for 392 devices\nstate transition unknown -> applied rejected reason='event finalized'\n```\n\nDetermine why settlement finalization precedes the acknowledgement grace window and why late evidence cannot correct finalized participation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Rename `temprature_c` to `temperature_c` in the unreleased schema.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Assess whether household sharing can expose historical sensor data after a member is removed. Review cache and authorization behavior only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Restructure the gateway SDK into transport, state, commands, updates, and diagnostics, then write a maintainer note. Preserve public APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan the retirement of the legacy Zigbee coordinator protocol, covering device inventory, bridge firmware, dual operation, migration, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add immutable provenance chains to transformed meter intervals.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Build the tablet floor-plan controller with room zones, device states, drag placement, zoom, and accessible list fallback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"do the device screen","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `DevRef` with `DeviceReference` across packages while preserving serialized fields and public aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why exported energy reports omit corrected intervals, implement the verified snapshot fix, and add a user-facing note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"Why does the fleet service retain old desired-state generations after devices acknowledge them? Explain recovery behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.48,"slice":"boundary","lang":"en"} -{"prompt":"Track down the heap fragmentation in the gateway after repeated protobuf configuration updates.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Write release notes for household device sharing, including roles, invitations, history access, and removal.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.36,"slice":"core","lang":"en"} -{"prompt":"Firmware rollout notes:\n\n```text\nCurrent cohorts: internal, 1%, 10%, 50%, 100%\nHealth signals: boot success, crash rate, connectivity, command latency, battery impact\nDevices may be offline for weeks and return after rollout completes\nUpdate package supports one previous firmware delta plus full image\nBootloader keeps one rollback slot\nA schema migration can make old firmware unable to read local state\nCritical security updates may bypass normal dwell times\nCustomers can configure maintenance windows\n```\n\nProduce an implementation-free rollout and compatibility design covering late devices, rollback, schema gates, maintenance windows, health thresholds, and emergency releases.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"Give the room list clearer status grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.32,"slice":"core","lang":"en"} -{"prompt":"Turn the current automation execution behavior into user documentation, then review whether timing, retries, and offline claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Outline a phased architecture for moving time-series storage from InfluxDB to ClickHouse, without implementing ingestion or queries.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"boundary","lang":"en"} -{"prompt":"Implement version-aware device-shadow history with compacted snapshots and replay.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Create an operator guide for diagnosing devices stuck in firmware validation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} -{"prompt":"Move telemetry quality classification out of `IngestController` while preserving stored flags.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Investigate why revoked device credentials continue connecting through one regional broker.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"Add generation-fenced ruleset publication to the home automation engine.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Set the BLE scan timeout to 20s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Create the responsive device-history view with telemetry charts, commands, updates, filters, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Corrige apenas `gateawy` para `gateway` no novo alerta.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"pt"} -{"prompt":"Review the device-log upload endpoint for tenant spoofing, secret leakage, decompression bombs, and unbounded retention.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Implement firmware-rollout history and write its API guide. Include cohorts, gates, pauses, rollback, pagination, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Design a migration from raw telemetry topics to a schema-governed event platform, including compatibility, validation, replay, quarantine, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"core","lang":"en"} -{"prompt":"Add content-hash deduplication to firmware artifacts with signature preservation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Build the desktop rule simulator with sample sensor inputs, execution trace, timing, and copyable diagnostics.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"continue the firmware fix","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"Extract metric-name normalization into one shared module while preserving emitted series.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why daylight-saving transitions run a heating schedule twice, implement the verified recurrence fix, and update help documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.78,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed local voice-control bridge for transcript privacy, authentication, replay, offline commands, and shared-home access.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"Find why one telemetry partition stops after receiving a NaN sensor value.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Draft a migration guide for partners moving from CSV meter files to the interval-data API.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} -{"prompt":"Data-quality incident excerpt:\n\n```text\npipeline=utility-intervals provider=u_17 date=2026-07-28\nexpected intervals per meter=96 at 15m cadence\nmeters processed=481,220\nmeters with 92 intervals=38,119\nprovider timezone=Europe/Berlin\nsource timestamps include explicit offsets\nnormalizer converts to local time, drops offset, then groups by date\ndate crosses daylight-saving transition\nquality rule expects fixed 96 intervals for every local date\nmissing intervals imputed as zero before billing estimate\n```\n\nDetermine why valid DST days appear incomplete and why the pipeline's zero imputation turns a validation mistake into incorrect estimates.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Add last-seen text to the device card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.24,"slice":"core","lang":"en"} -{"prompt":"Restructure the telemetry pipeline and document its transform interface. Preserve output while separating decode, normalize, validate, enrich, and store.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Architect a nationwide smart-meter ingestion platform with utility ownership, corrections, regional availability, settlement evidence, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed command receipts with device sequence, firmware version, and result digest.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new device protocol adapter, including discovery, mapping, fixtures, security, and monitoring.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Consolidate device display-name formatting across app and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Investigate why an automation still targets a device after it moves to another home.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional device ownership transfer with credential rotation and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Pin Mosquitto to `2.0.22`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Build the mobile outage-status screen with affected devices, restoration estimates, updates, and accessible timeline.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Remplace `Conected` par `Connected` uniquement dans le nouveau badge.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"fr"} -{"prompt":"Inspect the local gateway API for unauthenticated LAN access, CSRF, DNS rebinding, unsafe commands, and secret exposure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Implement utility-data export jobs and write the integration documentation. Include ranges, corrections, asynchronous states, retention, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} +{"prompt":"Replace `DevRef` with `DeviceReference` across packages while preserving serialized fields and public aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose why exported energy reports omit corrected intervals, implement the verified snapshot fix, and add a user-facing note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the fleet service retain old desired-state generations after devices acknowledge them? Explain recovery behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Track down the heap fragmentation in the gateway after repeated protobuf configuration updates.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Write release notes for household device sharing, including roles, invitations, history access, and removal.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Firmware rollout notes:\n\n```text\nCurrent cohorts: internal, 1%, 10%, 50%, 100%\nHealth signals: boot success, crash rate, connectivity, command latency, battery impact\nDevices may be offline for weeks and return after rollout completes\nUpdate package supports one previous firmware delta plus full image\nBootloader keeps one rollback slot\nA schema migration can make old firmware unable to read local state\nCritical security updates may bypass normal dwell times\nCustomers can configure maintenance windows\n```\n\nProduce an implementation-free rollout and compatibility design covering late devices, rollback, schema gates, maintenance windows, health thresholds, and emergency releases.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Give the room list clearer status grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Turn the current automation execution behavior into user documentation, then review whether timing, retries, and offline claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Outline a phased architecture for moving time-series storage from InfluxDB to ClickHouse, without implementing ingestion or queries.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement version-aware device-shadow history with compacted snapshots and replay.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create an operator guide for diagnosing devices stuck in firmware validation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Move telemetry quality classification out of `IngestController` while preserving stored flags.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why revoked device credentials continue connecting through one regional broker.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add generation-fenced ruleset publication to the home automation engine.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Set the BLE scan timeout to 20s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Create the responsive device-history view with telemetry charts, commands, updates, filters, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Corrige apenas `gateawy` para `gateway` no novo alerta.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"pt"} +{"prompt":"Review the device-log upload endpoint for tenant spoofing, secret leakage, decompression bombs, and unbounded retention.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement firmware-rollout history and write its API guide. Include cohorts, gates, pauses, rollback, pagination, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Design a migration from raw telemetry topics to a schema-governed event platform, including compatibility, validation, replay, quarantine, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add content-hash deduplication to firmware artifacts with signature preservation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Build the desktop rule simulator with sample sensor inputs, execution trace, timing, and copyable diagnostics.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Extract metric-name normalization into one shared module while preserving emitted series.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why daylight-saving transitions run a heating schedule twice, implement the verified recurrence fix, and update help documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed local voice-control bridge for transcript privacy, authentication, replay, offline commands, and shared-home access.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why one telemetry partition stops after receiving a NaN sensor value.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft a migration guide for partners moving from CSV meter files to the interval-data API.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Data-quality incident excerpt:\n\n```text\npipeline=utility-intervals provider=u_17 date=2026-07-28\nexpected intervals per meter=96 at 15m cadence\nmeters processed=481,220\nmeters with 92 intervals=38,119\nprovider timezone=Europe/Berlin\nsource timestamps include explicit offsets\nnormalizer converts to local time, drops offset, then groups by date\ndate crosses daylight-saving transition\nquality rule expects fixed 96 intervals for every local date\nmissing intervals imputed as zero before billing estimate\n```\n\nDetermine why valid DST days appear incomplete and why the pipeline's zero imputation turns a validation mistake into incorrect estimates.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Add last-seen text to the device card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Restructure the telemetry pipeline and document its transform interface. Preserve output while separating decode, normalize, validate, enrich, and store.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Architect a nationwide smart-meter ingestion platform with utility ownership, corrections, regional availability, settlement evidence, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement signed command receipts with device sequence, firmware version, and result digest.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new device protocol adapter, including discovery, mapping, fixtures, security, and monitoring.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Consolidate device display-name formatting across app and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why an automation still targets a device after it moves to another home.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add transactional device ownership transfer with credential rotation and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Pin Mosquitto to `2.0.22`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile outage-status screen with affected devices, restoration estimates, updates, and accessible timeline.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Remplace `Conected` par `Connected` uniquement dans le nouveau badge.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"fr"} +{"prompt":"Inspect the local gateway API for unauthenticated LAN access, CSRF, DNS rebinding, unsafe commands, and secret exposure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement utility-data export jobs and write the integration documentation. Include ranges, corrections, asynchronous states, retention, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Develop a roadmap for replacing proprietary gateway firmware with an open plugin runtime, including isolation, compatibility, signing, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Add bounded command replay for devices reconnecting after extended outages.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Create the responsive tariff-comparison view with rate periods, estimated impact, caveats, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"fix pairing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `FwUpdate` with `FirmwareUpdate` across packages while preserving protocol field names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why battery alerts fire repeatedly after acknowledgement, implement the verified state fix, and update notification documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Why does the gateway keep two previous configuration generations? Explain current rollback and corruption recovery.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.47,"slice":"boundary","lang":"en"} -{"prompt":"Track down occasional timestamp jumps in telemetry after gateway reboot.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Write a troubleshooting guide for missing device telemetry, covering connectivity, buffering, schemas, quarantine, and clocks.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Security design packet:\n\n```text\nFeature: temporary installer access\nHome owner generates a six-digit code valid for 30 minutes\nInstaller enters code on local gateway setup page\nAccess permits adding devices and running diagnostics, not viewing history\nGateway may be offline from cloud during installation\nCode can be used from any device on the local network\nOwner receives notification after cloud reconnect\nAccess session ends after 15 minutes idle or explicit revoke\nCurrent proposal stores hashed code in gateway config flash\n```\n\nReview code entropy, brute force, offline verification, local-network threats, scope, storage, expiry, revocation, and delayed notification. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a loading state to the room controls","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Plan and implement tenant-defined telemetry retention. First define precedence, legal holds, aggregates, exports, deletion proof, offline buffers, and rollout; then add policy storage and enforcement.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.93,"slice":"mixed","lang":"en"} -{"prompt":"Outline an architecture for peer-to-peer device control during cloud outages, including trust, discovery, consistency, safety, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"boundary","lang":"en"} -{"prompt":"Implement snapshot-consistent device-state exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Escribe una guía para integrar nuevos medidores, con identidad, intervalos, correcciones, validación y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} -{"prompt":"Move command-expiry calculation out of the delivery worker without changing behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Investigate why the iOS app loses room assignments after restoring a backup.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"Add atomic device-profile publication with validation, preview, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Remove the obsolete `shadow_v1` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"core","lang":"en"} -{"prompt":"Build the firmware-release detail page with compatibility, rollout progress, health metrics, pause, and rollback controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"`Deivce offline` を `Device offline` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"ja"} -{"prompt":"Review the remote-diagnostics endpoint for command injection, sensitive logs, stale authorization, resource abuse, and audit gaps.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"Implement device-ownership history and write its API guide. Include transfers, invitations, effective dates, pagination, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Plan a disaster-recovery strategy for the device cloud, including brokers, state, commands, firmware, keys, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"core","lang":"en"} -{"prompt":"Add content-hash deduplication to uploaded gateway diagnostic bundles.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Create the desktop fleet-group editor with rules, membership preview, exclusions, scheduling, and validation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"continue the device cleanup","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"Rename `MeterIntvl` to `MeterInterval` across packages while preserving serialized field names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why device transfers leave old owners subscribed to alerts, implement the verified fan-out fix, and update help documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.78,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed energy forecasting cache for household isolation, stale corrections, missing intervals, consent, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Find why a gateway retransmits the same buffered batch forever after one invalid sample.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Draft a support guide for recovering a gateway after interrupted firmware installation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Telemetry storage failure:\n\n```text\nshard=ts_18 tenant=t_71 series=device_power\ncompaction input blocks=[881,882,883]\nblock 882 min_time=10:00 max_time=11:00 checksum=ok\nlate sample batch writes block 884 min_time=10:42 max_time=10:47\ncompactor snapshot excludes block 884\nmanifest generation=992 replaces blocks 881..883 with block 991\nlate block 884 cleanup classified as fully covered by block 991 time range\nblock 884 deleted\nquery loses 2,441 late samples\n```\n\nDetermine why time-range coverage is mistaken for sample coverage and how compaction snapshot boundaries allowed the late block to be deleted.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Add signal quality text below the chart","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.24,"slice":"core","lang":"en"} -{"prompt":"Restructure the firmware package builder and document its component interface. Preserve package bytes while separating assembly, signing, delta generation, and validation.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"Architect a multi-region device-command platform with ownership, ordering, failover, offline queues, audit, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed telemetry batch receipts with sequence ranges and content digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new firmware board, including bootloader, partitions, keys, flashing, and hardware tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"Consolidate utility-timezone resolution across ingestion and exports without changing interval dates.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Investigate why a removed automation still runs once after deletion.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional gateway replacement with device reassignment and credential revocation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Set the retained-message limit to 2048","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Build the mobile sensor-detail screen with current value, trends, battery, calibration, alerts, and accessible charts.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"把 `Firmare update` 改成 `Firmware update`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"zh"} -{"prompt":"Inspect the device-provisioning QR parser for malformed payloads, tenant confusion, replay, oversized fields, and unsafe URLs.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Implement command-delivery history and write its API documentation. Include attempts, acknowledgements, expiry, redaction, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Design a global media-processing platform for uploads, transcoding, packaging, thumbnails, captions, moderation, and delivery. Cover job idempotency, asset lineage, storage tiers, regional execution, failure recovery, quotas, migration from per-product pipelines, and rollout milestones. Deliver an architecture proposal only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"core","lang":"en"} -{"prompt":"Before implementing low-latency live streaming, outline ingest, transcoding, segmenting, playback, regional failover, chat synchronization, moderation delay, observability, and phased rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"boundary","lang":"en"} -{"prompt":"Add AV1 output to the transcode worker","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Playback incident logs:\n\n```text\nasset=vid_881 manifest_version=42 player=web-9.14\nmaster playlist variants=[1080p,720p,480p]\nselected=1080p bandwidth_estimate=8.2Mbps\nsegment 441 CDN status=200 bytes=1848812 duration=4.0\nsegment 442 CDN status=206 bytes=524288 content-range=0-524287/1931120\nplayer retry range=524288- status=200 content-length=1931120\nbuffer append error='SourceBuffer append window overlap'\nABR downswitch requested=720p\nplayhead stalls at=1768.0s buffer_ahead=0\n```\n\nDetermine whether the CDN mishandles the second range request, the player appends duplicate bytes, or the variant switch exposes the corrupted segment state.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.83,"slice":"pasted-context","lang":"en"} -{"prompt":"Build the SwiftUI episode-player controls with chapters, speed, captions, audio tracks, casting, and VoiceOver-safe time controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Plan and implement a content-rights enforcement service. Begin with a design covering territories, time windows, subscription tiers, device restrictions, downloads, live events, policy versioning, cache invalidation, audit, and failure behavior. Then add the evaluator, policy APIs, signed decisions, metrics, and conformance tests. Treat policy semantics and rollout as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.97,"slice":"mixed","lang":"en"} -{"prompt":"Set `MAX_UPLOAD_GB` to 80","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Extract duplicated timecode parsing from captions and chapter imports while preserving accepted formats and errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Implement `/internal/transcode/capabilities` with codecs, profiles, hardware, limits, and worker generation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} -{"prompt":"make the player cinematic","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.41,"slice":"vague-eval","lang":"en"} -{"prompt":"Find why downloaded podcasts occasionally restart from zero after the app relaunches.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Explain how `SegmentTimeline` handles discontinuities, encoder restarts, and ad insertions. Do not change code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Creator launch notes:\n\n```text\nFeature: replace uploaded video before publication\nCreator may replace source media while title, description, comments setting, and scheduled publish time remain\nExisting preview links temporarily show processing state\nOld source is retained for seven days for recovery\nCaptions and chapters are revalidated against new duration\nCustom thumbnails remain unless dimensions become invalid\nReplacement is unavailable after first publication\nAnalytics from preview playback remain attached to the draft\nProcessing failure leaves the previous source active\n```\n\nTurn this into creator-facing release notes and a help article. Clarify recovery, processing failure, metadata retention, and the publication restriction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.44,"slice":"pasted-context","lang":"en"} -{"prompt":"Move the caption button away from the scrubber thumb","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.14,"slice":"boundary","lang":"en"} -{"prompt":"Write an operator guide for replaying failed transcode jobs without publishing duplicate renditions.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"Implement asset-rendition endpoints with codec filtering, signed URLs, and authorization, then document freshness, expiry, examples, and errors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Map out a migration from HLS-only packaging to CMAF shared segments for HLS and DASH, including compatibility, storage, validation, rollout, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Rename `segIdx` to `segmentIndex` in `PlayerState.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"en"} -{"prompt":"Teach the upload service to resume multipart transfers using content-range validation and per-part checksums.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Polish the playlist header","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.28,"slice":"core","lang":"en"} -{"prompt":"Bump FFmpeg to `8.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"Rename `MasterManifest` to `PrimaryManifest` across packager, player, tests, and metrics while preserving manifest output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Split `MediaPipeline` into probing, transcoding, packaging, validation, and publication phases without changing assets.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"en"} -{"prompt":"Implementation ticket:\n\n```text\nMEDIA-720 — automatic caption ingest\nSources: uploaded WebVTT, SRT, TTML, and provider-generated captions\nRequirements:\n- normalize to internal cue model\n- preserve language, kind, and source provenance\n- reject overlapping cues only for formats that disallow them\n- clamp cues extending at most 250ms beyond duration; reject larger overflow\n- duplicate upload is idempotent by content hash\n- publication requires language uniqueness per caption kind\n- malformed files return line and column when possible\n- expose parsed, rejected, clamped, and duplicate counters\n```\n\nImplement parsers, normalization, validation, storage, idempotency, publication checks, metrics, and fixtures.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Investigate why the Android player loses audio after switching from Bluetooth to the phone speaker.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Create the caption editor UI and add a concise guide for timings, overlaps, speaker labels, shortcuts, and validation.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Why does the transcoder preserve source color metadata even when the target profile fixes primaries? Explain current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Rewrite the local setup for running MinIO, MediaMTX, the transcode workers, and sample streams.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"This packaging test started failing after updating Bento4:\n\n```text\nFAIL TestKeyRotationAlignsWithSegments\nperiod=0 key_id=k1 segments=1..5\nperiod=1 key_id=k2 segments=6..10\nexpected rotation_time=20.000 actual=19.968\ninput frame rate=30000/1001 keyframe interval=60\nsegment target=4s\npackager timescale before=90000 after=30000\nsegment 5 duration=3.970\nsegment 6 starts pts=599040\nplayer accepts stream, validation fixture rejects boundary\n```\n\nDetermine whether timescale rounding, keyframe cadence, or the fixture's exact-time assumption causes the mismatch and whether encryption rotation remains safe.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.76,"slice":"boundary","lang":"en"} -{"prompt":"finish the streaming endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"Propose an architecture for dynamic ad insertion in live streams, including cue ingestion, personalization, manifest manipulation, measurement, privacy, fallback, and failover.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"core","lang":"en"} -{"prompt":"Add ID3 timed-metadata parsing to `streaminspect`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Pull request excerpt:\n\n```diff\n func ServeManifest(w http.ResponseWriter, r *http.Request) {\n- decision, err := rights.Check(r.Context(), viewer(r), assetID(r))\n- if err != nil || !decision.Allowed { http.Error(w, \"forbidden\", 403); return }\n- writeManifest(w, decision.PolicyVersion)\n+ go rights.Check(context.Background(), viewer(r), assetID(r))\n+ writeManifest(w, \"latest\")\n }\n```\n\nThe author says rights checks add too much playback latency. Review disclosure, territory, stale policy, audit, error handling, and what asynchronous checking can accomplish after delivery. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Schreibe eine kurze Referenz für die bestehenden Wiedergabe-Fehlercodes, einschließlich Ursachen und sicherer Wiederholungen. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"boundary","lang":"de"} -{"prompt":"Build the responsive livestream control room with preview, health indicators, scene switching, chat moderation, and keyboard shortcuts.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Review how playback sessions are currently counted, explain heartbeats and expiry, then turn the findings into an analytics guide.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"Set the default playback speed to `1.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Benenne `AssetCtx` repositoryweit in `AssetContext` um; JSON-Felder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"de"} -{"prompt":"Consolidate duration formatting across web, mobile, and TV clients without changing displayed text.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Diagnose the duplicate chapter marker","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Explain how the player chooses an audio adaptation set when language and accessibility preferences conflict.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Create API documentation for the existing playback-session endpoint, including expiry, device fields, heartbeats, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"en"} -{"prompt":"Plan a migration from origin-hosted media to a multi-CDN delivery layer, covering cache keys, failover, signing, logs, cost, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"core","lang":"en"} -{"prompt":"TV app ticket:\n\n```text\nScreen: series details\nHero: artwork, title, metadata, actions, current season context\nContinue action resumes latest unfinished episode\nSeason picker preserves focus when changing season\nEpisode rows show progress, download state, availability, and audio-description badge\nLarge artwork loads progressively without shifting layout\nOffline mode shows only playable downloaded episodes\nAccessibility: focus order follows visual layout; synopsis can be expanded; badges have spoken labels\nRemote control: long press opens episode actions\n```\n\nImplement the tvOS screen and UI tests using existing playback models.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"pasted-context","lang":"en"} -{"prompt":"Implement `POST /v1/assets/{id}/reprocess` with profile validation, idempotency, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Remove the extra comma in the subtitle menu","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"core","lang":"en"} -{"prompt":"Fix the clipped live badge and extract its repeated offset into the shared player styles.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.36,"slice":"mixed","lang":"en"} -{"prompt":"Replace scattered upload booleans with one explicit lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Cambia `cueIdx` por `cueIndex` solo en `CaptionTimeline.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"es"} +{"prompt":"Add bounded command replay for devices reconnecting after extended outages.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the responsive tariff-comparison view with rate periods, estimated impact, caveats, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"fix pairing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `FwUpdate` with `FirmwareUpdate` across packages while preserving protocol field names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose why battery alerts fire repeatedly after acknowledgement, implement the verified state fix, and update notification documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the gateway keep two previous configuration generations? Explain current rollback and corruption recovery.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down occasional timestamp jumps in telemetry after gateway reboot.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Write a troubleshooting guide for missing device telemetry, covering connectivity, buffering, schemas, quarantine, and clocks.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Security design packet:\n\n```text\nFeature: temporary installer access\nHome owner generates a six-digit code valid for 30 minutes\nInstaller enters code on local gateway setup page\nAccess permits adding devices and running diagnostics, not viewing history\nGateway may be offline from cloud during installation\nCode can be used from any device on the local network\nOwner receives notification after cloud reconnect\nAccess session ends after 15 minutes idle or explicit revoke\nCurrent proposal stores hashed code in gateway config flash\n```\n\nReview code entropy, brute force, offline verification, local-network threats, scope, storage, expiry, revocation, and delayed notification. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add a loading state to the room controls","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Plan and implement tenant-defined telemetry retention. First define precedence, legal holds, aggregates, exports, deletion proof, offline buffers, and rollout; then add policy storage and enforcement.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Outline an architecture for peer-to-peer device control during cloud outages, including trust, discovery, consistency, safety, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement snapshot-consistent device-state exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Escribe una guía para integrar nuevos medidores, con identidad, intervalos, correcciones, validación y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"es"} +{"prompt":"Move command-expiry calculation out of the delivery worker without changing behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Investigate why the iOS app loses room assignments after restoring a backup.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add atomic device-profile publication with validation, preview, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Remove the obsolete `shadow_v1` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the firmware-release detail page with compatibility, rollout progress, health metrics, pause, and rollback controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"`Deivce offline` を `Device offline` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"ja"} +{"prompt":"Review the remote-diagnostics endpoint for command injection, sensitive logs, stale authorization, resource abuse, and audit gaps.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement device-ownership history and write its API guide. Include transfers, invitations, effective dates, pagination, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan a disaster-recovery strategy for the device cloud, including brokers, state, commands, firmware, keys, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add content-hash deduplication to uploaded gateway diagnostic bundles.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the desktop fleet-group editor with rules, membership preview, exclusions, scheduling, and validation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Rename `MeterIntvl` to `MeterInterval` across packages while preserving serialized field names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why device transfers leave old owners subscribed to alerts, implement the verified fan-out fix, and update help documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed energy forecasting cache for household isolation, stale corrections, missing intervals, consent, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why a gateway retransmits the same buffered batch forever after one invalid sample.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft a support guide for recovering a gateway after interrupted firmware installation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Telemetry storage failure:\n\n```text\nshard=ts_18 tenant=t_71 series=device_power\ncompaction input blocks=[881,882,883]\nblock 882 min_time=10:00 max_time=11:00 checksum=ok\nlate sample batch writes block 884 min_time=10:42 max_time=10:47\ncompactor snapshot excludes block 884\nmanifest generation=992 replaces blocks 881..883 with block 991\nlate block 884 cleanup classified as fully covered by block 991 time range\nblock 884 deleted\nquery loses 2,441 late samples\n```\n\nDetermine why time-range coverage is mistaken for sample coverage and how compaction snapshot boundaries allowed the late block to be deleted.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add signal quality text below the chart","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Restructure the firmware package builder and document its component interface. Preserve package bytes while separating assembly, signing, delta generation, and validation.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Architect a multi-region device-command platform with ownership, ordering, failover, offline queues, audit, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement signed telemetry batch receipts with sequence ranges and content digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new firmware board, including bootloader, partitions, keys, flashing, and hardware tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Consolidate utility-timezone resolution across ingestion and exports without changing interval dates.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Investigate why a removed automation still runs once after deletion.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add transactional gateway replacement with device reassignment and credential revocation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Set the retained-message limit to 2048","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile sensor-detail screen with current value, trends, battery, calibration, alerts, and accessible charts.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"把 `Firmare update` 改成 `Firmware update`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"zh"} +{"prompt":"Inspect the device-provisioning QR parser for malformed payloads, tenant confusion, replay, oversized fields, and unsafe URLs.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Implement command-delivery history and write its API documentation. Include attempts, acknowledgements, expiry, redaction, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Design a global media-processing platform for uploads, transcoding, packaging, thumbnails, captions, moderation, and delivery. Cover job idempotency, asset lineage, storage tiers, regional execution, failure recovery, quotas, migration from per-product pipelines, and rollout milestones. Deliver an architecture proposal only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Before implementing low-latency live streaming, outline ingest, transcoding, segmenting, playback, regional failover, chat synchronization, moderation delay, observability, and phased rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add AV1 output to the transcode worker","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Playback incident logs:\n\n```text\nasset=vid_881 manifest_version=42 player=web-9.14\nmaster playlist variants=[1080p,720p,480p]\nselected=1080p bandwidth_estimate=8.2Mbps\nsegment 441 CDN status=200 bytes=1848812 duration=4.0\nsegment 442 CDN status=206 bytes=524288 content-range=0-524287/1931120\nplayer retry range=524288- status=200 content-length=1931120\nbuffer append error='SourceBuffer append window overlap'\nABR downswitch requested=720p\nplayhead stalls at=1768.0s buffer_ahead=0\n```\n\nDetermine whether the CDN mishandles the second range request, the player appends duplicate bytes, or the variant switch exposes the corrupted segment state.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Build the SwiftUI episode-player controls with chapters, speed, captions, audio tracks, casting, and VoiceOver-safe time controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Plan and implement a content-rights enforcement service. Begin with a design covering territories, time windows, subscription tiers, device restrictions, downloads, live events, policy versioning, cache invalidation, audit, and failure behavior. Then add the evaluator, policy APIs, signed decisions, metrics, and conformance tests. Treat policy semantics and rollout as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":1,"slice":"mixed","lang":"en"} +{"prompt":"Set `MAX_UPLOAD_GB` to 80","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Extract duplicated timecode parsing from captions and chapter imports while preserving accepted formats and errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement `/internal/transcode/capabilities` with codecs, profiles, hardware, limits, and worker generation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"make the player cinematic","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Find why downloaded podcasts occasionally restart from zero after the app relaunches.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Explain how `SegmentTimeline` handles discontinuities, encoder restarts, and ad insertions. Do not change code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Creator launch notes:\n\n```text\nFeature: replace uploaded video before publication\nCreator may replace source media while title, description, comments setting, and scheduled publish time remain\nExisting preview links temporarily show processing state\nOld source is retained for seven days for recovery\nCaptions and chapters are revalidated against new duration\nCustom thumbnails remain unless dimensions become invalid\nReplacement is unavailable after first publication\nAnalytics from preview playback remain attached to the draft\nProcessing failure leaves the previous source active\n```\n\nTurn this into creator-facing release notes and a help article. Clarify recovery, processing failure, metadata retention, and the publication restriction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} +{"prompt":"Move the caption button away from the scrubber thumb","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Write an operator guide for replaying failed transcode jobs without publishing duplicate renditions.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Implement asset-rendition endpoints with codec filtering, signed URLs, and authorization, then document freshness, expiry, examples, and errors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Map out a migration from HLS-only packaging to CMAF shared segments for HLS and DASH, including compatibility, storage, validation, rollout, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Rename `segIdx` to `segmentIndex` in `PlayerState.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Teach the upload service to resume multipart transfers using content-range validation and per-part checksums.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Polish the playlist header","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump FFmpeg to `8.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Rename `MasterManifest` to `PrimaryManifest` across packager, player, tests, and metrics while preserving manifest output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Split `MediaPipeline` into probing, transcoding, packaging, validation, and publication phases without changing assets.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implementation ticket:\n\n```text\nMEDIA-720 — automatic caption ingest\nSources: uploaded WebVTT, SRT, TTML, and provider-generated captions\nRequirements:\n- normalize to internal cue model\n- preserve language, kind, and source provenance\n- reject overlapping cues only for formats that disallow them\n- clamp cues extending at most 250ms beyond duration; reject larger overflow\n- duplicate upload is idempotent by content hash\n- publication requires language uniqueness per caption kind\n- malformed files return line and column when possible\n- expose parsed, rejected, clamped, and duplicate counters\n```\n\nImplement parsers, normalization, validation, storage, idempotency, publication checks, metrics, and fixtures.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Investigate why the Android player loses audio after switching from Bluetooth to the phone speaker.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the caption editor UI and add a concise guide for timings, overlaps, speaker labels, shortcuts, and validation.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Why does the transcoder preserve source color metadata even when the target profile fixes primaries? Explain current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Rewrite the local setup for running MinIO, MediaMTX, the transcode workers, and sample streams.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"This packaging test started failing after updating Bento4:\n\n```text\nFAIL TestKeyRotationAlignsWithSegments\nperiod=0 key_id=k1 segments=1..5\nperiod=1 key_id=k2 segments=6..10\nexpected rotation_time=20.000 actual=19.968\ninput frame rate=30000/1001 keyframe interval=60\nsegment target=4s\npackager timescale before=90000 after=30000\nsegment 5 duration=3.970\nsegment 6 starts pts=599040\nplayer accepts stream, validation fixture rejects boundary\n```\n\nDetermine whether timescale rounding, keyframe cadence, or the fixture's exact-time assumption causes the mismatch and whether encryption rotation remains safe.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"finish the streaming endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Propose an architecture for dynamic ad insertion in live streams, including cue ingestion, personalization, manifest manipulation, measurement, privacy, fallback, and failover.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add ID3 timed-metadata parsing to `streaminspect`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Pull request excerpt:\n\n```diff\n func ServeManifest(w http.ResponseWriter, r *http.Request) {\n- decision, err := rights.Check(r.Context(), viewer(r), assetID(r))\n- if err != nil || !decision.Allowed { http.Error(w, \"forbidden\", 403); return }\n- writeManifest(w, decision.PolicyVersion)\n+ go rights.Check(context.Background(), viewer(r), assetID(r))\n+ writeManifest(w, \"latest\")\n }\n```\n\nThe author says rights checks add too much playback latency. Review disclosure, territory, stale policy, audit, error handling, and what asynchronous checking can accomplish after delivery. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Schreibe eine kurze Referenz für die bestehenden Wiedergabe-Fehlercodes, einschließlich Ursachen und sicherer Wiederholungen. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"de"} +{"prompt":"Build the responsive livestream control room with preview, health indicators, scene switching, chat moderation, and keyboard shortcuts.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Review how playback sessions are currently counted, explain heartbeats and expiry, then turn the findings into an analytics guide.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Set the default playback speed to `1.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Benenne `AssetCtx` repositoryweit in `AssetContext` um; JSON-Felder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"de"} +{"prompt":"Consolidate duration formatting across web, mobile, and TV clients without changing displayed text.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose the duplicate chapter marker","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Explain how the player chooses an audio adaptation set when language and accessibility preferences conflict.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Create API documentation for the existing playback-session endpoint, including expiry, device fields, heartbeats, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Plan a migration from origin-hosted media to a multi-CDN delivery layer, covering cache keys, failover, signing, logs, cost, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"TV app ticket:\n\n```text\nScreen: series details\nHero: artwork, title, metadata, actions, current season context\nContinue action resumes latest unfinished episode\nSeason picker preserves focus when changing season\nEpisode rows show progress, download state, availability, and audio-description badge\nLarge artwork loads progressively without shifting layout\nOffline mode shows only playable downloaded episodes\nAccessibility: focus order follows visual layout; synopsis can be expanded; badges have spoken labels\nRemote control: long press opens episode actions\n```\n\nImplement the tvOS screen and UI tests using existing playback models.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Implement `POST /v1/assets/{id}/reprocess` with profile validation, idempotency, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Remove the extra comma in the subtitle menu","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fix the clipped live badge and extract its repeated offset into the shared player styles.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Replace scattered upload booleans with one explicit lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Cambia `cueIdx` por `cueIndex` solo en `CaptionTimeline.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"es"} {"prompt":"Investigate why AirPlay playback resumes several seconds behind the local device after reconnecting.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Summarize the current media-retention lifecycle for legal and storage reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Develop a capacity roadmap for processing five million video hours per month. Include worker pools, GPU allocation, queues, storage, retries, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"core","lang":"en"} -{"prompt":"Implement idempotent live-recording finalization with segment inventory and gap reporting.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Create the Compose podcast queue with reorder, swipe alternatives, download states, and TalkBack actions.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Fix `transcodding` in `jobs.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} -{"prompt":"Merge duplicate rendition-selection logic used by download and playback services while preserving choices.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Live-stream failure output:\n\n```text\nstream=live_118 ingest_region=us-east\nencoder connection=enc_72 epoch=18\nsegment sequence=881 duration=2.002 published\nnetwork reconnect encoder epoch=19 sequence reset=0\npackager maps incoming sequence 0 to global 882\nbackup encoder still active epoch=17 emits sequence=882\npackager accepts backup segment as global 882 after primary\nmanifest contains duplicate media sequence 882 with different URI\nplayers split between two timelines and some jump backward\n```\n\nDetermine why encoder epoch and media sequence do not uniquely identify segments and how backup ingest races the reconnected primary.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.83,"slice":"pasted-context","lang":"en"} -{"prompt":"Rename `capton_lang` to `caption_lang` in the unreleased schema.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"en"} +{"prompt":"Summarize the current media-retention lifecycle for legal and storage reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Develop a capacity roadmap for processing five million video hours per month. Include worker pools, GPU allocation, queues, storage, retries, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement idempotent live-recording finalization with segment inventory and gap reporting.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the Compose podcast queue with reorder, swipe alternatives, download states, and TalkBack actions.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Fix `transcodding` in `jobs.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Merge duplicate rendition-selection logic used by download and playback services while preserving choices.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Live-stream failure output:\n\n```text\nstream=live_118 ingest_region=us-east\nencoder connection=enc_72 epoch=18\nsegment sequence=881 duration=2.002 published\nnetwork reconnect encoder epoch=19 sequence reset=0\npackager maps incoming sequence 0 to global 882\nbackup encoder still active epoch=17 emits sequence=882\npackager accepts backup segment as global 882 after primary\nmanifest contains duplicate media sequence 882 with different URI\nplayers split between two timelines and some jump backward\n```\n\nDetermine why encoder epoch and media sequence do not uniquely identify segments and how backup ingest races the reconnected primary.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Rename `capton_lang` to `caption_lang` in the unreleased schema.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"Assess whether signed media URLs can be reused across profiles, territories, or account sessions. Review verification and cache behavior only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Restructure the player SDK into manifest, buffering, ABR, DRM, and telemetry modules, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"Plan the retirement of the legacy RTMP playback endpoint, covering clients, redirects, feature parity, communication, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.81,"slice":"core","lang":"en"} -{"prompt":"Add immutable provenance chains to derived media renditions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Restructure the player SDK into manifest, buffering, ABR, DRM, and telemetry modules, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan the retirement of the legacy RTMP playback endpoint, covering clients, redirects, feature parity, communication, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add immutable provenance chains to derived media renditions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Build the tablet clip editor with trim handles, frame preview, captions, undo, export, and accessible controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"do the playback screen","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `RendRef` with `RenditionReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why exported caption files omit corrected cues, implement the verified version-selection fix, and add a creator-facing note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.77,"slice":"mixed","lang":"en"} -{"prompt":"Why does the transcoder retain failed intermediate files for 48 hours? Explain current debugging and recovery behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.47,"slice":"boundary","lang":"en"} -{"prompt":"Track down the GPU memory leak after repeatedly switching encoder profiles.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"Write release notes for multi-audio downloads, including storage impact, defaults, and old-client compatibility.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"Download redesign notes:\n\n```text\nCurrent: one fixed 720p rendition, default audio, all captions\nNew need: viewer chooses quality and audio languages\nDownloads must remain playable when rights expire only if policy allows grace\nStorage estimate shown before confirmation\nPartial downloads resume by segment\nChanging device storage location invalidates open file handles\nDownloaded manifests must not expose origin URLs\nAccount logout deletes keys immediately and media later\nOld app versions understand only one audio track\n```\n\nProduce an implementation-free design and migration plan covering selection, rights, storage, resume, keys, logout, manifests, and compatibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"Give the playback settings sheet clearer sections","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.32,"slice":"core","lang":"en"} -{"prompt":"Turn the current live-stream latency behavior into broadcaster documentation, then review whether its timing and fallback claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Outline a phased architecture for moving media metadata from MongoDB to Postgres, without implementing schemas or migrations.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.84,"slice":"boundary","lang":"en"} +{"prompt":"Replace `RendRef` with `RenditionReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose why exported caption files omit corrected cues, implement the verified version-selection fix, and add a creator-facing note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the transcoder retain failed intermediate files for 48 hours? Explain current debugging and recovery behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down the GPU memory leak after repeatedly switching encoder profiles.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write release notes for multi-audio downloads, including storage impact, defaults, and old-client compatibility.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Download redesign notes:\n\n```text\nCurrent: one fixed 720p rendition, default audio, all captions\nNew need: viewer chooses quality and audio languages\nDownloads must remain playable when rights expire only if policy allows grace\nStorage estimate shown before confirmation\nPartial downloads resume by segment\nChanging device storage location invalidates open file handles\nDownloaded manifests must not expose origin URLs\nAccount logout deletes keys immediately and media later\nOld app versions understand only one audio track\n```\n\nProduce an implementation-free design and migration plan covering selection, rights, storage, resume, keys, logout, manifests, and compatibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Give the playback settings sheet clearer sections","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Turn the current live-stream latency behavior into broadcaster documentation, then review whether its timing and fallback claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Outline a phased architecture for moving media metadata from MongoDB to Postgres, without implementing schemas or migrations.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Implement version-aware caption history with correction links and publication snapshots.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Create an operator guide for diagnosing DRM license failures by platform and territory.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Move thumbnail selection out of `AssetController` while preserving chosen images and fallbacks.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Investigate why revoked playback sessions remain active through one CDN region.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","lang":"en"} -{"prompt":"Add generation-fenced encoding-profile publication with preview and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Set the preview clip length to 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Create the responsive creator analytics view with watch time, retention curves, filters, comparisons, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Corrige apenas `playbak` para `playback` no novo alerta.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"pt"} -{"prompt":"Review the subtitle-upload endpoint for parser bombs, unsafe markup, language spoofing, tenant confusion, and partial failures.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Implement live-event history and write its API guide. Include ingest epochs, status, failures, recordings, pagination, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Design a migration from centralized transcoding to regional compute near upload origins, including scheduling, storage, consistency, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"core","lang":"en"} -{"prompt":"Add content-hash deduplication to uploaded source media with tenant-isolated ownership.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Build the desktop stream-health dashboard with ingest, renditions, segments, latency, alerts, and diagnostics.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"continue the audio issue","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.54,"slice":"vague-eval","lang":"en"} -{"prompt":"Extract media-language normalization into one shared module while preserving selected tracks.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why scheduled premieres send notifications at the wrong local time, implement the verified timezone fix, and update creator documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.75,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed client-side ad measurement for fraud, privacy, offline playback, clock manipulation, and deduplication.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Find why one packager worker retries a permanently malformed segment forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Draft a migration guide for creators moving from SRT captions to WebVTT.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.36,"slice":"core","lang":"en"} -{"prompt":"Media-quality incident excerpt:\n\n```text\nprofile=mobile_hevc generation=71\nsource color_primaries=bt2020 transfer=smpte2084 matrix=bt2020nc\noutput codec=hevc pix_fmt=yuv420p10le\nencoder flags include tone_map=hable target=bt709\nprobe output color_primaries=bt2020 transfer=bt709 matrix=bt2020nc\nvisual report: washed-out colors on SDR Android devices\nvalidation checks resolution, bitrate, duration, and frame count only\nHDR test asset passed because reference player honors bt2020 primaries\n```\n\nDetermine how inconsistent color metadata survives tone mapping and why existing validation misses the SDR compatibility problem.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Add elapsed time beside the live badge","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.24,"slice":"core","lang":"en"} -{"prompt":"Restructure the transcode scheduler and document its worker interface. Preserve job choices while separating capabilities, placement, leases, retries, and completion.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"Architect a multi-region live-video control plane with ingest ownership, failover, sequence continuity, rights, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed rendition manifests with source digest and encoder provenance.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new playback platform, including capabilities, DRM, telemetry, fixtures, and certification.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.47,"slice":"core","lang":"en"} -{"prompt":"Consolidate playback-position serialization across TV and mobile clients without changing resume behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Investigate why chapter titles remain stale after a metadata republish.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional asset replacement with immutable source revisions and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Pin Shaka Player to `4.16.4`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Build the mobile download manager with queue order, quality, storage, progress, retry, and accessible actions.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Remplace `Subtiles` par `Subtitles` uniquement dans le nouveau menu.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"fr"} -{"prompt":"Inspect the media-proxy endpoint for SSRF, cache poisoning, oversized ranges, origin leakage, and authorization gaps.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} +{"prompt":"Create an operator guide for diagnosing DRM license failures by platform and territory.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Move thumbnail selection out of `AssetController` while preserving chosen images and fallbacks.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why revoked playback sessions remain active through one CDN region.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add generation-fenced encoding-profile publication with preview and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Set the preview clip length to 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Create the responsive creator analytics view with watch time, retention curves, filters, comparisons, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Corrige apenas `playbak` para `playback` no novo alerta.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"pt"} +{"prompt":"Review the subtitle-upload endpoint for parser bombs, unsafe markup, language spoofing, tenant confusion, and partial failures.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement live-event history and write its API guide. Include ingest epochs, status, failures, recordings, pagination, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Design a migration from centralized transcoding to regional compute near upload origins, including scheduling, storage, consistency, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add content-hash deduplication to uploaded source media with tenant-isolated ownership.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Build the desktop stream-health dashboard with ingest, renditions, segments, latency, alerts, and diagnostics.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Extract media-language normalization into one shared module while preserving selected tracks.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why scheduled premieres send notifications at the wrong local time, implement the verified timezone fix, and update creator documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed client-side ad measurement for fraud, privacy, offline playback, clock manipulation, and deduplication.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why one packager worker retries a permanently malformed segment forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft a migration guide for creators moving from SRT captions to WebVTT.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Media-quality incident excerpt:\n\n```text\nprofile=mobile_hevc generation=71\nsource color_primaries=bt2020 transfer=smpte2084 matrix=bt2020nc\noutput codec=hevc pix_fmt=yuv420p10le\nencoder flags include tone_map=hable target=bt709\nprobe output color_primaries=bt2020 transfer=bt709 matrix=bt2020nc\nvisual report: washed-out colors on SDR Android devices\nvalidation checks resolution, bitrate, duration, and frame count only\nHDR test asset passed because reference player honors bt2020 primaries\n```\n\nDetermine how inconsistent color metadata survives tone mapping and why existing validation misses the SDR compatibility problem.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Add elapsed time beside the live badge","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Restructure the transcode scheduler and document its worker interface. Preserve job choices while separating capabilities, placement, leases, retries, and completion.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Architect a multi-region live-video control plane with ingest ownership, failover, sequence continuity, rights, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement signed rendition manifests with source digest and encoder provenance.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new playback platform, including capabilities, DRM, telemetry, fixtures, and certification.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Consolidate playback-position serialization across TV and mobile clients without changing resume behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why chapter titles remain stale after a metadata republish.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add transactional asset replacement with immutable source revisions and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Pin Shaka Player to `4.16.4`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile download manager with queue order, quality, storage, progress, retry, and accessible actions.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remplace `Subtiles` par `Subtitles` uniquement dans le nouveau menu.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"fr"} +{"prompt":"Inspect the media-proxy endpoint for SSRF, cache poisoning, oversized ranges, origin leakage, and authorization gaps.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Implement playback-error history and write the integration documentation. Include platform, rendition, network state, redaction, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Develop a roadmap for replacing proprietary DRM wrappers with standard EME integrations, including clients, licenses, telemetry, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.87,"slice":"core","lang":"en"} -{"prompt":"Add bounded live-chat replay synchronized to media sequence numbers.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Create the responsive audio-track editor with waveform, regions, fades, playback, undo, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"fix captions","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `MediaEvt` with `MediaEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why downloaded episodes expire early after device timezone changes, implement the verified timestamp fix, and update help documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Why does the player retain two previous DRM licenses? Explain current offline and rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.48,"slice":"boundary","lang":"en"} -{"prompt":"Track down occasional audio drift after mid-roll ad insertion.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Write a troubleshooting guide for buffering, covering bandwidth, CDN, DRM, device decoding, and player logs.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Rights review packet:\n\n```text\nFeature: household playback sharing\nAccount owner invites up to five household members\nAll members share subscription tier and content entitlements\nConcurrent-stream limit applies across household\nDownloads are encrypted per device, not per member\nRemoving a member blocks new licenses immediately\nExisting offline licenses remain until their normal expiry, maximum 30 days\nViewing history remains attached to the removed member account\nOwner can see device names but not titles watched\n```\n\nReview entitlement revocation, offline access, device reuse, privacy, concurrency, audit, and user expectations. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a loading state to the episode rows","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Plan and implement tenant-defined media retention. First define precedence, legal holds, renditions, downloads, exports, deletion proof, and rollout; then add policy storage and enforcement.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.93,"slice":"mixed","lang":"en"} -{"prompt":"Outline an architecture for peer-assisted enterprise video delivery, including trust, topology, bandwidth controls, privacy, fallback, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"boundary","lang":"en"} -{"prompt":"Implement snapshot-consistent media catalog exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Escribe una guía para integrar subtítulos, con formatos, idiomas, tiempos, validación y publicación.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} -{"prompt":"Move playback-entitlement caching out of the manifest handler without changing decisions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Investigate why the iOS player loses selected captions after Picture in Picture.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Add atomic live-event configuration publication with preview and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Remove the obsolete `legacy_hls` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"core","lang":"en"} -{"prompt":"Build the asset-library grid with filters, processing states, bulk actions, drag upload, and accessible selection.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"`Playbak error` を `Playback error` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"ja"} -{"prompt":"Review the creator-upload completion endpoint for part substitution, checksum confusion, race conditions, tenant isolation, and quota bypass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"Implement asset-revision history and write its API guide. Include source replacement, processing, publication, rollback, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Plan a disaster-recovery strategy for media services, including sources, renditions, metadata, keys, manifests, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"core","lang":"en"} -{"prompt":"Add content-hash deduplication to caption uploads with provenance preservation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Create the desktop rights-policy editor with territories, windows, tiers, preview, conflicts, and validation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"continue the player cleanup","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.44,"slice":"vague-eval","lang":"en"} -{"prompt":"Rename `CaptionTrk` to `CaptionTrack` across packages while preserving manifest labels.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why replaced videos keep old thumbnail timestamps, implement the verified cache-invalidation fix, and update creator documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.73,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed playback telemetry cache for account isolation, consent, stale sessions, offline uploads, and deletion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.69,"slice":"boundary","lang":"en"} -{"prompt":"Find why an encoder retries the same corrupt frame indefinitely.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Draft a support guide for recovering a failed livestream recording.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} -{"prompt":"Storage incident output:\n\n```text\nasset=vid_441 source_revision=8\nretention worker marks revision=7 expired\nactive transcode job references source object rev7/original.mov\njob lease heartbeat delayed 94s during GPU reset\nretention query sees no active lease within 60s\nsource object deleted\nworker resumes and finishes video segments from local disk\ncaption extraction later requests source object and fails 404\npublication sees video renditions complete and captions optional, marks revision=8 ready\n```\n\nDetermine how lease timing permits deletion of an in-use source and why partial pipeline completion publishes an asset missing expected captions.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.81,"slice":"pasted-context","lang":"en"} -{"prompt":"Add bitrate text to the quality menu","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Restructure the rights evaluator and document its policy interface. Preserve decisions while separating context, rules, precedence, explanation, and caching.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"Architect a globally distributed media metadata service with regional ownership, publication consistency, audit, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed playback decisions with policy version, asset revision, and expiry.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new transcode profile, including capabilities, fixtures, quality validation, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Consolidate thumbnail URL generation across APIs without changing cache keys or images.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"core","lang":"en"} -{"prompt":"Investigate why deleted downloads still consume storage in the Android app.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.61,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional playlist reordering with version conflicts and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Set the caption cue limit to 50000","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Build the mobile creator upload flow with selection, metadata, progress, background recovery, and processing status.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"把 `Subtitel settings` 改成 `Subtitle settings`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"zh"} -{"prompt":"Inspect the live-chat replay endpoint for cross-stream leakage, timestamp manipulation, unbounded ranges, and deleted-message exposure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Implement media-delivery history and write its API documentation. Include CDNs, status, cache results, errors, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Design a mission-execution architecture for autonomous warehouse robots. Cover task assignment, route reservations, localization confidence, offline operation, safety stops, retries, fleet coordination, audit replay, simulator parity, and migration from the current central dispatcher. Deliver an RFC and milestones, not code.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"core","lang":"en"} -{"prompt":"Before implementing outdoor delivery zones, outline the geospatial model for boundaries, entrances, restricted areas, map versions, routing, stale clients, validation, and phased rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"boundary","lang":"en"} -{"prompt":"Add GeoJSON multipolygon support to `mapctl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Robot incident telemetry:\n\n```text\nrobot=r_41 mission=m_982 map_version=118\npose x=44.18 y=12.77 heading=1.57 confidence=0.94\nreservation corridor=c_17 holder=r_41 expires=14:08:10.000\nnetwork loss begins=14:07:51.442\nlocal planner enters corridor at=14:08:08.211\nserver expires reservation at=14:08:10.001\nrobot=r_53 receives corridor=c_17 reservation at=14:08:10.114\nr_41 reconnects at=14:08:12.801 and reports occupied=true\nfleet stop issued at=14:08:12.940\n```\n\nDetermine whether the offline robot should have treated the lease as unsafe before entering and how clock uncertainty and server reassignment created simultaneous ownership.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.88,"slice":"pasted-context","lang":"en"} -{"prompt":"Build the tablet mission-monitor screen with map, robot status, route progress, alerts, intervention controls, and accessible list fallback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Plan and implement a map-distribution service for robots and simulators. Begin with a design covering immutable versions, regional caches, compatibility, differential updates, signature verification, rollout cohorts, rollback, offline fleets, and audit. Then add storage, publication, download, validation, and conformance tests. Treat safety and compatibility design as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.97,"slice":"mixed","lang":"en"} -{"prompt":"Set `MAX_ROUTE_RETRIES` to 6","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Extract duplicated pose interpolation from replay and visualization while preserving numeric results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Implement `/internal/fleet/reservations` with resource, holder, generation, expiry, and conflict count.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} -{"prompt":"make the robot map cooler","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.42,"slice":"vague-eval","lang":"en"} -{"prompt":"Find why the localization service occasionally jumps a robot pose two meters after an elevator ride.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Explain how `RoutePlanner` chooses between distance, congestion, battery, and one-way aisle costs. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Operations launch notes:\n\n```text\nFeature: manual robot recovery mode\nAuthorized operators can pause a robot and request guided movement\nMovement controls are limited to low speed and expire after 30 seconds idle\nRobot retains local obstacle and emergency-stop enforcement\nRecovery actions are recorded with operator, robot, reason, and command result\nMode is unavailable during fire-alarm evacuation\nVideo preview may be delayed by up to two seconds\nLosing the operator connection stops guided movement\nA supervisor receives a summary after the session ends\n```\n\nTurn this into an operator guide with prerequisites, limitations, safety wording, session lifecycle, and troubleshooting.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.49,"slice":"pasted-context","lang":"en"} -{"prompt":"Move the robot heading label outside the route line","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.14,"slice":"boundary","lang":"en"} -{"prompt":"Write an operator runbook for replaying failed mission events without reissuing physical commands.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Implement map-version history with compatibility filters and signed downloads, then document activation, rollback, examples, and errors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} +{"prompt":"Develop a roadmap for replacing proprietary DRM wrappers with standard EME integrations, including clients, licenses, telemetry, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add bounded live-chat replay synchronized to media sequence numbers.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the responsive audio-track editor with waveform, regions, fades, playback, undo, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"fix captions","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `MediaEvt` with `MediaEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose why downloaded episodes expire early after device timezone changes, implement the verified timestamp fix, and update help documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the player retain two previous DRM licenses? Explain current offline and rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down occasional audio drift after mid-roll ad insertion.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Write a troubleshooting guide for buffering, covering bandwidth, CDN, DRM, device decoding, and player logs.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Rights review packet:\n\n```text\nFeature: household playback sharing\nAccount owner invites up to five household members\nAll members share subscription tier and content entitlements\nConcurrent-stream limit applies across household\nDownloads are encrypted per device, not per member\nRemoving a member blocks new licenses immediately\nExisting offline licenses remain until their normal expiry, maximum 30 days\nViewing history remains attached to the removed member account\nOwner can see device names but not titles watched\n```\n\nReview entitlement revocation, offline access, device reuse, privacy, concurrency, audit, and user expectations. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Add a loading state to the episode rows","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Plan and implement tenant-defined media retention. First define precedence, legal holds, renditions, downloads, exports, deletion proof, and rollout; then add policy storage and enforcement.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Outline an architecture for peer-assisted enterprise video delivery, including trust, topology, bandwidth controls, privacy, fallback, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement snapshot-consistent media catalog exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Escribe una guía para integrar subtítulos, con formatos, idiomas, tiempos, validación y publicación.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"es"} +{"prompt":"Move playback-entitlement caching out of the manifest handler without changing decisions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why the iOS player loses selected captions after Picture in Picture.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add atomic live-event configuration publication with preview and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Remove the obsolete `legacy_hls` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Build the asset-library grid with filters, processing states, bulk actions, drag upload, and accessible selection.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"`Playbak error` を `Playback error` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"ja"} +{"prompt":"Review the creator-upload completion endpoint for part substitution, checksum confusion, race conditions, tenant isolation, and quota bypass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement asset-revision history and write its API guide. Include source replacement, processing, publication, rollback, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan a disaster-recovery strategy for media services, including sources, renditions, metadata, keys, manifests, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add content-hash deduplication to caption uploads with provenance preservation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the desktop rights-policy editor with territories, windows, tiers, preview, conflicts, and validation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Rename `CaptionTrk` to `CaptionTrack` across packages while preserving manifest labels.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why replaced videos keep old thumbnail timestamps, implement the verified cache-invalidation fix, and update creator documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed playback telemetry cache for account isolation, consent, stale sessions, offline uploads, and deletion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why an encoder retries the same corrupt frame indefinitely.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft a support guide for recovering a failed livestream recording.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Storage incident output:\n\n```text\nasset=vid_441 source_revision=8\nretention worker marks revision=7 expired\nactive transcode job references source object rev7/original.mov\njob lease heartbeat delayed 94s during GPU reset\nretention query sees no active lease within 60s\nsource object deleted\nworker resumes and finishes video segments from local disk\ncaption extraction later requests source object and fails 404\npublication sees video renditions complete and captions optional, marks revision=8 ready\n```\n\nDetermine how lease timing permits deletion of an in-use source and why partial pipeline completion publishes an asset missing expected captions.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add bitrate text to the quality menu","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Restructure the rights evaluator and document its policy interface. Preserve decisions while separating context, rules, precedence, explanation, and caching.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Architect a globally distributed media metadata service with regional ownership, publication consistency, audit, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement signed playback decisions with policy version, asset revision, and expiry.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new transcode profile, including capabilities, fixtures, quality validation, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Consolidate thumbnail URL generation across APIs without changing cache keys or images.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why deleted downloads still consume storage in the Android app.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add transactional playlist reordering with version conflicts and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Set the caption cue limit to 50000","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile creator upload flow with selection, metadata, progress, background recovery, and processing status.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"把 `Subtitel settings` 改成 `Subtitle settings`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"zh"} +{"prompt":"Inspect the live-chat replay endpoint for cross-stream leakage, timestamp manipulation, unbounded ranges, and deleted-message exposure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement media-delivery history and write its API documentation. Include CDNs, status, cache results, errors, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Design a mission-execution architecture for autonomous warehouse robots. Cover task assignment, route reservations, localization confidence, offline operation, safety stops, retries, fleet coordination, audit replay, simulator parity, and migration from the current central dispatcher. Deliver an RFC and milestones, not code.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Before implementing outdoor delivery zones, outline the geospatial model for boundaries, entrances, restricted areas, map versions, routing, stale clients, validation, and phased rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add GeoJSON multipolygon support to `mapctl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Robot incident telemetry:\n\n```text\nrobot=r_41 mission=m_982 map_version=118\npose x=44.18 y=12.77 heading=1.57 confidence=0.94\nreservation corridor=c_17 holder=r_41 expires=14:08:10.000\nnetwork loss begins=14:07:51.442\nlocal planner enters corridor at=14:08:08.211\nserver expires reservation at=14:08:10.001\nrobot=r_53 receives corridor=c_17 reservation at=14:08:10.114\nr_41 reconnects at=14:08:12.801 and reports occupied=true\nfleet stop issued at=14:08:12.940\n```\n\nDetermine whether the offline robot should have treated the lease as unsafe before entering and how clock uncertainty and server reassignment created simultaneous ownership.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Build the tablet mission-monitor screen with map, robot status, route progress, alerts, intervention controls, and accessible list fallback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Plan and implement a map-distribution service for robots and simulators. Begin with a design covering immutable versions, regional caches, compatibility, differential updates, signature verification, rollout cohorts, rollback, offline fleets, and audit. Then add storage, publication, download, validation, and conformance tests. Treat safety and compatibility design as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":1.0,"slice":"mixed","lang":"en"} +{"prompt":"Set `MAX_ROUTE_RETRIES` to 6","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Extract duplicated pose interpolation from replay and visualization while preserving numeric results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Implement `/internal/fleet/reservations` with resource, holder, generation, expiry, and conflict count.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"make the robot map cooler","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Find why the localization service occasionally jumps a robot pose two meters after an elevator ride.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Explain how `RoutePlanner` chooses between distance, congestion, battery, and one-way aisle costs. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Operations launch notes:\n\n```text\nFeature: manual robot recovery mode\nAuthorized operators can pause a robot and request guided movement\nMovement controls are limited to low speed and expire after 30 seconds idle\nRobot retains local obstacle and emergency-stop enforcement\nRecovery actions are recorded with operator, robot, reason, and command result\nMode is unavailable during fire-alarm evacuation\nVideo preview may be delayed by up to two seconds\nLosing the operator connection stops guided movement\nA supervisor receives a summary after the session ends\n```\n\nTurn this into an operator guide with prerequisites, limitations, safety wording, session lifecycle, and troubleshooting.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"Move the robot heading label outside the route line","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Write an operator runbook for replaying failed mission events without reissuing physical commands.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement map-version history with compatibility filters and signed downloads, then document activation, rollback, examples, and errors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Map out a migration from raster occupancy grids to layered vector maps, covering conversion, validation, old firmware, simulation, rollout, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Rename `poseTs` to `poseTimestamp` in `LocalizationState.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"en"} -{"prompt":"Teach the mission scheduler to reserve charging docks atomically and release abandoned claims.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Polish the battery status panel","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.28,"slice":"core","lang":"en"} -{"prompt":"Bump `geos` to `3.14.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Rename `MasterMap` to `PrimaryMap` across services, simulator, metrics, and tests while preserving file formats.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Split `MissionCoordinator` into assignment, reservation, execution, recovery, and completion components without changing behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"en"} -{"prompt":"Implementation ticket:\n\n```text\nROBOT-1920 — elevator trip coordination\nResources: elevator car, landing door, entry zone, exit zone\nRobot requests trip with origin, destination, size class, and deadline\nOnly one incompatible robot load per car\nBuilding controller reports arrival, door state, motion, and faults\nRobot must not enter until car and door state agree\nDuplicate controller events are expected\nCommunication loss during travel transitions mission to supervised recovery\nEvery transition records source event and map version\nExpose wait time, failed trips, state disagreement, and recovery metrics\n```\n\nImplement the state machine, resource leases, controller adapter, event idempotency, recovery path, persistence, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.92,"slice":"pasted-context","lang":"en"} -{"prompt":"Investigate why the simulator completes turns faster than physical robots despite identical velocity limits.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Create the route-conflict inspector and add a short legend for reservations, predicted occupancy, stale poses, and priority overrides.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Why does the mapping service keep superseded map tiles for 90 days? Explain current rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"Rewrite the local setup for running ROS 2, Gazebo, PostGIS, and the fleet simulator.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"This path-planning test fails only under randomized execution:\n\n```text\nFAIL TestReservationAvoidsHeadOnConflict seed=88172\nrobot A start=(1,4) goal=(9,4) priority=2\nrobot B start=(9,4) goal=(1,4) priority=1\nplanner A reserves cells t=0..8\nplanner B detects conflict at cell=(5,4) t=4\nplanner B inserts wait at t=3\nreplan A triggered by cost update and drops reservation generation=41\nplanner B commits against generation=41\nplanner A commits replacement generation=42 using stale occupancy snapshot\nboth occupy cell=(5,4) t=5\n```\n\nDetermine whether generation checks, snapshot isolation, or reservation replacement ordering permits both plans to commit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.85,"slice":"boundary","lang":"en"} -{"prompt":"finish the route service","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} -{"prompt":"Propose an architecture for high-fidelity fleet simulation, including deterministic time, sensor models, map versions, scenario fixtures, fault injection, and production replay.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"core","lang":"en"} -{"prompt":"Add GPX route simplification to `tracktool`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Review excerpt:\n\n```diff\n func (s *Safety) AllowMove(cmd MoveCommand) bool {\n- if !s.estop.Clear() { return false }\n- if s.obstacles.Distance(cmd.Direction) < minDistance { return false }\n- if cmd.ExpiresAt.Before(s.clock.Now()) { return false }\n- return s.signature.Verify(cmd)\n+ return s.cloudDecision.Allowed(cmd.ID)\n }\n```\n\nThe author says central policy avoids inconsistent local rules. Review offline behavior, latency, stale decisions, emergency stop, obstacle sensing, signatures, and safety boundaries. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.81,"slice":"pasted-context","lang":"en"} -{"prompt":"Schreibe eine kurze Referenz für die bestehenden Missionsstatus und deren Auswirkungen auf Befehle und Wiederaufnahme. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"de"} -{"prompt":"Build the desktop scenario editor with map placement, robot starts, tasks, faults, timeline, undo, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Review how production missions are converted into simulator replays, then turn the findings into a validation guide with examples.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.62,"slice":"mixed","lang":"en"} -{"prompt":"Set the stale-pose threshold to 3s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Benenne `NavCtx` repositoryweit in `NavigationContext` um; Protokollfelder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"de"} -{"prompt":"Consolidate coordinate-frame conversion across localization and mapping without changing numeric output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Diagnose the duplicated stop alert","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Explain how the dispatcher prevents low-priority replenishment jobs from starving behind urgent picks.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Create API documentation for the existing mission-command endpoints, including generations, expiry, acknowledgement, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"boundary","lang":"en"} -{"prompt":"Plan a migration from one central fleet scheduler to zone-owned schedulers, covering robot transfers, shared resources, failover, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"core","lang":"en"} -{"prompt":"Product ticket:\n\n```text\nScreen: warehouse operations overview\nSummary cards: active missions, blocked robots, charging, manual recovery\nMap layers: robot positions, planned routes, restricted zones, congestion\nTable: robot, mission, battery, status, last update, zone\nLive events can arrive out of order\nMap must degrade to list view for accessibility and low-power devices\nStates: map unavailable, stale telemetry, partial building outage, loading\nOperators can filter by zone, robot model, mission type, and status\nAt 500+ robots, labels appear only on selection or alert\n```\n\nImplement the responsive dashboard and tests using existing fleet APIs.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.76,"slice":"pasted-context","lang":"en"} -{"prompt":"Implement `POST /v1/missions/{id}/pause` with generation checks, safety acknowledgement, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Remove the extra arrow from the route label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"core","lang":"en"} -{"prompt":"Fix the clipped robot label and extract its repeated map-edge inset into shared styles.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.36,"slice":"mixed","lang":"en"} -{"prompt":"Replace scattered mission booleans with one explicit lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Cambia `mapRev` por `mapRevision` solo en `RouteState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"es"} -{"prompt":"Investigate why the operator console briefly shows robots from the previous facility after switching workspaces.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"Summarize the current safety-stop lifecycle for engineering and compliance reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"Develop a capacity roadmap for coordinating 100,000 robots across 2,000 sites. Include partitioning, command delivery, maps, telemetry, simulation, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"core","lang":"en"} -{"prompt":"Implement idempotent map-change ingestion with topology validation and immutable revisions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Create the Compose robot-detail screen with mission, battery, pose confidence, alerts, logs, and TalkBack support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Fix `localizaton` in `metrics.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} -{"prompt":"Merge duplicate geometric-tolerance helpers used by map validation and route planning while preserving decisions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Localization failure output:\n\n```text\nrobot=r_88 map=warehouse-b version=204\nlidar scan match score=0.81 pose=(18.2,7.4,1.56)\nwheel odometry pose=(16.1,7.3,1.55)\nAprilTag detection id=tag_41 pose=(16.0,7.2,1.57)\nfilter innovation=2.21m threshold=2.0m\nmeasurement rejected as outlier\nnext five lidar updates reinforce shifted pose\nconfidence remains=0.89 because covariance shrinks\nrobot enters wrong aisle coordinate frame\n```\n\nDetermine why the filter rejects the stronger absolute measurement, then becomes more confident in the incorrect lidar hypothesis.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.83,"slice":"pasted-context","lang":"en"} -{"prompt":"Rename `waypont_id` to `waypoint_id` in the unreleased schema.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"en"} -{"prompt":"Assess whether mission replay can expose another tenant's map or telemetry through shared artifact caches. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Restructure the mapping SDK into geometry, topology, tiles, revisions, and validation, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.77,"slice":"mixed","lang":"en"} -{"prompt":"Plan the retirement of the legacy waypoint protocol, covering robot firmware, adapters, dual operation, migration, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"core","lang":"en"} -{"prompt":"Add immutable provenance chains to imported map layers.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} +{"prompt":"Rename `poseTs` to `poseTimestamp` in `LocalizationState.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Teach the mission scheduler to reserve charging docks atomically and release abandoned claims.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Polish the battery status panel","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump `geos` to `3.14.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename `MasterMap` to `PrimaryMap` across services, simulator, metrics, and tests while preserving file formats.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Split `MissionCoordinator` into assignment, reservation, execution, recovery, and completion components without changing behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implementation ticket:\n\n```text\nROBOT-1920 — elevator trip coordination\nResources: elevator car, landing door, entry zone, exit zone\nRobot requests trip with origin, destination, size class, and deadline\nOnly one incompatible robot load per car\nBuilding controller reports arrival, door state, motion, and faults\nRobot must not enter until car and door state agree\nDuplicate controller events are expected\nCommunication loss during travel transitions mission to supervised recovery\nEvery transition records source event and map version\nExpose wait time, failed trips, state disagreement, and recovery metrics\n```\n\nImplement the state machine, resource leases, controller adapter, event idempotency, recovery path, persistence, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Investigate why the simulator completes turns faster than physical robots despite identical velocity limits.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the route-conflict inspector and add a short legend for reservations, predicted occupancy, stale poses, and priority overrides.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Why does the mapping service keep superseded map tiles for 90 days? Explain current rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Rewrite the local setup for running ROS 2, Gazebo, PostGIS, and the fleet simulator.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"This path-planning test fails only under randomized execution:\n\n```text\nFAIL TestReservationAvoidsHeadOnConflict seed=88172\nrobot A start=(1,4) goal=(9,4) priority=2\nrobot B start=(9,4) goal=(1,4) priority=1\nplanner A reserves cells t=0..8\nplanner B detects conflict at cell=(5,4) t=4\nplanner B inserts wait at t=3\nreplan A triggered by cost update and drops reservation generation=41\nplanner B commits against generation=41\nplanner A commits replacement generation=42 using stale occupancy snapshot\nboth occupy cell=(5,4) t=5\n```\n\nDetermine whether generation checks, snapshot isolation, or reservation replacement ordering permits both plans to commit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"finish the route service","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Propose an architecture for high-fidelity fleet simulation, including deterministic time, sensor models, map versions, scenario fixtures, fault injection, and production replay.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add GPX route simplification to `tracktool`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Review excerpt:\n\n```diff\n func (s *Safety) AllowMove(cmd MoveCommand) bool {\n- if !s.estop.Clear() { return false }\n- if s.obstacles.Distance(cmd.Direction) < minDistance { return false }\n- if cmd.ExpiresAt.Before(s.clock.Now()) { return false }\n- return s.signature.Verify(cmd)\n+ return s.cloudDecision.Allowed(cmd.ID)\n }\n```\n\nThe author says central policy avoids inconsistent local rules. Review offline behavior, latency, stale decisions, emergency stop, obstacle sensing, signatures, and safety boundaries. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Schreibe eine kurze Referenz für die bestehenden Missionsstatus und deren Auswirkungen auf Befehle und Wiederaufnahme. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"de"} +{"prompt":"Build the desktop scenario editor with map placement, robot starts, tasks, faults, timeline, undo, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Review how production missions are converted into simulator replays, then turn the findings into a validation guide with examples.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Set the stale-pose threshold to 3s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Benenne `NavCtx` repositoryweit in `NavigationContext` um; Protokollfelder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"de"} +{"prompt":"Consolidate coordinate-frame conversion across localization and mapping without changing numeric output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose the duplicated stop alert","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Explain how the dispatcher prevents low-priority replenishment jobs from starving behind urgent picks.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Create API documentation for the existing mission-command endpoints, including generations, expiry, acknowledgement, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Plan a migration from one central fleet scheduler to zone-owned schedulers, covering robot transfers, shared resources, failover, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Product ticket:\n\n```text\nScreen: warehouse operations overview\nSummary cards: active missions, blocked robots, charging, manual recovery\nMap layers: robot positions, planned routes, restricted zones, congestion\nTable: robot, mission, battery, status, last update, zone\nLive events can arrive out of order\nMap must degrade to list view for accessibility and low-power devices\nStates: map unavailable, stale telemetry, partial building outage, loading\nOperators can filter by zone, robot model, mission type, and status\nAt 500+ robots, labels appear only on selection or alert\n```\n\nImplement the responsive dashboard and tests using existing fleet APIs.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Implement `POST /v1/missions/{id}/pause` with generation checks, safety acknowledgement, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remove the extra arrow from the route label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fix the clipped robot label and extract its repeated map-edge inset into shared styles.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Replace scattered mission booleans with one explicit lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Cambia `mapRev` por `mapRevision` solo en `RouteState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"es"} +{"prompt":"Investigate why the operator console briefly shows robots from the previous facility after switching workspaces.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Summarize the current safety-stop lifecycle for engineering and compliance reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Develop a capacity roadmap for coordinating 100,000 robots across 2,000 sites. Include partitioning, command delivery, maps, telemetry, simulation, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement idempotent map-change ingestion with topology validation and immutable revisions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the Compose robot-detail screen with mission, battery, pose confidence, alerts, logs, and TalkBack support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Fix `localizaton` in `metrics.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Merge duplicate geometric-tolerance helpers used by map validation and route planning while preserving decisions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Localization failure output:\n\n```text\nrobot=r_88 map=warehouse-b version=204\nlidar scan match score=0.81 pose=(18.2,7.4,1.56)\nwheel odometry pose=(16.1,7.3,1.55)\nAprilTag detection id=tag_41 pose=(16.0,7.2,1.57)\nfilter innovation=2.21m threshold=2.0m\nmeasurement rejected as outlier\nnext five lidar updates reinforce shifted pose\nconfidence remains=0.89 because covariance shrinks\nrobot enters wrong aisle coordinate frame\n```\n\nDetermine why the filter rejects the stronger absolute measurement, then becomes more confident in the incorrect lidar hypothesis.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Rename `waypont_id` to `waypoint_id` in the unreleased schema.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Assess whether mission replay can expose another tenant's map or telemetry through shared artifact caches. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Restructure the mapping SDK into geometry, topology, tiles, revisions, and validation, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan the retirement of the legacy waypoint protocol, covering robot firmware, adapters, dual operation, migration, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add immutable provenance chains to imported map layers.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Build the tablet manual-recovery flow with safety checks, video, controls, connection loss, and confirmation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"do the fleet page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `RobotRef` with `RobotReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why exported mission reports omit recovery actions, implement the verified event-filter fix, and add an operator note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.77,"slice":"mixed","lang":"en"} -{"prompt":"Why does the scheduler retain completed route reservations for five minutes? Explain current debugging and safety behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.46,"slice":"boundary","lang":"en"} +{"prompt":"Replace `RobotRef` with `RobotReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose why exported mission reports omit recovery actions, implement the verified event-filter fix, and add an operator note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the scheduler retain completed route reservations for five minutes? Explain current debugging and safety behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} {"prompt":"Track down the CPU spike in the map tile server after every facility revision.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write release notes for priority-based mission preemption, including eligibility, recovery, and operator visibility.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.36,"slice":"core","lang":"en"} +{"prompt":"Write release notes for priority-based mission preemption, including eligibility, recovery, and operator visibility.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Battery planning notes:\n\n```text\nCurrent scheduler sends robot to charge below 20%\nNew need: predict whether remaining energy can finish assigned mission\nInputs: route distance, payload, floor type, temperature, battery health, elevator waits\nPrediction may be unavailable for new robot models\nSafety reserve is configurable by site but has a global minimum\nCharging docks have queue estimates\nOperators may force completion during urgent operations with reason\nPrediction and override must be auditable\nOld firmware reports battery percent but not health\n```\n\nProduce an implementation-free design and rollout plan covering prediction, fallback, reserves, dock scheduling, overrides, audit, and compatibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Give the mission timeline clearer grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.32,"slice":"core","lang":"en"} -{"prompt":"Turn the current map-validation behavior into operator documentation, then review whether its geometry and compatibility claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Outline a phased architecture for moving fleet telemetry from Cassandra to ClickHouse, without implementing ingestion or queries.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.85,"slice":"boundary","lang":"en"} -{"prompt":"Implement version-aware mission history with compacted snapshots and replay.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Create an operator guide for diagnosing robots stuck waiting for shared resources.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} -{"prompt":"Move route-cost normalization out of `PlannerController` while preserving path choices.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Investigate why revoked operator access remains active in one facility console.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Add generation-fenced safety-policy publication with simulation preview and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Set the reservation TTL to 15s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Create the responsive map-version history with diffs, compatibility, activation, and rollback controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Corrige apenas `misson` para `mission` no novo alerta.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"pt"} -{"prompt":"Review the robot-log upload endpoint for tenant spoofing, sensitive video, decompression bombs, and unsafe retention.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} +{"prompt":"Give the mission timeline clearer grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Turn the current map-validation behavior into operator documentation, then review whether its geometry and compatibility claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Outline a phased architecture for moving fleet telemetry from Cassandra to ClickHouse, without implementing ingestion or queries.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement version-aware mission history with compacted snapshots and replay.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create an operator guide for diagnosing robots stuck waiting for shared resources.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Move route-cost normalization out of `PlannerController` while preserving path choices.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why revoked operator access remains active in one facility console.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add generation-fenced safety-policy publication with simulation preview and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Set the reservation TTL to 15s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Create the responsive map-version history with diffs, compatibility, activation, and rollback controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Corrige apenas `misson` para `mission` no novo alerta.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"pt"} +{"prompt":"Review the robot-log upload endpoint for tenant spoofing, sensitive video, decompression bombs, and unsafe retention.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Implement mission-intervention history and write its API guide. Include actor, reason, commands, outcomes, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Design a migration from static facility maps to continuously updated semantic maps, including validation, robot compatibility, audit, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"core","lang":"en"} -{"prompt":"Add content-hash deduplication to map artifacts with signature preservation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Build the desktop fleet replay viewer with map, telemetry, events, controls, bookmarks, and export.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"continue the localization bug","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.56,"slice":"vague-eval","lang":"en"} -{"prompt":"Extract zone-name normalization into one shared module while preserving identifiers and display names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why overnight missions use yesterday's restricted-zone schedule, implement the verified cache-key fix, and update operator documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.78,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed camera-based congestion estimator for privacy, occlusion, confidence, bias, retention, and safe fallback.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Find why one scheduler partition retries an impossible mission forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Draft a migration guide for facilities moving from local coordinates to global building coordinates.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Simulation parity report:\n\n```text\nscenario=loaded_turn_90deg seed=7712\nphysical robot duration=4.82s max_lateral_error=0.08m\nsimulator duration=3.91s max_lateral_error=0.02m\ncontroller configuration digest matches\nphysical wheel radius measured=0.0987m configured=0.1000m\nsimulator applies acceleration limit per axis\nfirmware applies vector magnitude limit\nsimulated floor friction=1.0 constant\nphysical telemetry shows slip ratio up to=0.07\nparity gate checks final pose only and passes\n```\n\nDetermine which model differences explain the timing gap and why the current parity gate misses behavior important to scheduling.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Add confidence text beside the pose marker","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.24,"slice":"core","lang":"en"} -{"prompt":"Restructure the mission scheduler and document its policy interface. Preserve assignments while separating eligibility, scoring, reservations, dispatch, and recovery.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.82,"slice":"mixed","lang":"en"} -{"prompt":"Architect a globally distributed fleet-control plane with site ownership, failover, command ordering, safety, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.98,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed mission receipts with map version, command sequence, and outcome digest.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new robot model, including capabilities, kinematics, simulation, safety, and certification.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.47,"slice":"core","lang":"en"} -{"prompt":"Consolidate mission-duration formatting across console and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Investigate why deleted restricted zones remain active on one robot cohort.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional robot reassignment between sites with credential rotation and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Pin ROS 2 to `Kilted Kaiju`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.08,"slice":"core","lang":"en"} -{"prompt":"Build the mobile incident-detail screen with affected robots, event timeline, map, actions, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Remplace `Localisation` par `Localization` uniquement dans le nouveau libellé anglais.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"fr"} -{"prompt":"Inspect the mission-upload endpoint for path injection, oversized scenarios, tenant confusion, unsafe plugins, and resource exhaustion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} +{"prompt":"Design a migration from static facility maps to continuously updated semantic maps, including validation, robot compatibility, audit, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add content-hash deduplication to map artifacts with signature preservation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Build the desktop fleet replay viewer with map, telemetry, events, controls, bookmarks, and export.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Extract zone-name normalization into one shared module while preserving identifiers and display names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Investigate why overnight missions use yesterday's restricted-zone schedule, implement the verified cache-key fix, and update operator documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed camera-based congestion estimator for privacy, occlusion, confidence, bias, retention, and safe fallback.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why one scheduler partition retries an impossible mission forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Draft a migration guide for facilities moving from local coordinates to global building coordinates.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Simulation parity report:\n\n```text\nscenario=loaded_turn_90deg seed=7712\nphysical robot duration=4.82s max_lateral_error=0.08m\nsimulator duration=3.91s max_lateral_error=0.02m\ncontroller configuration digest matches\nphysical wheel radius measured=0.0987m configured=0.1000m\nsimulator applies acceleration limit per axis\nfirmware applies vector magnitude limit\nsimulated floor friction=1.0 constant\nphysical telemetry shows slip ratio up to=0.07\nparity gate checks final pose only and passes\n```\n\nDetermine which model differences explain the timing gap and why the current parity gate misses behavior important to scheduling.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Add confidence text beside the pose marker","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Restructure the mission scheduler and document its policy interface. Preserve assignments while separating eligibility, scoring, reservations, dispatch, and recovery.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Architect a globally distributed fleet-control plane with site ownership, failover, command ordering, safety, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement signed mission receipts with map version, command sequence, and outcome digest.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new robot model, including capabilities, kinematics, simulation, safety, and certification.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Consolidate mission-duration formatting across console and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Investigate why deleted restricted zones remain active on one robot cohort.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add transactional robot reassignment between sites with credential rotation and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Pin ROS 2 to `Kilted Kaiju`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile incident-detail screen with affected robots, event timeline, map, actions, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Remplace `Localisation` par `Localization` uniquement dans le nouveau libellé anglais.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"fr"} +{"prompt":"Inspect the mission-upload endpoint for path injection, oversized scenarios, tenant confusion, unsafe plugins, and resource exhaustion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Implement robot-health history and write its API documentation. Include signals, state changes, firmware, pagination, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Develop a roadmap for replacing proprietary robot telemetry with an OpenTelemetry-based schema, including compatibility, edge cost, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"core","lang":"en"} -{"prompt":"Add bounded mission replay with checkpointed fleet projections.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Create the responsive charging-dock dashboard with queues, availability, faults, reservations, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"fix the map","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `MapEvt` with `MapEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why completed missions remain active in the mobile app, implement the verified projection fix, and update troubleshooting docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.73,"slice":"mixed","lang":"en"} -{"prompt":"Why does the planner keep two previous cost-map generations? Explain current fallback and replay behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.47,"slice":"boundary","lang":"en"} -{"prompt":"Track down occasional missing obstacle events after gateway reconnect.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Write a troubleshooting guide for failed map publication, covering geometry, topology, signatures, compatibility, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Safety review packet:\n\n```text\nFeature: operator-defined temporary no-go zone\nOperator draws polygon on live map and chooses duration up to eight hours\nZone becomes active after server validation and robot acknowledgement\nRobots already inside may exit using the shortest safe route\nIf a robot does not acknowledge within 30 seconds, site enters degraded mode\nZones can overlap permanent routes and charging docks\nDeletion requires acknowledgement before routing resumes\nMobile app supports viewing but not creation\nAudit stores polygon, map version, actor, reason, activation, and acknowledgements\n```\n\nReview geometry validation, activation semantics, robots inside, acknowledgement failure, deletion, stale maps, and audit. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a loading state to the mission cards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Plan and implement temporary restricted zones. First define geometry, precedence, acknowledgement, offline robots, expiry, deletion, audit, and rollout; then add storage, distribution, and route integration.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.93,"slice":"mixed","lang":"en"} -{"prompt":"Outline an architecture for robot-to-robot coordination during site-network outages, including trust, discovery, reservations, safety, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"boundary","lang":"en"} -{"prompt":"Implement snapshot-consistent fleet-state exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Escribe una guía para integrar nuevos mapas, con capas, geometría, compatibilidad, validación y publicación.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} -{"prompt":"Move reservation-expiry calculation out of the scheduler without changing behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Investigate why the Android console loses selected map layers after rotation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"Add atomic route-policy publication with simulator preview and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Remove the obsolete `planner_v1` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"core","lang":"en"} -{"prompt":"Build the map-layer manager with visibility, opacity, ordering, import status, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"`Misson paused` を `Mission paused` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"ja"} -{"prompt":"Review the remote-robot diagnostics endpoint for command injection, video leakage, stale authorization, and audit gaps.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"Implement map-validation history and write its API guide. Include checks, warnings, compatibility, pagination, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Plan a disaster-recovery strategy for fleet control, including maps, missions, commands, telemetry, keys, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Add content-hash deduplication to uploaded simulation scenarios.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Create the desktop safety-policy editor with rules, affected robots, simulation, conflicts, and approval.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"continue the scheduler cleanup","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.44,"slice":"vague-eval","lang":"en"} -{"prompt":"Rename `RouteRes` to `RouteReservation` across packages while preserving protocol fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why site transfers leave robots subscribed to old map updates, implement the verified routing fix, and update operator docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} +{"prompt":"Develop a roadmap for replacing proprietary robot telemetry with an OpenTelemetry-based schema, including compatibility, edge cost, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add bounded mission replay with checkpointed fleet projections.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the responsive charging-dock dashboard with queues, availability, faults, reservations, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"fix the map","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `MapEvt` with `MapEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose why completed missions remain active in the mobile app, implement the verified projection fix, and update troubleshooting docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the planner keep two previous cost-map generations? Explain current fallback and replay behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down occasional missing obstacle events after gateway reconnect.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Write a troubleshooting guide for failed map publication, covering geometry, topology, signatures, compatibility, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Safety review packet:\n\n```text\nFeature: operator-defined temporary no-go zone\nOperator draws polygon on live map and chooses duration up to eight hours\nZone becomes active after server validation and robot acknowledgement\nRobots already inside may exit using the shortest safe route\nIf a robot does not acknowledge within 30 seconds, site enters degraded mode\nZones can overlap permanent routes and charging docks\nDeletion requires acknowledgement before routing resumes\nMobile app supports viewing but not creation\nAudit stores polygon, map version, actor, reason, activation, and acknowledgements\n```\n\nReview geometry validation, activation semantics, robots inside, acknowledgement failure, deletion, stale maps, and audit. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add a loading state to the mission cards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Plan and implement temporary restricted zones. First define geometry, precedence, acknowledgement, offline robots, expiry, deletion, audit, and rollout; then add storage, distribution, and route integration.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Outline an architecture for robot-to-robot coordination during site-network outages, including trust, discovery, reservations, safety, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement snapshot-consistent fleet-state exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Escribe una guía para integrar nuevos mapas, con capas, geometría, compatibilidad, validación y publicación.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"es"} +{"prompt":"Move reservation-expiry calculation out of the scheduler without changing behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Investigate why the Android console loses selected map layers after rotation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add atomic route-policy publication with simulator preview and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Remove the obsolete `planner_v1` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Build the map-layer manager with visibility, opacity, ordering, import status, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"`Misson paused` を `Mission paused` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"ja"} +{"prompt":"Review the remote-robot diagnostics endpoint for command injection, video leakage, stale authorization, and audit gaps.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement map-validation history and write its API guide. Include checks, warnings, compatibility, pagination, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan a disaster-recovery strategy for fleet control, including maps, missions, commands, telemetry, keys, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add content-hash deduplication to uploaded simulation scenarios.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Create the desktop safety-policy editor with rules, affected robots, simulation, conflicts, and approval.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Rename `RouteRes` to `RouteReservation` across packages while preserving protocol fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Investigate why site transfers leave robots subscribed to old map updates, implement the verified routing fix, and update operator docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Assess the proposed cloud route cache for stale maps, site isolation, dynamic zones, revocation, and failover.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Find why a robot keeps retrying a permanently rejected mission.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Draft a support guide for recovering a robot after failed map activation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Mission event-store failure:\n\n```text\nmission=m_992 projection_version=881\ncommand pause sequence=118 stored event offset=77120\nprojection worker applies pause and checkpoints offset=77120\ncommand resume sequence=119 stored event offset=77121\nprojection worker crashes after updating state but before checkpoint\nrestart loads checkpoint=77120 and state snapshot already says running\nreplays resume event against running state, rejects invalid transition\npartition stops and later mission events accumulate\n```\n\nDetermine how state and checkpoint were committed separately and why replay is not idempotent after the partial projection update.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Add route length below the mission title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.24,"slice":"core","lang":"en"} -{"prompt":"Restructure the localization pipeline and document its sensor interface. Preserve poses while separating inputs, synchronization, filtering, validation, and publication.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.82,"slice":"mixed","lang":"en"} -{"prompt":"Architect a multi-region geospatial platform for maps, routing, revisions, search, and fleet clients with migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"boundary","lang":"en"} +{"prompt":"Find why a robot keeps retrying a permanently rejected mission.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Draft a support guide for recovering a robot after failed map activation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Mission event-store failure:\n\n```text\nmission=m_992 projection_version=881\ncommand pause sequence=118 stored event offset=77120\nprojection worker applies pause and checkpoints offset=77120\ncommand resume sequence=119 stored event offset=77121\nprojection worker crashes after updating state but before checkpoint\nrestart loads checkpoint=77120 and state snapshot already says running\nreplays resume event against running state, rejects invalid transition\npartition stops and later mission events accumulate\n```\n\nDetermine how state and checkpoint were committed separately and why replay is not idempotent after the partial projection update.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Add route length below the mission title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Restructure the localization pipeline and document its sensor interface. Preserve poses while separating inputs, synchronization, filtering, validation, and publication.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Architect a multi-region geospatial platform for maps, routing, revisions, search, and fleet clients with migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Implement signed map manifests with layer digests and compatibility ranges.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new mission type, including eligibility, scheduling, execution, recovery, and simulation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Consolidate robot-status formatting across console and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Investigate why an expired restricted zone remains visible in route previews.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.61,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional map ownership transfer between facilities with audit history.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Set the map tile cache to 2 GB","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Build the mobile route-preview screen with steps, restrictions, congestion, battery estimate, and accessible summary.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"把 `Robto offline` 改成 `Robot offline`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"zh"} -{"prompt":"Inspect the scenario-upload parser for path traversal, unsafe scripts, huge worlds, tenant confusion, and resource exhaustion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new mission type, including eligibility, scheduling, execution, recovery, and simulation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Consolidate robot-status formatting across console and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why an expired restricted zone remains visible in route previews.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add transactional map ownership transfer between facilities with audit history.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Set the map tile cache to 2 GB","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile route-preview screen with steps, restrictions, congestion, battery estimate, and accessible summary.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"把 `Robto offline` 改成 `Robot offline`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"zh"} +{"prompt":"Inspect the scenario-upload parser for path traversal, unsafe scripts, huge worlds, tenant confusion, and resource exhaustion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Implement mission-execution history and write its API documentation. Include commands, transitions, map versions, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Design a versioned contract-management architecture for clauses, templates, negotiations, signatures, amendments, obligations, and audit history. Cover immutable revisions, permissions, search, external collaborators, retention, regional storage, migration from uploaded PDFs, and rollout milestones. Deliver an RFC only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Before implementing electronic filing, outline the submission model for forms, attachments, validation, signatures, receipts, corrections, deadlines, outages, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"boundary","lang":"en"} -{"prompt":"Add detached signature verification to `/v2/filings`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Document-ingestion failure logs:\n\n```text\nmatter=m_881 upload=u_771 filename=agreement-final.pdf\nsha256=91af...02c pages=184\nOCR worker generation=44 extracted pages=1..184\npage 73 rotation=90 confidence=0.62\nlayout worker emitted clause anchors using original page coordinates\nredaction worker rotated page bitmap before applying anchors\nredaction count expected=42 applied=39 rejected_out_of_bounds=3\npreview renderer shows names visible on page 73\nvalidation compares redaction object count, not covered pixels\npublication status=ready\n```\n\nDetermine how coordinate systems diverge after rotation and why validation allows three failed redactions into a published document.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Build the responsive contract-clause editor with revision markers, comments, suggestions, defined-term links, and accessible keyboard navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Plan and implement a policy-rules service for government benefit applications. Begin with a design covering effective dates, jurisdiction, evidence, explanations, appeals, policy versioning, audit replay, failure behavior, and migration. Then add the evaluator, rule publication, decision trace, APIs, and conformance tests. Treat policy semantics and reproducibility as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.98,"slice":"mixed","lang":"en"} -{"prompt":"Set `MAX_ATTACHMENT_MB` to 40","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Extract duplicated legal-date parsing from filing and notice services while preserving accepted precision and errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Implement `/internal/signatures/status` with active certificates, trust roots, revocation age, and failures.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} -{"prompt":"make the forms less governmenty","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.42,"slice":"vague-eval","lang":"en"} +{"prompt":"Design a versioned contract-management architecture for clauses, templates, negotiations, signatures, amendments, obligations, and audit history. Cover immutable revisions, permissions, search, external collaborators, retention, regional storage, migration from uploaded PDFs, and rollout milestones. Deliver an RFC only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Before implementing electronic filing, outline the submission model for forms, attachments, validation, signatures, receipts, corrections, deadlines, outages, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add detached signature verification to `/v2/filings`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Document-ingestion failure logs:\n\n```text\nmatter=m_881 upload=u_771 filename=agreement-final.pdf\nsha256=91af...02c pages=184\nOCR worker generation=44 extracted pages=1..184\npage 73 rotation=90 confidence=0.62\nlayout worker emitted clause anchors using original page coordinates\nredaction worker rotated page bitmap before applying anchors\nredaction count expected=42 applied=39 rejected_out_of_bounds=3\npreview renderer shows names visible on page 73\nvalidation compares redaction object count, not covered pixels\npublication status=ready\n```\n\nDetermine how coordinate systems diverge after rotation and why validation allows three failed redactions into a published document.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Build the responsive contract-clause editor with revision markers, comments, suggestions, defined-term links, and accessible keyboard navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Plan and implement a policy-rules service for government benefit applications. Begin with a design covering effective dates, jurisdiction, evidence, explanations, appeals, policy versioning, audit replay, failure behavior, and migration. Then add the evaluator, rule publication, decision trace, APIs, and conformance tests. Treat policy semantics and reproducibility as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":1,"slice":"mixed","lang":"en"} +{"prompt":"Set `MAX_ATTACHMENT_MB` to 40","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Extract duplicated legal-date parsing from filing and notice services while preserving accepted precision and errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement `/internal/signatures/status` with active certificates, trust roots, revocation age, and failures.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"make the forms less governmenty","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"Find why submitted applications occasionally revert to draft after an applicant uploads another attachment.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Explain how `ClauseMatcher` relocates annotations between contract revisions and when it marks them orphaned. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Launch notes for clerks:\n\n```text\nFeature: filing correction requests\nA filer may request correction of metadata after acceptance\nEligible fields: party display name, internal reference, document description\nFiled document bytes and submission time cannot change\nClerk approves, partially approves, or denies the request\nApproved changes create a new metadata revision and preserve the original\nPublic docket reflects accepted corrections after publication\nNotifications contain case and request numbers but no document contents\nCorrection requests do not extend legal deadlines\n```\n\nTurn this into filer-facing release notes and a clerk procedure guide. Clearly distinguish metadata corrections from amended filings.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.48,"slice":"pasted-context","lang":"en"} -{"prompt":"Move the validation badge closer to the field label","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.13,"slice":"boundary","lang":"en"} -{"prompt":"Write an operator guide for replaying failed filing notifications without duplicating official receipts.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Implement contract-obligation endpoints with assignees, dates, status, and permissions, then document their lifecycle, examples, and errors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Map out a migration from free-form contract folders to matter-scoped document workspaces, including permissions, links, search, compatibility, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"core","lang":"en"} -{"prompt":"Rename `caseNo` to `caseNumber` in `FilingMapper.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"en"} -{"prompt":"Teach the filing worker to resume large attachment validation from durable page checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Polish the deadline summary card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.28,"slice":"core","lang":"en"} -{"prompt":"Bump `pdfbox` to `3.0.5`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Rename `MasterDocket` to `PrimaryDocket` across services, schemas, events, and dashboards while preserving public fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"Split `FilingProcessor` into intake, validation, signature, persistence, and receipt components without changing outcomes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Implementation ticket:\n\n```text\nCIVIC-2207 — application evidence requests\nCaseworker requests one or more evidence categories with due date and explanation\nApplicant uploads files or marks category unavailable with reason\nEach upload receives malware scan, format validation, and immutable receipt\nCaseworker may accept, reject, or request replacement\nA replacement does not delete prior evidence\nDeadline extension requires separate authorization and audit event\nDuplicate mobile uploads are common\nNotifications must not name sensitive evidence categories on shared devices\n```\n\nImplement the state model, commands, upload idempotency, review flow, receipts, extension checks, audit, notifications, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Investigate why the Android filing app associates a scanned attachment with the previously opened form.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Create the obligation timeline UI and add a short legend for due, completed, waived, disputed, and superseded items.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.64,"slice":"mixed","lang":"en"} -{"prompt":"Why does the docket service retain rejected filings for five years? Explain existing audit and retention behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.48,"slice":"core","lang":"en"} -{"prompt":"Rewrite the local setup for running MinIO, ClamAV, OpenSearch, and the synthetic filing service.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.34,"slice":"core","lang":"en"} -{"prompt":"This signature-validation test fails only around midnight UTC:\n\n```text\nFAIL CertificatePolicyTest.accepts_on_final_valid_day\ncertificate not_before=2025-08-01T00:00:00Z not_after=2026-07-30T23:59:59Z\nfiling signed_at=2026-07-30T21:10:00-04:00\nvalidator normalizes signed_at=2026-07-31T01:10:00Z\nexpected valid based on filer local date=2026-07-30\nactual expired\npolicy text says certificate must be valid at signing instant\nfixture comment says valid through local filing day\n```\n\nDetermine whether the implementation or fixture encodes the wrong legal-time assumption and identify the precise boundary being tested.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"finish the forms API","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"Propose an architecture for public-record redaction, including detection, human review, immutable originals, publication versions, appeals, and audit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Add Akoma Ntoso parsing to `statutectl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Review excerpt:\n\n```diff\n async function downloadEvidence(req, res) {\n- const decision = await cases.canViewEvidence(req.user, req.params.caseId)\n- if (!decision.allowed) return res.sendStatus(403)\n- return streamFile(res, req.params.fileId)\n+ const url = await storage.sign(req.params.fileId, { expiresIn: '1h' })\n+ cases.canViewEvidence(req.user, req.params.caseId).catch(logger.warn)\n+ return res.redirect(url)\n }\n```\n\nReview authorization ordering, file-to-case binding, signed URL lifetime, audit, revocation, and asynchronous checking. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Schreibe eine kurze Referenz für die bestehenden Antragsstatus und ihre Auswirkungen auf Bearbeitung und Fristen. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"boundary","lang":"de"} -{"prompt":"Build the desktop document-comparison view with synchronized pages, text diffs, moved clauses, annotations, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Review how official receipts are generated and verified, then turn the findings into an integrator guide with examples.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.61,"slice":"mixed","lang":"en"} -{"prompt":"Set the draft autosave interval to 20s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Benenne `CaseCtx` repositoryweit in `CaseContext` um; JSON-Felder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"de"} -{"prompt":"Consolidate party-name normalization across intake and docket search without changing results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Diagnose the duplicated filing receipt","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"Explain how the rules engine chooses the policy version for applications submitted before an effective-date change.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Create API documentation for the existing filing-status endpoint, including transitions, timestamps, receipts, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"en"} -{"prompt":"Plan a migration from nightly docket exports to an event-driven public feed, covering corrections, redactions, ordering, replay, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"core","lang":"en"} -{"prompt":"Product ticket:\n\n```text\nScreen: public case search\nFields: case number, party name, filing date range, case type, status\nResults show public title, court, latest activity, and access restrictions\nSome names are partially redacted\nPagination must remain stable while new filings arrive\nNo-results state distinguishes invalid query from no matches\nSearch terms appear in the URL for sharing, except protected identifiers\nAccessibility: table has mobile card alternative and result count announces once\nAbuse controls may return a verification challenge\n```\n\nImplement the responsive search page and tests using the existing public API.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Implement `POST /v1/filings/{id}/withdraw` with state checks, authorization, receipt generation, and audit.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"Remove the extra period from the deadline label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"core","lang":"en"} -{"prompt":"Fix the clipped status chip and extract its duplicated inline padding into the shared token.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.35,"slice":"mixed","lang":"en"} -{"prompt":"Replace scattered filing booleans with one explicit lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Cambia `docRev` por `documentRevision` solo en `ContractState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"es"} -{"prompt":"Investigate why the portal briefly shows another applicant's saved address after account switching.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Summarize the current legal-hold workflow for compliance reviewers using code and tests as sources.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Develop a capacity roadmap for retaining 500 million filings and their revisions. Include storage tiers, search, integrity, public access, retention, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"core","lang":"en"} -{"prompt":"Implement idempotent court-notice ingestion with source-version ordering and correction links.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Create the Compose application checklist with sections, evidence status, deadlines, validation, and TalkBack support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Fix `jurisidction` in `rules.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} -{"prompt":"Merge duplicate address-normalization pipelines used by applications and notices while preserving results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Publication incident logs:\n\n```text\ncase=c_881 filing=f_991 revision=7\nredaction review approved revision=7 at=15:01:12\npublic index event published offset=77110\ncorrection request approved revision=8 at=15:01:13\nrevision=8 changes party display name and adds one redaction\npublic index consumer applies revision=8 offset=77111\nretry queue later delivers revision=7 offset=77092\nexternal versioning disabled for retry consumer\npublic document reverts to revision=7 for 18 minutes\n```\n\nDetermine how the stale retry overwrites a newer public revision and which version-precedence guarantee is missing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Rename `submision_id` to `submission_id` in the unreleased migration.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"en"} -{"prompt":"Assess whether public docket search permits inference of sealed cases through counts, timing, or error differences. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Restructure the filing SDK into forms, uploads, submissions, receipts, and status, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} +{"prompt":"Explain how `ClauseMatcher` relocates annotations between contract revisions and when it marks them orphaned. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Launch notes for clerks:\n\n```text\nFeature: filing correction requests\nA filer may request correction of metadata after acceptance\nEligible fields: party display name, internal reference, document description\nFiled document bytes and submission time cannot change\nClerk approves, partially approves, or denies the request\nApproved changes create a new metadata revision and preserve the original\nPublic docket reflects accepted corrections after publication\nNotifications contain case and request numbers but no document contents\nCorrection requests do not extend legal deadlines\n```\n\nTurn this into filer-facing release notes and a clerk procedure guide. Clearly distinguish metadata corrections from amended filings.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"Move the validation badge closer to the field label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Write an operator guide for replaying failed filing notifications without duplicating official receipts.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Implement contract-obligation endpoints with assignees, dates, status, and permissions, then document their lifecycle, examples, and errors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Map out a migration from free-form contract folders to matter-scoped document workspaces, including permissions, links, search, compatibility, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Rename `caseNo` to `caseNumber` in `FilingMapper.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Teach the filing worker to resume large attachment validation from durable page checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Polish the deadline summary card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump `pdfbox` to `3.0.5`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename `MasterDocket` to `PrimaryDocket` across services, schemas, events, and dashboards while preserving public fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Split `FilingProcessor` into intake, validation, signature, persistence, and receipt components without changing outcomes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implementation ticket:\n\n```text\nCIVIC-2207 — application evidence requests\nCaseworker requests one or more evidence categories with due date and explanation\nApplicant uploads files or marks category unavailable with reason\nEach upload receives malware scan, format validation, and immutable receipt\nCaseworker may accept, reject, or request replacement\nA replacement does not delete prior evidence\nDeadline extension requires separate authorization and audit event\nDuplicate mobile uploads are common\nNotifications must not name sensitive evidence categories on shared devices\n```\n\nImplement the state model, commands, upload idempotency, review flow, receipts, extension checks, audit, notifications, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Investigate why the Android filing app associates a scanned attachment with the previously opened form.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the obligation timeline UI and add a short legend for due, completed, waived, disputed, and superseded items.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Why does the docket service retain rejected filings for five years? Explain existing audit and retention behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Rewrite the local setup for running MinIO, ClamAV, OpenSearch, and the synthetic filing service.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"This signature-validation test fails only around midnight UTC:\n\n```text\nFAIL CertificatePolicyTest.accepts_on_final_valid_day\ncertificate not_before=2025-08-01T00:00:00Z not_after=2026-07-30T23:59:59Z\nfiling signed_at=2026-07-30T21:10:00-04:00\nvalidator normalizes signed_at=2026-07-31T01:10:00Z\nexpected valid based on filer local date=2026-07-30\nactual expired\npolicy text says certificate must be valid at signing instant\nfixture comment says valid through local filing day\n```\n\nDetermine whether the implementation or fixture encodes the wrong legal-time assumption and identify the precise boundary being tested.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"finish the forms API","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Propose an architecture for public-record redaction, including detection, human review, immutable originals, publication versions, appeals, and audit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add Akoma Ntoso parsing to `statutectl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Review excerpt:\n\n```diff\n async function downloadEvidence(req, res) {\n- const decision = await cases.canViewEvidence(req.user, req.params.caseId)\n- if (!decision.allowed) return res.sendStatus(403)\n- return streamFile(res, req.params.fileId)\n+ const url = await storage.sign(req.params.fileId, { expiresIn: '1h' })\n+ cases.canViewEvidence(req.user, req.params.caseId).catch(logger.warn)\n+ return res.redirect(url)\n }\n```\n\nReview authorization ordering, file-to-case binding, signed URL lifetime, audit, revocation, and asynchronous checking. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Schreibe eine kurze Referenz für die bestehenden Antragsstatus und ihre Auswirkungen auf Bearbeitung und Fristen. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"de"} +{"prompt":"Build the desktop document-comparison view with synchronized pages, text diffs, moved clauses, annotations, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Review how official receipts are generated and verified, then turn the findings into an integrator guide with examples.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Set the draft autosave interval to 20s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Benenne `CaseCtx` repositoryweit in `CaseContext` um; JSON-Felder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"de"} +{"prompt":"Consolidate party-name normalization across intake and docket search without changing results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Diagnose the duplicated filing receipt","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Explain how the rules engine chooses the policy version for applications submitted before an effective-date change.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Create API documentation for the existing filing-status endpoint, including transitions, timestamps, receipts, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Plan a migration from nightly docket exports to an event-driven public feed, covering corrections, redactions, ordering, replay, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Product ticket:\n\n```text\nScreen: public case search\nFields: case number, party name, filing date range, case type, status\nResults show public title, court, latest activity, and access restrictions\nSome names are partially redacted\nPagination must remain stable while new filings arrive\nNo-results state distinguishes invalid query from no matches\nSearch terms appear in the URL for sharing, except protected identifiers\nAccessibility: table has mobile card alternative and result count announces once\nAbuse controls may return a verification challenge\n```\n\nImplement the responsive search page and tests using the existing public API.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Implement `POST /v1/filings/{id}/withdraw` with state checks, authorization, receipt generation, and audit.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remove the extra period from the deadline label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fix the clipped status chip and extract its duplicated inline padding into the shared token.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Replace scattered filing booleans with one explicit lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Cambia `docRev` por `documentRevision` solo en `ContractState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"es"} +{"prompt":"Investigate why the portal briefly shows another applicant's saved address after account switching.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Summarize the current legal-hold workflow for compliance reviewers using code and tests as sources.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Develop a capacity roadmap for retaining 500 million filings and their revisions. Include storage tiers, search, integrity, public access, retention, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement idempotent court-notice ingestion with source-version ordering and correction links.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the Compose application checklist with sections, evidence status, deadlines, validation, and TalkBack support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Fix `jurisidction` in `rules.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Merge duplicate address-normalization pipelines used by applications and notices while preserving results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Publication incident logs:\n\n```text\ncase=c_881 filing=f_991 revision=7\nredaction review approved revision=7 at=15:01:12\npublic index event published offset=77110\ncorrection request approved revision=8 at=15:01:13\nrevision=8 changes party display name and adds one redaction\npublic index consumer applies revision=8 offset=77111\nretry queue later delivers revision=7 offset=77092\nexternal versioning disabled for retry consumer\npublic document reverts to revision=7 for 18 minutes\n```\n\nDetermine how the stale retry overwrites a newer public revision and which version-precedence guarantee is missing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Rename `submision_id` to `submission_id` in the unreleased migration.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Assess whether public docket search permits inference of sealed cases through counts, timing, or error differences. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Restructure the filing SDK into forms, uploads, submissions, receipts, and status, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Plan the retirement of email-based filing receipts, covering usage, delivery evidence, accessibility, communication, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Add immutable provenance chains to normalized statutory text.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Build the tablet hearing-calendar view with filters, conflicts, location, remote links, and accessible day navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"do the case page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.39,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `DocRef` with `DocumentReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why generated notices omit approved name corrections, implement the verified revision-selection fix, and add a clerk-facing note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.77,"slice":"mixed","lang":"en"} -{"prompt":"Why does the contract service retain two previous rendered PDFs? Explain current rollback and verification behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.47,"slice":"boundary","lang":"en"} -{"prompt":"Track down the memory leak in OCR workers after processing scanned exhibits.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Write release notes for reusable filing-party profiles, including privacy, defaults, editing, and old-client behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.36,"slice":"core","lang":"en"} -{"prompt":"Rules migration notes:\n\n```text\nCurrent eligibility policy is embedded in Java code\nTarget policies are signed YAML bundles with effective dates\nDecisions must be reproducible for seven years\nRules reference external income thresholds updated annually\nCaseworkers need human-readable explanations\nEmergency policy correction may apply retroactively only through explicit re-evaluation\nOld applications must retain their original policy version\nPolicy publication requires legal and engineering approval\nRollback cannot erase decisions already issued\n```\n\nProduce an implementation-free migration plan covering bundle format, dependencies, approvals, simulation, effective dates, reproducibility, re-evaluation, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"pasted-context","lang":"en"} -{"prompt":"Give the form summary clearer grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.32,"slice":"core","lang":"en"} -{"prompt":"Turn the current electronic-signature behavior into filer documentation, then review whether its identity and validation claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Outline a phased architecture for moving document search from Solr to OpenSearch, without implementing indexing or queries.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.84,"slice":"boundary","lang":"en"} -{"prompt":"Implement version-aware contract obligation history with supersession links and snapshots.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Create an operator guide for diagnosing filings stuck in signature validation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} -{"prompt":"Move jurisdiction resolution out of `RulesController` while preserving policy choices.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Investigate why revoked external collaborators retain access through one document preview cache.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"Add generation-fenced template publication with preview and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Set the draft retention period to 90 days","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Create the responsive filing-history view with revisions, receipts, corrections, downloads, and accessible chronology.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Corrige apenas `evidance` para `evidence` no novo título.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"pt"} -{"prompt":"Review the attachment-preview endpoint for SSRF, malicious PDFs, stale authorization, range abuse, and public-cache leakage.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"Implement case-decision history and write its API guide. Include policy versions, explanations, appeals, pagination, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Design a migration from agency-specific applicant IDs to a federated identity graph, including confidence, privacy, merges, splits, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Add resumable evidence uploads with per-part checksums and malware-scan state.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Build the desktop policy-simulator with sample facts, decision trace, version comparison, and export.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"continue the filing bug","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.54,"slice":"vague-eval","lang":"en"} -{"prompt":"Extract deadline calculation into one shared module while preserving jurisdiction-specific dates.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why appeal deadlines use the wrong holiday calendar, implement the verified jurisdiction fix, and update clerk documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.78,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed AI clause-suggestion feature for privilege, retention, prompt injection, attribution, and hallucinated obligations.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"boundary","lang":"en"} -{"prompt":"Find why one filing worker retries a permanently malformed signature forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Draft a migration guide for agencies moving from CSV notices to the notices API.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"Accessibility incident excerpt:\n\n```text\nform=benefits-renewal version=81\nquestion q_44 condition=`household_size > 1`\nscreen reader user changes household_size from 1 to 2\nstate engine inserts q_44 visually after current field\nfocus remains on hidden DOM placeholder\naria-live announces 'one question added'\nTab moves to footer instead of q_44\nvalidation on submit reports q_44 required\nautomated tests check DOM presence but not focus sequence\n```\n\nDetermine why dynamic insertion breaks keyboard order and how the placeholder and focus-management assumptions caused an inaccessible required field.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"pasted-context","lang":"en"} -{"prompt":"Add revision text below the document title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.24,"slice":"core","lang":"en"} -{"prompt":"Restructure the document-rendering pipeline and document its renderer interface. Preserve PDFs while separating data, templates, layout, signing, and storage.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Architect a multi-region electronic-filing platform with jurisdiction ownership, receipts, deadlines, public access, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed filing receipts with document digests and policy version.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new application form, including schema, conditions, validation, accessibility, and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Consolidate docket-status formatting across portal and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Investigate why withdrawn filings remain in public autocomplete.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional case-transfer support with jurisdiction checks and immutable history.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Pin Tesseract to `5.5.1`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Build the mobile evidence-upload flow with category selection, scanning, progress, validation, retry, and receipts.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Remplace `Submision` par `Submission` uniquement dans le nouveau libellé.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"fr"} -{"prompt":"Inspect the public-document download path for sealed-content leakage, stale redactions, identifier enumeration, and cache confusion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Implement filing-receipt verification and write its integration documentation. Include digests, certificates, timestamps, errors, examples, and trust roots.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Develop a roadmap for replacing handwritten redaction rules with reviewed automated detection, including evaluation, human approval, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"core","lang":"en"} -{"prompt":"Add bounded event replay for application-case projections with checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Create the responsive contract-obligation dashboard with owners, dates, status, filters, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"fix the deadline thing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `FilingEvt` with `FilingEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why accepted correction requests do not update search results, implement the verified indexing fix, and update filer documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.74,"slice":"mixed","lang":"en"} -{"prompt":"Why does the form engine retain three previous schema versions? Explain current draft recovery and compatibility behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.47,"slice":"boundary","lang":"en"} -{"prompt":"Track down occasional missing text layers in OCR-generated PDFs.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Write a troubleshooting guide for rejected filings, covering validation, signatures, attachments, deadlines, and payment.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Security review packet:\n\n```text\nFeature: shareable case-document link\nCreator: authorized caseworker\nRecipient: external counsel without platform account\nLink grants read-only access to selected documents for seven days\nRecipient verifies email through one-time code\nCreator may revoke early\nDownloaded files receive visible recipient watermark\nLink token appears in URL query parameter\nAudit records opens and downloads\nForwarded email permits another person to complete verification if they control mailbox\nSealed documents are excluded by current UI filter\n```\n\nReview link leakage, recipient binding, forwarding, token placement, sealed-document enforcement, revocation, watermarks, and audit. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a loading state to the filing cards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Plan and implement jurisdiction-defined retention policies. First define precedence, holds, public copies, evidence, exports, deletion proof, and rollout; then add policy storage and enforcement.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.94,"slice":"mixed","lang":"en"} -{"prompt":"Outline an architecture for cross-agency case referrals with identity, consent, evidence transfer, status, audit, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"boundary","lang":"en"} -{"prompt":"Implement snapshot-consistent docket exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Escribe una guía para integrar formularios electrónicos, con esquemas, validación, firmas, recibos y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} -{"prompt":"Move filing-fee calculation out of the submission handler without changing amounts.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Investigate why the Android app loses draft attachments after process death.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.61,"slice":"boundary","lang":"en"} -{"prompt":"Add atomic policy-bundle publication with simulation, approval, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Remove the obsolete `legacy_receipt` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"core","lang":"en"} -{"prompt":"Build the public document viewer with page thumbnails, redaction markers, downloads, citations, and accessible reading order.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"`Applicaton status` を `Application status` に直して。新しい英語見出しだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"ja"} -{"prompt":"Review the policy-simulation endpoint for sensitive fact leakage, unauthorized versions, expensive inputs, and misleading explanations.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Implement contract-revision history and write its API guide. Include authors, diffs, signatures, publication, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Plan a disaster-recovery strategy for electronic filing, including documents, receipts, policies, keys, public indexes, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Add content-hash deduplication to uploaded evidence with case-scoped ownership.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} +{"prompt":"Add immutable provenance chains to normalized statutory text.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Build the tablet hearing-calendar view with filters, conflicts, location, remote links, and accessible day navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"do the case page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `DocRef` with `DocumentReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose why generated notices omit approved name corrections, implement the verified revision-selection fix, and add a clerk-facing note.","purpose":"debugging","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Why does the contract service retain two previous rendered PDFs? Explain current rollback and verification behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down the memory leak in OCR workers after processing scanned exhibits.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Write release notes for reusable filing-party profiles, including privacy, defaults, editing, and old-client behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Rules migration notes:\n\n```text\nCurrent eligibility policy is embedded in Java code\nTarget policies are signed YAML bundles with effective dates\nDecisions must be reproducible for seven years\nRules reference external income thresholds updated annually\nCaseworkers need human-readable explanations\nEmergency policy correction may apply retroactively only through explicit re-evaluation\nOld applications must retain their original policy version\nPolicy publication requires legal and engineering approval\nRollback cannot erase decisions already issued\n```\n\nProduce an implementation-free migration plan covering bundle format, dependencies, approvals, simulation, effective dates, reproducibility, re-evaluation, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Give the form summary clearer grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Turn the current electronic-signature behavior into filer documentation, then review whether its identity and validation claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Outline a phased architecture for moving document search from Solr to OpenSearch, without implementing indexing or queries.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement version-aware contract obligation history with supersession links and snapshots.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create an operator guide for diagnosing filings stuck in signature validation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Move jurisdiction resolution out of `RulesController` while preserving policy choices.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why revoked external collaborators retain access through one document preview cache.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add generation-fenced template publication with preview and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Set the draft retention period to 90 days","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Create the responsive filing-history view with revisions, receipts, corrections, downloads, and accessible chronology.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Corrige apenas `evidance` para `evidence` no novo título.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"pt"} +{"prompt":"Review the attachment-preview endpoint for SSRF, malicious PDFs, stale authorization, range abuse, and public-cache leakage.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement case-decision history and write its API guide. Include policy versions, explanations, appeals, pagination, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Design a migration from agency-specific applicant IDs to a federated identity graph, including confidence, privacy, merges, splits, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add resumable evidence uploads with per-part checksums and malware-scan state.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Build the desktop policy-simulator with sample facts, decision trace, version comparison, and export.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Extract deadline calculation into one shared module while preserving jurisdiction-specific dates.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why appeal deadlines use the wrong holiday calendar, implement the verified jurisdiction fix, and update clerk documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed AI clause-suggestion feature for privilege, retention, prompt injection, attribution, and hallucinated obligations.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why one filing worker retries a permanently malformed signature forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft a migration guide for agencies moving from CSV notices to the notices API.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Accessibility incident excerpt:\n\n```text\nform=benefits-renewal version=81\nquestion q_44 condition=`household_size > 1`\nscreen reader user changes household_size from 1 to 2\nstate engine inserts q_44 visually after current field\nfocus remains on hidden DOM placeholder\naria-live announces 'one question added'\nTab moves to footer instead of q_44\nvalidation on submit reports q_44 required\nautomated tests check DOM presence but not focus sequence\n```\n\nDetermine why dynamic insertion breaks keyboard order and how the placeholder and focus-management assumptions caused an inaccessible required field.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Add revision text below the document title","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Restructure the document-rendering pipeline and document its renderer interface. Preserve PDFs while separating data, templates, layout, signing, and storage.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Architect a multi-region electronic-filing platform with jurisdiction ownership, receipts, deadlines, public access, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement signed filing receipts with document digests and policy version.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new application form, including schema, conditions, validation, accessibility, and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Consolidate docket-status formatting across portal and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why withdrawn filings remain in public autocomplete.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Add transactional case-transfer support with jurisdiction checks and immutable history.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Pin Tesseract to `5.5.1`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile evidence-upload flow with category selection, scanning, progress, validation, retry, and receipts.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remplace `Submision` par `Submission` uniquement dans le nouveau libellé.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"fr"} +{"prompt":"Inspect the public-document download path for sealed-content leakage, stale redactions, identifier enumeration, and cache confusion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement filing-receipt verification and write its integration documentation. Include digests, certificates, timestamps, errors, examples, and trust roots.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Develop a roadmap for replacing handwritten redaction rules with reviewed automated detection, including evaluation, human approval, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add bounded event replay for application-case projections with checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create the responsive contract-obligation dashboard with owners, dates, status, filters, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"fix the deadline thing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `FilingEvt` with `FilingEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose why accepted correction requests do not update search results, implement the verified indexing fix, and update filer documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Why does the form engine retain three previous schema versions? Explain current draft recovery and compatibility behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down occasional missing text layers in OCR-generated PDFs.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Write a troubleshooting guide for rejected filings, covering validation, signatures, attachments, deadlines, and payment.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Security review packet:\n\n```text\nFeature: shareable case-document link\nCreator: authorized caseworker\nRecipient: external counsel without platform account\nLink grants read-only access to selected documents for seven days\nRecipient verifies email through one-time code\nCreator may revoke early\nDownloaded files receive visible recipient watermark\nLink token appears in URL query parameter\nAudit records opens and downloads\nForwarded email permits another person to complete verification if they control mailbox\nSealed documents are excluded by current UI filter\n```\n\nReview link leakage, recipient binding, forwarding, token placement, sealed-document enforcement, revocation, watermarks, and audit. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add a loading state to the filing cards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Plan and implement jurisdiction-defined retention policies. First define precedence, holds, public copies, evidence, exports, deletion proof, and rollout; then add policy storage and enforcement.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Outline an architecture for cross-agency case referrals with identity, consent, evidence transfer, status, audit, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement snapshot-consistent docket exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Escribe una guía para integrar formularios electrónicos, con esquemas, validación, firmas, recibos y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"es"} +{"prompt":"Move filing-fee calculation out of the submission handler without changing amounts.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Investigate why the Android app loses draft attachments after process death.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add atomic policy-bundle publication with simulation, approval, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Remove the obsolete `legacy_receipt` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Build the public document viewer with page thumbnails, redaction markers, downloads, citations, and accessible reading order.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"`Applicaton status` を `Application status` に直して。新しい英語見出しだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"ja"} +{"prompt":"Review the policy-simulation endpoint for sensitive fact leakage, unauthorized versions, expensive inputs, and misleading explanations.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement contract-revision history and write its API guide. Include authors, diffs, signatures, publication, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan a disaster-recovery strategy for electronic filing, including documents, receipts, policies, keys, public indexes, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add content-hash deduplication to uploaded evidence with case-scoped ownership.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Create the desktop redaction-review workspace with detections, page view, reasons, history, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"continue the form cleanup","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"Rename `PolicyVer` to `PolicyVersion` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why withdrawn applications still trigger evidence reminders, implement the verified scheduling fix, and update help documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.74,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed contract-search cache for matter isolation, privilege, deletion, stale permissions, and regional storage.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","lang":"en"} -{"prompt":"Find why one OCR worker retries an encrypted PDF forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Draft a support guide for recovering an interrupted electronic filing.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} +{"prompt":"Rename `PolicyVer` to `PolicyVersion` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why withdrawn applications still trigger evidence reminders, implement the verified scheduling fix, and update help documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed contract-search cache for matter isolation, privilege, deletion, stale permissions, and regional storage.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why one OCR worker retries an encrypted PDF forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft a support guide for recovering an interrupted electronic filing.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Projection failure output:\n\n```text\napplication=a_441 state=submitted version=18\nappeal event version=19 committed offset=88120\nprojection updates state=appealed and writes public summary\ncheckpoint write fails due transaction timeout\nworker restarts from offset=88119\nreplays appeal against state=appealed\nstate machine rejects transition submitted->appealed precondition because source snapshot already advanced\npartition stops and later notices are delayed\n```\n\nDetermine how projection state and checkpoint were committed separately and why replay cannot recognize the already-applied appeal.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Add filing date below the case title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Restructure the policy evaluator and document its rule interface. Preserve decisions while separating facts, applicability, evaluation, explanation, and audit.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.82,"slice":"mixed","lang":"en"} -{"prompt":"Architect a multi-region public-record platform with agency ownership, redaction, publication, search, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"boundary","lang":"en"} +{"prompt":"Add filing date below the case title","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Restructure the policy evaluator and document its rule interface. Preserve decisions while separating facts, applicability, evaluation, explanation, and audit.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Architect a multi-region public-record platform with agency ownership, redaction, publication, search, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Implement signed document-publication manifests with source revision and redaction digest.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new filing type, including schema, validation, fees, signatures, receipts, and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"Consolidate official-date formatting across portal and notices without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Investigate why expired external links remain visible in recent-document lists.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional matter transfer with permission remapping and immutable history.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Set the OCR page limit to 2000","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Build the mobile application-status screen with timeline, requests, deadlines, documents, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"把 `Filling received` 改成 `Filing received`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"zh"} -{"prompt":"Inspect the filing-package parser for path traversal, XML entity expansion, oversized archives, tenant confusion, and signature bypass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Implement public-record publication history and write its API documentation. Include revisions, redactions, withdrawals, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Design a learning-progress architecture for courses, assignments, competencies, attempts, feedback, accommodations, and transferred enrollments. Cover event history, grading revisions, tenant isolation, analytics, privacy, offline clients, migration from mutable grade rows, and rollout milestones. Deliver an RFC only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"core","lang":"en"} -{"prompt":"Before implementing adaptive practice, outline the learner model, item selection, mastery updates, cold start, teacher controls, explainability, privacy, evaluation, and phased launch.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"boundary","lang":"en"} -{"prompt":"Add attempt pagination to `/v2/assignments`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Grade synchronization logs:\n\n```text\ncourse=c_881 assignment=a_41 student=s_992\nLMS submission attempt=3 score=18/20 updated_at=14:01:08Z\nplatform grade event version=7 score=18 received=14:01:10Z\nteacher overrides score=19 at=14:01:12Z source=platform\nLMS retry delivers attempt=3 score=18 updated_at=14:01:08Z at=14:01:19Z\nconnector compares received_at, not source updated_at\nplatform grade version=9 score=18\nteacher override history remains but current grade regresses\n```\n\nDetermine why the delayed LMS retry overwrites a newer manual grade and whether source precedence or timestamp comparison is missing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Build the SwiftUI assignment-detail screen with instructions, attachments, due date, submission state, feedback, rubric, and VoiceOver support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Plan and implement an assessment-delivery service for timed exams. Begin with a design covering item versions, accommodations, autosave, reconnect, device changes, integrity signals, submission finality, scoring, audit replay, and rollout. Then add session APIs, durable responses, timers, submission, and conformance tests. Treat fairness and failure semantics as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.97,"slice":"mixed","lang":"en"} -{"prompt":"Set `MAX_QUIZ_ATTEMPTS` to 5","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Extract duplicated rubric-score validation from teacher and import flows while preserving outcomes and errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Implement `/internal/content/versions` with active release, draft count, dependency status, and validation failures.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"make the course page inspiring","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.42,"slice":"vague-eval","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new filing type, including schema, validation, fees, signatures, receipts, and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Consolidate official-date formatting across portal and notices without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why expired external links remain visible in recent-document lists.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add transactional matter transfer with permission remapping and immutable history.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Set the OCR page limit to 2000","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile application-status screen with timeline, requests, deadlines, documents, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"把 `Filling received` 改成 `Filing received`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"zh"} +{"prompt":"Inspect the filing-package parser for path traversal, XML entity expansion, oversized archives, tenant confusion, and signature bypass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement public-record publication history and write its API documentation. Include revisions, redactions, withdrawals, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Design a learning-progress architecture for courses, assignments, competencies, attempts, feedback, accommodations, and transferred enrollments. Cover event history, grading revisions, tenant isolation, analytics, privacy, offline clients, migration from mutable grade rows, and rollout milestones. Deliver an RFC only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Before implementing adaptive practice, outline the learner model, item selection, mastery updates, cold start, teacher controls, explainability, privacy, evaluation, and phased launch.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add attempt pagination to `/v2/assignments`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Grade synchronization logs:\n\n```text\ncourse=c_881 assignment=a_41 student=s_992\nLMS submission attempt=3 score=18/20 updated_at=14:01:08Z\nplatform grade event version=7 score=18 received=14:01:10Z\nteacher overrides score=19 at=14:01:12Z source=platform\nLMS retry delivers attempt=3 score=18 updated_at=14:01:08Z at=14:01:19Z\nconnector compares received_at, not source updated_at\nplatform grade version=9 score=18\nteacher override history remains but current grade regresses\n```\n\nDetermine why the delayed LMS retry overwrites a newer manual grade and whether source precedence or timestamp comparison is missing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"Build the SwiftUI assignment-detail screen with instructions, attachments, due date, submission state, feedback, rubric, and VoiceOver support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Plan and implement an assessment-delivery service for timed exams. Begin with a design covering item versions, accommodations, autosave, reconnect, device changes, integrity signals, submission finality, scoring, audit replay, and rollout. Then add session APIs, durable responses, timers, submission, and conformance tests. Treat fairness and failure semantics as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":1,"slice":"mixed","lang":"en"} +{"prompt":"Set `MAX_QUIZ_ATTEMPTS` to 5","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Extract duplicated rubric-score validation from teacher and import flows while preserving outcomes and errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement `/internal/content/versions` with active release, draft count, dependency status, and validation failures.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"make the course page inspiring","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"Find why the Android exam timer loses several minutes after the device wakes from sleep.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Explain how `MasteryUpdater` treats skipped, hinted, correct, and partially correct responses. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Instructor launch notes:\n\n```text\nFeature: assignment extensions\nInstructor grants a learner or section a new due date\nExtensions do not change the original course due date\nA learner-specific extension overrides a section extension\nLate status recalculates immediately\nExisting submissions remain unchanged\nNotifications show the new date but not the reason\nExtensions can be revoked unless the original due date has passed and work was submitted under the extension\nGradebook exports include effective due date\n```\n\nTurn this into instructor release notes and a help article with precedence examples and revocation limitations.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.46,"slice":"pasted-context","lang":"en"} -{"prompt":"Move the progress ring away from the lesson title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.13,"slice":"boundary","lang":"en"} +{"prompt":"Explain how `MasteryUpdater` treats skipped, hinted, correct, and partially correct responses. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Instructor launch notes:\n\n```text\nFeature: assignment extensions\nInstructor grants a learner or section a new due date\nExtensions do not change the original course due date\nA learner-specific extension overrides a section extension\nLate status recalculates immediately\nExisting submissions remain unchanged\nNotifications show the new date but not the reason\nExtensions can be revoked unless the original due date has passed and work was submitted under the extension\nGradebook exports include effective due date\n```\n\nTurn this into instructor release notes and a help article with precedence examples and revocation limitations.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"Move the progress ring away from the lesson title","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"Write an operator guide for replaying failed roster events without duplicating enrollments.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Implement course-completion endpoints with criteria, timestamps, revocation, and authorization, then document lifecycle, examples, and errors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Map out a migration from course-owned media copies to a shared content library, including permissions, versioning, links, analytics, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"Rename `learnerNo` to `learnerNumber` in `RosterMapper.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"en"} -{"prompt":"Teach the roster importer to process OneRoster CSV archives with row-level errors and resumable batches.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Polish the lesson completion card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.27,"slice":"core","lang":"en"} -{"prompt":"Bump `moodle-client` to `1.8.3`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Rename `MasterCourse` to `PrimaryCourse` across services, events, analytics, and tests while preserving public fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.64,"slice":"boundary","lang":"en"} -{"prompt":"Split `AssessmentService` into session, response, timing, scoring, and publication components without changing behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Implementation ticket:\n\n```text\nEDU-4410 — rubric-based grading\nRubric has ordered criteria with levels and optional free-text feedback\nEach assignment pins a rubric version at publication\nGraders may save drafts and publish a final evaluation\nTwo graders can work concurrently; publishing requires current evaluation version\nScore may be derived from levels or manually overridden with reason\nRegrading creates a new immutable evaluation revision\nLearner notifications occur only after publication\nExports include criterion scores, feedback, override, and rubric version\n```\n\nImplement models, commands, optimistic concurrency, scoring, revisions, notifications, exports, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.85,"slice":"pasted-context","lang":"en"} -{"prompt":"Investigate why the iPad whiteboard submits a blank image after switching apps during upload.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Create the rubric-grading UI and add a concise guide for levels, draft feedback, overrides, publishing, and regrading.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Why does the analytics service retain withdrawn quiz responses in aggregate snapshots? Explain current audit behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.47,"slice":"core","lang":"en"} -{"prompt":"Rewrite the local setup for running Moodle, MinIO, Kafka, and the synthetic student generator.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"This accommodation test fails around daylight-saving changes:\n\n```text\nexam opens=2026-10-25T01:30:00 Europe/Paris\nstandard duration=60m learner multiplier=1.5\nexpected closes=03:00 local\nactual closes=02:00+01:00\nservice adds 90 minutes to instant\nfixture adds 90 minutes to wall clock\nlocal time 02:00 occurs twice\npolicy text says elapsed testing time, excluding approved pauses\n```\n\nDetermine whether the implementation or fixture uses the wrong time model and explain the ambiguous local-time expectation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"finish the grade API","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"Propose an architecture for privacy-safe learning analytics, including consent, aggregation, identity, retention, deletion, research exports, and teacher access.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"core","lang":"en"} -{"prompt":"Add QTI 3.0 item parsing to `assessmentctl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Pull request excerpt:\n\n```diff\n async function getSubmission(req) {\n- const enrollment = await courses.requireEnrollment(req.user.id, req.params.courseId)\n- return submissions.load(req.params.submissionId, enrollment)\n+ const submission = await submissions.load(req.params.submissionId)\n+ courses.requireEnrollment(req.user.id, submission.courseId).catch(logger.warn)\n+ return submission\n }\n```\n\nThe author says enrollment checks should not delay feedback pages. Review authorization ordering, guessed IDs, revoked enrollment, audit, and asynchronous failure. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"pasted-context","lang":"en"} -{"prompt":"Schreibe eine kurze Referenz für die bestehenden Einreichungsstatus und ihre Auswirkungen auf Bearbeitung und Benotung. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"boundary","lang":"de"} -{"prompt":"Build the desktop course-outline editor with nested modules, drag reorder, prerequisites, publishing, undo, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Review how final grades are calculated and rounded, then turn the findings into an instructor guide with examples.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.61,"slice":"mixed","lang":"en"} -{"prompt":"Set the autosave interval to 10s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Benenne `GradeCtx` repositoryweit in `GradeContext` um; JSON-Felder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"de"} -{"prompt":"Consolidate learner-name formatting across gradebook and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"core","lang":"en"} -{"prompt":"Diagnose the duplicate course notification","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Explain how the content service pins embedded resources when a course version is published.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Create API documentation for the existing assignment-extension endpoint, including precedence, revocation, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"en"} -{"prompt":"Plan a migration from nightly SIS roster files to event-driven enrollment updates, covering ordering, corrections, replay, validation, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"core","lang":"en"} -{"prompt":"Mobile product ticket:\n\n```text\nScreen: learner course home\nHeader: course title, instructor, overall progress\nSections: continue learning, upcoming work, recent feedback, announcements\nUpcoming items use learner-specific due dates and accommodations\nOffline mode shows downloaded lessons and last known deadlines with stale indicator\nProgress updates may arrive out of order from multiple devices\nAccessibility: heading structure, readable progress text, no color-only urgency\nPerformance: first useful content under 1.5s from warm cache\n```\n\nImplement the responsive Compose screen and UI tests using current course APIs.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"pasted-context","lang":"en"} -{"prompt":"Implement `POST /v1/submissions/{id}/reopen` with state validation, authorization, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Remove the extra comma from the score label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"core","lang":"en"} -{"prompt":"Fix the clipped late badge and extract its duplicated offset into shared gradebook styles.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.35,"slice":"mixed","lang":"en"} -{"prompt":"Replace scattered submission booleans with one explicit lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Cambia `quizRev` por `quizRevision` solo en `AssessmentState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"es"} -{"prompt":"Investigate why the teacher portal briefly displays another section's students after switching courses.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Summarize the current accommodation workflow for accessibility and compliance reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"Develop a capacity roadmap for serving 25 million concurrent learners during national exams. Include sessions, autosave, timing, queues, scoring, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"core","lang":"en"} -{"prompt":"Implement idempotent attendance ingestion with correction versions and source provenance.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Create the SwiftUI feedback viewer with inline annotations, rubric, audio comments, revisions, and VoiceOver support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Fix `assigment` in `content.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} -{"prompt":"Merge duplicate due-date resolution used by notifications and gradebook while preserving effective dates.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Exam incident logs:\n\n```text\nsession=e_881 learner=s_92 attempt=1\nclient autosave response q_41 version=18 at=12:01:02\nnetwork offline\nclient edits q_41 locally version_base=18\nproctor invalidates q_41 due item correction, replacement=q_77\nnetwork reconnect sends q_41 response with client_op=991\nserver maps invalidated item to no active response slot and returns 409\nclient retry queue blocks later answers behind op=991\nsubmission timer expires with six unsynced responses\n```\n\nDetermine why one permanently conflicted response blocks unrelated autosaves and whether queue ordering or item-replacement mapping should resolve it.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.83,"slice":"pasted-context","lang":"en"} -{"prompt":"Rename `enrolment_id` to `enrollment_id` in the unreleased migration.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"en"} -{"prompt":"Assess whether course analytics can reveal an individual learner through small cohorts and filter combinations. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Restructure the learning SDK into courses, assignments, submissions, grades, and shared models, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.75,"slice":"mixed","lang":"en"} -{"prompt":"Plan the retirement of legacy SCORM playback, covering content inventory, tracking parity, conversion, communication, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.84,"slice":"core","lang":"en"} -{"prompt":"Add immutable provenance chains to imported grade records.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Build the tablet classroom dashboard with attendance, live activities, help requests, groups, and accessible layouts.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"do the gradebook","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `CourseRef` with `CourseReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why exported transcripts omit approved grade changes, implement the verified snapshot fix, and add a registrar-facing note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"Why does the content service retain two previous published course versions? Explain current rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.46,"slice":"boundary","lang":"en"} -{"prompt":"Track down the memory leak in document preview workers after rendering large slide decks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Write release notes for anonymous peer review, including assignment, identity protection, moderation, and deadlines.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"core","lang":"en"} -{"prompt":"Adaptive practice notes:\n\n```text\nSkill model: Bayesian knowledge tracing per learner and competency\nItems can cover multiple competencies\nTeacher may exclude items or lock difficulty range\nHints reduce evidence weight\nRepeated attempts on same item should not inflate mastery\nCold start uses course-level prior\nLearners need a simple explanation of why an item was selected\nModel updates may arrive from offline devices out of order\nNo sensitive demographic attributes may enter selection\n```\n\nProduce an implementation-free design and rollout plan covering updates, item selection, controls, explanations, offline ordering, evaluation, and privacy.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"Give the module list clearer progress grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.32,"slice":"core","lang":"en"} -{"prompt":"Turn the current late-submission behavior into learner documentation, then review whether timing and grace-period claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.67,"slice":"mixed","lang":"en"} -{"prompt":"Outline a phased architecture for moving analytics from nightly warehouse jobs to streaming projections, without implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.85,"slice":"boundary","lang":"en"} -{"prompt":"Implement version-aware grade history with correction links and publication snapshots.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Create an operator guide for diagnosing roster synchronization delays.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"Move course-progress calculation out of `CourseController` while preserving percentages.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Investigate why revoked guardian access remains active in one regional portal.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.69,"slice":"boundary","lang":"en"} -{"prompt":"Add generation-fenced rubric publication with preview and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Set the discussion edit window to 15 minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Create the responsive learner-progress dashboard with competencies, trends, evidence, filters, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Corrige apenas `learner progres` para `learner progress` no novo título.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"pt"} -{"prompt":"Review the assignment-upload endpoint for tenant spoofing, malicious files, quota bypass, stale enrollment, and partial failures.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Implement assessment-session history and write its API guide. Include timing, accommodations, responses, submission, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Design a migration from institution-specific learner IDs to a federated identity graph, including privacy, transfers, merges, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"core","lang":"en"} -{"prompt":"Add resumable course-package imports with checksums and row-level validation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Build the desktop item-bank editor with search, metadata, versions, preview, bulk actions, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"continue the scoring bug","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"Extract academic-term resolution into one shared module while preserving enrollment behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why reminder emails use the original due date after an extension, implement the verified cache fix, and update instructor docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.74,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed AI feedback assistant for student privacy, prompt injection, rubric fidelity, bias, attribution, and teacher oversight.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"boundary","lang":"en"} -{"prompt":"Find why one roster partition retries a permanently invalid record forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Draft a migration guide for partners moving from CSV rosters to OneRoster.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"core","lang":"en"} -{"prompt":"Analytics pipeline incident:\n\n```text\njob=course-completion date=2026-07-29\nsource events=441,992\nprojection output completions=18,441\nlate event learner=s_88 lesson=l_12 completed_at=2026-07-28\nwatermark=2026-07-29T00:00Z\nlate event routed to correction topic\ncorrection consumer updates learner progress but not course completion aggregate\nlearner UI shows 100%; institutional report shows 92%\nquality check compares total learners, not cross-projection consistency\n```\n\nDetermine why correction handling updates only one projection and why existing quality checks miss the contradictory completion states.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Add evidence count below the competency","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.24,"slice":"core","lang":"en"} -{"prompt":"Restructure the scoring pipeline and document its item interface. Preserve scores while separating responses, rules, partial credit, aggregation, and explanation.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"Architect a multi-region assessment platform with session ownership, timing, autosave, submission, scoring, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed grade-export manifests with course version and record digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new question type, including rendering, scoring, accessibility, fixtures, and analytics.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Consolidate course-date formatting across portal and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Investigate why deleted discussion posts remain in course search.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.61,"slice":"boundary","lang":"en"} +{"prompt":"Implement course-completion endpoints with criteria, timestamps, revocation, and authorization, then document lifecycle, examples, and errors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Map out a migration from course-owned media copies to a shared content library, including permissions, versioning, links, analytics, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Rename `learnerNo` to `learnerNumber` in `RosterMapper.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Teach the roster importer to process OneRoster CSV archives with row-level errors and resumable batches.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Polish the lesson completion card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump `moodle-client` to `1.8.3`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename `MasterCourse` to `PrimaryCourse` across services, events, analytics, and tests while preserving public fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Split `AssessmentService` into session, response, timing, scoring, and publication components without changing behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implementation ticket:\n\n```text\nEDU-4410 — rubric-based grading\nRubric has ordered criteria with levels and optional free-text feedback\nEach assignment pins a rubric version at publication\nGraders may save drafts and publish a final evaluation\nTwo graders can work concurrently; publishing requires current evaluation version\nScore may be derived from levels or manually overridden with reason\nRegrading creates a new immutable evaluation revision\nLearner notifications occur only after publication\nExports include criterion scores, feedback, override, and rubric version\n```\n\nImplement models, commands, optimistic concurrency, scoring, revisions, notifications, exports, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Investigate why the iPad whiteboard submits a blank image after switching apps during upload.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the rubric-grading UI and add a concise guide for levels, draft feedback, overrides, publishing, and regrading.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the analytics service retain withdrawn quiz responses in aggregate snapshots? Explain current audit behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Rewrite the local setup for running Moodle, MinIO, Kafka, and the synthetic student generator.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"This accommodation test fails around daylight-saving changes:\n\n```text\nexam opens=2026-10-25T01:30:00 Europe/Paris\nstandard duration=60m learner multiplier=1.5\nexpected closes=03:00 local\nactual closes=02:00+01:00\nservice adds 90 minutes to instant\nfixture adds 90 minutes to wall clock\nlocal time 02:00 occurs twice\npolicy text says elapsed testing time, excluding approved pauses\n```\n\nDetermine whether the implementation or fixture uses the wrong time model and explain the ambiguous local-time expectation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"finish the grade API","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Propose an architecture for privacy-safe learning analytics, including consent, aggregation, identity, retention, deletion, research exports, and teacher access.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add QTI 3.0 item parsing to `assessmentctl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Pull request excerpt:\n\n```diff\n async function getSubmission(req) {\n- const enrollment = await courses.requireEnrollment(req.user.id, req.params.courseId)\n- return submissions.load(req.params.submissionId, enrollment)\n+ const submission = await submissions.load(req.params.submissionId)\n+ courses.requireEnrollment(req.user.id, submission.courseId).catch(logger.warn)\n+ return submission\n }\n```\n\nThe author says enrollment checks should not delay feedback pages. Review authorization ordering, guessed IDs, revoked enrollment, audit, and asynchronous failure. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Schreibe eine kurze Referenz für die bestehenden Einreichungsstatus und ihre Auswirkungen auf Bearbeitung und Benotung. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"de"} +{"prompt":"Build the desktop course-outline editor with nested modules, drag reorder, prerequisites, publishing, undo, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Review how final grades are calculated and rounded, then turn the findings into an instructor guide with examples.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Set the autosave interval to 10s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Benenne `GradeCtx` repositoryweit in `GradeContext` um; JSON-Felder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"de"} +{"prompt":"Consolidate learner-name formatting across gradebook and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose the duplicate course notification","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Explain how the content service pins embedded resources when a course version is published.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Create API documentation for the existing assignment-extension endpoint, including precedence, revocation, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Plan a migration from nightly SIS roster files to event-driven enrollment updates, covering ordering, corrections, replay, validation, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Mobile product ticket:\n\n```text\nScreen: learner course home\nHeader: course title, instructor, overall progress\nSections: continue learning, upcoming work, recent feedback, announcements\nUpcoming items use learner-specific due dates and accommodations\nOffline mode shows downloaded lessons and last known deadlines with stale indicator\nProgress updates may arrive out of order from multiple devices\nAccessibility: heading structure, readable progress text, no color-only urgency\nPerformance: first useful content under 1.5s from warm cache\n```\n\nImplement the responsive Compose screen and UI tests using current course APIs.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Implement `POST /v1/submissions/{id}/reopen` with state validation, authorization, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Remove the extra comma from the score label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fix the clipped late badge and extract its duplicated offset into shared gradebook styles.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Replace scattered submission booleans with one explicit lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Cambia `quizRev` por `quizRevision` solo en `AssessmentState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"es"} +{"prompt":"Investigate why the teacher portal briefly displays another section's students after switching courses.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Summarize the current accommodation workflow for accessibility and compliance reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Develop a capacity roadmap for serving 25 million concurrent learners during national exams. Include sessions, autosave, timing, queues, scoring, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Implement idempotent attendance ingestion with correction versions and source provenance.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the SwiftUI feedback viewer with inline annotations, rubric, audio comments, revisions, and VoiceOver support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Fix `assigment` in `content.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Merge duplicate due-date resolution used by notifications and gradebook while preserving effective dates.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Exam incident logs:\n\n```text\nsession=e_881 learner=s_92 attempt=1\nclient autosave response q_41 version=18 at=12:01:02\nnetwork offline\nclient edits q_41 locally version_base=18\nproctor invalidates q_41 due item correction, replacement=q_77\nnetwork reconnect sends q_41 response with client_op=991\nserver maps invalidated item to no active response slot and returns 409\nclient retry queue blocks later answers behind op=991\nsubmission timer expires with six unsynced responses\n```\n\nDetermine why one permanently conflicted response blocks unrelated autosaves and whether queue ordering or item-replacement mapping should resolve it.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Rename `enrolment_id` to `enrollment_id` in the unreleased migration.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Assess whether course analytics can reveal an individual learner through small cohorts and filter combinations. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Restructure the learning SDK into courses, assignments, submissions, grades, and shared models, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan the retirement of legacy SCORM playback, covering content inventory, tracking parity, conversion, communication, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add immutable provenance chains to imported grade records.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Build the tablet classroom dashboard with attendance, live activities, help requests, groups, and accessible layouts.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"do the gradebook","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `CourseRef` with `CourseReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose why exported transcripts omit approved grade changes, implement the verified snapshot fix, and add a registrar-facing note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the content service retain two previous published course versions? Explain current rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Track down the memory leak in document preview workers after rendering large slide decks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write release notes for anonymous peer review, including assignment, identity protection, moderation, and deadlines.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Adaptive practice notes:\n\n```text\nSkill model: Bayesian knowledge tracing per learner and competency\nItems can cover multiple competencies\nTeacher may exclude items or lock difficulty range\nHints reduce evidence weight\nRepeated attempts on same item should not inflate mastery\nCold start uses course-level prior\nLearners need a simple explanation of why an item was selected\nModel updates may arrive from offline devices out of order\nNo sensitive demographic attributes may enter selection\n```\n\nProduce an implementation-free design and rollout plan covering updates, item selection, controls, explanations, offline ordering, evaluation, and privacy.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Give the module list clearer progress grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Turn the current late-submission behavior into learner documentation, then review whether timing and grace-period claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Outline a phased architecture for moving analytics from nightly warehouse jobs to streaming projections, without implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement version-aware grade history with correction links and publication snapshots.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create an operator guide for diagnosing roster synchronization delays.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Move course-progress calculation out of `CourseController` while preserving percentages.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why revoked guardian access remains active in one regional portal.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add generation-fenced rubric publication with preview and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Set the discussion edit window to 15 minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Create the responsive learner-progress dashboard with competencies, trends, evidence, filters, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Corrige apenas `learner progres` para `learner progress` no novo título.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"pt"} +{"prompt":"Review the assignment-upload endpoint for tenant spoofing, malicious files, quota bypass, stale enrollment, and partial failures.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement assessment-session history and write its API guide. Include timing, accommodations, responses, submission, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Design a migration from institution-specific learner IDs to a federated identity graph, including privacy, transfers, merges, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add resumable course-package imports with checksums and row-level validation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Build the desktop item-bank editor with search, metadata, versions, preview, bulk actions, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Extract academic-term resolution into one shared module while preserving enrollment behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why reminder emails use the original due date after an extension, implement the verified cache fix, and update instructor docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed AI feedback assistant for student privacy, prompt injection, rubric fidelity, bias, attribution, and teacher oversight.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why one roster partition retries a permanently invalid record forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft a migration guide for partners moving from CSV rosters to OneRoster.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Analytics pipeline incident:\n\n```text\njob=course-completion date=2026-07-29\nsource events=441,992\nprojection output completions=18,441\nlate event learner=s_88 lesson=l_12 completed_at=2026-07-28\nwatermark=2026-07-29T00:00Z\nlate event routed to correction topic\ncorrection consumer updates learner progress but not course completion aggregate\nlearner UI shows 100%; institutional report shows 92%\nquality check compares total learners, not cross-projection consistency\n```\n\nDetermine why correction handling updates only one projection and why existing quality checks miss the contradictory completion states.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Add evidence count below the competency","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Restructure the scoring pipeline and document its item interface. Preserve scores while separating responses, rules, partial credit, aggregation, and explanation.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Architect a multi-region assessment platform with session ownership, timing, autosave, submission, scoring, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement signed grade-export manifests with course version and record digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new question type, including rendering, scoring, accessibility, fixtures, and analytics.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Consolidate course-date formatting across portal and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why deleted discussion posts remain in course search.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Add transactional enrollment transfer between sections with grade and attendance history.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Pin MathJax to `4.0.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Build the mobile quiz-results screen with score, criteria, feedback, review restrictions, and accessible explanations.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Remplace `Assesment` par `Assessment` uniquement dans le nouveau titre.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"fr"} -{"prompt":"Inspect the QTI import path for XML entity expansion, unsafe resources, identifier collisions, huge items, and script injection.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Implement grade-revision history and write its API documentation. Include actor, reason, rubric, publication, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Develop a roadmap for replacing manual accessibility checks with automated plus human validation, including gates, ownership, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"Add bounded event replay for learner-progress projections with checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Create the responsive instructor inbox with questions, submissions, alerts, filters, and accessible actions.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"fix extensions","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `QuizEvt` with `AssessmentEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why completed courses still send inactivity reminders, implement the verified scheduling fix, and update learner documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.73,"slice":"mixed","lang":"en"} -{"prompt":"Why does the gradebook retain two previous calculation configurations? Explain current audit and rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.47,"slice":"boundary","lang":"en"} -{"prompt":"Track down occasional missing annotations in PDF assignment previews.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Write a troubleshooting guide for missing grades, covering submissions, rubrics, publication, synchronization, and overrides.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Privacy review packet:\n\n```text\nFeature: guardian progress digest\nGuardian receives weekly email with attendance, missing work, recent grades, and teacher comments\nLearner may have multiple guardians with different legal access\nSchool controls whether grades appear\nDigest generation snapshots data Sunday night\nGuardian access may be revoked before Monday delivery\nEmail links require login, but summary text appears in email body\nComments can contain sensitive support information\nDelivery vendor retains message metadata for 30 days\n```\n\nReview authorization timing, snapshot freshness, revocation, email contents, comment sensitivity, vendor retention, and audit. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a loading state to the assignment rows","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Plan and implement guardian access policies. First define relationship sources, scope, revocation, learner age transitions, notifications, audit, and rollout; then add policy storage and enforcement.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.93,"slice":"mixed","lang":"en"} -{"prompt":"Outline an architecture for cross-institution course sharing with identity, licensing, versions, enrollments, analytics, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"boundary","lang":"en"} -{"prompt":"Implement snapshot-consistent transcript exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Escribe una guía para integrar evaluaciones, con preguntas, versiones, tiempos, puntuación y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} -{"prompt":"Move late-status calculation out of the submission worker without changing results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Investigate why the iOS app loses downloaded lesson progress after reinstall and restore.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.64,"slice":"boundary","lang":"en"} -{"prompt":"Add atomic course-version publication with validation, preview, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Remove the obsolete `legacy_gradebook` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"core","lang":"en"} -{"prompt":"Build the content-library browser with filters, previews, versions, licensing, bulk actions, and accessible selection.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"`Assigment submitted` を `Assignment submitted` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"ja"} -{"prompt":"Review the exam-file upload endpoint for malware, stale sessions, tenant confusion, filename leakage, and quota bypass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Implement content-publication history and write its API guide. Include versions, validation, activation, rollback, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Plan a disaster-recovery strategy for learning services, including courses, submissions, grades, assessments, keys, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"core","lang":"en"} -{"prompt":"Add content-hash deduplication to submitted attachments with course-scoped ownership.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Create the desktop accommodation editor with timing, attempts, dates, scope, conflicts, and approval.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"continue the roster cleanup","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"Rename `GradeRev` to `GradeRevision` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why section transfers leave learners subscribed to old announcements, implement the verified fan-out fix, and update instructor docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.77,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed course-content cache for enrollment revocation, licensing, stale versions, offline clients, and isolation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Find why an assessment worker retries a permanently invalid response forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Draft a support guide for recovering an interrupted quiz submission.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Projection failure output:\n\n```text\nlearner=s_551 course=c_82 progress_version=991\nlesson_completed event offset=77118\nprojection updates lesson state and course percent=100\ncheckpoint transaction times out\ncompletion-certificate worker sees percent=100 and issues certificate\nprojection restarts from previous offset and replays lesson event\nidempotency key stored with checkpoint was not committed\ncourse percent increments beyond expected item count and becomes=104\n```\n\nDetermine how projection, checkpoint, and downstream certificate issuance lack one atomic boundary and why replay is not idempotent.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Add effective due date below the assignment","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.24,"slice":"core","lang":"en"} -{"prompt":"Restructure the roster pipeline and document its source interface. Preserve enrollments while separating decode, normalize, validate, reconcile, and publish.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"Architect a multi-region learning platform with institution ownership, course delivery, submissions, grades, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed transcript manifests with course and grade revision digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new SIS connector, including identities, rosters, corrections, fixtures, and monitoring.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Consolidate grade-status formatting across portal and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Investigate why deleted assignments remain in learner search.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.61,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional course ownership transfer with permissions and immutable history.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Pin Moodle to `5.0.2`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Build the mobile attendance screen with roster, status, bulk actions, offline capture, and accessible controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"把 `Cours progress` 改成 `Course progress`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"zh"} -{"prompt":"Inspect the grade-import endpoint for formula injection, identity confusion, stale course versions, partial commits, and privilege escalation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} +{"prompt":"Pin MathJax to `4.0.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile quiz-results screen with score, criteria, feedback, review restrictions, and accessible explanations.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Remplace `Assesment` par `Assessment` uniquement dans le nouveau titre.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"fr"} +{"prompt":"Inspect the QTI import path for XML entity expansion, unsafe resources, identifier collisions, huge items, and script injection.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement grade-revision history and write its API documentation. Include actor, reason, rubric, publication, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Develop a roadmap for replacing manual accessibility checks with automated plus human validation, including gates, ownership, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add bounded event replay for learner-progress projections with checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the responsive instructor inbox with questions, submissions, alerts, filters, and accessible actions.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"fix extensions","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `QuizEvt` with `AssessmentEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose why completed courses still send inactivity reminders, implement the verified scheduling fix, and update learner documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the gradebook retain two previous calculation configurations? Explain current audit and rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down occasional missing annotations in PDF assignment previews.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Write a troubleshooting guide for missing grades, covering submissions, rubrics, publication, synchronization, and overrides.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Privacy review packet:\n\n```text\nFeature: guardian progress digest\nGuardian receives weekly email with attendance, missing work, recent grades, and teacher comments\nLearner may have multiple guardians with different legal access\nSchool controls whether grades appear\nDigest generation snapshots data Sunday night\nGuardian access may be revoked before Monday delivery\nEmail links require login, but summary text appears in email body\nComments can contain sensitive support information\nDelivery vendor retains message metadata for 30 days\n```\n\nReview authorization timing, snapshot freshness, revocation, email contents, comment sensitivity, vendor retention, and audit. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add a loading state to the assignment rows","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Plan and implement guardian access policies. First define relationship sources, scope, revocation, learner age transitions, notifications, audit, and rollout; then add policy storage and enforcement.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Outline an architecture for cross-institution course sharing with identity, licensing, versions, enrollments, analytics, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement snapshot-consistent transcript exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Escribe una guía para integrar evaluaciones, con preguntas, versiones, tiempos, puntuación y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"es"} +{"prompt":"Move late-status calculation out of the submission worker without changing results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why the iOS app loses downloaded lesson progress after reinstall and restore.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add atomic course-version publication with validation, preview, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remove the obsolete `legacy_gradebook` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Build the content-library browser with filters, previews, versions, licensing, bulk actions, and accessible selection.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"`Assigment submitted` を `Assignment submitted` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"ja"} +{"prompt":"Review the exam-file upload endpoint for malware, stale sessions, tenant confusion, filename leakage, and quota bypass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement content-publication history and write its API guide. Include versions, validation, activation, rollback, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan a disaster-recovery strategy for learning services, including courses, submissions, grades, assessments, keys, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add content-hash deduplication to submitted attachments with course-scoped ownership.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the desktop accommodation editor with timing, attempts, dates, scope, conflicts, and approval.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Rename `GradeRev` to `GradeRevision` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why section transfers leave learners subscribed to old announcements, implement the verified fan-out fix, and update instructor docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed course-content cache for enrollment revocation, licensing, stale versions, offline clients, and isolation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why an assessment worker retries a permanently invalid response forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Draft a support guide for recovering an interrupted quiz submission.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Projection failure output:\n\n```text\nlearner=s_551 course=c_82 progress_version=991\nlesson_completed event offset=77118\nprojection updates lesson state and course percent=100\ncheckpoint transaction times out\ncompletion-certificate worker sees percent=100 and issues certificate\nprojection restarts from previous offset and replays lesson event\nidempotency key stored with checkpoint was not committed\ncourse percent increments beyond expected item count and becomes=104\n```\n\nDetermine how projection, checkpoint, and downstream certificate issuance lack one atomic boundary and why replay is not idempotent.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Add effective due date below the assignment","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Restructure the roster pipeline and document its source interface. Preserve enrollments while separating decode, normalize, validate, reconcile, and publish.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Architect a multi-region learning platform with institution ownership, course delivery, submissions, grades, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement signed transcript manifests with course and grade revision digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new SIS connector, including identities, rosters, corrections, fixtures, and monitoring.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Consolidate grade-status formatting across portal and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why deleted assignments remain in learner search.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add transactional course ownership transfer with permissions and immutable history.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Pin Moodle to `5.0.2`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile attendance screen with roster, status, bulk actions, offline capture, and accessible controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"把 `Cours progress` 改成 `Course progress`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"zh"} +{"prompt":"Inspect the grade-import endpoint for formula injection, identity confusion, stale course versions, partial commits, and privilege escalation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Implement learner-progress history and write its API documentation. Include evidence, revisions, source, pagination, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Design a custody architecture for digital assets with hot, warm, and cold wallets, policy approvals, transaction simulation, nonce management, signing ceremonies, key rotation, chain reorganizations, audit evidence, and migration from single-key accounts. Deliver an RFC and phased roadmap, not code.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.98,"slice":"core","lang":"en"} -{"prompt":"Before implementing cross-chain deposits, outline address assignment, confirmations, finality, reorg handling, token metadata, fraud controls, reconciliation, and staged rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"boundary","lang":"en"} -{"prompt":"Add EIP-1559 fee support to `txctl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Withdrawal incident logs:\n\n```text\nchain=ethereum wallet=w_17 request=wd_881\nreserved nonce=421 at=12:01:02\ntransaction hash=0x91a fee_cap=32gwei broadcast success\nworker timeout before persistence commit\nretry reserves nonce=421 because reservation row rolled back\nsecond transaction hash=0xa82 destination=same amount=same fee_cap=38gwei\nnode accepts replacement 0xa82\nindexer later observes both hashes, first status=dropped second status=confirmed\nledger records two broadcast attempts and marks request duplicated\n```\n\nDetermine whether nonce reservation and broadcast lack an atomic boundary, and distinguish an actual duplicate transfer from a legitimate replacement transaction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Build the SwiftUI transaction-detail screen with status timeline, network fee, addresses, confirmations, explorer action, warnings, and VoiceOver labels.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Plan and implement a transaction-policy engine for custodial withdrawals. Begin with a design covering asset, destination, velocity, allowlists, sanctions signals, approvals, simulations, policy versioning, emergency controls, audit replay, and failure behavior. Then add the evaluator, policy APIs, decision traces, and conformance tests. Treat policy correctness and reproducibility as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.98,"slice":"mixed","lang":"en"} -{"prompt":"Set `BTC_CONFIRMATIONS` to 6","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Extract duplicated hexadecimal address normalization from deposit and withdrawal services while preserving validation.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Implement `/internal/chains/status` with head height, finalized height, peer count, lag, and last reorg.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} -{"prompt":"make the wallet look serious","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.41,"slice":"vague-eval","lang":"en"} -{"prompt":"Find why Solana deposits occasionally disappear from balances after a fork rollback.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"Explain how `FinalityTracker` distinguishes observed, confirmed, finalized, and reverted transactions. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Customer release notes source:\n\n```text\nFeature: withdrawal address book\nCustomers may save named addresses per asset and network\nNew addresses require email confirmation before use\nOrganizations can require a 24-hour cooling period\nAddress labels are private to the organization\nRemoving an address prevents new withdrawals but does not affect pending ones\nNetwork and memo/tag fields are part of the saved destination\nUnsupported contract addresses are rejected when detectable\nOld API clients can withdraw to saved or unsaved destinations as before unless policy requires allowlisting\n```\n\nTurn this into release notes and an administrator guide with clear security limits and compatibility behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.46,"slice":"pasted-context","lang":"en"} -{"prompt":"Move the network badge closer to the asset symbol","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.13,"slice":"boundary","lang":"en"} -{"prompt":"Write an operator guide for replaying failed chain-index events without crediting deposits twice.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Implement deposit-address endpoints with asset validation, derivation metadata, pagination, and permissions, then document reuse, examples, and errors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Map out a migration from one omnibus wallet to sharded wallets by risk tier, including address continuity, sweeping, reconciliation, monitoring, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Rename `txHsh` to `transactionHash` in `TransferMapper.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"en"} -{"prompt":"Teach the chain indexer to checkpoint block hashes and rewind projections after bounded reorganizations.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Polish the portfolio balance card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.28,"slice":"core","lang":"en"} -{"prompt":"Bump `ethers` to `6.15.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Rename `MasterKeySet` to `PrimaryKeySet` across services, ceremonies, dashboards, and tests while preserving serialized identifiers.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.68,"slice":"boundary","lang":"en"} -{"prompt":"Split `WithdrawalService` into request, policy, signing, broadcasting, and reconciliation components without changing outcomes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.84,"slice":"core","lang":"en"} -{"prompt":"Implementation ticket:\n\n```text\nCHAIN-3112 — token contract metadata registry\nFields: network, contract address, symbol, decimals, display name, verification state\nUpdates require two-person approval\nDecimals changes after activation are forbidden without emergency migration\nIndexer rejects transfers for unknown contracts but stores raw events for replay\nDuplicate symbols are allowed across contracts\nPhishing and deprecated states suppress customer display\nEvery revision is immutable and signed\nExpose unknown-contract, suppressed-transfer, and metadata-version metrics\n```\n\nImplement storage, validation, approval, signing, publication, indexer integration, replay, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Investigate why the Android wallet shows an outdated fiat value after changing the selected currency.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Create the signing-request review UI and add a concise guide for simulation, policy findings, approvals, fees, and expiry.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Why does the Bitcoin indexer retain orphaned block transactions after a reorg? Explain current audit behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.52,"slice":"core","lang":"en"} -{"prompt":"Rewrite the local setup for running Anvil, Bitcoin Core regtest, the indexer, and synthetic wallets.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.36,"slice":"core","lang":"en"} -{"prompt":"This signature test fails only for some secp256k1 outputs:\n\n```text\nFAIL TestSignatureCanonicalLowS\nmessage_hash=8a11...f2\nr=0x71a...c4\ns=0x9f2...81\nexpected normalized_s=n-s\nactual verifier accepts high-s signature\nsigner library version=0.14 changed default normalization=false\nEthereum recovery succeeds for both forms\nBitcoin policy rejects high-s relay\nfixture labels algorithm=ECDSA without chain context\n```\n\nDetermine whether normalization belongs in the generic signer or chain-specific encoder and why the current test assumption is ambiguous.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"boundary","lang":"en"} -{"prompt":"finish the custody service","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"Propose an architecture for MPC signing across regions, including quorum, share refresh, membership changes, audit, liveness, compromise recovery, and ceremonies.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.99,"slice":"core","lang":"en"} -{"prompt":"Add PSBT v2 decoding to `walletinspect`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Review excerpt:\n\n```diff\n async function approveWithdrawal(req) {\n- const simulation = await simulator.run(req.params.id)\n- if (!simulation.safe) throw new Error('unsafe transaction')\n- await approvals.record(req.user.id, simulation.digest)\n+ approvals.record(req.user.id, 'pending').catch(logger.warn)\n+ signer.enqueue(req.params.id)\n return { status: 'accepted' }\n }\n```\n\nThe author says simulation makes approval too slow. Review approval binding, asynchronous failure, transaction mutation, audit, authorization, and what accepted means. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Schreibe eine kurze Referenz für die bestehenden Transaktionsstatus und ihre Auswirkungen auf Salden und Wiederholungen. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"de"} -{"prompt":"Build the desktop chain-monitor dashboard with heads, finality, reorgs, node health, filters, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Review how deposit confirmations affect available balances, then turn the findings into an operations guide with examples.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.62,"slice":"mixed","lang":"en"} -{"prompt":"Set the fee estimate TTL to 20s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Benenne `WalletCtx` repositoryweit in `WalletContext` um; JSON-Felder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"de"} -{"prompt":"Consolidate network-name normalization across deposit and withdrawal APIs without changing values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Diagnose the duplicate deposit alert","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"Explain how the nonce manager handles pending transactions that disappear from the mempool.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Create API documentation for the existing fee-estimate endpoint, including expiry, priority, units, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"en"} -{"prompt":"Plan a migration from locally managed node RPC endpoints to a multi-provider routing layer, covering trust, consistency, failover, cost, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"core","lang":"en"} -{"prompt":"Mobile product ticket:\n\n```text\nScreen: send asset\nSteps: asset, network, destination, amount, review, confirmation\nDestination may require memo or tag\nShow fiat estimate with timestamp and stale state\nFee estimate can change before signing\nAddress book entries display verification and cooling-period status\nScanner must show parsed network and reject incompatible addresses\nReview screen distinguishes network fee from service fee\nAccessibility: long addresses have grouped spoken form and copy action\nNever imply a broadcast transaction is final\n```\n\nImplement the iOS flow and UI tests using the existing transfer coordinator.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"pasted-context","lang":"en"} -{"prompt":"Implement `POST /v1/withdrawals/{id}/cancel` with state checks, signer coordination, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Remove the extra zero from the fee example","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"core","lang":"en"} -{"prompt":"Fix the clipped network chip and extract its duplicated padding into the shared token.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.35,"slice":"mixed","lang":"en"} -{"prompt":"Replace scattered withdrawal booleans with one explicit lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Cambia `blkHgt` por `blockHeight` solo en `ChainState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"es"} -{"prompt":"Investigate why the wallet briefly displays another account's deposit address after switching organizations.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Summarize the current key-rotation ceremony for security and audit reviewers using code and runbooks.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"Develop a capacity roadmap for indexing 200 supported chains and rollups. Include node traffic, finality, reorgs, storage, replay, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} +{"prompt":"Design a custody architecture for digital assets with hot, warm, and cold wallets, policy approvals, transaction simulation, nonce management, signing ceremonies, key rotation, chain reorganizations, audit evidence, and migration from single-key accounts. Deliver an RFC and phased roadmap, not code.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Before implementing cross-chain deposits, outline address assignment, confirmations, finality, reorg handling, token metadata, fraud controls, reconciliation, and staged rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add EIP-1559 fee support to `txctl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Withdrawal incident logs:\n\n```text\nchain=ethereum wallet=w_17 request=wd_881\nreserved nonce=421 at=12:01:02\ntransaction hash=0x91a fee_cap=32gwei broadcast success\nworker timeout before persistence commit\nretry reserves nonce=421 because reservation row rolled back\nsecond transaction hash=0xa82 destination=same amount=same fee_cap=38gwei\nnode accepts replacement 0xa82\nindexer later observes both hashes, first status=dropped second status=confirmed\nledger records two broadcast attempts and marks request duplicated\n```\n\nDetermine whether nonce reservation and broadcast lack an atomic boundary, and distinguish an actual duplicate transfer from a legitimate replacement transaction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Build the SwiftUI transaction-detail screen with status timeline, network fee, addresses, confirmations, explorer action, warnings, and VoiceOver labels.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Plan and implement a transaction-policy engine for custodial withdrawals. Begin with a design covering asset, destination, velocity, allowlists, sanctions signals, approvals, simulations, policy versioning, emergency controls, audit replay, and failure behavior. Then add the evaluator, policy APIs, decision traces, and conformance tests. Treat policy correctness and reproducibility as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Set `BTC_CONFIRMATIONS` to 6","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Extract duplicated hexadecimal address normalization from deposit and withdrawal services while preserving validation.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement `/internal/chains/status` with head height, finalized height, peer count, lag, and last reorg.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"make the wallet look serious","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Find why Solana deposits occasionally disappear from balances after a fork rollback.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Explain how `FinalityTracker` distinguishes observed, confirmed, finalized, and reverted transactions. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Customer release notes source:\n\n```text\nFeature: withdrawal address book\nCustomers may save named addresses per asset and network\nNew addresses require email confirmation before use\nOrganizations can require a 24-hour cooling period\nAddress labels are private to the organization\nRemoving an address prevents new withdrawals but does not affect pending ones\nNetwork and memo/tag fields are part of the saved destination\nUnsupported contract addresses are rejected when detectable\nOld API clients can withdraw to saved or unsaved destinations as before unless policy requires allowlisting\n```\n\nTurn this into release notes and an administrator guide with clear security limits and compatibility behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"Move the network badge closer to the asset symbol","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Write an operator guide for replaying failed chain-index events without crediting deposits twice.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement deposit-address endpoints with asset validation, derivation metadata, pagination, and permissions, then document reuse, examples, and errors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Map out a migration from one omnibus wallet to sharded wallets by risk tier, including address continuity, sweeping, reconciliation, monitoring, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Rename `txHsh` to `transactionHash` in `TransferMapper.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Teach the chain indexer to checkpoint block hashes and rewind projections after bounded reorganizations.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Polish the portfolio balance card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump `ethers` to `6.15.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename `MasterKeySet` to `PrimaryKeySet` across services, ceremonies, dashboards, and tests while preserving serialized identifiers.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Split `WithdrawalService` into request, policy, signing, broadcasting, and reconciliation components without changing outcomes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implementation ticket:\n\n```text\nCHAIN-3112 — token contract metadata registry\nFields: network, contract address, symbol, decimals, display name, verification state\nUpdates require two-person approval\nDecimals changes after activation are forbidden without emergency migration\nIndexer rejects transfers for unknown contracts but stores raw events for replay\nDuplicate symbols are allowed across contracts\nPhishing and deprecated states suppress customer display\nEvery revision is immutable and signed\nExpose unknown-contract, suppressed-transfer, and metadata-version metrics\n```\n\nImplement storage, validation, approval, signing, publication, indexer integration, replay, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Investigate why the Android wallet shows an outdated fiat value after changing the selected currency.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Create the signing-request review UI and add a concise guide for simulation, policy findings, approvals, fees, and expiry.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the Bitcoin indexer retain orphaned block transactions after a reorg? Explain current audit behavior.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Rewrite the local setup for running Anvil, Bitcoin Core regtest, the indexer, and synthetic wallets.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"This signature test fails only for some secp256k1 outputs:\n\n```text\nFAIL TestSignatureCanonicalLowS\nmessage_hash=8a11...f2\nr=0x71a...c4\ns=0x9f2...81\nexpected normalized_s=n-s\nactual verifier accepts high-s signature\nsigner library version=0.14 changed default normalization=false\nEthereum recovery succeeds for both forms\nBitcoin policy rejects high-s relay\nfixture labels algorithm=ECDSA without chain context\n```\n\nDetermine whether normalization belongs in the generic signer or chain-specific encoder and why the current test assumption is ambiguous.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"finish the custody service","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"vague-eval","lang":"en"} +{"prompt":"Propose an architecture for MPC signing across regions, including quorum, share refresh, membership changes, audit, liveness, compromise recovery, and ceremonies.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add PSBT v2 decoding to `walletinspect`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Review excerpt:\n\n```diff\n async function approveWithdrawal(req) {\n- const simulation = await simulator.run(req.params.id)\n- if (!simulation.safe) throw new Error('unsafe transaction')\n- await approvals.record(req.user.id, simulation.digest)\n+ approvals.record(req.user.id, 'pending').catch(logger.warn)\n+ signer.enqueue(req.params.id)\n return { status: 'accepted' }\n }\n```\n\nThe author says simulation makes approval too slow. Review approval binding, asynchronous failure, transaction mutation, audit, authorization, and what accepted means. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Schreibe eine kurze Referenz für die bestehenden Transaktionsstatus und ihre Auswirkungen auf Salden und Wiederholungen. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"de"} +{"prompt":"Build the desktop chain-monitor dashboard with heads, finality, reorgs, node health, filters, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Review how deposit confirmations affect available balances, then turn the findings into an operations guide with examples.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Set the fee estimate TTL to 20s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Benenne `WalletCtx` repositoryweit in `WalletContext` um; JSON-Felder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"de"} +{"prompt":"Consolidate network-name normalization across deposit and withdrawal APIs without changing values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose the duplicate deposit alert","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Explain how the nonce manager handles pending transactions that disappear from the mempool.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Create API documentation for the existing fee-estimate endpoint, including expiry, priority, units, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Plan a migration from locally managed node RPC endpoints to a multi-provider routing layer, covering trust, consistency, failover, cost, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Mobile product ticket:\n\n```text\nScreen: send asset\nSteps: asset, network, destination, amount, review, confirmation\nDestination may require memo or tag\nShow fiat estimate with timestamp and stale state\nFee estimate can change before signing\nAddress book entries display verification and cooling-period status\nScanner must show parsed network and reject incompatible addresses\nReview screen distinguishes network fee from service fee\nAccessibility: long addresses have grouped spoken form and copy action\nNever imply a broadcast transaction is final\n```\n\nImplement the iOS flow and UI tests using the existing transfer coordinator.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Implement `POST /v1/withdrawals/{id}/cancel` with state checks, signer coordination, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remove the extra zero from the fee example","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fix the clipped network chip and extract its duplicated padding into the shared token.","purpose":"frontendImpl","secondary":"refactor","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Replace scattered withdrawal booleans with one explicit lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Cambia `blkHgt` por `blockHeight` solo en `ChainState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"es"} +{"prompt":"Investigate why the wallet briefly displays another account's deposit address after switching organizations.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Summarize the current key-rotation ceremony for security and audit reviewers using code and runbooks.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Develop a capacity roadmap for indexing 200 supported chains and rollups. Include node traffic, finality, reorgs, storage, replay, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Implement idempotent staking-reward ingestion with source epochs and correction events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Create the Compose transaction-history screen with asset filters, status, network, pagination, and TalkBack summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Fix `withrawal` in `events.proto`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} -{"prompt":"Merge duplicate chain-address types used by policy and indexing while preserving encoded forms.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Indexer reorg failure:\n\n```text\nchain=polygon head=48199201 finalized=48199073\nblock 48199180 hash=0xa1 parent=0x91 applied\nblock 48199181 hash=0xb2 applied credits=44\nnew canonical block 48199180 hash=0xc3 parent=0x91 observed\nreorg walker finds common ancestor=48199179\nrollback projection reverses block 48199181 but skips 48199180 reason='height already present'\napply new block 48199180 fails unique height constraint\npartition stops; balances retain credits from old block 48199180\n```\n\nDetermine why height-based identity prevents rollback and replacement of the forked block and which projections remain inconsistent.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Rename `adress_tag` to `address_tag` in the unreleased schema.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"en"} -{"prompt":"Assess whether unsigned token metadata can spoof asset names, icons, decimals, or network identity in customer views. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Restructure the chain SDK into addresses, transactions, blocks, finality, and shared types, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Plan the retirement of legacy destination tags stored outside address records, covering migration, validation, compatibility, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.83,"slice":"core","lang":"en"} -{"prompt":"Add immutable provenance chains to normalized token transfers.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Build the tablet approval queue with simulations, risk findings, policy, quorum, expiry, and accessible actions.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"do the wallet page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.39,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `TxRef` with `TransactionReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why exported statements omit reorg corrections, implement the verified projection fix, and add an operations note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"Why does the signing service retain two previous policy bundles? Explain current rollback and verification behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.47,"slice":"boundary","lang":"en"} -{"prompt":"Track down the memory leak in transaction simulation after repeated contract calls.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"Write release notes for configurable withdrawal approval quorums, including thresholds, expiry, and emergency controls.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"core","lang":"en"} -{"prompt":"Key ceremony notes:\n\n```text\nCurrent root key uses 3-of-5 hardware tokens\nNew target: 4-of-7 with two additional regions\nExisting child keys remain valid until scheduled rotation\nCeremony must produce signed transcript and public key manifest\nNo single operator may initialize and attest the same token\nOne region may be unavailable during routine signing\nLost token replacement requires board approval\nEmergency recovery material stays offline\nOld verifier software supports only five participant identifiers\n```\n\nProduce an implementation-free migration and ceremony plan covering membership change, compatibility, liveness, attestation, transcripts, recovery, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"pasted-context","lang":"en"} -{"prompt":"Give the asset list clearer network grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.31,"slice":"core","lang":"en"} -{"prompt":"Turn the current deposit-finality behavior into customer documentation, then review whether its confirmation and reorg claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Outline a phased architecture for moving transaction history from Postgres to a chain-aware event store, without implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.87,"slice":"boundary","lang":"en"} -{"prompt":"Implement version-aware destination allowlists with cooling periods and immutable revisions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the Compose transaction-history screen with asset filters, status, network, pagination, and TalkBack summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Fix `withrawal` in `events.proto`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Merge duplicate chain-address types used by policy and indexing while preserving encoded forms.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Indexer reorg failure:\n\n```text\nchain=polygon head=48199201 finalized=48199073\nblock 48199180 hash=0xa1 parent=0x91 applied\nblock 48199181 hash=0xb2 applied credits=44\nnew canonical block 48199180 hash=0xc3 parent=0x91 observed\nreorg walker finds common ancestor=48199179\nrollback projection reverses block 48199181 but skips 48199180 reason='height already present'\napply new block 48199180 fails unique height constraint\npartition stops; balances retain credits from old block 48199180\n```\n\nDetermine why height-based identity prevents rollback and replacement of the forked block and which projections remain inconsistent.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Rename `adress_tag` to `address_tag` in the unreleased schema.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Assess whether unsigned token metadata can spoof asset names, icons, decimals, or network identity in customer views. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Restructure the chain SDK into addresses, transactions, blocks, finality, and shared types, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan the retirement of legacy destination tags stored outside address records, covering migration, validation, compatibility, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add immutable provenance chains to normalized token transfers.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Build the tablet approval queue with simulations, risk findings, policy, quorum, expiry, and accessible actions.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"do the wallet page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `TxRef` with `TransactionReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose why exported statements omit reorg corrections, implement the verified projection fix, and add an operations note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Why does the signing service retain two previous policy bundles? Explain current rollback and verification behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Track down the memory leak in transaction simulation after repeated contract calls.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write release notes for configurable withdrawal approval quorums, including thresholds, expiry, and emergency controls.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Key ceremony notes:\n\n```text\nCurrent root key uses 3-of-5 hardware tokens\nNew target: 4-of-7 with two additional regions\nExisting child keys remain valid until scheduled rotation\nCeremony must produce signed transcript and public key manifest\nNo single operator may initialize and attest the same token\nOne region may be unavailable during routine signing\nLost token replacement requires board approval\nEmergency recovery material stays offline\nOld verifier software supports only five participant identifiers\n```\n\nProduce an implementation-free migration and ceremony plan covering membership change, compatibility, liveness, attestation, transcripts, recovery, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Give the asset list clearer network grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Turn the current deposit-finality behavior into customer documentation, then review whether its confirmation and reorg claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Outline a phased architecture for moving transaction history from Postgres to a chain-aware event store, without implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement version-aware destination allowlists with cooling periods and immutable revisions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Create an operator guide for diagnosing deposits stuck below finality.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Move gas-estimate normalization out of `TransferController` while preserving displayed fees.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Investigate why revoked API credentials continue submitting withdrawals through one regional gateway.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"Add generation-fenced chain-configuration publication with simulation and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Set the withdrawal expiry to 30 minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Create the responsive key-inventory view with status, location, attestation, rotation, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Corrige apenas `transction` para `transaction` no novo alerta.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"pt"} -{"prompt":"Review the transaction-simulation endpoint for SSRF through RPC URLs, state override abuse, tenant confusion, and resource exhaustion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Implement chain-reorg history and write its API guide. Include depths, affected blocks, reversals, pagination, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} +{"prompt":"Move gas-estimate normalization out of `TransferController` while preserving displayed fees.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why revoked API credentials continue submitting withdrawals through one regional gateway.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add generation-fenced chain-configuration publication with simulation and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Set the withdrawal expiry to 30 minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Create the responsive key-inventory view with status, location, attestation, rotation, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Corrige apenas `transction` para `transaction` no novo alerta.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"pt"} +{"prompt":"Review the transaction-simulation endpoint for SSRF through RPC URLs, state override abuse, tenant confusion, and resource exhaustion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement chain-reorg history and write its API guide. Include depths, affected blocks, reversals, pagination, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Design a migration from static confirmation counts to chain-specific finality policies, including compatibility, audit, simulation, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Add resumable historical block backfills with hash checkpoints and reorg detection.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Build the desktop transaction simulator with decoded calls, balance changes, warnings, traces, and copyable output.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"continue the nonce bug","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.56,"slice":"vague-eval","lang":"en"} -{"prompt":"Extract asset-identifier normalization into one shared module while preserving canonical values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why withdrawal approvals use an outdated risk score, implement the verified snapshot-binding fix, and update operator documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed browser wallet connection flow for phishing, origin binding, account leakage, replay, and session revocation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","lang":"en"} -{"prompt":"Find why one indexer partition retries an unsupported transaction forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Draft a migration guide for API clients moving from integer fees to decimal string amounts.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"core","lang":"en"} -{"prompt":"Reconciliation incident excerpt:\n\n```text\nasset=USDC network=ethereum date=2026-07-29\nonchain wallet balance=12,841,992.113421\ninternal customer liabilities=12,811,400.113421\npending withdrawals=20,592.000000\noperational reserve expected=10,000.000000\nreconciliation difference=0\nlater discovered one pending withdrawal was already confirmed onchain\nindexer confirmation event delayed behind backfill partition\nledger still classified amount as pending\nformula subtracts pending from liabilities and masks the stale status\n```\n\nDetermine why reconciliation balances despite an incorrect pending classification and which independent invariant is missing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Add confirmation count below the status","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.24,"slice":"core","lang":"en"} -{"prompt":"Restructure the transaction indexer and document its chain-adapter interface. Preserve projections while separating fetch, canonicalize, apply, rollback, and checkpoint.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.83,"slice":"mixed","lang":"en"} -{"prompt":"Architect a multi-region custody control plane with wallet ownership, signing, policies, failover, audit, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.99,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed balance snapshots with chain heads and ledger digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new blockchain, including addresses, transactions, finality, fees, fixtures, and monitoring.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.48,"slice":"core","lang":"en"} -{"prompt":"Consolidate transaction-status formatting across portal and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Investigate why removed assets remain visible in wallet search.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional wallet ownership transfer with policy remapping and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Pin Bitcoin Core to `29.1`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Build the mobile address-book manager with verification, cooling periods, search, delete, and accessible confirmations.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Remplace `Withrawal` par `Withdrawal` uniquement dans le nouveau titre.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"fr"} -{"prompt":"Inspect the raw-transaction broadcast endpoint for chain confusion, fee abuse, stale simulation, replay, and authorization gaps.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Implement signing-ceremony history and write its API documentation. Include participants, attestations, outputs, failures, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Develop a roadmap for replacing software signing keys with hardware-backed threshold signing, including compatibility, ceremonies, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"core","lang":"en"} -{"prompt":"Add bounded transaction replay for wallet-balance projections with checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Create the responsive policy-decision viewer with matched rules, simulations, approvals, and accessible explanations.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} +{"prompt":"Add resumable historical block backfills with hash checkpoints and reorg detection.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Build the desktop transaction simulator with decoded calls, balance changes, warnings, traces, and copyable output.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Extract asset-identifier normalization into one shared module while preserving canonical values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Investigate why withdrawal approvals use an outdated risk score, implement the verified snapshot-binding fix, and update operator documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed browser wallet connection flow for phishing, origin binding, account leakage, replay, and session revocation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why one indexer partition retries an unsupported transaction forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft a migration guide for API clients moving from integer fees to decimal string amounts.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Reconciliation incident excerpt:\n\n```text\nasset=USDC network=ethereum date=2026-07-29\nonchain wallet balance=12,841,992.113421\ninternal customer liabilities=12,811,400.113421\npending withdrawals=20,592.000000\noperational reserve expected=10,000.000000\nreconciliation difference=0\nlater discovered one pending withdrawal was already confirmed onchain\nindexer confirmation event delayed behind backfill partition\nledger still classified amount as pending\nformula subtracts pending from liabilities and masks the stale status\n```\n\nDetermine why reconciliation balances despite an incorrect pending classification and which independent invariant is missing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Add confirmation count below the status","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Restructure the transaction indexer and document its chain-adapter interface. Preserve projections while separating fetch, canonicalize, apply, rollback, and checkpoint.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Architect a multi-region custody control plane with wallet ownership, signing, policies, failover, audit, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement signed balance snapshots with chain heads and ledger digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new blockchain, including addresses, transactions, finality, fees, fixtures, and monitoring.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Consolidate transaction-status formatting across portal and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why removed assets remain visible in wallet search.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add transactional wallet ownership transfer with policy remapping and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Pin Bitcoin Core to `29.1`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile address-book manager with verification, cooling periods, search, delete, and accessible confirmations.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remplace `Withrawal` par `Withdrawal` uniquement dans le nouveau titre.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"fr"} +{"prompt":"Inspect the raw-transaction broadcast endpoint for chain confusion, fee abuse, stale simulation, replay, and authorization gaps.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement signing-ceremony history and write its API documentation. Include participants, attestations, outputs, failures, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Develop a roadmap for replacing software signing keys with hardware-backed threshold signing, including compatibility, ceremonies, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add bounded transaction replay for wallet-balance projections with checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the responsive policy-decision viewer with matched rules, simulations, approvals, and accessible explanations.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"fix finality","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `ChainEvt` with `ChainEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why confirmed deposits still trigger pending reminders, implement the verified projection fix, and update customer documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.73,"slice":"mixed","lang":"en"} -{"prompt":"Why does the wallet service retain previous derivation ranges after address rotation? Explain current recovery behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.47,"slice":"boundary","lang":"en"} +{"prompt":"Replace `ChainEvt` with `ChainEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose why confirmed deposits still trigger pending reminders, implement the verified projection fix, and update customer documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the wallet service retain previous derivation ranges after address rotation? Explain current recovery behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Track down occasional missing internal calls in EVM transaction traces.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write a troubleshooting guide for failed withdrawals, covering policy, approval, signing, broadcast, fees, and finality.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Security review packet:\n\n```text\nFeature: temporary withdrawal-limit increase\nOrganization administrator requests higher daily limit with amount, duration, and reason\nTwo different approvers required above configured threshold\nIncrease activates immediately after final approval and lasts up to 24 hours\nPending withdrawals count against both old and new limits\nRevocation returns limit to baseline but does not cancel already approved withdrawals\nApprovers receive simulation of projected exposure\nAudit stores request, approvals, policy version, activation, and expiry\nEmergency administrators may bypass one approver with incident reference\n```\n\nReview approval independence, activation race, pending amounts, revocation, emergency bypass, policy binding, and audit. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a loading state to the transfer rows","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Plan and implement temporary withdrawal-limit increases. First define approvals, exposure calculation, expiry, revocation, emergency use, audit, and rollout; then add storage and enforcement.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.92,"slice":"mixed","lang":"en"} -{"prompt":"Outline an architecture for chain-agnostic smart-contract risk analysis, including simulation, signatures, provenance, caching, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"boundary","lang":"en"} -{"prompt":"Implement snapshot-consistent wallet-statement exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Escribe una guía para integrar una nueva red, con direcciones, transacciones, comisiones, finalidad y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"es"} -{"prompt":"Move confirmation-policy resolution out of the deposit worker without changing credits.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Investigate why the iOS app loses transaction filters after returning from background.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Add atomic token-metadata publication with approval, signature, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Remove the obsolete `legacy_nonce` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"core","lang":"en"} -{"prompt":"Build the transaction-policy editor with conditions, thresholds, approvals, simulation, conflicts, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"`Transation confirmed` を `Transaction confirmed` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"ja"} -{"prompt":"Review the signed-transaction download path for key material leakage, stale approvals, tenant confusion, and unsafe caching.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Implement wallet-policy history and write its API guide. Include revisions, approvals, activation, rollback, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Plan a disaster-recovery strategy for custody services, including keys, policies, wallets, indexers, ledgers, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"core","lang":"en"} -{"prompt":"Add content-hash deduplication to uploaded signing transcripts.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Create the desktop reconciliation workspace with chain balances, ledger entries, discrepancies, linking, and export.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"continue the policy cleanup","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.44,"slice":"vague-eval","lang":"en"} -{"prompt":"Rename `KeyCer` to `KeyCeremony` across packages while preserving serialized event fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why removed allowlist addresses remain usable through one signing worker, implement the verified cache fix, and update operations docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed chain-data cache for fork awareness, tenant isolation, stale finality, provider disagreement, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"Find why a signer retries a permanently rejected quorum request forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Draft a support guide for recovering a transaction stuck before broadcast.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Signer state failure:\n\n```text\nrequest=sg_881 policy_version=72 quorum=3\napproval a1 committed\napproval a2 committed\napproval a3 committed\nsigning session created generation=18\nshare node n2 returns partial signature and times out before receipt commit\ncoordinator retries session generation=19\nn2 reuses deterministic nonce for same request but different session transcript\naggregator combines shares from generation 18 and 19\nsignature verification fails; n2 marks key share unhealthy\n```\n\nDetermine how retry generations permit nonce reuse and cross-session share mixing, and which transcript binding is missing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Add policy version below the approval title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Restructure the signing coordinator and document its participant protocol. Preserve outputs while separating session, quorum, shares, aggregation, and receipts.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.88,"slice":"mixed","lang":"en"} -{"prompt":"Architect a globally distributed chain-indexing platform with network ownership, fork handling, replay, projections, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed reconciliation snapshots with chain heads and liability digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new transaction-policy rule, including inputs, simulation, explanation, fixtures, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Consolidate asset-amount formatting across portal and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Investigate why deprecated token contracts remain in address autocomplete.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional wallet reassignment between organizations with key-policy validation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Set the reorg alert threshold to 8 blocks","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Build the mobile deposit screen with network selection, address, memo, QR, confirmations, and accessible copy actions.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"把 `Withrawal pending` 改成 `Withdrawal pending`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"zh"} -{"prompt":"Inspect the token-list import endpoint for signature bypass, duplicate contracts, decimal changes, remote-image abuse, and tenant confusion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"Implement transaction-simulation history and write its API documentation. Include state block, calls, findings, expiry, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Design a reproducible scientific-workflow platform for simulations, parameter sweeps, checkpoints, datasets, notebooks, provenance, and published results. Cover scheduler integration, immutable environments, retries, quotas, lineage, regional storage, migration from shell scripts, and rollout milestones. Deliver an RFC only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"core","lang":"en"} -{"prompt":"Before implementing ensemble weather forecasts, outline data ingestion, member scheduling, checkpointing, grid consistency, aggregation, late members, publication, validation, and phased rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"boundary","lang":"en"} -{"prompt":"Add NetCDF chunk inspection to `climatectl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Simulation failure output:\n\n```text\nrun=atm_881 model=wrf-5.0 nodes=64 ranks=4096\nstep=1440 simulated_time=2026-07-30T12:00Z\ncheckpoint generation=18 begin\nrank 0 manifest uploaded parts=4095 expected=4096\nrank 2917 object upload timeout after=120s\nscheduler preempts allocation at=12:01:59\nretry resumes generation=18 because manifest state=writing\nmissing rank file is treated as zero-length optional boundary partition\nsimulation advances and pressure field develops NaNs near partition edge\nvalidation checks global file count only after merged output\n```\n\nDetermine why an incomplete distributed checkpoint is considered resumable and why the missing rank is not rejected before computation continues.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"Build the SwiftUI experiment-run screen with status, parameters, resource usage, charts, artifacts, cancellation, and VoiceOver summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Plan and implement a provenance service for scientific datasets and model runs. Begin with a design covering content identity, transformations, environments, external sources, mutable metadata, citations, access, retention, verification, and migration. Then add lineage APIs, signed manifests, query support, and conformance tests. Treat reproducibility semantics as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.97,"slice":"mixed","lang":"en"} -{"prompt":"Set `MAX_ENSEMBLE_MEMBERS` to 100","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Extract duplicated coordinate-axis normalization from forecast and observation readers while preserving values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Implement `/internal/jobs/capacity` with partitions, nodes, accelerators, queued demand, and reservations.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} +{"prompt":"Write a troubleshooting guide for failed withdrawals, covering policy, approval, signing, broadcast, fees, and finality.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Security review packet:\n\n```text\nFeature: temporary withdrawal-limit increase\nOrganization administrator requests higher daily limit with amount, duration, and reason\nTwo different approvers required above configured threshold\nIncrease activates immediately after final approval and lasts up to 24 hours\nPending withdrawals count against both old and new limits\nRevocation returns limit to baseline but does not cancel already approved withdrawals\nApprovers receive simulation of projected exposure\nAudit stores request, approvals, policy version, activation, and expiry\nEmergency administrators may bypass one approver with incident reference\n```\n\nReview approval independence, activation race, pending amounts, revocation, emergency bypass, policy binding, and audit. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add a loading state to the transfer rows","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Plan and implement temporary withdrawal-limit increases. First define approvals, exposure calculation, expiry, revocation, emergency use, audit, and rollout; then add storage and enforcement.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Outline an architecture for chain-agnostic smart-contract risk analysis, including simulation, signatures, provenance, caching, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement snapshot-consistent wallet-statement exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Escribe una guía para integrar una nueva red, con direcciones, transacciones, comisiones, finalidad y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"es"} +{"prompt":"Move confirmation-policy resolution out of the deposit worker without changing credits.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why the iOS app loses transaction filters after returning from background.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add atomic token-metadata publication with approval, signature, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Remove the obsolete `legacy_nonce` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Build the transaction-policy editor with conditions, thresholds, approvals, simulation, conflicts, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"`Transation confirmed` を `Transaction confirmed` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"ja"} +{"prompt":"Review the signed-transaction download path for key material leakage, stale approvals, tenant confusion, and unsafe caching.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement wallet-policy history and write its API guide. Include revisions, approvals, activation, rollback, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan a disaster-recovery strategy for custody services, including keys, policies, wallets, indexers, ledgers, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add content-hash deduplication to uploaded signing transcripts.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Create the desktop reconciliation workspace with chain balances, ledger entries, discrepancies, linking, and export.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Rename `KeyCer` to `KeyCeremony` across packages while preserving serialized event fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why removed allowlist addresses remain usable through one signing worker, implement the verified cache fix, and update operations docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed chain-data cache for fork awareness, tenant isolation, stale finality, provider disagreement, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why a signer retries a permanently rejected quorum request forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft a support guide for recovering a transaction stuck before broadcast.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Signer state failure:\n\n```text\nrequest=sg_881 policy_version=72 quorum=3\napproval a1 committed\napproval a2 committed\napproval a3 committed\nsigning session created generation=18\nshare node n2 returns partial signature and times out before receipt commit\ncoordinator retries session generation=19\nn2 reuses deterministic nonce for same request but different session transcript\naggregator combines shares from generation 18 and 19\nsignature verification fails; n2 marks key share unhealthy\n```\n\nDetermine how retry generations permit nonce reuse and cross-session share mixing, and which transcript binding is missing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add policy version below the approval title","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Restructure the signing coordinator and document its participant protocol. Preserve outputs while separating session, quorum, shares, aggregation, and receipts.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Architect a globally distributed chain-indexing platform with network ownership, fork handling, replay, projections, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1,"slice":"core","lang":"en"} +{"prompt":"Implement signed reconciliation snapshots with chain heads and liability digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new transaction-policy rule, including inputs, simulation, explanation, fixtures, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Consolidate asset-amount formatting across portal and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why deprecated token contracts remain in address autocomplete.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add transactional wallet reassignment between organizations with key-policy validation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Set the reorg alert threshold to 8 blocks","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile deposit screen with network selection, address, memo, QR, confirmations, and accessible copy actions.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"把 `Withrawal pending` 改成 `Withdrawal pending`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"zh"} +{"prompt":"Inspect the token-list import endpoint for signature bypass, duplicate contracts, decimal changes, remote-image abuse, and tenant confusion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement transaction-simulation history and write its API documentation. Include state block, calls, findings, expiry, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Design a reproducible scientific-workflow platform for simulations, parameter sweeps, checkpoints, datasets, notebooks, provenance, and published results. Cover scheduler integration, immutable environments, retries, quotas, lineage, regional storage, migration from shell scripts, and rollout milestones. Deliver an RFC only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Before implementing ensemble weather forecasts, outline data ingestion, member scheduling, checkpointing, grid consistency, aggregation, late members, publication, validation, and phased rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add NetCDF chunk inspection to `climatectl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Simulation failure output:\n\n```text\nrun=atm_881 model=wrf-5.0 nodes=64 ranks=4096\nstep=1440 simulated_time=2026-07-30T12:00Z\ncheckpoint generation=18 begin\nrank 0 manifest uploaded parts=4095 expected=4096\nrank 2917 object upload timeout after=120s\nscheduler preempts allocation at=12:01:59\nretry resumes generation=18 because manifest state=writing\nmissing rank file is treated as zero-length optional boundary partition\nsimulation advances and pressure field develops NaNs near partition edge\nvalidation checks global file count only after merged output\n```\n\nDetermine why an incomplete distributed checkpoint is considered resumable and why the missing rank is not rejected before computation continues.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Build the SwiftUI experiment-run screen with status, parameters, resource usage, charts, artifacts, cancellation, and VoiceOver summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Plan and implement a provenance service for scientific datasets and model runs. Begin with a design covering content identity, transformations, environments, external sources, mutable metadata, citations, access, retention, verification, and migration. Then add lineage APIs, signed manifests, query support, and conformance tests. Treat reproducibility semantics as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":1.0,"slice":"mixed","lang":"en"} +{"prompt":"Set `MAX_ENSEMBLE_MEMBERS` to 100","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Extract duplicated coordinate-axis normalization from forecast and observation readers while preserving values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement `/internal/jobs/capacity` with partitions, nodes, accelerators, queued demand, and reservations.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"make the charts feel scientific","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"Find why CUDA kernels produce stable results on A100 nodes but occasional infinities on H200 nodes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.83,"slice":"core","lang":"en"} -{"prompt":"Explain how `GridReprojector` handles antimeridian cells, polar singularities, and missing values. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Research release notes source:\n\n```text\nFeature: citable dataset snapshots\nResearchers create an immutable snapshot from one dataset revision\nSnapshot includes schema, files, checksums, licenses, and selected metadata\nA DOI can be requested after institutional review\nMetadata corrections after publication create a new descriptive revision without changing file digests\nEmbargoed snapshots are visible only to authorized collaborators until release time\nDeleting a source dataset does not remove a published snapshot\nStorage charges remain with the owning project\n```\n\nTurn this into researcher-facing release notes and a publication guide. Clearly distinguish data immutability from metadata correction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.46,"slice":"pasted-context","lang":"en"} -{"prompt":"Move the chart legend below the color scale","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.13,"slice":"boundary","lang":"en"} -{"prompt":"Write an operator guide for replaying failed observation ingests without duplicating station intervals.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Implement dataset-snapshot endpoints with file selection, checksums, and authorization, then document lifecycle, examples, and errors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Map out a migration from shared NFS scratch space to object-backed workflow storage, including performance, consistency, checkpoints, compatibility, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"core","lang":"en"} -{"prompt":"Rename `gridNo` to `gridNumber` in `ForecastMapper.py`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"en"} -{"prompt":"Teach the batch scheduler to reserve topology-aware GPU groups and release incomplete allocations.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Polish the dataset summary card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.28,"slice":"core","lang":"en"} -{"prompt":"Bump `xarray` to `2026.7.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Rename `MasterDataset` to `PrimaryDataset` across APIs, events, dashboards, and tests while preserving public identifiers.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.64,"slice":"boundary","lang":"en"} -{"prompt":"Split `WorkflowRunner` into planning, staging, execution, checkpointing, and publication components without changing outcomes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.81,"slice":"core","lang":"en"} -{"prompt":"Implementation ticket:\n\n```text\nSCI-611 — station observation corrections\nMeasurements keyed by station, variable, level, and observation time\nProviders may send preliminary, corrected, or final values\nCorrection messages reference provider record ID but may arrive out of order\nFinal values cannot be replaced by preliminary updates\nUnit conversion occurs before quality-control rules\nRaw payload and transformation version must remain available\nDuplicate provider messages are common\nExpose preliminary, corrected, rejected-stale, converted, and quality-failed metrics\n```\n\nImplement the version model, ingest commands, ordering, conversion, quality checks, provenance, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Investigate why the Android field app assigns a sensor reading to the previously selected sampling site.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Create the provenance graph UI and add a short legend for sources, transforms, environments, snapshots, and publications.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Why does the workflow service retain failed checkpoints for 30 days? Explain current debugging behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Rewrite the local setup for running Slurm, MinIO, JupyterHub, and synthetic climate jobs.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.36,"slice":"core","lang":"en"} -{"prompt":"This reprojection test fails after upgrading PROJ:\n\n```text\nsource CRS=EPSG:4326 target CRS=EPSG:3413\ninput lon=-45 lat=90\nexpected x=0 y=0\nactual x=0 y=-1.2e-9\nfixture uses exact equality\nbulk test reports 812 changed cells near pole\nmaximum absolute difference=3.7e-8m\noutput is later quantized to 0.01m\nchecksum fixtures compare pre-quantized floats\n```\n\nDetermine whether the library change is a real projection regression or harmless floating-point drift, and identify which validation layer uses the wrong tolerance.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.69,"slice":"boundary","lang":"en"} -{"prompt":"finish the workflow service","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"Propose an architecture for real-time satellite-data processing, including downlink ingestion, calibration, tiling, cloud masking, provenance, late passes, and publication.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"core","lang":"en"} -{"prompt":"Add GRIB2 bitmap decoding to `weatherdump`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Review excerpt:\n\n```diff\n def publish_result(run_id):\n- manifest = verify_all_outputs(run_id)\n- if not manifest.valid:\n- raise InvalidResult(manifest.errors)\n- registry.publish(run_id, manifest.digest)\n+ future = executor.submit(verify_all_outputs, run_id)\n+ registry.publish(run_id, 'pending')\n+ future.add_done_callback(log_verification)\n```\n\nThe author says verification delays researchers. Review publication semantics, invalid results, immutability, citations, audit, and asynchronous failure. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"pasted-context","lang":"en"} -{"prompt":"Schreibe eine kurze Referenz für die bestehenden Workflow-Status und ihre Auswirkungen auf Artefakte und Wiederaufnahme. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"boundary","lang":"de"} -{"prompt":"Build the desktop geospatial raster viewer with layers, projections, color maps, value inspection, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Review how dataset checksums are calculated and verified, then turn the findings into a publication guide with examples.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"Set the checkpoint interval to 30 minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Benenne `RunCtx` repositoryweit in `RunContext` um; JSON-Felder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"de"} -{"prompt":"Consolidate missing-value normalization across NetCDF and GRIB readers without changing arrays.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Diagnose the duplicate dataset alert","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Explain how the scheduler handles reservations when one node in a tightly coupled job fails health checks.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Create API documentation for the existing workflow-cancellation endpoint, including states, cleanup, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"boundary","lang":"en"} +{"prompt":"Find why CUDA kernels produce stable results on A100 nodes but occasional infinities on H200 nodes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Explain how `GridReprojector` handles antimeridian cells, polar singularities, and missing values. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Research release notes source:\n\n```text\nFeature: citable dataset snapshots\nResearchers create an immutable snapshot from one dataset revision\nSnapshot includes schema, files, checksums, licenses, and selected metadata\nA DOI can be requested after institutional review\nMetadata corrections after publication create a new descriptive revision without changing file digests\nEmbargoed snapshots are visible only to authorized collaborators until release time\nDeleting a source dataset does not remove a published snapshot\nStorage charges remain with the owning project\n```\n\nTurn this into researcher-facing release notes and a publication guide. Clearly distinguish data immutability from metadata correction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"Move the chart legend below the color scale","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Write an operator guide for replaying failed observation ingests without duplicating station intervals.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Implement dataset-snapshot endpoints with file selection, checksums, and authorization, then document lifecycle, examples, and errors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Map out a migration from shared NFS scratch space to object-backed workflow storage, including performance, consistency, checkpoints, compatibility, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Rename `gridNo` to `gridNumber` in `ForecastMapper.py`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Teach the batch scheduler to reserve topology-aware GPU groups and release incomplete allocations.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Polish the dataset summary card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump `xarray` to `2026.7.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename `MasterDataset` to `PrimaryDataset` across APIs, events, dashboards, and tests while preserving public identifiers.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Split `WorkflowRunner` into planning, staging, execution, checkpointing, and publication components without changing outcomes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implementation ticket:\n\n```text\nSCI-611 — station observation corrections\nMeasurements keyed by station, variable, level, and observation time\nProviders may send preliminary, corrected, or final values\nCorrection messages reference provider record ID but may arrive out of order\nFinal values cannot be replaced by preliminary updates\nUnit conversion occurs before quality-control rules\nRaw payload and transformation version must remain available\nDuplicate provider messages are common\nExpose preliminary, corrected, rejected-stale, converted, and quality-failed metrics\n```\n\nImplement the version model, ingest commands, ordering, conversion, quality checks, provenance, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Investigate why the Android field app assigns a sensor reading to the previously selected sampling site.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Create the provenance graph UI and add a short legend for sources, transforms, environments, snapshots, and publications.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Why does the workflow service retain failed checkpoints for 30 days? Explain current debugging behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Rewrite the local setup for running Slurm, MinIO, JupyterHub, and synthetic climate jobs.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"This reprojection test fails after upgrading PROJ:\n\n```text\nsource CRS=EPSG:4326 target CRS=EPSG:3413\ninput lon=-45 lat=90\nexpected x=0 y=0\nactual x=0 y=-1.2e-9\nfixture uses exact equality\nbulk test reports 812 changed cells near pole\nmaximum absolute difference=3.7e-8m\noutput is later quantized to 0.01m\nchecksum fixtures compare pre-quantized floats\n```\n\nDetermine whether the library change is a real projection regression or harmless floating-point drift, and identify which validation layer uses the wrong tolerance.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"finish the workflow service","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Propose an architecture for real-time satellite-data processing, including downlink ingestion, calibration, tiling, cloud masking, provenance, late passes, and publication.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add GRIB2 bitmap decoding to `weatherdump`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Review excerpt:\n\n```diff\n def publish_result(run_id):\n- manifest = verify_all_outputs(run_id)\n- if not manifest.valid:\n- raise InvalidResult(manifest.errors)\n- registry.publish(run_id, manifest.digest)\n+ future = executor.submit(verify_all_outputs, run_id)\n+ registry.publish(run_id, 'pending')\n+ future.add_done_callback(log_verification)\n```\n\nThe author says verification delays researchers. Review publication semantics, invalid results, immutability, citations, audit, and asynchronous failure. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Schreibe eine kurze Referenz für die bestehenden Workflow-Status und ihre Auswirkungen auf Artefakte und Wiederaufnahme. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"de"} +{"prompt":"Build the desktop geospatial raster viewer with layers, projections, color maps, value inspection, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Review how dataset checksums are calculated and verified, then turn the findings into a publication guide with examples.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Set the checkpoint interval to 30 minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Benenne `RunCtx` repositoryweit in `RunContext` um; JSON-Felder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"de"} +{"prompt":"Consolidate missing-value normalization across NetCDF and GRIB readers without changing arrays.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose the duplicate dataset alert","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Explain how the scheduler handles reservations when one node in a tightly coupled job fails health checks.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Create API documentation for the existing workflow-cancellation endpoint, including states, cleanup, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Plan a migration from ad hoc Conda environments to signed OCI research environments, covering reproducibility, GPUs, secrets, storage, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Visualization ticket:\n\n```text\nPage: ensemble forecast explorer\nControls: variable, pressure level, forecast time, member, aggregation\nMap: mean field with optional spread overlay\nChart: point forecast showing all members plus percentiles\nTime controls must retain selected geographic point\nMissing members shown explicitly; do not treat as zero\nColor scales have units and accessible text alternatives\nLarge datasets load progressively without resetting zoom\nComparison mode pins two model runs with matched valid times\n```\n\nImplement the responsive explorer and component tests using existing forecast APIs.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.76,"slice":"pasted-context","lang":"en"} -{"prompt":"Implement `POST /v1/runs/{id}/resume` with checkpoint validation, environment matching, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"boundary","lang":"en"} -{"prompt":"Remove the extra unit from the axis label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"core","lang":"en"} -{"prompt":"Fix the clipped map tooltip and extract its duplicated viewport inset into shared styles.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.36,"slice":"mixed","lang":"en"} -{"prompt":"Replace scattered run booleans with one explicit workflow lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Cambia `gridRev` por `gridRevision` solo en `ForecastState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"es"} -{"prompt":"Investigate why the research portal briefly shows another project's private dataset after workspace switching.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Summarize the current dataset-publication lifecycle for research-integrity reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"Develop a capacity roadmap for storing and serving 200 PB of climate data. Include chunking, tiers, catalogs, query patterns, integrity, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"core","lang":"en"} -{"prompt":"Implement idempotent model-output ingestion with run generations and correction support.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Create the Compose field-observation form with site, variables, units, quality flags, offline queue, and TalkBack support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Fix `preciptation` in `variables.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} -{"prompt":"Merge duplicate spatial-bounds types used by catalog and visualization while preserving serialized values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Forecast publication incident:\n\n```text\nrun=gfs_20260730_00 member=control\noutput valid_times=0..384h\npublication manifest generation=771 references 129 files\nobject-store list was eventually consistent and omitted hour=240\nmanifest validator expected at least 120 files, passed\ncatalog published run complete\nfile hour=240 appeared 14s later but was not in immutable manifest\nusers receive gap at one forecast time\nretry refuses new manifest because run marked published\n```\n\nDetermine why count-based validation and eventual listing produced an incomplete immutable publication and how completeness should have been established.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Rename `longtitude` to `longitude` in the unreleased schema.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"en"} -{"prompt":"Assess whether shared notebook environments can expose another project's mounted datasets or credentials. Review isolation only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Restructure the climate SDK into catalog, datasets, grids, forecasts, and provenance, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.75,"slice":"mixed","lang":"en"} -{"prompt":"Plan the retirement of legacy FTP observation delivery, covering providers, parity, acknowledgements, migration, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.83,"slice":"core","lang":"en"} +{"prompt":"Visualization ticket:\n\n```text\nPage: ensemble forecast explorer\nControls: variable, pressure level, forecast time, member, aggregation\nMap: mean field with optional spread overlay\nChart: point forecast showing all members plus percentiles\nTime controls must retain selected geographic point\nMissing members shown explicitly; do not treat as zero\nColor scales have units and accessible text alternatives\nLarge datasets load progressively without resetting zoom\nComparison mode pins two model runs with matched valid times\n```\n\nImplement the responsive explorer and component tests using existing forecast APIs.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Implement `POST /v1/runs/{id}/resume` with checkpoint validation, environment matching, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remove the extra unit from the axis label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fix the clipped map tooltip and extract its duplicated viewport inset into shared styles.","purpose":"frontendImpl","secondary":"refactor","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Replace scattered run booleans with one explicit workflow lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Cambia `gridRev` por `gridRevision` solo en `ForecastState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"es"} +{"prompt":"Investigate why the research portal briefly shows another project's private dataset after workspace switching.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Summarize the current dataset-publication lifecycle for research-integrity reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Develop a capacity roadmap for storing and serving 200 PB of climate data. Include chunking, tiers, catalogs, query patterns, integrity, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement idempotent model-output ingestion with run generations and correction support.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the Compose field-observation form with site, variables, units, quality flags, offline queue, and TalkBack support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Fix `preciptation` in `variables.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Merge duplicate spatial-bounds types used by catalog and visualization while preserving serialized values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Forecast publication incident:\n\n```text\nrun=gfs_20260730_00 member=control\noutput valid_times=0..384h\npublication manifest generation=771 references 129 files\nobject-store list was eventually consistent and omitted hour=240\nmanifest validator expected at least 120 files, passed\ncatalog published run complete\nfile hour=240 appeared 14s later but was not in immutable manifest\nusers receive gap at one forecast time\nretry refuses new manifest because run marked published\n```\n\nDetermine why count-based validation and eventual listing produced an incomplete immutable publication and how completeness should have been established.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Rename `longtitude` to `longitude` in the unreleased schema.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Assess whether shared notebook environments can expose another project's mounted datasets or credentials. Review isolation only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Restructure the climate SDK into catalog, datasets, grids, forecasts, and provenance, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan the retirement of legacy FTP observation delivery, covering providers, parity, acknowledgements, migration, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Add immutable provenance chains to calibrated satellite scenes.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Build the tablet sampling-route view with sites, offline maps, collection state, navigation, and accessible list fallback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"do the forecast page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `DataRef` with `DatasetReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why published figures use an older dataset revision, implement the verified snapshot-binding fix, and add a researcher note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"Why does the workflow service retain two previous container images after environment updates? Explain rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.46,"slice":"boundary","lang":"en"} -{"prompt":"Track down the memory leak in raster tilers after processing high-band-count scenes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Write release notes for parameter-sweep comparisons, including aggregation, missing runs, exports, and limits.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.36,"slice":"core","lang":"en"} -{"prompt":"Workflow checkpoint notes:\n\n```text\nCurrent checkpoints are opaque directories written by each model\nNew platform needs portable checkpoint manifests\nFiles may be shared across ranks through hard links\nA checkpoint is valid only when all ranks complete a barrier\nEnvironment, executable, configuration, and input dataset revisions must be captured\nUsers may resume with more nodes only if model declares repartition support\nPartial checkpoints should remain available for debugging but never resume automatically\nOld model versions emit no schema version\n```\n\nProduce an implementation-free format and migration plan covering completeness, identity, portability, validation, partial artifacts, compatibility, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"pasted-context","lang":"en"} -{"prompt":"Give the run list clearer state grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.31,"slice":"core","lang":"en"} -{"prompt":"Turn the current data-embargo behavior into researcher documentation, then review whether release timing and access claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Outline a phased architecture for moving workflow metadata from MongoDB to Postgres, without implementing migrations.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.82,"slice":"boundary","lang":"en"} -{"prompt":"Implement version-aware station metadata history with effective dates and correction links.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Build the tablet sampling-route view with sites, offline maps, collection state, navigation, and accessible list fallback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"do the forecast page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `DataRef` with `DatasetReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose why published figures use an older dataset revision, implement the verified snapshot-binding fix, and add a researcher note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Why does the workflow service retain two previous container images after environment updates? Explain rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down the memory leak in raster tilers after processing high-band-count scenes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write release notes for parameter-sweep comparisons, including aggregation, missing runs, exports, and limits.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Workflow checkpoint notes:\n\n```text\nCurrent checkpoints are opaque directories written by each model\nNew platform needs portable checkpoint manifests\nFiles may be shared across ranks through hard links\nA checkpoint is valid only when all ranks complete a barrier\nEnvironment, executable, configuration, and input dataset revisions must be captured\nUsers may resume with more nodes only if model declares repartition support\nPartial checkpoints should remain available for debugging but never resume automatically\nOld model versions emit no schema version\n```\n\nProduce an implementation-free format and migration plan covering completeness, identity, portability, validation, partial artifacts, compatibility, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Give the run list clearer state grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Turn the current data-embargo behavior into researcher documentation, then review whether release timing and access claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Outline a phased architecture for moving workflow metadata from MongoDB to Postgres, without implementing migrations.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement version-aware station metadata history with effective dates and correction links.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Create an operator guide for diagnosing Slurm jobs stuck in completing state.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Move unit-conversion selection out of `ObservationController` while preserving values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Investigate why revoked collaborators retain access through one dataset tile cache.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"Add generation-fenced model-configuration publication with validation and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Set the plot export DPI to 300","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Create the responsive dataset-browser with facets, previews, licenses, lineage, downloads, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Corrige apenas `temprature` para `temperature` no novo gráfico.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"pt"} -{"prompt":"Review the notebook-export endpoint for embedded credentials, private file leakage, unsafe HTML, huge outputs, and stale authorization.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Implement workflow-run history and write its API guide. Include inputs, environment, checkpoints, outputs, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Design a migration from static station files to a versioned geospatial registry, including identity, moves, corrections, compatibility, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"core","lang":"en"} -{"prompt":"Add resumable multi-file dataset uploads with checksums and atomic publication.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} +{"prompt":"Move unit-conversion selection out of `ObservationController` while preserving values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why revoked collaborators retain access through one dataset tile cache.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add generation-fenced model-configuration publication with validation and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Set the plot export DPI to 300","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Create the responsive dataset-browser with facets, previews, licenses, lineage, downloads, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Corrige apenas `temprature` para `temperature` no novo gráfico.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"pt"} +{"prompt":"Review the notebook-export endpoint for embedded credentials, private file leakage, unsafe HTML, huge outputs, and stale authorization.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement workflow-run history and write its API guide. Include inputs, environment, checkpoints, outputs, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Design a migration from static station files to a versioned geospatial registry, including identity, moves, corrections, compatibility, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add resumable multi-file dataset uploads with checksums and atomic publication.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Build the desktop ensemble-comparison view with synchronized maps, distributions, valid times, and export.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"continue the checkpoint bug","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.56,"slice":"vague-eval","lang":"en"} -{"prompt":"Extract coordinate-reference normalization into one shared module while preserving identifiers.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why observation alerts use an outdated station elevation, implement the verified metadata-version fix, and update operator docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.77,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed public forecast cache for embargoes, licensing, stale corrections, regional policy, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Find why one workflow partition retries an impossible resource request forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Draft a migration guide for researchers moving from local scripts to managed workflows.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} -{"prompt":"Numerical validation report:\n\n```text\nmodel=ocean_v12 baseline compiler=gcc-14 new compiler=gcc-15\nrun length=30 days\nsea_surface_height max_abs_diff=1.8e-7 day=1\nmax_abs_diff=2.1e-3 day=30\nenergy conservation baseline drift=0.0012% new drift=0.0013%\nbitwise checksum mismatch from first timestep\nstatistical climatology remains within tolerance\nvalidation pipeline requires bitwise equality for restart files\nnew compiler enables fused multiply-add in one kernel\n```\n\nDetermine whether the divergence is an unacceptable reproducibility regression or expected chaotic amplification, and which validation criteria should govern restart compatibility versus scientific equivalence.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Add valid-time text below the forecast title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.24,"slice":"core","lang":"en"} -{"prompt":"Restructure the observation pipeline and document its provider interface. Preserve data while separating decode, normalize, quality control, correction, and publication.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"Architect a multi-region scientific-data platform with dataset ownership, provenance, publication, compute locality, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed workflow manifests with environment, inputs, parameters, and output digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new forecast model, including grids, variables, workflows, validation, and publication.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.47,"slice":"core","lang":"en"} -{"prompt":"Consolidate scientific-time formatting across catalog and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Investigate why withdrawn datasets remain in public catalog autocomplete.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.61,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional dataset ownership transfer with permission remapping and provenance.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Pin GDAL to `3.11.3`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Build the mobile field-sample history with sites, variables, quality, sync state, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Remplace `Forcast` par `Forecast` uniquement dans le nouveau titre.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"fr"} -{"prompt":"Inspect the workflow-definition import path for command injection, unsafe mounts, secret exposure, huge DAGs, and tenant confusion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Implement dataset-publication history and write its API documentation. Include revisions, reviews, embargoes, DOI status, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Develop a roadmap for replacing manually curated quality rules with versioned executable policies, including simulation, approval, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"core","lang":"en"} -{"prompt":"Add bounded event replay for forecast-catalog projections with checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Create the responsive workflow-template gallery with filters, versions, inputs, preview, and accessible selection.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"fix the map colors","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.34,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `GridEvt` with `GridEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why completed runs still trigger stalled-job alerts, implement the verified projection fix, and update runbook documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.73,"slice":"mixed","lang":"en"} -{"prompt":"Why does the catalog retain two previous metadata schemas? Explain current compatibility and rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.47,"slice":"boundary","lang":"en"} -{"prompt":"Track down occasional missing chunks in Zarr dataset reads.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Write a troubleshooting guide for failed workflows, covering staging, quotas, environments, checkpoints, and publication.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Security review packet:\n\n```text\nFeature: shareable research result link\nCreator selects one published result and expiry up to 30 days\nRecipient does not need an account\nLink grants read-only access to plots, metadata, and selected output files\nEmbargoed datasets are excluded by UI but not independently checked by link service\nToken appears in URL path\nCreator may revoke early\nDownloads are logged with truncated IP and user agent\nLinked files may reveal paths containing project names\nCDN caches successful responses for one hour\n```\n\nReview embargo enforcement, token leakage, file scope, path metadata, revocation, caching, privacy, and audit. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a loading state to the run cards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Plan and implement project-defined data retention. First define precedence, published snapshots, citations, holds, scratch data, deletion proof, and rollout; then add policy storage and enforcement.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.94,"slice":"mixed","lang":"en"} -{"prompt":"Outline an architecture for federated scientific-data search across institutions, including identity, authorization, metadata, ranking, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"boundary","lang":"en"} -{"prompt":"Implement snapshot-consistent experiment exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Escribe una guía para integrar observaciones científicas, con unidades, tiempos, calidad, correcciones y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} -{"prompt":"Move dataset-license resolution out of the download handler without changing access.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Investigate why the iOS field app loses queued samples after restoring a backup.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Add atomic variable-registry publication with validation, approval, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Remove the obsolete `legacy_grid` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"core","lang":"en"} -{"prompt":"Build the dataset-version comparison view with schemas, files, metadata, provenance, and keyboard navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"`Temprature anomaly` を `Temperature anomaly` に直して。新しい英語ラベルだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"ja"} -{"prompt":"Review the public raster-tile endpoint for embargo leakage, expensive ranges, crafted coordinates, cache confusion, and tenant bypass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"Implement model-run comparison history and write its API guide. Include runs, variables, metrics, artifacts, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Plan a disaster-recovery strategy for scientific workflows, including datasets, environments, checkpoints, catalogs, keys, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Add content-hash deduplication to uploaded observation files with provider provenance.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Create the desktop workflow editor with DAG layout, parameters, validation, versioning, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"continue the dataset cleanup","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.44,"slice":"vague-eval","lang":"en"} -{"prompt":"Rename `RunRev` to `RunRevision` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why revoked collaborators still receive workflow completion emails, implement the verified recipient fix, and update user documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed notebook-result cache for project isolation, mutable environments, stale datasets, credentials, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"Find why a workflow worker retries a permanently unsupported GPU request forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Draft a support guide for recovering an interrupted dataset publication.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Projection failure output:\n\n```text\ndataset=d_881 revision=14 publication event offset=99218\ncatalog projection writes status=published and searchable=true\ncheckpoint transaction fails after database failover\nDOI worker observes published state and registers identifier\nprojection restarts from previous offset\nreplays publication against already-published state and rejects duplicate transition\npartition stops; DOI exists but publication event remains uncheckpointed\n```\n\nDetermine how projection, checkpoint, and DOI registration lack one durable boundary and why replay cannot recognize the prior application.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Add source count below the dataset title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} +{"prompt":"Extract coordinate-reference normalization into one shared module while preserving identifiers.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why observation alerts use an outdated station elevation, implement the verified metadata-version fix, and update operator docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed public forecast cache for embargoes, licensing, stale corrections, regional policy, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why one workflow partition retries an impossible resource request forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft a migration guide for researchers moving from local scripts to managed workflows.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Numerical validation report:\n\n```text\nmodel=ocean_v12 baseline compiler=gcc-14 new compiler=gcc-15\nrun length=30 days\nsea_surface_height max_abs_diff=1.8e-7 day=1\nmax_abs_diff=2.1e-3 day=30\nenergy conservation baseline drift=0.0012% new drift=0.0013%\nbitwise checksum mismatch from first timestep\nstatistical climatology remains within tolerance\nvalidation pipeline requires bitwise equality for restart files\nnew compiler enables fused multiply-add in one kernel\n```\n\nDetermine whether the divergence is an unacceptable reproducibility regression or expected chaotic amplification, and which validation criteria should govern restart compatibility versus scientific equivalence.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add valid-time text below the forecast title","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Restructure the observation pipeline and document its provider interface. Preserve data while separating decode, normalize, quality control, correction, and publication.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Architect a multi-region scientific-data platform with dataset ownership, provenance, publication, compute locality, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement signed workflow manifests with environment, inputs, parameters, and output digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new forecast model, including grids, variables, workflows, validation, and publication.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Consolidate scientific-time formatting across catalog and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why withdrawn datasets remain in public catalog autocomplete.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add transactional dataset ownership transfer with permission remapping and provenance.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Pin GDAL to `3.11.3`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile field-sample history with sites, variables, quality, sync state, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remplace `Forcast` par `Forecast` uniquement dans le nouveau titre.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"fr"} +{"prompt":"Inspect the workflow-definition import path for command injection, unsafe mounts, secret exposure, huge DAGs, and tenant confusion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement dataset-publication history and write its API documentation. Include revisions, reviews, embargoes, DOI status, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Develop a roadmap for replacing manually curated quality rules with versioned executable policies, including simulation, approval, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add bounded event replay for forecast-catalog projections with checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the responsive workflow-template gallery with filters, versions, inputs, preview, and accessible selection.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"fix the map colors","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `GridEvt` with `GridEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose why completed runs still trigger stalled-job alerts, implement the verified projection fix, and update runbook documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the catalog retain two previous metadata schemas? Explain current compatibility and rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down occasional missing chunks in Zarr dataset reads.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write a troubleshooting guide for failed workflows, covering staging, quotas, environments, checkpoints, and publication.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Security review packet:\n\n```text\nFeature: shareable research result link\nCreator selects one published result and expiry up to 30 days\nRecipient does not need an account\nLink grants read-only access to plots, metadata, and selected output files\nEmbargoed datasets are excluded by UI but not independently checked by link service\nToken appears in URL path\nCreator may revoke early\nDownloads are logged with truncated IP and user agent\nLinked files may reveal paths containing project names\nCDN caches successful responses for one hour\n```\n\nReview embargo enforcement, token leakage, file scope, path metadata, revocation, caching, privacy, and audit. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add a loading state to the run cards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Plan and implement project-defined data retention. First define precedence, published snapshots, citations, holds, scratch data, deletion proof, and rollout; then add policy storage and enforcement.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Outline an architecture for federated scientific-data search across institutions, including identity, authorization, metadata, ranking, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement snapshot-consistent experiment exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Escribe una guía para integrar observaciones científicas, con unidades, tiempos, calidad, correcciones y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"es"} +{"prompt":"Move dataset-license resolution out of the download handler without changing access.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Investigate why the iOS field app loses queued samples after restoring a backup.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add atomic variable-registry publication with validation, approval, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Remove the obsolete `legacy_grid` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the dataset-version comparison view with schemas, files, metadata, provenance, and keyboard navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"`Temprature anomaly` を `Temperature anomaly` に直して。新しい英語ラベルだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"ja"} +{"prompt":"Review the public raster-tile endpoint for embargo leakage, expensive ranges, crafted coordinates, cache confusion, and tenant bypass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement model-run comparison history and write its API guide. Include runs, variables, metrics, artifacts, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan a disaster-recovery strategy for scientific workflows, including datasets, environments, checkpoints, catalogs, keys, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add content-hash deduplication to uploaded observation files with provider provenance.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the desktop workflow editor with DAG layout, parameters, validation, versioning, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Rename `RunRev` to `RunRevision` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why revoked collaborators still receive workflow completion emails, implement the verified recipient fix, and update user documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed notebook-result cache for project isolation, mutable environments, stale datasets, credentials, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why a workflow worker retries a permanently unsupported GPU request forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft a support guide for recovering an interrupted dataset publication.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Projection failure output:\n\n```text\ndataset=d_881 revision=14 publication event offset=99218\ncatalog projection writes status=published and searchable=true\ncheckpoint transaction fails after database failover\nDOI worker observes published state and registers identifier\nprojection restarts from previous offset\nreplays publication against already-published state and rejects duplicate transition\npartition stops; DOI exists but publication event remains uncheckpointed\n```\n\nDetermine how projection, checkpoint, and DOI registration lack one durable boundary and why replay cannot recognize the prior application.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add source count below the dataset title","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"Restructure the dataset catalog and document its metadata-provider interface. Preserve results while separating ingest, normalize, validate, index, and publish.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Architect a global forecast-delivery platform with model ownership, regional caches, publication, corrections, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed dataset receipts with schema, file count, and content digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new quality-control rule, including inputs, flags, fixtures, review, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Consolidate variable-name formatting across portal and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Investigate why corrected station coordinates remain stale in map search.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.61,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional project transfer with dataset permissions and immutable provenance.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Pin NumPy to `2.3.2`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Build the mobile experiment-status screen with stages, resources, logs, outputs, cancellation, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"把 `Forcast run` 改成 `Forecast run`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"zh"} -{"prompt":"Inspect the dataset-archive importer for path traversal, decompression bombs, schema spoofing, huge metadata, and tenant confusion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Implement workflow-template history and write its API documentation. Include versions, validation, publication, rollback, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Design a reservation architecture for hotels, tours, and transportation inventory. Cover availability, holds, pricing snapshots, modifications, cancellations, overbooking, supplier reconciliation, multi-currency, regional failure, and migration from product-specific booking tables. Deliver an RFC and rollout plan only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"core","lang":"en"} -{"prompt":"Before implementing multi-city itineraries, outline the domain model, availability checks, partial failures, fare guarantees, schedule changes, cancellation, notifications, and phased launch.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"boundary","lang":"en"} -{"prompt":"Add hold expiry to `/v2/reservations`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Booking incident logs:\n\n```text\nproperty=h_882 room_type=deluxe date=2026-08-14\ninventory total=12 sold=11 held=1\nhold hd_71 expires=15:01:00Z\ncheckout request bk_91 confirms hold at=15:00:59.812\nexpiry worker reads hold active at=15:01:00.004\nbooking transaction commits at=15:01:00.019\nexpiry transaction releases inventory at=15:01:00.026\nsupplier confirmation succeeds\navailability projection now shows one room available\nsecond booking accepted and supplier rejects overbooked\n```\n\nDetermine how confirmation and expiry both mutate the same hold and why locking or state preconditions fail to serialize them.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Build the SwiftUI itinerary screen with day groups, booking status, maps, tickets, disruption alerts, and VoiceOver-friendly chronology.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Plan and implement a booking-modification service. Begin with a design covering repricing, supplier capabilities, atomic versus partial changes, payment adjustments, deadlines, idempotency, audit, notifications, and rollback. Then add quote, confirm, state, and reconciliation APIs with integration tests. Treat modification semantics as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.97,"slice":"mixed","lang":"en"} -{"prompt":"Set `HOLD_TTL_MINUTES` to 12","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Extract duplicated airport-code normalization from search and itinerary imports while preserving validation.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"core","lang":"en"} -{"prompt":"Implement `/internal/suppliers/status` with latency, error rate, last sync, circuit state, and inventory lag.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} -{"prompt":"make the hotel page dreamy","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.42,"slice":"vague-eval","lang":"en"} -{"prompt":"Find why the Android app occasionally shows yesterday's train departure after a schedule update.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Explain how `AvailabilityMerger` combines direct inventory, cached supplier results, and stop-sell rules. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Traveler release notes source:\n\n```text\nFeature: shared itineraries\nTrip owner invites up to ten collaborators\nCollaborators may view all itinerary items and add notes\nOnly owner can add, modify, or cancel bookings\nInvite links expire after seven days\nRemoving a collaborator blocks new access immediately\nDownloaded tickets previously saved to the collaborator's device are not remotely deleted\nNotes show author and edit history\nPrice and payment details can be hidden by the owner\n```\n\nTurn this into release notes and a help article with clear role, privacy, offline-ticket, and revocation limitations.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.46,"slice":"pasted-context","lang":"en"} -{"prompt":"Move the room amenity icons below the rate name","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.13,"slice":"boundary","lang":"en"} -{"prompt":"Write an operator guide for replaying failed supplier confirmations without creating duplicate bookings.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Implement booking-document endpoints with type filters, signed downloads, and authorization, then document expiry, examples, and errors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.67,"slice":"mixed","lang":"en"} -{"prompt":"Map out a migration from cached nightly hotel rates to live priced offers, including latency, fallback, taxes, currency, parity, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"core","lang":"en"} -{"prompt":"Rename `tripNo` to `tripNumber` in `ItineraryMapper.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"en"} -{"prompt":"Teach the supplier connector to resume paginated inventory syncs from durable cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Polish the fare summary card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.28,"slice":"core","lang":"en"} -{"prompt":"Bump `mapbox-maps-ios` to `11.14.2`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Rename `MasterItinerary` to `PrimaryItinerary` across services, events, tests, and dashboards while preserving public fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.64,"slice":"boundary","lang":"en"} -{"prompt":"Split `BookingService` into quote, hold, confirm, modify, cancel, and reconciliation components without changing outcomes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.83,"slice":"core","lang":"en"} -{"prompt":"Implementation ticket:\n\n```text\nTRAVEL-5120 — supplier schedule-change processing\nChanges include departure time, arrival time, terminal, equipment, segment cancellation\nEach supplier update has booking reference, segment ID, source version, and effective time\nOut-of-order updates are common\nMaterial changes require traveler acknowledgement\nMinor changes update itinerary silently but generate audit event\nSegment cancellation may create rebooking options\nDuplicate notifications must be suppressed\nOld itinerary versions remain available for support\nExpose received, stale, material, acknowledged, and rebook-required metrics\n```\n\nImplement ingestion, ordering, materiality rules, itinerary revisions, acknowledgement, options, notifications, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.87,"slice":"pasted-context","lang":"en"} -{"prompt":"Investigate why the iOS boarding-pass wallet card shows an old gate after a terminal change.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Create the rebooking-options UI and add a concise guide for fare difference, connection risk, deadlines, and confirmation.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.67,"slice":"mixed","lang":"en"} -{"prompt":"Why does the pricing service preserve the original exchange rate after a booking modification? Explain current accounting behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.48,"slice":"core","lang":"en"} -{"prompt":"Rewrite the local setup for running WireMock suppliers, Postgres, Kafka, and sample booking fixtures.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.34,"slice":"core","lang":"en"} -{"prompt":"This date test fails for one overnight route:\n\n```text\norigin=Pacific/Apia destination=Pacific/Honolulu\ndeparture local=2026-08-18T23:30+13:00\narrival local=2026-08-18T10:20-10:00\nduration expected=10h50m actual=10h50m\nitinerary day grouping expected arrival on day 2\nactual arrival grouped with departure on day 1\nfixture groups by traveler home zone=Europe/London\nUI groups each segment by origin local date\nproduct requirement says itinerary day follows destination local calendar\n```\n\nDetermine which calendar semantics are inconsistent and why duration correctness does not settle the grouping behavior.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"finish the reservation endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} -{"prompt":"Propose an architecture for disruption recovery, including event ingestion, affected travelers, option generation, inventory, notification, self-service, and agent escalation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Add OpenTravel Alliance XML parsing to `supplierctl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Review excerpt:\n\n```diff\n async function confirmBooking(req) {\n- const quote = await quotes.requireValid(req.body.quoteId)\n- const result = await supplier.confirm(quote)\n- await bookings.persist(result, quote)\n+ supplier.confirmById(req.body.quoteId).catch(logger.warn)\n+ await bookings.persistPending(req.body.quoteId)\n return { status: 'confirmed' }\n }\n```\n\nThe author says waiting for suppliers hurts conversion. Review response semantics, missing quote validation, supplier failure, duplicate requests, persistence, reconciliation, and traveler expectations. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"pasted-context","lang":"en"} -{"prompt":"Schreibe eine kurze Referenz für die bestehenden Buchungsstatus und ihre Auswirkungen auf Zahlung und Stornierung. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"boundary","lang":"de"} -{"prompt":"Build the desktop operations itinerary viewer with segment states, supplier references, changes, payments, and keyboard navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Review how cancellation penalties are calculated and displayed, then turn the findings into an agent guide with examples.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.62,"slice":"mixed","lang":"en"} -{"prompt":"Set the supplier timeout to 8s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Benenne `TripCtx` repositoryweit in `TripContext` um; JSON-Felder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"de"} -{"prompt":"Consolidate traveler-name formatting across tickets and itineraries without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"core","lang":"en"} -{"prompt":"Diagnose the duplicate booking email","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Explain how the offer cache handles stop-sell updates while checkout is in progress.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Create API documentation for the existing cancellation-quote endpoint, including penalties, expiry, currency, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"en"} -{"prompt":"Plan a migration from property-local room IDs to supplier-neutral accommodation units, including mapping, history, compatibility, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.87,"slice":"core","lang":"en"} -{"prompt":"Mobile design ticket:\n\n```text\nScreen: booking confirmation\nSummary: status, confirmation number, supplier, total paid\nSections vary by hotel, rail, flight, and activity\nPending supplier confirmation must not look final\nDocuments may arrive asynchronously\nChange and cancel actions depend on fare rules and deadlines\nOffline mode shows last confirmed itinerary with stale timestamp\nAccessibility: confirmation number has copy action; status announced before decorative artwork\nSupport action includes booking reference but not payment details\n```\n\nImplement the responsive Compose screen and tests using existing booking models.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"pasted-context","lang":"en"} -{"prompt":"Implement `POST /v1/bookings/{id}/acknowledge-change` with revision checks and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Remove the extra slash from the ticket link","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"core","lang":"en"} -{"prompt":"Fix the clipped fare badge and extract its duplicated padding into the shared booking token.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.35,"slice":"mixed","lang":"en"} -{"prompt":"Replace scattered booking booleans with one explicit lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Cambia `segRev` por `segmentRevision` solo en `ItineraryState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"es"} -{"prompt":"Investigate why the traveler app briefly shows another account's upcoming trip after logout and login.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Summarize the current booking-reconciliation lifecycle for finance and operations reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"Develop a capacity roadmap for handling 500,000 booking attempts per minute during major events. Include offers, holds, suppliers, payments, queues, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"core","lang":"en"} -{"prompt":"Implement idempotent loyalty-status ingestion with effective dates and corrections.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Create the SwiftUI hotel-search screen with map, filters, dates, guests, loading states, and VoiceOver summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Fix `reservaton` in `events.proto`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} -{"prompt":"Merge duplicate fare-rule normalization paths used by search and servicing while preserving decisions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Supplier sync failure:\n\n```text\nsupplier=s_81 property=h_992 sync_generation=441\npage 1 cursor=a rows=500 committed\npage 2 cursor=b rows=500 committed\npage 3 cursor=c request timeout\nretry begins from cursor=b due checkpoint lag\npage 2 applies room closures version=92\nsupplier then returns page 3 with reopen version=93\nlate original page 2 response arrives after page 3 and applies closure version=92\nadapter does not pass supplier versions into inventory store\nproperty becomes falsely unavailable\n```\n\nDetermine how cursor retry and response reordering permit stale inventory to overwrite newer state and which version data is discarded.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Rename `arival_time` to `arrival_time` in the unreleased schema.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"en"} +{"prompt":"Architect a global forecast-delivery platform with model ownership, regional caches, publication, corrections, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement signed dataset receipts with schema, file count, and content digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new quality-control rule, including inputs, flags, fixtures, review, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Consolidate variable-name formatting across portal and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why corrected station coordinates remain stale in map search.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add transactional project transfer with dataset permissions and immutable provenance.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Pin NumPy to `2.3.2`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile experiment-status screen with stages, resources, logs, outputs, cancellation, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"把 `Forcast run` 改成 `Forecast run`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"zh"} +{"prompt":"Inspect the dataset-archive importer for path traversal, decompression bombs, schema spoofing, huge metadata, and tenant confusion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement workflow-template history and write its API documentation. Include versions, validation, publication, rollback, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Design a reservation architecture for hotels, tours, and transportation inventory. Cover availability, holds, pricing snapshots, modifications, cancellations, overbooking, supplier reconciliation, multi-currency, regional failure, and migration from product-specific booking tables. Deliver an RFC and rollout plan only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Before implementing multi-city itineraries, outline the domain model, availability checks, partial failures, fare guarantees, schedule changes, cancellation, notifications, and phased launch.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add hold expiry to `/v2/reservations`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Booking incident logs:\n\n```text\nproperty=h_882 room_type=deluxe date=2026-08-14\ninventory total=12 sold=11 held=1\nhold hd_71 expires=15:01:00Z\ncheckout request bk_91 confirms hold at=15:00:59.812\nexpiry worker reads hold active at=15:01:00.004\nbooking transaction commits at=15:01:00.019\nexpiry transaction releases inventory at=15:01:00.026\nsupplier confirmation succeeds\navailability projection now shows one room available\nsecond booking accepted and supplier rejects overbooked\n```\n\nDetermine how confirmation and expiry both mutate the same hold and why locking or state preconditions fail to serialize them.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Build the SwiftUI itinerary screen with day groups, booking status, maps, tickets, disruption alerts, and VoiceOver-friendly chronology.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Plan and implement a booking-modification service. Begin with a design covering repricing, supplier capabilities, atomic versus partial changes, payment adjustments, deadlines, idempotency, audit, notifications, and rollback. Then add quote, confirm, state, and reconciliation APIs with integration tests. Treat modification semantics as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Set `HOLD_TTL_MINUTES` to 12","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Extract duplicated airport-code normalization from search and itinerary imports while preserving validation.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement `/internal/suppliers/status` with latency, error rate, last sync, circuit state, and inventory lag.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"make the hotel page dreamy","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Find why the Android app occasionally shows yesterday's train departure after a schedule update.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Explain how `AvailabilityMerger` combines direct inventory, cached supplier results, and stop-sell rules. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Traveler release notes source:\n\n```text\nFeature: shared itineraries\nTrip owner invites up to ten collaborators\nCollaborators may view all itinerary items and add notes\nOnly owner can add, modify, or cancel bookings\nInvite links expire after seven days\nRemoving a collaborator blocks new access immediately\nDownloaded tickets previously saved to the collaborator's device are not remotely deleted\nNotes show author and edit history\nPrice and payment details can be hidden by the owner\n```\n\nTurn this into release notes and a help article with clear role, privacy, offline-ticket, and revocation limitations.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} +{"prompt":"Move the room amenity icons below the rate name","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Write an operator guide for replaying failed supplier confirmations without creating duplicate bookings.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement booking-document endpoints with type filters, signed downloads, and authorization, then document expiry, examples, and errors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Map out a migration from cached nightly hotel rates to live priced offers, including latency, fallback, taxes, currency, parity, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Rename `tripNo` to `tripNumber` in `ItineraryMapper.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Teach the supplier connector to resume paginated inventory syncs from durable cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Polish the fare summary card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump `mapbox-maps-ios` to `11.14.2`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Rename `MasterItinerary` to `PrimaryItinerary` across services, events, tests, and dashboards while preserving public fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Split `BookingService` into quote, hold, confirm, modify, cancel, and reconciliation components without changing outcomes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implementation ticket:\n\n```text\nTRAVEL-5120 — supplier schedule-change processing\nChanges include departure time, arrival time, terminal, equipment, segment cancellation\nEach supplier update has booking reference, segment ID, source version, and effective time\nOut-of-order updates are common\nMaterial changes require traveler acknowledgement\nMinor changes update itinerary silently but generate audit event\nSegment cancellation may create rebooking options\nDuplicate notifications must be suppressed\nOld itinerary versions remain available for support\nExpose received, stale, material, acknowledged, and rebook-required metrics\n```\n\nImplement ingestion, ordering, materiality rules, itinerary revisions, acknowledgement, options, notifications, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Investigate why the iOS boarding-pass wallet card shows an old gate after a terminal change.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the rebooking-options UI and add a concise guide for fare difference, connection risk, deadlines, and confirmation.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Why does the pricing service preserve the original exchange rate after a booking modification? Explain current accounting behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Rewrite the local setup for running WireMock suppliers, Postgres, Kafka, and sample booking fixtures.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"This date test fails for one overnight route:\n\n```text\norigin=Pacific/Apia destination=Pacific/Honolulu\ndeparture local=2026-08-18T23:30+13:00\narrival local=2026-08-18T10:20-10:00\nduration expected=10h50m actual=10h50m\nitinerary day grouping expected arrival on day 2\nactual arrival grouped with departure on day 1\nfixture groups by traveler home zone=Europe/London\nUI groups each segment by origin local date\nproduct requirement says itinerary day follows destination local calendar\n```\n\nDetermine which calendar semantics are inconsistent and why duration correctness does not settle the grouping behavior.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"finish the reservation endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Propose an architecture for disruption recovery, including event ingestion, affected travelers, option generation, inventory, notification, self-service, and agent escalation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add OpenTravel Alliance XML parsing to `supplierctl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Review excerpt:\n\n```diff\n async function confirmBooking(req) {\n- const quote = await quotes.requireValid(req.body.quoteId)\n- const result = await supplier.confirm(quote)\n- await bookings.persist(result, quote)\n+ supplier.confirmById(req.body.quoteId).catch(logger.warn)\n+ await bookings.persistPending(req.body.quoteId)\n return { status: 'confirmed' }\n }\n```\n\nThe author says waiting for suppliers hurts conversion. Review response semantics, missing quote validation, supplier failure, duplicate requests, persistence, reconciliation, and traveler expectations. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Schreibe eine kurze Referenz für die bestehenden Buchungsstatus und ihre Auswirkungen auf Zahlung und Stornierung. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"de"} +{"prompt":"Build the desktop operations itinerary viewer with segment states, supplier references, changes, payments, and keyboard navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Review how cancellation penalties are calculated and displayed, then turn the findings into an agent guide with examples.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Set the supplier timeout to 8s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Benenne `TripCtx` repositoryweit in `TripContext` um; JSON-Felder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"de"} +{"prompt":"Consolidate traveler-name formatting across tickets and itineraries without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Diagnose the duplicate booking email","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Explain how the offer cache handles stop-sell updates while checkout is in progress.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Create API documentation for the existing cancellation-quote endpoint, including penalties, expiry, currency, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Plan a migration from property-local room IDs to supplier-neutral accommodation units, including mapping, history, compatibility, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Mobile design ticket:\n\n```text\nScreen: booking confirmation\nSummary: status, confirmation number, supplier, total paid\nSections vary by hotel, rail, flight, and activity\nPending supplier confirmation must not look final\nDocuments may arrive asynchronously\nChange and cancel actions depend on fare rules and deadlines\nOffline mode shows last confirmed itinerary with stale timestamp\nAccessibility: confirmation number has copy action; status announced before decorative artwork\nSupport action includes booking reference but not payment details\n```\n\nImplement the responsive Compose screen and tests using existing booking models.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Implement `POST /v1/bookings/{id}/acknowledge-change` with revision checks and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Remove the extra slash from the ticket link","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fix the clipped fare badge and extract its duplicated padding into the shared booking token.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Replace scattered booking booleans with one explicit lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Cambia `segRev` por `segmentRevision` solo en `ItineraryState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"es"} +{"prompt":"Investigate why the traveler app briefly shows another account's upcoming trip after logout and login.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Summarize the current booking-reconciliation lifecycle for finance and operations reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Develop a capacity roadmap for handling 500,000 booking attempts per minute during major events. Include offers, holds, suppliers, payments, queues, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement idempotent loyalty-status ingestion with effective dates and corrections.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the SwiftUI hotel-search screen with map, filters, dates, guests, loading states, and VoiceOver summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Fix `reservaton` in `events.proto`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Merge duplicate fare-rule normalization paths used by search and servicing while preserving decisions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Supplier sync failure:\n\n```text\nsupplier=s_81 property=h_992 sync_generation=441\npage 1 cursor=a rows=500 committed\npage 2 cursor=b rows=500 committed\npage 3 cursor=c request timeout\nretry begins from cursor=b due checkpoint lag\npage 2 applies room closures version=92\nsupplier then returns page 3 with reopen version=93\nlate original page 2 response arrives after page 3 and applies closure version=92\nadapter does not pass supplier versions into inventory store\nproperty becomes falsely unavailable\n```\n\nDetermine how cursor retry and response reordering permit stale inventory to overwrite newer state and which version data is discarded.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Rename `arival_time` to `arrival_time` in the unreleased schema.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"Assess whether shared itineraries expose hidden prices or passenger details through cached documents and notifications. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Restructure the travel SDK into search, offers, bookings, servicing, and itineraries, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Plan the retirement of legacy PDF vouchers, covering supplier requirements, digital documents, offline access, communication, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"en"} -{"prompt":"Add immutable provenance chains to normalized supplier offers.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Build the tablet disruption console with affected trips, options, traveler status, communications, and accessible controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} +{"prompt":"Restructure the travel SDK into search, offers, bookings, servicing, and itineraries, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan the retirement of legacy PDF vouchers, covering supplier requirements, digital documents, offline access, communication, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add immutable provenance chains to normalized supplier offers.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Build the tablet disruption console with affected trips, options, traveler status, communications, and accessible controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"do the itinerary page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `BookingRef` with `BookingReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why issued tickets omit acknowledged schedule changes, implement the verified revision fix, and add a traveler-facing note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.77,"slice":"mixed","lang":"en"} -{"prompt":"Why does the offer service retain two previous pricing snapshots? Explain current checkout and audit behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.47,"slice":"boundary","lang":"en"} +{"prompt":"Replace `BookingRef` with `BookingReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose why issued tickets omit acknowledged schedule changes, implement the verified revision fix, and add a traveler-facing note.","purpose":"debugging","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Why does the offer service retain two previous pricing snapshots? Explain current checkout and audit behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Track down the memory leak in map-route preview workers after long itineraries.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write release notes for flexible cancellation filters, including definitions, supplier caveats, and old-client behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} +{"prompt":"Write release notes for flexible cancellation filters, including definitions, supplier caveats, and old-client behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Offer-versioning notes:\n\n```text\nSearch offers include price, taxes, inventory, rules, and supplier token\nCheckout may begin up to 15 minutes after search\nSome suppliers guarantee price for five minutes; others do not\nA refreshed offer may preserve room or fare identity but change total\nCustomers need an explicit confirmation before a material increase\nPrice decreases may apply automatically\nSupplier token can expire independently of displayed quote\nOld clients send only offer ID, not version\n```\n\nProduce an implementation-free design and migration plan covering identity, versions, expiry, repricing, confirmation, compatibility, audit, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Give the itinerary timeline clearer day grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.32,"slice":"core","lang":"en"} -{"prompt":"Turn the current cancellation behavior into traveler documentation, then review whether penalty and timing claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Outline a phased architecture for moving supplier events from polling to webhooks plus reconciliation, without implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.84,"slice":"boundary","lang":"en"} -{"prompt":"Implement version-aware itinerary history with segment supersession and snapshots.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Create an operator guide for diagnosing bookings stuck in supplier confirmation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} -{"prompt":"Move traveler-timezone resolution out of `ItineraryController` while preserving displayed dates.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Investigate why revoked itinerary collaborators retain access through one document cache.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Add generation-fenced supplier-configuration publication with validation and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Set the search radius to 25 km","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Create the responsive booking-history view with trips, status, filters, documents, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Corrige apenas `departue` para `departure` no novo alerta.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"pt"} -{"prompt":"Review the supplier-voucher endpoint for tenant confusion, stale authorization, guessed references, unsafe redirects, and cache leakage.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Implement booking-change history and write its API guide. Include revisions, acknowledgement, options, deadlines, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Design a migration from supplier-specific traveler profiles to a shared normalized profile, including privacy, compatibility, validation, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.87,"slice":"core","lang":"en"} -{"prompt":"Add resumable itinerary-document imports with checksums and duplicate detection.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Build the desktop fare-rule inspector with sections, deadlines, penalties, source text, and comparison.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"continue the date bug","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.54,"slice":"vague-eval","lang":"en"} -{"prompt":"Extract supplier-code normalization into one shared module while preserving canonical values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why cancellation reminders use an outdated fare deadline, implement the verified snapshot fix, and update support documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed traveler-profile cache for account isolation, revoked collaborators, stale documents, privacy, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Find why one supplier worker retries an unsupported modification forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Draft a migration guide for partners moving from XML availability feeds to the inventory API.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Reconciliation incident excerpt:\n\n```text\nbooking=b_881 supplier_ref=SUP-991\ninternal status=cancelled refund_expected=420.00 EUR\nsupplier statement status=active charge=420.00 EUR\ncancellation request provider timeout at=10:01:12\nretry worker saw local cancelled state and skipped supplier call\nlocal state transition occurred before supplier response\nreconciliation rule nets expected refund against supplier charge and reports difference=0\ntraveler receives cancellation confirmation but reservation remains active\n```\n\nDetermine why local state advances before supplier confirmation and why reconciliation algebra masks the active reservation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Add supplier name below the booking title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Restructure the supplier connector framework and document its adapter interface. Preserve behavior while separating auth, offers, booking, servicing, and reconciliation.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.81,"slice":"mixed","lang":"en"} -{"prompt":"Architect a multi-region booking platform with inventory ownership, holds, confirmation, servicing, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed booking receipts with offer version and supplier confirmation digest.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new travel supplier, including offers, booking, changes, cancellation, fixtures, and monitoring.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.47,"slice":"core","lang":"en"} -{"prompt":"Consolidate reservation-status formatting across app and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Investigate why cancelled activities remain in destination search suggestions.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional itinerary ownership transfer with collaborator and document remapping.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Pin MapLibre to `6.1.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Build the mobile trip-sharing manager with invites, roles, privacy controls, revoke, and accessible confirmations.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Remplace `Itenerary` par `Itinerary` uniquement dans le nouveau titre.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"fr"} -{"prompt":"Inspect the booking-import endpoint for duplicate references, tenant spoofing, malicious documents, partial commits, and stale offers.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"Implement supplier-reconciliation history and write its API documentation. Include statements, matches, discrepancies, corrections, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Develop a roadmap for replacing static destination pages with real-time availability-aware content, including caching, fallback, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"Add bounded event replay for booking projections with durable checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} +{"prompt":"Give the itinerary timeline clearer day grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Turn the current cancellation behavior into traveler documentation, then review whether penalty and timing claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Outline a phased architecture for moving supplier events from polling to webhooks plus reconciliation, without implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement version-aware itinerary history with segment supersession and snapshots.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create an operator guide for diagnosing bookings stuck in supplier confirmation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Move traveler-timezone resolution out of `ItineraryController` while preserving displayed dates.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why revoked itinerary collaborators retain access through one document cache.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add generation-fenced supplier-configuration publication with validation and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Set the search radius to 25 km","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Create the responsive booking-history view with trips, status, filters, documents, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Corrige apenas `departue` para `departure` no novo alerta.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"pt"} +{"prompt":"Review the supplier-voucher endpoint for tenant confusion, stale authorization, guessed references, unsafe redirects, and cache leakage.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement booking-change history and write its API guide. Include revisions, acknowledgement, options, deadlines, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Design a migration from supplier-specific traveler profiles to a shared normalized profile, including privacy, compatibility, validation, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add resumable itinerary-document imports with checksums and duplicate detection.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Build the desktop fare-rule inspector with sections, deadlines, penalties, source text, and comparison.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Extract supplier-code normalization into one shared module while preserving canonical values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Investigate why cancellation reminders use an outdated fare deadline, implement the verified snapshot fix, and update support documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed traveler-profile cache for account isolation, revoked collaborators, stale documents, privacy, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why one supplier worker retries an unsupported modification forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft a migration guide for partners moving from XML availability feeds to the inventory API.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Reconciliation incident excerpt:\n\n```text\nbooking=b_881 supplier_ref=SUP-991\ninternal status=cancelled refund_expected=420.00 EUR\nsupplier statement status=active charge=420.00 EUR\ncancellation request provider timeout at=10:01:12\nretry worker saw local cancelled state and skipped supplier call\nlocal state transition occurred before supplier response\nreconciliation rule nets expected refund against supplier charge and reports difference=0\ntraveler receives cancellation confirmation but reservation remains active\n```\n\nDetermine why local state advances before supplier confirmation and why reconciliation algebra masks the active reservation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add supplier name below the booking title","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Restructure the supplier connector framework and document its adapter interface. Preserve behavior while separating auth, offers, booking, servicing, and reconciliation.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Architect a multi-region booking platform with inventory ownership, holds, confirmation, servicing, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement signed booking receipts with offer version and supplier confirmation digest.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new travel supplier, including offers, booking, changes, cancellation, fixtures, and monitoring.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Consolidate reservation-status formatting across app and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why cancelled activities remain in destination search suggestions.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add transactional itinerary ownership transfer with collaborator and document remapping.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Pin MapLibre to `6.1.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile trip-sharing manager with invites, roles, privacy controls, revoke, and accessible confirmations.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remplace `Itenerary` par `Itinerary` uniquement dans le nouveau titre.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"fr"} +{"prompt":"Inspect the booking-import endpoint for duplicate references, tenant spoofing, malicious documents, partial commits, and stale offers.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement supplier-reconciliation history and write its API documentation. Include statements, matches, discrepancies, corrections, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Develop a roadmap for replacing static destination pages with real-time availability-aware content, including caching, fallback, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add bounded event replay for booking projections with durable checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Create the responsive airport-transfer picker with pickup details, vehicle options, capacity, price, and accessible selection.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"fix rebooking","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `OfferEvt` with `OfferEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why modified bookings still send old departure reminders, implement the verified projection fix, and update traveler documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.74,"slice":"mixed","lang":"en"} -{"prompt":"Why does the itinerary service retain two previous document bundles? Explain current offline and rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.47,"slice":"boundary","lang":"en"} -{"prompt":"Track down occasional missing hotel images after property feed refreshes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Write a troubleshooting guide for failed booking confirmation, covering offers, holds, payment, suppliers, and retries.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Privacy review packet:\n\n```text\nFeature: automatic itinerary import from email\nUser connects mailbox and grants read-only message access\nService scans messages for travel confirmations and extracts bookings\nRaw message bodies retained for 24 hours for parsing retries\nAttachments retained only when added to itinerary\nUsers can disconnect mailbox and request deletion\nShared itinerary collaborators see extracted booking details, not source email\nParser vendor receives redacted message content for unsupported formats\nImport runs every 15 minutes\n```\n\nReview scope, consent, retention, deletion, vendor redaction, shared access, credentials, and user expectations. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a loading state to the itinerary cards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Plan and implement email itinerary import. First define authorization, message filtering, retention, vendor use, deduplication, deletion, audit, and rollout; then add ingestion and extraction.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.93,"slice":"mixed","lang":"en"} -{"prompt":"Outline an architecture for collaborative trip planning with shared edits, booking boundaries, offline clients, permissions, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"boundary","lang":"en"} -{"prompt":"Implement snapshot-consistent booking exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Escribe una guía para integrar proveedores de viajes, con ofertas, reservas, cambios, cancelaciones y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"es"} -{"prompt":"Move fare-deadline resolution out of the notification worker without changing reminders.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Investigate why the iOS app loses offline tickets after restoring a device backup.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.64,"slice":"boundary","lang":"en"} -{"prompt":"Add atomic destination-content publication with validation, preview, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Remove the obsolete `legacy_offer` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"core","lang":"en"} -{"prompt":"Build the desktop supplier-health dashboard with latency, errors, inventory lag, circuits, and diagnostics.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"`Bookng confirmed` を `Booking confirmed` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"ja"} -{"prompt":"Review the itinerary-document download path for collaborator revocation, passenger leakage, stale URLs, cache confusion, and enumeration.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"Implement offer-version history and write its API guide. Include price, rules, inventory, expiry, supersession, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Plan a disaster-recovery strategy for booking services, including offers, reservations, suppliers, documents, payments, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"core","lang":"en"} -{"prompt":"Add content-hash deduplication to uploaded travel documents with booking-scoped ownership.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Create the desktop property-content editor with rooms, amenities, images, policies, preview, and validation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"continue the supplier cleanup","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"Rename `TripRev` to `ItineraryRevision` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why removed collaborators still receive disruption alerts, implement the verified recipient fix, and update help documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed hotel-search cache for region, occupancy, taxes, stale inventory, account isolation, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Find why a cancellation worker retries a supplier's permanent rejection forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Draft a support guide for recovering an interrupted booking modification.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Projection failure output:\n\n```text\nbooking=b_771 revision=14 modification confirmed event offset=99120\nitinerary projection updates segment and status=changed\ncheckpoint transaction fails after database failover\nnotification worker sees changed state and sends new itinerary\nprojection restarts and replays event against revision=14\nstate machine rejects duplicate confirmation and partition stops\nsupplier state is correct but later booking updates queue behind failure\n```\n\nDetermine how projection, checkpoint, and notification lack one durable boundary and why replay is not idempotent.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.81,"slice":"pasted-context","lang":"en"} -{"prompt":"Add booking reference below the trip title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} +{"prompt":"Replace `OfferEvt` with `OfferEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose why modified bookings still send old departure reminders, implement the verified projection fix, and update traveler documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Why does the itinerary service retain two previous document bundles? Explain current offline and rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down occasional missing hotel images after property feed refreshes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Write a troubleshooting guide for failed booking confirmation, covering offers, holds, payment, suppliers, and retries.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Privacy review packet:\n\n```text\nFeature: automatic itinerary import from email\nUser connects mailbox and grants read-only message access\nService scans messages for travel confirmations and extracts bookings\nRaw message bodies retained for 24 hours for parsing retries\nAttachments retained only when added to itinerary\nUsers can disconnect mailbox and request deletion\nShared itinerary collaborators see extracted booking details, not source email\nParser vendor receives redacted message content for unsupported formats\nImport runs every 15 minutes\n```\n\nReview scope, consent, retention, deletion, vendor redaction, shared access, credentials, and user expectations. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add a loading state to the itinerary cards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Plan and implement email itinerary import. First define authorization, message filtering, retention, vendor use, deduplication, deletion, audit, and rollout; then add ingestion and extraction.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Outline an architecture for collaborative trip planning with shared edits, booking boundaries, offline clients, permissions, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement snapshot-consistent booking exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Escribe una guía para integrar proveedores de viajes, con ofertas, reservas, cambios, cancelaciones y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"es"} +{"prompt":"Move fare-deadline resolution out of the notification worker without changing reminders.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why the iOS app loses offline tickets after restoring a device backup.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add atomic destination-content publication with validation, preview, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Remove the obsolete `legacy_offer` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Build the desktop supplier-health dashboard with latency, errors, inventory lag, circuits, and diagnostics.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"`Bookng confirmed` を `Booking confirmed` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"ja"} +{"prompt":"Review the itinerary-document download path for collaborator revocation, passenger leakage, stale URLs, cache confusion, and enumeration.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement offer-version history and write its API guide. Include price, rules, inventory, expiry, supersession, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan a disaster-recovery strategy for booking services, including offers, reservations, suppliers, documents, payments, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add content-hash deduplication to uploaded travel documents with booking-scoped ownership.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the desktop property-content editor with rooms, amenities, images, policies, preview, and validation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Rename `TripRev` to `ItineraryRevision` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Investigate why removed collaborators still receive disruption alerts, implement the verified recipient fix, and update help documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed hotel-search cache for region, occupancy, taxes, stale inventory, account isolation, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why a cancellation worker retries a supplier's permanent rejection forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft a support guide for recovering an interrupted booking modification.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Projection failure output:\n\n```text\nbooking=b_771 revision=14 modification confirmed event offset=99120\nitinerary projection updates segment and status=changed\ncheckpoint transaction fails after database failover\nnotification worker sees changed state and sends new itinerary\nprojection restarts and replays event against revision=14\nstate machine rejects duplicate confirmation and partition stops\nsupplier state is correct but later booking updates queue behind failure\n```\n\nDetermine how projection, checkpoint, and notification lack one durable boundary and why replay is not idempotent.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add booking reference below the trip title","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"Restructure the itinerary projection and document its event interface. Preserve output while separating booking events, normalization, revisioning, rendering, and publication.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Architect a globally distributed travel inventory platform with supplier ownership, offers, holds, updates, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed booking receipts with itinerary revision and supplier response digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new booking-document type, including generation, validation, storage, expiry, and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"Consolidate travel-duration formatting across app and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Investigate why expired offers remain visible in saved-search results.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.61,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional booking transfer between traveler accounts with document and payment checks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Set the itinerary cache to 48 hours","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Build the mobile disruption-alert screen with affected segments, options, deadlines, support, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"把 `Departue changed` 改成 `Departure changed`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"zh"} -{"prompt":"Inspect the supplier-feed importer for XML entity expansion, duplicate IDs, tenant confusion, huge archives, and partial commits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Implement itinerary-revision history and write its API documentation. Include segments, changes, acknowledgements, documents, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Design a production-traceability architecture for raw materials, work orders, lots, serial numbers, inspections, rework, and shipments. Cover genealogy, immutable corrections, offline stations, supplier data, recalls, regional plants, migration from ERP tables, and rollout milestones. Deliver an RFC only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"core","lang":"en"} -{"prompt":"Before implementing dynamic production scheduling, outline capacity, tooling, labor skills, material availability, maintenance, priorities, frozen windows, explanations, and phased launch.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"boundary","lang":"en"} -{"prompt":"Add lot genealogy to `/v2/materials`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Traceability incident logs:\n\n```text\nplant=p_17 line=l_4 work_order=wo_881\ninput lot=rm_441 quantity=500kg issued at=06:01:12\nscanner station offline until=08:22:04\noperator records substitute lot=rm_442 locally at=06:14:30\nERP backflush posts original lot=rm_441 at=07:00:00\nstation reconnect uploads substitute event sequence=991\nreconciliation retains both issues because source IDs differ\nfinished lot=fg_82 genealogy shows 1000kg input for 500kg output\nrecall query includes both raw lots\n```\n\nDetermine why substitute and automatic backflush are treated as independent consumption rather than competing versions of one material issue.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Build the tablet work-order screen with steps, materials, machine state, quality checks, downtime, and accessible operator controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Plan and implement an electronic batch-record service. Begin with a design covering versioned instructions, signatures, witnessed steps, equipment, deviations, offline stations, corrections, release review, audit replay, and migration. Then add execution APIs, durable events, signature checks, and conformance tests. Treat record integrity and review semantics as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.98,"slice":"mixed","lang":"en"} -{"prompt":"Set `MAX_LOT_SPLITS` to 50","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Extract duplicated unit-of-measure conversion from receiving and production while preserving rounding.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Implement `/internal/lines/status` with running, idle, blocked, changeover, maintenance, and stale counts.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.51,"slice":"boundary","lang":"en"} -{"prompt":"make the factory dashboard clearer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.41,"slice":"vague-eval","lang":"en"} +{"prompt":"Architect a globally distributed travel inventory platform with supplier ownership, offers, holds, updates, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Implement signed booking receipts with itinerary revision and supplier response digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new booking-document type, including generation, validation, storage, expiry, and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Consolidate travel-duration formatting across app and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why expired offers remain visible in saved-search results.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add transactional booking transfer between traveler accounts with document and payment checks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Set the itinerary cache to 48 hours","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile disruption-alert screen with affected segments, options, deadlines, support, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"把 `Departue changed` 改成 `Departure changed`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"zh"} +{"prompt":"Inspect the supplier-feed importer for XML entity expansion, duplicate IDs, tenant confusion, huge archives, and partial commits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement itinerary-revision history and write its API documentation. Include segments, changes, acknowledgements, documents, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Design a production-traceability architecture for raw materials, work orders, lots, serial numbers, inspections, rework, and shipments. Cover genealogy, immutable corrections, offline stations, supplier data, recalls, regional plants, migration from ERP tables, and rollout milestones. Deliver an RFC only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Before implementing dynamic production scheduling, outline capacity, tooling, labor skills, material availability, maintenance, priorities, frozen windows, explanations, and phased launch.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add lot genealogy to `/v2/materials`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Traceability incident logs:\n\n```text\nplant=p_17 line=l_4 work_order=wo_881\ninput lot=rm_441 quantity=500kg issued at=06:01:12\nscanner station offline until=08:22:04\noperator records substitute lot=rm_442 locally at=06:14:30\nERP backflush posts original lot=rm_441 at=07:00:00\nstation reconnect uploads substitute event sequence=991\nreconciliation retains both issues because source IDs differ\nfinished lot=fg_82 genealogy shows 1000kg input for 500kg output\nrecall query includes both raw lots\n```\n\nDetermine why substitute and automatic backflush are treated as independent consumption rather than competing versions of one material issue.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Build the tablet work-order screen with steps, materials, machine state, quality checks, downtime, and accessible operator controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Plan and implement an electronic batch-record service. Begin with a design covering versioned instructions, signatures, witnessed steps, equipment, deviations, offline stations, corrections, release review, audit replay, and migration. Then add execution APIs, durable events, signature checks, and conformance tests. Treat record integrity and review semantics as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":1,"slice":"mixed","lang":"en"} +{"prompt":"Set `MAX_LOT_SPLITS` to 50","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Extract duplicated unit-of-measure conversion from receiving and production while preserving rounding.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement `/internal/lines/status` with running, idle, blocked, changeover, maintenance, and stale counts.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"make the factory dashboard clearer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"Find why a PLC gateway occasionally reports yesterday's recipe after a controller reboot.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Explain how `MaterialAllocator` chooses lots by expiry, status, location, and customer restrictions. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Operations release notes source:\n\n```text\nFeature: production deviation workflow\nOperator records deviation against an active work-order step\nRequired fields: category, description, detected time, affected quantity\nSupervisor triages and may contain, investigate, or reject the deviation\nClosing requires disposition and evidence\nDeviation does not automatically stop equipment unless configured by category\nCorrections append to history; original statements remain\nNotifications omit free-text details on shared devices\nOpen deviations appear in batch-release review\n```\n\nTurn this into operator release notes and a supervisor procedure guide. Clarify workflow status versus equipment control.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.47,"slice":"pasted-context","lang":"en"} -{"prompt":"Move the machine warning icon beside the state label","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.13,"slice":"boundary","lang":"en"} -{"prompt":"Write an operator guide for replaying failed inventory movements without doubling stock.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Implement inspection-result endpoints with samples, specifications, disposition, and permissions, then document lifecycle, examples, and errors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} +{"prompt":"Explain how `MaterialAllocator` chooses lots by expiry, status, location, and customer restrictions. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Operations release notes source:\n\n```text\nFeature: production deviation workflow\nOperator records deviation against an active work-order step\nRequired fields: category, description, detected time, affected quantity\nSupervisor triages and may contain, investigate, or reject the deviation\nClosing requires disposition and evidence\nDeviation does not automatically stop equipment unless configured by category\nCorrections append to history; original statements remain\nNotifications omit free-text details on shared devices\nOpen deviations appear in batch-release review\n```\n\nTurn this into operator release notes and a supervisor procedure guide. Clarify workflow status versus equipment control.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} +{"prompt":"Move the machine warning icon beside the state label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Write an operator guide for replaying failed inventory movements without doubling stock.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Implement inspection-result endpoints with samples, specifications, disposition, and permissions, then document lifecycle, examples, and errors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Map out a migration from plant-specific material codes to a global item master, including aliases, history, integrations, validation, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Rename `lotNo` to `lotNumber` in `MaterialMapper.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"en"} -{"prompt":"Teach the inventory worker to process warehouse transfers atomically across source and destination bins.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Polish the shift summary card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.28,"slice":"core","lang":"en"} -{"prompt":"Bump `node-red` to `4.1.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Rename `MasterRecipe` to `PrimaryRecipe` across services, PLC payloads, dashboards, and tests while preserving protocol values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"boundary","lang":"en"} -{"prompt":"Split `ProductionService` into scheduling, execution, material, quality, and completion components without changing outcomes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"en"} -{"prompt":"Implementation ticket:\n\n```text\nMFG-2840 — tool calibration enforcement\nTools have serial number, type, calibration status, due date, and capability range\nWork-order steps declare required tool type and measurement range\nScanner validates exact tool before step begins\nExpired or out-of-range tools block execution unless authorized override\nOffline stations use last signed calibration snapshot with maximum age 24 hours\nOverride requires supervisor, reason, and deviation record\nCalibration updates must invalidate station caches\nExpose blocked, stale-snapshot, override, and invalid-range metrics\n```\n\nImplement tool registry integration, step checks, offline snapshots, overrides, invalidation, deviations, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.88,"slice":"pasted-context","lang":"en"} -{"prompt":"Investigate why the Android scanner assigns a serial number to the previously selected pallet.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Create the lot-genealogy graph UI and add a short legend for consumption, splits, merges, rework, and shipment.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Why does the production service retain cancelled work orders in capacity projections? Explain current audit behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.47,"slice":"core","lang":"en"} -{"prompt":"Rewrite the local setup for running OPC UA simulation, Postgres, Kafka, and synthetic work orders.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"This inventory test fails under parallel picking:\n\n```text\nbin=A-17 lot=L-991 on_hand=10 reserved=0\npick request p1 quantity=6 begins\npick request p2 quantity=6 begins\np1 reads available=10 and inserts reservation=6\np2 reads available=10 and inserts reservation=6\nboth transactions commit under READ COMMITTED\nprojection reports reserved=12 available=-2\nconstraint checks each reservation quantity but not aggregate\n```\n\nDetermine why transaction isolation and constraints permit over-reservation and whether the aggregate invariant belongs in locking, schema, or command logic.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.75,"slice":"boundary","lang":"en"} -{"prompt":"finish the inventory endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.48,"slice":"vague-eval","lang":"en"} -{"prompt":"Propose an architecture for predictive-maintenance data, including sensor ingestion, asset identity, features, models, work orders, explanations, feedback, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"core","lang":"en"} -{"prompt":"Add ISA-95 equipment hierarchy parsing to `plantctl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Review excerpt:\n\n```diff\n async function releaseBatch(req) {\n- const review = await quality.completeReview(req.params.batchId)\n- if (!review.approved) throw forbidden()\n- await inventory.release(req.params.batchId, review.digest)\n+ quality.completeReview(req.params.batchId).catch(logger.warn)\n+ await inventory.release(req.params.batchId, 'pending')\n }\n```\n\nThe author says quality review delays shipments. Review release semantics, unresolved deviations, approval binding, audit, asynchronous failure, and inventory exposure. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Schreibe eine kurze Referenz für die bestehenden Arbeitsauftragsstatus und ihre Auswirkungen auf Material und Kapazität. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"de"} -{"prompt":"Build the desktop production-schedule board with lanes, drag rescheduling, constraints, conflicts, undo, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Review how OEE is currently calculated, explain availability, performance, and quality inputs, then produce an operations guide.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.63,"slice":"mixed","lang":"en"} -{"prompt":"Set the scanner timeout to 15s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Benenne `WorkCtx` repositoryweit in `WorkOrderContext` um; JSON-Felder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"de"} -{"prompt":"Consolidate equipment-state normalization across OPC UA and MQTT adapters without changing values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Diagnose the duplicate downtime alert","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Explain how the scheduler handles a work order whose required material becomes quarantined.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Create API documentation for the existing material-reservation endpoint, including expiry, partial allocation, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"boundary","lang":"en"} -{"prompt":"Plan a migration from nightly ERP inventory snapshots to event-driven stock movements, covering ordering, corrections, replay, validation, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"core","lang":"en"} -{"prompt":"Tablet design ticket:\n\n```text\nScreen: operator work queue\nCards show work order, product, quantity, due time, line, material readiness, priority\nOperator sees only certified operations\nBlocked cards explain material, tool, quality, or maintenance constraint\nStarting work requires station and equipment confirmation\nOffline mode shows downloaded queue with stale timestamp and prevents unverified reassignment\nAccessibility: priority and block reason are text, not color only\nGlove mode increases targets and removes swipe-only actions\n```\n\nImplement the responsive screen and tests using existing work-order APIs.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"pasted-context","lang":"en"} -{"prompt":"Implement `POST /v1/lots/{id}/quarantine` with reason, scope, downstream holds, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"boundary","lang":"en"} -{"prompt":"Remove the extra dash from the lot label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"core","lang":"en"} -{"prompt":"Fix the clipped priority badge and extract its duplicated padding into the shared work-card token.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.35,"slice":"mixed","lang":"en"} -{"prompt":"Replace scattered work-order booleans with one explicit lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Cambia `stepRev` por `stepRevision` solo en `BatchState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"es"} -{"prompt":"Investigate why the operator tablet briefly displays another line's work queue after station switching.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Summarize the current batch-release workflow for quality and compliance reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Develop a capacity roadmap for processing one billion traceability events per day. Include partitions, genealogy queries, retention, replay, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Implement idempotent supplier-certificate ingestion with expiry, revisions, and provenance.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Create the SwiftUI equipment-detail screen with state, maintenance, calibration, alarms, history, and VoiceOver support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Fix `calbration` in `tools.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} -{"prompt":"Merge duplicate lot-status types used by inventory and quality while preserving serialized values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Recall-query incident:\n\n```text\nraw lot=RM-771 used in intermediate lots=[IM-11,IM-12]\nIM-11 split into finished lots=[FG-21,FG-22]\nIM-12 reworked into IM-13 then consumed by FG-23\nrecall traversal returns FG-21 and FG-22 only\nrework event edge direction stored new=IM-13 -> old=IM-12\nnormal consumption traversal follows input -> output\nrework traversal therefore points backward\nquery marks visited IM-12 before exploring alternate edge\n```\n\nDetermine why rework edge direction and visited-node handling omit FG-23 from the recall scope.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.81,"slice":"pasted-context","lang":"en"} -{"prompt":"Rename `quanity_used` to `quantity_used` in the unreleased schema.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"en"} -{"prompt":"Assess whether supplier portals can see another supplier's quality findings through shared certificate caches. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Restructure the manufacturing SDK into items, inventory, work orders, quality, and genealogy, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} +{"prompt":"Rename `lotNo` to `lotNumber` in `MaterialMapper.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Teach the inventory worker to process warehouse transfers atomically across source and destination bins.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Polish the shift summary card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump `node-red` to `4.1.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename `MasterRecipe` to `PrimaryRecipe` across services, PLC payloads, dashboards, and tests while preserving protocol values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Split `ProductionService` into scheduling, execution, material, quality, and completion components without changing outcomes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implementation ticket:\n\n```text\nMFG-2840 — tool calibration enforcement\nTools have serial number, type, calibration status, due date, and capability range\nWork-order steps declare required tool type and measurement range\nScanner validates exact tool before step begins\nExpired or out-of-range tools block execution unless authorized override\nOffline stations use last signed calibration snapshot with maximum age 24 hours\nOverride requires supervisor, reason, and deviation record\nCalibration updates must invalidate station caches\nExpose blocked, stale-snapshot, override, and invalid-range metrics\n```\n\nImplement tool registry integration, step checks, offline snapshots, overrides, invalidation, deviations, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Investigate why the Android scanner assigns a serial number to the previously selected pallet.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Create the lot-genealogy graph UI and add a short legend for consumption, splits, merges, rework, and shipment.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Why does the production service retain cancelled work orders in capacity projections? Explain current audit behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Rewrite the local setup for running OPC UA simulation, Postgres, Kafka, and synthetic work orders.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"This inventory test fails under parallel picking:\n\n```text\nbin=A-17 lot=L-991 on_hand=10 reserved=0\npick request p1 quantity=6 begins\npick request p2 quantity=6 begins\np1 reads available=10 and inserts reservation=6\np2 reads available=10 and inserts reservation=6\nboth transactions commit under READ COMMITTED\nprojection reports reserved=12 available=-2\nconstraint checks each reservation quantity but not aggregate\n```\n\nDetermine why transaction isolation and constraints permit over-reservation and whether the aggregate invariant belongs in locking, schema, or command logic.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"finish the inventory endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Propose an architecture for predictive-maintenance data, including sensor ingestion, asset identity, features, models, work orders, explanations, feedback, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add ISA-95 equipment hierarchy parsing to `plantctl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Review excerpt:\n\n```diff\n async function releaseBatch(req) {\n- const review = await quality.completeReview(req.params.batchId)\n- if (!review.approved) throw forbidden()\n- await inventory.release(req.params.batchId, review.digest)\n+ quality.completeReview(req.params.batchId).catch(logger.warn)\n+ await inventory.release(req.params.batchId, 'pending')\n }\n```\n\nThe author says quality review delays shipments. Review release semantics, unresolved deviations, approval binding, audit, asynchronous failure, and inventory exposure. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Schreibe eine kurze Referenz für die bestehenden Arbeitsauftragsstatus und ihre Auswirkungen auf Material und Kapazität. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"de"} +{"prompt":"Build the desktop production-schedule board with lanes, drag rescheduling, constraints, conflicts, undo, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Review how OEE is currently calculated, explain availability, performance, and quality inputs, then produce an operations guide.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Set the scanner timeout to 15s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Benenne `WorkCtx` repositoryweit in `WorkOrderContext` um; JSON-Felder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"de"} +{"prompt":"Consolidate equipment-state normalization across OPC UA and MQTT adapters without changing values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose the duplicate downtime alert","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Explain how the scheduler handles a work order whose required material becomes quarantined.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Create API documentation for the existing material-reservation endpoint, including expiry, partial allocation, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Plan a migration from nightly ERP inventory snapshots to event-driven stock movements, covering ordering, corrections, replay, validation, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Tablet design ticket:\n\n```text\nScreen: operator work queue\nCards show work order, product, quantity, due time, line, material readiness, priority\nOperator sees only certified operations\nBlocked cards explain material, tool, quality, or maintenance constraint\nStarting work requires station and equipment confirmation\nOffline mode shows downloaded queue with stale timestamp and prevents unverified reassignment\nAccessibility: priority and block reason are text, not color only\nGlove mode increases targets and removes swipe-only actions\n```\n\nImplement the responsive screen and tests using existing work-order APIs.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Implement `POST /v1/lots/{id}/quarantine` with reason, scope, downstream holds, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remove the extra dash from the lot label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fix the clipped priority badge and extract its duplicated padding into the shared work-card token.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Replace scattered work-order booleans with one explicit lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Cambia `stepRev` por `stepRevision` solo en `BatchState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"es"} +{"prompt":"Investigate why the operator tablet briefly displays another line's work queue after station switching.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Summarize the current batch-release workflow for quality and compliance reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Develop a capacity roadmap for processing one billion traceability events per day. Include partitions, genealogy queries, retention, replay, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement idempotent supplier-certificate ingestion with expiry, revisions, and provenance.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the SwiftUI equipment-detail screen with state, maintenance, calibration, alarms, history, and VoiceOver support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Fix `calbration` in `tools.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Merge duplicate lot-status types used by inventory and quality while preserving serialized values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Recall-query incident:\n\n```text\nraw lot=RM-771 used in intermediate lots=[IM-11,IM-12]\nIM-11 split into finished lots=[FG-21,FG-22]\nIM-12 reworked into IM-13 then consumed by FG-23\nrecall traversal returns FG-21 and FG-22 only\nrework event edge direction stored new=IM-13 -> old=IM-12\nnormal consumption traversal follows input -> output\nrework traversal therefore points backward\nquery marks visited IM-12 before exploring alternate edge\n```\n\nDetermine why rework edge direction and visited-node handling omit FG-23 from the recall scope.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Rename `quanity_used` to `quantity_used` in the unreleased schema.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Assess whether supplier portals can see another supplier's quality findings through shared certificate caches. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Restructure the manufacturing SDK into items, inventory, work orders, quality, and genealogy, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Plan the retirement of paper batch records, covering station readiness, signatures, offline operation, validation, training, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Add immutable provenance chains to normalized inspection results.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} +{"prompt":"Add immutable provenance chains to normalized inspection results.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Build the tablet deviation-review flow with evidence, containment, investigation, disposition, signatures, and accessible controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"do the line dashboard","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `LotRef` with `LotReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why released batch certificates omit approved deviations, implement the verified revision fix, and add a quality-facing note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"Why does the inventory service retain two previous item-master versions? Explain current rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.46,"slice":"boundary","lang":"en"} -{"prompt":"Track down the memory leak in PDF label-generation workers after large print batches.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write release notes for alternate-material approvals, including eligibility, expiry, traceability, and old-client behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.36,"slice":"core","lang":"en"} -{"prompt":"Scheduling design notes:\n\n```text\nCurrent plan is generated nightly from ERP work orders\nNew scheduler replans every 15 minutes\nConstraints: machine capability, tooling, labor certification, material availability, cleaning, maintenance, due dates\nSome operations have fixed sequence; others may overlap\nFrozen window prevents automatic changes within two hours of execution\nSupervisor can pin work orders or override constraints with reason\nOperators need explanations for changed assignments\nOld shop-floor clients receive ordered lists only\n```\n\nProduce an implementation-free design and rollout plan covering constraints, frozen windows, overrides, explanations, compatibility, simulation, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"pasted-context","lang":"en"} -{"prompt":"Give the shift timeline clearer state grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.31,"slice":"core","lang":"en"} -{"prompt":"Turn the current material-allocation behavior into planner documentation, then review whether FEFO and substitution claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Outline a phased architecture for moving production telemetry from SQL Server to a time-series platform, without implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.84,"slice":"boundary","lang":"en"} +{"prompt":"Replace `LotRef` with `LotReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose why released batch certificates omit approved deviations, implement the verified revision fix, and add a quality-facing note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Why does the inventory service retain two previous item-master versions? Explain current rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down the memory leak in PDF label-generation workers after large print batches.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Write release notes for alternate-material approvals, including eligibility, expiry, traceability, and old-client behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Scheduling design notes:\n\n```text\nCurrent plan is generated nightly from ERP work orders\nNew scheduler replans every 15 minutes\nConstraints: machine capability, tooling, labor certification, material availability, cleaning, maintenance, due dates\nSome operations have fixed sequence; others may overlap\nFrozen window prevents automatic changes within two hours of execution\nSupervisor can pin work orders or override constraints with reason\nOperators need explanations for changed assignments\nOld shop-floor clients receive ordered lists only\n```\n\nProduce an implementation-free design and rollout plan covering constraints, frozen windows, overrides, explanations, compatibility, simulation, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Give the shift timeline clearer state grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Turn the current material-allocation behavior into planner documentation, then review whether FEFO and substitution claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Outline a phased architecture for moving production telemetry from SQL Server to a time-series platform, without implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Implement version-aware recipe history with effective dates and supersession links.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Create an operator guide for diagnosing work orders stuck in material hold.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} -{"prompt":"Move yield calculation out of `ProductionController` while preserving values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"core","lang":"en"} -{"prompt":"Investigate why revoked contractor access remains active on one plant kiosk.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Add generation-fenced recipe publication with simulation and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Set the inventory hold TTL to 30 minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Create the responsive inventory-location view with bins, lots, quantities, holds, filters, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Corrige apenas `prodution` para `production` no novo alerta.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"pt"} -{"prompt":"Review the label-template upload endpoint for script injection, printer commands, tenant confusion, huge assets, and stale approvals.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Implement batch-release history and write its API guide. Include reviews, deviations, signatures, status, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} +{"prompt":"Create an operator guide for diagnosing work orders stuck in material hold.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Move yield calculation out of `ProductionController` while preserving values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why revoked contractor access remains active on one plant kiosk.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add generation-fenced recipe publication with simulation and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Set the inventory hold TTL to 30 minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Create the responsive inventory-location view with bins, lots, quantities, holds, filters, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Corrige apenas `prodution` para `production` no novo alerta.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"pt"} +{"prompt":"Review the label-template upload endpoint for script injection, printer commands, tenant confusion, huge assets, and stale approvals.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement batch-release history and write its API guide. Include reviews, deviations, signatures, status, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Design a migration from static preventive maintenance to condition-based maintenance, including sensors, models, work orders, fallback, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Add resumable supplier-catalog imports with checksums and row-level errors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Build the desktop material-allocation workspace with requirements, available lots, constraints, preview, and undo.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"continue the genealogy bug","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"Extract plant-timezone resolution into one shared module while preserving production dates.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why calibration reminders use an outdated due date, implement the verified cache fix, and update operator docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.74,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed machine-state cache for plant isolation, stale alarms, maintenance, revocation, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.69,"slice":"boundary","lang":"en"} -{"prompt":"Find why one quality worker retries a permanently invalid result forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Draft a migration guide for suppliers moving from spreadsheet certificates to the quality API.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Inventory projection failure:\n\n```text\nmovement mv_881 transfers lot L-91 quantity=20 from A to B\nsource decrement committed projection version=441\ncheckpoint write times out\nshipment worker reads B quantity from separate projection and sees zero\nprojection restarts and replays movement\nsource A decrements another 20 because idempotency key shared checkpoint transaction did not commit\ndestination B increment fails unique movement constraint\nnet inventory drops by 20\n```\n\nDetermine how source, destination, checkpoint, and idempotency updates lack an atomic boundary and why replay becomes asymmetric.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.83,"slice":"pasted-context","lang":"en"} -{"prompt":"Add lot status below the material title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Restructure the inventory projection and document its movement interface. Preserve balances while separating validation, reservation, movement, projection, and reconciliation.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.82,"slice":"mixed","lang":"en"} -{"prompt":"Architect a multi-region manufacturing platform with plant ownership, items, work orders, genealogy, quality, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed batch records with recipe version and event digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new equipment adapter, including identity, states, commands, fixtures, and monitoring.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Consolidate quantity formatting across operator UI and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Investigate why scrapped lots remain in material autocomplete.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional work-order transfer between lines with reservation remapping and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Pin Eclipse Milo to `1.1.1`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Build the mobile downtime-report flow with category, duration, equipment, notes, photos, and accessible controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Remplace `Equipement` par `Equipment` uniquement dans le nouveau titre anglais.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"fr"} -{"prompt":"Inspect the work-instruction import path for path traversal, unsafe macros, huge documents, tenant confusion, and signature bypass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Implement deviation-history exports and write the API documentation. Include filters, evidence, signatures, revisions, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Develop a roadmap for replacing manual recall queries with precomputed genealogy projections, including parity, performance, validation, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.87,"slice":"core","lang":"en"} -{"prompt":"Add bounded event replay for inventory projections with durable checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Create the responsive maintenance dashboard with upcoming work, overdue assets, parts, technicians, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} +{"prompt":"Add resumable supplier-catalog imports with checksums and row-level errors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Build the desktop material-allocation workspace with requirements, available lots, constraints, preview, and undo.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Extract plant-timezone resolution into one shared module while preserving production dates.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why calibration reminders use an outdated due date, implement the verified cache fix, and update operator docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed machine-state cache for plant isolation, stale alarms, maintenance, revocation, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why one quality worker retries a permanently invalid result forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft a migration guide for suppliers moving from spreadsheet certificates to the quality API.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Inventory projection failure:\n\n```text\nmovement mv_881 transfers lot L-91 quantity=20 from A to B\nsource decrement committed projection version=441\ncheckpoint write times out\nshipment worker reads B quantity from separate projection and sees zero\nprojection restarts and replays movement\nsource A decrements another 20 because idempotency key shared checkpoint transaction did not commit\ndestination B increment fails unique movement constraint\nnet inventory drops by 20\n```\n\nDetermine how source, destination, checkpoint, and idempotency updates lack an atomic boundary and why replay becomes asymmetric.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add lot status below the material title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Restructure the inventory projection and document its movement interface. Preserve balances while separating validation, reservation, movement, projection, and reconciliation.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Architect a multi-region manufacturing platform with plant ownership, items, work orders, genealogy, quality, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement signed batch records with recipe version and event digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new equipment adapter, including identity, states, commands, fixtures, and monitoring.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Consolidate quantity formatting across operator UI and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why scrapped lots remain in material autocomplete.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Add transactional work-order transfer between lines with reservation remapping and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Pin Eclipse Milo to `1.1.1`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile downtime-report flow with category, duration, equipment, notes, photos, and accessible controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Remplace `Equipement` par `Equipment` uniquement dans le nouveau titre anglais.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"fr"} +{"prompt":"Inspect the work-instruction import path for path traversal, unsafe macros, huge documents, tenant confusion, and signature bypass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement deviation-history exports and write the API documentation. Include filters, evidence, signatures, revisions, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Develop a roadmap for replacing manual recall queries with precomputed genealogy projections, including parity, performance, validation, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add bounded event replay for inventory projections with durable checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the responsive maintenance dashboard with upcoming work, overdue assets, parts, technicians, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"fix the stock numbers","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `BatchEvt` with `BatchEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why quarantined material still appears allocatable, implement the verified projection fix, and update planner documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Why does the recipe service retain two previous parameter sets? Explain current rollback and in-flight batch behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.48,"slice":"boundary","lang":"en"} -{"prompt":"Track down occasional missing serial numbers after pallet aggregation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Write a troubleshooting guide for blocked work orders, covering materials, tooling, quality, maintenance, and certifications.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Security review packet:\n\n```text\nFeature: temporary vendor maintenance access\nPlant engineer creates access request for one equipment asset and time window\nVendor connects through browser-based remote session\nSession permits diagnostics and approved maintenance commands\nFile upload disabled; clipboard text allowed\nPlant engineer can observe and terminate session\nCommands are recorded, but screen video is not retained\nVendor identity comes from emailed one-time link plus SMS code\nEmergency session may start before second approval\n```\n\nReview identity, link forwarding, clipboard leakage, command scope, observation, recording, emergency bypass, and audit. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a loading state to the work-order rows","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Plan and implement vendor maintenance access. First define identity, approvals, scope, commands, recording, emergency use, revocation, and audit; then add session control and enforcement.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.94,"slice":"mixed","lang":"en"} -{"prompt":"Outline an architecture for supplier-to-plant traceability exchange with identities, lots, certificates, corrections, privacy, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"boundary","lang":"en"} -{"prompt":"Implement snapshot-consistent batch-record exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Escribe una guía para integrar equipos industriales, con identidad, estados, telemetría, comandos y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} -{"prompt":"Move shelf-life calculation out of the receiving worker without changing expiry dates.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Investigate why the iOS warehouse app loses offline scans after device restore.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Add atomic specification publication with validation, approval, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Remove the obsolete `legacy_recipe` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"core","lang":"en"} -{"prompt":"Build the batch-record viewer with step navigation, signatures, deviations, attachments, and accessible chronology.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"`Work oder complete` を `Work order complete` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"ja"} -{"prompt":"Review the equipment-command endpoint for stale authorization, unsafe ranges, replay, tenant confusion, and missing safety checks.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} +{"prompt":"Replace `BatchEvt` with `BatchEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose why quarantined material still appears allocatable, implement the verified projection fix, and update planner documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Why does the recipe service retain two previous parameter sets? Explain current rollback and in-flight batch behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down occasional missing serial numbers after pallet aggregation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Write a troubleshooting guide for blocked work orders, covering materials, tooling, quality, maintenance, and certifications.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Security review packet:\n\n```text\nFeature: temporary vendor maintenance access\nPlant engineer creates access request for one equipment asset and time window\nVendor connects through browser-based remote session\nSession permits diagnostics and approved maintenance commands\nFile upload disabled; clipboard text allowed\nPlant engineer can observe and terminate session\nCommands are recorded, but screen video is not retained\nVendor identity comes from emailed one-time link plus SMS code\nEmergency session may start before second approval\n```\n\nReview identity, link forwarding, clipboard leakage, command scope, observation, recording, emergency bypass, and audit. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add a loading state to the work-order rows","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Plan and implement vendor maintenance access. First define identity, approvals, scope, commands, recording, emergency use, revocation, and audit; then add session control and enforcement.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Outline an architecture for supplier-to-plant traceability exchange with identities, lots, certificates, corrections, privacy, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement snapshot-consistent batch-record exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Escribe una guía para integrar equipos industriales, con identidad, estados, telemetría, comandos y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"es"} +{"prompt":"Move shelf-life calculation out of the receiving worker without changing expiry dates.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why the iOS warehouse app loses offline scans after device restore.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add atomic specification publication with validation, approval, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Remove the obsolete `legacy_recipe` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Build the batch-record viewer with step navigation, signatures, deviations, attachments, and accessible chronology.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"`Work oder complete` を `Work order complete` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"ja"} +{"prompt":"Review the equipment-command endpoint for stale authorization, unsafe ranges, replay, tenant confusion, and missing safety checks.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Implement equipment-state history and write its API guide. Include sources, transitions, alarms, maintenance, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Plan a disaster-recovery strategy for manufacturing services, including items, inventory, work orders, records, keys, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} +{"prompt":"Plan a disaster-recovery strategy for manufacturing services, including items, inventory, work orders, records, keys, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Add content-hash deduplication to uploaded supplier certificates with provenance.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Create the desktop recall-scope explorer with genealogy, filters, quantities, shipments, and export.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"continue the inventory cleanup","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"Rename `EquipRef` to `EquipmentReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why transferred work orders keep old line notifications, implement the verified routing fix, and update operator documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.75,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed production-state cache for plant isolation, stale holds, quarantines, maintenance, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Find why a receiving worker retries an unsupported unit forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Draft a support guide for recovering an interrupted batch-record session.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"Batch projection failure:\n\n```text\nbatch=b_881 step=14 completion event offset=77110\nprojection updates step complete and next step active\ncheckpoint write fails during database failover\nlabel worker observes next step active and prints label\nprojection restarts and replays completion\nstate machine rejects already-completed step and partition stops\nphysical label exists but event remains uncheckpointed\n```\n\nDetermine how projection, checkpoint, and physical side effect lack one durable boundary and why replay cannot recognize prior completion.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Add quantity text below the lot title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Restructure the batch-execution engine and document its step interface. Preserve behavior while separating instructions, data capture, validation, signatures, and events.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.83,"slice":"mixed","lang":"en"} -{"prompt":"Architect a global traceability platform with plant ownership, item identity, genealogy, quality, recalls, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"boundary","lang":"en"} +{"prompt":"Create the desktop recall-scope explorer with genealogy, filters, quantities, shipments, and export.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Rename `EquipRef` to `EquipmentReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why transferred work orders keep old line notifications, implement the verified routing fix, and update operator documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed production-state cache for plant isolation, stale holds, quarantines, maintenance, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why a receiving worker retries an unsupported unit forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Draft a support guide for recovering an interrupted batch-record session.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Batch projection failure:\n\n```text\nbatch=b_881 step=14 completion event offset=77110\nprojection updates step complete and next step active\ncheckpoint write fails during database failover\nlabel worker observes next step active and prints label\nprojection restarts and replays completion\nstate machine rejects already-completed step and partition stops\nphysical label exists but event remains uncheckpointed\n```\n\nDetermine how projection, checkpoint, and physical side effect lack one durable boundary and why replay cannot recognize prior completion.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add quantity text below the lot title","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Restructure the batch-execution engine and document its step interface. Preserve behavior while separating instructions, data capture, validation, signatures, and events.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Architect a global traceability platform with plant ownership, item identity, genealogy, quality, recalls, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1,"slice":"core","lang":"en"} {"prompt":"Implement signed genealogy snapshots with lot and movement digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new quality specification, including tests, units, limits, revisions, and approval.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Consolidate work-order status formatting across UI and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Investigate why expired tools remain selectable in work instructions.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.61,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional material ownership transfer between plants with inventory and genealogy checks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Set the work-queue refresh to 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Build the mobile material-movement flow with scan, source, destination, quantity, validation, and accessible confirmation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"把 `Materail held` 改成 `Material held`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"zh"} -{"prompt":"Inspect the batch-record import path for path traversal, signature bypass, malicious attachments, huge records, and tenant confusion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"Implement lot-genealogy history and write its API documentation. Include edges, revisions, corrections, recall scope, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Design a community-content architecture for posts, comments, reactions, moderation, edits, deletions, feeds, notifications, and appeals. Cover immutable history, audience changes, privacy, ranking, regional storage, migration from the current activity tables, and rollout milestones. Deliver an RFC only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Before implementing community notes, outline authoring, evidence, contributor reputation, scoring, visibility thresholds, appeals, abuse resistance, explanations, and phased launch.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"boundary","lang":"en"} -{"prompt":"Add comment threading to `/v3/posts`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Moderation incident logs:\n\n```text\npost=p_881 author=u_71 audience=private_group:g_18\nmoderation action=remove reason=personal_data version=12\nfeed delete event published offset=77110\nsearch delete event published offset=44192\nappeal accepted version=13 restore=true audience=private_group:g_18\nfeed restore applies version=13\nsearch restore consumer uses stored document audience=public from version=9\npost appears in public search for 47s\npermission index refresh later removes it\n```\n\nDetermine why restoration uses stale audience metadata and how search visibility becomes public before authorization filtering catches up.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Build the SwiftUI community-feed screen with mixed media, reactions, comment previews, moderation states, pagination, and VoiceOver support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Plan and implement a content-moderation decision service. Begin with a design covering policy versions, automated signals, human review, severity, regional rules, emergency removal, appeals, transparency, audit replay, and failure behavior. Then add the evaluator, queues, decision APIs, and conformance tests. Treat policy semantics and due process as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.98,"slice":"mixed","lang":"en"} -{"prompt":"Set `MAX_COMMENT_DEPTH` to 8","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Extract duplicated audience resolution from posts and collections while preserving every visibility decision.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Implement `/internal/moderation/queues` with pending age, priority, assignments, decisions, and SLA breaches.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"make the profile more alive","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.41,"slice":"vague-eval","lang":"en"} -{"prompt":"Find why blocked users occasionally reappear in suggested follows after refreshing the app.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Explain how `FeedMixer` balances followed accounts, groups, recommendations, and freshness. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Community launch notes:\n\n```text\nFeature: comment controls\nPost author may allow everyone, followers, mentioned people, group members, or nobody to comment\nChanging the setting affects new comments only\nExisting comments remain visible unless separately hidden\nModerators may still comment on locked posts for official notices\nShared posts use the original post's comment policy\nOld mobile clients show a generic comments unavailable message\nComment controls do not prevent quote posts\n```\n\nTurn this into release notes and a help article with examples, limitations, and old-client behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"pasted-context","lang":"en"} -{"prompt":"Move the follow button closer to the profile name","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.13,"slice":"boundary","lang":"en"} -{"prompt":"Write an operator guide for replaying failed feed events without restoring deleted content.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Implement moderation-appeal endpoints with evidence, deadlines, decisions, and authorization, then document lifecycle, examples, and errors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Map out a migration from fan-out-on-write feeds to hybrid fan-out, including celebrities, privacy, deletes, ranking, consistency, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"core","lang":"en"} -{"prompt":"Rename `postNo` to `postNumber` in `FeedMapper.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"en"} -{"prompt":"Teach the notification worker to collapse repeated reactions while preserving distinct actors and undo events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Polish the creator stats card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.28,"slice":"core","lang":"en"} -{"prompt":"Bump `react-native-reanimated` to `4.0.2`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Rename `MasterFeed` to `PrimaryFeed` across services, events, metrics, and tests while preserving API fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.64,"slice":"boundary","lang":"en"} -{"prompt":"Split `CommunityService` into publishing, audience, engagement, moderation, and feed components without changing behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.81,"slice":"core","lang":"en"} -{"prompt":"Implementation ticket:\n\n```text\nSOCIAL-6114 — post edit history\nEvery edit creates immutable revision with body, attachments, audience, and edit time\nPublic UI shows edited indicator but not full history by default\nModerators can inspect all revisions\nAuthors may restore a prior text revision, but deleted attachments are not recreated\nSearch and feed should expose only active revision\nMentions added by edit may notify once; removed mentions do not notify\nEdits after moderation removal require review before republishing\nExpose edit, restore, review-required, and stale-index metrics\n```\n\nImplement revisions, restore, moderation interaction, search and feed updates, mentions, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Investigate why the Android feed sometimes shows the same video twice after reconnecting.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Create the moderation-history UI and add a concise guide for automated flags, human decisions, appeals, reversals, and policy versions.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Why does the search index retain deleted user handles as aliases? Explain current redirect and abuse-prevention behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.49,"slice":"core","lang":"en"} -{"prompt":"Rewrite the local setup for running Redpanda, Meilisearch, MinIO, and the synthetic community generator.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"This block test fails only when requests race:\n\n```text\nuser A follows B version=19\nA feed fanout receives B post p_88\nA blocks B version=20\nblock projection removes B items from current feed\nin-flight fanout worker holds audience snapshot version=19\nworker inserts p_88 after removal transaction\nfeed query checks materialized rows but not current block graph\nA sees p_88 until next compaction\n```\n\nDetermine why block enforcement relies on projection ordering and whether read-time filtering or generation fencing is missing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.77,"slice":"boundary","lang":"en"} -{"prompt":"finish the moderation API","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} -{"prompt":"Propose an architecture for privacy-preserving social recommendations, including consent, graph signals, sensitive attributes, blocks, deletion, explanations, and evaluation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"core","lang":"en"} -{"prompt":"Add ActivityPub collection parsing to `federationctl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Review excerpt:\n\n```diff\n async function getPost(req) {\n- const post = await posts.load(req.params.id)\n- if (!await audience.canView(req.user, post)) throw forbidden()\n- return post\n+ const post = await posts.load(req.params.id)\n+ audience.canView(req.user, post).catch(logger.warn)\n+ return post\n }\n```\n\nThe author says audience checks add feed latency. Review private groups, blocks, deleted accounts, stale membership, audit, and asynchronous failure. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"pasted-context","lang":"en"} -{"prompt":"Schreibe eine kurze Referenz für die bestehenden Moderationsstatus und ihre Auswirkungen auf Sichtbarkeit und Einspruch. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"de"} -{"prompt":"Build the desktop moderation queue with filters, evidence, policy context, keyboard review, decisions, and safe previews.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Review how notification preferences interact with mutes and blocks, then turn the findings into a user guide with examples.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.61,"slice":"mixed","lang":"en"} -{"prompt":"Set the post edit window to 30 minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Benenne `FeedCtx` repositoryweit in `FeedContext` um; JSON-Felder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"de"} +{"prompt":"Write an onboarding guide for adding a new quality specification, including tests, units, limits, revisions, and approval.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Consolidate work-order status formatting across UI and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why expired tools remain selectable in work instructions.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add transactional material ownership transfer between plants with inventory and genealogy checks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Set the work-queue refresh to 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile material-movement flow with scan, source, destination, quantity, validation, and accessible confirmation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"把 `Materail held` 改成 `Material held`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"zh"} +{"prompt":"Inspect the batch-record import path for path traversal, signature bypass, malicious attachments, huge records, and tenant confusion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement lot-genealogy history and write its API documentation. Include edges, revisions, corrections, recall scope, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Design a community-content architecture for posts, comments, reactions, moderation, edits, deletions, feeds, notifications, and appeals. Cover immutable history, audience changes, privacy, ranking, regional storage, migration from the current activity tables, and rollout milestones. Deliver an RFC only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Before implementing community notes, outline authoring, evidence, contributor reputation, scoring, visibility thresholds, appeals, abuse resistance, explanations, and phased launch.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add comment threading to `/v3/posts`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Moderation incident logs:\n\n```text\npost=p_881 author=u_71 audience=private_group:g_18\nmoderation action=remove reason=personal_data version=12\nfeed delete event published offset=77110\nsearch delete event published offset=44192\nappeal accepted version=13 restore=true audience=private_group:g_18\nfeed restore applies version=13\nsearch restore consumer uses stored document audience=public from version=9\npost appears in public search for 47s\npermission index refresh later removes it\n```\n\nDetermine why restoration uses stale audience metadata and how search visibility becomes public before authorization filtering catches up.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Build the SwiftUI community-feed screen with mixed media, reactions, comment previews, moderation states, pagination, and VoiceOver support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Plan and implement a content-moderation decision service. Begin with a design covering policy versions, automated signals, human review, severity, regional rules, emergency removal, appeals, transparency, audit replay, and failure behavior. Then add the evaluator, queues, decision APIs, and conformance tests. Treat policy semantics and due process as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":1.0,"slice":"mixed","lang":"en"} +{"prompt":"Set `MAX_COMMENT_DEPTH` to 8","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Extract duplicated audience resolution from posts and collections while preserving every visibility decision.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Implement `/internal/moderation/queues` with pending age, priority, assignments, decisions, and SLA breaches.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"make the profile more alive","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Find why blocked users occasionally reappear in suggested follows after refreshing the app.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Explain how `FeedMixer` balances followed accounts, groups, recommendations, and freshness. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Community launch notes:\n\n```text\nFeature: comment controls\nPost author may allow everyone, followers, mentioned people, group members, or nobody to comment\nChanging the setting affects new comments only\nExisting comments remain visible unless separately hidden\nModerators may still comment on locked posts for official notices\nShared posts use the original post's comment policy\nOld mobile clients show a generic comments unavailable message\nComment controls do not prevent quote posts\n```\n\nTurn this into release notes and a help article with examples, limitations, and old-client behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"Move the follow button closer to the profile name","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Write an operator guide for replaying failed feed events without restoring deleted content.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Implement moderation-appeal endpoints with evidence, deadlines, decisions, and authorization, then document lifecycle, examples, and errors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Map out a migration from fan-out-on-write feeds to hybrid fan-out, including celebrities, privacy, deletes, ranking, consistency, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Rename `postNo` to `postNumber` in `FeedMapper.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Teach the notification worker to collapse repeated reactions while preserving distinct actors and undo events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Polish the creator stats card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump `react-native-reanimated` to `4.0.2`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename `MasterFeed` to `PrimaryFeed` across services, events, metrics, and tests while preserving API fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Split `CommunityService` into publishing, audience, engagement, moderation, and feed components without changing behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implementation ticket:\n\n```text\nSOCIAL-6114 — post edit history\nEvery edit creates immutable revision with body, attachments, audience, and edit time\nPublic UI shows edited indicator but not full history by default\nModerators can inspect all revisions\nAuthors may restore a prior text revision, but deleted attachments are not recreated\nSearch and feed should expose only active revision\nMentions added by edit may notify once; removed mentions do not notify\nEdits after moderation removal require review before republishing\nExpose edit, restore, review-required, and stale-index metrics\n```\n\nImplement revisions, restore, moderation interaction, search and feed updates, mentions, metrics, and tests.","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Investigate why the Android feed sometimes shows the same video twice after reconnecting.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the moderation-history UI and add a concise guide for automated flags, human decisions, appeals, reversals, and policy versions.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Why does the search index retain deleted user handles as aliases? Explain current redirect and abuse-prevention behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Rewrite the local setup for running Redpanda, Meilisearch, MinIO, and the synthetic community generator.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"This block test fails only when requests race:\n\n```text\nuser A follows B version=19\nA feed fanout receives B post p_88\nA blocks B version=20\nblock projection removes B items from current feed\nin-flight fanout worker holds audience snapshot version=19\nworker inserts p_88 after removal transaction\nfeed query checks materialized rows but not current block graph\nA sees p_88 until next compaction\n```\n\nDetermine why block enforcement relies on projection ordering and whether read-time filtering or generation fencing is missing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"finish the moderation API","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Propose an architecture for privacy-preserving social recommendations, including consent, graph signals, sensitive attributes, blocks, deletion, explanations, and evaluation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add ActivityPub collection parsing to `federationctl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Review excerpt:\n\n```diff\n async function getPost(req) {\n- const post = await posts.load(req.params.id)\n- if (!await audience.canView(req.user, post)) throw forbidden()\n- return post\n+ const post = await posts.load(req.params.id)\n+ audience.canView(req.user, post).catch(logger.warn)\n+ return post\n }\n```\n\nThe author says audience checks add feed latency. Review private groups, blocks, deleted accounts, stale membership, audit, and asynchronous failure. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Schreibe eine kurze Referenz für die bestehenden Moderationsstatus und ihre Auswirkungen auf Sichtbarkeit und Einspruch. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"de"} +{"prompt":"Build the desktop moderation queue with filters, evidence, policy context, keyboard review, decisions, and safe previews.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Review how notification preferences interact with mutes and blocks, then turn the findings into a user guide with examples.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Set the post edit window to 30 minutes","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Benenne `FeedCtx` repositoryweit in `FeedContext` um; JSON-Felder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"de"} {"prompt":"Consolidate mention normalization across posts and comments without changing resolved users.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Diagnose the duplicate follower alert","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Explain how the moderation sampler selects low-confidence automated decisions for human review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Create API documentation for the existing post-audience endpoint, including transitions, restrictions, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"en"} -{"prompt":"Plan a migration from one global social graph to region-owned graph partitions, including follows, blocks, moves, reads, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"core","lang":"en"} -{"prompt":"Mobile design ticket:\n\n```text\nScreen: post composer\nSupports text, up to ten media items, alt text, audience, content warning, location toggle, scheduled time\nDraft autosaves locally and to cloud when signed in\nChanging audience may invalidate tagged group references\nUpload progress persists if composer closes\nPublishing can return moderation-review state instead of success\nAccessibility: media reorder has buttons, not drag only; every image prompts for alt text\nOffline mode saves draft but cannot schedule publication\n```\n\nImplement the iOS composer and UI tests using existing publishing APIs.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.73,"slice":"pasted-context","lang":"en"} -{"prompt":"Implement `POST /v1/posts/{id}/hide` with scope, reason, revision checks, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Remove the extra heart from the reaction label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"core","lang":"en"} -{"prompt":"Fix the clipped audience chip and extract its duplicated padding into the shared composer token.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.35,"slice":"mixed","lang":"en"} -{"prompt":"Replace scattered post booleans with one explicit publication state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Cambia `postRev` por `postRevision` solo en `ComposerState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"es"} -{"prompt":"Investigate why the app briefly displays another account's private drafts after account switching.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Summarize the current moderation-appeal workflow for policy and compliance reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"Develop a capacity roadmap for serving 100 million personalized feeds. Include graph storage, fan-out, ranking, caches, deletes, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.96,"slice":"core","lang":"en"} -{"prompt":"Implement idempotent report ingestion with reporter privacy and duplicate clustering.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Create the Compose profile screen with tabs, counts, follow state, moderation notices, and TalkBack order.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Fix `moderaton` in `events.proto`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} -{"prompt":"Merge duplicate audience types used by feed and search while preserving serialized values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Appeal projection failure:\n\n```text\ncontent=c_991 decision=remove version=18\nappeal accepted version=19 at=10:01:12\nmoderation projection writes visible=true\ncheckpoint transaction fails\nnotification worker observes visible=true and tells author restored\nprojection restarts and replays accepted event\nstate machine rejects already-accepted appeal\npartition stops; search restoration event was never emitted\npost remains missing from search despite author notice\n```\n\nDetermine how projection, checkpoint, notification, and downstream restoration lack one durable boundary and why replay is not idempotent.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Rename `folower_id` to `follower_id` in the unreleased migration.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"en"} -{"prompt":"Assess whether private-group posts can leak through image CDN cache keys or shared preview metadata. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Restructure the community SDK into posts, comments, graph, moderation, and feed, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Plan the retirement of legacy public follower lists, covering privacy settings, clients, exports, communication, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Add immutable provenance chains to moderation policy decisions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Build the tablet group-admin view with membership, roles, requests, rules, moderation, and accessible controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"do the feed page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.39,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `PostRef` with `PostReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why exported account archives omit restored posts, implement the verified revision-filter fix, and add a user-facing note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.78,"slice":"mixed","lang":"en"} -{"prompt":"Why does the feed service retain two previous ranking configurations? Explain current experiment rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.47,"slice":"boundary","lang":"en"} -{"prompt":"Track down the memory leak in video-preview workers after repeated scrubbing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Write release notes for profile audience controls, including followers, groups, search visibility, and old-client behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.36,"slice":"core","lang":"en"} -{"prompt":"Feed-ranking notes:\n\n```text\nCandidate sources: follows, groups, popular nearby, recommendations\nHard filters: blocks, mutes, audience, removed content, age policy\nRanking signals include recency, affinity, predicted engagement, diversity\nUsers can choose chronological mode\nSensitive-topic engagement cannot feed recommendations\nSeen-post state syncs across devices with delay\nSponsored posts have fixed insertion constraints\nFallback during model outage is follows sorted by time\n```\n\nProduce an implementation-free design and rollout plan covering candidates, filters, ranking, privacy, modes, ads, failure, evaluation, and explanations.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"pasted-context","lang":"en"} -{"prompt":"Give the comment thread clearer nesting","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.32,"slice":"core","lang":"en"} -{"prompt":"Turn the current account-deletion behavior into user documentation, then review whether removal and retention claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Outline a phased architecture for moving media moderation from synchronous upload checks to asynchronous review, without implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.84,"slice":"boundary","lang":"en"} -{"prompt":"Implement version-aware group-membership history with effective dates and audit links.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Create an operator guide for diagnosing delayed feed deletions.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} -{"prompt":"Move content-warning resolution out of `PostController` while preserving visibility.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Investigate why revoked group membership remains active in one regional websocket gateway.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Add generation-fenced moderation-policy publication with simulation and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Set the reaction limit to 50","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Create the responsive saved-posts view with collections, filters, bulk actions, offline state, and accessible navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Corrige apenas `folowing` para `following` no novo título.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"pt"} -{"prompt":"Review the media-upload endpoint for EXIF privacy, malicious files, tenant spoofing, quota bypass, and partial publication.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Implement moderation-case history and write its API guide. Include signals, assignments, decisions, appeals, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Design a migration from username identity to stable account IDs with change history, aliases, links, abuse controls, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"core","lang":"en"} -{"prompt":"Add resumable account-archive generation with checksums and deletion awareness.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Build the desktop audience-policy editor with roles, conditions, preview, conflicts, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"continue the block bug","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"Extract handle normalization into one shared module while preserving canonical values and aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why scheduled posts use an outdated audience, implement the verified snapshot-binding fix, and update creator documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.77,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed graph cache for blocks, private follows, account deletion, stale membership, and tenant isolation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"Find why one moderation worker retries an unsupported media type forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Draft a migration guide for bot developers moving from polling to community event subscriptions.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} -{"prompt":"Recommendation incident excerpt:\n\n```text\nuser=u_771 blocks topic=t_19 at=11:00:01\npreference projection updates excluded_topics version=91\nrecommendation batch built at=10:59:58 with candidates including topic=t_19\ncache key=user:u_771:feed generation=90\nrequest at=11:00:07 reads cached batch\nread-time filter checks blocked users but not excluded topics\nuser receives five posts from blocked topic\ncache invalidation event delayed behind partition rebalance\n```\n\nDetermine why topic exclusion relies solely on cache invalidation while user blocking has read-time enforcement, and which consistency guarantee is missing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.78,"slice":"pasted-context","lang":"en"} -{"prompt":"Add audience text below the post status","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.24,"slice":"core","lang":"en"} -{"prompt":"Restructure the feed pipeline and document its candidate-source interface. Preserve results while separating retrieval, filtering, ranking, mixing, and hydration.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.82,"slice":"mixed","lang":"en"} -{"prompt":"Architect a globally distributed social graph with regional ownership, moves, follows, blocks, privacy, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed moderation receipts with content revision and policy digest.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new moderation rule, including policy, signals, queues, explanations, tests, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"Consolidate engagement-count formatting across app and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Investigate why deleted groups remain in invite autocomplete.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} +{"prompt":"Diagnose the duplicate follower alert","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Explain how the moderation sampler selects low-confidence automated decisions for human review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Create API documentation for the existing post-audience endpoint, including transitions, restrictions, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Plan a migration from one global social graph to region-owned graph partitions, including follows, blocks, moves, reads, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Mobile design ticket:\n\n```text\nScreen: post composer\nSupports text, up to ten media items, alt text, audience, content warning, location toggle, scheduled time\nDraft autosaves locally and to cloud when signed in\nChanging audience may invalidate tagged group references\nUpload progress persists if composer closes\nPublishing can return moderation-review state instead of success\nAccessibility: media reorder has buttons, not drag only; every image prompts for alt text\nOffline mode saves draft but cannot schedule publication\n```\n\nImplement the iOS composer and UI tests using existing publishing APIs.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Implement `POST /v1/posts/{id}/hide` with scope, reason, revision checks, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Remove the extra heart from the reaction label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Fix the clipped audience chip and extract its duplicated padding into the shared composer token.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Replace scattered post booleans with one explicit publication state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Cambia `postRev` por `postRevision` solo en `ComposerState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"es"} +{"prompt":"Investigate why the app briefly displays another account's private drafts after account switching.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Summarize the current moderation-appeal workflow for policy and compliance reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Develop a capacity roadmap for serving 100 million personalized feeds. Include graph storage, fan-out, ranking, caches, deletes, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement idempotent report ingestion with reporter privacy and duplicate clustering.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create the Compose profile screen with tabs, counts, follow state, moderation notices, and TalkBack order.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Fix `moderaton` in `events.proto`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Merge duplicate audience types used by feed and search while preserving serialized values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Appeal projection failure:\n\n```text\ncontent=c_991 decision=remove version=18\nappeal accepted version=19 at=10:01:12\nmoderation projection writes visible=true\ncheckpoint transaction fails\nnotification worker observes visible=true and tells author restored\nprojection restarts and replays accepted event\nstate machine rejects already-accepted appeal\npartition stops; search restoration event was never emitted\npost remains missing from search despite author notice\n```\n\nDetermine how projection, checkpoint, notification, and downstream restoration lack one durable boundary and why replay is not idempotent.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Rename `folower_id` to `follower_id` in the unreleased migration.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Assess whether private-group posts can leak through image CDN cache keys or shared preview metadata. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Restructure the community SDK into posts, comments, graph, moderation, and feed, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan the retirement of legacy public follower lists, covering privacy settings, clients, exports, communication, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add immutable provenance chains to moderation policy decisions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Build the tablet group-admin view with membership, roles, requests, rules, moderation, and accessible controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"do the feed page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `PostRef` with `PostReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose why exported account archives omit restored posts, implement the verified revision-filter fix, and add a user-facing note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the feed service retain two previous ranking configurations? Explain current experiment rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down the memory leak in video-preview workers after repeated scrubbing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write release notes for profile audience controls, including followers, groups, search visibility, and old-client behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Feed-ranking notes:\n\n```text\nCandidate sources: follows, groups, popular nearby, recommendations\nHard filters: blocks, mutes, audience, removed content, age policy\nRanking signals include recency, affinity, predicted engagement, diversity\nUsers can choose chronological mode\nSensitive-topic engagement cannot feed recommendations\nSeen-post state syncs across devices with delay\nSponsored posts have fixed insertion constraints\nFallback during model outage is follows sorted by time\n```\n\nProduce an implementation-free design and rollout plan covering candidates, filters, ranking, privacy, modes, ads, failure, evaluation, and explanations.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Give the comment thread clearer nesting","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Turn the current account-deletion behavior into user documentation, then review whether removal and retention claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Outline a phased architecture for moving media moderation from synchronous upload checks to asynchronous review, without implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement version-aware group-membership history with effective dates and audit links.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create an operator guide for diagnosing delayed feed deletions.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Move content-warning resolution out of `PostController` while preserving visibility.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why revoked group membership remains active in one regional websocket gateway.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add generation-fenced moderation-policy publication with simulation and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Set the reaction limit to 50","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Create the responsive saved-posts view with collections, filters, bulk actions, offline state, and accessible navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Corrige apenas `folowing` para `following` no novo título.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"pt"} +{"prompt":"Review the media-upload endpoint for EXIF privacy, malicious files, tenant spoofing, quota bypass, and partial publication.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement moderation-case history and write its API guide. Include signals, assignments, decisions, appeals, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Design a migration from username identity to stable account IDs with change history, aliases, links, abuse controls, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add resumable account-archive generation with checksums and deletion awareness.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Build the desktop audience-policy editor with roles, conditions, preview, conflicts, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Extract handle normalization into one shared module while preserving canonical values and aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Investigate why scheduled posts use an outdated audience, implement the verified snapshot-binding fix, and update creator documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed graph cache for blocks, private follows, account deletion, stale membership, and tenant isolation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Find why one moderation worker retries an unsupported media type forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft a migration guide for bot developers moving from polling to community event subscriptions.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Recommendation incident excerpt:\n\n```text\nuser=u_771 blocks topic=t_19 at=11:00:01\npreference projection updates excluded_topics version=91\nrecommendation batch built at=10:59:58 with candidates including topic=t_19\ncache key=user:u_771:feed generation=90\nrequest at=11:00:07 reads cached batch\nread-time filter checks blocked users but not excluded topics\nuser receives five posts from blocked topic\ncache invalidation event delayed behind partition rebalance\n```\n\nDetermine why topic exclusion relies solely on cache invalidation while user blocking has read-time enforcement, and which consistency guarantee is missing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Add audience text below the post status","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Restructure the feed pipeline and document its candidate-source interface. Preserve results while separating retrieval, filtering, ranking, mixing, and hydration.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Architect a globally distributed social graph with regional ownership, moves, follows, blocks, privacy, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Implement signed moderation receipts with content revision and policy digest.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new moderation rule, including policy, signals, queues, explanations, tests, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Consolidate engagement-count formatting across app and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why deleted groups remain in invite autocomplete.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Add transactional group ownership transfer with role checks and immutable history.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Pin ActivityPub library to `2.6.1`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Build the mobile appeal-status screen with timeline, evidence, deadlines, decision, support, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Remplace `Comunity` par `Community` uniquement dans le nouveau titre.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"fr"} -{"prompt":"Inspect the federation inbox for signature confusion, replay, remote deletes, oversized activities, and SSRF through actor URLs.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Implement audience-change history and write its API documentation. Include revisions, affected content, actor, pagination, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.69,"slice":"mixed","lang":"en"} -{"prompt":"Develop a roadmap for replacing manually configured trend lists with abuse-resistant automated detection, including review, transparency, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"core","lang":"en"} -{"prompt":"Add bounded event replay for feed projections with durable checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Create the responsive creator dashboard with reach, engagement, audience, moderation status, filters, and accessible charts.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} +{"prompt":"Pin ActivityPub library to `2.6.1`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile appeal-status screen with timeline, evidence, deadlines, decision, support, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remplace `Comunity` par `Community` uniquement dans le nouveau titre.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"fr"} +{"prompt":"Inspect the federation inbox for signature confusion, replay, remote deletes, oversized activities, and SSRF through actor URLs.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement audience-change history and write its API documentation. Include revisions, affected content, actor, pagination, examples, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Develop a roadmap for replacing manually configured trend lists with abuse-resistant automated detection, including review, transparency, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add bounded event replay for feed projections with durable checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the responsive creator dashboard with reach, engagement, audience, moderation status, filters, and accessible charts.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"fix privacy","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `ModEvt` with `ModerationEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why restored accounts remain hidden from followers, implement the verified graph projection fix, and update help documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.75,"slice":"mixed","lang":"en"} -{"prompt":"Why does the post service retain two previous rendering configurations? Explain current rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.46,"slice":"boundary","lang":"en"} -{"prompt":"Track down occasional missing reactions after websocket reconnect.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Write a troubleshooting guide for missing posts, covering audience, blocks, moderation, indexing, and feed ranking.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.42,"slice":"core","lang":"en"} -{"prompt":"Safety review packet:\n\n```text\nFeature: temporary account visibility limit\nModerator can prevent an account's posts from recommendation surfaces for up to seven days\nFollowers still receive posts\nAccount owner is notified after the action starts, unless investigation exception applies\nAction requires policy reason and evidence link\nAppeal is available after notification\nExisting cached recommendations may contain the account\nSearch ranking is reduced but direct profile access remains\nEmergency moderators may apply action without second review\n```\n\nReview scope, cache propagation, transparency exceptions, appeal timing, search semantics, emergency authority, and audit. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a loading state to the profile posts","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Plan and implement temporary visibility limits. First define scope, notification, exceptions, cache behavior, appeals, emergency authority, audit, and rollout; then add enforcement.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.92,"slice":"mixed","lang":"en"} -{"prompt":"Outline an architecture for interoperable social federation with identity, trust, moderation, deletion, privacy, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"boundary","lang":"en"} -{"prompt":"Implement snapshot-consistent account exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Escribe una guía para integrar aplicaciones comunitarias, con eventos, firmas, reintentos, moderación y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"es"} -{"prompt":"Move notification-audience calculation out of the delivery worker without changing recipients.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Investigate why the iOS app loses scheduled drafts after restoring a backup.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Add atomic content-policy publication with simulation, approval, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Remove the obsolete `legacy_feed` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"core","lang":"en"} -{"prompt":"Build the group-rule editor with sections, acknowledgement, versions, preview, and accessible controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"`Coment removed` を `Comment removed` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"ja"} -{"prompt":"Review the account-archive download path for deleted-content leakage, stale URLs, private-group data, cache confusion, and enumeration.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"Implement content-revision history and write its API guide. Include edits, audiences, moderation, restoration, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Plan a disaster-recovery strategy for community services, including graph, content, media, moderation, search, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Add content-hash deduplication to uploaded post media with account-scoped ownership.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Create the desktop transparency-report explorer with categories, regions, trends, methodology, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"continue the feed cleanup","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"Rename `AudienceRev` to `AudienceRevision` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why removed followers still receive private-post alerts, implement the verified recipient fix, and update user docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.78,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed feed cache for blocks, mutes, audience changes, account moves, deletions, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"Find why a federation worker retries a permanently rejected activity forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Draft a support guide for recovering an interrupted account export.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Graph projection failure:\n\n```text\nuser=u_881 follows=u_441 event offset=99110\nprojection inserts edge and increments follower count\ncheckpoint transaction fails\nnotification worker observes edge and sends follow alert\nprojection restarts and replays event\nunique edge constraint rejects duplicate before count idempotency logic\npartition stops; later block event waits behind failure\n```\n\nDetermine how edge, count, checkpoint, and notification lack one atomic boundary and why duplicate replay stops rather than converges.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.81,"slice":"pasted-context","lang":"en"} -{"prompt":"Add policy reason below the moderation status","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Restructure the moderation pipeline and document its signal-provider interface. Preserve decisions while separating intake, signals, policy, review, and enforcement.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.83,"slice":"mixed","lang":"en"} -{"prompt":"Architect a global content platform with regional ownership, audience enforcement, moderation, search, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed account-export manifests with revision and content digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new feed candidate source, including filters, privacy, ranking, fixtures, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Consolidate audience-label formatting across app and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Investigate why expired visibility limits remain active in search ranking.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.62,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional account transfer between regional graph partitions with follow and block history.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Set the feed cache TTL to 90s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Build the mobile privacy-controls screen with audiences, discoverability, blocks, mutes, and accessible explanations.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"把 `Folower request` 改成 `Follower request`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"zh"} -{"prompt":"Inspect the moderation-evidence upload path for malicious files, reporter leakage, stale authorization, tenant confusion, and quota abuse.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} +{"prompt":"Replace `ModEvt` with `ModerationEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose why restored accounts remain hidden from followers, implement the verified graph projection fix, and update help documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Why does the post service retain two previous rendering configurations? Explain current rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Track down occasional missing reactions after websocket reconnect.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Write a troubleshooting guide for missing posts, covering audience, blocks, moderation, indexing, and feed ranking.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Safety review packet:\n\n```text\nFeature: temporary account visibility limit\nModerator can prevent an account's posts from recommendation surfaces for up to seven days\nFollowers still receive posts\nAccount owner is notified after the action starts, unless investigation exception applies\nAction requires policy reason and evidence link\nAppeal is available after notification\nExisting cached recommendations may contain the account\nSearch ranking is reduced but direct profile access remains\nEmergency moderators may apply action without second review\n```\n\nReview scope, cache propagation, transparency exceptions, appeal timing, search semantics, emergency authority, and audit. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add a loading state to the profile posts","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Plan and implement temporary visibility limits. First define scope, notification, exceptions, cache behavior, appeals, emergency authority, audit, and rollout; then add enforcement.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Outline an architecture for interoperable social federation with identity, trust, moderation, deletion, privacy, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement snapshot-consistent account exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Escribe una guía para integrar aplicaciones comunitarias, con eventos, firmas, reintentos, moderación y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"es"} +{"prompt":"Move notification-audience calculation out of the delivery worker without changing recipients.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why the iOS app loses scheduled drafts after restoring a backup.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add atomic content-policy publication with simulation, approval, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Remove the obsolete `legacy_feed` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Build the group-rule editor with sections, acknowledgement, versions, preview, and accessible controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"`Coment removed` を `Comment removed` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"ja"} +{"prompt":"Review the account-archive download path for deleted-content leakage, stale URLs, private-group data, cache confusion, and enumeration.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement content-revision history and write its API guide. Include edits, audiences, moderation, restoration, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan a disaster-recovery strategy for community services, including graph, content, media, moderation, search, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add content-hash deduplication to uploaded post media with account-scoped ownership.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the desktop transparency-report explorer with categories, regions, trends, methodology, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Rename `AudienceRev` to `AudienceRevision` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why removed followers still receive private-post alerts, implement the verified recipient fix, and update user docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed feed cache for blocks, mutes, audience changes, account moves, deletions, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why a federation worker retries a permanently rejected activity forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft a support guide for recovering an interrupted account export.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Graph projection failure:\n\n```text\nuser=u_881 follows=u_441 event offset=99110\nprojection inserts edge and increments follower count\ncheckpoint transaction fails\nnotification worker observes edge and sends follow alert\nprojection restarts and replays event\nunique edge constraint rejects duplicate before count idempotency logic\npartition stops; later block event waits behind failure\n```\n\nDetermine how edge, count, checkpoint, and notification lack one atomic boundary and why duplicate replay stops rather than converges.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add policy reason below the moderation status","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Restructure the moderation pipeline and document its signal-provider interface. Preserve decisions while separating intake, signals, policy, review, and enforcement.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Architect a global content platform with regional ownership, audience enforcement, moderation, search, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement signed account-export manifests with revision and content digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new feed candidate source, including filters, privacy, ranking, fixtures, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Consolidate audience-label formatting across app and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why expired visibility limits remain active in search ranking.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add transactional account transfer between regional graph partitions with follow and block history.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Set the feed cache TTL to 90s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile privacy-controls screen with audiences, discoverability, blocks, mutes, and accessible explanations.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"把 `Folower request` 改成 `Follower request`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"zh"} +{"prompt":"Inspect the moderation-evidence upload path for malicious files, reporter leakage, stale authorization, tenant confusion, and quota abuse.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Implement feed-ranking history and write its API documentation. Include configuration, experiments, activation, rollback, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Design a workforce-record architecture for employment, positions, compensation, benefits, leave, time, approvals, and historical corrections. Cover effective dating, tenant isolation, auditability, privacy, payroll snapshots, regional rules, migration from mutable HR tables, and rollout milestones. Deliver an RFC only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"core","lang":"en"} -{"prompt":"Before implementing global payroll, outline earnings, deductions, taxes, currencies, calendars, retroactive changes, approvals, reconciliation, country adapters, and phased rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"boundary","lang":"en"} -{"prompt":"Add effective-date filtering to `/v2/employees`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.56,"slice":"core","lang":"en"} -{"prompt":"Payroll incident logs:\n\n```text\nemployee=e_881 pay_period=2026-07-01..2026-07-15\nbase_hours=80 overtime_hours=6\nmanager approves timesheet version=18 at=16:01:12\npayroll snapshot captures version=18 at=16:01:13\nemployee correction removes 2 overtime hours version=19 at=16:01:14\ncorrection workflow status=pending_approval\nretro engine reads current timesheet version=19 without approval filter\npayroll calculation uses overtime_hours=4\npayslip audit references approved version=18\n```\n\nDetermine why calculation reads an unapproved correction while audit metadata remains pinned to the approved snapshot.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.83,"slice":"pasted-context","lang":"en"} -{"prompt":"Build the SwiftUI payslip screen with earnings, deductions, taxes, year-to-date totals, download, privacy mode, and VoiceOver support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Plan and implement an effective-dated compensation service. Begin with a design covering salary, hourly rates, currencies, recurring allowances, approvals, future changes, retroactivity, payroll snapshots, audit, and migration. Then add APIs, versioned storage, approval flows, and conformance tests. Treat temporal semantics as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.96,"slice":"mixed","lang":"en"} -{"prompt":"Set `MAX_CARRYOVER_DAYS` to 10","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Extract duplicated work-email normalization from hiring and directory sync while preserving validation.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Implement `/internal/payroll/runs` with status, country, employee count, exceptions, approval, and age.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} -{"prompt":"make the HR portal warmer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.41,"slice":"vague-eval","lang":"en"} -{"prompt":"Find why approved leave occasionally disappears from the team calendar after a manager transfer.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Explain how `LeaveBalanceCalculator` orders accrual, carryover, usage, expiry, and manual adjustment. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Employee launch notes:\n\n```text\nFeature: preferred-name history\nEmployees may change preferred first and display names\nLegal name remains separate and requires HR verification\nDirectory, chat, and org chart update after synchronization\nHistorical reports retain the name effective at report time when required\nManagers are notified only when configured by organization\nOld mobile clients may show prior name until next full refresh\nChanging preferred name does not alter payroll or tax documents\n```\n\nTurn this into release notes and an employee help article. Clearly distinguish preferred and legal name behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.44,"slice":"pasted-context","lang":"en"} -{"prompt":"Move the leave balance below the policy name","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.13,"slice":"boundary","lang":"en"} -{"prompt":"Write an operator guide for replaying failed payroll events without issuing duplicate payments.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"Implement employee-document endpoints with type filters, signed downloads, and authorization, then document expiry, examples, and errors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Map out a migration from manager-owned spreadsheets to a centralized headcount-planning model, including scenarios, permissions, versions, imports, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"core","lang":"en"} -{"prompt":"Rename `empNo` to `employeeNumber` in `PayrollMapper.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"en"} -{"prompt":"Teach the time importer to process overnight shifts across pay-period boundaries with row-level errors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Polish the benefits summary card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.28,"slice":"core","lang":"en"} -{"prompt":"Bump `date-fns` to `4.1.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Rename `MasterPosition` to `PrimaryPosition` across services, events, reports, and tests while preserving public fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.64,"slice":"boundary","lang":"en"} -{"prompt":"Split `PayrollService` into input, calculation, validation, approval, payment, and reporting components without changing results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.86,"slice":"core","lang":"en"} -{"prompt":"Implementation ticket:\n\n```text\nHR-4408 — employee position changes\nChange types: promotion, transfer, title change, manager change, location change, hours change\nEvery change has proposed effective date, reason, fields, approvals, and attachments\nOverlapping future changes must be validated in effective-date order\nApproval requirements depend on compensation and country\nApproved changes may be cancelled before effective date with audit event\nActivation updates directory, permissions, payroll, and reporting through events\nDuplicate integration events are expected\n```\n\nImplement the version model, validation, approvals, cancellation, activation, events, idempotency, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.88,"slice":"pasted-context","lang":"en"} -{"prompt":"Investigate why the Android shift app assigns a clock-in to the previously selected job code.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Create the position-change review UI and add a concise guide for effective date, field changes, approvals, dependencies, and activation.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.66,"slice":"mixed","lang":"en"} -{"prompt":"Why does the payroll service retain voided calculations in year-to-date aggregates? Explain current correction behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Rewrite the local setup for running Keycloak, Postgres, the payroll simulator, and synthetic employees.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"This leave test fails around an employee transfer:\n\n```text\nemployee=e_17 old_policy=US-CA new_policy=US-NY transfer_effective=2026-08-01\nleave request dates=2026-07-30..2026-08-03\nexpected hours=16 CA + 16 NY\nactual hours=32 NY\nrequest service resolves policy at request end date\nbalance service resolves each work date\napproval preview uses one policy, posting uses two\n```\n\nDetermine which temporal semantics should govern a leave request spanning policy changes and why preview and posting disagree.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"finish the payroll endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} +{"prompt":"Design a workforce-record architecture for employment, positions, compensation, benefits, leave, time, approvals, and historical corrections. Cover effective dating, tenant isolation, auditability, privacy, payroll snapshots, regional rules, migration from mutable HR tables, and rollout milestones. Deliver an RFC only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Before implementing global payroll, outline earnings, deductions, taxes, currencies, calendars, retroactive changes, approvals, reconciliation, country adapters, and phased rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add effective-date filtering to `/v2/employees`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Payroll incident logs:\n\n```text\nemployee=e_881 pay_period=2026-07-01..2026-07-15\nbase_hours=80 overtime_hours=6\nmanager approves timesheet version=18 at=16:01:12\npayroll snapshot captures version=18 at=16:01:13\nemployee correction removes 2 overtime hours version=19 at=16:01:14\ncorrection workflow status=pending_approval\nretro engine reads current timesheet version=19 without approval filter\npayroll calculation uses overtime_hours=4\npayslip audit references approved version=18\n```\n\nDetermine why calculation reads an unapproved correction while audit metadata remains pinned to the approved snapshot.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Build the SwiftUI payslip screen with earnings, deductions, taxes, year-to-date totals, download, privacy mode, and VoiceOver support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Plan and implement an effective-dated compensation service. Begin with a design covering salary, hourly rates, currencies, recurring allowances, approvals, future changes, retroactivity, payroll snapshots, audit, and migration. Then add APIs, versioned storage, approval flows, and conformance tests. Treat temporal semantics as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Set `MAX_CARRYOVER_DAYS` to 10","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Extract duplicated work-email normalization from hiring and directory sync while preserving validation.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement `/internal/payroll/runs` with status, country, employee count, exceptions, approval, and age.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"make the HR portal warmer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Find why approved leave occasionally disappears from the team calendar after a manager transfer.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Explain how `LeaveBalanceCalculator` orders accrual, carryover, usage, expiry, and manual adjustment. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Employee launch notes:\n\n```text\nFeature: preferred-name history\nEmployees may change preferred first and display names\nLegal name remains separate and requires HR verification\nDirectory, chat, and org chart update after synchronization\nHistorical reports retain the name effective at report time when required\nManagers are notified only when configured by organization\nOld mobile clients may show prior name until next full refresh\nChanging preferred name does not alter payroll or tax documents\n```\n\nTurn this into release notes and an employee help article. Clearly distinguish preferred and legal name behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} +{"prompt":"Move the leave balance below the policy name","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Write an operator guide for replaying failed payroll events without issuing duplicate payments.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement employee-document endpoints with type filters, signed downloads, and authorization, then document expiry, examples, and errors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Map out a migration from manager-owned spreadsheets to a centralized headcount-planning model, including scenarios, permissions, versions, imports, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Rename `empNo` to `employeeNumber` in `PayrollMapper.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Teach the time importer to process overnight shifts across pay-period boundaries with row-level errors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Polish the benefits summary card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump `date-fns` to `4.1.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename `MasterPosition` to `PrimaryPosition` across services, events, reports, and tests while preserving public fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Split `PayrollService` into input, calculation, validation, approval, payment, and reporting components without changing results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implementation ticket:\n\n```text\nHR-4408 — employee position changes\nChange types: promotion, transfer, title change, manager change, location change, hours change\nEvery change has proposed effective date, reason, fields, approvals, and attachments\nOverlapping future changes must be validated in effective-date order\nApproval requirements depend on compensation and country\nApproved changes may be cancelled before effective date with audit event\nActivation updates directory, permissions, payroll, and reporting through events\nDuplicate integration events are expected\n```\n\nImplement the version model, validation, approvals, cancellation, activation, events, idempotency, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Investigate why the Android shift app assigns a clock-in to the previously selected job code.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Create the position-change review UI and add a concise guide for effective date, field changes, approvals, dependencies, and activation.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Why does the payroll service retain voided calculations in year-to-date aggregates? Explain current correction behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Rewrite the local setup for running Keycloak, Postgres, the payroll simulator, and synthetic employees.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"This leave test fails around an employee transfer:\n\n```text\nemployee=e_17 old_policy=US-CA new_policy=US-NY transfer_effective=2026-08-01\nleave request dates=2026-07-30..2026-08-03\nexpected hours=16 CA + 16 NY\nactual hours=32 NY\nrequest service resolves policy at request end date\nbalance service resolves each work date\napproval preview uses one policy, posting uses two\n```\n\nDetermine which temporal semantics should govern a leave request spanning policy changes and why preview and posting disagree.","purpose":"planning","secondary":"debugging","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"finish the payroll endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"Propose an architecture for privacy-safe workforce analytics, including cohort thresholds, hierarchy, effective dates, access, exports, retention, and deletion.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Add ACH return-file parsing to `payrollctl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Review excerpt:\n\n```diff\n async function getPayslip(req) {\n- const allowed = await payroll.canView(req.user, req.params.employeeId)\n- if (!allowed) throw forbidden()\n- return payslips.load(req.params.id)\n+ const slip = await payslips.load(req.params.id)\n+ payroll.canView(req.user, slip.employeeId).catch(logger.warn)\n+ return slip\n }\n```\n\nThe author says authorization checks slow document downloads. Review guessed IDs, former managers, tenant isolation, audit, caching, and asynchronous denial. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"pasted-context","lang":"en"} -{"prompt":"Schreibe eine kurze Referenz für die bestehenden Abrechnungslauf-Status und ihre Auswirkungen auf Zahlungen und Korrekturen. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"de"} -{"prompt":"Build the desktop org-chart editor with vacancies, future changes, drag proposals, validation, undo, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Review how retroactive pay is calculated and applied, then turn the findings into a payroll-operator guide with examples.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.64,"slice":"mixed","lang":"en"} -{"prompt":"Set the timesheet reminder to Friday","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Benenne `LeaveCtx` repositoryweit in `LeaveContext` um; JSON-Felder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"de"} -{"prompt":"Consolidate employee-display-name formatting across directory and reports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"core","lang":"en"} -{"prompt":"Diagnose the duplicate payslip email","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Explain how the benefits engine handles eligibility when scheduled hours change mid-month.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Create API documentation for the existing leave-balance endpoint, including as-of dates, pending usage, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"boundary","lang":"en"} -{"prompt":"Plan a migration from nightly HRIS files to event-driven employee changes, covering ordering, effective dates, corrections, replay, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"core","lang":"en"} -{"prompt":"Mobile design ticket:\n\n```text\nScreen: team schedule\nViews: day, week, list\nRows show employee preferred name, shift, role, location, leave, open coverage\nManagers see only teams within their scope\nFuture position transfers change visibility on effective date\nOffline mode shows last synchronized schedule with timestamp\nShift swaps may be pending, approved, rejected, or expired\nAccessibility: status text, logical focus order, no swipe-only approvals\nPrivacy mode hides leave reason and personal notes\n```\n\nImplement the responsive iOS screen and UI tests using existing scheduling APIs.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Implement `POST /v1/timesheets/{id}/reopen` with state checks, authorization, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Remove the extra percent sign from the deduction","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"core","lang":"en"} -{"prompt":"Fix the clipped leave badge and extract its duplicated padding into the shared schedule token.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.35,"slice":"mixed","lang":"en"} -{"prompt":"Replace scattered payroll booleans with one explicit run lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Cambia `payRev` por `payRevision` solo en `PayslipState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"es"} -{"prompt":"Investigate why the manager portal briefly shows another department's salary bands after switching roles.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Summarize the current payroll-approval workflow for finance and audit reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Develop a capacity roadmap for processing payroll for 20 million workers across 80 countries. Include calendars, adapters, calculations, approvals, payments, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"core","lang":"en"} -{"prompt":"Implement idempotent tax-election ingestion with effective dates and correction versions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Create the Compose time-entry screen with shifts, breaks, job codes, validation, offline queue, and TalkBack support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Fix `compensaton` in `events.proto`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} -{"prompt":"Merge duplicate effective-date range types used by compensation and benefits while preserving serialization.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Payment-file incident:\n\n```text\npayroll_run=pr_881 country=US payment_batch=pb_41\nemployee count=4412 expected total=8,992,118.44\nACH file generated total=8,992,118.44\nupload provider timeout before receipt persistence\nretry regenerates file with same batch ID but updated creation timestamp\nprovider accepted first and second files because file hash differs\nbank duplicate detection keys on file hash\npayment reconciliation sees two provider references for one internal batch\n```\n\nDetermine how regeneration after uncertain upload changes the file identity and permits duplicate payroll payment submission.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.84,"slice":"pasted-context","lang":"en"} -{"prompt":"Rename `employe_id` to `employee_id` in the unreleased migration.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"en"} -{"prompt":"Assess whether workforce analytics filters allow inference of individual compensation through small cohorts. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Restructure the HR SDK into employees, positions, time, leave, compensation, and payroll, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.77,"slice":"mixed","lang":"en"} -{"prompt":"Plan the retirement of paper timesheets, covering devices, offline sites, signatures, exceptions, training, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"core","lang":"en"} -{"prompt":"Add immutable provenance chains to imported payroll inputs.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Build the tablet payroll-exception queue with issue groups, employee context, fixes, approvals, and accessible controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"do the employee page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.39,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `EmpRef` with `EmployeeReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why regenerated payslips omit approved retro pay, implement the verified snapshot fix, and add an employee-facing note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"Why does the compensation service retain two previous salary revisions? Explain current audit and rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.47,"slice":"boundary","lang":"en"} -{"prompt":"Track down the memory leak in payslip-rendering workers after large payroll runs.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Write release notes for delegated leave approval, including scope, fallback approvers, expiry, and visibility.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.36,"slice":"core","lang":"en"} -{"prompt":"Payroll snapshot notes:\n\n```text\nCurrent calculation reads live HR tables\nNew design pins employee, position, compensation, time, leave, benefits, and tax versions\nCorrections after snapshot may create retro items for next payroll\nEmergency correction before payment requires reopening and new approval\nSnapshot must remain reproducible for seven years\nCountry adapters receive normalized inputs plus local configuration version\nVoided runs retain snapshot and outputs\nOld reports reference run ID only\n```\n\nProduce an implementation-free snapshot model and migration plan covering identity, corrections, reopening, adapters, reproducibility, compatibility, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"pasted-context","lang":"en"} -{"prompt":"Give the compensation timeline clearer grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.31,"slice":"core","lang":"en"} -{"prompt":"Turn the current leave-accrual behavior into employee documentation, then review whether its carryover and expiry claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Outline a phased architecture for moving payroll calculations from a monolith to country adapters, without implementing them.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"boundary","lang":"en"} -{"prompt":"Implement version-aware tax configuration history with effective dates and signed publication.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Create an operator guide for diagnosing payroll runs stuck in validation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} -{"prompt":"Move overtime-rule resolution out of `TimeController` while preserving calculations.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Investigate why revoked manager access remains active in one regional employee cache.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"Add generation-fenced benefits-plan publication with simulation and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Set the payroll preview expiry to 24 hours","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Create the responsive leave-history view with accrual, usage, adjustments, expiry, filters, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Corrige apenas `payrol` para `payroll` no novo alerta.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"pt"} -{"prompt":"Review the employee-document upload endpoint for tenant spoofing, malware, sensitive filenames, stale employment, and quota bypass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Implement compensation-change history and write its API guide. Include effective dates, approvals, revisions, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Design a migration from organization-local employee IDs to a federated workforce identity, including privacy, transfers, rehires, merges, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"core","lang":"en"} -{"prompt":"Add resumable payroll-input imports with checksums and row-level validation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Build the desktop headcount-planning grid with scenarios, vacancies, costs, approvals, comparison, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"continue the leave bug","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.54,"slice":"vague-eval","lang":"en"} -{"prompt":"Extract work-location normalization into one shared module while preserving payroll jurisdictions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.61,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why benefit reminders use an outdated eligibility date, implement the verified snapshot fix, and update employee documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed payroll-results cache for employee isolation, corrections, revoked managers, regional rules, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"Find why one country adapter retries a permanently unsupported deduction forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} +{"prompt":"Add ACH return-file parsing to `payrollctl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Review excerpt:\n\n```diff\n async function getPayslip(req) {\n- const allowed = await payroll.canView(req.user, req.params.employeeId)\n- if (!allowed) throw forbidden()\n- return payslips.load(req.params.id)\n+ const slip = await payslips.load(req.params.id)\n+ payroll.canView(req.user, slip.employeeId).catch(logger.warn)\n+ return slip\n }\n```\n\nThe author says authorization checks slow document downloads. Review guessed IDs, former managers, tenant isolation, audit, caching, and asynchronous denial. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Schreibe eine kurze Referenz für die bestehenden Abrechnungslauf-Status und ihre Auswirkungen auf Zahlungen und Korrekturen. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"de"} +{"prompt":"Build the desktop org-chart editor with vacancies, future changes, drag proposals, validation, undo, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Review how retroactive pay is calculated and applied, then turn the findings into a payroll-operator guide with examples.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Set the timesheet reminder to Friday","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Benenne `LeaveCtx` repositoryweit in `LeaveContext` um; JSON-Felder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"de"} +{"prompt":"Consolidate employee-display-name formatting across directory and reports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose the duplicate payslip email","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Explain how the benefits engine handles eligibility when scheduled hours change mid-month.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Create API documentation for the existing leave-balance endpoint, including as-of dates, pending usage, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Plan a migration from nightly HRIS files to event-driven employee changes, covering ordering, effective dates, corrections, replay, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Mobile design ticket:\n\n```text\nScreen: team schedule\nViews: day, week, list\nRows show employee preferred name, shift, role, location, leave, open coverage\nManagers see only teams within their scope\nFuture position transfers change visibility on effective date\nOffline mode shows last synchronized schedule with timestamp\nShift swaps may be pending, approved, rejected, or expired\nAccessibility: status text, logical focus order, no swipe-only approvals\nPrivacy mode hides leave reason and personal notes\n```\n\nImplement the responsive iOS screen and UI tests using existing scheduling APIs.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Implement `POST /v1/timesheets/{id}/reopen` with state checks, authorization, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Remove the extra percent sign from the deduction","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fix the clipped leave badge and extract its duplicated padding into the shared schedule token.","purpose":"frontendImpl","secondary":"refactor","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Replace scattered payroll booleans with one explicit run lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Cambia `payRev` por `payRevision` solo en `PayslipState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"es"} +{"prompt":"Investigate why the manager portal briefly shows another department's salary bands after switching roles.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Summarize the current payroll-approval workflow for finance and audit reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Develop a capacity roadmap for processing payroll for 20 million workers across 80 countries. Include calendars, adapters, calculations, approvals, payments, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Implement idempotent tax-election ingestion with effective dates and correction versions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the Compose time-entry screen with shifts, breaks, job codes, validation, offline queue, and TalkBack support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Fix `compensaton` in `events.proto`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Merge duplicate effective-date range types used by compensation and benefits while preserving serialization.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Payment-file incident:\n\n```text\npayroll_run=pr_881 country=US payment_batch=pb_41\nemployee count=4412 expected total=8,992,118.44\nACH file generated total=8,992,118.44\nupload provider timeout before receipt persistence\nretry regenerates file with same batch ID but updated creation timestamp\nprovider accepted first and second files because file hash differs\nbank duplicate detection keys on file hash\npayment reconciliation sees two provider references for one internal batch\n```\n\nDetermine how regeneration after uncertain upload changes the file identity and permits duplicate payroll payment submission.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Rename `employe_id` to `employee_id` in the unreleased migration.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Assess whether workforce analytics filters allow inference of individual compensation through small cohorts. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Restructure the HR SDK into employees, positions, time, leave, compensation, and payroll, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan the retirement of paper timesheets, covering devices, offline sites, signatures, exceptions, training, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add immutable provenance chains to imported payroll inputs.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Build the tablet payroll-exception queue with issue groups, employee context, fixes, approvals, and accessible controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"do the employee page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `EmpRef` with `EmployeeReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose why regenerated payslips omit approved retro pay, implement the verified snapshot fix, and add an employee-facing note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Why does the compensation service retain two previous salary revisions? Explain current audit and rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down the memory leak in payslip-rendering workers after large payroll runs.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Write release notes for delegated leave approval, including scope, fallback approvers, expiry, and visibility.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Payroll snapshot notes:\n\n```text\nCurrent calculation reads live HR tables\nNew design pins employee, position, compensation, time, leave, benefits, and tax versions\nCorrections after snapshot may create retro items for next payroll\nEmergency correction before payment requires reopening and new approval\nSnapshot must remain reproducible for seven years\nCountry adapters receive normalized inputs plus local configuration version\nVoided runs retain snapshot and outputs\nOld reports reference run ID only\n```\n\nProduce an implementation-free snapshot model and migration plan covering identity, corrections, reopening, adapters, reproducibility, compatibility, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Give the compensation timeline clearer grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Turn the current leave-accrual behavior into employee documentation, then review whether its carryover and expiry claims match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Outline a phased architecture for moving payroll calculations from a monolith to country adapters, without implementing them.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement version-aware tax configuration history with effective dates and signed publication.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create an operator guide for diagnosing payroll runs stuck in validation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Move overtime-rule resolution out of `TimeController` while preserving calculations.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why revoked manager access remains active in one regional employee cache.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add generation-fenced benefits-plan publication with simulation and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Set the payroll preview expiry to 24 hours","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Create the responsive leave-history view with accrual, usage, adjustments, expiry, filters, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Corrige apenas `payrol` para `payroll` no novo alerta.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"pt"} +{"prompt":"Review the employee-document upload endpoint for tenant spoofing, malware, sensitive filenames, stale employment, and quota bypass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement compensation-change history and write its API guide. Include effective dates, approvals, revisions, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Design a migration from organization-local employee IDs to a federated workforce identity, including privacy, transfers, rehires, merges, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add resumable payroll-input imports with checksums and row-level validation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Build the desktop headcount-planning grid with scenarios, vacancies, costs, approvals, comparison, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Extract work-location normalization into one shared module while preserving payroll jurisdictions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why benefit reminders use an outdated eligibility date, implement the verified snapshot fix, and update employee documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed payroll-results cache for employee isolation, corrections, revoked managers, regional rules, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why one country adapter retries a permanently unsupported deduction forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Draft a migration guide for payroll partners moving from fixed-width files to the payroll API.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Leave projection failure:\n\n```text\nemployee=e_771 leave_request=l_91 approval event offset=88120\nprojection marks approved and deducts 24h pending balance\ncheckpoint transaction fails\ncalendar worker sees approved state and publishes absence\nprojection restarts and replays approval\nunique request transition rejects duplicate before balance idempotency\npartition stops; cancellation events wait behind failure\n```\n\nDetermine how request state, balance, checkpoint, and calendar publication lack one durable boundary and why replay cannot converge.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Add effective date below the position title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Restructure the payroll calculator and document its country-adapter interface. Preserve results while separating inputs, rules, calculation, validation, and outputs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.86,"slice":"mixed","lang":"en"} -{"prompt":"Architect a multi-region workforce platform with country ownership, employment history, time, payroll, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed payroll-run manifests with input versions and payment digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new payroll country, including inputs, rules, calendars, fixtures, reconciliation, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.48,"slice":"core","lang":"en"} -{"prompt":"Consolidate compensation formatting across portal and reports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Investigate why terminated employees remain in manager search suggestions.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.61,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional employee transfer between legal entities with payroll and benefits checks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"Pin Temporal SDK to `1.34.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Build the mobile benefits-enrollment flow with plans, dependents, costs, comparison, confirmation, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Remplace `Employement` par `Employment` uniquement dans le nouveau titre.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"fr"} -{"prompt":"Inspect the payroll-export endpoint for formula injection, excessive scope, stale authorization, sensitive fields, and unbounded jobs.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Implement payroll-run history and write its API documentation. Include snapshots, approvals, corrections, payments, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Develop a roadmap for replacing manually configured org charts with effective-dated position management, including integrations and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.86,"slice":"core","lang":"en"} -{"prompt":"Add bounded event replay for workforce projections with durable checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Create the responsive payroll-preview dashboard with totals, variances, exceptions, filters, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"fix the org chart","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `PayEvt` with `PayrollEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why transferred employees still receive old-location shift alerts, implement the verified recipient fix, and update manager docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Why does the time service retain two previous overtime configurations? Explain current audit and recalculation behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.48,"slice":"boundary","lang":"en"} -{"prompt":"Track down occasional missing breaks after offline timesheet synchronization.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Write a troubleshooting guide for missing pay, covering time, compensation, deductions, approvals, payments, and corrections.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Privacy review packet:\n\n```text\nFeature: compensation benchmarking\nManagers compare team compensation with aggregated peers by role, level, and location\nMinimum peer cohort is five employees\nResults include median and percentile band, not individual values\nManagers may adjust filters repeatedly\nHistorical views use employment state at selected date\nExecutives can access organization-wide slices\nExports are disabled\nQuery logs retain manager, filters, result size, and timestamp\nSmall locations may be grouped into region\n```\n\nReview differencing attacks, repeated filters, historical inference, executive scope, location grouping, logging, and audit. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a loading state to the payslip rows","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Plan and implement compensation benchmarking. First define cohorts, differencing controls, hierarchy, history, privacy, audit, and rollout; then add aggregation and access APIs.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.93,"slice":"mixed","lang":"en"} -{"prompt":"Outline an architecture for cross-company worker transfers with identity, employment history, consent, documents, payroll, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"boundary","lang":"en"} -{"prompt":"Implement snapshot-consistent employee exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Escribe una guía para integrar nóminas, con empleados, tiempo, compensación, deducciones, pagos y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"es"} -{"prompt":"Move pay-calendar resolution out of the run scheduler without changing dates.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Investigate why the iOS app loses pending time entries after restoring a backup.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Add atomic leave-policy publication with simulation, approval, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Remove the obsolete `legacy_payroll` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"core","lang":"en"} -{"prompt":"Build the employee-history viewer with positions, managers, locations, compensation changes, and accessible chronology.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"`Payrol complete` を `Payroll complete` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"ja"} -{"prompt":"Review the payslip-download path for employee enumeration, former-manager access, stale signed URLs, cache leakage, and audit gaps.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"Implement leave-policy history and write its API guide. Include accrual, carryover, expiry, activation, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Plan a disaster-recovery strategy for workforce services, including records, time, payroll, documents, keys, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Add content-hash deduplication to employee-document uploads with employee-scoped ownership.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Create the desktop payroll-reconciliation workspace with expected payments, provider results, discrepancies, corrections, and export.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"continue the payroll cleanup","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.44,"slice":"vague-eval","lang":"en"} -{"prompt":"Rename `CompRev` to `CompensationRevision` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why revoked delegates still approve leave, implement the verified authorization-cache fix, and update employee documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.78,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed employee-profile cache for tenant isolation, effective dates, terminations, manager changes, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"Find why a payroll worker retries a permanently invalid bank account forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Draft a support guide for recovering an interrupted payroll run.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"en"} -{"prompt":"Position projection failure:\n\n```text\nemployee=e_991 transfer event offset=77120 effective=2026-08-01\nprojection writes new manager and location\ncheckpoint transaction fails\npermissions worker observes new manager and grants access\nprojection restarts and replays transfer\nunique effective-date revision rejects duplicate before idempotency handling\npartition stops; later termination event waits behind failure\n```\n\nDetermine how position state, checkpoint, and permission updates lack one durable boundary and why replay cannot converge.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Add pay period below the payslip title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} +{"prompt":"Leave projection failure:\n\n```text\nemployee=e_771 leave_request=l_91 approval event offset=88120\nprojection marks approved and deducts 24h pending balance\ncheckpoint transaction fails\ncalendar worker sees approved state and publishes absence\nprojection restarts and replays approval\nunique request transition rejects duplicate before balance idempotency\npartition stops; cancellation events wait behind failure\n```\n\nDetermine how request state, balance, checkpoint, and calendar publication lack one durable boundary and why replay cannot converge.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add effective date below the position title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Restructure the payroll calculator and document its country-adapter interface. Preserve results while separating inputs, rules, calculation, validation, and outputs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Architect a multi-region workforce platform with country ownership, employment history, time, payroll, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement signed payroll-run manifests with input versions and payment digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new payroll country, including inputs, rules, calendars, fixtures, reconciliation, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Consolidate compensation formatting across portal and reports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why terminated employees remain in manager search suggestions.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add transactional employee transfer between legal entities with payroll and benefits checks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Pin Temporal SDK to `1.34.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile benefits-enrollment flow with plans, dependents, costs, comparison, confirmation, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remplace `Employement` par `Employment` uniquement dans le nouveau titre.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"fr"} +{"prompt":"Inspect the payroll-export endpoint for formula injection, excessive scope, stale authorization, sensitive fields, and unbounded jobs.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Implement payroll-run history and write its API documentation. Include snapshots, approvals, corrections, payments, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Develop a roadmap for replacing manually configured org charts with effective-dated position management, including integrations and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add bounded event replay for workforce projections with durable checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the responsive payroll-preview dashboard with totals, variances, exceptions, filters, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"fix the org chart","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `PayEvt` with `PayrollEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose why transferred employees still receive old-location shift alerts, implement the verified recipient fix, and update manager docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the time service retain two previous overtime configurations? Explain current audit and recalculation behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down occasional missing breaks after offline timesheet synchronization.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Write a troubleshooting guide for missing pay, covering time, compensation, deductions, approvals, payments, and corrections.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Privacy review packet:\n\n```text\nFeature: compensation benchmarking\nManagers compare team compensation with aggregated peers by role, level, and location\nMinimum peer cohort is five employees\nResults include median and percentile band, not individual values\nManagers may adjust filters repeatedly\nHistorical views use employment state at selected date\nExecutives can access organization-wide slices\nExports are disabled\nQuery logs retain manager, filters, result size, and timestamp\nSmall locations may be grouped into region\n```\n\nReview differencing attacks, repeated filters, historical inference, executive scope, location grouping, logging, and audit. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add a loading state to the payslip rows","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Plan and implement compensation benchmarking. First define cohorts, differencing controls, hierarchy, history, privacy, audit, and rollout; then add aggregation and access APIs.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Outline an architecture for cross-company worker transfers with identity, employment history, consent, documents, payroll, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement snapshot-consistent employee exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Escribe una guía para integrar nóminas, con empleados, tiempo, compensación, deducciones, pagos y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"es"} +{"prompt":"Move pay-calendar resolution out of the run scheduler without changing dates.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why the iOS app loses pending time entries after restoring a backup.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add atomic leave-policy publication with simulation, approval, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Remove the obsolete `legacy_payroll` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Build the employee-history viewer with positions, managers, locations, compensation changes, and accessible chronology.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"`Payrol complete` を `Payroll complete` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"ja"} +{"prompt":"Review the payslip-download path for employee enumeration, former-manager access, stale signed URLs, cache leakage, and audit gaps.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement leave-policy history and write its API guide. Include accrual, carryover, expiry, activation, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan a disaster-recovery strategy for workforce services, including records, time, payroll, documents, keys, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add content-hash deduplication to employee-document uploads with employee-scoped ownership.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the desktop payroll-reconciliation workspace with expected payments, provider results, discrepancies, corrections, and export.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Rename `CompRev` to `CompensationRevision` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Investigate why revoked delegates still approve leave, implement the verified authorization-cache fix, and update employee documentation.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed employee-profile cache for tenant isolation, effective dates, terminations, manager changes, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why a payroll worker retries a permanently invalid bank account forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft a support guide for recovering an interrupted payroll run.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Position projection failure:\n\n```text\nemployee=e_991 transfer event offset=77120 effective=2026-08-01\nprojection writes new manager and location\ncheckpoint transaction fails\npermissions worker observes new manager and grants access\nprojection restarts and replays transfer\nunique effective-date revision rejects duplicate before idempotency handling\npartition stops; later termination event waits behind failure\n```\n\nDetermine how position state, checkpoint, and permission updates lack one durable boundary and why replay cannot converge.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add pay period below the payslip title","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} {"prompt":"Restructure the employment-history pipeline and document its source interface. Preserve records while separating ingest, normalize, validate, effective-date, and publish.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Architect a global payroll platform with country ownership, normalized inputs, local rules, payments, audit, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.98,"slice":"boundary","lang":"en"} +{"prompt":"Architect a global payroll platform with country ownership, normalized inputs, local rules, payments, audit, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1,"slice":"core","lang":"en"} {"prompt":"Implement signed payslip manifests with run, employee, input, and output digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new benefits plan, including eligibility, costs, dates, fixtures, approval, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Consolidate leave-duration formatting across portal and reports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Investigate why expired delegations remain in approver autocomplete.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional employee rehire with identity linking and prior-record protection.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Set the payroll batch size to 1000","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Build the mobile compensation-change screen with current value, proposed value, effective date, approvals, and accessible summary.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"把 `Employe profile` 改成 `Employee profile`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"zh"} -{"prompt":"Inspect the timesheet-import endpoint for formula injection, employee confusion, overlapping shifts, partial commits, and privilege escalation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"Implement employment-revision history and write its API documentation. Include effective dates, changes, approvals, activation, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Design an authoritative multiplayer-session architecture for matchmaking, lobbies, game servers, reconnects, spectators, results, anti-cheat signals, and replay. Cover regional routing, deterministic state, migrations, failure recovery, auditability, and rollout milestones. Deliver an RFC only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"core","lang":"en"} -{"prompt":"Before implementing cross-region parties, outline identity, membership, leader transfer, matchmaking, voice, latency, region choice, disconnects, and phased launch.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"boundary","lang":"en"} -{"prompt":"Add reconnect tokens to the match gateway","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Match incident logs:\n\n```text\nmatch=m_881 region=eu-west server=s_41 generation=18\nplayer=p_71 connected session=ss_991\nserver loses control-plane heartbeat at=20:01:12\nreplacement server=s_52 generation=19 starts from checkpoint tick=44120\nold server remains reachable to players and advances to tick=44188\ncontrol plane routes reconnecting player p_71 to generation=19\nparty members split across generations\nboth servers submit signed match result with same match_id different outcome_digest\nresult service accepts first arrival, anti-cheat flags second as tampering\n```\n\nDetermine why a control-plane lease loss does not fence the old game server and how split generations reach result submission.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"Build the console match-summary screen with scoreboard, rewards, progression, highlights, report action, and controller navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Plan and implement a live-operations configuration service. Begin with a design covering versioned events, segmentation, schedules, time zones, experiments, validation, emergency disable, client compatibility, audit, and rollout. Then add publication APIs, signed bundles, targeting, and conformance tests. Treat compatibility and safe activation as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.96,"slice":"mixed","lang":"en"} -{"prompt":"Set `MAX_PARTY_SIZE` to 6","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Extract duplicated player-ID normalization from matchmaking and social services while preserving validation.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"core","lang":"en"} -{"prompt":"Implement `/internal/matches/regions` with capacity, queue age, active servers, drain state, and allocation failures.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.52,"slice":"boundary","lang":"en"} -{"prompt":"make the lobby more epic","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.42,"slice":"vague-eval","lang":"en"} -{"prompt":"Find why players sometimes lose earned XP after reconnecting during the results sequence.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Explain how `MatchmakerScore` balances skill, latency, party size, wait time, and platform constraints. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Player release notes source:\n\n```text\nFeature: party join requests\nPlayers may request to join a friend's closed party\nParty leader can accept, deny, or ignore\nRequests expire after five minutes\nA player may have one active request per party\nAcceptance still checks party capacity, platform restrictions, and match state\nBlocked players cannot request or appear in the queue\nOld clients receive a standard invitation after acceptance\nRequests do not reserve a party slot\n```\n\nTurn this into release notes and a player help article with clear limits and compatibility behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"pasted-context","lang":"en"} -{"prompt":"Move the ready indicator beside the player name","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.13,"slice":"boundary","lang":"en"} -{"prompt":"Write an operator guide for replaying failed match-result events without granting rewards twice.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new benefits plan, including eligibility, costs, dates, fixtures, approval, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Consolidate leave-duration formatting across portal and reports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why expired delegations remain in approver autocomplete.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add transactional employee rehire with identity linking and prior-record protection.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Set the payroll batch size to 1000","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile compensation-change screen with current value, proposed value, effective date, approvals, and accessible summary.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"把 `Employe profile` 改成 `Employee profile`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"zh"} +{"prompt":"Inspect the timesheet-import endpoint for formula injection, employee confusion, overlapping shifts, partial commits, and privilege escalation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement employment-revision history and write its API documentation. Include effective dates, changes, approvals, activation, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Design an authoritative multiplayer-session architecture for matchmaking, lobbies, game servers, reconnects, spectators, results, anti-cheat signals, and replay. Cover regional routing, deterministic state, migrations, failure recovery, auditability, and rollout milestones. Deliver an RFC only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Before implementing cross-region parties, outline identity, membership, leader transfer, matchmaking, voice, latency, region choice, disconnects, and phased launch.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add reconnect tokens to the match gateway","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Match incident logs:\n\n```text\nmatch=m_881 region=eu-west server=s_41 generation=18\nplayer=p_71 connected session=ss_991\nserver loses control-plane heartbeat at=20:01:12\nreplacement server=s_52 generation=19 starts from checkpoint tick=44120\nold server remains reachable to players and advances to tick=44188\ncontrol plane routes reconnecting player p_71 to generation=19\nparty members split across generations\nboth servers submit signed match result with same match_id different outcome_digest\nresult service accepts first arrival, anti-cheat flags second as tampering\n```\n\nDetermine why a control-plane lease loss does not fence the old game server and how split generations reach result submission.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Build the console match-summary screen with scoreboard, rewards, progression, highlights, report action, and controller navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Plan and implement a live-operations configuration service. Begin with a design covering versioned events, segmentation, schedules, time zones, experiments, validation, emergency disable, client compatibility, audit, and rollout. Then add publication APIs, signed bundles, targeting, and conformance tests. Treat compatibility and safe activation as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Set `MAX_PARTY_SIZE` to 6","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Extract duplicated player-ID normalization from matchmaking and social services while preserving validation.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement `/internal/matches/regions` with capacity, queue age, active servers, drain state, and allocation failures.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"make the lobby more epic","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Find why players sometimes lose earned XP after reconnecting during the results sequence.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Explain how `MatchmakerScore` balances skill, latency, party size, wait time, and platform constraints. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Player release notes source:\n\n```text\nFeature: party join requests\nPlayers may request to join a friend's closed party\nParty leader can accept, deny, or ignore\nRequests expire after five minutes\nA player may have one active request per party\nAcceptance still checks party capacity, platform restrictions, and match state\nBlocked players cannot request or appear in the queue\nOld clients receive a standard invitation after acceptance\nRequests do not reserve a party slot\n```\n\nTurn this into release notes and a player help article with clear limits and compatibility behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} +{"prompt":"Move the ready indicator beside the player name","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Write an operator guide for replaying failed match-result events without granting rewards twice.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Implement player-sanction endpoints with duration, scope, evidence, and authorization, then document lifecycle, examples, and errors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Map out a migration from global matchmaking queues to mode-and-region partitions, including party routing, fairness, metrics, compatibility, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Rename `plyrNo` to `playerNumber` in `LobbyMapper.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"en"} -{"prompt":"Teach the result processor to deduplicate signed server reports by match generation and outcome digest.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Polish the season progress card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.28,"slice":"core","lang":"en"} -{"prompt":"Bump `nakama-js` to `2.8.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Rename `MasterServer` to `PrimaryGameServer` across control plane, protocol, metrics, and tests while preserving wire values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.68,"slice":"boundary","lang":"en"} -{"prompt":"Split `MatchService` into allocation, session, state, results, rewards, and cleanup components without changing behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.84,"slice":"core","lang":"en"} -{"prompt":"Implementation ticket:\n\n```text\nGAME-992 — tournament brackets\nFormats: single elimination and double elimination\nEntrants may be solo players or fixed teams\nMatches carry best-of count, scheduled window, server region, and result state\nAdvancement occurs only after verified final result\nDisputed results pause dependent matches\nByes are assigned deterministically from seed order\nAdministrator corrections create new bracket revision, never rewrite history\nClients receive bracket patches with generation numbers\nExpose scheduled, completed, disputed, corrected, and blocked-match metrics\n```\n\nImplement bracket generation, scheduling, result advancement, disputes, revisions, patches, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.89,"slice":"pasted-context","lang":"en"} -{"prompt":"Investigate why the Android game shows the previous party's voice indicators after leaving and joining another party.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Create the tournament-bracket UI and add a concise guide for seeds, byes, series state, disputes, and advancement.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Why does the replay service retain invalidated match recordings? Explain current anti-cheat and audit behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.48,"slice":"core","lang":"en"} -{"prompt":"Rewrite the local setup for running Agones, Redis, NATS, and simulated game clients.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.35,"slice":"core","lang":"en"} -{"prompt":"This matchmaking test fails with mixed-input parties:\n\n```text\nparty A skill=[1400,1410] platforms=[pc,pc]\nparty B skill=[1390,1420] platforms=[console,console]\ncrossplay setting A=enabled B=friends_only\nfriend edge exists A1<->B1\nexpected compatible=true actual=false\nmatcher requires every member pair to be friends for friends_only\nproduct rule says one social edge between party leaders is sufficient\nclient preview checks leader edge, server checks Cartesian product\n```\n\nDetermine which compatibility semantics are implemented inconsistently and why preview and server disagree.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.69,"slice":"boundary","lang":"en"} -{"prompt":"finish the tournament API","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} -{"prompt":"Propose an architecture for deterministic server-side replays, including input capture, state hashes, versioning, compression, validation, privacy, and production debugging.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Add Source RCON packet parsing to `serverctl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Review excerpt:\n\n```diff\n async function grantRewards(matchId) {\n- const result = await results.requireVerified(matchId)\n- await rewards.apply(result.players, result.digest)\n+ results.verify(matchId).catch(logger.warn)\n+ await rewards.apply(await results.latestPlayers(matchId), 'pending')\n }\n```\n\nThe author says result verification delays progression. Review tampered outcomes, generation binding, duplicates, reversals, audit, and asynchronous failure. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Schreibe eine kurze Referenz für die bestehenden Match-Status und ihre Auswirkungen auf Verbindung, Ergebnis und Belohnung. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"de"} -{"prompt":"Build the desktop live-ops calendar with events, regions, segments, conflicts, preview, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Review how ranked points are calculated and corrected, then turn the findings into a player-support guide with examples.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.63,"slice":"mixed","lang":"en"} -{"prompt":"Set the reconnect window to 90s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Benenne `MatchCtx` repositoryweit in `MatchContext` um; Protokollfelder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"de"} -{"prompt":"Consolidate platform-name normalization across parties and matchmaking without changing compatibility.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Diagnose the duplicate reward toast","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Explain how the server allocator handles draining nodes with active and pending matches.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Create API documentation for the existing party-invite endpoint, including expiry, capacity, blocks, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"en"} -{"prompt":"Plan a migration from mutable player inventories to an event-sourced economy ledger, including corrections, grants, spends, migration, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"core","lang":"en"} -{"prompt":"Console UI ticket:\n\n```text\nScreen: multiplayer lobby\nAreas: party members, selected mode, region, readiness, matchmaking status\nLeader can change mode and region or remove members\nMembers control ready state and voice mute\nCrossplay and input restrictions appear before queueing\nMatchmaking progress has searching, expanding, found, joining, failed, cancelled\nController focus must remain stable when members join or leave\nAccessibility: readiness and voice status are spoken, not color-only\nSplit-screen profiles show separate focus indicators\n```\n\nImplement the lobby and UI tests using existing party models.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Implement `POST /v1/matches/{id}/forfeit` with participant checks, generation binding, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"boundary","lang":"en"} -{"prompt":"Remove the extra star from the rank label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"core","lang":"en"} -{"prompt":"Fix the clipped party badge and extract its duplicated padding into the shared lobby token.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.35,"slice":"mixed","lang":"en"} -{"prompt":"Replace scattered match booleans with one explicit session lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Cambia `srvGen` por `serverGeneration` solo en `MatchState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"es"} -{"prompt":"Investigate why the player app briefly displays another account's inventory after profile switching.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Summarize the current match-result verification workflow for anti-cheat and operations reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Develop a capacity roadmap for running one million concurrent matches. Include allocation, networking, state, telemetry, results, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"core","lang":"en"} -{"prompt":"Implement idempotent achievement-progress ingestion with event ordering and correction support.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Create the SwiftUI party finder with filters, player cards, join requests, blocks, pagination, and VoiceOver support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Fix `matchmakng` in `events.proto`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} -{"prompt":"Merge duplicate match-result types used by rewards and anti-cheat while preserving encoded values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Economy projection incident:\n\n```text\nplayer=p_881 reward event match=m_77 grant=500 coins offset=99120\nbalance projection increments coins to=1400\ncheckpoint transaction fails\ninventory service observes balance and unlocks item purchase\nprojection restarts and replays grant\nunique event constraint rejects duplicate before checkpoint advances\npartition stops; later spend event queues behind failure\nclient already purchased item using first grant\n```\n\nDetermine how balance, checkpoint, and inventory side effects lack one durable boundary and why replay does not converge.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Rename `playr_id` to `player_id` in the unreleased migration.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"en"} -{"prompt":"Assess whether private match replays can leak through shared CDN keys, spectator links, or result metadata. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Restructure the game SDK into parties, matchmaking, sessions, results, and progression, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.77,"slice":"mixed","lang":"en"} -{"prompt":"Plan the retirement of legacy peer-hosted matches, covering player populations, host migration, parity, communication, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.87,"slice":"core","lang":"en"} -{"prompt":"Add immutable provenance chains to competitive match results.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Build the tablet spectator dashboard with player list, scores, timeline, camera controls, delay, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"do the season page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.39,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `PartyRef` with `PartyReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why ranked rewards omit corrected match outcomes, implement the verified projection fix, and add a player-support note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.79,"slice":"mixed","lang":"en"} -{"prompt":"Why does the live-ops service retain two previous event bundles? Explain current rollback and client compatibility behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.47,"slice":"boundary","lang":"en"} -{"prompt":"Track down the memory leak in replay decoder workers after long matches.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Write release notes for input-based matchmaking, including eligibility, party restrictions, fallback, and old-client behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.36,"slice":"core","lang":"en"} -{"prompt":"Season design notes:\n\n```text\nSeason has start, end, progression track, challenges, rewards, and ranked reset\nPlayers may complete challenges offline and upload later\nRewards pin content version at claim time\nLate challenge events accepted for 48 hours after season end\nRanked reset occurs at exact server instant by region-independent clock\nOld clients understand linear tracks only\nEmergency extension must not duplicate already claimed rewards\nAll configuration and claims require audit replay\n```\n\nProduce an implementation-free design and rollout plan covering timing, offline events, versions, late data, extensions, compatibility, and audit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"pasted-context","lang":"en"} -{"prompt":"Give the scoreboard clearer team grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.31,"slice":"core","lang":"en"} -{"prompt":"Turn the current disconnect-penalty behavior into player documentation, then review whether grace periods and exemptions match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.67,"slice":"mixed","lang":"en"} -{"prompt":"Outline a phased architecture for moving replay storage from local disks to object storage, without implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.83,"slice":"boundary","lang":"en"} +{"prompt":"Rename `plyrNo` to `playerNumber` in `LobbyMapper.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Teach the result processor to deduplicate signed server reports by match generation and outcome digest.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Polish the season progress card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump `nakama-js` to `2.8.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename `MasterServer` to `PrimaryGameServer` across control plane, protocol, metrics, and tests while preserving wire values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Split `MatchService` into allocation, session, state, results, rewards, and cleanup components without changing behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implementation ticket:\n\n```text\nGAME-992 — tournament brackets\nFormats: single elimination and double elimination\nEntrants may be solo players or fixed teams\nMatches carry best-of count, scheduled window, server region, and result state\nAdvancement occurs only after verified final result\nDisputed results pause dependent matches\nByes are assigned deterministically from seed order\nAdministrator corrections create new bracket revision, never rewrite history\nClients receive bracket patches with generation numbers\nExpose scheduled, completed, disputed, corrected, and blocked-match metrics\n```\n\nImplement bracket generation, scheduling, result advancement, disputes, revisions, patches, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Investigate why the Android game shows the previous party's voice indicators after leaving and joining another party.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the tournament-bracket UI and add a concise guide for seeds, byes, series state, disputes, and advancement.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the replay service retain invalidated match recordings? Explain current anti-cheat and audit behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Rewrite the local setup for running Agones, Redis, NATS, and simulated game clients.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"This matchmaking test fails with mixed-input parties:\n\n```text\nparty A skill=[1400,1410] platforms=[pc,pc]\nparty B skill=[1390,1420] platforms=[console,console]\ncrossplay setting A=enabled B=friends_only\nfriend edge exists A1<->B1\nexpected compatible=true actual=false\nmatcher requires every member pair to be friends for friends_only\nproduct rule says one social edge between party leaders is sufficient\nclient preview checks leader edge, server checks Cartesian product\n```\n\nDetermine which compatibility semantics are implemented inconsistently and why preview and server disagree.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"finish the tournament API","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Propose an architecture for deterministic server-side replays, including input capture, state hashes, versioning, compression, validation, privacy, and production debugging.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add Source RCON packet parsing to `serverctl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Review excerpt:\n\n```diff\n async function grantRewards(matchId) {\n- const result = await results.requireVerified(matchId)\n- await rewards.apply(result.players, result.digest)\n+ results.verify(matchId).catch(logger.warn)\n+ await rewards.apply(await results.latestPlayers(matchId), 'pending')\n }\n```\n\nThe author says result verification delays progression. Review tampered outcomes, generation binding, duplicates, reversals, audit, and asynchronous failure. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Schreibe eine kurze Referenz für die bestehenden Match-Status und ihre Auswirkungen auf Verbindung, Ergebnis und Belohnung. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"de"} +{"prompt":"Build the desktop live-ops calendar with events, regions, segments, conflicts, preview, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Review how ranked points are calculated and corrected, then turn the findings into a player-support guide with examples.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Set the reconnect window to 90s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Benenne `MatchCtx` repositoryweit in `MatchContext` um; Protokollfelder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"de"} +{"prompt":"Consolidate platform-name normalization across parties and matchmaking without changing compatibility.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose the duplicate reward toast","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Explain how the server allocator handles draining nodes with active and pending matches.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Create API documentation for the existing party-invite endpoint, including expiry, capacity, blocks, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Plan a migration from mutable player inventories to an event-sourced economy ledger, including corrections, grants, spends, migration, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Console UI ticket:\n\n```text\nScreen: multiplayer lobby\nAreas: party members, selected mode, region, readiness, matchmaking status\nLeader can change mode and region or remove members\nMembers control ready state and voice mute\nCrossplay and input restrictions appear before queueing\nMatchmaking progress has searching, expanding, found, joining, failed, cancelled\nController focus must remain stable when members join or leave\nAccessibility: readiness and voice status are spoken, not color-only\nSplit-screen profiles show separate focus indicators\n```\n\nImplement the lobby and UI tests using existing party models.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Implement `POST /v1/matches/{id}/forfeit` with participant checks, generation binding, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Remove the extra star from the rank label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fix the clipped party badge and extract its duplicated padding into the shared lobby token.","purpose":"frontendImpl","secondary":"refactor","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Replace scattered match booleans with one explicit session lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Cambia `srvGen` por `serverGeneration` solo en `MatchState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"es"} +{"prompt":"Investigate why the player app briefly displays another account's inventory after profile switching.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Summarize the current match-result verification workflow for anti-cheat and operations reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Develop a capacity roadmap for running one million concurrent matches. Include allocation, networking, state, telemetry, results, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1,"slice":"core","lang":"en"} +{"prompt":"Implement idempotent achievement-progress ingestion with event ordering and correction support.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create the SwiftUI party finder with filters, player cards, join requests, blocks, pagination, and VoiceOver support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Fix `matchmakng` in `events.proto`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Merge duplicate match-result types used by rewards and anti-cheat while preserving encoded values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Economy projection incident:\n\n```text\nplayer=p_881 reward event match=m_77 grant=500 coins offset=99120\nbalance projection increments coins to=1400\ncheckpoint transaction fails\ninventory service observes balance and unlocks item purchase\nprojection restarts and replays grant\nunique event constraint rejects duplicate before checkpoint advances\npartition stops; later spend event queues behind failure\nclient already purchased item using first grant\n```\n\nDetermine how balance, checkpoint, and inventory side effects lack one durable boundary and why replay does not converge.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Rename `playr_id` to `player_id` in the unreleased migration.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Assess whether private match replays can leak through shared CDN keys, spectator links, or result metadata. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Restructure the game SDK into parties, matchmaking, sessions, results, and progression, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan the retirement of legacy peer-hosted matches, covering player populations, host migration, parity, communication, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add immutable provenance chains to competitive match results.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Build the tablet spectator dashboard with player list, scores, timeline, camera controls, delay, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"do the season page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `PartyRef` with `PartyReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose why ranked rewards omit corrected match outcomes, implement the verified projection fix, and add a player-support note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Why does the live-ops service retain two previous event bundles? Explain current rollback and client compatibility behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Track down the memory leak in replay decoder workers after long matches.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Write release notes for input-based matchmaking, including eligibility, party restrictions, fallback, and old-client behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Season design notes:\n\n```text\nSeason has start, end, progression track, challenges, rewards, and ranked reset\nPlayers may complete challenges offline and upload later\nRewards pin content version at claim time\nLate challenge events accepted for 48 hours after season end\nRanked reset occurs at exact server instant by region-independent clock\nOld clients understand linear tracks only\nEmergency extension must not duplicate already claimed rewards\nAll configuration and claims require audit replay\n```\n\nProduce an implementation-free design and rollout plan covering timing, offline events, versions, late data, extensions, compatibility, and audit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Give the scoreboard clearer team grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Turn the current disconnect-penalty behavior into player documentation, then review whether grace periods and exemptions match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Outline a phased architecture for moving replay storage from local disks to object storage, without implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Implement version-aware player-sanction history with scope, expiry, and appeal links.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Create an operator guide for diagnosing matches stuck in allocating state.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} -{"prompt":"Move region selection out of `MatchController` while preserving chosen regions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.58,"slice":"core","lang":"en"} -{"prompt":"Investigate why revoked tournament admins retain access through one regional console cache.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"Add generation-fenced live-ops publication with validation, preview, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Set the spectator delay to 120s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Create the responsive match-history view with modes, results, stats, replays, filters, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Corrige apenas `tourament` para `tournament` no novo título.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"pt"} -{"prompt":"Review the custom-map upload endpoint for malicious archives, unsafe scripts, oversized geometry, tenant confusion, and signature bypass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"core","lang":"en"} -{"prompt":"Implement match-generation history and write its API guide. Include servers, checkpoints, failover, results, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Design a migration from static skill ratings to mode-specific uncertainty-aware ratings, including backfill, parity, explanation, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"core","lang":"en"} -{"prompt":"Add resumable replay uploads with chunk hashes and generation binding.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Build the desktop economy-ledger explorer with grants, spends, reversals, balances, filters, and export.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"continue the reward bug","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"Extract mode-name normalization into one shared module while preserving queue identifiers.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why scheduled events use an outdated player segment, implement the verified snapshot fix, and update live-ops documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.77,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed player-profile cache for account switching, sanctions, privacy settings, region moves, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Find why one result worker retries an invalid server signature forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Draft a migration guide for community-server operators moving to the allocation API.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} -{"prompt":"Matchmaking quality incident:\n\n```text\nmode=ranked_duo region=ap-southeast\nmedian wait improved 92s -> 44s\nskill delta p95 worsened 81 -> 244\nconfiguration expansion step changed from +25 skill/20s to +75 skill/10s\nquality gate checks global mean skill delta=61, below threshold=80\nregion has low population and tail is hidden by global aggregation\nchurn after first match rises 6% in region\nrollback restores p95 and churn\n```\n\nDetermine why the quality gate passed despite severe regional tail degradation and which aggregation assumptions are wrong.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.76,"slice":"pasted-context","lang":"en"} -{"prompt":"Add server region below the match title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Restructure the matchmaking pipeline and document its constraint interface. Preserve pairings while separating candidates, compatibility, scoring, expansion, and allocation.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.83,"slice":"mixed","lang":"en"} -{"prompt":"Architect a globally distributed game-session platform with region ownership, migration, state, results, and audit milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.98,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed match receipts with server generation and result digest.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new game mode, including rules, matchmaking, servers, results, telemetry, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"Consolidate rank formatting across game clients and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Investigate why expired sanctions remain in party search filters.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional player transfer between regional shards with party and inventory checks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"Pin Agones to `1.52.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Build the mobile challenge tracker with progress, expiry, rewards, categories, offline state, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Remplace `Matchmakng` par `Matchmaking` uniquement dans le nouveau titre.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"fr"} -{"prompt":"Inspect the replay-download endpoint for private-match leakage, stale spectator access, guessed IDs, cache confusion, and unbounded ranges.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} -{"prompt":"Implement season-configuration history and write its API documentation. Include versions, schedules, rewards, activation, rollback, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} +{"prompt":"Create an operator guide for diagnosing matches stuck in allocating state.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Move region selection out of `MatchController` while preserving chosen regions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why revoked tournament admins retain access through one regional console cache.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add generation-fenced live-ops publication with validation, preview, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Set the spectator delay to 120s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Create the responsive match-history view with modes, results, stats, replays, filters, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Corrige apenas `tourament` para `tournament` no novo título.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"pt"} +{"prompt":"Review the custom-map upload endpoint for malicious archives, unsafe scripts, oversized geometry, tenant confusion, and signature bypass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement match-generation history and write its API guide. Include servers, checkpoints, failover, results, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Design a migration from static skill ratings to mode-specific uncertainty-aware ratings, including backfill, parity, explanation, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add resumable replay uploads with chunk hashes and generation binding.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Build the desktop economy-ledger explorer with grants, spends, reversals, balances, filters, and export.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Extract mode-name normalization into one shared module while preserving queue identifiers.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why scheduled events use an outdated player segment, implement the verified snapshot fix, and update live-ops documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed player-profile cache for account switching, sanctions, privacy settings, region moves, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why one result worker retries an invalid server signature forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft a migration guide for community-server operators moving to the allocation API.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Matchmaking quality incident:\n\n```text\nmode=ranked_duo region=ap-southeast\nmedian wait improved 92s -> 44s\nskill delta p95 worsened 81 -> 244\nconfiguration expansion step changed from +25 skill/20s to +75 skill/10s\nquality gate checks global mean skill delta=61, below threshold=80\nregion has low population and tail is hidden by global aggregation\nchurn after first match rises 6% in region\nrollback restores p95 and churn\n```\n\nDetermine why the quality gate passed despite severe regional tail degradation and which aggregation assumptions are wrong.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Add server region below the match title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Restructure the matchmaking pipeline and document its constraint interface. Preserve pairings while separating candidates, compatibility, scoring, expansion, and allocation.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Architect a globally distributed game-session platform with region ownership, migration, state, results, and audit milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement signed match receipts with server generation and result digest.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new game mode, including rules, matchmaking, servers, results, telemetry, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Consolidate rank formatting across game clients and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why expired sanctions remain in party search filters.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add transactional player transfer between regional shards with party and inventory checks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Pin Agones to `1.52.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile challenge tracker with progress, expiry, rewards, categories, offline state, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remplace `Matchmakng` par `Matchmaking` uniquement dans le nouveau titre.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"fr"} +{"prompt":"Inspect the replay-download endpoint for private-match leakage, stale spectator access, guessed IDs, cache confusion, and unbounded ranges.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement season-configuration history and write its API documentation. Include versions, schedules, rewards, activation, rollback, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Develop a roadmap for replacing batch anti-cheat review with near-real-time evidence pipelines, including false positives, appeals, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Add bounded event replay for player-progression projections with checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Create the responsive server-browser with regions, modes, latency, filters, favorites, and accessible selection.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"fix party invites","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `MatchEvt` with `MatchEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why forfeited matches still grant completion rewards, implement the verified result-state fix, and update player documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.76,"slice":"mixed","lang":"en"} -{"prompt":"Why does the party service retain two previous membership snapshots? Explain current reconnect behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.47,"slice":"boundary","lang":"en"} -{"prompt":"Track down occasional missing voice participants after region migration.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Write a troubleshooting guide for failed matchmaking, covering party restrictions, regions, sanctions, capacity, and connectivity.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Security review packet:\n\n```text\nFeature: temporary tournament administrator\nTournament owner invites administrator for one event and expiry up to seven days\nAdministrator may schedule matches, correct results, and resolve disputes\nAdministrator cannot change prize configuration or ownership\nInvitation uses account ID and requires MFA confirmation\nCorrections after prize payout require finance approval\nAccess revocation should apply within one minute\nOffline desktop client may retain cached bracket data\nAll actions include actor, event, reason, before/after, and client device\n```\n\nReview scope, expiry, revocation, cached data, result correction, payout boundaries, MFA, and audit. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.77,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a loading state to the lobby members","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Plan and implement temporary tournament administrators. First define scope, expiry, revocation, corrections, payouts, MFA, audit, and rollout; then add enforcement and management APIs.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.92,"slice":"mixed","lang":"en"} -{"prompt":"Outline an architecture for cross-game identity and progression with consent, namespaces, entitlements, privacy, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"boundary","lang":"en"} -{"prompt":"Implement snapshot-consistent player-history exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Escribe una guía para integrar servidores de juego, con asignación, sesiones, resultados, firmas y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"es"} -{"prompt":"Move disconnect-penalty resolution out of the result worker without changing sanctions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.59,"slice":"core","lang":"en"} -{"prompt":"Investigate why the iOS companion app loses pending party requests after restore.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.61,"slice":"boundary","lang":"en"} -{"prompt":"Add atomic matchmaking-policy publication with simulation, approval, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Remove the obsolete `legacy_rating` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"core","lang":"en"} -{"prompt":"Build the match-replay viewer with timeline, player perspectives, events, bookmarks, speed, and accessible controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"`Matchmakng failed` を `Matchmaking failed` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"ja"} -{"prompt":"Review the custom-game configuration endpoint for unsafe scripts, oversized state, privilege escalation, tenant confusion, and denial of service.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Implement player-sanction history and write its API guide. Include scope, evidence, appeals, expiry, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Plan a disaster-recovery strategy for multiplayer services, including parties, matches, results, progression, configs, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Add content-hash deduplication to uploaded match replays with participant-scoped access.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Create the desktop ranked-season dashboard with distributions, queues, quality, rewards, anomalies, and accessible charts.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"continue the match cleanup","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.43,"slice":"vague-eval","lang":"en"} -{"prompt":"Rename `SeasonRev` to `SeasonRevision` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why removed party members still receive match-found alerts, implement the verified recipient fix, and update support docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.77,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed session cache for generation fencing, sanctions, party changes, regional failover, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"Find why a game-server allocator retries an unsupported build forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Draft a support guide for recovering a match with a missing result.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Tournament projection failure:\n\n```text\ntournament=t_881 match=m_41 result event offset=99120\nbracket projection advances winner to next round\ncheckpoint transaction fails\nscheduler sees next match ready and allocates server\nprojection restarts and replays result\nunique advancement constraint rejects duplicate before checkpoint advances\npartition stops; correction event waits behind failure\n```\n\nDetermine how bracket state, checkpoint, and scheduling lack one durable boundary and why replay cannot converge.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.82,"slice":"pasted-context","lang":"en"} -{"prompt":"Add build version below the match title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Restructure the match-result pipeline and document its verifier interface. Preserve outcomes while separating reports, verification, arbitration, projection, and rewards.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.84,"slice":"mixed","lang":"en"} -{"prompt":"Architect a global live-operations platform with game ownership, versioned configs, targeting, scheduling, compatibility, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed progression snapshots with season, config, and balance digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new matchmaking constraint, including compatibility, scoring, fixtures, simulation, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"Consolidate match-duration formatting across clients and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Investigate why expired tournament roles remain in admin autocomplete.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} +{"prompt":"Add bounded event replay for player-progression projections with checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the responsive server-browser with regions, modes, latency, filters, favorites, and accessible selection.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"fix party invites","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `MatchEvt` with `MatchEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose why forfeited matches still grant completion rewards, implement the verified result-state fix, and update player documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the party service retain two previous membership snapshots? Explain current reconnect behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down occasional missing voice participants after region migration.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write a troubleshooting guide for failed matchmaking, covering party restrictions, regions, sanctions, capacity, and connectivity.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Security review packet:\n\n```text\nFeature: temporary tournament administrator\nTournament owner invites administrator for one event and expiry up to seven days\nAdministrator may schedule matches, correct results, and resolve disputes\nAdministrator cannot change prize configuration or ownership\nInvitation uses account ID and requires MFA confirmation\nCorrections after prize payout require finance approval\nAccess revocation should apply within one minute\nOffline desktop client may retain cached bracket data\nAll actions include actor, event, reason, before/after, and client device\n```\n\nReview scope, expiry, revocation, cached data, result correction, payout boundaries, MFA, and audit. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add a loading state to the lobby members","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Plan and implement temporary tournament administrators. First define scope, expiry, revocation, corrections, payouts, MFA, audit, and rollout; then add enforcement and management APIs.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Outline an architecture for cross-game identity and progression with consent, namespaces, entitlements, privacy, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement snapshot-consistent player-history exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Escribe una guía para integrar servidores de juego, con asignación, sesiones, resultados, firmas y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"es"} +{"prompt":"Move disconnect-penalty resolution out of the result worker without changing sanctions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Investigate why the iOS companion app loses pending party requests after restore.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add atomic matchmaking-policy publication with simulation, approval, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Remove the obsolete `legacy_rating` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Build the match-replay viewer with timeline, player perspectives, events, bookmarks, speed, and accessible controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"`Matchmakng failed` を `Matchmaking failed` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"ja"} +{"prompt":"Review the custom-game configuration endpoint for unsafe scripts, oversized state, privilege escalation, tenant confusion, and denial of service.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement player-sanction history and write its API guide. Include scope, evidence, appeals, expiry, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Plan a disaster-recovery strategy for multiplayer services, including parties, matches, results, progression, configs, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add content-hash deduplication to uploaded match replays with participant-scoped access.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the desktop ranked-season dashboard with distributions, queues, quality, rewards, anomalies, and accessible charts.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Rename `SeasonRev` to `SeasonRevision` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why removed party members still receive match-found alerts, implement the verified recipient fix, and update support docs.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed session cache for generation fencing, sanctions, party changes, regional failover, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why a game-server allocator retries an unsupported build forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft a support guide for recovering a match with a missing result.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Tournament projection failure:\n\n```text\ntournament=t_881 match=m_41 result event offset=99120\nbracket projection advances winner to next round\ncheckpoint transaction fails\nscheduler sees next match ready and allocates server\nprojection restarts and replays result\nunique advancement constraint rejects duplicate before checkpoint advances\npartition stops; correction event waits behind failure\n```\n\nDetermine how bracket state, checkpoint, and scheduling lack one durable boundary and why replay cannot converge.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add build version below the match title","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Restructure the match-result pipeline and document its verifier interface. Preserve outcomes while separating reports, verification, arbitration, projection, and rewards.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Architect a global live-operations platform with game ownership, versioned configs, targeting, scheduling, compatibility, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Implement signed progression snapshots with season, config, and balance digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new matchmaking constraint, including compatibility, scoring, fixtures, simulation, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Consolidate match-duration formatting across clients and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why expired tournament roles remain in admin autocomplete.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Add transactional team-roster changes with tournament eligibility and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Set the replay retention to 180 days","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Build the mobile tournament screen with bracket, schedule, standings, notifications, streams, and accessible navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"把 `Rewad claimed` 改成 `Reward claimed`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"zh"} -{"prompt":"Inspect the match-result submission endpoint for forged servers, replay, generation confusion, oversized evidence, and tenant bypass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.78,"slice":"core","lang":"en"} -{"prompt":"Implement tournament-revision history and write its API documentation. Include brackets, results, corrections, disputes, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Design a policy-and-claims architecture for quotes, coverage, endorsements, billing, first notice of loss, evidence, reserves, payments, recoveries, and audit history. Cover effective dating, immutable corrections, partner integrations, regional rules, migration from product-specific systems, and rollout milestones. Deliver an RFC only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"core","lang":"en"} -{"prompt":"Before implementing automated claim triage, outline input evidence, rules, models, confidence, human review, explanations, fraud signals, escalation, fairness evaluation, and phased launch.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"boundary","lang":"en"} -{"prompt":"Add reserve history to `/v2/claims`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Claims incident logs:\n\n```text\nclaim=cl_881 policy=pol_91 loss_date=2026-07-14\ncoverage snapshot version=18 active=true deductible=500\nendorsement version=19 effective=2026-07-01 removes coverage type=water\nendorsement imported late at=2026-07-30\ncoverage projection recalculates claim as not_covered\npayment p_71 already issued=4200 on version=18\nrecovery worker opens overpayment case automatically\nendorsement source says signed_at=2026-07-20 and may not apply retroactively\n```\n\nDetermine why effective date alone overrides the claim snapshot and whether endorsement issuance, knowledge time, or policy rules should control retroactivity.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Build the SwiftUI claim-detail screen with status timeline, coverage, deductible, documents, payments, contacts, and VoiceOver support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Plan and implement a coverage-decision service. Begin with a design covering policy versions, loss facts, exclusions, endorsements, jurisdiction, explanations, manual overrides, appeals, audit replay, and failure behavior. Then add the evaluator, decision APIs, rule publication, and conformance tests. Treat temporal and legal semantics as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.98,"slice":"mixed","lang":"en"} -{"prompt":"Set `MAX_CLAIM_ATTACHMENTS` to 100","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Extract duplicated policy-number normalization from quoting and claims while preserving validation.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"core","lang":"en"} -{"prompt":"Implement `/internal/claims/queues` with pending age, owner, priority, reserve exposure, and SLA breaches.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.53,"slice":"boundary","lang":"en"} -{"prompt":"make the quote page reassuring","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.42,"slice":"vague-eval","lang":"en"} -{"prompt":"Find why uploaded accident photos occasionally appear under the previous claim after app relaunch.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Explain how `ReserveCalculator` combines expected loss, deductible, limits, prior payments, and recoveries. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Policyholder launch notes:\n\n```text\nFeature: claim document requests\nAdjuster requests one or more document categories with due date and explanation\nPolicyholder uploads files or marks an item unavailable with reason\nEach upload receives malware scan and receipt\nAdjuster may accept, reject, or request replacement\nPrior files remain in claim history after replacement\nNotifications show claim number but omit requested category on locked screens\nMissing the due date does not automatically close the claim\n```\n\nTurn this into release notes and a policyholder help article with clear deadline and replacement behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"pasted-context","lang":"en"} -{"prompt":"Move the coverage badge closer to the policy title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.13,"slice":"boundary","lang":"en"} -{"prompt":"Write an operator guide for replaying failed claim-payment events without issuing duplicate disbursements.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.44,"slice":"core","lang":"en"} -{"prompt":"Implement claim-document endpoints with category filters, signed downloads, and authorization, then document lifecycle, examples, and errors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.68,"slice":"mixed","lang":"en"} -{"prompt":"Map out a migration from mutable policy rows to effective-dated policy revisions, including endorsements, quotes, renewals, claims, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.93,"slice":"core","lang":"en"} -{"prompt":"Rename `clmNo` to `claimNumber` in `ClaimMapper.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"boundary","lang":"en"} -{"prompt":"Teach the payment worker to reconcile uncertain provider submissions before retrying.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Polish the deductible summary card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.28,"slice":"core","lang":"en"} -{"prompt":"Bump `drools` to `10.1.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Rename `MasterPolicy` to `PrimaryPolicy` across services, events, reports, and tests while preserving public fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.64,"slice":"boundary","lang":"en"} -{"prompt":"Split `ClaimsService` into intake, coverage, investigation, reserves, payments, and closure components without changing outcomes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} -{"prompt":"Implementation ticket:\n\n```text\nINS-774 — claim reserve adjustments\nReserve categories: indemnity, expense, legal, recovery\nAdjuster proposes new amount with reason and supporting evidence\nApproval threshold depends on delta, claim type, jurisdiction, and authority level\nApproved adjustment creates immutable revision and accounting event\nConcurrent proposals require current reserve version\nClosing a claim sets remaining reserves to zero through explicit adjustment\nReopening restores no prior reserve automatically\nExpose proposed, approved, rejected, stale, and threshold-escalated metrics\n```\n\nImplement reserve revisions, validation, approval routing, concurrency, accounting events, closure behavior, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.86,"slice":"pasted-context","lang":"en"} -{"prompt":"Investigate why the Android adjuster app loses recorded statements when switching networks during upload.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Create the reserve-adjustment review UI and add a concise guide for categories, current value, delta, authority, evidence, and approval.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.67,"slice":"mixed","lang":"en"} -{"prompt":"Why does the claims warehouse retain withdrawn fraud indicators? Explain current audit and model-evaluation behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.48,"slice":"core","lang":"en"} -{"prompt":"Rewrite the local setup for running WireMock carriers, Postgres, Kafka, and synthetic claims.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.34,"slice":"core","lang":"en"} -{"prompt":"This deductible test fails after a policy move:\n\n```text\npolicy p_17 jurisdiction changes CA -> NV effective=2026-08-01\nclaim loss spans storm damage 2026-07-31T23:00..2026-08-01T02:00 local\nCA deductible=1000 NV deductible=500\nexpected based on loss inception=1000\nactual based on claim report date=500\ncoverage service resolves jurisdiction at report timestamp\npolicy document says governing location at time of loss\n```\n\nDetermine which timestamp and location should pin the rule version and why the current implementation differs from the fixture.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.73,"slice":"boundary","lang":"en"} -{"prompt":"finish the claims API","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.49,"slice":"vague-eval","lang":"en"} -{"prompt":"Propose an architecture for claim-event analytics with privacy, late corrections, financial snapshots, model features, retention, and reproducibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.91,"slice":"core","lang":"en"} -{"prompt":"Add ACORD XML parsing to `policyctl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Review excerpt:\n\n```diff\n async function issuePayment(claimId, amount) {\n- const decision = await coverage.requirePayable(claimId, amount)\n- const receipt = await provider.send(decision.payment)\n- await payments.record(receipt, decision.digest)\n+ coverage.requirePayable(claimId, amount).catch(logger.warn)\n+ provider.send({ claimId, amount })\n+ await payments.recordPending(claimId, amount)\n }\n```\n\nThe author says coverage checks and provider calls slow adjusters. Review authorization, coverage binding, uncertain submission, duplicate payment, audit, and response semantics. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Schreibe eine kurze Referenz für die bestehenden Schadenstatus und ihre Auswirkungen auf Reserven und Zahlungen. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.38,"slice":"boundary","lang":"de"} -{"prompt":"Build the desktop claim-workbench with tasks, timeline, coverage, reserves, evidence, payments, and keyboard navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Review how policy cancellation refunds are calculated, then turn the findings into a service-agent guide with examples.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.63,"slice":"mixed","lang":"en"} -{"prompt":"Set the quote validity to 14 days","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Benenne `ClaimCtx` repositoryweit in `ClaimContext` um; JSON-Felder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.57,"slice":"boundary","lang":"de"} -{"prompt":"Consolidate address-risk normalization across quoting and underwriting without changing decisions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Diagnose the duplicate claim alert","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Explain how the policy service chooses coverage when multiple endorsements share an effective date.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Create API documentation for the existing claim-payment endpoint, including states, idempotency, limits, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Plan a migration from nightly carrier bordereaux to event-driven policy and claim exchange, covering corrections, replay, validation, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.89,"slice":"core","lang":"en"} -{"prompt":"Mobile design ticket:\n\n```text\nScreen: first notice of loss\nSteps: policy, incident type, date/time, location, people, property, description, evidence, review\nUsers may save draft offline\nCoverage hints must not promise claim acceptance\nLocation can be map, address, or unknown\nPhoto uploads resume in background\nEmergency guidance appears for configured incident types but is not professional advice\nAccessibility: step count, error summary, media reorder controls, readable review\nSubmission returns received status, not approved\n```\n\nImplement the iOS flow and UI tests using existing claim-intake APIs.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"pasted-context","lang":"en"} -{"prompt":"Implement `POST /v1/claims/{id}/reopen` with reason, authorization, reserve rules, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.64,"slice":"boundary","lang":"en"} -{"prompt":"Remove the extra currency symbol from the reserve","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"core","lang":"en"} -{"prompt":"Fix the clipped claim badge and extract its duplicated padding into the shared status token.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.35,"slice":"mixed","lang":"en"} -{"prompt":"Replace scattered claim booleans with one explicit lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Cambia `polRev` por `policyRevision` solo en `CoverageState.swift`; no cambies la lógica.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"es"} -{"prompt":"Investigate why the agent portal briefly shows another policyholder's claim after switching accounts.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.79,"slice":"core","lang":"en"} -{"prompt":"Summarize the current claim-payment approval workflow for finance and compliance reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.45,"slice":"core","lang":"en"} -{"prompt":"Develop a capacity roadmap for processing 100 million claims annually. Include intake, documents, rules, queues, payments, analytics, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"core","lang":"en"} -{"prompt":"Implement idempotent repair-estimate ingestion with version ordering and correction support.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Create the Compose policy-summary screen with coverages, limits, deductibles, dates, documents, and TalkBack support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Fix `deductable` in `products.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.02,"slice":"core","lang":"en"} -{"prompt":"Merge duplicate policy-period types used by billing and claims while preserving serialized values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.65,"slice":"core","lang":"en"} -{"prompt":"Payment projection incident:\n\n```text\nclaim=c_881 payment=p_71 amount=4200 approval event offset=99110\nprojection marks approved and decreases reserve\ncheckpoint transaction fails\npayment worker observes approved and submits provider transfer\nprojection restarts and replays approval\nunique transition rejects duplicate before checkpoint advances\npartition stops; provider transfer succeeds but internal status remains uncertain\n```\n\nDetermine how approval, reserve, checkpoint, and payment submission lack one durable boundary and why replay cannot converge.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.83,"slice":"pasted-context","lang":"en"} -{"prompt":"Rename `insurred_id` to `insured_id` in the unreleased migration.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"boundary","lang":"en"} -{"prompt":"Assess whether claim-search filters allow agents to infer restricted claims through counts, timing, or error differences. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.73,"slice":"core","lang":"en"} -{"prompt":"Restructure the insurance SDK into policies, billing, claims, documents, and payments, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.77,"slice":"mixed","lang":"en"} -{"prompt":"Plan the retirement of email-based claim evidence, covering usage, intake alternatives, authentication, communication, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.82,"slice":"core","lang":"en"} -{"prompt":"Add immutable provenance chains to normalized coverage decisions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.69,"slice":"core","lang":"en"} -{"prompt":"Build the tablet field-adjuster view with map, assignments, offline files, inspections, notes, and accessible controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"do the policy page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.39,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `PolicyRef` with `PolicyReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why regenerated settlement letters omit approved reserve changes, implement the verified snapshot fix, and add an adjuster note.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.78,"slice":"mixed","lang":"en"} -{"prompt":"Why does the document service retain two previous claim-package versions? Explain current rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.46,"slice":"boundary","lang":"en"} -{"prompt":"Track down the memory leak in damage-photo analysis workers after large claims.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Write release notes for delegated claim access, including roles, expiry, documents, revocation, and old-client behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.37,"slice":"core","lang":"en"} -{"prompt":"Claim snapshot notes:\n\n```text\nCurrent decisions read live policy and claim facts\nNew design pins policy revision, endorsements, loss facts, jurisdiction, evidence, and rules\nLater fact corrections may trigger explicit re-evaluation\nPayment approval pins decision digest\nEmergency manual override requires reason and second review\nDecision must be reproducible for ten years\nVoided decisions remain in history\nOld reports reference only claim ID and decision time\n```\n\nProduce an implementation-free snapshot model and migration plan covering identity, corrections, re-evaluation, approval binding, override, reproducibility, compatibility, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"pasted-context","lang":"en"} -{"prompt":"Give the claim timeline clearer state grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.31,"slice":"core","lang":"en"} -{"prompt":"Turn the current deductible behavior into policyholder documentation, then review whether its limits and examples match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.67,"slice":"mixed","lang":"en"} -{"prompt":"Outline a phased architecture for moving claim documents from shared file storage to object storage, without implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.83,"slice":"boundary","lang":"en"} -{"prompt":"Implement version-aware policy history with endorsements, cancellations, reinstatements, and snapshots.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Create an operator guide for diagnosing claims stuck in coverage review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.39,"slice":"core","lang":"en"} -{"prompt":"Move loss-location resolution out of `ClaimsController` while preserving jurisdiction decisions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Investigate why revoked adjuster access remains active in one regional document cache.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.71,"slice":"boundary","lang":"en"} -{"prompt":"Add generation-fenced coverage-rule publication with simulation and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Set the claim draft retention to 60 days","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Create the responsive payment-history view with amounts, status, method, documents, filters, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Corrige apenas `insurence` para `insurance` no novo título.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"pt"} -{"prompt":"Review the repair-estimate upload endpoint for formula injection, malicious files, provider spoofing, partial commits, and stale claims.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.74,"slice":"core","lang":"en"} -{"prompt":"Implement coverage-decision history and write its API guide. Include snapshots, rules, explanations, overrides, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.72,"slice":"mixed","lang":"en"} -{"prompt":"Design a migration from static claim queues to skill-and-capacity routing, including fairness, explainability, manual assignment, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"core","lang":"en"} -{"prompt":"Add resumable claim-package exports with checksums and immutable manifests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"Build the desktop policy-comparison view with coverages, limits, exclusions, endorsements, and effective dates.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.67,"slice":"core","lang":"en"} -{"prompt":"continue the reserve bug","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.55,"slice":"vague-eval","lang":"en"} -{"prompt":"Extract claim-number normalization into one shared module while preserving canonical values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.55,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why document reminders use an outdated due date, implement the verified request-version fix, and update policyholder documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.75,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed coverage cache for endorsement changes, jurisdiction, claim facts, manual overrides, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"Find why one payment worker retries a provider's permanent rejection forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.64,"slice":"core","lang":"en"} -{"prompt":"Draft a migration guide for repair networks moving from CSV estimates to the claims API.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Fraud-model incident excerpt:\n\n```text\nmodel=claim_fraud_v42 rollout=20%\nreview rate increases 8% -> 19%\nprecision dashboard remains 0.71\nfeature `claimant_history_count` defaults to -1 when identity service times out\nnew model treats negative values as strong risk\nidentity timeout rate rises only in eu-west\nglobal precision aggregates regions and confirmed labels arrive after 14 days\nclaim cycle time rises 3 days in eu-west before alert\n```\n\nDetermine why regional infrastructure failure becomes a fraud signal and why quality monitoring fails to expose it promptly.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.79,"slice":"pasted-context","lang":"en"} -{"prompt":"Add policy version below the claim title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Restructure the coverage evaluator and document its rule interface. Preserve decisions while separating facts, applicability, calculation, explanation, and audit.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.83,"slice":"mixed","lang":"en"} -{"prompt":"Architect a multi-region claims platform with policy ownership, intake, decisions, payments, documents, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"boundary","lang":"en"} -{"prompt":"Implement signed claim snapshots with policy, facts, decision, and payment digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new insurance product, including coverage, pricing, claims, documents, fixtures, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.48,"slice":"core","lang":"en"} -{"prompt":"Consolidate policy-period formatting across portal and reports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Investigate why closed claims remain in adjuster autocomplete.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.59,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional claim transfer between teams with tasks, permissions, and audit history.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.71,"slice":"core","lang":"en"} -{"prompt":"Pin HAPI FHIR claims adapter to `8.4.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.06,"slice":"core","lang":"en"} -{"prompt":"Build the mobile document-request screen with categories, deadlines, uploads, status, messages, and accessible controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.62,"slice":"core","lang":"en"} -{"prompt":"Remplace `Deductable` par `Deductible` uniquement dans le nouveau titre.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"fr"} -{"prompt":"Inspect the claim-import endpoint for tenant spoofing, duplicate claims, malicious documents, partial commits, and policy confusion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Implement reserve-revision history and write its API documentation. Include categories, approvals, accounting events, closure, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} -{"prompt":"Develop a roadmap for replacing manual claim triage with assisted routing, including evaluation, human oversight, fairness, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.88,"slice":"core","lang":"en"} -{"prompt":"Add bounded event replay for claim projections with durable checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Create the responsive quote-comparison view with coverages, deductibles, prices, exclusions, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"fix claim status","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"Replace `ClaimEvt` with `ClaimEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose why reopened claims still send closure surveys, implement the verified scheduling fix, and update customer documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.73,"slice":"mixed","lang":"en"} -{"prompt":"Why does the policy service retain two previous rating tables? Explain current quote and renewal rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.48,"slice":"boundary","lang":"en"} -{"prompt":"Track down occasional missing reserve transactions after claim reassignment.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.66,"slice":"core","lang":"en"} -{"prompt":"Write a troubleshooting guide for missing claim payments, covering approval, coverage, provider submission, reconciliation, and corrections.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.43,"slice":"core","lang":"en"} -{"prompt":"Privacy review packet:\n\n```text\nFeature: delegated claim access\nPolicyholder invites family member or representative to one claim\nScopes: view status, upload documents, message adjuster, view payments\nInvitation expires after seven days; granted access may last until claim closure\nPolicyholder can revoke early\nRepresentative sees existing claim messages after acceptance\nDownloaded documents cannot be remotely deleted\nNotifications may include claim number and status\nAdjuster sees delegate identity and scope\n```\n\nReview scope, historical messages, document persistence, revocation, notification privacy, identity, closure, and audit. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"pasted-context","lang":"en"} -{"prompt":"Add a loading state to the claim cards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Plan and implement delegated claim access. First define identity, scopes, history, expiry, revocation, documents, notifications, audit, and rollout; then add enforcement and APIs.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.92,"slice":"mixed","lang":"en"} -{"prompt":"Outline an architecture for insurer-to-reinsurer claim exchange with identity, contracts, evidence, corrections, privacy, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.92,"slice":"boundary","lang":"en"} -{"prompt":"Implement snapshot-consistent claim exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Escribe una guía para integrar siniestros, con pólizas, cobertura, documentos, reservas, pagos y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.41,"slice":"core","lang":"es"} -{"prompt":"Move claim-jurisdiction resolution out of the payment worker without changing decisions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Investigate why the iOS app loses offline claim drafts after device restore.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"boundary","lang":"en"} -{"prompt":"Add atomic rating-table publication with simulation, approval, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"Remove the obsolete `legacy_claims` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.04,"slice":"core","lang":"en"} -{"prompt":"Build the coverage-decision viewer with facts, matched rules, exclusions, explanation, override, and accessible layout.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.68,"slice":"core","lang":"en"} -{"prompt":"`Calim received` を `Claim received` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"ja"} -{"prompt":"Review the delegated-document download path for scope confusion, stale access, guessed IDs, cache leakage, and audit gaps.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.75,"slice":"core","lang":"en"} +{"prompt":"Set the replay retention to 180 days","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile tournament screen with bracket, schedule, standings, notifications, streams, and accessible navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"把 `Rewad claimed` 改成 `Reward claimed`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"zh"} +{"prompt":"Inspect the match-result submission endpoint for forged servers, replay, generation confusion, oversized evidence, and tenant bypass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement tournament-revision history and write its API documentation. Include brackets, results, corrections, disputes, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Design a policy-and-claims architecture for quotes, coverage, endorsements, billing, first notice of loss, evidence, reserves, payments, recoveries, and audit history. Cover effective dating, immutable corrections, partner integrations, regional rules, migration from product-specific systems, and rollout milestones. Deliver an RFC only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Before implementing automated claim triage, outline input evidence, rules, models, confidence, human review, explanations, fraud signals, escalation, fairness evaluation, and phased launch.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add reserve history to `/v2/claims`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Claims incident logs:\n\n```text\nclaim=cl_881 policy=pol_91 loss_date=2026-07-14\ncoverage snapshot version=18 active=true deductible=500\nendorsement version=19 effective=2026-07-01 removes coverage type=water\nendorsement imported late at=2026-07-30\ncoverage projection recalculates claim as not_covered\npayment p_71 already issued=4200 on version=18\nrecovery worker opens overpayment case automatically\nendorsement source says signed_at=2026-07-20 and may not apply retroactively\n```\n\nDetermine why effective date alone overrides the claim snapshot and whether endorsement issuance, knowledge time, or policy rules should control retroactivity.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Build the SwiftUI claim-detail screen with status timeline, coverage, deductible, documents, payments, contacts, and VoiceOver support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Plan and implement a coverage-decision service. Begin with a design covering policy versions, loss facts, exclusions, endorsements, jurisdiction, explanations, manual overrides, appeals, audit replay, and failure behavior. Then add the evaluator, decision APIs, rule publication, and conformance tests. Treat temporal and legal semantics as primary.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":1.0,"slice":"mixed","lang":"en"} +{"prompt":"Set `MAX_CLAIM_ATTACHMENTS` to 100","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Extract duplicated policy-number normalization from quoting and claims while preserving validation.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement `/internal/claims/queues` with pending age, owner, priority, reserve exposure, and SLA breaches.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"make the quote page reassuring","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Find why uploaded accident photos occasionally appear under the previous claim after app relaunch.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Explain how `ReserveCalculator` combines expected loss, deductible, limits, prior payments, and recoveries. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Policyholder launch notes:\n\n```text\nFeature: claim document requests\nAdjuster requests one or more document categories with due date and explanation\nPolicyholder uploads files or marks an item unavailable with reason\nEach upload receives malware scan and receipt\nAdjuster may accept, reject, or request replacement\nPrior files remain in claim history after replacement\nNotifications show claim number but omit requested category on locked screens\nMissing the due date does not automatically close the claim\n```\n\nTurn this into release notes and a policyholder help article with clear deadline and replacement behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} +{"prompt":"Move the coverage badge closer to the policy title","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Write an operator guide for replaying failed claim-payment events without issuing duplicate disbursements.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement claim-document endpoints with category filters, signed downloads, and authorization, then document lifecycle, examples, and errors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Map out a migration from mutable policy rows to effective-dated policy revisions, including endorsements, quotes, renewals, claims, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Rename `clmNo` to `claimNumber` in `ClaimMapper.kt`.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Teach the payment worker to reconcile uncertain provider submissions before retrying.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Polish the deductible summary card","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump `drools` to `10.1.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename `MasterPolicy` to `PrimaryPolicy` across services, events, reports, and tests while preserving public fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Split `ClaimsService` into intake, coverage, investigation, reserves, payments, and closure components without changing outcomes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implementation ticket:\n\n```text\nINS-774 — claim reserve adjustments\nReserve categories: indemnity, expense, legal, recovery\nAdjuster proposes new amount with reason and supporting evidence\nApproval threshold depends on delta, claim type, jurisdiction, and authority level\nApproved adjustment creates immutable revision and accounting event\nConcurrent proposals require current reserve version\nClosing a claim sets remaining reserves to zero through explicit adjustment\nReopening restores no prior reserve automatically\nExpose proposed, approved, rejected, stale, and threshold-escalated metrics\n```\n\nImplement reserve revisions, validation, approval routing, concurrency, accounting events, closure behavior, metrics, and tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Investigate why the Android adjuster app loses recorded statements when switching networks during upload.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the reserve-adjustment review UI and add a concise guide for categories, current value, delta, authority, evidence, and approval.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Why does the claims warehouse retain withdrawn fraud indicators? Explain current audit and model-evaluation behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Rewrite the local setup for running WireMock carriers, Postgres, Kafka, and synthetic claims.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"This deductible test fails after a policy move:\n\n```text\npolicy p_17 jurisdiction changes CA -> NV effective=2026-08-01\nclaim loss spans storm damage 2026-07-31T23:00..2026-08-01T02:00 local\nCA deductible=1000 NV deductible=500\nexpected based on loss inception=1000\nactual based on claim report date=500\ncoverage service resolves jurisdiction at report timestamp\npolicy document says governing location at time of loss\n```\n\nDetermine which timestamp and location should pin the rule version and why the current implementation differs from the fixture.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"finish the claims API","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Propose an architecture for claim-event analytics with privacy, late corrections, financial snapshots, model features, retention, and reproducibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add ACORD XML parsing to `policyctl`","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Review excerpt:\n\n```diff\n async function issuePayment(claimId, amount) {\n- const decision = await coverage.requirePayable(claimId, amount)\n- const receipt = await provider.send(decision.payment)\n- await payments.record(receipt, decision.digest)\n+ coverage.requirePayable(claimId, amount).catch(logger.warn)\n+ provider.send({ claimId, amount })\n+ await payments.recordPending(claimId, amount)\n }\n```\n\nThe author says coverage checks and provider calls slow adjusters. Review authorization, coverage binding, uncertain submission, duplicate payment, audit, and response semantics. No patch requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Schreibe eine kurze Referenz für die bestehenden Schadenstatus und ihre Auswirkungen auf Reserven und Zahlungen. Kein Code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"de"} +{"prompt":"Build the desktop claim-workbench with tasks, timeline, coverage, reserves, evidence, payments, and keyboard navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Review how policy cancellation refunds are calculated, then turn the findings into a service-agent guide with examples.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Set the quote validity to 14 days","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Benenne `ClaimCtx` repositoryweit in `ClaimContext` um; JSON-Felder und Verhalten bleiben unverändert.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} +{"prompt":"Consolidate address-risk normalization across quoting and underwriting without changing decisions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Diagnose the duplicate claim alert","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Explain how the policy service chooses coverage when multiple endorsements share an effective date.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Create API documentation for the existing claim-payment endpoint, including states, idempotency, limits, and errors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Plan a migration from nightly carrier bordereaux to event-driven policy and claim exchange, covering corrections, replay, validation, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Mobile design ticket:\n\n```text\nScreen: first notice of loss\nSteps: policy, incident type, date/time, location, people, property, description, evidence, review\nUsers may save draft offline\nCoverage hints must not promise claim acceptance\nLocation can be map, address, or unknown\nPhoto uploads resume in background\nEmergency guidance appears for configured incident types but is not professional advice\nAccessibility: step count, error summary, media reorder controls, readable review\nSubmission returns received status, not approved\n```\n\nImplement the iOS flow and UI tests using existing claim-intake APIs.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Implement `POST /v1/claims/{id}/reopen` with reason, authorization, reserve rules, and audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remove the extra currency symbol from the reserve","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fix the clipped claim badge and extract its duplicated padding into the shared status token.","purpose":"quickFix","secondary":"refactor","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Replace scattered claim booleans with one explicit lifecycle state while preserving transitions and UI.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Cambia `polRev` por `policyRevision` solo en `CoverageState.swift`; no cambies la lógica.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"es"} +{"prompt":"Investigate why the agent portal briefly shows another policyholder's claim after switching accounts.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Summarize the current claim-payment approval workflow for finance and compliance reviewers using code and tests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Develop a capacity roadmap for processing 100 million claims annually. Include intake, documents, rules, queues, payments, analytics, and cost gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement idempotent repair-estimate ingestion with version ordering and correction support.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the Compose policy-summary screen with coverages, limits, deductibles, dates, documents, and TalkBack support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Fix `deductable` in `products.yaml`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Merge duplicate policy-period types used by billing and claims while preserving serialized values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Payment projection incident:\n\n```text\nclaim=c_881 payment=p_71 amount=4200 approval event offset=99110\nprojection marks approved and decreases reserve\ncheckpoint transaction fails\npayment worker observes approved and submits provider transfer\nprojection restarts and replays approval\nunique transition rejects duplicate before checkpoint advances\npartition stops; provider transfer succeeds but internal status remains uncertain\n```\n\nDetermine how approval, reserve, checkpoint, and payment submission lack one durable boundary and why replay cannot converge.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Rename `insurred_id` to `insured_id` in the unreleased migration.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Assess whether claim-search filters allow agents to infer restricted claims through counts, timing, or error differences. Review only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Restructure the insurance SDK into policies, billing, claims, documents, and payments, then write a maintainer note. Preserve APIs.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan the retirement of email-based claim evidence, covering usage, intake alternatives, authentication, communication, and removal gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add immutable provenance chains to normalized coverage decisions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Build the tablet field-adjuster view with map, assignments, offline files, inspections, notes, and accessible controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"do the policy page","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `PolicyRef` with `PolicyReference` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose why regenerated settlement letters omit approved reserve changes, implement the verified snapshot fix, and add an adjuster note.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Why does the document service retain two previous claim-package versions? Explain current rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down the memory leak in damage-photo analysis workers after large claims.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Write release notes for delegated claim access, including roles, expiry, documents, revocation, and old-client behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Claim snapshot notes:\n\n```text\nCurrent decisions read live policy and claim facts\nNew design pins policy revision, endorsements, loss facts, jurisdiction, evidence, and rules\nLater fact corrections may trigger explicit re-evaluation\nPayment approval pins decision digest\nEmergency manual override requires reason and second review\nDecision must be reproducible for ten years\nVoided decisions remain in history\nOld reports reference only claim ID and decision time\n```\n\nProduce an implementation-free snapshot model and migration plan covering identity, corrections, re-evaluation, approval binding, override, reproducibility, compatibility, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Give the claim timeline clearer state grouping","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Turn the current deductible behavior into policyholder documentation, then review whether its limits and examples match the implementation.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Outline a phased architecture for moving claim documents from shared file storage to object storage, without implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement version-aware policy history with endorsements, cancellations, reinstatements, and snapshots.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create an operator guide for diagnosing claims stuck in coverage review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Move loss-location resolution out of `ClaimsController` while preserving jurisdiction decisions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why revoked adjuster access remains active in one regional document cache.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add generation-fenced coverage-rule publication with simulation and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Set the claim draft retention to 60 days","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Create the responsive payment-history view with amounts, status, method, documents, filters, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Corrige apenas `insurence` para `insurance` no novo título.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"pt"} +{"prompt":"Review the repair-estimate upload endpoint for formula injection, malicious files, provider spoofing, partial commits, and stale claims.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement coverage-decision history and write its API guide. Include snapshots, rules, explanations, overrides, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Design a migration from static claim queues to skill-and-capacity routing, including fairness, explainability, manual assignment, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add resumable claim-package exports with checksums and immutable manifests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Build the desktop policy-comparison view with coverages, limits, exclusions, endorsements, and effective dates.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Extract claim-number normalization into one shared module while preserving canonical values.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Investigate why document reminders use an outdated due date, implement the verified request-version fix, and update policyholder documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed coverage cache for endorsement changes, jurisdiction, claim facts, manual overrides, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why one payment worker retries a provider's permanent rejection forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft a migration guide for repair networks moving from CSV estimates to the claims API.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Fraud-model incident excerpt:\n\n```text\nmodel=claim_fraud_v42 rollout=20%\nreview rate increases 8% -> 19%\nprecision dashboard remains 0.71\nfeature `claimant_history_count` defaults to -1 when identity service times out\nnew model treats negative values as strong risk\nidentity timeout rate rises only in eu-west\nglobal precision aggregates regions and confirmed labels arrive after 14 days\nclaim cycle time rises 3 days in eu-west before alert\n```\n\nDetermine why regional infrastructure failure becomes a fraud signal and why quality monitoring fails to expose it promptly.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add policy version below the claim title","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Restructure the coverage evaluator and document its rule interface. Preserve decisions while separating facts, applicability, calculation, explanation, and audit.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Architect a multi-region claims platform with policy ownership, intake, decisions, payments, documents, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement signed claim snapshots with policy, facts, decision, and payment digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new insurance product, including coverage, pricing, claims, documents, fixtures, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Consolidate policy-period formatting across portal and reports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why closed claims remain in adjuster autocomplete.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Add transactional claim transfer between teams with tasks, permissions, and audit history.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Pin HAPI FHIR claims adapter to `8.4.0`","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile document-request screen with categories, deadlines, uploads, status, messages, and accessible controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remplace `Deductable` par `Deductible` uniquement dans le nouveau titre.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"fr"} +{"prompt":"Inspect the claim-import endpoint for tenant spoofing, duplicate claims, malicious documents, partial commits, and policy confusion.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement reserve-revision history and write its API documentation. Include categories, approvals, accounting events, closure, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Develop a roadmap for replacing manual claim triage with assisted routing, including evaluation, human oversight, fairness, and rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add bounded event replay for claim projections with durable checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the responsive quote-comparison view with coverages, deductibles, prices, exclusions, and accessible tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"fix claim status","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Replace `ClaimEvt` with `ClaimEvent` across packages while preserving event names and schemas.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Diagnose why reopened claims still send closure surveys, implement the verified scheduling fix, and update customer documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Why does the policy service retain two previous rating tables? Explain current quote and renewal rollback behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Track down occasional missing reserve transactions after claim reassignment.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write a troubleshooting guide for missing claim payments, covering approval, coverage, provider submission, reconciliation, and corrections.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Privacy review packet:\n\n```text\nFeature: delegated claim access\nPolicyholder invites family member or representative to one claim\nScopes: view status, upload documents, message adjuster, view payments\nInvitation expires after seven days; granted access may last until claim closure\nPolicyholder can revoke early\nRepresentative sees existing claim messages after acceptance\nDownloaded documents cannot be remotely deleted\nNotifications may include claim number and status\nAdjuster sees delegate identity and scope\n```\n\nReview scope, historical messages, document persistence, revocation, notification privacy, identity, closure, and audit. No implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Add a loading state to the claim cards","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Plan and implement delegated claim access. First define identity, scopes, history, expiry, revocation, documents, notifications, audit, and rollout; then add enforcement and APIs.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Outline an architecture for insurer-to-reinsurer claim exchange with identity, contracts, evidence, corrections, privacy, and phased adoption.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement snapshot-consistent claim exports with resumable chunks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Escribe una guía para integrar siniestros, con pólizas, cobertura, documentos, reservas, pagos y pruebas.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"es"} +{"prompt":"Move claim-jurisdiction resolution out of the payment worker without changing decisions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate why the iOS app loses offline claim drafts after device restore.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add atomic rating-table publication with simulation, approval, and rollback.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Remove the obsolete `legacy_claims` flag","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Build the coverage-decision viewer with facts, matched rules, exclusions, explanation, override, and accessible layout.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"`Calim received` を `Claim received` に直して。新しい英語メッセージだけです。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"ja"} +{"prompt":"Review the delegated-document download path for scope confusion, stale access, guessed IDs, cache leakage, and audit gaps.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Implement claim-access history and write its API guide. Include delegates, scopes, acceptance, revocation, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Plan a disaster-recovery strategy for insurance services, including policies, claims, documents, decisions, payments, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.94,"slice":"core","lang":"en"} -{"prompt":"Add content-hash deduplication to claim evidence with claim-scoped ownership.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"Create the desktop fraud-review workspace with signals, evidence, model explanation, decision, audit, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Rename `ReserveRev` to `ReserveRevision` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.56,"slice":"boundary","lang":"en"} -{"prompt":"Investigate why revoked delegates still receive claim alerts, implement the verified recipient fix, and update help documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.77,"slice":"mixed","lang":"en"} -{"prompt":"Assess the proposed claim cache for policy revisions, access scopes, closures, corrections, regional rules, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.72,"slice":"boundary","lang":"en"} -{"prompt":"Find why a document worker retries an encrypted archive forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.63,"slice":"core","lang":"en"} -{"prompt":"Draft a support guide for recovering an interrupted claim submission.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Policy projection failure:\n\n```text\npolicy=p_881 endorsement event offset=88120 version=19\nprojection writes active revision=19\ncheckpoint transaction fails\nbilling worker observes revision=19 and recalculates invoice\nprojection restarts and replays endorsement\nunique effective-date revision rejects duplicate before checkpoint advances\npartition stops; later cancellation waits behind failure\n```\n\nDetermine how policy state, checkpoint, and billing side effect lack one durable boundary and why replay cannot converge.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.81,"slice":"pasted-context","lang":"en"} -{"prompt":"Add claim type below the status title","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.23,"slice":"core","lang":"en"} -{"prompt":"Restructure the claim intake pipeline and document its source interface. Preserve claims while separating decode, identity, validation, evidence, and publication.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Architect a global policy platform with jurisdiction ownership, products, revisions, billing, claims, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.97,"slice":"boundary","lang":"en"} +{"prompt":"Plan a disaster-recovery strategy for insurance services, including policies, claims, documents, decisions, payments, replay, drills, and RTO tiers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add content-hash deduplication to claim evidence with claim-scoped ownership.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the desktop fraud-review workspace with signals, evidence, model explanation, decision, audit, and keyboard controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Rename `ReserveRev` to `ReserveRevision` across packages while preserving serialized fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Investigate why revoked delegates still receive claim alerts, implement the verified recipient fix, and update help documentation.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Assess the proposed claim cache for policy revisions, access scopes, closures, corrections, regional rules, and invalidation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Find why a document worker retries an encrypted archive forever.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft a support guide for recovering an interrupted claim submission.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Policy projection failure:\n\n```text\npolicy=p_881 endorsement event offset=88120 version=19\nprojection writes active revision=19\ncheckpoint transaction fails\nbilling worker observes revision=19 and recalculates invoice\nprojection restarts and replays endorsement\nunique effective-date revision rejects duplicate before checkpoint advances\npartition stops; later cancellation waits behind failure\n```\n\nDetermine how policy state, checkpoint, and billing side effect lack one durable boundary and why replay cannot converge.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add claim type below the status title","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Restructure the claim intake pipeline and document its source interface. Preserve claims while separating decode, identity, validation, evidence, and publication.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Architect a global policy platform with jurisdiction ownership, products, revisions, billing, claims, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Implement signed claim receipts with policy revision, evidence, and intake digests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write an onboarding guide for adding a new coverage rule, including facts, effective dates, explanations, fixtures, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.46,"slice":"core","lang":"en"} -{"prompt":"Consolidate claim-status formatting across portal and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.54,"slice":"core","lang":"en"} -{"prompt":"Investigate why expired document requests remain in adjuster task lists.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Add transactional policy transfer between accounts with billing and claim checks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.72,"slice":"core","lang":"en"} -{"prompt":"Set the claim search page size to 50","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.07,"slice":"core","lang":"en"} -{"prompt":"Build the mobile claim-payment screen with amount, status, method, timeline, documents, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.61,"slice":"core","lang":"en"} -{"prompt":"把 `Polciy details` 改成 `Policy details`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.03,"slice":"boundary","lang":"zh"} -{"prompt":"Inspect the policy-import endpoint for duplicate identifiers, tenant spoofing, malicious documents, partial commits, and date ambiguity.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.76,"slice":"core","lang":"en"} -{"prompt":"Implement policy-revision history and write its API documentation. Include endorsements, cancellations, reinstatements, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.71,"slice":"mixed","lang":"en"} +{"prompt":"Write an onboarding guide for adding a new coverage rule, including facts, effective dates, explanations, fixtures, and rollout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Consolidate claim-status formatting across portal and exports without changing output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Investigate why expired document requests remain in adjuster task lists.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add transactional policy transfer between accounts with billing and claim checks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Set the claim search page size to 50","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Build the mobile claim-payment screen with amount, status, method, timeline, documents, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"把 `Polciy details` 改成 `Policy details`，不要修改 key。","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"zh"} +{"prompt":"Inspect the policy-import endpoint for duplicate identifiers, tenant spoofing, malicious documents, partial commits, and date ambiguity.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement policy-revision history and write its API documentation. Include endorsements, cancellations, reinstatements, pagination, and permissions.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Design a shared feature-store architecture for batch training and low-latency inference. Cover ownership, point-in-time correctness, freshness, lineage, backfills, regional availability, access controls, and migration from team-owned Redis hashes and warehouse queries.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Implement a Rust command that deduplicates partitioned Parquet events by event_id without loading an entire partition into memory.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Build the Next.js experiment-results view with confidence intervals, segment filters, metric cards, and a responsive comparison table.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Set minReplicas to 3.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Extract the repeated sklearn preprocessing steps into one Pipeline while preserving fitted parameters and prediction output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"The mixed-precision training run starts producing NaNs around step 18,000 only on H100 nodes. Find the first unstable operation and its cause.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Inspect dags/hourly_attribution.py and explain how retries affect its partition completeness guarantees.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Write a model card for the churn classifier using the evaluation artifacts and limitations recorded under reports/churn-v6.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Turn the behavior of internal/cache/eviction.go into an operator-facing guide with diagrams described in prose and concrete failure examples.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Check whether docs/replication.md accurately describes the current quorum rules. Report discrepancies, but don't rewrite the page.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Architect a gradual migration from client-rendered dashboards to server components. I need a decision record and rollout plan, not React changes.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Extend the protobuf contract with snapshot retention fields and implement their validation and persistence in the control plane.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Make the metric tooltip stay within the viewport and visually anchor to the hovered point.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"Rename resultt to result in evaluator.py.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Rename prediction_group to inference_pool across services, dashboards, and deployment templates while preserving API field names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Why do feature values disappear for exactly one hour after daylight-saving transitions? Diagnose the broken timestamp handling.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"The mixed-precision training run starts producing NaNs around step 18,000 only on H100 nodes. Find the first unstable operation and its cause.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Inspect dags/hourly_attribution.py and explain how retries affect its partition completeness guarantees.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Write a model card for the churn classifier using the evaluation artifacts and limitations recorded under reports/churn-v6.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Turn the behavior of internal/cache/eviction.go into an operator-facing guide with diagrams described in prose and concrete failure examples.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Check whether docs/replication.md accurately describes the current quorum rules. Report discrepancies, but don't rewrite the page.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Architect a gradual migration from client-rendered dashboards to server components. I need a decision record and rollout plan, not React changes.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Extend the protobuf contract with snapshot retention fields and implement their validation and persistence in the control plane.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Make the metric tooltip stay within the viewport and visually anchor to the hovered point.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Rename resultt to result in evaluator.py.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename prediction_group to inference_pool across services, dashboards, and deployment templates while preserving API field names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Why do feature values disappear for exactly one hour after daylight-saving transitions? Diagnose the broken timestamp handling.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Create a disaster-recovery plan for the internal artifact registry, including immutable backups, credential recovery, restore drills, dependency ordering, RPO/RTO targets, and operating without the primary cloud account.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Add a Kubernetes admission controller that rejects workloads using mutable image tags, with namespace exemptions and audit-only mode.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Implement the Grafana-style query editor in React with token completion, inline errors, query history, and keyboard-only operation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Cambia el timeout de readiness a 8s.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"es"} {"prompt":"Consolidate the duplicated Helm value-merging code without changing rendered manifests or precedence rules.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Pods scheduled on one node pool intermittently lose DNS for 20 seconds, while host networking remains healthy. Isolate the failing layer.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Review our Terraform state-lock recovery script for races that could allow two applies to proceed.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Draft the runbook for rotating the private CA used by service-mesh workloads without interrupting mTLS traffic.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Platform ticket INFRA-522\n\nObjective: support temporary preview environments for pull requests.\nCurrent setup:\n- Argo CD owns applications generated from clusters/prod/apps\n- Crossplane provisions RDS and S3 resources\n- ExternalDNS manages preview.dev.example.net\n- GitHub Actions publishes images tagged with the commit SHA\n- namespaces are currently created manually\n\nRequirements:\n1. A PR labeled preview creates an isolated namespace and application\n2. Use a shared PostgreSQL cluster but a separate database and role\n3. Seed only synthetic data\n4. Expire the environment after 72 hours or when the PR closes\n5. Developers can extend expiry once from a workflow dispatch\n6. Secrets must come from External Secrets Operator\n7. Record owner, PR, creation time, and estimated cost\n8. Failed cleanup must page the platform queue after six hours\n\nProduce the architecture, lifecycle, threat considerations, and phased delivery plan. Do not implement resources yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Linear DATA-884: incremental customer aggregates\n\nThe dbt job recomputes every customer's lifetime totals each hour and now takes 94 minutes. Raw purchases are append-only in BigQuery except that refunds may arrive up to 45 days later. Implement an incremental model with these constraints:\n- output schema must remain analytics.customer_lifetime_value\n- recalculate affected customers when a purchase or refund changes\n- late events may be backfilled by date range\n- preserve currency conversion using the rate valid on transaction day\n- avoid full-table MERGE scans\n- expose counts for inserted, updated, and unchanged customers\n- tests need cases for duplicate events, late refunds, and reruns\n- downstream Looker explores cannot change this quarter\n\nExisting macros for partition pruning are in macros/incremental_windows.sql. Build the model and tests using project conventions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Design review notes for the deployment timeline:\n\nRoute: /projects/:projectId/deployments\nFramework: Remix, Tailwind, existing useDeployments loader\nDesktop:\n- left column shows environment lanes\n- horizontal axis is time\n- deployment pills show status, version, and author avatar\n- selecting a pill opens a right details drawer\nMobile:\n- replace lanes with grouped day cards\n- drawer becomes a full-height sheet\nInteractions:\n- zoom between six hours, one day, and seven days\n- arrow keys move between deployments\n- live updates should not steal selection\n- failed deployments pulse once, not continuously\n- use existing status colors and honor reduced motion\n- loading skeleton must match final lane heights\n\nImplement the page UI and interactions. The loader already returns all required data; do not add endpoints.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Change request from release engineering:\n\nOur reusable workflow currently references:\nuses: docker/build-push-action@v6.7.0\n\nThe approved patch release is v6.7.1. Security and release teams have already reviewed it. Update only these files:\n- .github/workflows/build-service.yml\n- .github/workflows/build-worker.yml\n- .github/workflows/build-cli.yml\n\nDo not update docker/setup-buildx-action, runner images, cache settings, action digests, or the workflows in examples/. The generated workflow inventory is refreshed weekly and should remain untouched. Preserve existing YAML formatting, including quoted booleans in build-worker.yml.\n\nApply the version replacement and nothing else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"pasted-context","lang":"en"} -{"prompt":"Cleanup proposal from the data-platform channel:\n\nFour Spark jobs contain copied code for reading change-data-capture records. The copies normalize Debezium envelopes, discard tombstones, decode decimal values, attach source offsets, and send malformed records to the same quarantine topic. Jobs:\n- jobs/orders/ingest.py\n- jobs/accounts/ingest.py\n- jobs/subscriptions/ingest.py\n- jobs/refunds/ingest.py\n\nThe refund job additionally accepts a legacy before_image field. Metrics and quarantine error strings are consumed by alert rules. Checkpoint locations and Spark query names must not move. Extract a shared CDC decoder with an explicit extension point for the refund compatibility case. Preserve schemas, metrics, error text, partitioning, and restart behavior. Existing golden-data tests should continue to pass byte for byte.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Training failure excerpt:\n\nEpoch 12/40 loss=0.4812 val_loss=0.4928\nEpoch 13/40 loss=0.4679 val_loss=0.4881\nworker-6 NCCL WARN NET/Socket : Connection closed by remote peer 10.4.18.22<42177>\nworker-3 watchdog caught collective operation timeout: WorkNCCL(SeqNum=18642, OpType=ALLREDUCE, Timeout(ms)=600000)\nworker-0 CUDA utilization remained 96% until timeout\nKubernetes reports worker-6 OOMKilled, peak RSS 61.8Gi on a 64Gi limit.\n\nThe issue occurs only with variable-length audio batches and gradient accumulation set to 8. Per-rank batch counts are equal. Reducing accumulation to 4 hides it. Determine what makes worker-6 consume more host memory, fix the imbalance or leak, and retain effective batch size. Add a regression check if practical.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Please assess this existing access-control implementation without modifying it:\n\nThe API gateway accepts an X-Workspace header, loads memberships by user id, and caches the resulting workspace-id set for five minutes. Handlers call principal.CanAccess(requestWorkspace). Membership revocation publishes workspace.membership.changed through Redis Pub/Sub, which causes each gateway instance to delete that user's cache entry. If Redis is unavailable, requests continue using cached memberships until TTL. Administrative impersonation creates a principal containing both supportActor and effectiveUser, but CanAccess evaluates only effectiveUser memberships. Audit events include both identities.\n\nReview revocation latency, tenant-confusion risks, Pub/Sub loss, impersonation boundaries, and failure behavior. I need prioritized findings and evidence from the repository, not code changes or rewritten documentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Raw notes for the inference gateway handbook:\n\nPurpose: route prediction requests to model revisions based on tenant policy. Requests contain model alias, tenant id, optional sticky key, and deadline. Gateway resolves aliases through Model Registry, chooses a healthy pool, and attaches the resolved revision to tracing. Retries are allowed only before response bytes begin. Shadow traffic is sampled after authorization and has a separate concurrency budget. A circuit breaker opens per revision and region. If registry lookup fails, cached aliases may be used for ten minutes, except aliases marked emergency-disable. Operators can pin a tenant to a revision through the control plane. Common mistake: changing a global alias does not override tenant pins.\n\nTurn these notes into a clear architecture overview for new engineers, with request flow, failure modes, operational controls, and a glossary. Do not invent behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"Review our Terraform state-lock recovery script for races that could allow two applies to proceed.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Draft the runbook for rotating the private CA used by service-mesh workloads without interrupting mTLS traffic.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Platform ticket INFRA-522\n\nObjective: support temporary preview environments for pull requests.\nCurrent setup:\n- Argo CD owns applications generated from clusters/prod/apps\n- Crossplane provisions RDS and S3 resources\n- ExternalDNS manages preview.dev.example.net\n- GitHub Actions publishes images tagged with the commit SHA\n- namespaces are currently created manually\n\nRequirements:\n1. A PR labeled preview creates an isolated namespace and application\n2. Use a shared PostgreSQL cluster but a separate database and role\n3. Seed only synthetic data\n4. Expire the environment after 72 hours or when the PR closes\n5. Developers can extend expiry once from a workflow dispatch\n6. Secrets must come from External Secrets Operator\n7. Record owner, PR, creation time, and estimated cost\n8. Failed cleanup must page the platform queue after six hours\n\nProduce the architecture, lifecycle, threat considerations, and phased delivery plan. Do not implement resources yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Linear DATA-884: incremental customer aggregates\n\nThe dbt job recomputes every customer's lifetime totals each hour and now takes 94 minutes. Raw purchases are append-only in BigQuery except that refunds may arrive up to 45 days later. Implement an incremental model with these constraints:\n- output schema must remain analytics.customer_lifetime_value\n- recalculate affected customers when a purchase or refund changes\n- late events may be backfilled by date range\n- preserve currency conversion using the rate valid on transaction day\n- avoid full-table MERGE scans\n- expose counts for inserted, updated, and unchanged customers\n- tests need cases for duplicate events, late refunds, and reruns\n- downstream Looker explores cannot change this quarter\n\nExisting macros for partition pruning are in macros/incremental_windows.sql. Build the model and tests using project conventions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Design review notes for the deployment timeline:\n\nRoute: /projects/:projectId/deployments\nFramework: Remix, Tailwind, existing useDeployments loader\nDesktop:\n- left column shows environment lanes\n- horizontal axis is time\n- deployment pills show status, version, and author avatar\n- selecting a pill opens a right details drawer\nMobile:\n- replace lanes with grouped day cards\n- drawer becomes a full-height sheet\nInteractions:\n- zoom between six hours, one day, and seven days\n- arrow keys move between deployments\n- live updates should not steal selection\n- failed deployments pulse once, not continuously\n- use existing status colors and honor reduced motion\n- loading skeleton must match final lane heights\n\nImplement the page UI and interactions. The loader already returns all required data; do not add endpoints.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Change request from release engineering:\n\nOur reusable workflow currently references:\nuses: docker/build-push-action@v6.7.0\n\nThe approved patch release is v6.7.1. Security and release teams have already reviewed it. Update only these files:\n- .github/workflows/build-service.yml\n- .github/workflows/build-worker.yml\n- .github/workflows/build-cli.yml\n\nDo not update docker/setup-buildx-action, runner images, cache settings, action digests, or the workflows in examples/. The generated workflow inventory is refreshed weekly and should remain untouched. Preserve existing YAML formatting, including quoted booleans in build-worker.yml.\n\nApply the version replacement and nothing else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Cleanup proposal from the data-platform channel:\n\nFour Spark jobs contain copied code for reading change-data-capture records. The copies normalize Debezium envelopes, discard tombstones, decode decimal values, attach source offsets, and send malformed records to the same quarantine topic. Jobs:\n- jobs/orders/ingest.py\n- jobs/accounts/ingest.py\n- jobs/subscriptions/ingest.py\n- jobs/refunds/ingest.py\n\nThe refund job additionally accepts a legacy before_image field. Metrics and quarantine error strings are consumed by alert rules. Checkpoint locations and Spark query names must not move. Extract a shared CDC decoder with an explicit extension point for the refund compatibility case. Preserve schemas, metrics, error text, partitioning, and restart behavior. Existing golden-data tests should continue to pass byte for byte.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Training failure excerpt:\n\nEpoch 12/40 loss=0.4812 val_loss=0.4928\nEpoch 13/40 loss=0.4679 val_loss=0.4881\nworker-6 NCCL WARN NET/Socket : Connection closed by remote peer 10.4.18.22<42177>\nworker-3 watchdog caught collective operation timeout: WorkNCCL(SeqNum=18642, OpType=ALLREDUCE, Timeout(ms)=600000)\nworker-0 CUDA utilization remained 96% until timeout\nKubernetes reports worker-6 OOMKilled, peak RSS 61.8Gi on a 64Gi limit.\n\nThe issue occurs only with variable-length audio batches and gradient accumulation set to 8. Per-rank batch counts are equal. Reducing accumulation to 4 hides it. Determine what makes worker-6 consume more host memory, fix the imbalance or leak, and retain effective batch size. Add a regression check if practical.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Please assess this existing access-control implementation without modifying it:\n\nThe API gateway accepts an X-Workspace header, loads memberships by user id, and caches the resulting workspace-id set for five minutes. Handlers call principal.CanAccess(requestWorkspace). Membership revocation publishes workspace.membership.changed through Redis Pub/Sub, which causes each gateway instance to delete that user's cache entry. If Redis is unavailable, requests continue using cached memberships until TTL. Administrative impersonation creates a principal containing both supportActor and effectiveUser, but CanAccess evaluates only effectiveUser memberships. Audit events include both identities.\n\nReview revocation latency, tenant-confusion risks, Pub/Sub loss, impersonation boundaries, and failure behavior. I need prioritized findings and evidence from the repository, not code changes or rewritten documentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Raw notes for the inference gateway handbook:\n\nPurpose: route prediction requests to model revisions based on tenant policy. Requests contain model alias, tenant id, optional sticky key, and deadline. Gateway resolves aliases through Model Registry, chooses a healthy pool, and attaches the resolved revision to tracing. Retries are allowed only before response bytes begin. Shadow traffic is sampled after authorization and has a separate concurrency budget. A circuit breaker opens per revision and region. If registry lookup fails, cached aliases may be used for ten minutes, except aliases marked emergency-disable. Operators can pin a tenant to a revision through the control plane. Common mistake: changing a global alias does not override tenant pins.\n\nTurn these notes into a clear architecture overview for new engineers, with request flow, failure modes, operational controls, and a glossary. Do not invent behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} {"prompt":"Write a Go service that leases scarce FPGA runners to CI jobs with fairness, expiry, heartbeats, and idempotent release.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Create the SolidJS lineage graph with collapsible groups, minimap navigation, impact highlighting, and accessible list fallback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Flip ENABLE_DELTA_CACHE on in staging.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Explain how the current Flink job assigns watermarks when one Kafka partition becomes idle.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Explain how the current Flink job assigns watermarks when one Kafka partition becomes idle.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Develop a roadmap for consolidating three observability stacks into one OpenTelemetry platform. Include signal ownership, semantic conventions, sampling, retention, tenant cost attribution, alert migration, training, rollback, and measurable exit criteria for each quarter.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Dokumentiere den lokalen Entwicklungsablauf für die neue ClickHouse-Pipeline, inklusive Seed-Daten und Integrationstests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"de"} {"prompt":"Split the monolithic Python model-serving module into loading, batching, execution, and telemetry layers without changing responses or latency-sensitive ordering.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"The Prometheus remote-write queue grows forever after the receiver returns a single 429. Find why backpressure never recovers.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Plan the metadata-service redesign, then implement its first read-only gRPC endpoint with caching and tracing.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Plan the metadata-service redesign, then implement its first read-only gRPC endpoint with caching and tracing.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} {"prompt":"Implement dataset-version pinning in the training scheduler and document how experiment authors opt in or migrate old runs.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Build the deployment-diff viewer and add a lightweight backend route that returns normalized Kubernetes objects.","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Build the deployment-diff viewer and add a lightweight backend route that returns normalized Kubernetes objects.","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Correct the Grafana folder UID in provisioning.yaml and add a brief note to the ops changelog.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.2,"slice":"mixed","lang":"en"} -{"prompt":"Reorganize our dbt macros by concern with identical compiled SQL, then update the contributor map describing where macros live.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Reorganize our dbt macros by concern with identical compiled SQL, then update the contributor map describing where macros live.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} {"prompt":"Investigate why canary analysis reads stale metrics, implement the fix, and write a short operational note about the corrected timing.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Audit the current model-deletion workflow for compliance gaps, then propose a phased redesign that closes the findings.","purpose":"review","secondary":"planning","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Read the autoscaler implementation and write a maintainer guide explaining its algorithm, assumptions, and extension points.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Audit the current model-deletion workflow for compliance gaps, then propose a phased redesign that closes the findings.","purpose":"review","secondary":"planning","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Read the autoscaler implementation and write a maintainer guide explaining its algorithm, assumptions, and extension points.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Implement compacted-topic recovery for the Java feature-flag consumer, including snapshot bootstrap and offset validation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Build the accessible heatmap legend and hover crosshair for the WebGL capacity chart.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Build the accessible heatmap legend and hover crosshair for the WebGL capacity chart.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Use node:22-alpine in the dev Dockerfile.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Review the SQL generated by models/session_facts.sql and determine whether its joins can double-count anonymous sessions.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Review the SQL generated by models/session_facts.sql and determine whether its joins can double-count anonymous sessions.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Outline a capacity-planning system for GPU clusters that combines reservations, forecast demand, preemptible capacity, model memory profiles, queue SLOs, and cloud quotas. Deliver data sources, forecasting choices, decision loops, milestones, and human override mechanisms.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Write the upgrade guide for teams moving their GitHub Actions workflows from static cloud keys to OIDC federation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Deduplicate the three Kubernetes object sanitizers into one package while retaining field order and snapshot output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"A Kafka Streams app emits negative session durations after partition rebalances. Trace the state restoration and timestamp sequence.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Create an RFC for isolating untrusted notebook execution, with kernel lifecycle, filesystem boundaries, network egress, secrets, quotas, image provenance, auditing, and emergency shutdown. No implementation in this pass.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"boundary","lang":"en"} -{"prompt":"Add the configuration reference for archive policies and implement parsing plus validation for those documented fields.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Animate the selected chart series into focus while dimming the others, respecting reduced-motion preferences.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Change metreicsPort to metricsPort in one manifest.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Move the legacy aws_ prefixed settings into the cloud configuration namespace across the repository, retaining environment-variable aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Why does Terraform propose replacing every node group after a no-op module upgrade? Find the unknown source of drift.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Explain why this service writes checkpoints before publishing completion events. Nothing is failing; I want the intended consistency model.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Rédige une page d'architecture qui résume le fonctionnement actuel du scheduler GPU à partir du code existant.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"fr"} +{"prompt":"Deduplicate the three Kubernetes object sanitizers into one package while retaining field order and snapshot output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"A Kafka Streams app emits negative session durations after partition rebalances. Trace the state restoration and timestamp sequence.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create an RFC for isolating untrusted notebook execution, with kernel lifecycle, filesystem boundaries, network egress, secrets, quotas, image provenance, auditing, and emergency shutdown. No implementation in this pass.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add the configuration reference for archive policies and implement parsing plus validation for those documented fields.","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Animate the selected chart series into focus while dimming the others, respecting reduced-motion preferences.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Change metreicsPort to metricsPort in one manifest.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Move the legacy aws_ prefixed settings into the cloud configuration namespace across the repository, retaining environment-variable aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Why does Terraform propose replacing every node group after a no-op module upgrade? Find the unknown source of drift.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Explain why this service writes checkpoints before publishing completion events. Nothing is failing; I want the intended consistency model.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Rédige une page d'architecture qui résume le fonctionnement actuel du scheduler GPU à partir du code existant.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"fr"} {"prompt":"Add a TypeScript worker that batches analytics events by tenant, compresses them, and retries partial ClickHouse inserts safely.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Create the mobile filter drawer for the dataset catalog with nested facets and persistent selections.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Bump uv.lock's ruff version to 0.12.5.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Assess whether our current S3 multipart cleanup job can delete an upload that is still receiving parts.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Plan the retirement of our shared production Kubernetes cluster. Address workload inventory, dependency mapping, namespace ownership, data-plane migration, ingress cutover, IP allowlists, observability continuity, cost, rollback windows, and final decommission evidence.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Plan the retirement of our shared production Kubernetes cluster. Address workload inventory, dependency mapping, namespace ownership, data-plane migration, ingress cutover, IP allowlists, observability continuity, cost, rollback windows, and final decommission evidence.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} {"prompt":"Write a concise incident-response checklist for compromised package-registry credentials.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Extract Terraform resource naming into a shared module without changing any existing resource addresses or plans.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"The Python data loader produces different sample orders after resuming from the same checkpoint. Determine which RNG state is missing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Ticket MLPLAT-1931\n\nFeature: reproducible training manifests\nToday, the scheduler stores a free-form JSON config and the image tag. Re-running a six-month-old experiment may resolve different datasets, packages, and feature definitions.\n\nThe manifest must capture:\n- immutable container digest\n- source commit and dirty status\n- dataset versions plus snapshot timestamps\n- feature-view revisions\n- Python lockfile hash\n- secret names, but never secret values\n- hardware class and distributed-training topology\n- scheduler defaults after expansion\n\nResearchers need to clone a manifest with explicitly listed overrides. Compliance requires manifests for regulated projects to remain queryable for seven years. Some historical runs lack several fields. Design the schema, APIs, storage lifecycle, compatibility behavior, and staged rollout. Include integrity guarantees and how the UI should communicate unreproducible legacy runs. Planning deliverable only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Backend story OBS-441\n\nWe receive OpenTelemetry traces through a Go collector extension. A new customer needs tail sampling based on final HTTP status, total duration, and whether any span contains exception.type. Implement a bounded-memory sampler with these rules:\n- retain traces for at most 20 seconds\n- always keep errors and traces slower than tenant threshold\n- probabilistically sample the remainder using tenant rate\n- late spans after decision are counted and dropped\n- enforce per-tenant and global memory limits\n- emit decision reason, buffered span count, evictions, and late-span metrics\n- configuration reload must not discard buffered traces\n- decisions for one trace must be deterministic across replicas when all spans reach one replica\n\nUse the extension points in collector/tailsample and add load plus property tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"The Python data loader produces different sample orders after resuming from the same checkpoint. Determine which RNG state is missing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Ticket MLPLAT-1931\n\nFeature: reproducible training manifests\nToday, the scheduler stores a free-form JSON config and the image tag. Re-running a six-month-old experiment may resolve different datasets, packages, and feature definitions.\n\nThe manifest must capture:\n- immutable container digest\n- source commit and dirty status\n- dataset versions plus snapshot timestamps\n- feature-view revisions\n- Python lockfile hash\n- secret names, but never secret values\n- hardware class and distributed-training topology\n- scheduler defaults after expansion\n\nResearchers need to clone a manifest with explicitly listed overrides. Compliance requires manifests for regulated projects to remain queryable for seven years. Some historical runs lack several fields. Design the schema, APIs, storage lifecycle, compatibility behavior, and staged rollout. Include integrity guarantees and how the UI should communicate unreproducible legacy runs. Planning deliverable only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"core","lang":"en"} +{"prompt":"Backend story OBS-441\n\nWe receive OpenTelemetry traces through a Go collector extension. A new customer needs tail sampling based on final HTTP status, total duration, and whether any span contains exception.type. Implement a bounded-memory sampler with these rules:\n- retain traces for at most 20 seconds\n- always keep errors and traces slower than tenant threshold\n- probabilistically sample the remainder using tenant rate\n- late spans after decision are counted and dropped\n- enforce per-tenant and global memory limits\n- emit decision reason, buffered span count, evictions, and late-span metrics\n- configuration reload must not discard buffered traces\n- decisions for one trace must be deterministic across replicas when all spans reach one replica\n\nUse the extension points in collector/tailsample and add load plus property tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"UI ticket pasted from Slack:\n\nNora: the cost explorer needs a proper compare mode before finance review\nAli: baseline period and comparison period should each be selectable, but prevent overlap\nNora: cards show absolute cost, delta dollars, and delta percent\nAli: positive spend delta is visually negative, so don't reuse success green\nNora: chart can toggle daily/weekly and stacked/service views\nAli: clicking a service filters the table, clicking again clears it\nNora: on narrow screens move controls into a sheet; table becomes ranked cards\nAli: loading either period should not blank the other one\nNora: include a text alternative summarizing the largest increases and decreases\n\nImplement compare mode in CostExplorer.tsx using the existing useCostSeries queries. Backend fields already exist. Match current design tokens and keyboard patterns.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} {"prompt":"Failure captured from production:\n\n2026-07-29T03:14:51.990Z allocator INFO desired=18 current=12 pending=6\n2026-07-29T03:14:52.041Z cloud_api WARN create returned 409 instance_name=gpu-pool-a-0013\n2026-07-29T03:14:52.042Z allocator INFO retrying request attempt=1 delay=250ms\n2026-07-29T03:14:52.301Z cloud_api INFO create accepted operation=op-7731\n2026-07-29T03:14:52.305Z allocator INFO desired=18 current=12 pending=5\n2026-07-29T03:15:07.814Z reconciler WARN orphan instance discovered name=gpu-pool-a-0013 labels={}\n\nAfter this sequence, the autoscaler permanently believes one capacity slot exists, but the orphan is never assigned or deleted. The 409 happens when a recently deleted cloud name remains reserved. Determine how pending accounting diverges, fix reconciliation safely, and cover delayed-name-reuse behavior.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Review the current feature materialization path and tell me where training-serving skew can enter. No modifications.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Review the current feature materialization path and tell me where training-serving skew can enter. No modifications.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Set enableServiceLinks to false.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Combine the duplicate DAG validation passes while keeping diagnostics and traversal order identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Combine the duplicate DAG validation passes while keeping diagnostics and traversal order identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Escreva um guia de troubleshooting para falhas de autenticação no registry interno, com comandos de diagnóstico seguros.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"pt"} {"prompt":"The browser's memory climbs whenever users switch between large trace waterfalls, even after tabs close. Identify the retained canvas or worker state.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Build the Qwik alert-rule editor with condition groups, expression previews, and inline validation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} @@ -8047,34 +7850,32 @@ {"prompt":"Add retention-policy enforcement to the object catalog and write customer-facing documentation for expiration behavior.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Implement the Kubernetes resource topology view and the aggregation endpoint it needs for large clusters.","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Update the stale feature flag name in one workflow and add a release-note sentence about the correction.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.2,"slice":"mixed","lang":"en"} -{"prompt":"Restructure the alert evaluator into parsing and execution stages without behavior changes, then update its maintainer notes.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Find why batch predictions occasionally omit their final shard, fix it, and document the recovered edge case for operators.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Restructure the alert evaluator into parsing and execution stages without behavior changes, then update its maintainer notes.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Find why batch predictions occasionally omit their final shard, fix it, and document the recovered edge case for operators.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Analyze the current Terraform provider upgrade process for supply-chain risk, then draft a safer migration roadmap.","purpose":"review","secondary":"planning","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Inspect the query planner code and write an architecture note explaining cost estimation and fallback behavior.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Build a Python API for registering evaluation datasets with immutable versions, checksums, lineage, and role-based access.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Inspect the query planner code and write an architecture note explaining cost estimation and fallback behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Build a Python API for registering evaluation datasets with immutable versions, checksums, lineage, and role-based access.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Implement the keyboard-first command palette for our observability console, including fuzzy results and recent actions.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Change the dev port to 4174.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Explain whether the existing Redis cluster client can return stale reads immediately after slot migration.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Explain whether the existing Redis cluster client can return stale reads immediately after slot migration.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Design a provenance system for generated container images. Account for source identity, hermetic builds, SBOMs, attestations, keyless signing, promotion across environments, air-gapped verification, revocation, retention, and an incremental rollout that does not block emergency patches.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Write a release announcement for the new regional data-residency controls, including limitations and migration actions.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Write a release announcement for the new regional data-residency controls, including limitations and migration actions.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Extract cloud-provider-specific instance discovery behind interfaces while preserving reconciliation timing and metrics.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"One dbt snapshot updates every row nightly although source hashes remain stable. Determine which generated value changes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Plan a multi-account AWS network architecture for isolating training, inference, data processing, and shared services. Cover routing, private service access, centralized egress, DNS, inspection, blast radius, quota ownership, migration from the flat VPC, and a recovery path if the transit layer fails.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"boundary","lang":"en"} -{"prompt":"Add examples to the policy-language reference and implement the new contains_any operator those examples describe.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Give the empty chart state a useful visual hierarchy and an action to clear filters.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"Replace truee with true in flags.yaml.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Rename clusterClass to capacityClass across the control plane while retaining the old JSON and CLI aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Why does our cost report disagree with the cloud invoice only for spot-instance credits? Identify the unknown accounting error.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Walk me through why the current log shipper fsyncs before advancing its cursor. Assume the implementation is healthy.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"把现有的 dataset versioning 代码整理成一篇面向开发者的说明文档，不需要改实现。","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"zh"} -{"prompt":"keep going with the migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} -{"prompt":"build out that worker","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"One dbt snapshot updates every row nightly although source hashes remain stable. Determine which generated value changes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Plan a multi-account AWS network architecture for isolating training, inference, data processing, and shared services. Cover routing, private service access, centralized egress, DNS, inspection, blast radius, quota ownership, migration from the flat VPC, and a recovery path if the transit layer fails.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add examples to the policy-language reference and implement the new contains_any operator those examples describe.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Give the empty chart state a useful visual hierarchy and an action to clear filters.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Replace truee with true in flags.yaml.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename clusterClass to capacityClass across the control plane while retaining the old JSON and CLI aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Why does our cost report disagree with the cloud invoice only for spot-instance credits? Identify the unknown accounting error.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Walk me through why the current log shipper fsyncs before advancing its cursor. Assume the implementation is healthy.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"把现有的 dataset versioning 代码整理成一篇面向开发者的说明文档，不需要改实现。","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"zh"} {"prompt":"make the dashboard nicer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"quick yaml cleanup","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} -{"prompt":"figure out the flaky thing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"check the pipeline logic","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"write up what we have","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"Implement a temporal join operator for the internal streaming engine, including late-data handling and checkpoint restoration.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"quick yaml cleanup","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"figure out the flaky thing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"check the pipeline logic","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"write up what we have","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Implement a temporal join operator for the internal streaming engine, including late-data handling and checkpoint restoration.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Create the React resource-usage treemap with zoom breadcrumbs, stable colors, and screen-reader summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Pin golangci-lint to v2.3.0.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Evaluate whether the current MLflow artifact proxy prevents path traversal in nested artifact names.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} @@ -8082,305 +7883,301 @@ {"prompt":"既存の autoscaler を運用するための runbook を書いて。主要メトリクス、よくある障害、復旧手順を含めてください。","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"ja"} {"prompt":"Separate query parsing from execution in the metrics gateway with no changes to accepted syntax or returned errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"A Ray cluster marks actors healthy while their pods are stuck terminating, so replacements never launch. Find the state mismatch.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Architecture request from the reliability review:\n\nOur internal package mirror depends on one regional object bucket, one PostgreSQL catalog, and a stateless metadata API. Builds in five regions fetch through local caching proxies. During the last outage, expired proxy entries caused every region to stampede the unavailable origin. Engineers bypassed the mirror, which broke provenance tracking. Security requires malware scanning before a package becomes visible and immediate quarantine when a later scan revokes it. Existing package URLs cannot change for two years.\n\nDesign a highly available mirror architecture and migration roadmap. Cover cache consistency, origin failover, catalog replication, upload sequencing, quarantine propagation, offline build policy, provenance, stampede controls, SLOs, disaster exercises, and phased rollout without changing current client URLs. No code requested.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Story DATA-1207: privacy deletion propagation\n\nThe TypeScript privacy service accepts deletion requests but currently stops after deleting the primary PostgreSQL profile. Implement coordinated deletion across:\n- PostgreSQL profile and preferences\n- ClickHouse analytics rows\n- S3 export objects\n- Redis personalization cache\n- feature-store online and offline entries\n\nRequirements:\n- durable per-system state machine\n- idempotent retries for 30 days\n- distinguish verified absence from temporary verification failure\n- cap concurrent ClickHouse mutations\n- preserve a minimal legally approved receipt with hashed subject id\n- expose progress to support without revealing deleted data\n- page after 24 hours and escalate after 21 days\n- support dry-run inventory for internal audits\n\nUse Temporal workflows already configured in services/privacy. Add failure-injection tests for every external system and migration handling for in-flight requests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Frontend brief from the model-registry team:\n\nPage: ModelVersionCompare\nInputs: two model-version ids already loaded by compareLoader\nSections:\n- metadata differences\n- training parameters with changed rows pinned first\n- dataset lineage side by side\n- evaluation metrics with relative deltas\n- downloadable artifact inventory\n\nProduct notes:\nMissing values must look different from unchanged values. Long JSON parameters need expandable syntax-highlighted cells. Users should be able to copy a deep link to one section. On mobile, switch from columns to labeled before/after blocks. A sticky summary should show counts of changed, added, and removed fields. Metric increases are not always good; use the metric definition's higherIsBetter field. Maintain visible keyboard focus and supply non-color indicators.\n\nBuild the comparison UI using the existing loader data and design system.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Intermittent failure from CI:\n\nFAILED tests/integration/test_registry_gc.py::test_upload_racing_with_gc\nE AssertionError: expected blob sha256:0a91... to exist\nE assert 404 == 200\nCaptured worker logs:\ngc mark complete generation=188 reachable=18423\nupload committed manifest=model-x:v17 blob=sha256:0a91 generation=188\nsweep deleting blob=sha256:0a91 last_seen_generation=187\nregistry manifest read model-x:v17 -> 200\nregistry blob read sha256:0a91 -> 404\n\nThe failure appears about once per 300 runs and became more frequent after GC marking moved to a read replica. Transactions are PostgreSQL repeatable-read; object deletion is asynchronous. Determine the race, fix it without pausing uploads for the whole collection cycle, and add a deterministic regression test.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Change cacheTtlSec to cacheTTLSeconds in one local helper.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Architecture request from the reliability review:\n\nOur internal package mirror depends on one regional object bucket, one PostgreSQL catalog, and a stateless metadata API. Builds in five regions fetch through local caching proxies. During the last outage, expired proxy entries caused every region to stampede the unavailable origin. Engineers bypassed the mirror, which broke provenance tracking. Security requires malware scanning before a package becomes visible and immediate quarantine when a later scan revokes it. Existing package URLs cannot change for two years.\n\nDesign a highly available mirror architecture and migration roadmap. Cover cache consistency, origin failover, catalog replication, upload sequencing, quarantine propagation, offline build policy, provenance, stampede controls, SLOs, disaster exercises, and phased rollout without changing current client URLs. No code requested.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Story DATA-1207: privacy deletion propagation\n\nThe TypeScript privacy service accepts deletion requests but currently stops after deleting the primary PostgreSQL profile. Implement coordinated deletion across:\n- PostgreSQL profile and preferences\n- ClickHouse analytics rows\n- S3 export objects\n- Redis personalization cache\n- feature-store online and offline entries\n\nRequirements:\n- durable per-system state machine\n- idempotent retries for 30 days\n- distinguish verified absence from temporary verification failure\n- cap concurrent ClickHouse mutations\n- preserve a minimal legally approved receipt with hashed subject id\n- expose progress to support without revealing deleted data\n- page after 24 hours and escalate after 21 days\n- support dry-run inventory for internal audits\n\nUse Temporal workflows already configured in services/privacy. Add failure-injection tests for every external system and migration handling for in-flight requests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Frontend brief from the model-registry team:\n\nPage: ModelVersionCompare\nInputs: two model-version ids already loaded by compareLoader\nSections:\n- metadata differences\n- training parameters with changed rows pinned first\n- dataset lineage side by side\n- evaluation metrics with relative deltas\n- downloadable artifact inventory\n\nProduct notes:\nMissing values must look different from unchanged values. Long JSON parameters need expandable syntax-highlighted cells. Users should be able to copy a deep link to one section. On mobile, switch from columns to labeled before/after blocks. A sticky summary should show counts of changed, added, and removed fields. Metric increases are not always good; use the metric definition's higherIsBetter field. Maintain visible keyboard focus and supply non-color indicators.\n\nBuild the comparison UI using the existing loader data and design system.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Intermittent failure from CI:\n\nFAILED tests/integration/test_registry_gc.py::test_upload_racing_with_gc\nE AssertionError: expected blob sha256:0a91... to exist\nE assert 404 == 200\nCaptured worker logs:\ngc mark complete generation=188 reachable=18423\nupload committed manifest=model-x:v17 blob=sha256:0a91 generation=188\nsweep deleting blob=sha256:0a91 last_seen_generation=187\nregistry manifest read model-x:v17 -> 200\nregistry blob read sha256:0a91 -> 404\n\nThe failure appears about once per 300 runs and became more frequent after GC marking moved to a read replica. Transactions are PostgreSQL repeatable-read; object deletion is asynchronous. Determine the race, fix it without pausing uploads for the whole collection cycle, and add a deterministic regression test.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Change cacheTtlSec to cacheTTLSeconds in one local helper.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} {"prompt":"Unify the duplicated histogram bucket parsers without altering defaults or validation messages.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Read the cluster drain controller and explain what prevents it from evicting quorum-critical pods.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Read the cluster drain controller and explain what prevents it from evicting quorum-critical pods.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Write customer-facing instructions for exporting audit logs into Splunk using the existing HEC integration.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Implement an append-only audit store in Go with hash chaining, periodic checkpoints, tenant partitioning, and verification tooling.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Build the responsive SLO editor with burn-rate previews, multi-window conditions, and an accessible expression summary.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement an append-only audit store in Go with hash chaining, periodic checkpoints, tenant partitioning, and verification tooling.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Build the responsive SLO editor with burn-rate previews, multi-window conditions, and an accessible expression summary.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Remove the unused experimental flag.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Review the current Vault token-renewal loop and assess behavior during leader failover and clock jumps.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Review the current Vault token-renewal loop and assess behavior during leader failover and clock jumps.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Plan a federated data-catalog architecture for independently operated business units. Address identity, ownership, schema discovery, lineage exchange, policy enforcement, regional metadata, search relevance, stale registrations, interoperability, governance, and migration from the centralized catalog.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Prepare a migration tutorial for converting Prometheus recording rules into our new MetricsQL rule format.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Prepare a migration tutorial for converting Prometheus recording rules into our new MetricsQL rule format.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Replace inheritance in the Java connector framework with composition while preserving plugin APIs and runtime behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"A cron-triggered Airflow DAG skips the first partition after every scheduler restart. Find the timetable or state bug.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Architect the transition from public webhook endpoints to private connectivity for regulated customers. Provide options, tradeoffs, milestones, compatibility strategy, and operational ownership; don't implement it.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Expand the CLI reference with a restore command and implement that command against the existing snapshot API.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Center the loading spinner inside the chart's plot area rather than the full card.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} -{"prompt":"Fix the stray slash in the registry URL.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Rename masterDataset to canonicalDataset throughout the monorepo, keeping stored JSON keys backward compatible.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Warum schlagen Uploads nur nach einem Nginx reload mit 499 fehl? Die Ursache ist noch unklar; bitte diagnostizieren.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"de"} -{"prompt":"Assess whether the existing dataset import path validates checksums before or after decompression, and explain the security implications. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Summarize the current quota evaluator as a public API concepts page, without proposing implementation changes.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Implement a deterministic sharding library for assigning tenants to ingestion workers with minimal movement during scaling.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Create the animated connection-state banner for the realtime console, including offline and reconnecting modes.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Architect the transition from public webhook endpoints to private connectivity for regulated customers. Provide options, tradeoffs, milestones, compatibility strategy, and operational ownership; don't implement it.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Expand the CLI reference with a restore command and implement that command against the existing snapshot API.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Center the loading spinner inside the chart's plot area rather than the full card.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Fix the stray slash in the registry URL.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename masterDataset to canonicalDataset throughout the monorepo, keeping stored JSON keys backward compatible.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Warum schlagen Uploads nur nach einem Nginx reload mit 499 fehl? Die Ursache ist noch unklar; bitte diagnostizieren.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"de"} +{"prompt":"Assess whether the existing dataset import path validates checksums before or after decompression, and explain the security implications. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Summarize the current quota evaluator as a public API concepts page, without proposing implementation changes.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Implement a deterministic sharding library for assigning tenants to ingestion workers with minimal movement during scaling.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create the animated connection-state banner for the realtime console, including offline and reconnecting modes.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Set retentionDays to 30.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Examine our current cosine-similarity implementation and verify that zero vectors, NaNs, and SIMD reduction are handled safely.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Create a two-year roadmap for making the internal developer platform self-service. Include product boundaries, golden paths, extension points, scorecards, adoption sequencing, staffing assumptions, cost controls, governance, and metrics that distinguish real developer-time savings from portal usage.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Draft release notes for the new autoscaling policies based on merged changes and operator-visible behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Draft release notes for the new autoscaling policies based on merged changes and operator-visible behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Split the React query builder's state machine from its rendering code without changing interactions or serialized queries.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"The Redis-backed semaphore sometimes grants more permits than configured after a client timeout. Reconstruct the interleaving and find the bug.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Design tenant-aware cache invalidation, then implement the event consumer and guarded rollout metrics.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Add server-side saved searches and build their management panel in the data catalog.","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Create the incident timeline UI and implement the cursor-paginated events endpoint it consumes.","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Diagnose the missing OpenTelemetry spans, fix propagation, and write a short integration note for downstream services.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Switch the typoed env key and restart note.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Add server-side saved searches and build their management panel in the data catalog.","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Create the incident timeline UI and implement the cursor-paginated events endpoint it consumes.","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Diagnose the missing OpenTelemetry spans, fix propagation, and write a short integration note for downstream services.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Switch the typoed env key and restart note.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.2,"slice":"mixed","lang":"en"} {"prompt":"Extract shared pagination logic from the REST clients while keeping requests and iteration order unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Audit the current signed-URL validation code for confused-deputy and canonicalization issues. Do not patch it.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write a concise ADR explaining the decision to keep inference request logs for seven days.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Create a gRPC service in Kotlin for managing training reservations, including optimistic concurrency and quota enforcement.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Write a concise ADR explaining the decision to keep inference request logs for seven days.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Create a gRPC service in Kotlin for managing training reservations, including optimistic concurrency and quota enforcement.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Build the Lit-based log viewer with virtual scrolling, search highlights, wrapping controls, and ANSI color support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Change 60s to 90s in probe.yaml.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Review how the existing backup catalog handles two snapshots with the same logical timestamp.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Plan a safe migration of 600 TB of Iceberg tables from one object-store account to another while queries and daily compaction continue. Cover catalog updates, file references, bandwidth throttling, integrity verification, encryption keys, rollback boundaries, stale readers, regional transfer cost, and final deletion controls.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} -{"prompt":"Écris un guide d'intégration pour le nouveau endpoint de batch inference, avec exemples curl, limites et codes d'erreur.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"fr"} +{"prompt":"Review how the existing backup catalog handles two snapshots with the same logical timestamp.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Plan a safe migration of 600 TB of Iceberg tables from one object-store account to another while queries and daily compaction continue. Cover catalog updates, file references, bandwidth throttling, integrity verification, encryption keys, rollback boundaries, stale readers, regional transfer cost, and final deletion controls.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1,"slice":"core","lang":"en"} +{"prompt":"Écris un guide d'intégration pour le nouveau endpoint de batch inference, avec exemples curl, limites et codes d'erreur.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"fr"} {"prompt":"Collapse the duplicate metrics registration layers without changing names, labels, or initialization timing.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"The vector index occasionally returns an item excluded by its metadata filter. Find whether filtering, compaction, or stale segments are responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Develop an adoption plan for policy-as-code across infrastructure repositories. Include policy ownership, exceptions, testing, local feedback, enforcement stages, legacy-resource handling, audit evidence, and success measures. The deliverable should be a roadmap, not policy files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Update the REST reference to describe cursor expiry and implement expiry enforcement in the pagination token decoder.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Make the selected table row easier to distinguish without relying on color alone.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"The vector index occasionally returns an item excluded by its metadata filter. Find whether filtering, compaction, or stale segments are responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Develop an adoption plan for policy-as-code across infrastructure repositories. Include policy ownership, exceptions, testing, local feedback, enforcement stages, legacy-resource handling, audit evidence, and success measures. The deliverable should be a roadmap, not policy files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Update the REST reference to describe cursor expiry and implement expiry enforcement in the pagination token decoder.","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Make the selected table row easier to distinguish without relying on color alone.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Rename one CSS variable from --grey-90 to --gray-90.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Replace worker terminology with executor across all internal packages while preserving public config and telemetry names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Why do deleted Kubernetes finalizers return after reconciliation? Determine which controller is writing stale state.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Explain why the current feature cache stores missing values explicitly instead of omitting them. No behavior is known to be wrong.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Convert the existing disaster-recovery scripts into a readable operator procedure, without changing or evaluating their behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Replace worker terminology with executor across all internal packages while preserving public config and telemetry names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Why do deleted Kubernetes finalizers return after reconciliation? Determine which controller is writing stale state.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Explain why the current feature cache stores missing values explicitly instead of omitting them. No behavior is known to be wrong.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Convert the existing disaster-recovery scripts into a readable operator procedure, without changing or evaluating their behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Implement a bounded concurrent crawler in Go for discovering internal OpenAPI specifications, with robots-style exclusions and retry budgets.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Build the dataset-permission matrix UI with sticky headers, bulk selection, and clear inherited-state indicators.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Enable gzip in the dev proxy.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Inspect the existing OPA bundle downloader for rollback protection and partial-download handling.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Enable gzip in the dev proxy.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Inspect the existing OPA bundle downloader for rollback protection and partial-download handling.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Map out a transition from per-service cron jobs to a centrally governed workflow platform. Address tenancy, scheduling semantics, secrets, backfills, observability, ownership, cost, migration order, escape hatches, and what remains intentionally service-local.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Write a README section describing how to reproduce benchmark results on supported GPU types.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Extract common OAuth token parsing into one library while keeping service-specific validation and error behavior unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Our WebAssembly transform produces corrupt output only when input spans a 64 KiB memory boundary. Locate the addressing error.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Our WebAssembly transform produces corrupt output only when input spans a 64 KiB memory boundary. Locate the addressing error.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"sort out the platform direction","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} -{"prompt":"finish up the ingestion piece","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"Create the dark-mode palette preview in the design-system docs, including contrast badges and token search.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"finish up the ingestion piece","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Create the dark-mode palette preview in the design-system docs, including contrast badges and token search.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Change the typo in CACHE_DRIver.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Separate model-registry storage from its HTTP handlers without changing routes, transactions, or errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Shard rebalancing stalls at 99% with no errors when one worker leaves mid-transfer. Find the unfulfilled completion condition.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Review the current JWT key-selection logic and determine how it behaves when two keys share a kid.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Escribe una guía breve para interpretar los nuevos dashboards de latencia y sus alertas de burn rate.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} -{"prompt":"Design a secure OTA update architecture for battery-powered sensor nodes that may remain offline for a year. Cover signed firmware, delta updates, anti-rollback, staged cohorts, boot failure recovery, constrained flash, compromised keys, telemetry, and manufacturing-time provisioning.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Implement logical-decoding ingestion in Rust that persists PostgreSQL row changes to partitioned object storage with resumable offsets.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Build the Jetpack Compose device-detail screen with live sensor cards, connection state, alert history, and tablet layout.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Shard rebalancing stalls at 99% with no errors when one worker leaves mid-transfer. Find the unfulfilled completion condition.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Review the current JWT key-selection logic and determine how it behaves when two keys share a kid.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Escribe una guía breve para interpretar los nuevos dashboards de latencia y sus alertas de burn rate.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"es"} +{"prompt":"Design a secure OTA update architecture for battery-powered sensor nodes that may remain offline for a year. Cover signed firmware, delta updates, anti-rollback, staged cohorts, boot failure recovery, constrained flash, compromised keys, telemetry, and manufacturing-time provisioning.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"core","lang":"en"} +{"prompt":"Implement logical-decoding ingestion in Rust that persists PostgreSQL row changes to partitioned object storage with resumable offsets.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.85,"slice":"core","lang":"en"} +{"prompt":"Build the Jetpack Compose device-detail screen with live sensor cards, connection state, alert history, and tablet layout.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Change the SPI clock to 8 MHz.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Extract the duplicated I2C transaction state machines into one driver without changing timing, retries, or error codes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Recorded accelerometer samples become byte-shifted after the DMA buffer wraps. Determine whether the descriptor chain or cache coherency is wrong.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Review storage/btree/page_split.c and explain whether its separator-key rules hold for variable-length keys.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write a board-bring-up guide for the Rev C controller, including flashing, serial diagnostics, and expected power rails.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Recorded accelerometer samples become byte-shifted after the DMA buffer wraps. Determine whether the descriptor chain or cache coherency is wrong.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Review storage/btree/page_split.c and explain whether its separator-key rules hold for variable-length keys.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Write a board-bring-up guide for the Rev C controller, including flashing, serial diagnostics, and expected power rails.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Plan the migration of our iOS persistence layer from Core Data to SwiftData. Include schema compatibility, CloudKit synchronization, staged rollout, rollback, background imports, test strategy, and treatment of stores created by older app versions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Add a SQLite virtual table extension that exposes compressed telemetry blocks as timestamped rows.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Create the SwiftUI medication schedule with expandable days, missed-dose badges, Dynamic Type, and VoiceOver actions.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Set SWIFT_STRICT_CONCURRENCY to complete.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Move database observation logic out of three view models into a shared repository while preserving published UI states.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"O app iOS às vezes perde alterações feitas offline depois do login. Descubra qual merge ou troca de conta está descartando os dados.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"pt"} -{"prompt":"Assess whether the current SQLite migration sequence remains safe when an app is killed between versions 17 and 18.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Assess whether the current SQLite migration sequence remains safe when an app is killed between versions 17 and 18.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Draft App Store release notes for the redesigned offline maps and reduced download size.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Produce a rollout plan for adding biometric approval to mobile wire transfers. Deliver threat decisions, fallback rules, milestones, observability, and recovery procedures—not UI or server code.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Update the SQL schema comments for device leases and implement the lease-renewal transaction they describe.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Increase the selected tab's underline thickness and animate it between tabs.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"Move the close icon 2px left.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Rename peripheralId to deviceId across the mobile SDK while keeping serialized keys and public compatibility aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Why does the settings sheet dismiss itself on iPad after a Bluetooth scan completes? Find the unknown state interaction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Explain why the current firmware journal writes a commit marker to a separate flash page. Assume recovery works correctly.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Turn the existing database encryption implementation into a customer-facing security overview without proposing changes.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Architect a local-first notes database supporting rich-text blocks, attachments, shared notebooks, and multiple devices. Address identifiers, operation ordering, conflict semantics, tombstones, compaction, encryption, attachment transfer, partial synchronization, schema evolution, and a migration from the current last-write-wins document model.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Produce a rollout plan for adding biometric approval to mobile wire transfers. Deliver threat decisions, fallback rules, milestones, observability, and recovery procedures—not UI or server code.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Update the SQL schema comments for device leases and implement the lease-renewal transaction they describe.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Increase the selected tab's underline thickness and animate it between tabs.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Move the close icon 2px left.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename peripheralId to deviceId across the mobile SDK while keeping serialized keys and public compatibility aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Why does the settings sheet dismiss itself on iPad after a Bluetooth scan completes? Find the unknown state interaction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Explain why the current firmware journal writes a commit marker to a separate flash page. Assume recovery works correctly.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Turn the existing database encryption implementation into a customer-facing security overview without proposing changes.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Architect a local-first notes database supporting rich-text blocks, attachments, shared notebooks, and multiple devices. Address identifiers, operation ordering, conflict semantics, tombstones, compaction, encryption, attachment transfer, partial synchronization, schema evolution, and a migration from the current last-write-wins document model.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} {"prompt":"Implement a Go service that assigns monotonic sequence ranges to database writers without making every write depend on consensus.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Build the Flutter Bluetooth pairing flow with scanning, permission education, PIN entry, retry states, and screen-reader support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Bump the database schema version to 42.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Separate WAL serialization from file I/O while keeping the on-disk format and fsync ordering identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"The Android process deadlocks during Room database initialization only after restoring an encrypted backup. Locate the lock inversion.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"请检查现有的 MVCC 可见性判断，解释长事务期间 vacuum 为什么不会删除仍需要的版本。不要修改代码。","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"请检查现有的 MVCC 可见性判断，解释长事务期间 vacuum 为什么不会删除仍需要的版本。不要修改代码。","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"zh"} {"prompt":"Write the migration guide for consumers moving from integer device IDs to UUIDs in SDK 5.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Architecture notes from the hardware sync:\n\nProduct: environmental gateway, STM32H7, 2 MiB internal flash, external QSPI available but not populated on every SKU. The current bootloader stores one application image and enters DFU after a failed checksum. New requirements are signed remote updates, automatic rollback after three failed boots, staged rollout by hardware revision, and support for devices offline for up to eighteen months. Cellular customers pay per byte. Manufacturing currently flashes a shared development certificate that must be replaced. Field technicians need a USB recovery path. Secure-element inventory is available only for premium SKUs.\n\nDesign the boot chain, image layout, key hierarchy, anti-rollback scheme, update protocol, recovery states, and manufacturing migration. Include tradeoffs for devices without external flash and a phased validation plan. No code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"pasted-context","lang":"en"} -{"prompt":"Issue DB-712: resumable index creation\n\nOur embedded database builds secondary indexes in one transaction. Large mobile stores may spend twenty minutes rebuilding after a schema migration, and an app kill restarts from zero. Implement resumable construction with these constraints:\n- readers continue using the table without the incomplete index\n- writes during construction must be reflected before activation\n- progress survives process termination\n- temporary state is removed after rollback\n- index becomes visible atomically\n- corruption detection uses existing page checksums\n- disk overhead remains below 1.5x table size\n- old application versions must ignore construction metadata safely\n- tests should inject crashes after every persistent-state transition\n\nRelevant code is engine/index/build.rs and engine/catalog/schema.rs. Preserve the current index file format if possible.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Mobile design ticket:\n\nScreen: IndoorMapView in the Android warehouse app\nData already available: floor-plan bitmap, worker position, pick stops, restricted polygons, and route polyline\n\nExpected behavior:\n- pinch to zoom around gesture centroid\n- double tap zooms one level\n- follow mode keeps the worker centered until the user pans\n- current pick stop gets a pulsing ring, disabled under Reduce Motion\n- restricted zones use both hatching and color\n- route line remains readable over dark and light floor plans\n- a recenter button appears only after follow mode disengages\n- TalkBack users get a linear list of stops and distances\n- landscape tablets reserve a side panel for stop details\n\nImplement the Compose UI and gestures using the existing IndoorMapState. Do not change route calculation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Approved firmware change:\n\nThe product team confirmed that the status LED should remain illuminated for 250 ms rather than 100 ms after a successful NFC scan. This is a constant-only adjustment.\n\nFile: firmware/ui/status_led.c\nCurrent line:\n#define NFC_SUCCESS_HOLD_MS 100\nRequired line:\n#define NFC_SUCCESS_HOLD_MS 250\n\nDo not change the failure pattern, PWM brightness, low-battery behavior, test tolerances, or any other timing constant. The hardware validation for 250 ms is already complete. Apply this exact change and leave formatting untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"pasted-context","lang":"en"} -{"prompt":"Cleanup request from the storage team:\n\nThree page types implement nearly identical checksum handling:\n- BTreeLeafPage\n- BTreeInternalPage\n- OverflowPage\n\nEach implementation zeros the checksum field, hashes the encoded page, stores the little-endian result, and verifies it during decode. Error strings and corruption counters differ by page type and are asserted by tests. OverflowPage hashes only used payload bytes; B-tree pages hash the entire fixed-size page. The serialized format is already deployed in millions of mobile databases and cannot change. Extract shared internal checksum mechanics while preserving byte layout, hashed ranges, page-specific messages, counters, and decode ordering. Do not introduce virtual dispatch or allocations in the hot path. Benchmark results should remain within noise.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Issue DB-712: resumable index creation\n\nOur embedded database builds secondary indexes in one transaction. Large mobile stores may spend twenty minutes rebuilding after a schema migration, and an app kill restarts from zero. Implement resumable construction with these constraints:\n- readers continue using the table without the incomplete index\n- writes during construction must be reflected before activation\n- progress survives process termination\n- temporary state is removed after rollback\n- index becomes visible atomically\n- corruption detection uses existing page checksums\n- disk overhead remains below 1.5x table size\n- old application versions must ignore construction metadata safely\n- tests should inject crashes after every persistent-state transition\n\nRelevant code is engine/index/build.rs and engine/catalog/schema.rs. Preserve the current index file format if possible.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Mobile design ticket:\n\nScreen: IndoorMapView in the Android warehouse app\nData already available: floor-plan bitmap, worker position, pick stops, restricted polygons, and route polyline\n\nExpected behavior:\n- pinch to zoom around gesture centroid\n- double tap zooms one level\n- follow mode keeps the worker centered until the user pans\n- current pick stop gets a pulsing ring, disabled under Reduce Motion\n- restricted zones use both hatching and color\n- route line remains readable over dark and light floor plans\n- a recenter button appears only after follow mode disengages\n- TalkBack users get a linear list of stops and distances\n- landscape tablets reserve a side panel for stop details\n\nImplement the Compose UI and gestures using the existing IndoorMapState. Do not change route calculation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Approved firmware change:\n\nThe product team confirmed that the status LED should remain illuminated for 250 ms rather than 100 ms after a successful NFC scan. This is a constant-only adjustment.\n\nFile: firmware/ui/status_led.c\nCurrent line:\n#define NFC_SUCCESS_HOLD_MS 100\nRequired line:\n#define NFC_SUCCESS_HOLD_MS 250\n\nDo not change the failure pattern, PWM brightness, low-battery behavior, test tolerances, or any other timing constant. The hardware validation for 250 ms is already complete. Apply this exact change and leave formatting untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Cleanup request from the storage team:\n\nThree page types implement nearly identical checksum handling:\n- BTreeLeafPage\n- BTreeInternalPage\n- OverflowPage\n\nEach implementation zeros the checksum field, hashes the encoded page, stores the little-endian result, and verifies it during decode. Error strings and corruption counters differ by page type and are asserted by tests. OverflowPage hashes only used payload bytes; B-tree pages hash the entire fixed-size page. The serialized format is already deployed in millions of mobile databases and cannot change. Extract shared internal checksum mechanics while preserving byte layout, hashed ranges, page-specific messages, counters, and decode ordering. Do not introduce virtual dispatch or allocations in the hot path. Benchmark results should remain within noise.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Crash report from iPhone 18 Pro:\n\nException Type: EXC_BAD_ACCESS (SIGSEGV)\nException Subtype: KERN_INVALID_ADDRESS at 0x0000000000000010\nThread 11 Crashed:\n0 libswiftCore.dylib swift_retain\n1 TrailSync SyncBatch.deinit + 44\n2 TrailSync UploadCoordinator.finish(batch:) + 188\n3 TrailSync closure #2 in UploadCoordinator.start() + 96\n4 libswift_Concurrency completeTaskWithClosure\n\nBreadcrumbs:\n09:17:03 app entered background\n09:17:04 background upload task completed\n09:17:04 account signed out by MDM policy\n09:17:04 pending batch store cleared\n09:17:05 crash\n\nIt reproduces rarely when sign-out and a background URLSession callback overlap. Diagnose the ownership or actor-isolation bug and fix it without retaining user data after sign-out.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Review request, no edits:\n\nThe key-value engine uses 32-bit page numbers. Page zero stores two alternating meta records; each contains root page, freelist head, transaction id, and checksum. Writers copy modified pages, fsync the data file, write the inactive meta record, then fsync again. Readers pin the newest valid transaction id. Freed pages enter a pending list keyed by the oldest reader transaction and return to the freelist after that reader exits. File truncation is never attempted.\n\nAssess crash consistency, transaction-id wraparound, reader starvation, page reuse, corrupted-meta recovery, and whether the two fsync sequence is sufficient on supported filesystems. Cite relevant code paths and report findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Raw documentation notes:\n\nThe mobile SDK maintains two queues. PriorityQueue contains explicit user actions such as send message or submit inspection. MaintenanceQueue contains analytics, prefetch, and stale-cache cleanup. Both persist in SQLite. Priority work may borrow all four network permits; maintenance work may use at most one when priority items exist. Authentication failures pause both queues until token refresh completes. A permanent 4xx moves an item to FailedItems, except 409 conflict, which invokes the resource merge handler. Exponential retry is capped at six hours and adds full jitter. The operating system may suspend execution at any time. Queue state is scoped by signed-in account and erased on sign-out.\n\nTurn this into a developer guide explaining scheduling, persistence, retries, conflict handling, account isolation, and extension points.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"Review request, no edits:\n\nThe key-value engine uses 32-bit page numbers. Page zero stores two alternating meta records; each contains root page, freelist head, transaction id, and checksum. Writers copy modified pages, fsync the data file, write the inactive meta record, then fsync again. Readers pin the newest valid transaction id. Freed pages enter a pending list keyed by the oldest reader transaction and return to the freelist after that reader exits. File truncation is never attempted.\n\nAssess crash consistency, transaction-id wraparound, reader starvation, page reuse, corrupted-meta recovery, and whether the two fsync sequence is sufficient on supported filesystems. Cite relevant code paths and report findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Raw documentation notes:\n\nThe mobile SDK maintains two queues. PriorityQueue contains explicit user actions such as send message or submit inspection. MaintenanceQueue contains analytics, prefetch, and stale-cache cleanup. Both persist in SQLite. Priority work may borrow all four network permits; maintenance work may use at most one when priority items exist. Authentication failures pause both queues until token refresh completes. A permanent 4xx moves an item to FailedItems, except 409 conflict, which invokes the resource merge handler. Exponential retry is capped at six hours and adds full jitter. The operating system may suspend execution at any time. Queue state is scoped by signed-in account and erased on sign-out.\n\nTurn this into a developer guide explaining scheduling, persistence, retries, conflict handling, account isolation, and extension points.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} {"prompt":"Create a migration roadmap from integer primary keys to sortable UUIDv7 identifiers across 60 PostgreSQL tables and three mobile clients.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Add a background compactor to the C++ time-series store with crash-safe manifest replacement and bounded write amplification.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Implement the watchOS hydration complication gallery with previews, crown navigation, and large-text support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Change BUTTON_DEBOUNCE_MS to 35.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Consolidate SQLite statement binding into one helper without changing coercion, null handling, or error text.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"The ESP32 resets when Wi-Fi reconnects during a flash write. Determine whether brownout, watchdog timing, or concurrent flash access causes it.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Read the existing conflict resolver and explain why field-level timestamps are compared before operation sequence numbers.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Consolidate SQLite statement binding into one helper without changing coercion, null handling, or error text.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"The ESP32 resets when Wi-Fi reconnects during a flash write. Determine whether brownout, watchdog timing, or concurrent flash access causes it.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Read the existing conflict resolver and explain why field-level timestamps are compared before operation sequence numbers.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Write a concise API guide for querying historical sensor readings with cursors and downsampling.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"First design a cross-device draft synchronization protocol, then implement the server-side operation log and compaction worker.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} {"prompt":"Implement passkey registration in the Kotlin API and document the mobile client's challenge-response sequence.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Build the SwiftUI database-health dashboard and add the diagnostics endpoint that supplies page and WAL statistics.","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Build the SwiftUI database-health dashboard and add the diagnostics endpoint that supplies page and WAL statistics.","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Correct the iOS minimum version in Package.swift and add a one-line compatibility note to the changelog.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.2,"slice":"mixed","lang":"en"} {"prompt":"Reorganize the firmware protocol handlers by message family without behavior changes, then update the maintainer map.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Find why image uploads duplicate after an app resumes, implement the correction, and document the recovered race for SDK integrators.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Audit the existing database-key rotation flow, then propose a staged redesign addressing the weaknesses you find.","purpose":"review","secondary":"planning","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Study the firmware command dispatcher and write a developer guide explaining its validation and extension points.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Find why image uploads duplicate after an app resumes, implement the correction, and document the recovered race for SDK integrators.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Audit the existing database-key rotation flow, then propose a staged redesign addressing the weaknesses you find.","purpose":"planning","secondary":"review","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Study the firmware command dispatcher and write a developer guide explaining its validation and extension points.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Implement Raft snapshot streaming with chunk checksums, resumable transfer, and bounded follower memory.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Create the Android camera calibration wizard with overlay guides, progress feedback, and retry states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the Android camera calibration wizard with overlay guides, progress feedback, and retry states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Set the SQLite busy timeout to 5s.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Explain how database/query/range_scan.go avoids returning duplicate keys after a page split.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Explain how database/query/range_scan.go avoids returning duplicate keys after a page split.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Develop a plan for separating patient data by residency region while retaining global account discovery and emergency access. Cover data ownership, routing, encryption keys, audit evidence, mobile caching, background jobs, migrations, and failure behavior when a home region is unavailable.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Escribe las notas de migración para el nuevo formato binario de telemetría, con ejemplos y estrategia de compatibilidad.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"es"} +{"prompt":"Escribe las notas de migración para el nuevo formato binario de telemetría, con ejemplos y estrategia de compatibilidad.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} {"prompt":"Extract packet framing from the UART driver without changing interrupt timing or the wire protocol.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Realm notifications stop firing after a user switches workspaces twice. Identify which subscription or lifecycle object is stale.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Design a phased replacement for our homegrown database replication protocol. I need alternatives, compatibility constraints, milestones, and rollback gates, not implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"boundary","lang":"en"} -{"prompt":"Document the wire format for alarm acknowledgements and implement its encoder and decoder.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Give the reconnect banner a softer shadow and slide it below the navigation bar.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"Make the toggle track 4px wider.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Rename databaseHandle to storeHandle across the SDK, retaining source-compatible deprecated accessors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"更新後に一部の端末だけ boot loop になります。署名検証、rollback counter、flash layout のどこが壊れているか調べてください。","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"ja"} -{"prompt":"Why does the current mobile cache retain tombstones for 90 days? Explain the intended behavior; storage usage is expected.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Summarize the existing Bluetooth session code as an integration guide for hardware partners.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Realm notifications stop firing after a user switches workspaces twice. Identify which subscription or lifecycle object is stale.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Design a phased replacement for our homegrown database replication protocol. I need alternatives, compatibility constraints, milestones, and rollback gates, not implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Document the wire format for alarm acknowledgements and implement its encoder and decoder.","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Give the reconnect banner a softer shadow and slide it below the navigation bar.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Make the toggle track 4px wider.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename databaseHandle to storeHandle across the SDK, retaining source-compatible deprecated accessors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"更新後に一部の端末だけ boot loop になります。署名検証、rollback counter、flash layout のどこが壊れているか調べてください。","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"ja"} +{"prompt":"Why does the current mobile cache retain tombstones for 90 days? Explain the intended behavior; storage usage is expected.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Summarize the existing Bluetooth session code as an integration guide for hardware partners.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Implement a PostgreSQL extension function that estimates table bloat from catalog statistics without taking heavyweight locks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Build the React Native emergency-contact editor with relationship pickers, validation, and unsaved-change protection.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Build the React Native emergency-contact editor with relationship pickers, validation, and unsaved-change protection.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Remove the duplicate semicolon in board.c.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Assess whether the current LSM compaction picker can starve the highest level under continuous writes.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Map a migration from per-device MQTT credentials to short-lived workload certificates. Address bootstrap identity, offline renewal, clock uncertainty, revocation, broker compatibility, manufacturing, fleet rollout, emergency recovery, and observability for millions of deployed units.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Write an operator runbook for recovering a PostgreSQL replica whose timeline diverged after failover.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Split the monolithic Swift SyncEngine into transport, operation log, merge, and persistence components without changing behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"A BLE characteristic occasionally reports an old value immediately after reconnect. Determine whether Android caching or our subscription order is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"A BLE characteristic occasionally reports an old value immediately after reconnect. Determine whether Android caching or our subscription order is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Database ticket DBENG-933\n\nObserved issue: range scans hold page pins until the iterator is destroyed. Analytics callers sometimes keep iterators alive for minutes, preventing cache eviction and increasing resident memory. We need incremental release without changing scan results.\n\nRequirements:\n- at most three leaf pages pinned per iterator\n- forward and reverse scans remain supported\n- snapshot visibility must remain stable\n- concurrent splits and merges cannot skip or duplicate keys\n- seek and resume tokens retain current encoding\n- iterator errors remain sticky\n- cancellation releases pins promptly\n- benchmarks for 1M-key scans must not regress more than 3%\n- fault tests should cover eviction and structural changes between next() calls\n\nImplement the iterator changes in engine/scan and preserve the public C API.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Release-planning notes:\n\nThe mobile app currently downloads a complete 800 MB offline map region. Product wants incremental map updates and user-selectable subregions. Tiles are generated daily, but road closures may need urgent publication. Existing iOS and Android clients identify a region only by integer revision. Downloads use a CDN and resume with HTTP ranges. Devices can have less than 1 GB free, remain offline for months, and downgrade to an older app through enterprise management. Legal requires country-border data to match the same publication snapshot. A corrupt update must never destroy the last usable map.\n\nCreate the storage, manifest, compatibility, rollout, and recovery design. Include delta-generation strategy, integrity verification, disk budgeting, snapshot consistency, CDN caching, downgrade behavior, and phased client migration. Deliver a plan only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"UI request from issue IOS-1402:\n\nView: SleepTrendView.swift\nData source already provides nightly duration, sleep stages, confidence, and missing-data reasons.\n\nDesign requirements:\n- seven-day and thirty-day segmented modes\n- smooth line for total sleep with gaps where data is unavailable\n- stage composition appears as stacked bars below the line\n- tapping a night selects both charts and opens a detail card\n- VoiceOver rotor should move between nights\n- use textual indicators for low-confidence readings\n- horizontal scrolling is allowed only in thirty-day mode\n- the current night remains visible after rotation\n- Reduce Motion disables the selection transition\n- export button stays in the navigation toolbar\n\nImplement the SwiftUI visualization and interactions using existing data types. No health-data queries need changes.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Failure report from the database fuzz suite:\n\nseed=817400193 operations=22817 page_size=4096\nop[22812] delete range [6f2200, 6f49ff]\nop[22813] checkpoint\nop[22814] crash after wal fsync before manifest rename\nop[22815] reopen\nop[22816] scan [6f0000, 6fffff]\nexpected 184 keys, got 187\nunexpected keys: 6f231a, 6f31cc, 6f4820\n\nThe three keys were covered by the range tombstone before the crash. Point deletes recover correctly. The WAL contains the range-delete record and a valid checksum, but the reopened memtable does not expose the tombstone. Determine which recovery or sequence-boundary rule loses it and fix the bug without changing the persisted WAL format.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Design notes from the database reliability review:\n\nWe run a multi-tenant PostgreSQL cluster with one primary, two synchronous regional replicas, and four asynchronous reporting replicas. Tenant sizes range from 10 MB to 14 TB. Large tenant restores currently require restoring the entire cluster. Product wants tenant-level point-in-time recovery with a four-hour RTO, but shared tables and cross-tenant billing records complicate isolation. Logical dumps are too slow. Backups are encrypted with one cluster key. Schema changes occur daily, and restores must be testable without exposing production data to developers.\n\nDevelop an architecture and migration plan for tenant-scoped recovery. Cover data layout, shared references, WAL or logical capture, encryption, verification, operational workflow, schema compatibility, cost, and failure rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"pasted-context","lang":"en"} -{"prompt":"Backend issue FW-318:\n\nA gateway receives binary frames from up to 128 RS-485 devices. The current parser assumes each read begins on a frame boundary, but the new DMA driver returns arbitrary chunks. Implement a streaming parser for this format:\n- preamble: AA 55\n- one-byte version\n- two-byte little-endian payload length, maximum 2048\n- payload\n- CRC32C over version, length, and payload\n\nRequirements include fragmented frames, multiple frames per chunk, noise before a preamble, bad CRC recovery, bounded memory, counters by rejection reason, and no heap allocation in the steady state. Version 1 and 2 payload decoders already exist. Add property tests and fuzz seeds for truncated, nested-preamble, and maximum-length inputs.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Product ticket AND-2268:\n\nScreen: account storage manager\nPurpose: help users understand and reclaim offline storage.\n\nSections:\n- downloaded map regions with size and last-used date\n- queued uploads, split into retrying and waiting for Wi-Fi\n- cached attachments grouped by workspace\n- database and essential data shown as non-removable\n\nInteractions:\nUsers can select multiple removable items, see estimated recovered space, and confirm deletion. Deleting a map currently in navigation must be disabled with an explanation. Operations may take several seconds and should report item-level failures. The list must update if sync removes an upload in the background. Support TalkBack, font scaling, landscape tablets, and low-storage warning styling without relying on red alone.\n\nImplement this in Compose using StorageInventoryViewModel; deletion APIs already exist.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Known config change from the database team:\n\nSetting: wal_segment_cache_entries\nFile: config/defaults.toml\nOld value: 16\nNew value: 32\n\nThe cache implementation and memory budget were already reviewed under DB-901. This request is only to adopt the approved default for new installations. Existing installations persist their explicit values and are unaffected. Do not change the maximum, documentation, sample benchmark configuration, environment override, or tests unrelated to the default. Preserve the surrounding key order and comment formatting.\n\nMake the single value change.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"pasted-context","lang":"en"} -{"prompt":"Internal cleanup brief:\n\nThe iOS app has three implementations of account-scoped cache invalidation in AvatarStore, DocumentPreviewStore, and SearchSuggestionStore. Each listens for AccountSession.didSignOut, cancels in-flight tasks, deletes disk entries, clears memory, and publishes an empty state. Their operation order differs intentionally: DocumentPreviewStore must close file handles before deletion; SearchSuggestionStore has no disk layer. Tests assert publisher timing, and privacy requirements prohibit retaining any prior-account content after the sign-out notification completes.\n\nExtract a reusable account-bound lifecycle helper while preserving each store's ordering, threading, published values, and public API. Avoid introducing a singleton. Behavior and privacy guarantees must remain identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Crash and power trace:\n\nDevice: soil-node Rev B, firmware 3.8.1\nReset reason: watchdog\n03:22:18.441 radio IRQ asserted\n03:22:18.442 task radio_rx entered\n03:22:18.443 flash_gc acquiring storage_mutex\n03:22:18.444 radio_rx waiting storage_mutex\n03:22:18.448 flash_gc erasing sector 19\n03:22:21.448 watchdog reset\n\nCurrent watchdog window is 2 seconds. Sector erase normally takes 180 ms but reaches 3.1 seconds below -20°C. The radio receive task also writes its acknowledgement counter to the same flash journal. We cannot simply increase the watchdog window because safety requirements cap it at 2 seconds. Diagnose the blocking design and implement a safe fix that retains acknowledgement durability and cold-temperature operation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Code-review context:\n\nThe mobile database encrypts every 4 KiB page independently using AES-GCM. Nonce input is database_id || page_number || generation. Generation increments whenever a page number is reused and is stored in the encrypted page header. The unencrypted file header stores database_id and a wrapped data key. WAL records contain encrypted after-images using the target page nonce. Compaction may copy ciphertext unchanged. Backups copy the database and WAL while writes continue, then capture the latest manifest. Deleted pages return to the freelist after the oldest reader releases its snapshot.\n\nReview nonce uniqueness, header tampering, backup consistency, torn writes, page reuse, key rotation, and information leakage. Report security findings and uncertainties; do not change code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Notes for the public SDK documentation:\n\nConnectionManager represents four states: disconnected, connecting, ready, and suspended. connect() is idempotent and may be called before permissions are granted. The manager automatically reconnects with capped exponential delay unless disconnect(permanent: true) is used. The operating system may suspend Bluetooth in the background; this transitions to suspended and does not count as a failed attempt. Command requests made before ready are queued in memory, limited to 50, and fail oldest-first when full. Commands are never persisted across process termination. Firmware-update commands disable ordinary reconnect until the update session resolves. State callbacks arrive on the caller-provided executor.\n\nWrite a developer-facing connection lifecycle guide with usage examples, threading notes, retry behavior, queue limits, and common mistakes.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"Release-planning notes:\n\nThe mobile app currently downloads a complete 800 MB offline map region. Product wants incremental map updates and user-selectable subregions. Tiles are generated daily, but road closures may need urgent publication. Existing iOS and Android clients identify a region only by integer revision. Downloads use a CDN and resume with HTTP ranges. Devices can have less than 1 GB free, remain offline for months, and downgrade to an older app through enterprise management. Legal requires country-border data to match the same publication snapshot. A corrupt update must never destroy the last usable map.\n\nCreate the storage, manifest, compatibility, rollout, and recovery design. Include delta-generation strategy, integrity verification, disk budgeting, snapshot consistency, CDN caching, downgrade behavior, and phased client migration. Deliver a plan only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"pasted-context","lang":"en"} +{"prompt":"UI request from issue IOS-1402:\n\nView: SleepTrendView.swift\nData source already provides nightly duration, sleep stages, confidence, and missing-data reasons.\n\nDesign requirements:\n- seven-day and thirty-day segmented modes\n- smooth line for total sleep with gaps where data is unavailable\n- stage composition appears as stacked bars below the line\n- tapping a night selects both charts and opens a detail card\n- VoiceOver rotor should move between nights\n- use textual indicators for low-confidence readings\n- horizontal scrolling is allowed only in thirty-day mode\n- the current night remains visible after rotation\n- Reduce Motion disables the selection transition\n- export button stays in the navigation toolbar\n\nImplement the SwiftUI visualization and interactions using existing data types. No health-data queries need changes.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Failure report from the database fuzz suite:\n\nseed=817400193 operations=22817 page_size=4096\nop[22812] delete range [6f2200, 6f49ff]\nop[22813] checkpoint\nop[22814] crash after wal fsync before manifest rename\nop[22815] reopen\nop[22816] scan [6f0000, 6fffff]\nexpected 184 keys, got 187\nunexpected keys: 6f231a, 6f31cc, 6f4820\n\nThe three keys were covered by the range tombstone before the crash. Point deletes recover correctly. The WAL contains the range-delete record and a valid checksum, but the reopened memtable does not expose the tombstone. Determine which recovery or sequence-boundary rule loses it and fix the bug without changing the persisted WAL format.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Design notes from the database reliability review:\n\nWe run a multi-tenant PostgreSQL cluster with one primary, two synchronous regional replicas, and four asynchronous reporting replicas. Tenant sizes range from 10 MB to 14 TB. Large tenant restores currently require restoring the entire cluster. Product wants tenant-level point-in-time recovery with a four-hour RTO, but shared tables and cross-tenant billing records complicate isolation. Logical dumps are too slow. Backups are encrypted with one cluster key. Schema changes occur daily, and restores must be testable without exposing production data to developers.\n\nDevelop an architecture and migration plan for tenant-scoped recovery. Cover data layout, shared references, WAL or logical capture, encryption, verification, operational workflow, schema compatibility, cost, and failure rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Backend issue FW-318:\n\nA gateway receives binary frames from up to 128 RS-485 devices. The current parser assumes each read begins on a frame boundary, but the new DMA driver returns arbitrary chunks. Implement a streaming parser for this format:\n- preamble: AA 55\n- one-byte version\n- two-byte little-endian payload length, maximum 2048\n- payload\n- CRC32C over version, length, and payload\n\nRequirements include fragmented frames, multiple frames per chunk, noise before a preamble, bad CRC recovery, bounded memory, counters by rejection reason, and no heap allocation in the steady state. Version 1 and 2 payload decoders already exist. Add property tests and fuzz seeds for truncated, nested-preamble, and maximum-length inputs.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Product ticket AND-2268:\n\nScreen: account storage manager\nPurpose: help users understand and reclaim offline storage.\n\nSections:\n- downloaded map regions with size and last-used date\n- queued uploads, split into retrying and waiting for Wi-Fi\n- cached attachments grouped by workspace\n- database and essential data shown as non-removable\n\nInteractions:\nUsers can select multiple removable items, see estimated recovered space, and confirm deletion. Deleting a map currently in navigation must be disabled with an explanation. Operations may take several seconds and should report item-level failures. The list must update if sync removes an upload in the background. Support TalkBack, font scaling, landscape tablets, and low-storage warning styling without relying on red alone.\n\nImplement this in Compose using StorageInventoryViewModel; deletion APIs already exist.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Known config change from the database team:\n\nSetting: wal_segment_cache_entries\nFile: config/defaults.toml\nOld value: 16\nNew value: 32\n\nThe cache implementation and memory budget were already reviewed under DB-901. This request is only to adopt the approved default for new installations. Existing installations persist their explicit values and are unaffected. Do not change the maximum, documentation, sample benchmark configuration, environment override, or tests unrelated to the default. Preserve the surrounding key order and comment formatting.\n\nMake the single value change.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Internal cleanup brief:\n\nThe iOS app has three implementations of account-scoped cache invalidation in AvatarStore, DocumentPreviewStore, and SearchSuggestionStore. Each listens for AccountSession.didSignOut, cancels in-flight tasks, deletes disk entries, clears memory, and publishes an empty state. Their operation order differs intentionally: DocumentPreviewStore must close file handles before deletion; SearchSuggestionStore has no disk layer. Tests assert publisher timing, and privacy requirements prohibit retaining any prior-account content after the sign-out notification completes.\n\nExtract a reusable account-bound lifecycle helper while preserving each store's ordering, threading, published values, and public API. Avoid introducing a singleton. Behavior and privacy guarantees must remain identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Crash and power trace:\n\nDevice: soil-node Rev B, firmware 3.8.1\nReset reason: watchdog\n03:22:18.441 radio IRQ asserted\n03:22:18.442 task radio_rx entered\n03:22:18.443 flash_gc acquiring storage_mutex\n03:22:18.444 radio_rx waiting storage_mutex\n03:22:18.448 flash_gc erasing sector 19\n03:22:21.448 watchdog reset\n\nCurrent watchdog window is 2 seconds. Sector erase normally takes 180 ms but reaches 3.1 seconds below -20°C. The radio receive task also writes its acknowledgement counter to the same flash journal. We cannot simply increase the watchdog window because safety requirements cap it at 2 seconds. Diagnose the blocking design and implement a safe fix that retains acknowledgement durability and cold-temperature operation.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Code-review context:\n\nThe mobile database encrypts every 4 KiB page independently using AES-GCM. Nonce input is database_id || page_number || generation. Generation increments whenever a page number is reused and is stored in the encrypted page header. The unencrypted file header stores database_id and a wrapped data key. WAL records contain encrypted after-images using the target page nonce. Compaction may copy ciphertext unchanged. Backups copy the database and WAL while writes continue, then capture the latest manifest. Deleted pages return to the freelist after the oldest reader releases its snapshot.\n\nReview nonce uniqueness, header tampering, backup consistency, torn writes, page reuse, key rotation, and information leakage. Report security findings and uncertainties; do not change code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Notes for the public SDK documentation:\n\nConnectionManager represents four states: disconnected, connecting, ready, and suspended. connect() is idempotent and may be called before permissions are granted. The manager automatically reconnects with capped exponential delay unless disconnect(permanent: true) is used. The operating system may suspend Bluetooth in the background; this transitions to suspended and does not count as a failed attempt. Command requests made before ready are queued in memory, limited to 50, and fail oldest-first when full. Commands are never persisted across process termination. Firmware-update commands disable ordinary reconnect until the update session resolves. State callbacks arrive on the caller-provided executor.\n\nWrite a developer-facing connection lifecycle guide with usage examples, threading notes, retry behavior, queue limits, and common mistakes.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Implement a Rust proxy that multiplexes database sessions over a limited connection pool while preserving transaction affinity.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Create the SwiftUI firmware-update screen with download, transfer, verification, reboot, recovery, and failure states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the SwiftUI firmware-update screen with download, transfer, verification, reboot, recovery, and failure states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Switch the default locale to en-GB.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Explain how the current query planner chooses between an index scan and a covering table scan.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Explain how the current query planner chooses between an index scan and a covering table scan.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Plan a zero-downtime transition from one shared mobile API to region-specific endpoints. Include endpoint discovery, client-version compatibility, queued offline requests, authentication, data residency, failover, telemetry, staged routing, and rollback for clients that update slowly.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Write a troubleshooting guide for BLE pairing failures across Android OEM variants.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Replace duplicated transaction retry loops with one helper while preserving retry counts, jitter, and exception mapping.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Concurrent inserts occasionally violate a supposedly unique email index under snapshot isolation. Reconstruct how both transactions commit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Create an RFC for moving device telemetry from MQTT topics to a durable append-only log. Compare options and define migration stages, dual publication, ordering, retention, replay, device compatibility, cost, and operational ownership.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"boundary","lang":"en"} -{"prompt":"Add protocol examples to docs/commands.md and implement support for the new batch-read command.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Add a gentle shimmer to unloaded map tiles and stop it once imagery appears.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"Make the badge corner radius 6px.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Rename syncToken to continuationToken throughout client and server code while retaining the old wire field.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Why do SQLite readers sometimes see database is locked even though WAL mode is enabled? Find the unanticipated lock holder.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Explain why the existing iOS sync engine uploads deletions before edits. Assume current conflict behavior is intentional.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Turn the current firmware update behavior into a concise support article for field technicians.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"continue the offline strategy","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} -{"prompt":"finish that database command","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Write a troubleshooting guide for BLE pairing failures across Android OEM variants.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Replace duplicated transaction retry loops with one helper while preserving retry counts, jitter, and exception mapping.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Concurrent inserts occasionally violate a supposedly unique email index under snapshot isolation. Reconstruct how both transactions commit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create an RFC for moving device telemetry from MQTT topics to a durable append-only log. Compare options and define migration stages, dual publication, ordering, retention, replay, device compatibility, cost, and operational ownership.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add protocol examples to docs/commands.md and implement support for the new batch-read command.","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Add a gentle shimmer to unloaded map tiles and stop it once imagery appears.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Make the badge corner radius 6px.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename syncToken to continuationToken throughout client and server code while retaining the old wire field.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Why do SQLite readers sometimes see database is locked even though WAL mode is enabled? Find the unanticipated lock holder.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Explain why the existing iOS sync engine uploads deletions before edits. Assume current conflict behavior is intentional.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Turn the current firmware update behavior into a concise support article for field technicians.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"polish the phone screen","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"tiny firmware tweak","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} -{"prompt":"clean up the storage bits","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"track down the sync weirdness","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} -{"prompt":"look through the protocol code","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"document what the SDK does","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"tiny firmware tweak","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"clean up the storage bits","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"track down the sync weirdness","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"look through the protocol code","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"document what the SDK does","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Implement a garbage collector for orphaned object-store blobs referenced by a transactional metadata database.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Build the iOS storage-usage chart with category drilldowns, animated selection, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Build the iOS storage-usage chart with category drilldowns, animated selection, and accessible summaries.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Set MAX_CONNECTIONS to 12.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Review the flash wear-leveling algorithm and estimate whether metadata sectors receive disproportionate erase cycles.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Design a long-term schema-evolution strategy for event payloads shared by firmware, mobile apps, cloud ingestion, and analytics. Cover version negotiation, unknown fields, validation ownership, code generation, compatibility tests, rollout order, retention, replay, and deprecating devices that cannot update.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Draft the privacy-policy appendix describing what offline application data remains on a device after logout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Design a long-term schema-evolution strategy for event payloads shared by firmware, mobile apps, cloud ingestion, and analytics. Cover version negotiation, unknown fields, validation ownership, code generation, compatibility tests, rollout order, retention, replay, and deprecating devices that cannot update.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Draft the privacy-policy appendix describing what offline application data remains on a device after logout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Split database metrics collection from query execution while preserving metric names and timing boundaries.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"An iOS background task reports success while its final SQLite transaction is rolled back during suspension. Find the completion-order bug.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"An iOS background task reports success while its final SQLite transaction is rolled back during suspension. Find the completion-order bug.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Design account-to-account data transfer, then implement the audited backend workflow with resumable copying.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"Implement database snapshot download links and build the admin panel for creating and revoking them.","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Create the Compose conflict-resolution screen and add the endpoint that returns field-level differences.","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Implement database snapshot download links and build the admin panel for creating and revoking them.","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Create the Compose conflict-resolution screen and add the endpoint that returns field-level differences.","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Diagnose the intermittent firmware checksum rejection, fix it, and document byte-order expectations for bootloader integrators.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Correct the migration filename date.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Extract common cursor encoding without altering existing tokens or error responses.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Assess whether the current Android keystore wrapper can silently regenerate keys after biometric enrollment changes.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write an architecture note explaining the existing database checkpoint and recovery sequence.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Extract common cursor encoding without altering existing tokens or error responses.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Assess whether the current Android keystore wrapper can silently regenerate keys after biometric enrollment changes.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Write an architecture note explaining the existing database checkpoint and recovery sequence.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Implement a C library for decoding compact CBOR telemetry messages without dynamic allocation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Build the tablet master-detail interface for browsing database backups and restore points.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Change ENABLE_NFC to 1.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Explain how the current mobile client decides whether a queued mutation is safe to retry.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Develop a roadmap for replacing physical SIMs with eSIM provisioning across an industrial device fleet. Include manufacturing, carrier APIs, secure activation, offline sites, inventory, regional constraints, rollback, support tooling, telemetry, and staged hardware compatibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Write customer-facing release notes for encrypted local backups and the new recovery-key flow.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Consolidate the three database schema diff implementations while keeping their output ordering identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"The STM32 occasionally executes an old interrupt vector after swapping firmware banks. Determine which cache or remap step is missing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Plan, but don't implement, a shared identity model for mobile users, devices, and service technicians. Include enrollment, delegation, revocation, offline proofs, auditability, privacy boundaries, and migration from shared site passwords.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"boundary","lang":"en"} -{"prompt":"Update the database API reference with savepoint semantics and implement nested savepoint support in the driver.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Make the sensor card flash once when a critical reading arrives, with a reduced-motion alternative.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"Shift the floating button down 3px.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Rename pairedDevice to enrolledDevice across the codebase while retaining old Codable keys.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Why does the query result cache grow after every schema migration even when entries expire? Diagnose the leak.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Explain why the existing bootloader verifies the image twice, once before writing and once before booting. No failure is reported.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Summarize the existing account-deletion code into a compliance procedure for auditors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Implement serializable transaction validation for the educational database engine, including predicate-conflict tracking.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Create the React Native map-download queue with progress, pause, resume, failure reasons, and storage warnings.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Explain how the current mobile client decides whether a queued mutation is safe to retry.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Develop a roadmap for replacing physical SIMs with eSIM provisioning across an industrial device fleet. Include manufacturing, carrier APIs, secure activation, offline sites, inventory, regional constraints, rollback, support tooling, telemetry, and staged hardware compatibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Write customer-facing release notes for encrypted local backups and the new recovery-key flow.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Consolidate the three database schema diff implementations while keeping their output ordering identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"The STM32 occasionally executes an old interrupt vector after swapping firmware banks. Determine which cache or remap step is missing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Plan, but don't implement, a shared identity model for mobile users, devices, and service technicians. Include enrollment, delegation, revocation, offline proofs, auditability, privacy boundaries, and migration from shared site passwords.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Update the database API reference with savepoint semantics and implement nested savepoint support in the driver.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Make the sensor card flash once when a critical reading arrives, with a reduced-motion alternative.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Shift the floating button down 3px.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename pairedDevice to enrolledDevice across the codebase while retaining old Codable keys.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Why does the query result cache grow after every schema migration even when entries expire? Diagnose the leak.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Explain why the existing bootloader verifies the image twice, once before writing and once before booting. No failure is reported.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Summarize the existing account-deletion code into a compliance procedure for auditors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Implement serializable transaction validation for the educational database engine, including predicate-conflict tracking.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create the React Native map-download queue with progress, pause, resume, failure reasons, and storage warnings.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Use 115200 as the debug baud rate.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Review the current CRDT text implementation and explain how it prevents duplicate insertion after replay.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Review the current CRDT text implementation and explain how it prevents duplicate insertion after replay.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Create an architecture and migration plan for moving encrypted mobile backups from vendor cloud storage to user-selected providers. Address provider APIs, key custody, interrupted uploads, version retention, restore discovery, deletion, account loss, migration coexistence, and backward compatibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Escreva uma página de referência para os códigos de erro do protocolo de pareamento e como o app deve tratá-los.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"pt"} -{"prompt":"Move common sensor calibration math into one module without changing floating-point results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"A PostgreSQL connection pool sometimes returns a session with the previous tenant's search_path. Find the reset failure.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Outline a strategy for deprecating the v1 device protocol while some field units cannot receive firmware updates. Include gateway translation, security limits, support timelines, fleet discovery, rollout stages, and final containment.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Add schema examples for geofence events and implement their ingestion validation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Add a visible pressed state to the keypad buttons and improve spacing in landscape.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"Change the icon size from 23 to 24.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Rename syncQueue to operationQueue repository-wide, preserving database table and telemetry names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Why does a read replica return rows older than its reported replay LSN? Find the unknown consistency issue.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Explain why the current pairing protocol includes both a nonce and a monotonically increasing counter. Assume it is functioning correctly.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Transform the existing restore workflow into a step-by-step support playbook without modifying the implementation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Move common sensor calibration math into one module without changing floating-point results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"A PostgreSQL connection pool sometimes returns a session with the previous tenant's search_path. Find the reset failure.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Outline a strategy for deprecating the v1 device protocol while some field units cannot receive firmware updates. Include gateway translation, security limits, support timelines, fleet discovery, rollout stages, and final containment.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add schema examples for geofence events and implement their ingestion validation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Add a visible pressed state to the keypad buttons and improve spacing in landscape.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Change the icon size from 23 to 24.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename syncQueue to operationQueue repository-wide, preserving database table and telemetry names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Why does a read replica return rows older than its reported replay LSN? Find the unknown consistency issue.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Explain why the current pairing protocol includes both a nonce and a monotonically increasing counter. Assume it is functioning correctly.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Transform the existing restore workflow into a step-by-step support playbook without modifying the implementation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Implement a durable delayed-job queue on PostgreSQL with leasing, priority aging, cancellation, and concurrent workers.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Build the macOS sidebar for connected devices with grouping, search, connection indicators, and keyboard navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Set the flash page count to 512.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Inspect the existing database backup verifier and determine whether it detects reordered chunks.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Inspect the existing database backup verifier and determine whether it detects reordered chunks.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Design a migration from device-local rules to centrally managed automation while preserving offline execution. Cover rule distribution, versioning, conflict ownership, secrets, safety limits, audit logs, staged rollout, emergency disable, and how older firmware interprets unsupported actions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Write the README for the protocol simulator, including scripted scenarios and fault injection.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Extract mobile account-switch cleanup into composable lifecycle handlers without changing deletion order.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"The database recovery test hangs only when the final WAL record exactly fills a block. Locate the loop or boundary error.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"resume the device roadmap","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} -{"prompt":"do the persistence part","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"The database recovery test hangs only when the final WAL record exactly fills a block. Locate the loop or boundary error.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Build the SwiftUI signal-strength indicator with smooth transitions and a no-signal state.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Fix the typo in DEVICE_NMAE.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Separate firmware manifest parsing from validation while preserving accepted images and errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Offline edits sometimes apply to the wrong account after rapid sign-out and sign-in. Find the ownership race.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Review the existing page-cache eviction policy and explain how dirty pages are protected from premature reuse.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Separate firmware manifest parsing from validation while preserving accepted images and errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Offline edits sometimes apply to the wrong account after rapid sign-out and sign-in. Find the ownership race.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Review the existing page-cache eviction policy and explain how dirty pages are protected from premature reuse.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Redacta una guía de recuperación para dispositivos que quedan en modo bootloader después de una actualización fallida.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} -{"prompt":"Map out the staged rollout for our STM32 bootloader rewrite, including rollback checkpoints and hardware-in-the-loop gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Add a Go endpoint to reserve inventory atomically in the warehouse service, using the existing PostgreSQL transaction helper.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Map out the staged rollout for our STM32 bootloader rewrite, including rollback checkpoints and hardware-in-the-loop gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add a Go endpoint to reserve inventory atomically in the warehouse service, using the existing PostgreSQL transaction helper.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Build the SwiftUI pairing screen for nearby AirLink sensors, including scanning, empty, permission-denied, and connected states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Bump tokio to 1.47","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Split PacketDecoder.swift into transport-neutral parsing and BLE framing layers without changing the decoded output.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"The macOS menu-bar app sometimes exits when a device reconnects after sleep. Find the cause; there is no crash dialog, only an EXC_BAD_ACCESS entry in Console.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"The macOS menu-bar app sometimes exits when a device reconnects after sleep. Find the cause; there is no crash dialog, only an EXC_BAD_ACCESS entry in Console.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Audit this SPI driver for races","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Write release notes for v2.6","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Write release notes for v2.6","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Design a migration from the monolithic telemetry collector to per-protocol workers. Cover process boundaries, message contracts, backpressure, deployment sequencing, observability, compatibility with field units on firmware 3.x, and how we can roll back without losing buffered measurements. The deliverable should be an RFC and milestone breakdown, not implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Implement CBOR decoding for sensor envelopes","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Create a responsive dashboard card that plots battery voltage and highlights brownout periods using our existing Charts theme.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Turn ENABLE_LEGACY_SCAN off","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Consolidate the three CRC implementations under crates/checksum while keeping their public functions and byte-for-byte results unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Consolidate the three CRC implementations under crates/checksum while keeping their public functions and byte-for-byte results unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Why does the Rust gateway report negative packet ages only on 32-bit ARM builds? Reproduce it and trace where the value goes wrong.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Walk me through how DeviceLeaseManager decides whether another process may claim a serial port. I only want an explanation of the current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Draft a README section explaining how to flash a development board with probe-rs and recover from a failed update.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Outline the OTA key-rotation approach","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Wire the Python ingestion worker to publish malformed-frame metrics with bounded device_id cardinality.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Polish the Bluetooth permission sheet","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Draft a README section explaining how to flash a development board with probe-rs and recover from a failed update.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Outline the OTA key-rotation approach","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Wire the Python ingestion worker to publish malformed-frame metrics with bounded device_id cardinality.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Polish the Bluetooth permission sheet","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"Correct the misspelled baudrate key in config/example.toml","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Extract reconnect timing from BleSession into a reusable policy object; behavior, delays, and emitted events must stay identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Extract reconnect timing from BleSession into a reusable policy object; behavior, delays, and emitted events must stay identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Investigate random watchdog resets","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Is the nonce construction in crypto/session_keys.c safe when the frame counter wraps? Review the implementation and threat assumptions without modifying it.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Escribe la guía de contribución para compilar el firmware, ejecutar Unity tests y enviar cambios al repositorio.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"es"} +{"prompt":"Is the nonce construction in crypto/session_keys.c safe when the frame counter wraps? Review the implementation and threat assumptions without modifying it.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Escribe la guía de contribución para compilar el firmware, ejecutar Unity tests y enviar cambios al repositorio.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} {"prompt":"Propose an architecture for synchronizing offline device settings across the iOS app, cloud API, and intermittently connected gateways. Include conflict resolution, versioning, storage ownership, security boundaries, failure recovery, and a sequence of milestones that lets us ship read-only synchronization before bidirectional edits.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Add a bounded retry queue to the MQTT publisher with jittered backoff and disk persistence for power loss.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Implement the calibration wizard UI from the checked-in Figma export, including keyboard navigation and a reduced-motion transition.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"The status dot should use var(--warning-500), not var(--orange-400), in DeviceRow.css. Make that color correction only.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Rename MasterNode to CoordinatorNode throughout firmware, simulator, tests, generated bindings, and docs references while preserving all runtime behavior and wire identifiers.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Why do USB transfers stall after roughly 18 minutes under sustained load? The host keeps submitting URBs, but completions stop until the board is unplugged.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"The status dot should use var(--warning-500), not var(--orange-400), in DeviceRow.css. Make that color correction only.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename MasterNode to CoordinatorNode throughout firmware, simulator, tests, generated bindings, and docs references while preserving all runtime behavior and wire identifiers.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Why do USB transfers stall after roughly 18 minutes under sustained load? The host keeps submitting URBs, but completions stop until the board is unplugged.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Why does FrameAssembler retain the final delimiter instead of discarding it? Explain whether that is intentional based on the parser and its tests; nothing is currently failing.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Summarize the existing provisioning handshake as a concise sequence diagram description for the developer handbook.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Plan the transition from numeric board IDs to UUIDs across storage, APIs, logs, and factory tooling, with a compatibility window for already shipped devices.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"The protocol has already been decided: implement the /v3/devices/{id}/commands endpoint with idempotency keys, a 24-hour replay record, and the existing DeviceCommand protobuf.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Add a compact device-list mode with denser rows, abbreviated signal labels, a toggle in Display Settings, and responsive behavior on iPad split view.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Rename local variable repsonse to response in HttpProbe.ts","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Reorganize the radio command handlers by feature and remove duplicated validation helpers, with no changes to accepted commands, error codes, or timing.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Summarize the existing provisioning handshake as a concise sequence diagram description for the developer handbook.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Plan the transition from numeric board IDs to UUIDs across storage, APIs, logs, and factory tooling, with a compatibility window for already shipped devices.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"The protocol has already been decided: implement the /v3/devices/{id}/commands endpoint with idempotency keys, a 24-hour replay record, and the existing DeviceCommand protobuf.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add a compact device-list mode with denser rows, abbreviated signal labels, a toggle in Display Settings, and responsive behavior on iPad split view.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Rename local variable repsonse to response in HttpProbe.ts","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Reorganize the radio command handlers by feature and remove duplicated validation helpers, with no changes to accepted commands, error codes, or timing.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Track down the reconnect crash on macOS 15, add a regression test once understood, and write a short root-cause note for docs/incidents/ble-reconnect.md.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Review the pending secure-boot design for downgrade and key-compromise risks, then turn your findings into a decision memo for the firmware team.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Produce an API guide for remote firmware jobs, and add a runnable TypeScript example that submits a job and polls it to completion.","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"Plan and implement the first phase of resumable artifact uploads: define the request lifecycle and storage invariants, then build the create-session and append-chunk endpoints behind upload_v2.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"Implement a serial-port discovery command in fieldctl and add a concise usage section with Linux udev troubleshooting.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Review the pending secure-boot design for downgrade and key-compromise risks, then turn your findings into a decision memo for the firmware team.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Produce an API guide for remote firmware jobs, and add a runnable TypeScript example that submits a job and polls it to completion.","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Plan and implement the first phase of resumable artifact uploads: define the request lifecycle and storage invariants, then build the create-session and append-chunk endpoints behind upload_v2.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Implement a serial-port discovery command in fieldctl and add a concise usage section with Linux udev troubleshooting.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} {"prompt":"Ticket UI-1842\n\nField techs use the app outdoors with gloves. The new pairing flow technically works, but several states still render as raw text inside DebugPanel. Product notes:\n- Scanning should show nearby units as large tappable cards.\n- Each card needs serial suffix, model, RSSI strength, and a clear selected state.\n- If Bluetooth is disabled, show the existing radio-off illustration and a button that opens system settings.\n- Pairing can take 20 seconds; keep the chosen device visible and show progress without blocking navigation.\n- VoiceOver must announce changes without repeating the entire list.\n\nAcceptance: replace DebugPanel in PairingView.swift with the production SwiftUI flow. Reuse DeviceCardStyle and our spacing tokens. Do not change discovery behavior.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} {"prompt":"CI log from release/3.4:\n\nRun actions/upload-artifact@v4\nWith the provided path, there will be 0 files uploaded.\nWarning: No files were found with the provided path: build/output/*.hex\nError: Process completed with exit code 1\n\nRelevant workflow:\n - name: Build firmware\n run: make BOARD=rev_c release\n - uses: actions/upload-artifact@v4\n with:\n name: gateway-rev-c\n path: build/output/*.hex\n\nMake now emits build/rev_c/release/gateway.hex after last week's directory cleanup. Update the artifact path to that exact file; don't alter the build or workflow structure.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"pasted-context","lang":"en"} -{"prompt":"Notes from code review:\n\nlib/protocol/frame.ts currently imports crc16 from lib/device/crc.ts. The simulator imports FrameDecoder from lib/protocol, while lib/device/index.ts re-exports the simulator adapter. That cycle is why the bundler needs the odd lazy require.\n\nDesired dependency direction:\n protocol-core <- device-adapter <- simulator\n\nMove checksum primitives and frame types into packages/protocol-core. Keep the existing public imports working through re-exports, preserve emitted frame bytes, and don't rename JSON fields. Tests under test/golden_frames must remain unchanged. This is structural cleanup only; no new packet formats or validation rules.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Notes from code review:\n\nlib/protocol/frame.ts currently imports crc16 from lib/device/crc.ts. The simulator imports FrameDecoder from lib/protocol, while lib/device/index.ts re-exports the simulator adapter. That cycle is why the bundler needs the odd lazy require.\n\nDesired dependency direction:\n protocol-core <- device-adapter <- simulator\n\nMove checksum primitives and frame types into packages/protocol-core. Keep the existing public imports working through re-exports, preserve emitted frame bytes, and don't rename JSON fields. Tests under test/golden_frames must remain unchanged. This is structural cleanup only; no new packet formats or validation rules.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Crash report from a field gateway:\n\nThread 7 Crashed:\n0 libswiftCore.so swift_release + 28\n1 RelayKit Channel.close() + 184\n2 RelayKit closure #1 in Channel.timeoutExpired() + 92\n3 libdispatch _dispatch_call_block_and_release + 24\n\nLog tail:\n14:03:11.009 channel 42 timeout scheduled generation=7\n14:03:11.011 channel 42 peer-close received\n14:03:11.013 channel 42 removed from registry\n14:03:11.114 channel 42 timeout fired generation=7\n\nThis started after we made close callbacks asynchronous. It occurs about once per 50,000 connections and ASan hasn't caught it. Determine the actual lifetime/race bug and show how to reproduce it reliably before changing anything.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Proposed patch:\n\ndiff --git a/firmware/radio.c b/firmware/radio.c\n@@\n- if (retry_count < MAX_RETRIES) {\n- schedule_retry(packet);\n- }\n+ if (retry_count++ <= MAX_RETRIES) {\n+ schedule_retry(packet);\n+ } else {\n+ metrics_inc(RADIO_DROPPED);\n+ }\n\ndiff --git a/firmware/config.h b/firmware/config.h\n@@\n-#define MAX_RETRIES 3\n+#define MAX_RETRIES 4\n\nAuthor says this preserves three retry attempts while exposing drops. Check that claim against the counter semantics, ownership of packet, and existing tests. Flag correctness or safety issues, but do not edit the patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"Proposed patch:\n\ndiff --git a/firmware/radio.c b/firmware/radio.c\n@@\n- if (retry_count < MAX_RETRIES) {\n- schedule_retry(packet);\n- }\n+ if (retry_count++ <= MAX_RETRIES) {\n+ schedule_retry(packet);\n+ } else {\n+ metrics_inc(RADIO_DROPPED);\n+ }\n\ndiff --git a/firmware/config.h b/firmware/config.h\n@@\n-#define MAX_RETRIES 3\n+#define MAX_RETRIES 4\n\nAuthor says this preserves three retry attempts while exposing drops. Check that claim against the counter semantics, ownership of packet, and existing tests. Flag correctness or safety issues, but do not edit the patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} {"prompt":"Document that thing","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} {"prompt":"Figure out the rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"Finish the daemon bit","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} @@ -8388,23 +8185,23 @@ {"prompt":"Set the Helm chart appVersion to 4.8.1","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Move feature-vector normalization out of train.py into a shared transform used by training and batch inference, preserving current numerical results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Our CUDA training job hangs after validation epoch 6 with GPU utilization at zero and one dataloader worker still alive. Work out where it deadlocks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Assess whether FeatureStoreClient can return stale values after invalidate() races with getOrLoad(). Just report what the current code guarantees.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Assess whether FeatureStoreClient can return stale values after invalidate() races with getOrLoad(). Just report what the current code guarantees.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Create a troubleshooting page for common Airflow backfill failures in our analytics repository.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Lay out a three-stage migration from nightly pandas jobs on a single EC2 instance to partitioned Dagster assets on Kubernetes. Account for historical recomputation, data-quality gates, cost limits, lineage, dual-running, alert ownership, and rollback if the new Parquet outputs diverge from the current warehouse tables.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Implement incremental checkpoint loading in the PyTorch trainer so interrupted spot jobs resume optimizer, scheduler, scaler, sampler epoch, and RNG state.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Add a scrubber to the Android inference timeline that previews the selected audio window and remains usable with TalkBack.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Fix the port number in docker-compose.dev.yml","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Deduplicate the Snowflake query-building code shared by cohort_export and churn_features without changing generated SQL.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"The ONNX export produces plausible outputs on CPU but nonsense on TensorRT for batches larger than one. Diagnose which shape assumption is wrong.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Explain how the current ranking pipeline combines freshness, semantic similarity, and sponsored boosts, including where each score is normalized.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"The ONNX export produces plausible outputs on CPU but nonsense on TensorRT for batches larger than one. Diagnose which shape assumption is wrong.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Explain how the current ranking pipeline combines freshness, semantic similarity, and sponsored boosts, including where each score is normalized.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Schreibe einen kurzen Migrationsleitfaden für das neue dbt-Schema und erwähne die geänderten Modellnamen.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"de"} -{"prompt":"Architect a privacy-safe feedback loop for on-device recommendations. The proposal needs data minimization, consent boundaries, delayed labels, deletion propagation, experiment assignment, offline clients, abuse controls, and a way to measure model quality without centralizing raw interaction histories. Break delivery into independently reversible milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Architect a privacy-safe feedback loop for on-device recommendations. The proposal needs data minimization, consent boundaries, delayed labels, deletion propagation, experiment assignment, offline clients, abuse controls, and a way to measure model quality without centralizing raw interaction histories. Break delivery into independently reversible milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Write the Kafka consumer that compacts per-user embedding updates into S3 snapshots, tolerating duplicates and out-of-order messages.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Render model-comparison metrics as an accessible Compose table with sortable columns, sticky experiment names, and clear win/loss coloring.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Render model-comparison metrics as an accessible Compose table with sortable columns, sticky experiment names, and clear win/loss coloring.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Change CACHE_TTL_SECONDS from 300 to 600","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Separate annotation parsing from image decoding in dataset_loader.py while retaining the same Dataset API and sample ordering.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"A single malformed Avro record makes the Flink checkpoint grow forever instead of failing or moving to the dead-letter stream. Find out why.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Read the feature registry implementation and tell me whether aliases are resolved at registration time or lookup time. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Read the feature registry implementation and tell me whether aliases are resolved at registration time or lookup time. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Draft the deprecation notice for the v1 embeddings endpoint, including dates, affected SDK versions, and the replacement call.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Develop a capacity and failure-domain plan for serving the reranker in three regions. Include GPU bin-packing assumptions, cold starts, cross-region fallback, model-version skew, request shedding, SLOs, canary evaluation, and estimated headroom for a 4x traffic spike during catalog imports.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Add row-level lineage emission to the Spark enrichment job using the existing OpenLineage transport, with batching to avoid per-record network calls.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} @@ -8412,80 +8209,80 @@ {"prompt":"Pin numpy to 2.1.3 in requirements-lock.txt","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Flatten the nested evaluation config types and remove duplicate defaulting logic without changing accepted YAML or serialized run metadata.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Training accuracy drops only when gradient accumulation is set to 8; loss scaling and effective batch size look correct. Locate the hidden state or scheduler bug.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Why is normalize_query called twice in the search path? Determine whether both calls serve distinct purposes; the results are currently correct.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Turn the existing feature freshness logic into a plain-language operations note with one concrete stale-data example.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"Define the plan for adopting Iceberg tables in the events lake; implementation will happen in a later project.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Use the approved schema in specs/prediction-event.md to implement the Protobuf type, validation, and producer serialization.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Crée le panneau de comparaison des modèles avec les graphiques existants, un sélecteur de dataset et les états loading/error.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"fr"} -{"prompt":"Replace the dashboard title 'Modal Health' with 'Model Health'","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Rename prediction_score to ranking_score across Python, SQL, protobuf adapters, and dashboards while maintaining backward-compatible payload fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Why are validation examples duplicated after a worker restart? This is corrupting our metrics, and I don't know whether the sampler or checkpoint restore is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Why is normalize_query called twice in the search path? Determine whether both calls serve distinct purposes; the results are currently correct.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Turn the existing feature freshness logic into a plain-language operations note with one concrete stale-data example.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Define the plan for adopting Iceberg tables in the events lake; implementation will happen in a later project.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Use the approved schema in specs/prediction-event.md to implement the Protobuf type, validation, and producer serialization.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Crée le panneau de comparaison des modèles avec les graphiques existants, un sélecteur de dataset et les états loading/error.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"fr"} +{"prompt":"Replace the dashboard title 'Modal Health' with 'Model Health'","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename prediction_score to ranking_score across Python, SQL, protobuf adapters, and dashboards while maintaining backward-compatible payload fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Why are validation examples duplicated after a worker restart? This is corrupting our metrics, and I don't know whether the sampler or checkpoint restore is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Compare the two existing quantization paths and recommend which is safer for our mobile model, without implementing changes.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} {"prompt":"Write an architectural overview of the current feature ingestion path based on the repository, not a proposal for replacing it.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} {"prompt":"Design the migration to per-tenant vector indexes, then implement the tenant-routing layer and a guarded backfill command for the first pilot customer. Preserve shared-index reads during rollout, define measurable abort criteria, and leave destructive cleanup for a later phase.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} {"prompt":"Create the drift-detection worker and document the metric definitions operators will see in Grafana.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} {"prompt":"Implement the Android labeling queue UI, then add a short QA checklist covering gestures, rotation, and TalkBack.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"Correct the broken MLflow tracking URL and add a regression test that confirms the resolved URI used by dev runs.","purpose":"quickFix","secondary":"backendImpl","mixed":true,"difficulty":0.3,"slice":"mixed","lang":"en"} +{"prompt":"Correct the broken MLflow tracking URL and add a regression test that confirms the resolved URI used by dev runs.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Reorganize the batch-scoring package into reader, transform, and writer modules with identical outputs, then update its maintainer guide to explain the new boundaries.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Run 1182 failure excerpt:\n\n[ranker-eval] shard 23/64 complete\n[ranker-eval] shard 24/64 complete\n[ranker-eval] waiting for reducer barrier\n[worker-07] heartbeat timeout after 30000ms\n[worker-07] state=RUNNING rss=612MiB cpu=0.0%\n[coordinator] participants=64 arrived=63 generation=91\n[coordinator] retrying worker-07 assignment\n[worker-12] duplicate shard claim: 24\n\nThe job never exits, and cancel leaves the coordinator pod in Terminating until Kubernetes kills it. It happens roughly one run in twenty after enabling speculative execution. Find the protocol failure that strands the barrier and determine whether duplicate shard completion is involved. We need diagnosis first, not a timeout increase.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Run 1182 failure excerpt:\n\n[ranker-eval] shard 23/64 complete\n[ranker-eval] shard 24/64 complete\n[ranker-eval] waiting for reducer barrier\n[worker-07] heartbeat timeout after 30000ms\n[worker-07] state=RUNNING rss=612MiB cpu=0.0%\n[coordinator] participants=64 arrived=63 generation=91\n[coordinator] retrying worker-07 assignment\n[worker-12] duplicate shard claim: 24\n\nThe job never exits, and cancel leaves the coordinator pod in Terminating until Kubernetes kills it. It happens roughly one run in twenty after enabling speculative execution. Find the protocol failure that strands the barrier and determine whether duplicate shard completion is involved. We need diagnosis first, not a timeout increase.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} {"prompt":"PR excerpt:\n\nclass CachedFeatureReader:\n async def get(self, entity_id):\n cached = await self.cache.get(entity_id)\n if cached:\n return json.loads(cached)\n value = await self.store.fetch(entity_id)\n await self.cache.set(entity_id, json.dumps(value), ex=300)\n return value\n\nReviewer thread:\n- Does `if cached` incorrectly treat a valid empty payload as a miss?\n- Are simultaneous misses intentionally allowed to stampede the store?\n- What happens if serialization fails after fetch?\n- The cache client may return bytes or str depending on transport.\n\nReview this change for correctness and production risk. Do not rewrite it; I need concrete findings with severity and references to existing client behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} {"prompt":"Internal ticket DOC-771\n\nThe on-call channel keeps confusing three clocks:\n1. event_time from the mobile client\n2. ingested_at assigned by Kafka Connect\n3. materialized_at from the warehouse load\n\nCurrent runbook sentence: 'Freshness is the time since the event was received.' That wording is ambiguous and led someone to restart a healthy connector during a late mobile sync. Relevant alert names are FeatureEventLag, WarehouseMaterializationLag, and MobileSyncBacklog.\n\nRewrite the freshness section of docs/runbooks/features.md. Define each clock, map each alert to the correct interval, and include one diagnostic example. Keep it operational and under 500 words; no code changes.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} {"prompt":"Architecture request copied from Slack:\n\nMina 09:14 We can't keep rebuilding every customer index when the encoder changes.\nDev 09:16 Product wants old and new embeddings queryable during the two-week trial.\nSara 09:19 Storage says a full duplicate is 38 TB, budget allows about 12 TB temporary growth.\nMina 09:23 Mobile clients may send model_version for months; older clients send nothing.\nDev 09:28 Compliance needs tenant deletion to affect every retained representation within 24h.\n\nPlease turn this into a migration strategy for versioned embeddings. Resolve storage and compatibility constraints, specify read/write routing, deletion propagation, validation gates, and rollback. Break it into milestones and call out unanswered decisions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Story DATA-309\n\nGiven an input message:\n{\n \"account_id\": \"a17\",\n \"features\": {\"age_days\": 4, \"country\": \"NZ\"},\n \"observed_at\": \"2026-07-21T10:03:00Z\"\n}\n\nThe ingestion service must validate account_id, reject timestamps more than six hours in the future, attach schema_version=3, and publish to feature-events-v3. Duplicate messages share the X-Event-Id header and should acknowledge without republishing. Store idempotency records for 48 hours in Redis. Existing v2 handling stays intact behind its route.\n\nImplement the v3 consumer in services/feature-ingest, including metrics and tests for duplicates and future timestamps.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Make this screen nicer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"Tiny config thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"vague-eval","lang":"en"} +{"prompt":"Story DATA-309\n\nGiven an input message:\n{\n \"account_id\": \"a17\",\n \"features\": {\"age_days\": 4, \"country\": \"NZ\"},\n \"observed_at\": \"2026-07-21T10:03:00Z\"\n}\n\nThe ingestion service must validate account_id, reject timestamps more than six hours in the future, attach schema_version=3, and publish to feature-events-v3. Duplicate messages share the X-Event-Id header and should acknowledge without republishing. Store idempotency records for 48 hours in Redis. Existing v2 handling stays intact behind its route.\n\nImplement the v3 consumer in services/feature-ingest, including metrics and tests for duplicates and future timestamps.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Make this screen nicer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Tiny config thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} {"prompt":"Break the Rust linter crate into syntax, semantic, and reporting modules while keeping every diagnostic code, span, and command-line option stable.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"The dedicated game server leaks about 40 MB per completed match. Heap snapshots disagree about whether Lua closures or replay buffers retain it; isolate the owner.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Check the rollback logic in migrations/20260718_add_wallet_ledger.sql for lock duration and data-loss risk. Findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Check the rollback logic in migrations/20260718_add_wallet_ledger.sql for lock duration and data-loss risk. Findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Compose the changelog entry for the new cargo subcommand","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"Plan a zero-downtime replacement of our Redis-backed matchmaking queues with a NATS JetStream design. Cover ordering, redelivery, regional affinity, player cancellation races, draining old queues, observability, capacity tests, and rollback. Organize it as an RFC with milestones and explicit invariants; no implementation yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Implement a Rust parser for the replay container format, including checksum validation, unknown-chunk skipping, and streaming reads from stdin.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Create the Unreal inventory grid widget with drag-and-drop, stack counts, controller focus, tooltip placement, and split-stack feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement a Rust parser for the replay container format, including checksum validation, unknown-chunk skipping, and streaming reads from stdin.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create the Unreal inventory grid widget with drag-and-drop, stack counts, controller focus, tooltip placement, and split-stack feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Flip matchmaking_shadow to true in staging","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Merge the duplicated OAuth token validation paths in gateway and websocket-auth without altering accepted issuers or error responses.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Players occasionally spawn beneath the map after reconnecting during a zone transfer. Determine whether saved transforms, navmesh projection, or replication order is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Trace how the CLI resolves layered config from defaults, project files, environment variables, and flags. Explain precedence with examples but don't modify it.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Players occasionally spawn beneath the map after reconnecting during a zone transfer. Determine whether saved transforms, navmesh projection, or replication order is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Trace how the CLI resolves layered config from defaults, project files, environment variables, and flags. Explain precedence with examples but don't modify it.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Escreva a descrição do PR para a mudança de autenticação do launcher, incluindo riscos, testes e plano de rollback.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"pt"} {"prompt":"Outline a service boundary and migration roadmap for extracting player identity from the Java game monolith. Address session compatibility, account merges, ban enforcement, regional reads, event ownership, dual writes, failure recovery, and how existing clients continue authenticating throughout the rollout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Add PostgreSQL advisory locking to prevent two economy workers from settling the same match payout.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Style the Godot pause menu for ultrawide displays and make controller focus visible in both light and dark themes.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Style the Godot pause menu for ultrawide displays and make controller focus visible in both light and dark themes.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Update the copyright year","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Extract the deterministic RNG interface from combat simulation so tests and replay verification share one implementation, preserving generated sequences.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"After upgrading Netty, websocket clients disconnect under packet loss with 'unexpected continuation frame'. Find whether framing, compression, or retry behavior changed.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Does the existing loot sampler guarantee a result when all adjusted weights round to zero? Inspect code and tests; nothing has failed yet.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"After upgrading Netty, websocket clients disconnect under packet loss with 'unexpected continuation frame'. Find whether framing, compression, or retry behavior changed.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Does the existing loot sampler guarantee a result when all adjusted weights round to zero? Inspect code and tests; nothing has failed yet.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Prepare concise CLI help text for serverctl drain, including the timeout and force flags.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"Design a durable tournament scheduler for millions of brackets across time zones. Include state transitions, idempotent advancement, late score corrections, notification timing, shard ownership, disaster recovery, audit history, and staged delivery. Specify what belongs in PostgreSQL, the queue, and immutable event storage.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Design a durable tournament scheduler for millions of brackets across time zones. Include state transitions, idempotent advancement, late score corrections, notification timing, shard ownership, disaster recovery, audit history, and staged delivery. Specify what belongs in PostgreSQL, the queue, and immutable event storage.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.95,"slice":"core","lang":"en"} {"prompt":"Build the gRPC method that streams live match events with resume cursors and per-subscriber backpressure.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Implement the spectator HUD overlay with team colors, responsive safe areas, animated objective status, and a low-vision mode.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement the spectator HUD overlay with team colors, responsive safe areas, animated objective status, and a low-vision mode.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Change the default log level to info","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Move matchmaking rating math into a domain package and remove service-layer copies; all historical fixture outputs must remain exact.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"The headless server passes tests locally but freezes on shutdown in CI about 5% of runs. Find which task or thread is keeping it alive.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Describe what happens today when two guild leaders edit permissions simultaneously, based solely on the transaction code and isolation level.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Turn the comments in cmd/import_save.rs into a polished user-facing migration guide.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"Produce the implementation roadmap for replacing integer currency amounts with fixed-precision decimals across services and saved games.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Implement the already-approved lease protocol in the coordinator, including renewal, fencing tokens, and expired-owner rejection.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Add a small but complete toast component for saved loadouts, with stacking, dismissal animation, screen-reader announcements, and mobile placement.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Use port 7778 instead of 7777 in dev-server.json","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Rename guild_id to clan_id across the repository while preserving database column names and wire compatibility.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"为什么战斗回放在第 10,000 帧后开始漂移？线上结果是错的，但我们还不知道是浮点误差还是 RNG 状态丢失。","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"zh"} -{"prompt":"Why does SessionRegistry use weak references for spectators but strong references for players? Explain the current ownership choice; no bug has been observed.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Summarize the existing save-file upgrade sequence for the support handbook, including what users see on failure.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Plan the anti-cheat event pipeline, including trust boundaries and rollout phases; don't write the detectors yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"Turn the comments in cmd/import_save.rs into a polished user-facing migration guide.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Produce the implementation roadmap for replacing integer currency amounts with fixed-precision decimals across services and saved games.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement the already-approved lease protocol in the coordinator, including renewal, fencing tokens, and expired-owner rejection.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add a small but complete toast component for saved loadouts, with stacking, dismissal animation, screen-reader announcements, and mobile placement.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Use port 7778 instead of 7777 in dev-server.json","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename guild_id to clan_id across the repository while preserving database column names and wire compatibility.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"为什么战斗回放在第 10,000 帧后开始漂移？线上结果是错的，但我们还不知道是浮点误差还是 RNG 状态丢失。","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"zh"} +{"prompt":"Why does SessionRegistry use weak references for spectators but strong references for players? Explain the current ownership choice; no bug has been observed.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Summarize the existing save-file upgrade sequence for the support handbook, including what users see on failure.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Plan the anti-cheat event pipeline, including trust boundaries and rollout phases; don't write the detectors yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Implement the dedicated-server replay uploader with multipart resume support, then document its operator flags and failure modes.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Build the cross-platform friends panel and write a short visual QA checklist for mouse, touch, and controller input.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Fix the known off-by-one in MAX_PARTY_SIZE and update the server-side validation test that currently encodes the wrong limit.","purpose":"quickFix","secondary":"backendImpl","mixed":true,"difficulty":0.3,"slice":"mixed","lang":"en"} +{"prompt":"Fix the known off-by-one in MAX_PARTY_SIZE and update the server-side validation test that currently encodes the wrong limit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Restructure the save-game codecs without changing bytes on disk, then add a maintainer note describing the new module ownership.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Diagnose the zone-transfer duplication bug and prepare a brief incident summary covering impact, trigger, and mitigation after the cause is proven.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Patch under review:\n\ndiff --git a/server/economy/settle.go b/server/economy/settle.go\n@@\n- tx, err := db.BeginTx(ctx, nil)\n+ tx, err := db.BeginTx(ctx, &sql.TxOptions{Isolation: sql.LevelSerializable})\n@@\n- if err := creditWallet(tx, playerID, reward); err != nil {\n+ if err := creditWallet(tx, playerID, reward); err != nil && !errors.Is(err, ErrAlreadyCredited) {\n return err\n }\n\nThe author says serializable isolation plus swallowing ErrAlreadyCredited makes settlement idempotent. Review that claim against transaction retries, the payout unique key, rollback behavior, and how callers acknowledge queue messages. Do not edit the branch; give findings ordered by severity.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"チャットからの依頼:\n\nKen 11:02 新しい launcher token の仕様がコードだけにある\nAya 11:05 desktop は Authorization header、console は query param を使っている\nKen 11:08 有効期限は15分、refresh token は一回だけ使える\nAya 11:12 エラーコード AUTH_14 と AUTH_19 の違いが support に伝わっていない\n\nこの内容を docs/authentication.md にまとめてください。現在の挙動を説明し、desktop と console の例、token refresh の流れ、各エラーコードの意味を含める。実装変更は不要です。","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"ja"} -{"prompt":"Planning notes from ops review:\n\n- Current Redis queue peaks at 220k waiting players.\n- A regional outage can strand tickets whose owner heartbeat disappears.\n- Parties must never split across match assignments.\n- Skill buckets are recomputed every 30 seconds.\n- Product wants cross-region fallback after 45 seconds, but legal forbids two regions for the youth pool.\n- We can dual-publish for one week; clients cannot be updated first.\n\nCreate a migration plan to JetStream-based matchmaking. Define ownership and fencing, party atomicity, regional policy, shadow comparisons, rollout metrics, abort thresholds, and rollback. Identify which product and legal decisions remain unresolved.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Issue CLI-622\n\nCommand:\n$ arena-admin import-season --file season.json\n\nRequirements:\n- Stream the JSON array rather than loading the 6 GB file.\n- Validate season_id, bracket size, and RFC3339 timestamps.\n- Print rejected records to a separate JSONL file with line and reason.\n- Insert accepted records in batches of 500 inside retryable transactions.\n- SIGINT should finish the current transaction, write a checkpoint, and exit 130.\n- Rerunning from a checkpoint must not duplicate tournaments.\n- Existing small-file output remains unchanged.\n\nImplement this in cmd/import-season and add integration coverage using PostgreSQL.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"UI bug ticket:\n\nResolution: 3440x1440, UI scale 125%\nSteps:\n1. Open spectator mode.\n2. Expand the team roster.\n3. Trigger overtime.\n\nObserved: the objective timer overlaps the sixth player row and the bottom safe-area padding disappears. At 1920x1080 it looks correct. Design notes say the roster may show up to eight players and the timer must remain centered in the gameplay safe zone, not the full window. Rework SpectatorHUD.tscn constraints to support ultrawide and eight-player rosters. Preserve the current animation and 16:9 appearance.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"チャットからの依頼:\n\nKen 11:02 新しい launcher token の仕様がコードだけにある\nAya 11:05 desktop は Authorization header、console は query param を使っている\nKen 11:08 有効期限は15分、refresh token は一回だけ使える\nAya 11:12 エラーコード AUTH_14 と AUTH_19 の違いが support に伝わっていない\n\nこの内容を docs/authentication.md にまとめてください。現在の挙動を説明し、desktop と console の例、token refresh の流れ、各エラーコードの意味を含める。実装変更は不要です。","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"ja"} +{"prompt":"Planning notes from ops review:\n\n- Current Redis queue peaks at 220k waiting players.\n- A regional outage can strand tickets whose owner heartbeat disappears.\n- Parties must never split across match assignments.\n- Skill buckets are recomputed every 30 seconds.\n- Product wants cross-region fallback after 45 seconds, but legal forbids two regions for the youth pool.\n- We can dual-publish for one week; clients cannot be updated first.\n\nCreate a migration plan to JetStream-based matchmaking. Define ownership and fencing, party atomicity, regional policy, shadow comparisons, rollout metrics, abort thresholds, and rollback. Identify which product and legal decisions remain unresolved.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Issue CLI-622\n\nCommand:\n$ arena-admin import-season --file season.json\n\nRequirements:\n- Stream the JSON array rather than loading the 6 GB file.\n- Validate season_id, bracket size, and RFC3339 timestamps.\n- Print rejected records to a separate JSONL file with line and reason.\n- Insert accepted records in batches of 500 inside retryable transactions.\n- SIGINT should finish the current transaction, write a checkpoint, and exit 130.\n- Rerunning from a checkpoint must not duplicate tournaments.\n- Existing small-file output remains unchanged.\n\nImplement this in cmd/import-season and add integration coverage using PostgreSQL.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"UI bug ticket:\n\nResolution: 3440x1440, UI scale 125%\nSteps:\n1. Open spectator mode.\n2. Expand the team roster.\n3. Trigger overtime.\n\nObserved: the objective timer overlaps the sixth player row and the bottom safe-area padding disappears. At 1920x1080 it looks correct. Design notes say the roster may show up to eight players and the timer must remain centered in the gameplay safe zone, not the full window. Rework SpectatorHUD.tscn constraints to support ultrawide and eight-player rosters. Preserve the current animation and 16:9 appearance.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Tweak the known thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} {"prompt":"Clean up that subsystem","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"Something is busted again","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"Examine the Terraform module for our public API load balancer and flag privilege, exposure, state, and availability risks without applying changes.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Write the upgrade notes for PostgreSQL 18","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Write the upgrade notes for PostgreSQL 18","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Devise a phased plan to move secrets from Kubernetes manifests and CI variables into Vault. Include auth methods for workloads and developers, namespace ownership, rotation, emergency access, audit requirements, migration ordering, rollback, and how to detect applications still reading legacy secrets.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Implement a Kubernetes controller that reconciles TenantDatabase resources into roles, schemas, quotas, and rotation-ready credentials.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Create the web console for viewing deployment rollouts, with cluster filters, step timelines, log drawers, cancellation confirmation, and accessible status colors.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} @@ -8494,54 +8291,54 @@ {"prompt":"The API gateway returns intermittent 502s during pod scale-down even though readiness flips before SIGTERM handling finishes. Trace the race across Kubernetes, Envoy, and the Go server.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Tell me how the current Pulumi stack assigns CIDR blocks to preview environments and whether allocation is deterministic.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Redact a concise postmortem draft from the incident timeline in ops/incidents/2026-07-redis.md.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Lay out the architecture for active-active control planes in two regions. The design must cover leader election scope, eventual consistency, conflicting operator actions, database failover, certificate authorities, queue ownership, observability, chaos testing, and a staged migration from today's single-region deployment with clear retreat points.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Lay out the architecture for active-active control planes in two regions. The design must cover leader election scope, eventual consistency, conflicting operator actions, database failover, certificate authorities, queue ownership, observability, chaos testing, and a staged migration from today's single-region deployment with clear retreat points.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Add per-tenant concurrency limiting to the Java export service with fair queuing and metrics for throttled requests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Build a responsive secrets-audit page with virtualized results, severity filters, code-location links, and keyboard-friendly triage controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Build a responsive secrets-audit page with virtualized results, severity filters, code-location links, and keyboard-friendly triage controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Remove the stray comma in nginx.conf","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Consolidate repeated retry and circuit-breaker setup across the TypeScript service clients without changing thresholds or error propagation.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"A Terraform apply wants to replace the production NAT gateway after an unrelated tag edit. Determine which computed value is causing the forced replacement.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"A Terraform apply wants to replace the production NAT gateway after an unrelated tag edit. Determine which computed value is causing the forced replacement.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Ist die aktuelle mTLS-Konfiguration zwischen ingress und payments gegen Zertifikatswechsel robust? Bitte nur Code und Manifeste prüfen, nichts ändern.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"de"} {"prompt":"Prepare the operator runbook for draining a Kafka broker during maintenance, including verification and abort conditions.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Map a migration from per-service Prometheus installations to a managed metrics platform while retaining twelve months of query compatibility. Cover remote-write duplication, recording rules, dashboard ownership, cardinality controls, alert equivalence, cost validation, tenant isolation, cutover sequencing, and rollback if alert latency exceeds the SLO.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Implement the Python cleanup job that expires orphaned preview environments after checking active GitHub deployments and protected labels.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Design the user-visible maintenance banner component with scheduled countdowns, timezone-aware copy, dismissal rules, and mobile layout.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement the Python cleanup job that expires orphaned preview environments after checking active GitHub deployments and protected labels.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Design the user-visible maintenance banner component with scheduled countdowns, timezone-aware copy, dismissal rules, and mobile layout.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} {"prompt":"Bump the Alpine image from 3.21 to 3.22","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Rename internal package clusterutil to kubeclient across all Go modules, retaining compatibility wrappers for external imports.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Our cron controller creates duplicate jobs around the daylight-saving transition even though schedule IDs are unique. Diagnose the time calculation and reconciliation interaction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Analyze whether the current container-image promotion script can move an unscanned digest into production. No changes, just the control-flow and threat assessment.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Rewrite the README deployment section to match the current Argo CD workflow and remove obsolete Helm 2 instructions.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Rename internal package clusterutil to kubeclient across all Go modules, retaining compatibility wrappers for external imports.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Our cron controller creates duplicate jobs around the daylight-saving transition even though schedule IDs are unique. Diagnose the time calculation and reconciliation interaction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Analyze whether the current container-image promotion script can move an unscanned digest into production. No changes, just the control-flow and threat assessment.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Rewrite the README deployment section to match the current Argo CD workflow and remove obsolete Helm 2 instructions.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Propose a disaster-recovery roadmap for the customer metadata plane with a 15-minute RPO and one-hour RTO. Include dependency classification, cross-account backups, encryption keys, restore rehearsals, DNS and queue recovery, evidence collection, degraded-mode operation, ownership, and incremental milestones that can be validated before buying full standby capacity.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Add a server-side dry-run mode to infra-plan that resolves modules and policy checks but performs no cloud mutations.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Make the deployment diff viewer usable on narrow screens with synchronized scrolling, expandable unchanged sections, and a clear destructive-change treatment.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Change 'us_east_1' to 'us-east-1' in examples/aws.yaml","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Rename Environment to Workspace throughout the CLI, backend, SDKs, and tests while preserving config keys and API response fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Why does the health endpoint return 200 for thirty seconds after database connectivity is lost? This violates our readiness expectation; locate the unknown cause.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Why is forceNewDeployment always set on ECS updates? Explain the intended current behavior from history and tests; deployments are succeeding.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Rédige un résumé de l'architecture réseau actuelle pour le manuel d'astreinte; il faut expliquer les flux, pas proposer de changements.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"fr"} -{"prompt":"Create an implementation plan for migrating admission policies from Gatekeeper to ValidatingAdmissionPolicy, including inventory and compatibility testing.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"The ADR is final; implement its lease-fencing algorithm in the scheduler and persist epochs in PostgreSQL.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Give the log-level dropdown a searchable command-palette presentation with grouped options and persistent recent selections.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Swap the two mislabeled Grafana legend strings","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Make the deployment diff viewer usable on narrow screens with synchronized scrolling, expandable unchanged sections, and a clear destructive-change treatment.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Change 'us_east_1' to 'us-east-1' in examples/aws.yaml","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename Environment to Workspace throughout the CLI, backend, SDKs, and tests while preserving config keys and API response fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Why does the health endpoint return 200 for thirty seconds after database connectivity is lost? This violates our readiness expectation; locate the unknown cause.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Why is forceNewDeployment always set on ECS updates? Explain the intended current behavior from history and tests; deployments are succeeding.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Rédige un résumé de l'architecture réseau actuelle pour le manuel d'astreinte; il faut expliquer les flux, pas proposer de changements.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"fr"} +{"prompt":"Create an implementation plan for migrating admission policies from Gatekeeper to ValidatingAdmissionPolicy, including inventory and compatibility testing.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"The ADR is final; implement its lease-fencing algorithm in the scheduler and persist epochs in PostgreSQL.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Give the log-level dropdown a searchable command-palette presentation with grouped options and persistent recent selections.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Swap the two mislabeled Grafana legend strings","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Decouple cloud account discovery from policy evaluation without changing CLI output, then document the new extension point for provider authors.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Find the source of the etcd watch stall under compaction, apply the fix, and add a concise incident note explaining why our alarms missed it.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Find the source of the etcd watch stall under compaction, apply the fix, and add a concise incident note explaining why our alarms missed it.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Review the proposed multi-cluster credential flow for escalation paths and token leakage, then draft a security sign-off memo with your verdict.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Write the migration guide for the new deployment manifest and add a converter command that rewrites legacy YAML while preserving comments where possible.","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Plan and implement audit-log cold storage: decide partitioning, retention, and restore guarantees, then build the S3 writer behind a disabled feature flag.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"Incident excerpt:\n\n2026-07-29T02:14:08Z reconciler tenant=violet generation=183 desired=6 ready=5\n2026-07-29T02:14:08Z lease acquired holder=ctrl-7 epoch=991\n2026-07-29T02:14:09Z create replica id=r-6 request=4fd2\n2026-07-29T02:14:09Z lease acquired holder=ctrl-2 epoch=991\n2026-07-29T02:14:10Z create replica id=r-7 request=91aa\n2026-07-29T02:14:13Z status desired=6 actual=7\n\nBoth controllers believe they own epoch 991 after a brief PostgreSQL failover. The lease row has a unique primary key and transactions use READ COMMITTED. Determine how equal epochs became simultaneously valid and why request idempotency did not stop the extra replica. Provide the root cause and a reproducible test before patching.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Incident excerpt:\n\n2026-07-29T02:14:08Z reconciler tenant=violet generation=183 desired=6 ready=5\n2026-07-29T02:14:08Z lease acquired holder=ctrl-7 epoch=991\n2026-07-29T02:14:09Z create replica id=r-6 request=4fd2\n2026-07-29T02:14:09Z lease acquired holder=ctrl-2 epoch=991\n2026-07-29T02:14:10Z create replica id=r-7 request=91aa\n2026-07-29T02:14:13Z status desired=6 actual=7\n\nBoth controllers believe they own epoch 991 after a brief PostgreSQL failover. The lease row has a unique primary key and transactions use READ COMMITTED. Determine how equal epochs became simultaneously valid and why request idempotency did not stop the extra replica. Provide the root cause and a reproducible test before patching.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} {"prompt":"RFC diff excerpt:\n\n+ Agents obtain a regional token from the control plane.\n+ Tokens remain valid for 24 hours to tolerate outages.\n+ Any cluster in the organization may redeem the token.\n+ Revocation is propagated asynchronously through the audit stream.\n+ Bootstrap agents may skip audience validation for compatibility.\n\nContext: agents run in customer-controlled clusters, organizations can have separate regulated and unregulated regions, and the audit stream has a documented 20-minute delivery SLO. Review this existing proposal for authentication, replay, tenant-boundary, revocation, and downgrade risks. Return findings and open questions only; don't redesign or edit the RFC.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Docs request from support:\n\nCustomers see these statuses in the deployment API:\nQUEUED, VALIDATING, APPLYING, VERIFYING, SUCCEEDED, FAILED, ROLLING_BACK, ROLLED_BACK.\n\nConfusing cases:\n- FAILED can still transition to ROLLING_BACK.\n- cancellation during APPLYING is best-effort.\n- VERIFYING may last 30 minutes if health evidence is delayed.\n- a 409 from retry means the original request is still authoritative.\n\nUpdate docs/api/deployments.md with a state-transition explanation, retry guidance, and two curl examples. Keep the prose client-facing and avoid exposing internal queue names. No server changes are requested.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} -{"prompt":"Backlog synthesis:\n\nOPS-91: restore testing is manual and takes two engineers six hours.\nSEC-44: backup keys currently share an account with production keys.\nDB-208: cross-region snapshots lag between 20 and 70 minutes.\nSUP-18: customers need read-only access during regional recovery.\nFIN-73: a permanently warm secondary would exceed this year's budget.\n\nTurn these constraints into a disaster-recovery plan for the metadata service. Compare pilot-light and warm-standby options, define RPO/RTO tiers, key ownership, restore automation, degraded read paths, game days, milestones, and objective go/no-go criteria.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Feature request INFRA-1408\n\nPOST /v1/previews/{id}/extend\nBody: {\"hours\": 12}\n\nRules:\n- authenticated project members only\n- hours must be one of 1, 6, 12, 24\n- resulting expiry cannot exceed seven days from creation\n- return the unchanged preview on an idempotent retry\n- reject previews already deleting with 409\n- write PreviewExpiryExtended to the audit stream\n- update the Kubernetes expiry annotation asynchronously\n\nImplement the endpoint in services/environment-api using the existing command bus. Include authorization, idempotency, metrics, and transaction-level tests; do not change the UI.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Ship the visible part","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Docs request from support:\n\nCustomers see these statuses in the deployment API:\nQUEUED, VALIDATING, APPLYING, VERIFYING, SUCCEEDED, FAILED, ROLLING_BACK, ROLLED_BACK.\n\nConfusing cases:\n- FAILED can still transition to ROLLING_BACK.\n- cancellation during APPLYING is best-effort.\n- VERIFYING may last 30 minutes if health evidence is delayed.\n- a 409 from retry means the original request is still authoritative.\n\nUpdate docs/api/deployments.md with a state-transition explanation, retry guidance, and two curl examples. Keep the prose client-facing and avoid exposing internal queue names. No server changes are requested.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Backlog synthesis:\n\nOPS-91: restore testing is manual and takes two engineers six hours.\nSEC-44: backup keys currently share an account with production keys.\nDB-208: cross-region snapshots lag between 20 and 70 minutes.\nSUP-18: customers need read-only access during regional recovery.\nFIN-73: a permanently warm secondary would exceed this year's budget.\n\nTurn these constraints into a disaster-recovery plan for the metadata service. Compare pilot-light and warm-standby options, define RPO/RTO tiers, key ownership, restore automation, degraded read paths, game days, milestones, and objective go/no-go criteria.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Feature request INFRA-1408\n\nPOST /v1/previews/{id}/extend\nBody: {\"hours\": 12}\n\nRules:\n- authenticated project members only\n- hours must be one of 1, 6, 12, 24\n- resulting expiry cannot exceed seven days from creation\n- return the unchanged preview on an idempotent retry\n- reject previews already deleting with 409\n- write PreviewExpiryExtended to the audit stream\n- update the Kubernetes expiry annotation asynchronously\n\nImplement the endpoint in services/environment-api using the existing command bus. Include authorization, idempotency, metrics, and transaction-level tests; do not change the UI.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Ship the visible part","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"Do the obvious cleanup","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} {"prompt":"Design a migration from our single PostgreSQL primary to tenant-partitioned clusters. Cover routing metadata, transaction boundaries, cross-tenant admin queries, connection pooling, backup/restore, replica lag, dual writes, tenant moves, observability, rollback, and milestones that let us validate the largest tenants before broad cutover.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Add cursor-based pagination to the audit-events endpoint, including stable ordering when multiple events share a timestamp.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Build the React account-switcher popover with search, recent workspaces, keyboard navigation, and a loading skeleton.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Bump Prisma to 6.12","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Extract SQL filter construction from UserRepository into reusable query specifications without changing generated queries or result ordering.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"The checkout API sometimes returns an empty order after a successful commit. Find the race between the write transaction and replica read.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"The checkout API sometimes returns an empty order after a successful commit. Find the race between the write transaction and replica read.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Inspect the row-level security policies for tenant escape paths","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Draft the v4 API migration guide","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Draft the v4 API migration guide","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Lay out an RFC for replacing integer invoice IDs with opaque sortable identifiers across PostgreSQL, Kafka events, public APIs, SDKs, exports, and support tooling. Include collision guarantees, index effects, compatibility with bookmarked URLs, backfill strategy, dual-read duration, rollback conditions, and an incremental delivery sequence. Do not implement it yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Implement bulk user suspension with per-user authorization checks and idempotent audit events","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Create the SwiftUI subscription-management screen with plan cards, renewal details, cancellation flow, error states, and VoiceOver labels.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} @@ -8549,126 +8346,125 @@ {"prompt":"Consolidate the duplicate transaction retry loops in billing and ledger while preserving retry counts, jitter, and surfaced errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Why does the SQLite cache report database locked only when the iOS app returns from background? Reproduce and locate the unclosed transaction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Explain how ApiKeyAuthenticator selects a tenant when both the hostname and key metadata contain tenant IDs. No code changes.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Write doc comments for the public QueryBuilder methods","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} -{"prompt":"Plan the retirement of our legacy REST search endpoint. Account for mobile clients that may remain offline for months, saved integrations, SDK release timing, usage telemetry, customer communication, compatibility shims, rate-limit differences, and a reversible sequence from deprecation headers through final shutdown.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Write doc comments for the public QueryBuilder methods","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Plan the retirement of our legacy REST search endpoint. Account for mobile clients that may remain offline for months, saved integrations, SDK release timing, usage telemetry, customer communication, compatibility shims, rate-limit differences, and a reversible sequence from deprecation headers through final shutdown.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Add a transactional outbox publisher for customer-profile changes using the existing Debezium connector.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Implement the responsive invoice table with sticky totals, column visibility controls, empty states, and accessible sorting.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Set minimum iOS to 17.0","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Move date-range validation into the domain layer while keeping every API status code and validation message unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Production queries against customer_notes became 40x slower after yesterday's migration, but EXPLAIN differs between replicas. Determine why the planner stopped using the partial index.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Is the current refresh-token rotation logic safe against two simultaneous refresh requests? Analyze code and tests only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Is the current refresh-token rotation logic safe against two simultaneous refresh requests? Analyze code and tests only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} {"prompt":"Escribe una página de referencia para los filtros del endpoint de transacciones, con ejemplos de curl y respuestas de error.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} -{"prompt":"Propose the architecture for an append-only financial ledger that can support corrections, historical balance reconstruction, multi-currency amounts, idempotent imports, and independent reconciliation. Compare partitioning choices, define invariants, identify ownership boundaries, and split delivery into milestones that avoid a big-bang replacement of the current balance table.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} -{"prompt":"Build the GraphQL mutation that merges duplicate contacts and rewrites dependent ownership records atomically.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Propose the architecture for an append-only financial ledger that can support corrections, historical balance reconstruction, multi-currency amounts, idempotent imports, and independent reconciliation. Compare partitioning choices, define invariants, identify ownership boundaries, and split delivery into milestones that avoid a big-bang replacement of the current balance table.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Build the GraphQL mutation that merges duplicate contacts and rewrites dependent ownership records atomically.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Add an animated conflict-resolution sheet to the macOS app for records edited both locally and remotely.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Change the Settings icon from 18px to 20px; the component and desired value are already identified.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Rename AccountRecord to CustomerRecord across the repository while retaining table names, serialized keys, and public SDK types.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Why are deleted comments reappearing after an offline iPad sync? The source of truth is unclear and the resurrection is corrupting customer records.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"Change the Settings icon from 18px to 20px; the component and desired value are already identified.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename AccountRecord to CustomerRecord across the repository while retaining table names, serialized keys, and public SDK types.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Why are deleted comments reappearing after an offline iPad sync? The source of truth is unclear and the resurrection is corrupting customer records.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Why does SearchRepository issue two count queries for exported reports? Determine whether both are required by the existing behavior; nothing is failing.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Document the current webhook signature scheme, including canonicalization, timestamp tolerance, key rotation, and verification examples. Do not alter the verifier.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Prepare a design for introducing soft deletion to shared folders, with retention, restore, purge, indexing, and audit implications.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"The OpenAPI contract is approved. Implement PATCH /v2/customers/{id} with ETag preconditions and field-level authorization.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Add a compact date picker to the report toolbar with presets, custom ranges, validation feedback, and mobile behavior.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Document the current webhook signature scheme, including canonicalization, timestamp tolerance, key rotation, and verification examples. Do not alter the verifier.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Prepare a design for introducing soft deletion to shared folders, with retention, restore, purge, indexing, and audit implications.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"The OpenAPI contract is approved. Implement PATCH /v2/customers/{id} with ETag preconditions and field-level authorization.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add a compact date picker to the report toolbar with presets, custom ranges, validation feedback, and mobile behavior.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Rename `reciever` to `receiver` in SyncEnvelope.swift","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Split CustomerService into command and query collaborators, preserving transactions, emitted events, and all externally visible behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Diagnose the unknown duplicate-charge path, implement the correction once the cause is proven, and add a regression test around the triggering interleaving.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Split CustomerService into command and query collaborators, preserving transactions, emitted events, and all externally visible behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Diagnose the unknown duplicate-charge path, implement the correction once the cause is proven, and add a regression test around the triggering interleaving.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Audit the existing database-encryption key rotation flow, then write a security review memo with findings and unresolved assumptions.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Produce the webhook integration guide and add a small Node.js verification utility that customers can run against captured requests.","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Produce the webhook integration guide and add a small Node.js verification utility that customers can run against captured requests.","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} {"prompt":"Design and implement the first stage of organization merges: specify invariants and rollback rules, then build the dry-run analyzer behind an admin-only flag.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"Implement the audit-log export endpoint and add a client-facing reference section describing pagination, limits, and error responses.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Product ticket WEB-2481\n\nThe customer detail page currently uses a desktop-only two-column layout. On a 390px viewport the activity timeline falls below six dense metadata panels, so users scroll several screens before seeing recent events.\n\nDesired behavior:\n- On phones, show name, status, and primary actions first.\n- Put secondary metadata in a collapsed Details section.\n- Keep the activity timeline immediately below the header.\n- The action menu must remain reachable at 200% zoom.\n- Tablet and desktop layouts should not visually regress.\n- Loading and permission-denied states need the same hierarchy.\n\nImplement the responsive layout in CustomerDetailPage.tsx using existing primitives and tokens. No API changes.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Implement the audit-log export endpoint and add a client-facing reference section describing pagination, limits, and error responses.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Product ticket WEB-2481\n\nThe customer detail page currently uses a desktop-only two-column layout. On a 390px viewport the activity timeline falls below six dense metadata panels, so users scroll several screens before seeing recent events.\n\nDesired behavior:\n- On phones, show name, status, and primary actions first.\n- Put secondary metadata in a collapsed Details section.\n- Keep the activity timeline immediately below the header.\n- The action menu must remain reachable at 200% zoom.\n- Tablet and desktop layouts should not visually regress.\n- Loading and permission-denied states need the same hierarchy.\n\nImplement the responsive layout in CustomerDetailPage.tsx using existing primitives and tokens. No API changes.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Release build output:\n\nwarning: marketing version 8.3 does not match release metadata 8.3.1\nArchive succeeded\nUploading symbols...\nerror: expected dSYM at build/Release/AppStore/Atlas.dSYM\nnote: archive output is build/archive/Atlas.xcarchive/dSYMs/Atlas.app.dSYM\n\nWorkflow excerpt:\n SYMBOL_PATH: build/Release/AppStore/Atlas.dSYM\n run: scripts/upload-symbols \"$SYMBOL_PATH\"\n\nThe archive layout changed in Xcode 18. Set SYMBOL_PATH to the exact new path shown above. This is a known path correction; don't modify the upload script or archive settings.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"pasted-context","lang":"en"} -{"prompt":"Cleanup notes:\n\npackages/data-access/src/customerRepo.ts owns SQL construction, row mapping, cache invalidation, analytics emission, and email-trigger decisions. `customerRepo.test.ts` mocks twelve unrelated services, and the same row-to-domain conversion exists in the export worker.\n\nTarget boundaries:\n- persistence: SQL plus row mapping\n- application: mutation orchestration\n- observers: analytics and email triggers\n\nSeparate these responsibilities and share the mapper with export-worker. Preserve public repository methods, transaction scope, emitted events, and query text snapshots. This work must not alter customer behavior or database schema.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Crash excerpt from iPad sync:\n\nFatal error: Duplicate keys of type 'RecordID' were found in a Dictionary\n0 Swift._assertionFailure\n1 Dictionary.init(uniqueKeysWithValues:)\n2 SyncBatch.coalesceChanges()\n3 SyncCoordinator.applyRemoteBatch()\n\nLog tail:\nremote batch cursor=991 count=84\nlocal pending count=3\ncoalesce record=72D op=update\ncoalesce record=72D op=delete\nnetwork retry response duplicated request-id=af31\n\nIt occurs only after the app reconnects through a captive portal. We don't know whether the server sends duplicates or the retry layer replays a batch. Identify the source and the correct coalescing semantics before patching.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Diff to assess:\n\ndiff --git a/db/migrations/20260729_email_unique.sql b/db/migrations/20260729_email_unique.sql\n+UPDATE users SET email = lower(trim(email));\n+CREATE UNIQUE INDEX CONCURRENTLY users_email_unique\n+ON users (tenant_id, email)\n+WHERE deleted_at IS NULL;\n\ndiff --git a/services/users/find.ts b/services/users/find.ts\n-return db.one('SELECT * FROM users WHERE email = $1', [email]);\n+return db.one('SELECT * FROM users WHERE lower(email) = lower($1)', [email]);\n\nReview locking, duplicate handling, failed concurrent index recovery, query-index compatibility, and tenant scoping. Do not edit the migration; return specific findings and required preflight checks.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Write up the API stuff","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Cleanup notes:\n\npackages/data-access/src/customerRepo.ts owns SQL construction, row mapping, cache invalidation, analytics emission, and email-trigger decisions. `customerRepo.test.ts` mocks twelve unrelated services, and the same row-to-domain conversion exists in the export worker.\n\nTarget boundaries:\n- persistence: SQL plus row mapping\n- application: mutation orchestration\n- observers: analytics and email triggers\n\nSeparate these responsibilities and share the mapper with export-worker. Preserve public repository methods, transaction scope, emitted events, and query text snapshots. This work must not alter customer behavior or database schema.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Crash excerpt from iPad sync:\n\nFatal error: Duplicate keys of type 'RecordID' were found in a Dictionary\n0 Swift._assertionFailure\n1 Dictionary.init(uniqueKeysWithValues:)\n2 SyncBatch.coalesceChanges()\n3 SyncCoordinator.applyRemoteBatch()\n\nLog tail:\nremote batch cursor=991 count=84\nlocal pending count=3\ncoalesce record=72D op=update\ncoalesce record=72D op=delete\nnetwork retry response duplicated request-id=af31\n\nIt occurs only after the app reconnects through a captive portal. We don't know whether the server sends duplicates or the retry layer replays a batch. Identify the source and the correct coalescing semantics before patching.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Diff to assess:\n\ndiff --git a/db/migrations/20260729_email_unique.sql b/db/migrations/20260729_email_unique.sql\n+UPDATE users SET email = lower(trim(email));\n+CREATE UNIQUE INDEX CONCURRENTLY users_email_unique\n+ON users (tenant_id, email)\n+WHERE deleted_at IS NULL;\n\ndiff --git a/services/users/find.ts b/services/users/find.ts\n-return db.one('SELECT * FROM users WHERE email = $1', [email]);\n+return db.one('SELECT * FROM users WHERE lower(email) = lower($1)', [email]);\n\nReview locking, duplicate handling, failed concurrent index recovery, query-index compatibility, and tenant scoping. Do not edit the migration; return specific findings and required preflight checks.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Write up the API stuff","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} {"prompt":"Sort out the migration approach","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"Finish the data layer","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"Create a visionOS attachment browser with spatial cards, selection feedback, progressive image loading, and an accessible flat fallback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Update Kotlin to 2.2.0","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Move push-notification payload parsing into a platform-neutral module while preserving Android and iOS behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Move push-notification payload parsing into a platform-neutral module while preserving Android and iOS behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"The Android app freezes when rotating during biometric authentication. Determine which lifecycle callback or coroutine is blocking the main thread.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Check whether the current Swift actor isolation around DownloadRegistry actually prevents duplicate downloads. Explanation only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Check whether the current Swift actor isolation around DownloadRegistry actually prevents duplicate downloads. Explanation only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Write App Store release notes for offline maps","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"Develop a roadmap for unifying authentication across our iOS, Android, web, and desktop clients. Address passkeys, legacy password sessions, device binding, refresh-token storage, account recovery, staged SDK adoption, server compatibility, telemetry, and rollback. Separate prerequisite platform work from user-visible rollout milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Add device-bound refresh tokens to the Kotlin authentication service with rotation and replay detection.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Implement the Compose download manager screen with per-item progress, pause controls, storage warnings, and TalkBack support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Change `adressLine` to `addressLine` in one DTO","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Consolidate three nearly identical iOS sheet coordinators without changing presentation order, dismissal callbacks, or deep-link behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Push registration succeeds, but some devices never receive silent notifications after restoring from backup. Find where the token/account association goes stale.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Push registration succeeds, but some devices never receive silent notifications after restoring from backup. Find where the token/account association goes stale.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Walk through how the app decides between cached, bundled, and downloaded map tiles when offline.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Rédige la documentation utilisateur pour activer les passkeys dans l'application iOS, avec les cas de récupération de compte.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"fr"} -{"prompt":"Architect a shared offline mutation engine for mobile clients. The design should cover durable queues, dependency ordering, optimistic UI, server-assigned identifiers, conflict resolution, encryption at rest, background execution limits, partial authentication loss, schema evolution, diagnostics, and an adoption path that does not require rewriting every feature at once.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} -{"prompt":"Implement an idempotent endpoint that accepts batched mobile mutations and returns per-operation conflict metadata.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Architect a shared offline mutation engine for mobile clients. The design should cover durable queues, dependency ordering, optimistic UI, server-assigned identifiers, conflict resolution, encryption at rest, background execution limits, partial authentication loss, schema evolution, diagnostics, and an adoption path that does not require rewriting every feature at once.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement an idempotent endpoint that accepts batched mobile mutations and returns per-operation conflict metadata.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Build the macOS command-palette window with fuzzy results, grouped actions, keyboard-only operation, and multi-display positioning.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Set the Android target SDK to 36","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Extract image cache eviction policy from the UIKit view controller while keeping memory and disk behavior identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"An async image cell occasionally shows the previous user's avatar after rapid scrolling. Trace the cancellation or reuse bug.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Evaluate the current keychain access-group setup for accidental credential sharing between the production app and extensions.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Evaluate the current keychain access-group setup for accidental credential sharing between the production app and extensions.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Prepare a README section for running UI tests on Android emulators and iOS simulators.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Define a phased migration from our custom mobile analytics SDK to OpenTelemetry. Include event compatibility, batching, offline retention, privacy controls, sampling, battery impact, crash-path behavior, backend ingestion changes, dashboard validation, SDK release sequencing, and criteria for disabling the legacy uploader.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Create the server endpoint for registering passkey credentials, including attestation validation and duplicate-credential protection.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Add a Dynamic Type-friendly onboarding carousel with reduced-motion behavior and restored progress after relaunch.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Create the server endpoint for registering passkey credentials, including attestation validation and duplicate-credential protection.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add a Dynamic Type-friendly onboarding carousel with reduced-motion behavior and restored progress after relaunch.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Correct the German localization key for Settings","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Separate Bluetooth scanning state from the Compose screen model, keeping device ordering and all displayed states unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"The macOS app's CPU usage climbs to 100% after the system clock moves backward. Identify the timer or retry loop responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Explain why BackgroundSyncScheduler requests both processing and refresh tasks, and what each currently handles.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Document the deep-link URL formats and examples for support engineers","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Sketch a rollout strategy for end-to-end encrypted shared notes across four clients, including key distribution, member removal, device recovery, search limitations, old-client behavior, migration of existing notes, telemetry boundaries, and staged validation. Call out which product choices must be settled before implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Sketch a rollout strategy for end-to-end encrypted shared notes across four clients, including key distribution, member removal, device recovery, search limitations, old-client behavior, migration of existing notes, telemetry boundaries, and staged validation. Call out which product choices must be settled before implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Add resumable media uploads to the Swift networking package using server-issued offsets and persisted task metadata.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Create the foldable layout for the Android conversation screen, with adaptive panes and seamless posture transitions.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Turn off FEATURE_NEW_COMPOSER in beta","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Rename SyncItem to PendingMutation throughout mobile shared code while preserving database entity names and serialized payloads.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Biometric unlock sometimes accepts and immediately returns to the locked screen. Diagnose the state transition; the trigger is not understood.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Review how the app currently redacts notification content on locked devices across each privacy setting.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Write a developer guide to the existing mobile sync protocol, based on code rather than proposing a new protocol.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Plan the conversion from callback-based iOS networking to async/await, including sequencing and compatibility with extensions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Implement the finalized notification-preferences contract in the API and mobile shared client.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Créer la vue SwiftUI des appareils connectés avec recherche, suppression, états hors ligne et support VoiceOver.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"fr"} -{"prompt":"Change the spinner tint to AccentColor in LoginView.swift","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Reorganize navigation routes by feature without changing deep links, back-stack behavior, or analytics names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Why are location updates delayed by minutes only after Low Power Mode is toggled? The app's tracking is broken and we don't know which OS interaction causes it.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Determine why the existing Android database uses a deferred foreign key for attachment rows; no failure is being reported.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Summarize the current account-recovery flow into support-facing prose, including states and escalation points.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Produce the architecture and milestone plan for moving mobile feature flags to signed local snapshots.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"Rename SyncItem to PendingMutation throughout mobile shared code while preserving database entity names and serialized payloads.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Biometric unlock sometimes accepts and immediately returns to the locked screen. Diagnose the state transition; the trigger is not understood.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Review how the app currently redacts notification content on locked devices across each privacy setting.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Write a developer guide to the existing mobile sync protocol, based on code rather than proposing a new protocol.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Plan the conversion from callback-based iOS networking to async/await, including sequencing and compatibility with extensions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement the finalized notification-preferences contract in the API and mobile shared client.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Créer la vue SwiftUI des appareils connectés avec recherche, suppression, états hors ligne et support VoiceOver.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"fr"} +{"prompt":"Change the spinner tint to AccentColor in LoginView.swift","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Reorganize navigation routes by feature without changing deep links, back-stack behavior, or analytics names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Why are location updates delayed by minutes only after Low Power Mode is toggled? The app's tracking is broken and we don't know which OS interaction causes it.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Determine why the existing Android database uses a deferred foreign key for attachment rows; no failure is being reported.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Summarize the current account-recovery flow into support-facing prose, including states and escalation points.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Produce the architecture and milestone plan for moving mobile feature flags to signed local snapshots.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Implement the device-revocation service and document the endpoint, token effects, and expected client recovery behavior.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Build the iOS diagnostics screen and add a support article explaining how users export and share its bundle.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"Update the known-wrong callback URL and adjust the endpoint test that still expects the old value.","purpose":"quickFix","secondary":"backendImpl","mixed":true,"difficulty":0.3,"slice":"mixed","lang":"en"} +{"prompt":"Update the known-wrong callback URL and adjust the endpoint test that still expects the old value.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"Split the mobile session package into storage, refresh, and policy modules with identical behavior, then write a maintainer overview of the new structure.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Investigate the notification duplication regression, fix the underlying cause, and add a short release-note entry once verified.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Pull request excerpt:\n\nfinal class SessionVault {\n private var cached: Session?\n func session() async throws -> Session {\n if let cached { return cached }\n let stored = try await keychain.load()\n cached = stored\n return stored\n }\n func clear() async throws {\n try await keychain.delete()\n cached = nil\n }\n}\n\nThe type is marked @MainActor in the full file. Background extensions call session() through an async protocol. Review whether actor isolation, cache lifetime, keychain errors, and concurrent clear/read operations produce security or correctness risks. Do not change the code; provide findings with concrete interleavings.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Documentation ticket MOB-900\n\nThe app stores offline work in three places:\n- PendingMutation.sqlite for unsent edits\n- MediaQueue/ for attachment bytes\n- LastSnapshot.bin for server state\n\nSupport currently tells users that signing out 'removes cached data,' but the implementation retains MediaQueue files for seven days to support account recovery. Removing the app clears everything; revoking a device remotely prevents upload but does not immediately erase local files.\n\nRewrite docs/privacy/offline-data.md to state exactly what is retained for sign-out, device revocation, account deletion, and app removal. Keep the tone user-facing and avoid promising OS-level secure deletion.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} -{"prompt":"Notes from mobile architecture sync:\n\n- iOS has 14 callback-based service protocols.\n- Three are consumed by widgets that cannot adopt the newest deployment target yet.\n- Android shared code expects cancellation to propagate into native calls.\n- Analytics records operation start and completion IDs.\n- A previous async wrapper double-resumed continuations on cancellation.\n- Product wants feature teams migrating independently.\n\nCreate a staged async/await adoption plan. Define adapter boundaries, cancellation semantics, continuation safety checks, testing, telemetry compatibility, sequencing for widgets, and removal criteria for legacy protocols. No implementation in this task.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Backend story AUTH-1932\n\nPOST /v2/devices/revoke\nRequest: { device_id, reason }\n\nRules:\n- the device must belong to the authenticated account\n- revoking the current device requires recent reauthentication\n- all refresh-token families issued to that device become invalid\n- access tokens remain valid for at most five minutes\n- repeated requests return the original revocation result\n- publish DeviceRevoked after commit\n- audit reason is restricted to enum values lost, sold, compromised, other\n\nImplement the handler, transaction, token-family invalidation, outbox event, and integration tests. The mobile UI is out of scope.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Design handoff copied from ticket:\n\nScreen: Downloads\nStates: empty, active, paused, failed, storage-low\nRows show title, thumbnail, progress, remaining bytes, and one primary action.\nSwipe actions are delete and retry. On tablets the queue and selected item details appear side by side. At accessibility text sizes, thumbnails may shrink but controls cannot. Progress changes should not cause VoiceOver to reread the whole row. Product wants the storage warning pinned above active downloads.\n\nImplement this screen in Jetpack Compose using the existing DownloadViewModel. Do not change queue behavior or networking.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Make the app screen pop","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"Fix that small constant","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"vague-eval","lang":"en"} +{"prompt":"Investigate the notification duplication regression, fix the underlying cause, and add a short release-note entry once verified.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Pull request excerpt:\n\nfinal class SessionVault {\n private var cached: Session?\n func session() async throws -> Session {\n if let cached { return cached }\n let stored = try await keychain.load()\n cached = stored\n return stored\n }\n func clear() async throws {\n try await keychain.delete()\n cached = nil\n }\n}\n\nThe type is marked @MainActor in the full file. Background extensions call session() through an async protocol. Review whether actor isolation, cache lifetime, keychain errors, and concurrent clear/read operations produce security or correctness risks. Do not change the code; provide findings with concrete interleavings.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Documentation ticket MOB-900\n\nThe app stores offline work in three places:\n- PendingMutation.sqlite for unsent edits\n- MediaQueue/ for attachment bytes\n- LastSnapshot.bin for server state\n\nSupport currently tells users that signing out 'removes cached data,' but the implementation retains MediaQueue files for seven days to support account recovery. Removing the app clears everything; revoking a device remotely prevents upload but does not immediately erase local files.\n\nRewrite docs/privacy/offline-data.md to state exactly what is retained for sign-out, device revocation, account deletion, and app removal. Keep the tone user-facing and avoid promising OS-level secure deletion.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} +{"prompt":"Notes from mobile architecture sync:\n\n- iOS has 14 callback-based service protocols.\n- Three are consumed by widgets that cannot adopt the newest deployment target yet.\n- Android shared code expects cancellation to propagate into native calls.\n- Analytics records operation start and completion IDs.\n- A previous async wrapper double-resumed continuations on cancellation.\n- Product wants feature teams migrating independently.\n\nCreate a staged async/await adoption plan. Define adapter boundaries, cancellation semantics, continuation safety checks, testing, telemetry compatibility, sequencing for widgets, and removal criteria for legacy protocols. No implementation in this task.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Backend story AUTH-1932\n\nPOST /v2/devices/revoke\nRequest: { device_id, reason }\n\nRules:\n- the device must belong to the authenticated account\n- revoking the current device requires recent reauthentication\n- all refresh-token families issued to that device become invalid\n- access tokens remain valid for at most five minutes\n- repeated requests return the original revocation result\n- publish DeviceRevoked after commit\n- audit reason is restricted to enum values lost, sold, compromised, other\n\nImplement the handler, transaction, token-family invalidation, outbox event, and integration tests. The mobile UI is out of scope.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Design handoff copied from ticket:\n\nScreen: Downloads\nStates: empty, active, paused, failed, storage-low\nRows show title, thumbnail, progress, remaining bytes, and one primary action.\nSwipe actions are delete and retry. On tablets the queue and selected item details appear side by side. At accessibility text sizes, thumbnails may shrink but controls cannot. Progress changes should not cause VoiceOver to reread the whole row. Product wants the storage warning pinned above active downloads.\n\nImplement this screen in Jetpack Compose using the existing DownloadViewModel. Do not change queue behavior or networking.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Make the app screen pop","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"Separate physics integration from entity iteration in the ECS engine while preserving deterministic replay hashes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"The robotics simulator drifts from recorded hardware motion after exactly 65,536 ticks. Find the overflow or precision error.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"The robotics simulator drifts from recorded hardware motion after exactly 65,536 ticks. Find the overflow or precision error.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Assess the lock-free ring buffer for memory-ordering bugs on ARM64. Do not modify it.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Write the README for the new map compiler","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Plan a migration from our custom scene format to glTF while preserving engine-specific metadata, deterministic asset builds, patch compatibility, editor workflows, and old saved projects. Include conversion validation, dual-format support, rollout milestones, rollback, and a strategy for plugins that currently deserialize the old binary format directly.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Write the README for the new map compiler","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Plan a migration from our custom scene format to glTF while preserving engine-specific metadata, deterministic asset builds, patch compatibility, editor workflows, and old saved projects. Include conversion validation, dual-format support, rollout milestones, rollback, and a strategy for plugins that currently deserialize the old binary format directly.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} {"prompt":"Implement hierarchical pathfinding over streamed world chunks with cancellation and bounded memory.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Create the Unity crafting panel with drag targets, recipe filtering, controller navigation, and animated success feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Change MAX_DRONES from 12 to 16","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Unify the duplicated quaternion conversion helpers in importer and runtime without changing floating-point outputs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Our ESP32 controller reboots only when Wi-Fi reconnects while both motors are active. Diagnose whether power, watchdog timing, or a driver race is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Our ESP32 controller reboots only when Wi-Fi reconnects while both motors are active. Diagnose whether power, watchdog timing, or a driver race is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Explain how the current asset cooker decides which textures belong in a shared bundle.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Escreva as notas de versão do firmware 5.4, incluindo o novo modo de calibração e os problemas conhecidos.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"pt"} {"prompt":"Develop a safety architecture for remote robot commands over unreliable networks. Define authority, command expiry, sequencing, emergency-stop behavior, offline autonomy boundaries, authentication, auditability, simulator validation, degraded modes, rollout stages, and the evidence required before enabling commands outside a test fleet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} -{"prompt":"Add a Rust command scheduler that rejects stale actuator commands and persists monotonic sequence state across restarts.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add a Rust command scheduler that rejects stale actuator commands and persists monotonic sequence state across restarts.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Build the Godot controller-remapping screen with conflict warnings, input capture, reset controls, and localization-safe layout.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Pin arm-none-eabi-gcc to 14.2","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Extract collision layer rules into a data-driven table while preserving all existing interactions and replay results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Extract collision layer rules into a data-driven table while preserving all existing interactions and replay results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Audio crackles after several scene reloads, and the number of active OpenAL sources keeps rising. Locate the resource lifetime bug.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Check whether the current bootloader validates image length before hashing and flashing. Report security findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Prepare a hardware setup guide for the RP2350 debug probe","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Prepare a hardware setup guide for the RP2350 debug probe","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Outline a roadmap for bringing deterministic multiplayer to the existing single-player simulation. Address tick ownership, input delay, rollback state, floating-point differences, bandwidth, cheating boundaries, replay compatibility, debugging tools, staged prototypes, and criteria for choosing rollback versus lockstep before production work begins.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Implement delta-compressed snapshot serialization for the C++ server with golden-vector tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Add an in-game telemetry graph overlay with zoom, series toggles, frame-time thresholds, and gamepad focus.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Implement delta-compressed snapshot serialization for the C++ server with golden-vector tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add an in-game telemetry graph overlay with zoom, series toggles, frame-time thresholds, and gamepad focus.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Fix the misspelled GPIO label","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Split the embedded protocol crate into codec, transport, and commands modules while preserving its public API and wire bytes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"A newly manufactured board occasionally reports impossible negative temperatures for its first reading. Determine whether initialization, I2C timing, or sign extension is at fault.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"A newly manufactured board occasionally reports impossible negative temperatures for its first reading. Determine whether initialization, I2C timing, or sign extension is at fault.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Walk me through the current rollback buffer ownership model and why snapshots use intrusive reference counts.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Draft contributor docs for adding a new world importer","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Create a milestone plan for migrating factory calibration from desktop scripts to an on-device guided flow, covering fixture compatibility, signed calibration records, operator permissions, offline factories, validation tolerances, audit exports, rollback to scripts, and pilot sequencing across three hardware revisions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} @@ -8676,539 +8472,536 @@ {"prompt":"Implement the editor viewport gizmos for translating spline control points with snapping and undo feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Use 115200 as the sample config baud rate","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Rename WorldChunk to RegionChunk across engine and tools while retaining asset field names and plugin compatibility.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"The game server's hit validation diverges only on AMD hosts under high load. Find the unknown nondeterministic path.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Review the current firmware update state machine for paths that can leave the device unbootable, without changing it.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Turn the existing CAN command implementation into a protocol reference with byte layouts and examples.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Plan the asset-bundle naming migration, including compatibility and conversion phases, but do not touch code.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Implement the finalized binary packet spec from docs/protocol-v7.md in the embedded Rust crate.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"设计游戏内任务追踪面板，需要折叠分组、距离提示、手柄导航和超宽屏适配。","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"zh"} -{"prompt":"Change the selected-tab underline to 2px","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Rearrange firmware command handlers by subsystem while preserving opcodes, timing, and error replies.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Why does the drone enter failsafe after exactly 49 days of uptime? The behavior is broken, and the timer interaction is unknown.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Explain why the existing renderer queues transparent objects back-to-front before batching; no rendering defect is reported.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Write a concise explanation of the current save-file chunk format for plugin developers.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"The game server's hit validation diverges only on AMD hosts under high load. Find the unknown nondeterministic path.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Review the current firmware update state machine for paths that can leave the device unbootable, without changing it.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Turn the existing CAN command implementation into a protocol reference with byte layouts and examples.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Plan the asset-bundle naming migration, including compatibility and conversion phases, but do not touch code.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement the finalized binary packet spec from docs/protocol-v7.md in the embedded Rust crate.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"设计游戏内任务追踪面板，需要折叠分组、距离提示、手柄导航和超宽屏适配。","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"zh"} +{"prompt":"Change the selected-tab underline to 2px","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rearrange firmware command handlers by subsystem while preserving opcodes, timing, and error replies.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Why does the drone enter failsafe after exactly 49 days of uptime? The behavior is broken, and the timer interaction is unknown.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Explain why the existing renderer queues transparent objects back-to-front before batching; no rendering defect is reported.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Write a concise explanation of the current save-file chunk format for plugin developers.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Plan and implement signed calibration bundles: define trust and rollout rules, then add verification and persistence to firmware behind a factory flag.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} {"prompt":"Implement the replay validator CLI and document its exit codes, output modes, and CI usage.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Create the visual controller calibration wizard and add a technician checklist for verifying dead zones and axis direction.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"Correct the known packet-type constant and update the decoder fixture that copied the incorrect value.","purpose":"quickFix","secondary":"backendImpl","mixed":true,"difficulty":0.3,"slice":"mixed","lang":"en"} -{"prompt":"Consolidate map metadata readers with identical output, then write a brief maintainer note about the new extension mechanism.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Proposed change:\n\ndiff --git a/firmware/update.c b/firmware/update.c\n@@\n- if (!verify_signature(image, len)) return ERR_SIGNATURE;\n- flash_write(SLOT_B, image, len);\n+ flash_write(SLOT_B, image, len);\n+ if (!verify_signature(SLOT_B, len)) erase_slot(SLOT_B);\n\ndiff --git a/firmware/boot.c b/firmware/boot.c\n@@\n- boot_slot = SLOT_A;\n+ boot_slot = newest_valid_slot();\n\nThe author says verifying after write reduces RAM usage and remains safe because invalid images are erased. Review power-loss behavior, boot metadata, length validation, erase failures, and whether partially written SLOT_B can ever be selected. Findings only; do not edit the patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Correct the known packet-type constant and update the decoder fixture that copied the incorrect value.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Consolidate map metadata readers with identical output, then write a brief maintainer note about the new extension mechanism.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Proposed change:\n\ndiff --git a/firmware/update.c b/firmware/update.c\n@@\n- if (!verify_signature(image, len)) return ERR_SIGNATURE;\n- flash_write(SLOT_B, image, len);\n+ flash_write(SLOT_B, image, len);\n+ if (!verify_signature(SLOT_B, len)) erase_slot(SLOT_B);\n\ndiff --git a/firmware/boot.c b/firmware/boot.c\n@@\n- boot_slot = SLOT_A;\n+ boot_slot = newest_valid_slot();\n\nThe author says verifying after write reduces RAM usage and remains safe because invalid images are erased. Review power-loss behavior, boot metadata, length validation, erase failures, and whether partially written SLOT_B can ever be selected. Findings only; do not edit the patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} {"prompt":"Documentation request copied from hardware Slack:\n\nSam: opcode 0x31 sets motor limits but the wiki still says it only sets max RPM.\nInez: payload is now four little-endian uint16 fields: rpm, current_mA, accel, decel.\nSam: firmware before 4.2 ignores the last two fields and returns ACK anyway.\nInez: error 0x07 means current exceeds the board revision limit, not generic bad input.\n\nUpdate docs/can/motor-limits.md with the exact payload, compatibility note, ACK behavior, error meaning, and one byte-level request example. No firmware changes.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} -{"prompt":"Architecture workshop notes:\n\n- The current rollback buffer stores 180 full simulation states at 14 MB each.\n- Target consoles allow 512 MB for the entire multiplayer subsystem.\n- Re-simulating more than 12 frames misses the render deadline.\n- Physics state has pointer-rich structures that cannot be memcpy'd safely.\n- Replays must remain deterministic across patches within one season.\n- Spectators may join 30 seconds late.\n\nDevelop a state-history design and delivery plan. Compare full snapshots, deltas, and component journals; address memory, restore cost, versioning, spectators, validation, telemetry, and staged prototypes. Do not implement it.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Feature EMB-554\n\nInput arrives as CAN-FD frames with:\n- stream ID: 12 bits\n- sequence: uint16 wrapping\n- flags: START, END, ABORT\n- up to 56 payload bytes\n\nReassembly rules:\n- at most eight active streams\n- reject gaps and duplicate START\n- discard inactive streams after 750 ms\n- ABORT clears state without emitting data\n- completed payload maximum is 4096 bytes\n- no heap allocation after initialization\n\nImplement the reassembler in firmware/protocol and expose completed messages through the existing callback. Add host tests for wraparound, timeouts, interleaving, overflow, and abort.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Editor UI ticket:\n\nArtists need to inspect navigation regions while placing obstacles. Add a viewport overlay with:\n- translucent region fills keyed by traversal type\n- boundary outlines that remain visible over bright scenes\n- hover label with region ID and cost\n- toolbar toggles for fill, edges, and labels\n- a legend that collapses on narrow editor windows\n- no measurable repaint when the overlay is hidden\n\nThe navigation data already exists in NavDebugModel. Implement the overlay and controls using the editor's current theme and undo-safe selection behavior.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Architecture workshop notes:\n\n- The current rollback buffer stores 180 full simulation states at 14 MB each.\n- Target consoles allow 512 MB for the entire multiplayer subsystem.\n- Re-simulating more than 12 frames misses the render deadline.\n- Physics state has pointer-rich structures that cannot be memcpy'd safely.\n- Replays must remain deterministic across patches within one season.\n- Spectators may join 30 seconds late.\n\nDevelop a state-history design and delivery plan. Compare full snapshots, deltas, and component journals; address memory, restore cost, versioning, spectators, validation, telemetry, and staged prototypes. Do not implement it.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Feature EMB-554\n\nInput arrives as CAN-FD frames with:\n- stream ID: 12 bits\n- sequence: uint16 wrapping\n- flags: START, END, ABORT\n- up to 56 payload bytes\n\nReassembly rules:\n- at most eight active streams\n- reject gaps and duplicate START\n- discard inactive streams after 750 ms\n- ABORT clears state without emitting data\n- completed payload maximum is 4096 bytes\n- no heap allocation after initialization\n\nImplement the reassembler in firmware/protocol and expose completed messages through the existing callback. Add host tests for wraparound, timeouts, interleaving, overflow, and abort.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Editor UI ticket:\n\nArtists need to inspect navigation regions while placing obstacles. Add a viewport overlay with:\n- translucent region fills keyed by traversal type\n- boundary outlines that remain visible over bright scenes\n- hover label with region ID and cost\n- toolbar toggles for fill, edges, and labels\n- a legend that collapses on narrow editor windows\n- no measurable repaint when the overlay is hidden\n\nThe navigation data already exists in NavDebugModel. Implement the overlay and controls using the editor's current theme and undo-safe selection behavior.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Adjust the one value","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"vague-eval","lang":"en"} {"prompt":"Untangle the engine bits","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"Find whatever broke rendering","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"Read the OAuth proxy implementation and identify where scopes are narrowed, cached, and revalidated. Explanation only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Read the OAuth proxy implementation and identify where scopes are narrowed, cached, and revalidated. Explanation only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Write a security advisory for the fixed session leak","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Create an RFC for replacing static service credentials with workload identity across Kubernetes, CI, local development, and external batch systems. Cover trust roots, token exchange, audience scoping, emergency access, rotation, audit evidence, migration sequencing, compatibility gaps, measurable gates, and rollback before static secrets are revoked.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} -{"prompt":"Add a Go token-exchange endpoint with audience restrictions, nonce replay protection, and short-lived signed credentials.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Build the admin role editor with permission grouping, dependency warnings, diff preview, and confirmation for privilege escalation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create an RFC for replacing static service credentials with workload identity across Kubernetes, CI, local development, and external batch systems. Cover trust roots, token exchange, audience scoping, emergency access, rotation, audit evidence, migration sequencing, compatibility gaps, measurable gates, and rollback before static secrets are revoked.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add a Go token-exchange endpoint with audience restrictions, nonce replay protection, and short-lived signed credentials.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Build the admin role editor with permission grouping, dependency warnings, diff preview, and confirmation for privilege escalation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Rotate the test JWKS fixture expiry date","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Extract authorization decision logging from policy evaluation without changing decisions, latency budgets, or log fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Requests authenticated through one edge region occasionally inherit another tenant's cached policy result. Locate the cache-key or propagation defect.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Check whether the current SAML callback validates RelayState binding and destination consistently across identity providers.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Schreibe eine verständliche Anleitung zur Rotation von Webhook-Schlüsseln, inklusive Überlappungszeit und Verifikation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"de"} -{"prompt":"Map out a multi-quarter migration from role-based access checks embedded in services to a centralized relationship-based authorization system. Include model ownership, latency and availability budgets, consistency, shadow evaluation, decision diffs, emergency fallback, schema evolution, auditability, developer tooling, and milestones that avoid weakening existing controls.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Requests authenticated through one edge region occasionally inherit another tenant's cached policy result. Locate the cache-key or propagation defect.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Check whether the current SAML callback validates RelayState binding and destination consistently across identity providers.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Schreibe eine verständliche Anleitung zur Rotation von Webhook-Schlüsseln, inklusive Überlappungszeit und Verifikation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"de"} +{"prompt":"Map out a multi-quarter migration from role-based access checks embedded in services to a centralized relationship-based authorization system. Include model ownership, latency and availability budgets, consistency, shadow evaluation, decision diffs, emergency fallback, schema evolution, auditability, developer tooling, and milestones that avoid weakening existing controls.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Implement a streaming policy-decision export that redacts sensitive attributes and preserves event ordering per tenant.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Create the access-review dashboard with expiring grants, owner filters, bulk attest controls, and high-risk visual treatment.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the access-review dashboard with expiring grants, owner filters, bulk attest controls, and high-risk visual treatment.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Change SESSION_TTL_MINUTES to 30","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Merge duplicate JWT claim parsers across gateway and worker packages while preserving validation errors and accepted tokens.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Merge duplicate JWT claim parsers across gateway and worker packages while preserving validation errors and accepted tokens.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"The audit stream drops logout events during Kafka leader elections but no producer error is logged. Determine where acknowledgements are being lost.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Explain the current break-glass workflow from request through expiry and retrospective review, based on code and configuration.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Draft the threat-model summary for third-party OAuth applications","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Plan the deprecation of wildcard OAuth redirect URIs across thousands of existing integrations. Address inventory, customer ownership, compatibility windows, exception handling, validation rollout, telemetry, support tooling, communications, enforcement stages, and a rapid rollback mechanism if legitimate authorization flows are blocked.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Plan the deprecation of wildcard OAuth redirect URIs across thousands of existing integrations. Address inventory, customer ownership, compatibility windows, exception handling, validation rollout, telemetry, support tooling, communications, enforcement stages, and a rapid rollback mechanism if legitimate authorization flows are blocked.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1,"slice":"core","lang":"en"} {"prompt":"Implement SCIM group membership patch operations with atomic add/remove semantics and idempotent retries.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Add a passkey enrollment dialog with device naming, platform guidance, fallback choices, and clear failure recovery.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Separate identity-provider metadata fetching from SAML assertion validation while retaining cache behavior and error responses.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Password resets intermittently invalidate sessions for the wrong account when emails differ only by case. Trace the identity lookup bug.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Assess how current API-key prefix matching behaves under collisions and whether full secrets are ever queried unnecessarily.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add a passkey enrollment dialog with device naming, platform guidance, fallback choices, and clear failure recovery.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Separate identity-provider metadata fetching from SAML assertion validation while retaining cache behavior and error responses.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Password resets intermittently invalidate sessions for the wrong account when emails differ only by case. Trace the identity lookup bug.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Assess how current API-key prefix matching behaves under collisions and whether full secrets are ever queried unnecessarily.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Prepare customer-facing docs for configuring OIDC group claims","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Design a key-management architecture for encrypting tenant exports with customer-managed keys. Cover envelope encryption, grants, regional copies, rotation, revocation, asynchronous jobs, disaster recovery, audit evidence, support access, failure semantics, and an incremental rollout from platform-owned keys.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Design a key-management architecture for encrypting tenant exports with customer-managed keys. Cover envelope encryption, grants, regional copies, rotation, revocation, asynchronous jobs, disaster recovery, audit evidence, support access, failure semantics, and an incremental rollout from platform-owned keys.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1,"slice":"core","lang":"en"} {"prompt":"Build a Java background worker that rotates encrypted data keys without decrypting payloads outside the HSM boundary.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Implement the security-event timeline with correlated sessions, expandable evidence, time-zone switching, and export feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Set allow_signup to false in production.toml","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Rename PermissionSet to AccessProfile across internal modules while maintaining JSON, database, and SDK compatibility.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"OIDC login loops only for users with more than 150 groups. Diagnose whether cookie size, claim mapping, or redirect state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Review the existing service-account impersonation checks and tell me which actors can form transitive chains.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Rename PermissionSet to AccessProfile across internal modules while maintaining JSON, database, and SDK compatibility.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"OIDC login loops only for users with more than 150 groups. Diagnose whether cookie size, claim mapping, or redirect state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Review the existing service-account impersonation checks and tell me which actors can form transitive chains.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Write a concise glossary for authentication, authorization, identity, principal, actor, and subject as used in this repo.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Produce a migration strategy for splitting authentication data from the main application database, including transactional seams, session continuity, replicas, encryption, backup isolation, dual writes, consistency monitoring, cutover gates, and rollback without forcing every user to sign in again.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Produce a migration strategy for splitting authentication data from the main application database, including transactional seams, session continuity, replicas, encryption, backup isolation, dual writes, consistency monitoring, cutover gates, and rollback without forcing every user to sign in again.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} {"prompt":"Add an endpoint that lists active sessions with device metadata and supports idempotent bulk revocation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Build a responsive policy simulator where admins can select an actor, resource, and action and inspect the decision trace.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Change the security banner copy to the approved sentence","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Change the security banner copy to the approved sentence","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} {"prompt":"Consolidate organization-membership resolution under one service without changing authorization decisions or database access patterns.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"WebAuthn registration fails on some Windows machines with a generic NotAllowedError. Determine whether our challenge, RP ID, or timeout handling is invalid.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Is the existing recovery-code generator unbiased and resistant to online guessing? Review implementation and rate limits without editing.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Document the API-key lifecycle from creation through rotation and revocation, using current behavior only.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Develop the rollout plan for mandatory MFA on administrator accounts; code is out of scope.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Implement the approved token-introspection response contract and cache semantics in auth-service.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Add a small session-expired modal with sign-in recovery, unsaved-work messaging, and accessible focus management.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"WebAuthn registration fails on some Windows machines with a generic NotAllowedError. Determine whether our challenge, RP ID, or timeout handling is invalid.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Is the existing recovery-code generator unbiased and resistant to online guessing? Review implementation and rate limits without editing.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Document the API-key lifecycle from creation through rotation and revocation, using current behavior only.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Develop the rollout plan for mandatory MFA on administrator accounts; code is out of scope.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement the approved token-introspection response contract and cache semantics in auth-service.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add a small session-expired modal with sign-in recovery, unsaved-work messaging, and accessible focus management.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Replace `authenication` with `authentication` in README.md","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Restructure scope evaluation into parse, normalize, and decide stages with byte-for-byte identical decision logs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Why do revoked API keys remain usable for up to two minutes? This is unexpected and the responsible cache layer is unknown.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Explain why the current refresh-token table retains consumed token hashes for 90 days; no malfunction is alleged.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Summarize the existing SSO domain-verification code into an administrator guide rather than changing its behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Restructure scope evaluation into parse, normalize, and decide stages with byte-for-byte identical decision logs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Why do revoked API keys remain usable for up to two minutes? This is unexpected and the responsible cache layer is unknown.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Explain why the current refresh-token table retains consumed token hashes for 90 days; no malfunction is alleged.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Summarize the existing SSO domain-verification code into an administrator guide rather than changing its behavior.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Plan the credential-rotation system and implement a read-only inventory command that identifies owners, age, and unsupported credential types.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"Build the signed JWKS publication service and write integration documentation covering cache headers and overlap during rotation.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Create the admin consent screen and produce a visual QA note for long permission lists, localization, and keyboard navigation.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"Correct the known session-cookie domain and update the backend fixture that asserts the old domain.","purpose":"quickFix","secondary":"backendImpl","mixed":true,"difficulty":0.3,"slice":"mixed","lang":"en"} -{"prompt":"Extract token claims into a shared value object without behavior changes, then document its invariants for service maintainers.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Security feature AUTH-2210\n\nImplement POST /v1/service-accounts/{id}/tokens with:\n- caller requires service_account.tokens.create on the target\n- requested scopes must be a subset of the account's grants\n- lifetime range is 60 to 3600 seconds\n- tokens use the regional signing key and include jti, aud, sub, tenant_id\n- duplicate Idempotency-Key returns the same token until its expiry\n- never persist plaintext tokens\n- publish TokenIssued with metadata but no token value\n- rate limit per actor and target account\n\nAdd the handler, signing path, idempotency storage, audit event, metrics, and integration tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"UI specification from design review:\n\nPage: Access Reviews\nDesktop uses a table; below 720px it becomes stacked cards. Each item shows grantee, resource, reason, grant age, owner, and risk level. Reviewers can approve, revoke, or defer. Revocation requires confirmation if the grant came from a group. Bulk actions must remain visible while scrolling, but never cover validation errors. Screen readers need the selection count and asynchronous action outcomes. Empty, expired-session, and partial-failure states are included in ui/states/access-review.png.\n\nImplement this page with existing React Query hooks and design-system components. Backend behavior is unchanged.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Build the signed JWKS publication service and write integration documentation covering cache headers and overlap during rotation.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Create the admin consent screen and produce a visual QA note for long permission lists, localization, and keyboard navigation.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Correct the known session-cookie domain and update the backend fixture that asserts the old domain.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Extract token claims into a shared value object without behavior changes, then document its invariants for service maintainers.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Security feature AUTH-2210\n\nImplement POST /v1/service-accounts/{id}/tokens with:\n- caller requires service_account.tokens.create on the target\n- requested scopes must be a subset of the account's grants\n- lifetime range is 60 to 3600 seconds\n- tokens use the regional signing key and include jti, aud, sub, tenant_id\n- duplicate Idempotency-Key returns the same token until its expiry\n- never persist plaintext tokens\n- publish TokenIssued with metadata but no token value\n- rate limit per actor and target account\n\nAdd the handler, signing path, idempotency storage, audit event, metrics, and integration tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"UI specification from design review:\n\nPage: Access Reviews\nDesktop uses a table; below 720px it becomes stacked cards. Each item shows grantee, resource, reason, grant age, owner, and risk level. Reviewers can approve, revoke, or defer. Revocation requires confirmation if the grant came from a group. Bulk actions must remain visible while scrolling, but never cover validation errors. Screen readers need the selection count and asynchronous action outcomes. Empty, expired-session, and partial-failure states are included in ui/states/access-review.png.\n\nImplement this page with existing React Query hooks and design-system components. Backend behavior is unchanged.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} {"prompt":"Failing docs check:\n\nERROR docs/examples/oidc.yaml: issuer does not match configured test provider\nexpected: https://idp.example.test/realms/acme\nactual: https://idp.example.test/realm/acme\n\nSearch results show the singular `/realm/` value appears only in docs/examples/oidc.yaml line 7. The provider fixture and every other example use `/realms/acme`. Correct that one URL. Do not update snapshots, tests, provider configuration, or surrounding prose.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"pasted-context","lang":"en"} -{"prompt":"Restructuring brief:\n\nservices/auth currently has:\n- jwt.ts validating tokens and loading tenants\n- permissions.ts parsing claims and querying memberships\n- middleware.ts duplicating both for websocket upgrades\n- audit.ts importing middleware types\n\nThis creates an import cycle and websocket authorization has drifted from HTTP authorization. Introduce token-verification and authorization-decision boundaries used by both transports. Break the cycle, remove duplicated claim normalization, and retain exact status codes, websocket close codes, metrics labels, audit fields, and accepted token fixtures. No policy behavior should change.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Production log tail:\n\n12:41:08 token revoked family=9c2 user=184\n12:41:08 cache invalidate key=session:184 published region=iad\n12:41:09 request accepted region=fra token_jti=7ab family=9c2\n12:41:10 invalidate received region=fra key=session:184\n12:41:10 cache miss region=fra\n12:41:10 introspection response active=true family=9c2\n12:41:11 cache set active=true ttl=120\n\nA revoked refresh family remained active in Frankfurt even after invalidation arrived. The database row is revoked. Determine why introspection reconstructed active=true and whether replica lag, cache keying, or transaction visibility explains it. Reproduce the failure before applying a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Restructuring brief:\n\nservices/auth currently has:\n- jwt.ts validating tokens and loading tenants\n- permissions.ts parsing claims and querying memberships\n- middleware.ts duplicating both for websocket upgrades\n- audit.ts importing middleware types\n\nThis creates an import cycle and websocket authorization has drifted from HTTP authorization. Introduce token-verification and authorization-decision boundaries used by both transports. Break the cycle, remove duplicated claim normalization, and retain exact status codes, websocket close codes, metrics labels, audit fields, and accepted token fixtures. No policy behavior should change.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Production log tail:\n\n12:41:08 token revoked family=9c2 user=184\n12:41:08 cache invalidate key=session:184 published region=iad\n12:41:09 request accepted region=fra token_jti=7ab family=9c2\n12:41:10 invalidate received region=fra key=session:184\n12:41:10 cache miss region=fra\n12:41:10 introspection response active=true family=9c2\n12:41:11 cache set active=true ttl=120\n\nA revoked refresh family remained active in Frankfurt even after invalidation arrived. The database row is revoked. Determine why introspection reconstructed active=true and whether replica lag, cache keying, or transaction visibility explains it. Reproduce the failure before applying a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} {"prompt":"Tell me what auth does","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Put together the words","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} {"prompt":"Design a zero-trust machine-identity architecture for services, CI jobs, developer workstations, and edge robots. Cover enrollment, attestation, short-lived credentials, authorization, revocation, offline operation, audit evidence, and migration from shared certificates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Implement an OIDC authorization-code flow in Rust with PKCE, rotating refresh tokens, state validation, and session revocation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement an OIDC authorization-code flow in Rust with PKCE, rotating refresh tokens, state validation, and session revocation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Build the browser extension popup for managing site permissions, blocked requests, and per-domain rules.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Set CSP_REPORT_ONLY to false.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Extract JWT claim normalization into one package without changing accepted tokens or authorization outcomes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"WebAuthn registration fails intermittently on Safari after Face ID succeeds. Find which challenge or navigation state becomes invalid.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Inspect security/key_cache.go and explain whether a revoked signing key can remain usable during cache refresh.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write an integration guide for partners adopting signed webhook requests and overlapping secret rotation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Outline a migration strategy from static robot credentials to hardware-backed identities. I need trust decisions, stages, and rollback criteria, not firmware or server code.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Add the documented token-exchange fields to openapi.yaml and implement their server-side validation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Make the blocked-site indicator more prominent and animate it once when the extension opens.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"Rename req to request in callback.ts.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Rename serviceAccount to workloadIdentity across the monorepo while preserving wire fields and config aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Warum werden abgelaufene Sessions nach einem Redis failover wieder gültig? Finde die unbekannte Ursache.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"de"} -{"prompt":"Explain why the current authorization engine evaluates explicit denies before administrator grants. Assume behavior is correct.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Turn the existing API-key creation code into a concise security concepts page for developers.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Extract JWT claim normalization into one package without changing accepted tokens or authorization outcomes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"WebAuthn registration fails intermittently on Safari after Face ID succeeds. Find which challenge or navigation state becomes invalid.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Inspect security/key_cache.go and explain whether a revoked signing key can remain usable during cache refresh.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Write an integration guide for partners adopting signed webhook requests and overlapping secret rotation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Outline a migration strategy from static robot credentials to hardware-backed identities. I need trust decisions, stages, and rollback criteria, not firmware or server code.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add the documented token-exchange fields to openapi.yaml and implement their server-side validation.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Make the blocked-site indicator more prominent and animate it once when the extension opens.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Rename req to request in callback.ts.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename serviceAccount to workloadIdentity across the monorepo while preserving wire fields and config aliases.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Warum werden abgelaufene Sessions nach einem Redis failover wieder gültig? Finde die unbekannte Ursache.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} +{"prompt":"Explain why the current authorization engine evaluates explicit denies before administrator grants. Assume behavior is correct.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Turn the existing API-key creation code into a concise security concepts page for developers.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Map out an autonomy architecture for warehouse robots that must keep operating through control-plane outages. Cover mission leasing, local safety, map versions, conflict avoidance, degraded modes, reconciliation, observability, and staged deployment.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Create a ROS 2 service that reserves loading bays, enforces lease expiry, and resolves concurrent robot claims.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Implement the React fleet map with live robot positions, mission paths, geofence overlays, and accessible list fallback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Change the lidar range to 25m.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Consolidate duplicate coordinate-frame conversions while preserving floating-point results and timestamp handling.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"The robot's pose jumps two meters after map relocalization even though scan matching converges. Locate the frame or timestamp error.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Assess whether navigation/path_planner.cpp can route through a zone that becomes restricted during an active mission.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Consolidate duplicate coordinate-frame conversions while preserving floating-point results and timestamp handling.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"The robot's pose jumps two meters after map relocalization even though scan matching converges. Locate the frame or timestamp error.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Assess whether navigation/path_planner.cpp can route through a zone that becomes restricted during an active mission.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Draft an operator runbook for recovering robots stranded by a failed map deployment.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Security architecture ticket IAM-2081\n\nObjective: eliminate long-lived credentials used by customer-managed data connectors.\nCurrent state:\n- connectors run in customer Kubernetes clusters\n- each connector receives a static API key during installation\n- keys are scoped to one tenant but remain valid until manually revoked\n- connectors may be offline for several weeks\n- some environments cannot accept inbound traffic\n- installations range from version 2.1 to 7.4\n\nRequirements:\n1. Bootstrap without sending a reusable secret through Helm values\n2. Issue short-lived credentials after proving installation identity\n3. Support planned and emergency rotation\n4. Permit offline buffering without permitting indefinite API access\n5. Expose enrollment, renewal, failure, and revocation evidence\n6. Allow gradual rollout by tenant and connector version\n7. Preserve an emergency recovery path for air-gapped customers\n\nProduce the threat model, protocol design, compatibility approach, and migration plan. No implementation yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Backend story SEC-771\n\nAdd one-time recovery codes to the Go identity service.\n\nAcceptance criteria:\n- generate ten high-entropy human-readable codes when MFA is enrolled or regenerated\n- store only an appropriate slow hash\n- each code may be consumed once\n- consumption must be atomic across regions\n- successful use revokes all active refresh tokens except the current recovery session\n- regeneration invalidates every previous unused code\n- audit events record actor, account, and outcome, never the code\n- rate limits apply per account and network source\n- support agents cannot view or generate codes\n- responses should not reveal whether a submitted code was previously used\n\nFollow transaction patterns in internal/mfa and add concurrency, replay, and audit-redaction tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Browser extension design notes:\n\nPage: RulesEditor.tsx\nData model already provides hostname patterns, resource types, action, priority, and enabled state.\n\nDesired behavior:\n- rules appear in priority order and support drag reordering\n- domain patterns have inline validation with an example of matched sites\n- resource types use a searchable multi-select\n- conflicting rules show a non-blocking warning\n- unsaved edits persist if the popup closes\n- a test panel accepts a URL and explains the winning rule\n- screen-reader users need a non-drag method to reorder\n- narrow popup mode uses a full-screen editor for one rule\n- dark theme must distinguish disabled and invalid states without opacity alone\n\nBuild the editor using the existing rules store; do not change matching semantics.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Approved dependency update:\n\nPackage: @simplewebauthn/browser\nCurrent version: 13.1.0\nApproved version: 13.1.2\nFiles in scope:\n- apps/portal/package.json\n- pnpm-lock.yaml\n\nThe security review and browser matrix are complete. Update only this dependency and the lockfile entries produced by the package manager. Do not update @simplewebauthn/server, TypeScript, pnpm, unrelated transitive packages, browser targets, or authentication code. Preserve the existing semver style and workspace configuration.\n\nApply the known patch bump.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} -{"prompt":"Cleanup note from the identity team:\n\nThe service contains four nearly identical principal builders for HTTP, gRPC, background jobs, and support impersonation. All builders normalize tenant ids, attach roles, resolve feature entitlements, and derive audit identity. Differences are intentional: jobs have no user actor, gRPC includes peer workload identity, and impersonation tracks both real and effective users. Authorization tests assert exact claims and audit records.\n\nExtract shared normalization and construction primitives without merging the distinct entry points. Preserve authorization results, claim ordering, error messages, audit identity, tracing fields, and public interfaces. Avoid a mutable global context. This should be structural cleanup only.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Authentication incident excerpt:\n\n2026-07-28T04:12:10Z token_refresh INFO account=8f1 family=9aa presented=41 issued=42\n2026-07-28T04:12:10Z token_refresh INFO account=8f1 family=9aa presented=41 issued=43\n2026-07-28T04:12:11Z token_refresh WARN reuse_detected family=9aa token=41\n2026-07-28T04:12:11Z session INFO family_revoked family=9aa\n\nThe mobile client sent two refresh requests concurrently after waking. Both database transactions committed, producing two valid descendants. A later retry of the old token revoked the whole family and logged the user out. Refresh rows use PostgreSQL, isolation is read committed, and uniqueness currently covers token hash only. Diagnose the race and implement rotation that permits idempotent network retry without allowing sibling tokens.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Revisión solicitada, sin cambios:\n\nEl servicio firma access tokens con Ed25519. Las claves privadas viven en KMS y el proceso mantiene claves públicas en memoria durante diez minutos. Un registro de PostgreSQL contiene kid, estado, not_before y not_after. La rotación crea una clave pending, espera la propagación a verificadores, la marca active y después mueve la anterior a retiring. Los verificadores aceptan active y retiring. Un trabajo elimina claves retiring cuando expira el último token posible. Si KMS no responde, la emisión falla cerrada; la verificación local continúa.\n\nEvalúa ventanas de rotación, relojes desincronizados, caché, rollback de base de datos, kid collisions, revocación urgente y eliminación de claves. Entrega hallazgos solamente.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"es"} +{"prompt":"Security architecture ticket IAM-2081\n\nObjective: eliminate long-lived credentials used by customer-managed data connectors.\nCurrent state:\n- connectors run in customer Kubernetes clusters\n- each connector receives a static API key during installation\n- keys are scoped to one tenant but remain valid until manually revoked\n- connectors may be offline for several weeks\n- some environments cannot accept inbound traffic\n- installations range from version 2.1 to 7.4\n\nRequirements:\n1. Bootstrap without sending a reusable secret through Helm values\n2. Issue short-lived credentials after proving installation identity\n3. Support planned and emergency rotation\n4. Permit offline buffering without permitting indefinite API access\n5. Expose enrollment, renewal, failure, and revocation evidence\n6. Allow gradual rollout by tenant and connector version\n7. Preserve an emergency recovery path for air-gapped customers\n\nProduce the threat model, protocol design, compatibility approach, and migration plan. No implementation yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Backend story SEC-771\n\nAdd one-time recovery codes to the Go identity service.\n\nAcceptance criteria:\n- generate ten high-entropy human-readable codes when MFA is enrolled or regenerated\n- store only an appropriate slow hash\n- each code may be consumed once\n- consumption must be atomic across regions\n- successful use revokes all active refresh tokens except the current recovery session\n- regeneration invalidates every previous unused code\n- audit events record actor, account, and outcome, never the code\n- rate limits apply per account and network source\n- support agents cannot view or generate codes\n- responses should not reveal whether a submitted code was previously used\n\nFollow transaction patterns in internal/mfa and add concurrency, replay, and audit-redaction tests.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Browser extension design notes:\n\nPage: RulesEditor.tsx\nData model already provides hostname patterns, resource types, action, priority, and enabled state.\n\nDesired behavior:\n- rules appear in priority order and support drag reordering\n- domain patterns have inline validation with an example of matched sites\n- resource types use a searchable multi-select\n- conflicting rules show a non-blocking warning\n- unsaved edits persist if the popup closes\n- a test panel accepts a URL and explains the winning rule\n- screen-reader users need a non-drag method to reorder\n- narrow popup mode uses a full-screen editor for one rule\n- dark theme must distinguish disabled and invalid states without opacity alone\n\nBuild the editor using the existing rules store; do not change matching semantics.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Approved dependency update:\n\nPackage: @simplewebauthn/browser\nCurrent version: 13.1.0\nApproved version: 13.1.2\nFiles in scope:\n- apps/portal/package.json\n- pnpm-lock.yaml\n\nThe security review and browser matrix are complete. Update only this dependency and the lockfile entries produced by the package manager. Do not update @simplewebauthn/server, TypeScript, pnpm, unrelated transitive packages, browser targets, or authentication code. Preserve the existing semver style and workspace configuration.\n\nApply the known patch bump.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Cleanup note from the identity team:\n\nThe service contains four nearly identical principal builders for HTTP, gRPC, background jobs, and support impersonation. All builders normalize tenant ids, attach roles, resolve feature entitlements, and derive audit identity. Differences are intentional: jobs have no user actor, gRPC includes peer workload identity, and impersonation tracks both real and effective users. Authorization tests assert exact claims and audit records.\n\nExtract shared normalization and construction primitives without merging the distinct entry points. Preserve authorization results, claim ordering, error messages, audit identity, tracing fields, and public interfaces. Avoid a mutable global context. This should be structural cleanup only.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Authentication incident excerpt:\n\n2026-07-28T04:12:10Z token_refresh INFO account=8f1 family=9aa presented=41 issued=42\n2026-07-28T04:12:10Z token_refresh INFO account=8f1 family=9aa presented=41 issued=43\n2026-07-28T04:12:11Z token_refresh WARN reuse_detected family=9aa token=41\n2026-07-28T04:12:11Z session INFO family_revoked family=9aa\n\nThe mobile client sent two refresh requests concurrently after waking. Both database transactions committed, producing two valid descendants. A later retry of the old token revoked the whole family and logged the user out. Refresh rows use PostgreSQL, isolation is read committed, and uniqueness currently covers token hash only. Diagnose the race and implement rotation that permits idempotent network retry without allowing sibling tokens.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Revisión solicitada, sin cambios:\n\nEl servicio firma access tokens con Ed25519. Las claves privadas viven en KMS y el proceso mantiene claves públicas en memoria durante diez minutos. Un registro de PostgreSQL contiene kid, estado, not_before y not_after. La rotación crea una clave pending, espera la propagación a verificadores, la marca active y después mueve la anterior a retiring. Los verificadores aceptan active y retiring. Un trabajo elimina claves retiring cuando expira el último token posible. Si KMS no responde, la emisión falla cerrada; la verificación local continúa.\n\nEvalúa ventanas de rotación, relojes desincronizados, caché, rollback de base de datos, kid collisions, revocación urgente y eliminación de claves. Entrega hallazgos solamente.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"es"} {"prompt":"Raw notes for the partner security guide:\n\nRequests use HTTP Message Signatures. Covered components are method, authority, path, content-digest, x-request-id, and created. Partners receive two key ids during rotation. The server accepts signatures created within five minutes and stores request ids for ten minutes to reject replay. Bodies above 10 MB are streamed while computing SHA-256. Proxies may normalize header casing but must not rewrite path encoding. A missing content-digest is allowed only for empty bodies. Clock skew errors return a server timestamp. Verification failures use one generic 401 response, while diagnostics are available through an authenticated support endpoint.\n\nTurn these notes into an integration guide with canonicalization examples, rotation procedure, replay rules, streaming advice, clock troubleshooting, and safe debugging steps.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} {"prompt":"Create a phased roadmap for introducing safety-certified motion control into the existing ROS 2 stack, including subsystem boundaries, hazard analysis, validation evidence, fallback modes, ownership, and deployment gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Add a C++ mission executor that persists checkpoints, resumes after process restart, and rejects stale commands.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Render the web-based robot diagnostics panel with live joint states, warning timelines, and a responsive command drawer.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add a C++ mission executor that persists checkpoints, resumes after process restart, and rejects stale commands.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Render the web-based robot diagnostics panel with live joint states, warning timelines, and a responsive command drawer.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Flip enableMockGps to false.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Split camera calibration loading from validation while preserving accepted files and diagnostics.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"The safety controller enters emergency stop when the system clock steps backward. Determine which deadline calculation uses wall time.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Examine the current obstacle-fusion pipeline and explain how contradictory radar and lidar observations are resolved.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Split camera calibration loading from validation while preserving accepted files and diagnostics.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"The safety controller enters emergency stop when the system clock steps backward. Determine which deadline calculation uses wall time.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Examine the current obstacle-fusion pipeline and explain how contradictory radar and lidar observations are resolved.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Write a field-maintenance guide for replacing and recalibrating a wheel encoder.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Plan a delegated-administration model, then implement scoped role grants and revocation in the authorization service.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} {"prompt":"Implement token introspection caching and document its consistency and revocation behavior for API teams.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Build the extension's certificate viewer and add the native-messaging method that retrieves certificate-chain details.","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Build the extension's certificate viewer and add the native-messaging method that retrieves certificate-chain details.","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Correct the redirect URI in dev.json and add a note to the local-auth troubleshooting page.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.2,"slice":"mixed","lang":"en"} {"prompt":"Reorganize policy evaluators by resource type with identical decisions, then update the architecture overview.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Determine why robots occasionally execute a canceled mission, fix the race, and document cancellation guarantees for integrators.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Determine why robots occasionally execute a canceled mission, fix the race, and document cancellation guarantees for integrators.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Audit the current administrator impersonation controls, then propose a remediation roadmap for the issues found.","purpose":"review","secondary":"planning","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Read the permission-matching engine and produce a maintainer guide explaining precedence and extension points.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Read the permission-matching engine and produce a maintainer guide explaining precedence and extension points.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Implement a privacy-preserving rate limiter using keyed hashes so raw account identifiers never enter Redis.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Create the React security-events explorer with facet filters, expandable evidence, and keyboard navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Set sessionMaxAge to 12h.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Explain whether the current CSRF middleware covers requests sent through the extension's native bridge.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Architect a unified secrets platform for Kubernetes, serverless jobs, developer tools, and robots. Address source of truth, delivery, renewal, offline caching, break-glass access, policy, auditing, disaster recovery, and migration from environment variables.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Rédige un runbook pour révoquer rapidement une clé de signature compromise sans interrompre tous les clients.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"fr"} -{"prompt":"Move duplicated nonce parsing into one utility without changing validation or error responses.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"After an extension update, previously denied domains briefly become allowed. Find the ruleset initialization race.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Propose an architecture for secure remote teleoperation over unreliable cellular links. Cover command authority, latency, dead-man behavior, encryption, video degradation, regional relays, auditing, emergency takeover, and rollout. Deliver a design only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"boundary","lang":"en"} -{"prompt":"Document the robot heartbeat protocol and implement its timeout and lease-renewal handler.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Add a clear visual distinction between inherited and explicitly granted permissions.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"Move the shield icon 3px right.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Rename authSubject to principal across all services while retaining protobuf and database field names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Why do revoked browser sessions still receive websocket events? Locate the unknown invalidation gap.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Explain why permission bundles are version-pinned for running workflows. Nothing is known to be broken.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"既存の OAuth consent 処理を、アプリ開発者向けの概念ガイドとしてまとめてください。実装変更は不要です。","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"ja"} -{"prompt":"Introduce a Python service that validates robot maps, computes compatibility metadata, and publishes immutable revisions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Build the browser extension onboarding flow with permission explanations, pinning guidance, and an interactive test.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Explain whether the current CSRF middleware covers requests sent through the extension's native bridge.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Architect a unified secrets platform for Kubernetes, serverless jobs, developer tools, and robots. Address source of truth, delivery, renewal, offline caching, break-glass access, policy, auditing, disaster recovery, and migration from environment variables.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1,"slice":"core","lang":"en"} +{"prompt":"Rédige un runbook pour révoquer rapidement une clé de signature compromise sans interrompre tous les clients.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"fr"} +{"prompt":"Move duplicated nonce parsing into one utility without changing validation or error responses.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"After an extension update, previously denied domains briefly become allowed. Find the ruleset initialization race.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Propose an architecture for secure remote teleoperation over unreliable cellular links. Cover command authority, latency, dead-man behavior, encryption, video degradation, regional relays, auditing, emergency takeover, and rollout. Deliver a design only.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Document the robot heartbeat protocol and implement its timeout and lease-renewal handler.","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Add a clear visual distinction between inherited and explicitly granted permissions.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Move the shield icon 3px right.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename authSubject to principal across all services while retaining protobuf and database field names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Why do revoked browser sessions still receive websocket events? Locate the unknown invalidation gap.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Explain why permission bundles are version-pinned for running workflows. Nothing is known to be broken.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"既存の OAuth consent 処理を、アプリ開発者向けの概念ガイドとしてまとめてください。実装変更は不要です。","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"ja"} +{"prompt":"Introduce a Python service that validates robot maps, computes compatibility metadata, and publishes immutable revisions.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Build the browser extension onboarding flow with permission explanations, pinning guidance, and an interactive test.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Change TOKEN_SKEW_SECONDS to 90.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Assess whether the current certificate-path validator handles name constraints on intermediate CAs correctly.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Assess whether the current certificate-path validator handles name constraints on intermediate CAs correctly.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} {"prompt":"Develop a migration roadmap from role-based access control to relationship-based authorization. Include modeling, consistency, policy rollout, debugging tools, auditability, data backfill, dual evaluation, performance, and rollback.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Prepare customer-facing release notes for organization-wide session controls and forced logout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Consolidate the three certificate loaders while preserving trust-store precedence and diagnostics.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"The navigation stack oscillates between two paths near a narrow obstacle. Find which planner state prevents convergence.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Platform migration notes:\n\nThe company currently has five independent authorization libraries. Java and Go services evaluate static roles locally; the GraphQL gateway calls a Python policy service; mobile APIs use hard-coded ownership checks; batch jobs rely on warehouse grants. Audit events use different action names, and support cannot explain a denied request consistently. Product plans resource sharing, organization groups, temporary grants, and policy simulation. Availability target is 99.99%, and authorization may not silently fail open. Some data-processing jobs run disconnected for twelve hours.\n\nCreate a target architecture and staged migration plan. Cover policy model, decision API, local versus remote evaluation, version pinning, caching, audit schema, explainability, offline jobs, rollout metrics, dual evaluation, emergency controls, ownership, and rollback. No implementation in this phase.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"pasted-context","lang":"en"} -{"prompt":"Backend ticket ROB-552\n\nImplement traffic reservations for narrow warehouse aisles. Robots publish route segments with earliest entry, latest exit, width class, and priority. The coordinator must:\n- prevent incompatible overlapping reservations\n- allow compatible same-direction convoys\n- expire reservations when heartbeats stop\n- support atomic replacement during replanning\n- avoid starvation for low-priority robots\n- reject routes using outdated map revisions\n- remain safe during coordinator leader failover\n- emit wait time, conflict, preemption, expiry, and stale-map metrics\n- provide an explain response for denied routes\n\nUse PostgreSQL for durable state and the existing etcd leader lease. Add deterministic simulation tests for crossing traffic, failure during replacement, clock skew, and prolonged high-priority demand.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Design handoff for SecurityCenter.tsx:\n\nThe page already receives active sessions, enrolled factors, recovery methods, recent security events, and organization policy.\n\nRequired UI:\n- top summary highlights actions the user should take\n- sessions group by device with current session clearly identified\n- terminating another session needs confirmation and pending feedback\n- factors show last-used date and whether policy requires them\n- adding a factor opens an accessible step-by-step dialog\n- recovery methods must not reveal secret material\n- recent events use plain-language summaries with expandable technical details\n- narrow screens stack sections; desktop uses a two-column layout\n- live session changes should not move keyboard focus\n- high-risk warnings need icon and text, not color alone\n\nImplement the page with existing hooks and mutations. No identity API changes.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Failure captured during robot testing:\n\n14:08:22.110 mission=991 waypoint=18 pose=(42.12,18.44) map=v128\n14:08:22.114 map_update received revision=v129 transform_dx=0.31 transform_dy=-0.08\n14:08:22.119 planner canceled generation=771\n14:08:22.121 planner started generation=772 map=v129\n14:08:22.124 controller accepted path generation=771 points=34\n14:08:22.130 planner completed generation=772 points=38\n14:08:22.132 controller WARN path rejected generation=772 active=771\n\nThe robot follows the old path until a collision monitor stops it. Cancellation and completion callbacks run on different ROS executors. Determine how the stale generation becomes active, fix ordering safely, and add a deterministic regression test for map updates during planning.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Prepare customer-facing release notes for organization-wide session controls and forced logout.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Consolidate the three certificate loaders while preserving trust-store precedence and diagnostics.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"The navigation stack oscillates between two paths near a narrow obstacle. Find which planner state prevents convergence.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Platform migration notes:\n\nThe company currently has five independent authorization libraries. Java and Go services evaluate static roles locally; the GraphQL gateway calls a Python policy service; mobile APIs use hard-coded ownership checks; batch jobs rely on warehouse grants. Audit events use different action names, and support cannot explain a denied request consistently. Product plans resource sharing, organization groups, temporary grants, and policy simulation. Availability target is 99.99%, and authorization may not silently fail open. Some data-processing jobs run disconnected for twelve hours.\n\nCreate a target architecture and staged migration plan. Cover policy model, decision API, local versus remote evaluation, version pinning, caching, audit schema, explainability, offline jobs, rollout metrics, dual evaluation, emergency controls, ownership, and rollback. No implementation in this phase.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Backend ticket ROB-552\n\nImplement traffic reservations for narrow warehouse aisles. Robots publish route segments with earliest entry, latest exit, width class, and priority. The coordinator must:\n- prevent incompatible overlapping reservations\n- allow compatible same-direction convoys\n- expire reservations when heartbeats stop\n- support atomic replacement during replanning\n- avoid starvation for low-priority robots\n- reject routes using outdated map revisions\n- remain safe during coordinator leader failover\n- emit wait time, conflict, preemption, expiry, and stale-map metrics\n- provide an explain response for denied routes\n\nUse PostgreSQL for durable state and the existing etcd leader lease. Add deterministic simulation tests for crossing traffic, failure during replacement, clock skew, and prolonged high-priority demand.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Design handoff for SecurityCenter.tsx:\n\nThe page already receives active sessions, enrolled factors, recovery methods, recent security events, and organization policy.\n\nRequired UI:\n- top summary highlights actions the user should take\n- sessions group by device with current session clearly identified\n- terminating another session needs confirmation and pending feedback\n- factors show last-used date and whether policy requires them\n- adding a factor opens an accessible step-by-step dialog\n- recovery methods must not reveal secret material\n- recent events use plain-language summaries with expandable technical details\n- narrow screens stack sections; desktop uses a two-column layout\n- live session changes should not move keyboard focus\n- high-risk warnings need icon and text, not color alone\n\nImplement the page with existing hooks and mutations. No identity API changes.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Failure captured during robot testing:\n\n14:08:22.110 mission=991 waypoint=18 pose=(42.12,18.44) map=v128\n14:08:22.114 map_update received revision=v129 transform_dx=0.31 transform_dy=-0.08\n14:08:22.119 planner canceled generation=771\n14:08:22.121 planner started generation=772 map=v129\n14:08:22.124 controller accepted path generation=771 points=34\n14:08:22.130 planner completed generation=772 points=38\n14:08:22.132 controller WARN path rejected generation=772 active=771\n\nThe robot follows the old path until a collision monitor stops it. Cancellation and completion callbacks run on different ROS executors. Determine how the stale generation becomes active, fix ordering safely, and add a deterministic regression test for map updates during planning.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} {"prompt":"Flip requireMfaForAdmins to true.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Extract browser-policy serialization from storage without changing persisted JSON or upgrade behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Review the current emergency-stop arbitration and explain which source wins when hardware and remote commands conflict.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Review the current emergency-stop arbitration and explain which source wins when hardware and remote commands conflict.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Write a short contributor guide for adding new authorization actions and audit names.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Implement a signed command queue for intermittently connected robots with expiry, replay protection, and acknowledgements.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement a signed command queue for intermittently connected robots with expiry, replay protection, and acknowledgements.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Create the Vue policy simulator with resource selectors, decision traces, and side-by-side version comparison.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Replace localhost:3000 with localhost:3001.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Check whether the extension's content-script bridge validates message origins before dispatch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Check whether the extension's content-script bridge validates message origins before dispatch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Draft a strategy for replacing shared administrator accounts with individual privileged access. Address enrollment, just-in-time elevation, approvals, session recording, emergency access, vendor users, legacy devices, evidence retention, and migration milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Write the incident-response procedure for suspected refresh-token theft.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Separate policy parsing from decision execution while preserving every existing result and error.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Robot missions remain leased after the coordinator restarts, but their heartbeats are rejected. Find the epoch mismatch.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Design account-recovery governance for high-value enterprise tenants. Produce roles, approvals, evidence, cooldowns, threat mitigations, and staged adoption; don't implement endpoints.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Add recovery-session examples to the API reference and implement the recovery-session state machine.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Give the permission request dialog clearer grouping and a sticky approval action.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Write the incident-response procedure for suspected refresh-token theft.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Separate policy parsing from decision execution while preserving every existing result and error.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Robot missions remain leased after the coordinator restarts, but their heartbeats are rejected. Find the epoch mismatch.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Design account-recovery governance for high-value enterprise tenants. Produce roles, approvals, evidence, cooldowns, threat mitigations, and staged adoption; don't implement endpoints.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add recovery-session examples to the API reference and implement the recovery-session state machine.","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Give the permission request dialog clearer grouping and a sticky approval action.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Increase the lock icon to 18px.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Rename RobotUser to OperatorIdentity across services while retaining database discriminators and API compatibility.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Why does logout clear cookies but leave the desktop native session active? Diagnose the missing revocation path.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Explain why existing access tokens remain valid briefly after a password change. Assume the documented grace period is intentional.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Convert the current mTLS enrollment implementation into an operator-facing setup guide.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Rename RobotUser to OperatorIdentity across services while retaining database discriminators and API compatibility.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Why does logout clear cookies but leave the desktop native session active? Diagnose the missing revocation path.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Explain why existing access tokens remain valid briefly after a password change. Assume the documented grace period is intentional.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Convert the current mTLS enrollment implementation into an operator-facing setup guide.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Implement a Go transparency log for signing-key events with inclusion proofs and verifiable checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Build the Svelte robot-mission editor with waypoint dragging, validation overlays, and undo history.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Set passwordMinLength to 14.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Assess whether the current audit-event deduplication could hide repeated denied-access attempts.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Assess whether the current audit-event deduplication could hide repeated denied-access attempts.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Create a roadmap for cryptographic agility across stored data, network protocols, tokens, firmware signatures, and customer integrations. Include algorithm inventory, negotiation, downgrade prevention, test infrastructure, migration order, emergency replacement, and ownership.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} {"prompt":"Write release notes for the new phishing-resistant administrator login flow.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Unify duplicated actor-context propagation while preserving tracing and audit fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"The extension's service worker stops receiving alarms after the browser suspends it twice. Locate the lifecycle bug.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Plan a safe transition from manually authored robot maps to continuously updated maps. Cover approval, compatibility, localization impact, rollback, partial fleet rollout, validation evidence, stale missions, and operator controls.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"boundary","lang":"en"} -{"prompt":"Document the policy-bundle signature envelope and implement its verifier in the edge agent.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Make expired-session rows visually distinct and add a one-click cleanup action.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"Correct priviledged to privileged in one enum.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Rename grantId to authorizationId throughout internal code while retaining external field names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Why do some robots ignore a newly revoked operating-zone permission until reboot? Find the invalidation failure.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Explain why the current consent screen requests host access separately from browser-history access. No UI change requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Resume el flujo actual de alta de dispositivos como una guía para administradores, sin cambiar código.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"es"} +{"prompt":"Plan a safe transition from manually authored robot maps to continuously updated maps. Cover approval, compatibility, localization impact, rollback, partial fleet rollout, validation evidence, stale missions, and operator controls.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Document the policy-bundle signature envelope and implement its verifier in the edge agent.","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Make expired-session rows visually distinct and add a one-click cleanup action.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Correct priviledged to privileged in one enum.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename grantId to authorizationId throughout internal code while retaining external field names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Why do some robots ignore a newly revoked operating-zone permission until reboot? Find the invalidation failure.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Explain why the current consent screen requests host access separately from browser-history access. No UI change requested.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Resume el flujo actual de alta de dispositivos como una guía para administradores, sin cambiar código.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} {"prompt":"Implement an encrypted local command journal for a robot controller with power-loss recovery and bounded flash wear.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Build the React session-management drawer with device details, revocation progress, and current-session protection.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Pin jose to 6.1.0.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Examine the robot's map-signature verification and determine whether rollback to an older signed map is possible.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Lay out a migration from one organization-wide encryption key to per-tenant envelope encryption. Include data inventory, key hierarchy, online re-encryption, backups, search indexes, analytics copies, disaster recovery, observability, rollback, and deletion guarantees.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Document how developers should test browser-extension permissions across Chrome, Firefox, and Edge.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Move token-hash comparison into a shared constant-time helper without changing supported formats.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Move token-hash comparison into a shared constant-time helper without changing supported formats.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Authentication requests spike CPU only when invalid JWTs contain many dotted segments. Find the pathological parsing path.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Design delegated robot-fleet management, then implement scoped fleet invitations and acceptance.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"Add authorization decision exports and build the administrator UI for requesting them.","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} -{"prompt":"Create the security-key enrollment wizard and add the endpoint for naming registered credentials.","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Add authorization decision exports and build the administrator UI for requesting them.","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Create the security-key enrollment wizard and add the endpoint for naming registered credentials.","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Investigate delayed robot revocation, fix cache propagation, and document the revised consistency window.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Change cookieSameSite to strict.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Extract shared permission-test fixtures without changing their scenario coverage.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Review the current password-reset implementation for account-enumeration differences across response paths.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Extract shared permission-test fixtures without changing their scenario coverage.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Review the current password-reset implementation for account-enumeration differences across response paths.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Write a concise ADR for storing authorization policies in versioned bundles.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Create a Rust service that issues SPIFFE-compatible workload certificates with renewal and revocation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Create a Rust service that issues SPIFFE-compatible workload certificates with renewal and revocation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Implement the browser extension's per-site privacy dashboard with trackers, cookies, and permission history.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Remove the obsolete OAuth scope.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Explain how the existing credential broker prevents one workload from claiming another workload's identity.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Develop an architecture for cross-company access to shared project resources. Cover external identities, trust federation, invitations, lifecycle, policy boundaries, audit evidence, breach containment, data residency, and migration from guest accounts.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Prepare a troubleshooting guide for clock-skew errors in signed API requests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Remove the obsolete OAuth scope.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Explain how the existing credential broker prevents one workload from claiming another workload's identity.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Develop an architecture for cross-company access to shared project resources. Cover external identities, trust federation, invitations, lifecycle, policy boundaries, audit evidence, breach containment, data residency, and migration from guest accounts.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Prepare a troubleshooting guide for clock-skew errors in signed API requests.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Separate mission authorization from mission scheduling without changing accepted commands.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Robot telemetry decrypts correctly but fails authentication after packet reordering. Find the nonce-window bug.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Create a phased strategy for replacing security questions with stronger recovery methods. Plan customer communication, legacy accounts, support exceptions, fraud controls, accessibility, metrics, and final removal; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Add examples to the access-review API docs and implement the review-completion transaction.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Give policy-denial messages a clearer hierarchy and expandable technical details.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"Change the key icon from 16px to 17px.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Rename membershipRole to accessRole across packages while retaining GraphQL and database compatibility.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Why do hardware-backed credentials fail only after an Android security patch? Diagnose the attestation-chain issue.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Explain why support impersonation sessions cannot create new API keys. Assume the restriction is intended.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Transform the current audit-search behavior into a user guide for compliance administrators.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Robot telemetry decrypts correctly but fails authentication after packet reordering. Find the nonce-window bug.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create a phased strategy for replacing security questions with stronger recovery methods. Plan customer communication, legacy accounts, support exceptions, fraud controls, accessibility, metrics, and final removal; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add examples to the access-review API docs and implement the review-completion transaction.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Give policy-denial messages a clearer hierarchy and expandable technical details.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Change the key icon from 16px to 17px.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename membershipRole to accessRole across packages while retaining GraphQL and database compatibility.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Why do hardware-backed credentials fail only after an Android security patch? Diagnose the attestation-chain issue.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Explain why support impersonation sessions cannot create new API keys. Assume the restriction is intended.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Transform the current audit-search behavior into a user guide for compliance administrators.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Add a distributed lock service for robot maintenance bays with fencing tokens and lease recovery.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Build the SolidJS access-review table with bulk decisions, inherited context, and sticky identity columns.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Build the SolidJS access-review table with bulk decisions, inherited context, and sticky identity columns.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Set enrollmentCodeTTL to 15m.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Assess whether the current recovery-code generator introduces modulo bias or ambiguous characters.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Assess whether the current recovery-code generator introduces modulo bias or ambiguous characters.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Architect a secure software-supply-chain program for robot firmware, browser extensions, backend services, and infrastructure modules. Cover provenance, signing, dependency policy, build isolation, promotion, verification, revocation, incident response, and phased enforcement.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} -{"prompt":"Write customer-facing release notes for improved session visibility and remote sign-out.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Consolidate duplicate scope-matching functions without changing wildcard or case behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"The robot control UI shows stale permission state after reconnect even though commands are rejected correctly. Find the subscription issue.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"continue the identity roadmap","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} -{"prompt":"finish the auth endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Write customer-facing release notes for improved session visibility and remote sign-out.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Consolidate duplicate scope-matching functions without changing wildcard or case behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"The robot control UI shows stale permission state after reconnect even though commands are rejected correctly. Find the subscription issue.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"finish the auth endpoint","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"make the extension friendlier","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} -{"prompt":"tiny permission config tweak","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} -{"prompt":"clean up the claims code","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"chase the robot auth issue","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} -{"prompt":"look over the key flow","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"write up access behavior","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"tiny permission config tweak","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"clean up the claims code","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"chase the robot auth issue","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"look over the key flow","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"write up access behavior","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Implement an append-only authorization audit service with tenant partitions, integrity checkpoints, and retention enforcement.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Create the React robot-access matrix with zone filters, temporary grants, and expiration previews.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the React robot-access matrix with zone filters, temporary grants, and expiration previews.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Bump Chrome minimum version to 130.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Review the existing DPoP proof verifier for replay behavior across clustered API instances.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Review the existing DPoP proof verifier for replay behavior across clustered API instances.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Plan a transition from password-based robot technician access to passkeys and device certificates. Include shared workstations, offline sites, lost devices, recovery, authorization, fleet rollout, support, and legacy-controller compatibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Write an administrator guide for configuring conditional access by network zone and device posture.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Decouple audit serialization from transport while preserving exact event payloads.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Decouple audit serialization from transport while preserving exact event payloads.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"MFA prompts loop forever when two browser tabs complete enrollment simultaneously. Determine the state conflict.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Design the decommissioning process for an identity region. Deliver dependency inventory, session migration, key handling, routing, audit retention, rollback windows, and verification criteria rather than implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Document robot command delegation and implement its signed delegation-token validator.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Add a compact visual timeline for recent sign-ins and security changes.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"Replace allowInsecure: yes with false.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Rename policyRevision to policyVersion repository-wide while keeping serialized names stable.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Why do certificate renewals fail only for robots that were offline during CA rotation? Find the chain-building failure.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Explain why the browser extension stores granted origins separately from requested origins. No bug is reported.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Convert the existing privileged-session logic into a concise auditor-facing control description.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Build a Kotlin service that manages time-limited access grants with approvals, expiry, and immutable audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Design the decommissioning process for an identity region. Deliver dependency inventory, session migration, key handling, routing, audit retention, rollback windows, and verification criteria rather than implementation.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Document robot command delegation and implement its signed delegation-token validator.","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Add a compact visual timeline for recent sign-ins and security changes.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Replace allowInsecure: yes with false.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename policyRevision to policyVersion repository-wide while keeping serialized names stable.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Why do certificate renewals fail only for robots that were offline during CA rotation? Find the chain-building failure.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Explain why the browser extension stores granted origins separately from requested origins. No bug is reported.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Convert the existing privileged-session logic into a concise auditor-facing control description.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Build a Kotlin service that manages time-limited access grants with approvals, expiry, and immutable audit events.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Implement the browser extension's request-trace viewer with grouped redirects and redacted headers.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Remove the duplicate OAuth callback URL.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Inspect the current policy-cache key and determine whether organization context can collide across regions.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Inspect the current policy-cache key and determine whether organization context can collide across regions.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Create a multi-year roadmap for customer-managed encryption keys across databases, object storage, search, queues, and backups. Include control-plane boundaries, key outages, rotation, revocation, migration, support responsibilities, and availability tradeoffs.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} -{"prompt":"Prepare the README for the robot identity simulator, including enrollment and revocation scenarios.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Split browser storage migration from rules initialization without changing startup behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"A signed robot command validates on x86 but fails on ARM because the canonical payload differs. Find the serialization discrepancy.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Prepare the README for the robot identity simulator, including enrollment and revocation scenarios.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Split browser storage migration from rules initialization without changing startup behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"A signed robot command validates on x86 but fails on ARM because the canonical payload differs. Find the serialization discrepancy.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Design emergency access governance, then implement time-boxed break-glass sessions with approval evidence.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"Add robot-zone grant persistence and build the admin map used to manage grants.","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Add robot-zone grant persistence and build the admin map used to manage grants.","purpose":"backendImpl","secondary":"frontendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Create the passkey management screen and implement credential-renaming support in the API.","purpose":"frontendImpl","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Diagnose missing audit actors, fix context propagation, and document the corrected background-job contract.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Change authTimeoutMs to 5000.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Extract the shared certificate-test builder without altering fixtures or assertions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Extract the shared certificate-test builder without altering fixtures or assertions.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Assess whether the current robot enrollment QR code leaks reusable bootstrap material.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write a migration guide for services moving from API keys to workload identity.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Implement a replay-resistant signed webhook receiver in Python with streaming body verification.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Build the responsive organization-role editor with permission previews and unsaved-change warnings.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Write a migration guide for services moving from API keys to workload identity.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Implement a replay-resistant signed webhook receiver in Python with streaming body verification.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Build the responsive organization-role editor with permission previews and unsaved-change warnings.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Set maxLoginAttempts to 8.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Explain how the existing authorization service preserves consistency during policy-bundle replacement.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Architect secure fleet-to-cloud communication for ten million intermittently connected devices. Cover identity, key rotation, routing, replay protection, protocol versions, revocation distribution, regional failure, manufacturing, observability, and incremental migration.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Explain how the existing authorization service preserves consistency during policy-bundle replacement.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Architect secure fleet-to-cloud communication for ten million intermittently connected devices. Cover identity, key rotation, routing, replay protection, protocol versions, revocation distribution, regional failure, manufacturing, observability, and incremental migration.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1,"slice":"core","lang":"en"} {"prompt":"Draft release notes for improved recovery-code security and session revocation.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Unify duplicated organization-id validation while preserving authorization errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"The browser occasionally sends requests before the extension restores its deny rules. Locate the startup ordering bug.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Map a strategy for retiring legacy RSA signing keys. Include client inventory, dual signing, verification telemetry, offline robots, emergency rollback, partner communication, and final key destruction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Add delegation examples to the SDK docs and implement delegation-chain validation.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Make the security summary card easier to scan with grouped status indicators.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} -{"prompt":"Change the banner padding to 12px.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Rename credentialFamily to sessionFamily throughout internal code while preserving storage columns.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Why does a robot accept one final command after its certificate is revoked? Identify the unknown caching path.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Explain why recovery sessions cannot modify MFA factors until reauthentication. Assume this is intentional.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"既存の workload identity 実装を、新しいサービスチーム向けの導入ガイドにまとめてください。","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"ja"} +{"prompt":"Unify duplicated organization-id validation while preserving authorization errors.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"The browser occasionally sends requests before the extension restores its deny rules. Locate the startup ordering bug.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Map a strategy for retiring legacy RSA signing keys. Include client inventory, dual signing, verification telemetry, offline robots, emergency rollback, partner communication, and final key destruction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add delegation examples to the SDK docs and implement delegation-chain validation.","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Make the security summary card easier to scan with grouped status indicators.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Change the banner padding to 12px.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename credentialFamily to sessionFamily throughout internal code while preserving storage columns.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Why does a robot accept one final command after its certificate is revoked? Identify the unknown caching path.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Explain why recovery sessions cannot modify MFA factors until reauthentication. Assume this is intentional.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"既存の workload identity 実装を、新しいサービスチーム向けの導入ガイドにまとめてください。","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"ja"} {"prompt":"Create a Go policy-bundle distributor with signed revisions, resumable downloads, and stale-client metrics.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Build the robot incident-review UI with synchronized map playback, logs, and command history.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Pin cryptography to 45.0.5.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Review the current device-attestation verifier for certificate-chain and nonce-binding gaps.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Design a privacy-preserving identity-linking system for users with accounts across multiple acquired products. Cover proof, consent, unlinking, conflicting attributes, bans, deletion, auditability, migration, and support operations.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Review the current device-attestation verifier for certificate-chain and nonce-binding gaps.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Design a privacy-preserving identity-linking system for users with accounts across multiple acquired products. Cover proof, consent, unlinking, conflicting attributes, bans, deletion, auditability, migration, and support operations.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1,"slice":"core","lang":"en"} {"prompt":"Write an FAQ for administrators about session duration, idle timeout, and forced reauthentication.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} -{"prompt":"Decouple extension rule evaluation from Chrome APIs without changing matching results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Clock synchronization makes active robot leases expire in bulk. Find which expiry comparisons use wall time.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"pick up the trust plan","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} -{"prompt":"finish the identity service","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"Create the mobile-friendly robot enrollment wizard with camera, manual-code, and recovery paths.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Decouple extension rule evaluation from Chrome APIs without changing matching results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Clock synchronization makes active robot leases expire in bulk. Find which expiry comparisons use wall time.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"finish the identity service","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} +{"prompt":"Create the mobile-friendly robot enrollment wizard with camera, manual-code, and recovery paths.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Fix the misspelled AUDIT_RETENTON key.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Separate enrollment token parsing from verification without changing accepted tokens.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Users are logged into the wrong tenant after accepting invitations in two tabs. Find the session-context race.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Inspect the current policy explanation output and identify where sensitive resource attributes could leak.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Separate enrollment token parsing from verification without changing accepted tokens.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Users are logged into the wrong tenant after accepting invitations in two tabs. Find the session-context race.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Inspect the current policy explanation output and identify where sensitive resource attributes could leak.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Rédige une procédure de récupération pour les administrateurs qui perdent leur unique security key.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"fr"} {"prompt":"Design a migration from hand-authored feature SQL to a governed feature platform. Cover ownership, point-in-time correctness, offline and online parity, lineage, schema evolution, backfills, validation gates, cost controls, adoption milestones, and rollback for models that regress after switching sources.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Implement a Python worker that joins click events to the latest eligible catalog snapshot without leaking future data.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Build the model-run comparison page with aligned metric charts, dataset filters, confidence intervals, and shareable URLs.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Bump scikit-learn to 1.7.1","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Extract common tensor validation from the three inference adapters without changing accepted shapes or error messages.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Our recommender returns nearly identical results for every user after several hours. Find where embeddings or cache keys collapse.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Audit the training split code for temporal leakage","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write the dataset card for product-search-v5","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Our recommender returns nearly identical results for every user after several hours. Find where embeddings or cache keys collapse.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Audit the training split code for temporal leakage","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Write the dataset card for product-search-v5","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Lay out an RFC for serving multiple embedding-model generations concurrently. Address version routing, index ownership, storage growth, mixed-version queries, cache isolation, tenant migrations, deletion propagation, quality comparisons, fallback, and a milestone sequence that avoids rebuilding every vector index at once.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Add streaming JSONL ingestion to the labeling CLI","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Create the annotation-review workspace with synchronized image zoom, hotkeys, issue tags, and reviewer progress.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Set TRAINING_SEED to 4821","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Move normalization statistics loading behind one shared transform while preserving current floating-point outputs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Validation loss becomes NaN only with mixed precision and sequence lengths above 2048. Trace the first invalid operation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Move normalization statistics loading behind one shared transform while preserving current floating-point outputs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Validation loss becomes NaN only with mixed precision and sequence lengths above 2048. Trace the first invalid operation.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Explain how the batch sampler balances languages and whether replacement is used. No edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} -{"prompt":"Draft the model rollback runbook","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Draft the model rollback runbook","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Propose a long-term architecture for privacy-preserving model evaluation on customer data. Include aggregation boundaries, minimum cohort sizes, deletion handling, reproducibility, experiment isolation, abuse prevention, auditability, regional constraints, failure modes, and phased validation before any results influence production promotion.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} {"prompt":"Implement checkpoint compaction for the distributed trainer so workers can resume without downloading every historical shard.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Add a responsive confusion-matrix viewer with normalized/raw modes, tooltips, zoom, and color-blind-safe palettes.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add a responsive confusion-matrix viewer with normalized/raw modes, tooltips, zoom, and color-blind-safe palettes.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Correct the dataset filename in configs/eval.yaml","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Separate experiment assignment from metric emission without changing cohort membership or event fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"The feature backfill duplicates about 0.2% of rows after worker preemption. Determine which checkpoint or idempotency assumption fails.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Check whether the current vector-distance fallback is mathematically equivalent to the SIMD path for zero-length inputs.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Separate experiment assignment from metric emission without changing cohort membership or event fields.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"The feature backfill duplicates about 0.2% of rows after worker preemption. Determine which checkpoint or idempotency assumption fails.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Check whether the current vector-distance fallback is mathematically equivalent to the SIMD path for zero-length inputs.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Escribe una guía para reproducir experimentos antiguos usando los snapshots de datos y el registro de modelos.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} {"prompt":"Develop a roadmap for replacing the batch-only fraud model with hybrid streaming and batch features. Cover event-time handling, delayed labels, replay, online/offline consistency, cold starts, model refresh cadence, serving degradation, audit evidence, shadow evaluation, and independently reversible implementation milestones.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Build a Rust service that validates model artifacts, computes content hashes, and publishes immutable registry records.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Implement the feature-lineage graph with expandable nodes, search, impact highlighting, and keyboard navigation.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Change the chart label from 'AUC %' to 'AUC'","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Rename TrainingExample to LabeledExample across Python, Protobuf, and tests while preserving stored field names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Why does the GPU worker silently switch to CPU after the third checkpoint? Training becomes unusably slow and the trigger is unknown.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Why is temperature scaling applied before tenant-specific calibration? Determine the intended current rationale; metrics are not known to be broken.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Document the existing prediction endpoint, including tensor formats, batching behavior, limits, and response examples.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Plan the move from MLflow artifacts to an internal immutable registry, including data migration and rollout gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"The architecture in adr/042-online-features.md is approved; implement its Redis write-through path and version checks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Add a compact model-status card with promotion state, health indicators, version history, and loading behavior.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Replace `trian_split` with `train_split` in one notebook utility","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Reorganize feature computation into source, transform, and sink layers while preserving rows, ordering, and metrics.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Investigate the unexplained ranking regression, restore correct behavior after locating the cause, and add a reproducible evaluation case.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"Review the current training-data deletion pipeline, then produce a compliance memo describing guarantees and gaps.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Change the chart label from 'AUC %' to 'AUC'","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rename TrainingExample to LabeledExample across Python, Protobuf, and tests while preserving stored field names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Why does the GPU worker silently switch to CPU after the third checkpoint? Training becomes unusably slow and the trigger is unknown.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Why is temperature scaling applied before tenant-specific calibration? Determine the intended current rationale; metrics are not known to be broken.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Document the existing prediction endpoint, including tensor formats, batching behavior, limits, and response examples.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Plan the move from MLflow artifacts to an internal immutable registry, including data migration and rollout gates.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"The architecture in adr/042-online-features.md is approved; implement its Redis write-through path and version checks.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add a compact model-status card with promotion state, health indicators, version history, and loading behavior.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Replace `trian_split` with `train_split` in one notebook utility","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Reorganize feature computation into source, transform, and sink layers while preserving rows, ordering, and metrics.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Investigate the unexplained ranking regression, restore correct behavior after locating the cause, and add a reproducible evaluation case.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Review the current training-data deletion pipeline, then produce a compliance memo describing guarantees and gaps.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} {"prompt":"Write the inference API guide and add a runnable Python client that demonstrates streaming batches and retries.","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"Plan and implement the first stage of feature schema versioning: define compatibility rules, then add registry validation behind a warning-only mode.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Plan and implement the first stage of feature schema versioning: define compatibility rules, then add registry validation behind a warning-only mode.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Implement the drift-alert evaluator and document every emitted metric, threshold, and suppression rule.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Ticket MLUI-611\n\nResearchers compare up to six evaluation runs. The current page renders six separate full-width charts, forcing constant scrolling and making aligned time points impossible to inspect.\n\nRequirements:\n- metric selector supports accuracy, F1, latency, and calibration error\n- chosen runs share one x-axis but retain distinct series colors\n- hovering pins a vertical cursor across all visible plots\n- users can hide individual runs without losing selection\n- narrow screens use a horizontally scrollable plot, not compressed labels\n- exported PNG must include run names and dataset version\n\nImplement the comparison workspace in web/src/evaluation. Reuse our Vega wrapper and existing run query.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Ticket MLUI-611\n\nResearchers compare up to six evaluation runs. The current page renders six separate full-width charts, forcing constant scrolling and making aligned time points impossible to inspect.\n\nRequirements:\n- metric selector supports accuracy, F1, latency, and calibration error\n- chosen runs share one x-axis but retain distinct series colors\n- hovering pins a vertical cursor across all visible plots\n- users can hide individual runs without losing selection\n- narrow screens use a horizontally scrollable plot, not compressed labels\n- exported PNG must include run names and dataset version\n\nImplement the comparison workspace in web/src/evaluation. Reuse our Vega wrapper and existing run query.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Failing nightly command:\n\n$ python -m pipelines.evaluate --config configs/nightly.yaml\nFileNotFoundError: data/eval/golden-v6.parqet\n\nRepository paths:\ndata/eval/golden-v6.parquet\nconfigs/nightly.yaml: dataset: data/eval/golden-v6.parqet\nconfigs/release.yaml: dataset: data/eval/golden-v6.parquet\n\nThe nightly config contains a known misspelling. Correct only that path to `data/eval/golden-v6.parquet`. Do not regenerate data, edit the loader, or touch release.yaml.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"pasted-context","lang":"en"} -{"prompt":"Refactoring brief from maintainers:\n\ntrainer/checkpoint.py currently serializes model state, uploads blobs, updates registry metadata, prunes old checkpoints, and sends Slack alerts. The evaluator duplicates blob hashing and registry writes. Tests mock storage internals through CheckpointManager.\n\nDesired ownership:\n- artifact package: hashing and blob I/O\n- registry package: immutable metadata records\n- trainer: checkpoint policy\n- notifications: observes published events\n\nRestructure these modules and share artifact persistence with evaluator. Preserve checkpoint file bytes, registry schema, retention decisions, exception types, and CheckpointManager's public interface.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Training log excerpt:\n\nstep=18820 loss=2.431 scale=8192 grad_norm=1.92\nstep=18821 loss=2.389 scale=8192 grad_norm=2.07\nstep=18822 loss=nan scale=4096 grad_norm=nan\nrank=3 attention_scores min=-inf max=inf seq_len=3072\nrank=0 attention_scores min=-31.2 max=28.7 seq_len=2048\nwarning: all_reduce completed with mismatched tensor shapes\n\nThe failure appears only when one rank receives a sequence longer than 2048 and gradient checkpointing is enabled. Find the first invalid shape or operation and explain why collective validation did not fail earlier. Diagnosis before code changes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Refactoring brief from maintainers:\n\ntrainer/checkpoint.py currently serializes model state, uploads blobs, updates registry metadata, prunes old checkpoints, and sends Slack alerts. The evaluator duplicates blob hashing and registry writes. Tests mock storage internals through CheckpointManager.\n\nDesired ownership:\n- artifact package: hashing and blob I/O\n- registry package: immutable metadata records\n- trainer: checkpoint policy\n- notifications: observes published events\n\nRestructure these modules and share artifact persistence with evaluator. Preserve checkpoint file bytes, registry schema, retention decisions, exception types, and CheckpointManager's public interface.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Training log excerpt:\n\nstep=18820 loss=2.431 scale=8192 grad_norm=1.92\nstep=18821 loss=2.389 scale=8192 grad_norm=2.07\nstep=18822 loss=nan scale=4096 grad_norm=nan\nrank=3 attention_scores min=-inf max=inf seq_len=3072\nrank=0 attention_scores min=-31.2 max=28.7 seq_len=2048\nwarning: all_reduce completed with mismatched tensor shapes\n\nThe failure appears only when one rank receives a sequence longer than 2048 and gradient checkpointing is enabled. Find the first invalid shape or operation and explain why collective validation did not fail earlier. Diagnosis before code changes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} {"prompt":"Proposed sampling change:\n\ndiff --git a/data/sampler.py b/data/sampler.py\n@@\n- rng = random.Random(seed + epoch)\n- rng.shuffle(indices)\n+ rng = np.random.default_rng(seed)\n+ indices = rng.choice(indices, size=len(indices), replace=True)\n@@\n- return indices[rank::world_size]\n+ return np.array_split(indices, world_size)[rank]\n\nThe author says this only improves performance while preserving deterministic balanced sampling. Review determinism across epochs, replacement, shard sizes, duplicates, resume behavior, and compatibility with existing golden orders. Do not edit the patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"Write something for the model API","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} -{"prompt":"Work out the platform direction","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} -{"prompt":"Finish the pipeline piece","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Write something for the model API","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Work out the platform direction","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"vague-eval","lang":"en"} +{"prompt":"Finish the pipeline piece","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} {"prompt":"Build the Kubernetes rollout timeline with pod states, deployment events, revision markers, and auto-refresh pause controls.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Set the dev cluster region to eu-west-1","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Extract provider-neutral DNS reconciliation from the Route53 controller without changing record behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Pods remain Terminating for twenty minutes after a node disappears. Determine whether finalizers, volume detach, or eviction handling is stuck.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Assess the Terraform state bucket policy for cross-account access and deletion protection. Findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write the on-call guide for failed Argo rollouts","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Pods remain Terminating for twenty minutes after a node disappears. Determine whether finalizers, volume detach, or eviction handling is stuck.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Assess the Terraform state bucket policy for cross-account access and deletion protection. Findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Write the on-call guide for failed Argo rollouts","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Create a phased architecture plan for moving background jobs from Kubernetes CronJobs to a shared scheduler. Include tenancy, fairness, deadlines, retries, dependency graphs, secrets, regional failover, observability, migration adapters, rollback, and milestones that let individual teams opt in without coupling release schedules.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Implement a Go reconciler that renews external DNS leases with fencing tokens and conflict-safe retries.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Create the cloud-cost explorer with grouped filters, daily stacked charts, budget overlays, and drill-down tables.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Bump the base image to Debian 13","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Bump the base image to Debian 13","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"Deduplicate HTTP client construction across the AWS, GCP, and Azure adapters while preserving timeouts and retries.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"The ingress controller leaks file descriptors during certificate reloads and eventually stops accepting connections. Locate the unclosed resource.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Explain how preview environments receive isolated database roles and when those roles are revoked.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"The ingress controller leaks file descriptors during certificate reloads and eventually stops accepting connections. Locate the unclosed resource.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Explain how preview environments receive isolated database roles and when those roles are revoked.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Rédige les notes de migration pour le nouveau chart Helm, avec les valeurs renommées et la procédure de rollback.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"fr"} {"prompt":"Architect a regional failover strategy for the deployment control plane. Address authoritative state, in-flight operations, fencing, artifact availability, DNS, credential scope, duplicate execution, operator control, degraded modes, recovery testing, and a rollout path from today's single-region system with measurable abort criteria.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} -{"prompt":"Add per-namespace fairness to the Rust build queue with weighted limits and starvation metrics.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Implement a responsive policy-violation drawer with code snippets, remediation links, suppression controls, and keyboard focus restoration.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add per-namespace fairness to the Rust build queue with weighted limits and starvation metrics.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement a responsive policy-violation drawer with code snippets, remediation links, suppression controls, and keyboard focus restoration.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Change replicas from 2 to 3","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Move environment-name normalization into a shared package while keeping all accepted spellings and error strings unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Move environment-name normalization into a shared package while keeping all accepted spellings and error strings unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Terraform reports perpetual diffs for IAM conditions even immediately after apply. Find the normalization or provider mismatch.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Walk through how the current admission webhook handles timeouts and failurePolicy settings across clusters.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Draft a runbook for rotating the container registry credentials","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Draft a runbook for rotating the container registry credentials","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Plan a migration from bespoke service dashboards to standardized OpenTelemetry service views. Include semantic conventions, legacy metric mapping, cardinality budgets, traces-to-logs correlation, ownership, SLO compatibility, dual-running, validation, training, and retirement milestones for old dashboards and exporters.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Build a controller that snapshots PersistentVolumeClaims on policy schedules and records restore metadata.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Build a controller that snapshots PersistentVolumeClaims on policy schedules and records restore metadata.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Add an environment-creation wizard with quota estimates, region compatibility warnings, progress states, and retryable failures.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Correct the Helm repository URL","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Split policy evaluation, formatting, and CLI exit handling into separate modules with identical outputs and exit codes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"A canary rollout occasionally promotes despite failed analysis runs. Trace the race between metric evaluation and deadline handling.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Review whether the current backup retention rules satisfy monthly and yearly restore requirements. No configuration changes.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"A canary rollout occasionally promotes despite failed analysis runs. Trace the race between metric evaluation and deadline handling.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Review whether the current backup retention rules satisfy monthly and yearly restore requirements. No configuration changes.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Create contributor docs for adding a new cloud provider adapter","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Define a roadmap for replacing long-lived CI cloud keys with federated identity. Cover trust configuration, repository scoping, pull requests from forks, reusable workflows, emergency fallback, auditability, phased enforcement, detection of remaining keys, and rollback if release pipelines cannot assume roles.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Implement an idempotent cleanup worker for expired preview stacks with dependency-aware deletion and resumable checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement an idempotent cleanup worker for expired preview stacks with dependency-aware deletion and resumable checkpoints.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Build the incident overview screen with service topology, active alerts, timeline annotations, and role-based action visibility.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Disable TRACE_EXPORT in local.env","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Rename ClusterLease to ControlLease across services while preserving CRD fields and stored resource names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"DNS records disappear briefly during no-op reconciliations in one region. Determine why the controller deletes before confirming replacements.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Examine the current network-policy generator and tell me whether empty peer lists mean deny-all or no restriction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Document the current deployment API, including rollout phases, cancellation semantics, and retry examples.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Plan the transition from static namespaces to virtual clusters; implementation belongs in later work.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Implement the approved backup manifest format and validation rules in backup-controller.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Erstelle die UI für den Rollback-Dialog mit Revisionsvergleich, Risikohinweis und klarer Bestätigung.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"de"} -{"prompt":"Set the warning icon to 16px","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Reorganize cloud credentials by provider without changing resolution order or supported environment variables.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} -{"prompt":"Why does the scheduler launch two copies of a singleton job after leader failover? The duplicate execution is broken and unexplained.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Explain why the current autoscaler ignores pending pods with local volumes; nothing is currently reported as failing.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Write a plain-language overview of how infrastructure plans become applied changes, based on existing code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Design the migration to signed deployment manifests and implement signature verification in audit-only mode.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Rename ClusterLease to ControlLease across services while preserving CRD fields and stored resource names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"DNS records disappear briefly during no-op reconciliations in one region. Determine why the controller deletes before confirming replacements.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Examine the current network-policy generator and tell me whether empty peer lists mean deny-all or no restriction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Document the current deployment API, including rollout phases, cancellation semantics, and retry examples.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Plan the transition from static namespaces to virtual clusters; implementation belongs in later work.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Implement the approved backup manifest format and validation rules in backup-controller.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Erstelle die UI für den Rollback-Dialog mit Revisionsvergleich, Risikohinweis und klarer Bestätigung.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"de"} +{"prompt":"Set the warning icon to 16px","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Reorganize cloud credentials by provider without changing resolution order or supported environment variables.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Why does the scheduler launch two copies of a singleton job after leader failover? The duplicate execution is broken and unexplained.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Explain why the current autoscaler ignores pending pods with local volumes; nothing is currently reported as failing.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Write a plain-language overview of how infrastructure plans become applied changes, based on existing code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Design the migration to signed deployment manifests and implement signature verification in audit-only mode.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} {"prompt":"Add a capacity-report command and document its flags, JSON schema, and automation examples.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} {"prompt":"Create the secrets-rotation status page and add a support note explaining each displayed state.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"Fix the known staging account ID and update the assertion that copied the old value.","purpose":"quickFix","secondary":"backendImpl","mixed":true,"difficulty":0.3,"slice":"mixed","lang":"en"} -{"prompt":"Consolidate resource label parsing with unchanged behavior, then document the accepted syntax for maintainers.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"Infrastructure review excerpt:\n\nresource \"aws_iam_role\" \"preview_runner\" {\n assume_role_policy = data.aws_iam_policy_document.runner_assume.json\n}\n\ndata \"aws_iam_policy_document\" \"runner_assume\" {\n statement {\n actions = [\"sts:AssumeRole\"]\n principals { type = \"AWS\", identifiers = [\"*\"] }\n condition { test = \"StringLike\", variable = \"aws:PrincipalArn\", values = [\"arn:aws:iam::*:role/ci-*\"] }\n }\n}\n\nThe role policy grants CloudFormation, IAM PassRole, and S3 artifact access. Review whether the wildcard principal plus condition safely limits assumption, and assess confused-deputy, account-boundary, and PassRole risks. Findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Docs ticket OPS-1287\n\nThe restore command now has three phases:\n1. validate checks snapshot metadata and encryption-key access\n2. stage restores into an isolated namespace\n3. promote switches service routing after health checks\n\nFlags are `--snapshot`, `--target`, `--skip-promote`, and `--max-lag`. A failed promote leaves the staged database running for inspection. Running the same restore ID resumes from its last completed phase. Operators keep assuming retries start over and deleting the staged namespace.\n\nRewrite docs/runbooks/restore.md to explain phases, resume behavior, cleanup, flags, and abort conditions. No controller changes.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} -{"prompt":"Planning notes from platform sync:\n\n- 430 repositories use static AWS keys in CI secrets.\n- 60 accept pull requests from forks.\n- reusable release workflows run in a central repository.\n- some self-hosted runners lack outbound access to the identity provider.\n- security wants keys disabled within six months.\n- release engineering requires a one-command emergency fallback.\n\nProduce a phased workload-identity migration plan. Define trust boundaries, repository enrollment, fork behavior, central workflow claims, offline-runner handling, telemetry, enforcement gates, emergency access, and rollback. Do not implement provider resources yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Story PLATFORM-731\n\nCreate `platformctl snapshots prune`.\n\nRules:\n- retain the newest 14 daily, 8 weekly, and 12 monthly snapshots per database\n- snapshots under legal hold are never deleted\n- dry-run is default; `--execute` performs deletions\n- concurrent invocations must not delete the same snapshot twice\n- partial cloud failures should be resumable\n- JSON output includes kept/deleted/reason for every candidate\n- exit 2 when policy configuration is invalid, 1 for operational failure\n\nImplement the command and shared retention engine in Rust with golden tests and a fake object-store integration suite.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Dashboard request:\n\nOperators need a live view of namespace quota pressure. Each row shows requested, used, and limit for CPU, memory, GPU, and persistent storage. Values update every 15 seconds. Above 80% use warning colors; above 95% use critical colors plus text, never color alone. Rows can expand to list the five largest workloads. Filters cover cluster, owner, and environment. On mobile, metrics stack inside cards. Implement this in console/src/quotas using the existing metrics endpoint and design tokens.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Fix the known staging account ID and update the assertion that copied the old value.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Consolidate resource label parsing with unchanged behavior, then document the accepted syntax for maintainers.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Infrastructure review excerpt:\n\nresource \"aws_iam_role\" \"preview_runner\" {\n assume_role_policy = data.aws_iam_policy_document.runner_assume.json\n}\n\ndata \"aws_iam_policy_document\" \"runner_assume\" {\n statement {\n actions = [\"sts:AssumeRole\"]\n principals { type = \"AWS\", identifiers = [\"*\"] }\n condition { test = \"StringLike\", variable = \"aws:PrincipalArn\", values = [\"arn:aws:iam::*:role/ci-*\"] }\n }\n}\n\nThe role policy grants CloudFormation, IAM PassRole, and S3 artifact access. Review whether the wildcard principal plus condition safely limits assumption, and assess confused-deputy, account-boundary, and PassRole risks. Findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Docs ticket OPS-1287\n\nThe restore command now has three phases:\n1. validate checks snapshot metadata and encryption-key access\n2. stage restores into an isolated namespace\n3. promote switches service routing after health checks\n\nFlags are `--snapshot`, `--target`, `--skip-promote`, and `--max-lag`. A failed promote leaves the staged database running for inspection. Running the same restore ID resumes from its last completed phase. Operators keep assuming retries start over and deleting the staged namespace.\n\nRewrite docs/runbooks/restore.md to explain phases, resume behavior, cleanup, flags, and abort conditions. No controller changes.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Planning notes from platform sync:\n\n- 430 repositories use static AWS keys in CI secrets.\n- 60 accept pull requests from forks.\n- reusable release workflows run in a central repository.\n- some self-hosted runners lack outbound access to the identity provider.\n- security wants keys disabled within six months.\n- release engineering requires a one-command emergency fallback.\n\nProduce a phased workload-identity migration plan. Define trust boundaries, repository enrollment, fork behavior, central workflow claims, offline-runner handling, telemetry, enforcement gates, emergency access, and rollback. Do not implement provider resources yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Story PLATFORM-731\n\nCreate `platformctl snapshots prune`.\n\nRules:\n- retain the newest 14 daily, 8 weekly, and 12 monthly snapshots per database\n- snapshots under legal hold are never deleted\n- dry-run is default; `--execute` performs deletions\n- concurrent invocations must not delete the same snapshot twice\n- partial cloud failures should be resumable\n- JSON output includes kept/deleted/reason for every candidate\n- exit 2 when policy configuration is invalid, 1 for operational failure\n\nImplement the command and shared retention engine in Rust with golden tests and a fake object-store integration suite.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Dashboard request:\n\nOperators need a live view of namespace quota pressure. Each row shows requested, used, and limit for CPU, memory, GPU, and persistent storage. Values update every 15 seconds. Above 80% use warning colors; above 95% use critical colors plus text, never color alone. Rows can expand to list the five largest workloads. Filters cover cluster, owner, and environment. On mobile, metrics stack inside cards. Implement this in console/src/quotas using the existing metrics endpoint and design tokens.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Make the tiny UI adjustment","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} -{"prompt":"Fix the config bit","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"vague-eval","lang":"en"} -{"prompt":"Split the CLI argument parser from command execution while keeping flags, help output, and exit codes unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"The Rust formatter enters an infinite loop on nested comments followed by a raw string. Find the parser state that stops advancing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Review the bytecode verifier for paths that could read beyond a function body. No modifications.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Fix the config bit","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Split the CLI argument parser from command execution while keeping flags, help output, and exit codes unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"The Rust formatter enters an infinite loop on nested comments followed by a raw string. Find the parser state that stops advancing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Review the bytecode verifier for paths that could read beyond a function body. No modifications.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Write shell completion setup docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"Design a migration from the current AST interpreter to a register-based bytecode VM. Cover instruction format, source maps, exceptions, garbage collection boundaries, native extensions, debugging, compatibility tests, incremental adoption, performance gates, and rollback while the interpreter remains available.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} {"prompt":"Implement response-file expansion for the C++ compiler driver with cycle detection and platform-specific quoting.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Create a terminal dependency-tree viewer with folding, search, color themes, and screen-reader-friendly plain output.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Create a terminal dependency-tree viewer with folding, search, color themes, and screen-reader-friendly plain output.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} {"prompt":"Change the default output extension to .wasm","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Consolidate duplicate span-merging logic across lexer and macro expander without changing diagnostic locations.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Incremental builds sometimes reuse stale generated headers after a feature flag changes. Determine which dependency edge is missing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Explain how the linker chooses between weak symbols from two archives in the current implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Escreva a referência dos códigos de saída do comando `forge test`.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"pt"} -{"prompt":"Plan a plugin architecture for the static analyzer that allows third-party rules without exposing unstable compiler internals. Address process isolation, version negotiation, diagnostics, configuration, caching, security, distribution, failure handling, and milestones for migrating built-in rules before opening the interface externally.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Add a streaming parser for large SARIF reports with bounded memory and preserved result ordering.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Consolidate duplicate span-merging logic across lexer and macro expander without changing diagnostic locations.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Incremental builds sometimes reuse stale generated headers after a feature flag changes. Determine which dependency edge is missing.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Explain how the linker chooses between weak symbols from two archives in the current implementation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Escreva a referência dos códigos de saída do comando `forge test`.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"pt"} +{"prompt":"Plan a plugin architecture for the static analyzer that allows third-party rules without exposing unstable compiler internals. Address process isolation, version negotiation, diagnostics, configuration, caching, security, distribution, failure handling, and milestones for migrating built-in rules before opening the interface externally.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} +{"prompt":"Add a streaming parser for large SARIF reports with bounded memory and preserved result ordering.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} {"prompt":"Build the TUI test runner with live worker status, failure expansion, rerun shortcuts, and monochrome support.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Fix `--quite` to `--quiet` in one example","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Extract target-triple normalization into a shared crate while preserving all aliases and diagnostics.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"The compiler crashes only when an async closure captures a generic associated type. Reduce and locate the invalid lowering assumption.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Check whether the package resolver's tie-breaking is deterministic when two registries contain the same version.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Prepare a contributor guide for adding a lint rule","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Fix `--quite` to `--quiet` in one example","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Extract target-triple normalization into a shared crate while preserving all aliases and diagnostics.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"The compiler crashes only when an async closure captures a generic associated type. Reduce and locate the invalid lowering assumption.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Check whether the package resolver's tie-breaking is deterministic when two registries contain the same version.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Prepare a contributor guide for adding a lint rule","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Outline an architecture for reproducible remote builds across Linux, macOS, and Windows. Include toolchain identity, hermetic inputs, cache keys, sandboxing, secrets, network access, artifact provenance, platform-specific signing, failure fallback, rollout phases, and objective comparisons against current local builds.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} {"prompt":"Implement content-addressed artifact caching in the Go build daemon with concurrent upload deduplication.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Add a web-based flamegraph viewer with zoom, search, frame details, and shareable selections.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} -{"prompt":"Bump the language edition to 2024","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Move package lockfile encoding behind a versioned serializer without changing current bytes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add a web-based flamegraph viewer with zoom, search, frame details, and shareable selections.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Bump the language edition to 2024","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Move package lockfile encoding behind a versioned serializer without changing current bytes.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"A cancellation signal causes some test workers to hang while others exit. Find the descriptor or task preventing shutdown.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Walk through how macro hygiene identifiers are generated and compared in the current compiler.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Walk through how macro hygiene identifiers are generated and compared in the current compiler.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} {"prompt":"Draft release notes for forge 3.0","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Create a migration roadmap for replacing bespoke configuration parsing with a typed schema system. Address backward compatibility, unknown keys, environment interpolation, secret references, generated docs, editor support, plugin fields, automated conversion, warning phases, and rollback before legacy syntax is rejected.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Implement a daemon protocol for multiplexing compiler requests with cancellation and per-client resource quotas.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement a daemon protocol for multiplexing compiler requests with cancellation and per-client resource quotas.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Build the package graph screen with cycle highlighting, version badges, edge filtering, and SVG export.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Set the formatter line width to 100","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Rename BuildUnit to CompilationUnit across the codebase while preserving cache record fields and plugin APIs.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"The dependency solver picks an older incompatible package only when optional features form a cycle. Diagnose the search-state bug.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Review whether the existing response-file parser matches Windows CommandLineToArgvW semantics. Do not change it.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Document the current compiler JSON diagnostics format with examples, not a redesign.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Plan the migration to a new lockfile format, including staged compatibility; implementation comes later.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Implement the finalized module-resolution algorithm from specs/modules-v2.md.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"为命令行性能报告做一个网页界面，要有火焰图、筛选器、对比模式和可分享链接。","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"zh"} -{"prompt":"Replace `--colour` with `--color` in docs/quickstart.md","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Rearrange parser passes into explicit stages without changing accepted programs or diagnostics.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Why does `forge test` report success when a worker is killed by OOM? The result aggregation is broken and the cause is unknown.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Explain why the current linker keeps discarded section names in the string table; no output bug is reported.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Write an overview of the existing incremental compilation cache for plugin authors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Plan the bytecode verifier rollout and implement a warning-only verifier pass for unsupported instructions.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} -{"prompt":"Add a `forge explain` command and document its query syntax, output schema, and examples.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Review whether the existing response-file parser matches Windows CommandLineToArgvW semantics. Do not change it.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Document the current compiler JSON diagnostics format with examples, not a redesign.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Plan the migration to a new lockfile format, including staged compatibility; implementation comes later.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Implement the finalized module-resolution algorithm from specs/modules-v2.md.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"为命令行性能报告做一个网页界面，要有火焰图、筛选器、对比模式和可分享链接。","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"zh"} +{"prompt":"Replace `--colour` with `--color` in docs/quickstart.md","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Rearrange parser passes into explicit stages without changing accepted programs or diagnostics.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Why does `forge test` report success when a worker is killed by OOM? The result aggregation is broken and the cause is unknown.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Explain why the current linker keeps discarded section names in the string table; no output bug is reported.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Write an overview of the existing incremental compilation cache for plugin authors.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Plan the bytecode verifier rollout and implement a warning-only verifier pass for unsupported instructions.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Add a `forge explain` command and document its query syntax, output schema, and examples.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} {"prompt":"Create the browser-based diagnostic explorer and write a QA checklist for large files and keyboard navigation.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Correct the known default target triple and update the unit test asserting the old value.","purpose":"quickFix","secondary":"backendImpl","mixed":true,"difficulty":0.3,"slice":"mixed","lang":"en"} +{"prompt":"Correct the known default target triple and update the unit test asserting the old value.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"Consolidate package-name validation without behavior changes, then document the shared invariants.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"Code review excerpt:\n\nfn verify_jump(func: &Function, pc: usize, offset: i32) -> Result<()> {\n let target = pc.wrapping_add(offset as usize);\n if target > func.code.len() {\n return Err(Error::InvalidJump(target));\n }\n if func.code[target].is_operand_byte() {\n return Err(Error::JumpIntoOperand(target));\n }\n Ok(())\n}\n\nBytecode offsets are signed relative to the next instruction. Empty functions are allowed in malformed inputs and must be rejected safely. Review integer conversion, boundary checks, indexing, backward jumps, and the stated offset base. Do not patch it; provide exploitable and correctness findings.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Documentation issue CLI-441\n\nUsers confuse these commands:\n- `forge cache clean` removes local entries only\n- `forge cache purge --remote` requests remote deletion\n- `forge cache gc` removes unreachable local blobs after scanning lockfiles\n\nRemote purge is asynchronous and returns request ID. GC may retain blobs referenced by worktrees outside the current directory if they are registered. Clean never affects build outputs already copied into dist/.\n\nRewrite docs/cache.md with a comparison table, safety notes, examples, and a section explaining what each command does not delete. No behavior changes.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} -{"prompt":"VM architecture notes:\n\n- Interpreter executes roughly 65 million instructions/sec.\n- Startup must remain under 20 ms for CLI scripts.\n- Native extensions can hold opaque interpreter object pointers.\n- Debugger breakpoints refer to AST node IDs.\n- Existing snapshot tests cover 18,000 programs.\n- We need bytecode serialization eventually, but not in phase one.\n\nTurn this into a staged design for a register-based VM. Define instruction representation, lowering, exception semantics, GC interaction, native-extension compatibility, debugger mapping, performance gates, validation, and rollback to the interpreter.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"pasted-context","lang":"en"} -{"prompt":"Issue FORGE-1204\n\nSupport response files prefixed with `@`.\n\nRequirements:\n- UTF-8 with optional BOM on Unix\n- Windows decoding follows the active code page unless BOM is present\n- nested files resolve relative to the containing file\n- maximum nesting depth 16\n- report the full inclusion chain on cycles\n- quoting follows the platform command-line parser\n- `@@foo` escapes to literal `@foo`\n- expansion occurs before subcommand parsing\n\nImplement this in compiler-driver and add cross-platform golden tests. Existing direct argument parsing must remain unchanged.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Web tooling ticket:\n\nThe CI trace viewer currently renders 50,000 spans as DOM rows and freezes Chrome. Replace the main pane with a virtualized timeline. Users need zoom, pan, text search, critical-path highlighting, worker-lane collapse, duration tooltips, and a details drawer. Selection must survive live trace updates. Provide a plain table fallback when reduced motion or assistive technology mode is enabled. The API already returns normalized spans; don't change it.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Change the little option","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"vague-eval","lang":"en"} +{"prompt":"Code review excerpt:\n\nfn verify_jump(func: &Function, pc: usize, offset: i32) -> Result<()> {\n let target = pc.wrapping_add(offset as usize);\n if target > func.code.len() {\n return Err(Error::InvalidJump(target));\n }\n if func.code[target].is_operand_byte() {\n return Err(Error::JumpIntoOperand(target));\n }\n Ok(())\n}\n\nBytecode offsets are signed relative to the next instruction. Empty functions are allowed in malformed inputs and must be rejected safely. Review integer conversion, boundary checks, indexing, backward jumps, and the stated offset base. Do not patch it; provide exploitable and correctness findings.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Documentation issue CLI-441\n\nUsers confuse these commands:\n- `forge cache clean` removes local entries only\n- `forge cache purge --remote` requests remote deletion\n- `forge cache gc` removes unreachable local blobs after scanning lockfiles\n\nRemote purge is asynchronous and returns request ID. GC may retain blobs referenced by worktrees outside the current directory if they are registered. Clean never affects build outputs already copied into dist/.\n\nRewrite docs/cache.md with a comparison table, safety notes, examples, and a section explaining what each command does not delete. No behavior changes.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"VM architecture notes:\n\n- Interpreter executes roughly 65 million instructions/sec.\n- Startup must remain under 20 ms for CLI scripts.\n- Native extensions can hold opaque interpreter object pointers.\n- Debugger breakpoints refer to AST node IDs.\n- Existing snapshot tests cover 18,000 programs.\n- We need bytecode serialization eventually, but not in phase one.\n\nTurn this into a staged design for a register-based VM. Define instruction representation, lowering, exception semantics, GC interaction, native-extension compatibility, debugger mapping, performance gates, validation, and rollback to the interpreter.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Issue FORGE-1204\n\nSupport response files prefixed with `@`.\n\nRequirements:\n- UTF-8 with optional BOM on Unix\n- Windows decoding follows the active code page unless BOM is present\n- nested files resolve relative to the containing file\n- maximum nesting depth 16\n- report the full inclusion chain on cycles\n- quoting follows the platform command-line parser\n- `@@foo` escapes to literal `@foo`\n- expansion occurs before subcommand parsing\n\nImplement this in compiler-driver and add cross-platform golden tests. Existing direct argument parsing must remain unchanged.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Web tooling ticket:\n\nThe CI trace viewer currently renders 50,000 spans as DOM rows and freezes Chrome. Replace the main pane with a virtualized timeline. Users need zoom, pan, text search, critical-path highlighting, worker-lane collapse, duration tooltips, and a details drawer. Selection must survive live trace updates. Provide a plain table fallback when reduced motion or assistive technology mode is enabled. The API already returns normalized spans; don't change it.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Change the little option","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} {"prompt":"Clean up compiler stuff","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} -{"prompt":"Figure out why builds are weird","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Figure out why builds are weird","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} {"prompt":"Audit the payment webhook handler for replay, ordering, and signature-validation risks. Findings only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Write the PCI scope overview for engineers","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Write the PCI scope overview for engineers","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Design a migration from synchronous card authorization to an asynchronous payment-intent workflow. Cover state ownership, idempotency, webhook races, client compatibility, partial failures, ledger timing, fraud checks, observability, reconciliation, rollout milestones, and rollback without double-charging customers.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} -{"prompt":"Implement a Java service that reserves gift-card balances atomically across split-tender checkout.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Create the checkout payment-method picker with saved cards, wallets, gift cards, validation, and accessible errors.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement a Java service that reserves gift-card balances atomically across split-tender checkout.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Create the checkout payment-method picker with saved cards, wallets, gift cards, validation, and accessible errors.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Set the test currency to EUR","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Extract money rounding into a shared value type while preserving every historical invoice result.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Some refunds settle twice after a webhook retry, despite an idempotency key. Locate the transaction or key-scope defect.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Check whether the current payout scheduler can starve low-volume merchants. Do not change scheduling.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Some refunds settle twice after a webhook retry, despite an idempotency key. Locate the transaction or key-scope defect.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Check whether the current payout scheduler can starve low-volume merchants. Do not change scheduling.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} {"prompt":"Schreibe eine Integrationsanleitung für signierte Zahlungs-Webhooks mit Fehlerbeispielen.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"de"} {"prompt":"Map out an architecture for marketplace seller payouts across currencies and regions. Include ledger invariants, reserves, negative balances, FX timing, tax holds, banking cutoffs, retries, reconciliation, regulatory boundaries, operational overrides, and staged delivery starting with one country and one payout rail.","purpose":"planning","secondary":null,"mixed":false,"difficulty":1.0,"slice":"core","lang":"en"} {"prompt":"Add durable idempotency storage to the TypeScript payment-intent service with payload-conflict detection.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Build the merchant dispute dashboard with evidence status, deadlines, amount filters, and bulk document upload.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Correct the cents conversion constant","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Consolidate duplicated webhook event parsing across Stripe and Adyen adapters without changing normalized events.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"The reconciliation job shows balances off by one cent only for JPY refunds converted through USD. Find the rounding sequence error.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Explain how the current ledger represents authorization holds, captures, reversals, and expirations.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} -{"prompt":"Draft customer-facing release notes for bank-transfer payments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Consolidate duplicated webhook event parsing across Stripe and Adyen adapters without changing normalized events.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"The reconciliation job shows balances off by one cent only for JPY refunds converted through USD. Find the rounding sequence error.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Explain how the current ledger represents authorization holds, captures, reversals, and expirations.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Draft customer-facing release notes for bank-transfer payments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} {"prompt":"Plan the retirement of a legacy payment processor while preserving subscriptions, stored payment references, refunds, disputes, reporting, and historical reconciliation. Include processor coexistence, merchant cohorting, customer communication, data portability, shadow comparisons, rollback, and criteria for shutting down old webhooks.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Implement the ACH return-event consumer with deduplication and ledger compensation entries.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Add an invoice-payment timeline with state icons, expandable events, timezone display, and retry feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Bump the sandbox API version","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} -{"prompt":"Move processor-specific decline mapping behind an adapter while retaining all customer-visible messages.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Payment sessions occasionally remain pending after both capture and webhook success. Determine which state transition is lost.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Review whether the current card-fingerprint handling can link customers across tenants unintentionally.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Move processor-specific decline mapping behind an adapter while retaining all customer-visible messages.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Payment sessions occasionally remain pending after both capture and webhook success. Determine which state transition is lost.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Review whether the current card-fingerprint handling can link customers across tenants unintentionally.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} {"prompt":"Write a support runbook for delayed payouts","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Propose a design for real-time transaction risk scoring that remains available when the ML service is degraded. Cover latency budgets, feature freshness, deterministic fallbacks, manual rules, explainability, audit retention, shadow evaluation, regional routing, rollout, and rollback without changing approval rates abruptly.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} -{"prompt":"Build a reconciliation command that compares processor settlements to ledger entries and emits resumable discrepancy files.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Build a reconciliation command that compares processor settlements to ledger entries and emits resumable discrepancy files.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Implement the mobile refund flow with amount selection, reason entry, confirmation, progress, and partial-refund history.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Change PAYMENT_TIMEOUT_MS to 45000","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Rename SettlementBatch to PayoutBatch across services while preserving database tables and event names.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Card verification fails only when customers return from a specific bank's 3DS page. Diagnose the malformed or lost redirect state.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} -{"prompt":"Read the chargeback evidence builder and tell me which fields are omitted for digital goods.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Card verification fails only when customers return from a specific bank's 3DS page. Diagnose the malformed or lost redirect state.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Read the chargeback evidence builder and tell me which fields are omitted for digital goods.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} {"prompt":"Prepare an API reference for payout status events","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Create a migration plan for adopting ISO 20022 bank messages, covering schema mapping, coexistence, reconciliation, validation, partner certification, observability, archival requirements, phased corridor rollout, and rollback to legacy formats.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} {"prompt":"Add a fraud-rule evaluator with versioned rulesets and deterministic decision traces.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Build the payment-link editor with live preview, expiration controls, branding, and localization-safe layout.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Build the payment-link editor with live preview, expiration controls, branding, and localization-safe layout.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} {"prompt":"Replace the outdated support email","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} {"prompt":"Separate invoice rendering from tax calculation while preserving PDFs, totals, and event timing.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Payout reports intermittently omit the final transaction of each page. Find whether cursor construction or ordering is wrong.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} -{"prompt":"Assess whether the existing retry policy can duplicate non-idempotent processor calls. Analysis only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Document the current refund API behavior, including partial refunds and idempotent retries.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} -{"prompt":"Plan the migration from floating-point tax calculations to decimal arithmetic; do not implement it yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Implement the approved payout state machine from docs/payout-states.md.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Criar a tela de confirmação de pagamento com resumo, taxas, cupom, erros e suporte a leitor de tela.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"pt"} -{"prompt":"Change 'succesful' to 'successful' in Receipt.tsx","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} -{"prompt":"Restructure the ledger posting code into validation, entry construction, and persistence with identical results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} -{"prompt":"Why do some expired authorization holds remain in available-balance calculations? The balance is wrong and the source is unknown.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} -{"prompt":"Explain why the current webhook verifier accepts two active signing secrets during rotation. Nothing is failing.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} -{"prompt":"Write an operational overview of existing settlement reconciliation, not a proposal.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Payout reports intermittently omit the final transaction of each page. Find whether cursor construction or ordering is wrong.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Assess whether the existing retry policy can duplicate non-idempotent processor calls. Analysis only.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Document the current refund API behavior, including partial refunds and idempotent retries.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Plan the migration from floating-point tax calculations to decimal arithmetic; do not implement it yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Implement the approved payout state machine from docs/payout-states.md.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Criar a tela de confirmação de pagamento com resumo, taxas, cupom, erros e suporte a leitor de tela.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"pt"} +{"prompt":"Change 'succesful' to 'successful' in Receipt.tsx","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Restructure the ledger posting code into validation, entry construction, and persistence with identical results.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Why do some expired authorization holds remain in available-balance calculations? The balance is wrong and the source is unknown.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Explain why the current webhook verifier accepts two active signing secrets during rotation. Nothing is failing.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Write an operational overview of existing settlement reconciliation, not a proposal.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} {"prompt":"Plan the ledger partitioning migration and implement a read-only analyzer that estimates tenant movement cost.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} {"prompt":"Implement the dispute-evidence endpoint and document its file limits, states, and error responses.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} {"prompt":"Build the subscription pause UI and add a product QA note covering dates, proration copy, and accessibility.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} -{"prompt":"Fix the known tax-region code and update the backend fixture that contains the old code.","purpose":"quickFix","secondary":"backendImpl","mixed":true,"difficulty":0.3,"slice":"mixed","lang":"en"} -{"prompt":"Consolidate processor error translation without behavior changes, then document the mapping contract.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} -{"prompt":"Payment implementation ticket:\n\nPOST /v2/payment-intents/{id}/capture\nBody: { amount?, idempotency_key }\n\nRules:\n- omitted amount captures the remaining authorized balance\n- partial capture is allowed up to three times\n- total captured cannot exceed authorization\n- declined captures do not consume the idempotency key\n- successful responses replay exactly for 48 hours\n- processor call and ledger posting cannot share a transaction\n- publish CaptureCompleted only after ledger durability\n- concurrent captures must serialize per intent\n\nImplement the command handler, locking, processor adapter call, recovery state, outbox event, and integration tests for concurrency and retries.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Checkout design ticket:\n\nAt review step, users need to see subtotal, discounts, tax, shipping, gift-card credit, and final amount. If the total changes after address validation, highlight changed rows and require acknowledgment before Pay becomes enabled. On phones the summary is collapsible but the final amount stays visible. Errors from wallets should appear beside the selected method, not as a global toast. Support 200% zoom, screen readers, and right-to-left currencies. Implement in CheckoutReview.tsx with existing pricing data; no backend changes.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} -{"prompt":"CI snapshot failure:\n\n- Expected\n+ Received\n\n- \"support@example.com\"\n+ \"payments-help@example.com\"\n\nProduct copy file:\nconfig/contact.json currently contains `support@example.com`.\nApproved ticket value: `payments-help@example.com`.\nThe snapshot was already updated in the branch, but the source value was missed. Change only config/contact.json to the approved address. Do not modify the snapshot or tests.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"pasted-context","lang":"en"} -{"prompt":"Refactoring request from ledger team:\n\nposting/service.ts validates commands, converts currencies, builds entries, opens transactions, persists entries, updates cached balances, and publishes events. The reconciliation worker duplicates entry construction for imported settlements. Tests rely on exact entry order and error types.\n\nCreate explicit validation, entry-builder, and persistence boundaries; share the builder with reconciliation. Preserve transaction scope, journal ordering, rounding, public service methods, event payloads, balance timing, and every existing error code. This is structural work only—no new ledger states or processor behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} -{"prompt":"Incident log:\n\n09:18:41 refund request id=r88 amount=4000 idempotency=abc\n09:18:41 processor accepted external=rf_991\n09:18:42 db commit timeout connection reset\n09:18:44 retry id=r88 idempotency=abc lookup miss\n09:18:44 processor accepted external=rf_992\n09:18:45 ledger posted refund=rf_992\n09:19:02 webhook received external=rf_991\n\nTwo processor refunds occurred, but our idempotency table contains only rf_992. Determine the failure window and why retry lookup missed the first attempt. Reproduce it and identify the correct recovery invariant before changing code.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} -{"prompt":"Tell me if payments look okay","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Fix the known tax-region code and update the backend fixture that contains the old code.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Consolidate processor error translation without behavior changes, then document the mapping contract.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Payment implementation ticket:\n\nPOST /v2/payment-intents/{id}/capture\nBody: { amount?, idempotency_key }\n\nRules:\n- omitted amount captures the remaining authorized balance\n- partial capture is allowed up to three times\n- total captured cannot exceed authorization\n- declined captures do not consume the idempotency key\n- successful responses replay exactly for 48 hours\n- processor call and ledger posting cannot share a transaction\n- publish CaptureCompleted only after ledger durability\n- concurrent captures must serialize per intent\n\nImplement the command handler, locking, processor adapter call, recovery state, outbox event, and integration tests for concurrency and retries.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Checkout design ticket:\n\nAt review step, users need to see subtotal, discounts, tax, shipping, gift-card credit, and final amount. If the total changes after address validation, highlight changed rows and require acknowledgment before Pay becomes enabled. On phones the summary is collapsible but the final amount stays visible. Errors from wallets should appear beside the selected method, not as a global toast. Support 200% zoom, screen readers, and right-to-left currencies. Implement in CheckoutReview.tsx with existing pricing data; no backend changes.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"CI snapshot failure:\n\n- Expected\n+ Received\n\n- \"support@example.com\"\n+ \"payments-help@example.com\"\n\nProduct copy file:\nconfig/contact.json currently contains `support@example.com`.\nApproved ticket value: `payments-help@example.com`.\nThe snapshot was already updated in the branch, but the source value was missed. Change only config/contact.json to the approved address. Do not modify the snapshot or tests.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"Refactoring request from ledger team:\n\nposting/service.ts validates commands, converts currencies, builds entries, opens transactions, persists entries, updates cached balances, and publishes events. The reconciliation worker duplicates entry construction for imported settlements. Tests rely on exact entry order and error types.\n\nCreate explicit validation, entry-builder, and persistence boundaries; share the builder with reconciliation. Preserve transaction scope, journal ordering, rounding, public service methods, event payloads, balance timing, and every existing error code. This is structural work only—no new ledger states or processor behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Incident log:\n\n09:18:41 refund request id=r88 amount=4000 idempotency=abc\n09:18:41 processor accepted external=rf_991\n09:18:42 db commit timeout connection reset\n09:18:44 retry id=r88 idempotency=abc lookup miss\n09:18:44 processor accepted external=rf_992\n09:18:45 ledger posted refund=rf_992\n09:19:02 webhook received external=rf_991\n\nTwo processor refunds occurred, but our idempotency table contains only rf_992. Determine the failure window and why retry lookup missed the first attempt. Reproduce it and identify the correct recovery invariant before changing code.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Tell me if payments look okay","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} {"prompt":"Write the usual blurb","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} diff --git a/data/round2-01.jsonl b/data/round2-01.jsonl index 087997d..7aa906b 100644 --- a/data/round2-01.jsonl +++ b/data/round2-01.jsonl @@ -1,200 +1,200 @@ -{"prompt": "our on-call runbook for the settlement job is four years stale. rewrite it against how the job actually behaves today — retry semantics, the manual replay command, who to page", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "a partner integration is coming that needs us to expose per-line-item tax breakdown, which we don't currently persist — we compute it at invoice time and throw it away. before we start storing it i want to think through retention, whether we backfill, and what it means for the invoice PDFs that were already generated with the old rounding", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "en"} -{"prompt": "our device provisioning flow is undocumented and also slightly wrong — the cert rotation step happens after first telemetry, which nobody intended. i need the sequence written up for the field team, and the ordering bug sorted out in the firmware handshake", "purpose": "writing", "secondary": "debugging", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "a contractor delivered the disputes module last month and it works, but i haven't read a line of it and we're about to depend on it heavily. go through `services/disputes/` and tell me what you'd flag: correctness, error handling, anything that will hurt at volume, and anything that reads like it was written against an older version of our gateway SDK", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "we're about to move order history off postgres onto a partitioned setup and i genuinely don't know the sequencing. constraints: no downtime, 400M rows, reporting queries hit the same tables, and the mobile team ships a release every tuesday so any API change has to be additive for at least two months. want a migration strategy with rollback points before anyone writes code", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "three helpers in utils/money.ts do rounding: `roundMoney`, `toCents`, `safeRound`. two of them disagree on negatives. collapse them into one and update the ~60 call sites", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "webhook delivery worker needs exponential backoff with jitter, capped at 6 hours, max 12 attempts, then dead-letter", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "payout table needs zebra striping", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "drop the currency symbol from the cart subtotal, product asked", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "boundary", "lang": "en"} -{"prompt": "src/pipeline/transform_orders.py is 1100 lines and every dbt model imports from it. i want it broken into something sane — but first tell me how you'd carve it up and in what order, then do the first slice", "purpose": "planning", "secondary": "refactor", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "same three lines of duplicated setup at the top of every one of these tests. worth extracting a fixture?\n\ndef test_charge_declined(db, monkeypatch):\n gw = FakeGateway()\n monkeypatch.setattr(charges, \"gateway\", gw)\n order = make_order(db, total=Decimal(\"25.00\"), currency=\"usd\")\n gw.next_response = DECLINE\n with pytest.raises(ChargeDeclined):\n charges.capture(order)\n\ndef test_charge_partial(db, monkeypatch):\n gw = FakeGateway()\n monkeypatch.setattr(charges, \"gateway\", gw)\n order = make_order(db, total=Decimal(\"25.00\"), currency=\"usd\")\n gw.next_response = PARTIAL\n result = charges.capture(order)\n assert result.captured == Decimal(\"10.00\")\n\ndef test_charge_retries_on_timeout(db, monkeypatch):\n gw = FakeGateway()\n monkeypatch.setattr(charges, \"gateway\", gw)\n order = make_order(db, total=Decimal(\"25.00\"), currency=\"usd\")\n gw.responses = [TIMEOUT, OK]\n assert charges.capture(order).attempts == 2", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "design ticket from figma handoff — build the empty state for the payouts screen:\n\nPayouts • Empty state\nIllustration: 160x160, centered, 32px above the heading. Use the existing `illustration/wallet` asset.\nHeading: \"No payouts yet\" — text-lg, semibold, foreground.\nBody: \"Payouts appear here once your first order settles. This usually takes 2 business days.\" — text-sm, muted-foreground, max-width 420px, centered.\nPrimary button: \"View settlement schedule\" — secondary variant, opens the schedule sheet.\nSpacing: 96px top padding on desktop, 48px on mobile.\nDark mode: illustration swaps to the `-dark` variant; nothing else changes.\nMotion: fade + 8px rise on mount, 180ms ease-out, respects reduced-motion.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "paste of the dedup helper in the ingestion job. two of these live in the repo (one in `ingest/`, one in `backfill/`) and they've drifted. unify them:\n\ndef dedupe(rows, key=lambda r: r[\"id\"]):\n seen = set()\n out = []\n for r in rows:\n k = key(r)\n if k in seen:\n continue\n seen.add(k)\n out.append(r)\n return out\n\n# backfill/util.py version\ndef dedupe_rows(rows, key_field=\"id\", keep=\"last\"):\n index = {}\n for r in rows:\n k = r.get(key_field)\n if keep == \"last\" or k not in index:\n index[k] = r\n return list(index.values())\n\ncallers: ingest/orders.py:88, ingest/refunds.py:41, backfill/orders.py:210, backfill/merchants.py:77, tools/reconcile.py:19", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "can you look over the new webhook signature verification and also write up how partners should implement it on their end", "purpose": "review", "secondary": "writing", "mixed": true, "difficulty": 0.55, "slice": "mixed", "lang": "en"} -{"prompt": "o job de conciliação está a demorar 3h e ninguém sabe porquê. antes de mexer, explica-me o que ele faz passo a passo", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "pt"} -{"prompt": "invoice numbering has to be gapless per legal entity, and right now it's a `MAX(id)+1` in the app. i need both the approach and the actual implementation — sequence table vs advisory lock vs something else, then build it", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "before we ship split-tender i want a written threat model of the auth-then-void window, and then the guard rails implemented in the charge service", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "settlement docs and the settlement code disagree about when a batch closes. figure out which one is lying, then fix whichever is wrong", "purpose": "review", "secondary": "writing", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "the k6 run against staging ingest, before and after we turned on batching. is this actually better or am i reading noise?\n\n scenarios: (100.00%) 1 scenario, 400 max VUs, 5m30s max duration\n\n checks.........................: 99.81% ✓ 238914 ✗ 452\n data_received..................: 1.4 GB 4.6 MB/s\n http_req_blocked...............: avg=1.21ms min=1µs med=4µs max=1.02s\n http_req_duration..............: avg=411.02ms min=18.11ms med=298ms max=9.81s\n { expected_response:true }...: avg=402.55ms min=18.11ms med=291ms max=9.81s\n http_req_failed................: 0.18% ✓ 452 ✗ 238914\n http_reqs......................: 239366 798.55/s\n iteration_duration.............: avg=1.24s min=201ms med=1.11s max=11.2s\n vus............................: 400 min=40 max=400\n\n ✗ p(95) < 500ms\n ↳ p(95)=1.42s", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "support keeps forwarding this and i want one canonical doc instead of ten slack answers:\n\n> Hi — we're integrating your payouts API and the docs don't say what happens when a payout fails. Do you retry automatically? Is there a webhook? We saw a payout go from `pending` to `failed` and then back to `pending` two hours later which we did not expect. Also: are `failure_code` values stable enough to switch on, or should we treat them as display-only? Our finance team needs to know whether a `failed` payout can still settle later, because we've already reversed the ledger entry on our side by then.\n\nwrite the page that answers all of that", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "two of these do the same job with different names and one of them silently swallows the error. collapse them:\n\n// packages/gateway/src/http.ts\nexport async function postJSON(url: string, body: unknown, timeoutMs = 30_000) {\n const ctrl = new AbortController()\n const t = setTimeout(() => ctrl.abort(), timeoutMs)\n try {\n const res = await fetch(url, { method: 'POST', body: JSON.stringify(body), signal: ctrl.signal })\n if (!res.ok) throw new GatewayError(res.status, await res.text())\n return await res.json()\n } finally {\n clearTimeout(t)\n }\n}\n\n// packages/gateway/src/legacy/request.ts\nexport async function sendJson(url, payload, opts = {}) {\n try {\n const res = await fetch(url, { method: 'POST', body: JSON.stringify(payload) })\n return await res.json()\n } catch (e) {\n return null\n }\n}", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "someone drafted this migration for the split-tender work. would this lock the table in prod?\n\nBEGIN;\n\nALTER TABLE orders ADD COLUMN tender_count smallint NOT NULL DEFAULT 1;\n\nALTER TABLE payments\n ADD COLUMN instrument_kind text NOT NULL DEFAULT 'card',\n ADD CONSTRAINT payments_instrument_kind_chk\n CHECK (instrument_kind IN ('card','gift_card','store_credit'));\n\nCREATE INDEX idx_payments_order_instrument\n ON payments (order_id, instrument_kind);\n\nUPDATE payments SET instrument_kind = 'gift_card'\n WHERE gateway = 'internal_gc';\n\nALTER TABLE payments ALTER COLUMN instrument_kind DROP DEFAULT;\n\nCOMMIT;\n\npayments is 190M rows, postgres 15, no downtime window", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "there's a `docs/adr/` folder with eleven ADRs and four of them describe systems we deleted. clear out the dead ones, and write a new ADR covering the ledger v2 decision we actually made in march but never recorded", "purpose": "writing", "secondary": "refactor", "mixed": true, "difficulty": 0.5, "slice": "mixed", "lang": "en"} -{"prompt": "firmware devices on the 4.1 build sometimes report telemetry timestamps a year in the future and our ingest happily accepts them, poisoning the warehouse. find out where the clock goes wrong on the device side, and add the ingest-side guard so bad timestamps never land again", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "merchant dashboard imports the design system in three different ways depending on when the file was written: barrel imports, deep paths, and a couple of copy-pasted components that were never migrated. normalise all of it, delete the copies, same pixels on screen afterwards", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "dedupe the two CSV writers", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "we inherited a rust firmware crate from an acquisition and the interrupt handling in `src/rt/isr.rs` looks unusual to me — there's a static mut ring buffer touched from both the ISR and the main loop with a bare `unsafe` and no critical section. is that actually sound on a single-core cortex-m, or are we one compiler upgrade away from disaster", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "three of us reviewed the ledger PR and disagreed about whether the compensating-entry approach is sound. settle it — read `internal/ledger/` and tell me who's right", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "webhook signing helper is duplicated between the node SDK and the python SDK and they've drifted on how they canonicalise the payload. get them back in sync, then add the note to both SDK readmes so integrators know which versions changed", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "we're a four-person team and every deploy needs someone to babysit the settlement job afterwards. that's not sustainable for the next quarter when we double order volume. what would you sequence — better alerting first, or making the job idempotent so a bad deploy doesn't need a human? give me the reasoning and a rough order of work, not code", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "payout amount doc, for support", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "checkout blows up for about 1 in 40 carts and this is all sentry gives me:\n\nTypeError: Cannot read properties of undefined (reading 'currency')\n at normalizeLineItem (/srv/checkout/dist/cart/normalize.js:88:31)\n at Array.map ()\n at buildOrderDraft (/srv/checkout/dist/cart/draft.js:42:38)\n at async createOrder (/srv/checkout/dist/orders/create.js:117:20)\n at async /srv/checkout/dist/http/routes/orders.js:29:24\n at async Object.handler (/srv/checkout/node_modules/fastify/lib/handleRequest.js:129:9)\n {\n requestId: 'req_9f2b1c',\n cartId: 'cart_01HQ8V',\n lineItems: 4,\n promoApplied: true,\n userAgent: 'Shopify-Mobile/9.4.1 (iOS 18.2)'\n }\n\nit only ever fires when a promo is on the cart, never on a plain cart. no idea what makes those items different", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "why does the ESP32 reboot roughly 40s after it associates to wifi? nothing in my firmware touches the watchdog", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "toolbar icons are 1px off center in dark mode only", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "npm audit tail from the payments package, tell me which of these actually matter for us and just do the safe upgrades:\n\n# npm audit report\n\naxios 1.6.0 - 1.7.3\nSevere: Server-Side Request Forgery in axios\nfix available via `npm audit fix --force`\nWill install axios@1.11.2, which is a breaking change\nnode_modules/axios\n @acme/gateway-sdk 0.4.0 - 0.9.2\n Depends on vulnerable versions of axios\n node_modules/@acme/gateway-sdk\n\ntar-fs 2.0.0 - 2.1.1\nModerate: Link Following in tar-fs\nfix available via `npm audit fix`\nnode_modules/tar-fs\n\n7 vulnerabilities (4 moderate, 3 high)", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "continue from where the sync work stopped", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "here's the hunk that landed friday. does it hold up?\n\n@@ -41,17 +41,24 @@ func (s *Settler) Settle(ctx context.Context, batchID string) error {\n-\ttx, err := s.db.BeginTx(ctx, nil)\n+\ttx, err := s.db.BeginTx(ctx, &sql.TxOptions{Isolation: sql.LevelReadCommitted})\n \tif err != nil {\n \t\treturn err\n \t}\n-\tdefer tx.Rollback()\n+\tdefer func() { _ = tx.Rollback() }()\n \n \trows, err := tx.QueryContext(ctx, selectPendingSQL, batchID)\n \tif err != nil {\n \t\treturn err\n \t}\n+\tdefer rows.Close()\n \n \tfor rows.Next() {\n \t\tvar p payout\n \t\tif err := rows.Scan(&p.ID, &p.AmountCents, &p.Currency); err != nil {\n \t\t\treturn err\n \t\t}\n-\t\tif err := s.send(ctx, p); err != nil {\n+\t\tgo func(p payout) {\n+\t\t\t_ = s.send(ctx, p)\n+\t\t}(p)\n-\t\t\treturn err\n-\t\t}\n \t}\n \treturn tx.Commit()\n }", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "ticket copy below, turn it into customer-facing release notes for the 4.2 firmware drop. keep it short, they are field techs not engineers:\n\nFW-2201 — Modbus RTU timing\nDevices on long RS-485 runs (>300m) intermittently dropped frames when polled faster than 20Hz. Root cause was the inter-frame delay being computed from the nominal baud rate rather than the measured one. Fixed by sampling the actual bit time at link-up.\n\nFW-2214 — Battery gauge drift\nThe SoC estimate drifted up to 12% after ~40 charge cycles because the coulomb counter was never re-zeroed at full charge. Now re-zeroes when terminal voltage holds above 4.15V for 90 seconds.\n\nFW-2230 — OTA rollback\nA failed OTA could leave slot B marked valid. Bootloader now requires a heartbeat from the new image within 60s before confirming.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "pasted-context", "lang": "en"} -{"prompt": "rename `TxnCtx` to `PaymentContext` everywhere, it's in about 30 files", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "pytest output, no clue why this only fails on CI:\n\n=================================== FAILURES ===================================\n_______________ test_settlement_rounds_half_even[eur-2.005] ____________________\n\namounts = ['2.005', '10.115', '0.005']\n\n @pytest.mark.parametrize(\"currency,amount\", CASES)\n def test_settlement_rounds_half_even(currency, amount):\n got = settle(Decimal(amount), currency)\n> assert got == Decimal(\"2.00\")\nE assert Decimal('2.01') == Decimal('2.00')\nE + where Decimal('2.01') = settle(Decimal('2.005'), 'eur')\n\ntests/test_settlement.py:64: AssertionError\n=========================== short test summary info ============================\nFAILED tests/test_settlement.py::test_settlement_rounds_half_even[eur-2.005]\nFAILED tests/test_settlement.py::test_settlement_rounds_half_even[eur-0.005]\n2 failed, 318 passed in 41.22s\n\nlocally all 320 pass. same python version per the container image", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "give the dashboard some love", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "vague-eval", "lang": "en"} -{"prompt": "quiero un README para el paquete `acme-payments-sdk`, con ejemplos de uso y la tabla de errores", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "es"} -{"prompt": "epic dropped in my lap this morning, need a shape for it before standup:\n\nPAY-880: Split-tender checkout\nCustomers should be able to pay with up to three instruments on one order (gift card + card + store credit). Partial authorization must be supported; if the second instrument declines we must void the first within 30s or the customer sees a phantom hold. Refunds must unwind in reverse order of capture. Accounting needs one journal entry per instrument, not per order. Mobile and web both in scope; POS is explicitly out of scope for this quarter. Legal wants a written record of authorization order for disputes.\n\nno estimates yet, just want the milestones and where the risk is", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "skeleton loader for the orders table please, matching the card one we already have", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "git log since v3.8 is below, produce the changelog entry. group by user-visible vs internal, drop the noise:\n\n8f21c0a fix(cart): guard against null promo on line items\n1b93de2 chore: bump esbuild 0.21.5 -> 0.23.0\nc0aa774 feat(checkout): remember last used shipping method\n77de110 refactor(orders): extract draft builder\n2e91b45 fix(orders): don't double-count tax on split shipments\naa30f19 test: flaky settlement rounding case\n9c1d004 feat(admin): bulk refund from the order list\n4410bb7 chore(deps): dependabot bump tar-fs\nb77e910 fix(webhooks): retry paypal IPN on 5xx instead of dropping\n30cc219 docs: correct the payout schedule table\ne1f0a52 perf(cart): memoize currency formatter", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "walk me through what `reconcileLedger` actually does before i touch it", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "serial console from the gateway board, it wedges after a few hours in the field but never on my desk:\n\n[00:04:12.331] mqtt: connected broker=ssl://ingest.acme.io:8883\n[01:58:03.117] mqtt: publish qos=1 topic=v1/telemetry len=284\n[01:58:03.402] mqtt: puback id=41221\n[02:11:44.980] wifi: rssi=-81 (weak)\n[02:11:47.002] mqtt: keepalive timeout, reconnecting\n[02:11:47.004] net: dhcp renew\n[02:11:52.118] mqtt: connect failed rc=-2\n[02:12:02.118] mqtt: connect failed rc=-2\n[02:12:12.119] mqtt: connect failed rc=-2\n[02:12:12.120] heap: free=3128 largest=1024 min_ever=3128\n[02:12:22.121] mqtt: connect failed rc=-2\n[02:12:22.122] heap: free=2104 largest=768 min_ever=2104\n[02:12:32.123] mqtt: connect failed rc=-2\n[02:12:32.124] heap: free=1080 largest=512 min_ever=1080\n", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "nochmal die Frage: warum ruft der Checkout `getShippingRates` zweimal auf, wenn man die Adresse ändert?", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "de"} -{"prompt": "do the thing with the invoices", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "ruff is unhappy on the pipeline package, clear these out:\n\npipelines/orders/load.py:12:1: F401 [*] `datetime.timezone` imported but unused\npipelines/orders/load.py:88:5: E722 Do not use bare `except`\npipelines/orders/load.py:141:9: F841 Local variable `rowcount` is assigned to but never used\npipelines/orders/transform.py:23:1: E402 Module level import not at top of file\npipelines/orders/transform.py:210:80: E501 Line too long (118 > 100)\npipelines/orders/transform.py:377:15: B008 Do not perform function call `dict()` in argument defaults\npipelines/common/io.py:5:1: F401 [*] `typing.Optional` imported but unused\npipelines/common/io.py:66:12: SIM108 Use ternary operator instead of `if`-`else`-block\nFound 8 errors (3 fixable with the `--fix` option).", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "pasted-context", "lang": "en"} -{"prompt": "our staging environment shares a gateway sandbox account with two other teams, which is why our e2e tests are flaky, and i'm tired of it. options as i see them: our own sandbox account, a recorded-fixtures approach, or a fake gateway we maintain. weigh those up for a team our size and tell me what you'd do", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "a merchant reported that their payout for tuesday arrived split into two payments with different reference numbers, which shouldn't be possible. i've been staring at the batching code for an hour. the batch closes on a size trigger and a time trigger and i think both can fire, but i can't prove it from reading. take a look and explain what's happening", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "our checkout conversion dropped 4% on android chrome last week and nothing in the payments code changed. the only thing i can find is that the card element sometimes doesn't get focus on first tap. i don't know whether that's the cause or a red herring, and i don't know how to tell", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "a `/v1/instruments` endpoint is needed: list saved payment instruments for the authenticated merchant's customer, with the default one first, expired cards excluded unless `include_expired=true`, and last-four plus brand only — never the token. keep it consistent with how `/v1/orders` handles auth and pagination", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "finish it", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "POST /v1/refunds handler is pasted below — i need the public API reference page for it. request/response schema, every error code, and an idempotency note:\n\n@router.post(\"/v1/refunds\", status_code=201)\nasync def create_refund(body: RefundIn, idem: str = Header(alias=\"Idempotency-Key\")):\n order = await orders.get(body.order_id)\n if order is None:\n raise HTTPException(404, \"order_not_found\")\n if order.state not in (\"captured\", \"partially_refunded\"):\n raise HTTPException(409, \"order_not_refundable\")\n if body.amount_cents > order.refundable_cents:\n raise HTTPException(422, \"amount_exceeds_refundable\")\n existing = await idem_store.get(idem)\n if existing:\n return existing\n refund = await gateway.refund(order.charge_id, body.amount_cents, reason=body.reason)\n await idem_store.put(idem, refund, ttl=86400)\n return refund", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "airflow scheduler log tail — the daily orders DAG has been marked success while producing nothing for three days:\n\n[2026-07-27, 02:00:04 UTC] {scheduler_job.py:412} INFO - DAG orders_daily scheduled run 2026-07-26\n[2026-07-27, 02:00:09 UTC] {taskinstance.py:1157} INFO - Executing extract_orders on 2026-07-26T00:00:00+00:00\n[2026-07-27, 02:00:11 UTC] {sql.py:88} INFO - Running: SELECT * FROM orders WHERE updated_at >= '2026-07-26' AND updated_at < '2026-07-27'\n[2026-07-27, 02:00:12 UTC] {sql.py:96} INFO - Fetched 0 rows\n[2026-07-27, 02:00:12 UTC] {taskinstance.py:1372} INFO - Marking task as SUCCESS\n[2026-07-27, 02:00:13 UTC] {taskinstance.py:1157} INFO - Executing load_warehouse on 2026-07-26T00:00:00+00:00\n[2026-07-27, 02:00:14 UTC] {load.py:52} INFO - upserting 0 rows into warehouse.fct_orders\n[2026-07-27, 02:00:14 UTC] {taskinstance.py:1372} INFO - Marking task as SUCCESS\n[2026-07-27, 02:00:15 UTC] {dagrun.py:604} INFO - Marking run successful\n\nthe source table definitely has rows for those days", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "explain plan for our slowest reporting query, is the sort the real problem or is it the nested loop:\n\nGroupAggregate (cost=2841002.31..2912441.09 rows=1428215 width=48) (actual time=18422.113..21033.885 rows=1201 loops=1)\n Group Key: m.merchant_id, date_trunc('day', o.captured_at)\n -> Sort (cost=2841002.31..2844572.85 rows=1428215 width=32) (actual time=18421.980..19884.210 rows=4118222 loops=1)\n Sort Key: m.merchant_id, (date_trunc('day', o.captured_at))\n Sort Method: external merge Disk: 214880kB\n -> Nested Loop (cost=0.43..2610411.02 rows=1428215 width=32) (actual time=0.061..14022.771 rows=4118222 loops=1)\n -> Seq Scan on merchants m (cost=0.00..812.44 rows=3244 width=16) (actual time=0.008..1.902 rows=3244 loops=1)\n -> Index Scan using orders_merchant_captured_idx on orders o (cost=0.43..798.11 rows=440 width=24) (actual time=0.004..3.902 rows=1269 loops=3244)\n Index Cond: (merchant_id = m.merchant_id)\nPlanning Time: 0.641 ms\nExecution Time: 21041.223 ms", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "gift card balance shows stale after a partial redemption — i think it's just the cache key missing the version, one-line change if so", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "dependabot opened this and i can't tell if it's safe to merge blind:\n\nBumps `pyarrow` from 14.0.2 to 17.0.0.\n\nRelease notes (17.0.0):\n- ARROW-41567: [Python] Deprecate `pyarrow.parquet.ParquetDataset` legacy behaviour; `use_legacy_dataset` removed\n- ARROW-42011: [C++] Default compression for `write_table` changed from `snappy` to `zstd`\n- ARROW-40199: [Python] `Table.to_pandas` now returns nullable dtypes by default when `types_mapper` is unset\n- ARROW-43121: [C++] Minimum supported glibc raised to 2.28\n\nCommits\n- 9a1b2c3 MINOR: bump version\n- 77aa019 ARROW-43121: raise glibc floor\n- 2b91d40 ARROW-40199: nullable dtypes by default\n\nCompatibility score: 61%", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "browser console on the checkout page, customers report the pay button doing nothing:\n\nrefused to execute inline script because it violates the following Content Security Policy directive: \"script-src 'self' https://js.stripe.com\"\n (index):1\nUncaught (in promise) IntegrationError: We could not retrieve data from the specified Element. Please make sure the Element you are attempting to use is still mounted.\n at Bn (v3:1:19233)\n at e._handleMessage (v3:1:41102)\n at e._handleMessage (v3:1:40011)\npayment-form.tsx:212 Uncaught TypeError: Cannot read properties of null (reading 'confirmPayment')\n at handleSubmit (payment-form.tsx:212:28)\n at HTMLFormElement.callCallback (react-dom.development.js:4164:14)\nGET https://api.acme.io/v1/payment_intents/pi_3Qb 401 (Unauthorized)\n\nhappens on safari only as far as we can tell", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "comparto el hilo de slack de anoche, resúmelo en un post-mortem para el canal #incidents:\n\nmarta: el settlement job lleva 40 min parado\nmarta: los locks en payouts están al rojo\ndani: yo veo la conexión del pooler saturada, 200/200\ndani: creo que alguien lanzó el replay manual sin el flag de batch\nmarta: confirmado, jorge lo lanzó a las 21:14 para el merchant 8812\njorge: perdón, pensaba que el replay ya iba en lotes\ndani: he matado el proceso, los locks se liberaron a las 21:52\nmarta: cola drenada a las 22:06, sin pagos perdidos\ndani: mañana metemos un guard para que replay sin --batch no arranque\nmarta: y hay que documentarlo, nadie sabía que era peligroso", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "es"} -{"prompt": "tax calculation lives in the order service, the cart service and the admin refund flow. i want one owner for it. sketch the target shape and the steps to get there without a big-bang cutover", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "got this in prod, go service, no idea:\n\npanic: send on closed channel\n\ngoroutine 214 [running]:\nacme/settle.(*Batcher).enqueue(0xc0001a4000, {0xc0004b2100, 0x18})\n\t/build/settle/batcher.go:132 +0x9c\nacme/settle.(*Batcher).Add(...)\n\t/build/settle/batcher.go:98\nacme/settle.(*Worker).handle(0xc0000b6060, {0x8f2d40, 0xc0001bc0c0})\n\t/build/settle/worker.go:74 +0x1c5\nacme/settle.(*Worker).Run.func1()\n\t/build/settle/worker.go:41 +0x59\ncreated by acme/settle.(*Worker).Run in goroutine 1\n\t/build/settle/worker.go:39 +0x8d\n\nexit status 2\n\nit survived four weeks in staging without a single one of these", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "terraform for the ingest bucket, below. anything here that would make an auditor unhappy?\n\nresource \"aws_s3_bucket\" \"ingest\" {\n bucket = \"acme-ingest-prod\"\n}\n\nresource \"aws_s3_bucket_public_access_block\" \"ingest\" {\n bucket = aws_s3_bucket.ingest.id\n block_public_acls = true\n ignore_public_acls = true\n block_public_policy = false\n restrict_public_buckets = false\n}\n\nresource \"aws_s3_bucket_policy\" \"ingest\" {\n bucket = aws_s3_bucket.ingest.id\n policy = jsonencode({\n Version = \"2012-10-17\"\n Statement = [{\n Effect = \"Allow\"\n Principal = \"*\"\n Action = [\"s3:GetObject\"]\n Resource = \"${aws_s3_bucket.ingest.arn}/public/*\"\n }]\n })\n}\n\nresource \"aws_s3_bucket_lifecycle_configuration\" \"ingest\" {\n bucket = aws_s3_bucket.ingest.id\n rule {\n id = \"expire-raw\"\n status = \"Enabled\"\n expiration { days = 3650 }\n }\n}", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "spec below, stand up the endpoint. postgres + sqlc, follow how /v1/orders does it:\n\nGET /v1/settlements\n query: merchant_id (required), from (date), to (date), status (pending|paid|failed), cursor, limit (default 50, max 200)\n auth: merchant-scoped API key; a platform key may pass merchant_id for any merchant it owns\n response: { data: Settlement[], next_cursor: string|null }\n Settlement: { id, merchant_id, amount_cents, currency, status, expected_at, paid_at|null, failure_code|null }\n ordering: expected_at desc, id desc\n errors: 400 invalid_range if to < from, 403 merchant_not_owned, 422 limit_out_of_range\n the cursor must be opaque and must survive new rows being inserted mid-page", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "diff below — write the commit message. we squash, so one subject line plus a body:\n\ndiff --git a/internal/ledger/post.go b/internal/ledger/post.go\n@@ -18,6 +18,7 @@ type Entry struct {\n \tAccount string\n \tAmount int64\n \tCurrency string\n+\tBatchID string\n }\n@@ -55,9 +56,16 @@ func Post(ctx context.Context, db DB, entries []Entry) error {\n-\tfor _, e := range entries {\n-\t\tif _, err := db.Exec(ctx, insertEntry, e.Account, e.Amount, e.Currency); err != nil {\n-\t\t\treturn err\n-\t\t}\n-\t}\n+\tbatch := &pgx.Batch{}\n+\tfor _, e := range entries {\n+\t\tbatch.Queue(insertEntry, e.Account, e.Amount, e.Currency, e.BatchID)\n+\t}\n+\tres := db.SendBatch(ctx, batch)\n+\tdefer res.Close()\n+\tfor range entries {\n+\t\tif _, err := res.Exec(); err != nil {\n+\t\t\treturn fmt.Errorf(\"post entry: %w\", err)\n+\t\t}\n+\t}\n \treturn nil\n }", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"} -{"prompt": "sort out the invoice thing from yesterday", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "docs/webhooks.md still describes the v1 payload shape we killed in march. bring it in line with what we send now, and add the migration note partners keep asking for", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "help", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "summarise what the settlement service does for a new hire, then turn that into the actual service README", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.45, "slice": "mixed", "lang": "en"} -{"prompt": "reading through the fraud scoring service for the first time. give me the tour — entry points, what calls what, where the model gets loaded, and anything that looks load-bearing but undocumented", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "loading spinner on the refunds table flashes for 40ms then disappears, looks broken", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "unify the two date formatters and then note it in the changelog", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.35, "slice": "mixed", "lang": "en"} -{"prompt": "dark mode on the invoice preview inverts the PDF thumbnail and it looks terrible", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "needs to be faster", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "docstrings in `pipelines/common/io.py` are wrong about what happens on partial writes — they describe behaviour we removed. correct them to match the code", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "我们的 payout 对账逻辑要不要拆成独立服务？先给我一个方案对比，别写代码", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "zh"} -{"prompt": "same thing as last time but for refunds", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "tell me whether the retry logic in `gateway/client.go` can double-charge, and if it can, patch it", "purpose": "review", "secondary": "quickFix", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "stale `TODO(marta): remove after Q1` comments all over the ingest package, it's Q3", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "boundary", "lang": "en"} -{"prompt": "just make the dashboard usable again", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "jest is red after the money refactor and i can't tell if the test or the code is wrong:\n\n FAIL src/cart/__tests__/totals.test.ts\n ● cart totals › applies percentage promo before shipping\n\n expect(received).toEqual(expected) // deep equality\n\n - Expected - 3\n + Received + 3\n\n Object {\n - \"discountCents\": 450,\n - \"shippingCents\": 599,\n - \"totalCents\": 4649,\n + \"discountCents\": 449,\n + \"shippingCents\": 599,\n + \"totalCents\": 4650,\n \"subtotalCents\": 4500,\n }\n\n at Object. (src/cart/__tests__/totals.test.ts:88:23)\n\nTests: 1 failed, 214 passed, 215 total\nSnapshots: 0 total\nTime: 18.446 s", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "prometheus alert fired overnight and i don't understand the rule, let alone the alert:\n\nALERT SettlementLagHigh\n expr: max by (region) (settlement_batch_age_seconds{env=\"prod\"}) > 900\n for: 10m\n labels: { severity: page, team: payments }\n annotations:\n summary: \"settlement batches lagging in {{ $labels.region }}\"\n\nfiring instances:\n settlement_batch_age_seconds{env=\"prod\",region=\"eu-west-1\",shard=\"3\"} 1841\n settlement_batch_age_seconds{env=\"prod\",region=\"eu-west-1\",shard=\"7\"} 1802\n settlement_batch_age_seconds{env=\"prod\",region=\"us-east-1\",shard=\"1\"} 212\n\nlag cleared on its own at 04:12 without anyone touching it", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "jira ticket, verbatim, and i want the rollout plan not the code:\n\nDATA-417 — Retire the nightly full refresh\nToday `warehouse_refresh` truncates and rebuilds fct_orders, fct_payments and dim_merchant every night (runtime 3h10m, growing ~4%/month). We want incremental models instead. Constraints: finance reconciles against fct_payments at 06:00 UTC and cannot see partial state; the merchant dimension is SCD2 and history must not be rewritten; three downstream Looker models and one ML feature job read these tables. There is no staging warehouse with production volume. Prior attempt in February was rolled back after duplicate rows appeared in fct_payments.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "eslint output after the checkout rewrite, just make it quiet:\n\n/app/src/checkout/PaymentForm.tsx\n 14:8 warning 'useMemo' is defined but never used @typescript-eslint/no-unused-vars\n 88:11 error 'cardToken' is assigned a value but never used @typescript-eslint/no-unused-vars\n 132:5 error React Hook useEffect has a missing dependency: 'merchantId' react-hooks/exhaustive-deps\n 204:7 warning Unexpected console statement no-console\n\n/app/src/checkout/SummaryPanel.tsx\n 9:1 error 'formatMoney' is defined but never used @typescript-eslint/no-unused-vars\n 41:22 error Missing \"key\" prop for element in iterator react/jsx-key\n\n✖ 6 problems (4 errors, 2 warnings)\n 3 errors and 0 warnings potentially fixable with the `--fix` option.", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "pasted-context", "lang": "en"} -{"prompt": "cargo clippy on the firmware crate, mostly noise but a couple look real:\n\nwarning: this `if` statement can be collapsed\n --> src/modbus/frame.rs:118:5\n |\n118 | / if crc_ok {\n119 | | if len >= MIN_FRAME {\n | |_________^\n = help: for further information visit https://rust-lang.github.io/rust-clippy/\n\nwarning: casting `u32` to `u16` may truncate the value\n --> src/modbus/timing.rs:44:23\n |\n44 | let ticks: u16 = (bit_time_ns / 1000) as u16;\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^\n\nwarning: large size difference between variants\n --> src/proto/mod.rs:12:1\n |\n12 | enum Msg { Ping, Telemetry([u8; 512]) }\n\nwarning: `acme-fw` (lib) generated 14 warnings", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "ingest handler as it stands, pasted below. i want the same behaviour with the nesting flattened out, it's five levels deep in places:\n\nfunc (h *Handler) Ingest(w http.ResponseWriter, r *http.Request) {\n\tif r.Method == http.MethodPost {\n\t\tif ct := r.Header.Get(\"Content-Type\"); ct == \"application/json\" {\n\t\t\tvar batch Batch\n\t\t\tif err := json.NewDecoder(r.Body).Decode(&batch); err == nil {\n\t\t\t\tif len(batch.Readings) > 0 {\n\t\t\t\t\tif h.limiter.Allow(batch.DeviceID) {\n\t\t\t\t\t\tif err := h.store.Write(r.Context(), batch); err == nil {\n\t\t\t\t\t\t\tw.WriteHeader(202)\n\t\t\t\t\t\t\treturn\n\t\t\t\t\t\t}\n\t\t\t\t\t\thttp.Error(w, \"store\", 500)\n\t\t\t\t\t\treturn\n\t\t\t\t\t}\n\t\t\t\t\thttp.Error(w, \"rate\", 429)\n\t\t\t\t\treturn\n\t\t\t\t}\n\t\t\t}\n\t\t\thttp.Error(w, \"bad json\", 400)\n\t\t\treturn\n\t\t}\n\t}\n\thttp.Error(w, \"nope\", 400)\n}", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "docker logs from the ingest pod, it restarts every ~9 minutes under load:\n\n2026-07-29T11:02:14.881Z INFO ingest listening on :8080\n2026-07-29T11:04:02.113Z INFO batch accepted device=dev_7781 readings=512\n2026-07-29T11:06:41.552Z WARN write queue depth 8192 (max 8192)\n2026-07-29T11:07:03.918Z WARN write queue depth 8192 (max 8192)\n2026-07-29T11:08:22.004Z WARN gc pause 812ms\n2026-07-29T11:09:15.337Z WARN gc pause 1.44s\n2026-07-29T11:10:58.221Z ERROR liveness probe failed: context deadline exceeded\n2026-07-29T11:11:02.119Z INFO SIGTERM received, draining\n2026-07-29T11:11:32.120Z ERROR drain timed out, 6112 readings dropped\nstream closed EOF for prod/ingest-7d9c4f8b6-x2plq (ingest)\n\nmemory limit is 2Gi and it never reports above 1.3Gi", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "le rapport de l'audit sécurité, section paiements. dis-moi ce qui est vraiment exploitable chez nous :\n\nF-03 — Les clés API marchand sont stockées en clair dans la table `api_keys` (colonne `secret`). Rotation manuelle uniquement.\nF-07 — L'endpoint `/v1/charges` accepte un champ `merchant_id` dans le corps de la requête et ne vérifie pas qu'il correspond au scope du token.\nF-11 — Les webhooks sortants ne signent pas le corps ; les partenaires vérifient uniquement l'adresse IP source.\nF-14 — Les journaux applicatifs contiennent le PAN tronqué (6+4) ainsi que le nom du porteur.\nF-19 — Pas de limite de tentatives sur `/v1/auth/token` (bruteforce possible sur les clés courtes).", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "fr"} -{"prompt": "figma spec for the settlement timeline widget on the merchant dashboard:\n\nSettlement timeline (desktop ≥1024px)\n- Horizontal rail, 4 nodes: Captured → In transit → Paid → Reconciled. Node diameter 20px, 3px stroke.\n- Completed nodes: filled accent, white check glyph. Current node: accent stroke, pulsing 2s ease-in-out halo. Future nodes: 1px muted stroke, no fill.\n- Connector: 2px line, accent up to the current node, muted after. Animate the fill left-to-right over 400ms when a node completes.\n- Under each node: label (text-xs, medium) and timestamp (text-xs, muted). Timestamps in merchant local time, \"—\" when unknown.\n- Failed state: current node turns destructive, connector stops, an inline banner appears below the rail with the failure reason and a Retry link.\n- Below 1024px the rail becomes vertical, nodes left-aligned, 16px gutter.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "handoff notes for the mobile checkout sheet, build it in SwiftUI against our design system:\n\nCheckoutSheet\n- Presented as a `.sheet` with detents [.medium, .large]; drag indicator visible.\n- Header: order total (title2, bold) with the merchant name beneath (footnote, secondary).\n- Instrument list: rows of 56pt, leading icon 24pt, trailing checkmark on the selected row. Tapping a row selects it; long-press opens the remove menu.\n- \"Add payment method\" row pinned to the bottom of the list, tinted accent, chevron trailing.\n- Pay button: full width, 50pt tall, 12pt corner radius, disabled until an instrument is selected, spinner replaces the label while authorizing.\n- Errors surface as an inline red caption under the Pay button, never as an alert.\n- Dynamic Type up to AX3 must not clip the total; the row stack switches to vertical past AX1.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "css for our status chips, currently copy-pasted per status. i want one component out of this without any visual change:\n\n.chip-pending {\n display: inline-flex; align-items: center; gap: 6px;\n padding: 2px 10px; border-radius: 9999px;\n font-size: 12px; font-weight: 500; line-height: 20px;\n background: var(--gray-100); color: var(--gray-700);\n}\n.chip-paid {\n display: inline-flex; align-items: center; gap: 6px;\n padding: 2px 10px; border-radius: 9999px;\n font-size: 12px; font-weight: 500; line-height: 20px;\n background: var(--green-100); color: var(--green-800);\n}\n.chip-failed {\n display: inline-flex; align-items: center; gap: 6px;\n padding: 2px 10px; border-radius: 9999px;\n font-size: 12px; font-weight: 600; line-height: 20px;\n background: var(--red-100); color: var(--red-800);\n}", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "paste from the RFC someone abandoned in march. is any of it still true, and what would you keep?\n\n## Ledger v2 — motivation\nThe current ledger writes one row per order and derives per-instrument amounts at read time. With split tender this stops working: the derivation assumes a single capture. Proposal is double-entry with an `entries` table keyed by (account, batch_id) and a nightly compaction job.\n\n## Open questions\n- Do we backfill history or start fresh at cutover?\n- Compaction under load: the February prototype held locks for 40+ minutes.\n- Reporting reads go through `v_ledger_flat`; do we keep the view or force callers to migrate?\n\n## Not doing\nMulti-currency netting. Real-time reconciliation.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "这是 backfill 脚本的报错，跑到一半就挂了，看不出是数据问题还是代码问题：\n\nTraceback (most recent call last):\n File \"tools/backfill_payments.py\", line 141, in \n main()\n File \"tools/backfill_payments.py\", line 118, in main\n load_chunk(conn, rows)\n File \"tools/backfill_payments.py\", line 87, in load_chunk\n cur.executemany(UPSERT_SQL, [as_tuple(r) for r in rows])\n File \"/usr/lib/python3.12/site-packages/psycopg/cursor.py\", line 742, in executemany\n raise ex.with_traceback(None)\npsycopg.errors.UniqueViolation: duplicate key value violates unique constraint \"fct_payments_pkey\"\nDETAIL: Key (payment_id)=(pay_01HR9K2M) already exists.\n\n已经跑过一次 partial backfill，可能有关系", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "zh"} -{"prompt": "README for the reconciliation CLI is basically the argparse help text. here's what the tool actually takes now, write something a new operator could follow:\n\nusage: reconcile [-h] --since SINCE [--until UNTIL] [--merchant MERCHANT]\n [--source {gateway,ledger,both}] [--batch BATCH] [--dry-run]\n [--out OUT] [--format {csv,ndjson,table}] [--fail-on-drift]\n [--tolerance-cents TOLERANCE_CENTS] [--parallel PARALLEL]\n\nnotes the team knows but never wrote down: --dry-run still writes the audit row; --fail-on-drift is what CI uses; --parallel above 8 starves the pooler; --source both is the only mode that catches missing gateway events; running without --merchant on a full day takes ~25 minutes.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "pasted-context", "lang": "en"} -{"prompt": "incident timeline from last night, in raw form. turn it into the post-mortem doc, our template has Summary / Impact / Timeline / Root cause / Action items:\n\n21:04 alert SettlementLagHigh eu-west-1\n21:07 on-call ack, sees pooler at 200/200 connections\n21:12 manual replay found running for merchant 8812, started 20:51\n21:14 replay killed\n21:18 connections recover to 40/200, lag still climbing\n21:31 second replay discovered on shard 7, also killed\n21:52 locks released, batches start draining\n22:06 queue empty, lag back under 60s\n22:20 confirmed no payouts lost, 41 delayed by >30m\n09:15 next day: guard added to block replay without --batch\n\nimpact numbers: 41 merchants saw delayed payouts, longest 74 minutes, no financial loss", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "grafana panel query plus what support is telling us. something's off and i want the endpoint documented properly once we know:\n\nsum(rate(http_requests_total{route=\"/v1/payouts\",code=~\"4..\"}[5m])) by (code)\n\n code=\"400\" 0.02/s\n code=\"401\" 0.00/s\n code=\"409\" 1.84/s\n code=\"422\" 0.31/s\n\nsupport ticket: \"we get 409 conflict on about a third of our payout creates but the payout is created anyway, so we ignore it now\"\n\nnobody can tell me what 409 means on that route — it isn't in the reference at all", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "pyproject and the CI matrix disagree and the build is amber. smallest change that makes them agree:\n\n[project]\nname = \"acme-pipelines\"\nrequires-python = \">=3.10\"\ndependencies = [\n \"pandas>=2.0,<2.2\",\n \"pyarrow>=14,<15\",\n \"psycopg[binary]>=3.1\",\n \"dbt-core==1.7.9\",\n]\n\n# .github/workflows/ci.yml\nstrategy:\n matrix:\n python: [\"3.10\", \"3.11\", \"3.12\", \"3.13\"]\n\n# failure on 3.13:\nERROR: Could not find a version that satisfies the requirement pandas<2.2,>=2.0\nERROR: No matching distribution found for pandas<2.2,>=2.0", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"} -{"prompt": "helm values diff between staging and prod, i think one of these is why prod is slower:\n\n--- staging/values.yaml\n+++ prod/values.yaml\n@@ -8,7 +8,7 @@ ingest:\n replicas: 4\n- maxUnavailable: 1\n+ maxUnavailable: 0\n@@ -18,10 +18,10 @@ ingest:\n resources:\n requests:\n- cpu: 500m\n- memory: 1Gi\n+ cpu: 250m\n+ memory: 2Gi\n limits:\n- cpu: \"2\"\n+ cpu: 500m\n memory: 2Gi\n@@ -31,6 +31,7 @@ ingest:\n env:\n WRITE_QUEUE_MAX: \"8192\"\n+ GOGC: \"20\"\n BATCH_FLUSH_MS: \"250\"", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "o ficheiro `services/payouts/schedule.py` está assim há dois anos e ninguém lhe toca. o que é que ele faz exatamente, sobretudo a parte dos feriados?\n\ndef next_payout_date(merchant, after=None):\n d = after or date.today()\n delay = merchant.payout_delay_days or 2\n d = d + timedelta(days=delay)\n while d.weekday() >= 5 or d in HOLIDAYS.get(merchant.country, ()):\n d = d + timedelta(days=1)\n if merchant.payout_schedule == \"weekly\":\n while d.weekday() != merchant.payout_weekday:\n d = d + timedelta(days=1)\n elif merchant.payout_schedule == \"monthly\":\n d = d.replace(day=min(merchant.payout_dom, monthrange(d.year, d.month)[1]))\n if d <= (after or date.today()):\n d = (d + timedelta(days=32)).replace(day=merchant.payout_dom)\n return d", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "pt"} -{"prompt": "three call sites, three different ways of building the same gateway request. i want one builder and identical behaviour:\n\n# charges.py\nreq = {\"amount\": amount_cents, \"currency\": cur.lower(), \"source\": token,\n \"capture\": True, \"metadata\": {\"order\": order_id}}\n\n# refunds.py\nreq = dict(amount=amount_cents, currency=cur.upper(), charge=charge_id,\n reason=reason or \"requested_by_customer\",\n metadata={\"order\": str(order_id), \"actor\": actor})\n\n# admin/tools/manual_charge.py\nreq = {}\nreq[\"amount\"] = int(amount * 100)\nreq[\"currency\"] = cur\nreq[\"source\"] = token\nreq[\"capture\"] = capture\nif order_id:\n req[\"metadata\"] = {\"order\": order_id, \"manual\": \"1\"}", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "gateway client's retry decorator, which is wrapped around six methods and looks wrong to me but i want it restructured rather than rewritten:\n\ndef with_retries(attempts=3, backoff=0.5):\n def deco(fn):\n @wraps(fn)\n def inner(*a, **kw):\n last = None\n for i in range(attempts):\n try:\n return fn(*a, **kw)\n except (Timeout, ConnectionError) as e:\n last = e\n time.sleep(backoff * (2 ** i))\n except GatewayError as e:\n if e.status >= 500:\n last = e\n time.sleep(backoff * (2 ** i))\n else:\n raise\n raise last\n return inner\n return deco", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "legacy module header, comments included. same behaviour, modern shape, no new deps:\n\n# NOTE(2019): this file predates the payments service split. it talks to the\n# old ledger over a socket. do not remove the sleep on line 40, it is load\n# bearing (see INC-221).\n\nclass LedgerBridge(object):\n def __init__(self, host, port, retries=3):\n self.host = host\n self.port = port\n self.retries = retries\n self._sock = None\n\n def _connect(self):\n if self._sock is None:\n self._sock = socket.create_connection((self.host, self.port), 5)\n time.sleep(0.25)\n return self._sock\n\n def post(self, entry):\n for i in range(self.retries):\n try:\n s = self._connect()\n s.sendall(json.dumps(entry).encode() + b\"\\n\")\n return json.loads(s.recv(65536).decode())\n except Exception:\n self._sock = None\n raise RuntimeError(\"ledger unreachable\")", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "product wrote this in the ticket and i need it broken into shippable pieces with an order and the risky bits called out:\n\nMerchants should be able to set their own payout schedule from the dashboard: daily, weekly on a chosen weekday, or monthly on a chosen day. Changing the schedule must not affect payouts already in flight. Merchants on manual payouts should see the option but disabled with an upsell. We need an audit record of every schedule change including who changed it. Finance wants a report of merchants whose schedule changed in the last 30 days. Support needs the ability to override a schedule temporarily without the merchant seeing it change permanently.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "rate limiting keeps coming up and we keep deferring it. below is what ops observed last week; i want the design written down before any code — where counters live, redis failure behaviour, response headers, and the order we roll it across v1/v2/v3:\n\ntop talkers, 7d, requests per minute at peak:\n merchant 8812 14,200 rpm (bulk order sync every 5 min)\n merchant 4419 9,850 rpm (polling /v1/payouts once per second per store)\n merchant 7702 6,140 rpm (webhook replay loop, self-inflicted)\n everyone else < 900 rpm\n\ntwo of those three took the API down for everyone on tuesday for eleven minutes", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "reconciliation service has grown three responsibilities and i want a target architecture on paper before anyone opens an editor — and while you're in there, the naming is a mess. two deliverables: the design doc first, then the rename pass across the package", "purpose": "planning", "secondary": "refactor", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "finance asked for a plain-language explanation of how we compute the payout amount, including fees and reserves, and while writing it i realised the reserve calculation in `payouts/amount.go` doesn't match what we tell merchants. do both: the explainer, and then correct whichever side is wrong", "purpose": "writing", "secondary": "debugging", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "tengo dos problemas con el exportador de CSV: primero, nadie sabe qué significan las columnas y hace falta documentación para soporte; segundo, tarda 40 minutos con un millón de filas y creo que hay una consulta N+1 escondida. mira las dos cosas", "purpose": "writing", "secondary": "debugging", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "es"} -{"prompt": "`services/settlement/` has a `utils.py` that's become a junk drawer — 40 functions, no theme. split it along actual responsibilities, and once that's done i want the module docstrings to actually describe the new layout", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.55, "slice": "mixed", "lang": "en"} -{"prompt": "customers on the merchant dashboard see payout amounts flicker between the cached and fresh value for about a second. i suspect the SWR key, but i also want the loading behaviour on that whole screen rethought so it stops happening in general", "purpose": "debugging", "secondary": "frontendImpl", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "since thursday the nightly dbt run fails about half the time on `fct_payments` with a duplicate key, and it started right after the incremental change went in. work out what's actually duplicating, then put a test in the model so it can't happen silently again", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "il y a deux composants `MoneyInput` dans le repo, un dans `packages/ui` et un dans l'app checkout, et ils gèrent les décimales différemment. garde-en un seul, et corrige au passage le padding qui saute sur mobile", "purpose": "refactor", "secondary": "frontendImpl", "mixed": true, "difficulty": 0.5, "slice": "mixed", "lang": "fr"} -{"prompt": "`X-Merchant-Id` is accepted on six endpoints and ignored on the rest, which is confusing enough that partners get it wrong constantly. decide what the right behaviour is and write it up, then make the handlers consistent", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "settlement batch size is a magic 500 in four files. bump it to 2000 everywhere and note the change in the runbook so on-call isn't surprised", "purpose": "quickFix", "secondary": "writing", "mixed": true, "difficulty": 0.3, "slice": "mixed", "lang": "en"} -{"prompt": "admin refund modal still says \"Refund order\" when it's a partial. change the copy to reflect the amount, and update the help-centre article that shows the old screenshot", "purpose": "quickFix", "secondary": "writing", "mixed": true, "difficulty": 0.25, "slice": "mixed", "lang": "en"} -{"prompt": "we've been asked to support offline payments on the POS terminals, which means queueing captures on device and reconciling when the network comes back. i have no idea how we handle a capture that expires while queued, or a refund issued against a capture that hasn't reached us yet. i want the whole flow reasoned through — device state machine, server-side dedupe, what the merchant sees in the dashboard while things are pending — before we commit to a shape", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "honestly the biggest problem with our data platform is that nobody knows which tables are canonical. there are three `orders` tables in two schemas, one of them is a view over another, and the ML team reads a fourth one that a contractor built in 2023. i want a plan for consolidating this: what we keep, what we deprecate, how we migrate the readers, and how we stop it happening again", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "firmware team wants over-the-air updates delivered in waves rather than all at once, with automatic halt if the failure rate crosses a threshold. we have 30k devices on flaky rural links, no device-side telemetry beyond a heartbeat, and no way to roll back once slot B is confirmed. what does a safe rollout system look like here, and what has to exist before we can even start", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "engineering handbook has nothing about how we handle money in code and every new hire asks the same questions — cents vs decimals, where rounding happens, why the go service uses int64 and python uses Decimal, what to do about currencies with three decimal places. i'd like a proper page on it with examples from our own codebase", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "public API changelog has been a bulleted list of git commits for a year and partners have told us politely that it's useless. rewrite the last three months of it the way stripe does theirs — what changed, who it affects, what you need to do, with dates and version markers. the raw commits are in `CHANGELOG-raw.md`", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "we're deprecating the v1 payouts endpoints in january and i need the comms package: the deprecation notice for the docs site, the email to affected merchants, the response header we'll add, and a short internal note about what support should say when someone calls. tone should be apologetic but firm about the date", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "i've been asked to summarise, for the security review board, exactly what data crosses the boundary between our app servers and the gateway, in what direction, and how long we retain each field. i can read the code but writing this in a form a non-engineer reviewer will accept is the hard part", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "nobody on the team can explain how the fraud score gets into the checkout decision, including the person who wrote it. i want to understand the whole path: what features are computed where, which service calls the model, what happens when the model times out, and whether the fallback is a hard-coded threshold or something smarter", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "two engineers are arguing about whether our webhook delivery is at-least-once or effectively at-most-once given how the worker acks. rather than take sides i'd like someone to actually trace the code path from event write through delivery and ack, and say plainly which it is and where the gap is", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "before the pen test next month, go over how we authenticate merchant API calls end to end — key issuance, storage, the scope check middleware, rotation, and what happens with a revoked key that's already in flight. i'm not asking for changes yet, i want to know where we stand", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "src/sync/reconcile.ts is 900 lines and does fetching, diffing, conflict resolution and persistence in one file. no behaviour should change, but i want it in modules that a new person could navigate, with the conflict rules isolated enough that they're testable on their own", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "every service in the monorepo has its own hand-rolled config loading — env vars in some, a yaml file in others, and the python one reads both plus a json blob from consul. i'd like one approach across all of them, same values resolved the same way, and no service changing behaviour as a result", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "dependency situation in the settlement worker is grim: database handle, gateway client, metrics recorder and feature-flag client all reached through package-level singletons, which is why it's untestable. thread them through as dependencies instead without changing what the worker does", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "device registry needs a bulk enrolment path: operators upload a CSV of serial numbers and MAC addresses, we mint certs for each, and the whole thing has to be resumable because they upload 20k rows over a hotel wifi connection. postgres and a worker queue are fine, no new infra", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "chip radius should be 4px not 9999px", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "boundary", "lang": "en"} -{"prompt": "modal close button sits 2px too high", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "boundary", "lang": "en"} -{"prompt": "console.log left in the payment form", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "core", "lang": "en"} -{"prompt": "receipt footer has last year's address", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "core", "lang": "en"} -{"prompt": "\"recieve\" on the billing empty state", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "core", "lang": "en"} -{"prompt": "turn split_tender on in staging", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "core", "lang": "en"} -{"prompt": "webhook timeout 5s -> 15s", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "core", "lang": "en"} -{"prompt": "pin dbt-core to 1.7.9 in CI", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "boundary", "lang": "en"} -{"prompt": "CHANGELOG date says 2025, should be 2026", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "boundary", "lang": "en"} -{"prompt": "raise the payout page size to 100", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "boundary", "lang": "en"} -{"prompt": "das Retry-Limit auf 5 setzen, bitte", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "boundary", "lang": "de"} -{"prompt": "flag icons next to the currency codes", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "empty cart art above the fold on mobile", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "disable bulk refund when nothing's selected", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "pricing page hover feels sluggish", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "sticky header on the orders list", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "toast should slide, not fade", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "tighten the mobile card gap to 8px", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "boundary", "lang": "en"} -{"prompt": "spinner flashes for 40ms, looks broken", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "failed chip amber with an icon", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "`TxnCtx` should be `PaymentContext`", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "one money helper, not three", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "pull the promo logic out of `buildOrderDraft`", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "kill the barrel file in packages/ui", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "`amt` -> `amountCents` across the go service", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "die Test-Helper gehören in ein eigenes Paket", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "de"} -{"prompt": "split settlement/utils.py by responsibility", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "inline the single-use `formatChip` helper", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "who calls `LedgerBridge.post` these days?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "is our webhook signature check constant-time?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "what does `reconcileLedger` do on a partial?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "safe to run two settlement workers?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "¿es seguro exponer `failure_code` a los partners?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "es"} -{"prompt": "PR description for the batching change", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "docstring for `next_payout_date`, please", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "one-paragraph summary of the ledger ADR", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "release notes für Firmware 4.2, bitte kurz", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "de"} -{"prompt": "design doc for per-merchant limits", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "milestones for the POS offline work", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "`/v1/devices/{id}/certs` rotate endpoint, go", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "nightly job to expire stale carts", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "cursor pagination on the disputes list", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "dedupe the money helpers, then note it in the changelog", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.35, "slice": "mixed", "lang": "en"} -{"prompt": "scope out the retry redesign, then land step one", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "the usual, for the payouts screen", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "pick up the reconciliation thing", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "tidy", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "vague-eval", "lang": "en"} -{"prompt": "otra vez lo del checkout", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "es"} -{"prompt": "can you look at the thing", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "ship the rest of it", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "設定画面のあれ、直しておいて", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "ja"} -{"prompt": "payout CSV header says Amount, make it Amount (cents)", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "core", "lang": "en"} -{"prompt": "sandbox base URL still points at api-test", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "boundary", "lang": "en"} -{"prompt": "drop the unused `legacy_gc` column", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "merchant avatar should be circular", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "core", "lang": "en"} -{"prompt": "amount column right-aligned, monospaced", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "keyboard focus ring is invisible on dark", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "payments team wiki has a page called \"How refunds work\" that three different people have edited in three different directions, so it now contradicts itself twice — once about whether partial refunds can exceed the captured amount and once about the 90-day window. sort out what's actually true from the code and rewrite the page so it reads like one person wrote it", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "new engineers keep asking why there are two settlement services, and the honest answer is that one was a migration that never finished. i'd like that written down somewhere permanent — what each one owns today, which one is authoritative for which merchant cohort, and the fact that nobody should add features to the old one", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "support is drowning in \"where is my payout\" tickets and half of them are answered by explaining the two-day settlement delay. give me a help-centre article that covers the normal timeline, what a weekend or bank holiday does to it, why a payout can show as pending for longer, and when they should actually escalate to us", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "there's a class in the checkout service called `OrderCoordinator` that everyone is afraid of, about 600 lines, and it's the last thing standing between us and deleting the old cart module. read it and tell me what it's actually responsible for, what state it owns, and which of its methods are dead code — i'm not asking for changes yet", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "a junior on the team opened a PR that adds caching to the merchant lookup and it's got 40 files in it because they also reformatted everything. i can't see the actual change through the noise. tell me what the substantive change is, whether the cache invalidation is sound, and what i should push back on", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "someone on the data team wants to know whether our `fct_payments` model can be trusted for revenue reporting, given that it's incremental and keyed on payment_id with a merge strategy. i'd like an honest read of the model and its tests, including what happens when a payment row is updated after the incremental window has passed", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "error handling in the payments package is a mix of sentinel errors, wrapped errors with %w, and a custom `PaymentError` type that swallows the cause about half the time. i want one convention applied throughout, callers updated, and identical behaviour at the API boundary — same status codes, same response bodies", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "our integration tests spin up the whole stack through a 300-line bash script that predates docker compose, and every new test copies a chunk of it. i'd like the setup expressed once, in something maintainable, with the tests themselves unchanged — they should pass exactly as they do now, just faster to reason about", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "analytics team wants event-level payment data in the warehouse within five minutes instead of the current nightly batch, and my instinct is CDC off the postgres WAL, but i haven't thought through schema evolution, backfill, or what we do when the consumer falls behind. talk me through the options and what you'd pick for a team that has no streaming experience", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "en"} -{"prompt": "roughly once a day a merchant's dashboard shows a payout that then disappears on refresh, and support has three screenshots proving it. the API returns the payout from one replica and not from another as far as i can tell, but our reads are supposed to be routed to the primary for that endpoint. no errors anywhere in the logs", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "invoice preview screen renders server-side HTML in a webview and it's slow, janky on scroll, and completely inaccessible to VoiceOver. rebuild it as a native SwiftUI view backed by the same invoice model, matching the existing PDF layout closely enough that finance won't notice, including the itemised tax rows and the footer", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "we need an internal endpoint that support can hit to force-close a settlement batch early, with a reason and an actor recorded, guarded so it can only run on batches older than an hour and never on one that's mid-transfer. it should return the resulting batch state and the ids of anything it skipped", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "telemetry ingest endpoint currently accepts one reading per request and devices batch by sending 500 requests in a burst. add a batch endpoint that takes up to 1000 readings, rejects the whole batch if any reading fails validation, dedupes on (device_id, captured_at) against the last hour, and returns per-reading status", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} +{"prompt":"AegisQuartzPlayerService 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":"Find AegisBirchMigratorStore's duplicate retry source","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Design handed over a final pass for AegisCraneWorkspaceService, and the basic data flow in projects/aegis/ml/pipeline/features.py already works. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing Tokio deployment\n- keep the work scoped to AegisCraneWorkspaceService and its direct tests\n\nThis repository spans payments, iOS, Kubernetes; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"AegisFlintTimelineCoordinator: ship, then document","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"projects/aegis/lib/codec/frame.cc now contains AegisSummitProxyService'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.4,"slice":"core","lang":"en"} +{"prompt":"The AegisHarborIndexStore surface in projects/aegis/apps/console/routes/usage.svelte 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":"Split AegisDriftConsoleStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"AegisGarnetModalCoordinator: diagnose, then correct","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Please resist widening this one: AegisCraneWorkspaceStore works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside AegisCraneWorkspaceStore\n- keep public behavior and serialized data unchanged\n\nThe relevant code crosses payments, iOS, Kubernetes. Prefer evidence from the repository and make any assumption explicit.\n\nThe cause and exact value change are already known, so keep this as a contained correction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"En projects/aegis/workers/thumbnail/consumer.ex, AegisOpalRouterStore tiene un problema intermitente en el flujo de NATS JetStream. La causa ya está clara: cambia solo el timeout de staging de 15 a 30 segundos y ajusta su assertion.\n\nRestricciones:\n- seguir con NATS JetStream\n- conservar compatibilidad y cancelación\n- limitar el cambio a AegisOpalRouterStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"es"} +{"prompt":"Ticket OPS-41124: retire the legacy replay path for AegisLumenChartFlow\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 AegisLumenChartFlow 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":"# projects/aegis/config/staging.toml\n[worker.aegiscinderauthflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegiscinderauthflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegiscinderauthflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisCinderAuthFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41123\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/aegis/config/staging.toml and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Apparently: # projects/aegis/workers/thumbnail/consumer.ex\n[worker.aegisflinttimelineflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisflinttimelineflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisflinttimelineflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisFlintTimelineFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41121\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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Align AegisFlintTimelineFlow'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":"Bring AegisIrisBatchStore'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":"Release verification found a single stale AegisRainfallDBService value; the cause, desired value, and affected assertion are already agreed. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current Tokio operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"AegisPrismCacheStore is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. 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- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current Tokio operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes 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":"Two asks around AegisEmberRelayCoordinator: (1) assess ownership and failure handling in projects/aegis/crates/index/src/segment.rs; (2) capture the contract and rollback note for consumers. Keep public behavior and serialized data unchanged, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"diff --git a/projects/aegis/Sources/App/SessionStore.swift b/projects/aegis/Sources/App/SessionStore.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/aegis/Sources/App/SessionStore.swift\n+++ b/projects/aegis/Sources/App/SessionStore.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate AegisRainfallDBCoordinator'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":"AegisQuartzPlayerCoordinator: ship a sensible version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"AegisFrostPanelCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Please turn AegisFrostPanelService'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":"Describe AegisWillowCodecStore's error envelope","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"AegisMoonlitSDKCoordinator: sequence, then restructure","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"AegisOrbitSyncCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Lately: // projects/aegis/apps/console/routes/usage.svelte\nfinal class AegisMarbleTokenFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 AegisMarbleTokenFlow 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":"Oddly: // projects/aegis/ui/settings/PrivacyPane.tsx\nfinal class AegisDriftConsoleFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 AegisDriftConsoleFlow; 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":"AegisCoralUploadCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Summarize the AegisSpruceDaemonService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Responsive layout for AegisFlintTimelineStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"For AegisEchoRegistryCoordinator, separate AegisEchoRegistryCoordinator's policy from transport without behavior changes; once that is complete, correct the known stale timeout beside it. Work from projects/aegis/src/sync/reconcile.ts, stay with PostgreSQL 17, and keep public behavior and serialized data unchanged. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Incident timeline — INC-41153\n\n08:02 deploy AegisCedarPolicyCoordinator 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Turn the material above into a concise AegisCedarPolicyCoordinator 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":"UI ticket DES-41151: finish the compact AegisJuniperCLICoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/aegis/ui/settings/PrivacyPane.tsx\nFramework: NATS JetStream\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 AegisJuniperCLICoordinator'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":"Currently: projects/aegis/apps/console/routes/usage.svelte 里的 AegisMarbleTokenService 最近在 PostgreSQL 17 流程中出现间歇性问题。 请实现幂等 endpoint，包含持久 cursor、tenant 鉴权、spans 和 retry 测试。\n\n约束：\n- 继续使用 PostgreSQL 17\n- 保持兼容性和取消语义\n- 改动只限于 AegisMarbleTokenService","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"zh"} +{"prompt":"Split projects/aegis/workers/thumbnail/consumer.ex by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current AegisNovaPickerStore design actually guarantees what its callers assume. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside AegisNovaPickerStore\n- keep public behavior and serialized data unchanged\n\nThe relevant code crosses payments, iOS, Kubernetes. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Release engineering needs a AegisAmberFilterService 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":"diff --git a/projects/aegis/Sources/App/SessionStore.swift b/projects/aegis/Sources/App/SessionStore.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/aegis/Sources/App/SessionStore.swift\n+++ b/projects/aegis/Sources/App/SessionStore.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is AegisPrismCacheFlow'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":"UI ticket DES-41145: finish the compact AegisAcornWidgetFlow filter experience\n\nRoute: /catalog/search\nSource: projects/aegis/app/src/main/SyncWorker.kt\nFramework: PostgreSQL 17\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Use the UI evidence to complete AegisAcornWidgetFlow'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":"Incident timeline — INC-41115\n\n08:02 deploy AegisSableParserFlow 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 AegisSableParserFlow 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":"AegisIrisBatchCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"AegisVelaDrawerCoordinator: give it a nicer flow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Test Suite 'AegisMicaProfileFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[AegisMicaProfileFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/aegis/infra/modules/edge/main.tf:144: error: -[AegisMicaProfileFlowTests 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 '-[AegisMicaProfileFlowTests 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\nFind the source of this AegisMicaProfileFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Test Suite 'AegisEmberRelayFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[AegisEmberRelayFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/aegis/pkg/cache/lease.rs:144: error: -[AegisEmberRelayFlowTests 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 '-[AegisEmberRelayFlowTests 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 AegisEmberRelayFlow'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":"Today: Incident timeline — INC-41119\n\n08:02 deploy AegisNimbusFormFlow 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 AegisNimbusFormFlow 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":"Unifie les validateurs de AegisNimbusFormService","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"fr"} +{"prompt":"Why is AegisMapleQueueService stalling?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Context: # projects/aegis/db/migrations/20260730_events.sql\n[worker.aegisledgergatecoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisledgergatecoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisledgergatecoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisLedgerGateCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41150\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/aegis/db/migrations/20260730_events.sql and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Move AegisEmberRelayStore behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-41132: retire the legacy replay path for AegisMapleQueueFlow\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 AegisMapleQueueFlow 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":"We need to move AegisQuartzPlayerStore from the legacy store to NATS JetStream. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Draft AegisSpruceDaemonStore's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"AegisBirchMigratorService's SyncWorker.kt needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"The next client release depends on a new AegisNovaPickerService capability in projects/aegis/internal/auth/refresh.go, with WebGPU already chosen by the platform group. Implement the endpoint and durable cursor, enforce tenant authorization and idempotency, emit useful spans, cap work per request, and include focused tests for retries, cancellation, and malformed cursors.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing WebGPU deployment\n- keep the work scoped to AegisNovaPickerService and its direct tests\n\nThis repository spans payments, iOS, Kubernetes; use its existing conventions rather than importing a new abstraction.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"AegisMarbleTokenCoordinator: handle the lingering thing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Clarify AegisEchoRegistryStore's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Where did AegisWillowCodecService's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Background: UI ticket DES-41113: finish the compact AegisOspreyJobFlow filter experience\n\nRoute: /catalog/search\nSource: projects/aegis/packages/api/openapi.yaml\nFramework: SQLite\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\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Bring AegisOspreyJobFlow'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":"AegisNovaPickerCoordinator is blocking the next release because two validators with subtly different error strings. I need two concrete outcomes from a single pass: finish AegisNovaPickerCoordinator's responsive empty and retry states, and capture the contract and rollback note for consumers. Use the existing WebGPU conventions in projects/aegis/infra/modules/edge/main.tf; keep public behavior and serialized data unchanged. 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":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Production says AegisCloudReconcilerStore is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Reconstruct the failing timeline from logs and tests, identify which invariant first breaks, and distinguish causal signals from effects or cleanup noise.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current SQLite operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Two engineers disagree about whether AegisFernSnapshotStore's cache is authoritative. Walk the reads and writes in projects/aegis/cmd/exporter/main.py and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Before we approve AegisSlateEditorStore, assess whether two validators with subtly different error strings is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Fresh release brief for AegisPrismCacheCoordinator:\n- primary outcome: change AegisPrismCacheCoordinator'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/aegis/Sources/CLI/Commands/Doctor.swift\n- platform constraint: Tokio\n- known complication: a misleading timeout name used in five packages\n\nBoth results are required, but they should remain independently reviewable. Keep public behavior and serialized data unchanged; 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.6,"slice":"mixed","lang":"en"} +{"prompt":"Question: diff --git a/projects/aegis/db/migrations/20260730_events.sql b/projects/aegis/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/aegis/db/migrations/20260730_events.sql\n+++ b/projects/aegis/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nWire AegisEchoRegistryFlow'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.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Ticket OPS-41142: retire the legacy replay path for AegisBeaconStoreFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for AegisBeaconStoreFlow, 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":"In projects/aegis/ui/settings/PrivacyPane.tsx hat AegisOpalRouterService ein sporadisches Problem im NATS JetStream-Ablauf. Verfolge Queue, Scheduler und Abbruch, vergleiche Hypothesen und finde die Ursache vor jeder Änderung.\n\nRandbedingungen:\n- NATS JetStream weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf AegisOpalRouterService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um AegisOpalRouterService mit NATS JetStream kompatibel.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} +{"prompt":"The API work is done; what remains for AegisSableParserStore is the visible interaction layer across loading, offline, empty, and success cases. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside AegisSableParserStore\n- keep public behavior and serialized data unchanged\n\nThe relevant code crosses payments, iOS, Kubernetes. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"A previously stable test around AegisSummitProxyStore 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":"For AegisBasilRunnerCoordinator, produce a consumer guide for AegisBasilRunnerCoordinator; once that is complete, give the existing implementation a read-only safety pass. Work from projects/aegis/services/ledger/replay.go, stay with WebGPU, and keep public behavior and serialized data unchanged. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Security flagged AegisTideWorkerService for a read-only pass because its PostgreSQL 17 boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current PostgreSQL 17 operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes 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":"# projects/aegis/cmd/exporter/main.py\n[worker.aegiscraneworkspacecoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegiscraneworkspacecoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegiscraneworkspacecoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisCraneWorkspaceCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41159\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/aegis/cmd/exporter/main.py and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Before we approve AegisLedgerGateStore, assess whether two validators with subtly different error strings is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"projects/aegis/packages/api/openapi.yaml 里的 AegisCoralUploadStore 最近在 SQLite 流程中出现间歇性问题。 请给出阶段、兼容层、指标、rollback 和 ownership，先不要修改代码。\n\n约束：\n- 继续使用 SQLite\n- 保持兼容性和取消语义\n- 改动只限于 AegisCoralUploadStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"Observation: # projects/aegis/lib/codec/frame.cc\n[worker.aegisdeltacanvasflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisdeltacanvasflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisdeltacanvasflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisDeltaCanvasFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41116\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/aegis/lib/codec/frame.cc. 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":"Constraint: projects/aegis/pkg/cache/lease.rs now contains AegisCloudReconcilerFlow's normalization branch three times. Consolidate it behind one private helper, keep call ordering identical, and avoid touching generated code. Please preserve behavior. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Two deliverables are holding up AegisTideWorkerCoordinator. First, separate AegisTideWorkerCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/aegis/src/sync/reconcile.ts, which follows PostgreSQL 17 conventions and currently suffers from duplicate retries after a network handoff. Keep public behavior and serialized data unchanged.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Teach AegisMosaicGridStore to verify signed continuation tokens, reject cross-tenant cursors, and rotate keys without invalidating tokens issued during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"AegisBeaconStoreCoordinator: polish the last piece","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Why does AegisFrostPanelStore's WebGPU worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Request: Ticket OPS-41139: retire the legacy replay path for AegisIrisBatchFlow\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 AegisIrisBatchFlow 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":"Spell AegisDriftConsoleService's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Goal: // projects/aegis/apps/console/routes/usage.svelte\nfinal class AegisHarborIndexCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 AegisHarborIndexCoordinator 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":"AegisDeltaCanvasCoordinator: polish, then correct","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Memory attributed to AegisPineMetricsStore rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Does AegisCopperBridgeFlow enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Support wants the behavior in projects/aegis/app/src/main/SyncWorker.kt recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Flip AegisMoonlitSDKStore's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"I inherited AegisOspreyJobStore and need a careful read of projects/aegis/config/staging.toml before I can sign off on the next release. 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- keep public behavior and serialized data unchanged\n- stay compatible with the existing SQLite deployment\n- keep the work scoped to AegisOspreyJobStore and its direct tests\n\nThis repository spans payments, iOS, Kubernetes; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Unify the AegisMicaProfileStore validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Symptom: Two engineers disagree about whether AegisIrisBatchService's cache is authoritative. Walk the reads and writes in projects/aegis/cmd/exporter/main.py and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"AegisAtlasSearchCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump AegisLumenChartService's timeout to 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-41125: finish the compact AegisBirchMigratorFlow filter experience\n\nRoute: /catalog/search\nSource: projects/aegis/app/src/main/SyncWorker.kt\nFramework: PostgreSQL 17\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring AegisBirchMigratorFlow'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":"Read projects/aegis/pkg/cache/lease.rs and tell me whether AegisSlateEditorService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Ist AegisNimbusFormStore sicher?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"de"} +{"prompt":"Headsup: # projects/aegis/workers/thumbnail/consumer.ex\n[worker.aegisorbitsyncflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisorbitsyncflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisorbitsyncflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisOrbitSyncFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41141\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/aegis/workers/thumbnail/consumer.ex and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"pasted-context","lang":"en"} +{"prompt":"FYI: Ticket OPS-41112: retire the legacy replay path for AegisNovaPickerFlow\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 AegisNovaPickerFlow 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":"Is there a cleaner way to separate AegisOrbitSyncStore's transport, persistence, and retry policy without changing its API or timing behavior? Go ahead and make that structural change. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Set AegisRavenSessionStore's port to 8081","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"A flaky failure around AegisPineMetricsService survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside AegisPineMetricsService\n- keep public behavior and serialized data unchanged\n\nThe relevant code crosses payments, iOS, Kubernetes. Prefer evidence from the repository and make any assumption explicit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-41111\n\n08:02 deploy AegisOpalRouterFlow 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 AegisOpalRouterFlow 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":"Ticket OPS-41148: retire the legacy replay path for AegisSlateEditorFlow\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 AegisSlateEditorFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"AegisSlateEditorCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Meanwhile: # projects/aegis/Sources/App/SessionStore.swift\n[worker.aegisveladrawerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisveladrawerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisveladrawerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisVelaDrawerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41134\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/aegis/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":"Sequence AegisGarnetModalService's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current AegisHarborIndexService design actually guarantees what its callers assume. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside AegisHarborIndexService\n- keep public behavior and serialized data unchanged\n\nThe relevant code crosses payments, iOS, Kubernetes. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Locally: Ticket OPS-41144: retire the legacy replay path for AegisWrenExportFlow\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 AegisWrenExportFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Is there a cleaner way to separate AegisCedarPolicyFlow's transport, persistence, and retry policy without changing its API or timing behavior? Go ahead and make that structural change. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Production: Ticket OPS-41136: retire the legacy replay path for AegisSummitProxyFlow\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 AegisSummitProxyFlow 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":"AegisWrenExportCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"AegisSummitProxyCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Staging: projects/aegis/engine/render/atlas.cpp has grown through several launches, and AegisCopperBridgeService now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing NATS JetStream deployment\n- keep the work scoped to AegisCopperBridgeService and its direct tests\n\nThis repository spans payments, iOS, Kubernetes; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Corrija o timeout de AegisBasilRunnerService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"pt"} +{"prompt":"CI: Ticket OPS-41118: retire the legacy replay path for AegisMoonlitSDKFlow\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 AegisMoonlitSDKFlow 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":"Security flagged AegisAsterWebhookService for a read-only pass because its WebGPU boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current WebGPU operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes 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 name pendingAck means two different things across AegisCopperBridgeStore's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Describe AegisSableParserService's error envelope","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Why is AegisDeltaCanvasService stalling?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"A flaky failure around AegisCloudReconcilerService survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside AegisCloudReconcilerService\n- keep public behavior and serialized data unchanged\n\nThe relevant code crosses payments, iOS, Kubernetes. Prefer evidence from the repository and make any assumption explicit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/aegis/crates/index/src/segment.rs b/projects/aegis/crates/index/src/segment.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/aegis/crates/index/src/segment.rs\n+++ b/projects/aegis/crates/index/src/segment.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is AegisAtlasSearchFlow'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/aegis/web/components/FilterDrawer.vue\n[worker.aegisfrostpanelflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisfrostpanelflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisfrostpanelflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisFrostPanelFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41147\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/aegis/web/components/FilterDrawer.vue and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Two asks around AegisBirchMigratorCoordinator: (1) change AegisBirchMigratorCoordinator's known staging timeout from 15 to 30 seconds; (2) give the existing implementation a read-only safety pass. Keep public behavior and serialized data unchanged, and leave a clear boundary between the resulting artifacts or edits.","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Atlas: Is there a cleaner way to separate AegisCraneWorkspaceFlow's transport, persistence, and retry policy without changing its API or timing behavior? Go ahead and make that structural change. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"En projects/aegis/config/staging.toml, AegisCedarPolicyService tiene un problema intermitente en el flujo de SQLite. Añade el endpoint idempotente con cursor durable, autorización tenant, spans y tests de retry.\n\nRestricciones:\n- seguir con SQLite\n- conservar compatibilidad y cancelación\n- limitar el cambio a AegisCedarPolicyService Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con SQLite alrededor de AegisCedarPolicyService.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"es"} +{"prompt":"Three teams extended AegisJuniperCLIService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current NATS JetStream operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes 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":"# projects/aegis/ml/pipeline/features.py\n[worker.aegisfernsnapshotflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisfernsnapshotflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisfernsnapshotflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisFernSnapshotFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41149\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/aegis/ml/pipeline/features.py. 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":"Could the reasoning behind AegisWrenExportService's Tokio choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"AegisWrenExportStore has four wrappers that only translate the same error enum. Collapse them into one adapter and preserve every public case, message, and metric label. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"We need to move AegisVelaDrawerStore from the legacy store to Tokio. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"I inherited AegisDeltaCanvasStore and need a careful read of projects/aegis/engine/render/atlas.cpp before I can sign off on the next release. 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- keep public behavior and serialized data unchanged\n- stay compatible with the existing NATS JetStream deployment\n- keep the work scoped to AegisDeltaCanvasStore and its direct tests\n\nThis repository spans payments, iOS, Kubernetes; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Split projects/aegis/web/components/FilterDrawer.vue by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Fresh release brief for AegisOpalRouterCoordinator:\n- primary outcome: separate AegisOpalRouterCoordinator's policy from transport without behavior changes\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/aegis/workers/thumbnail/consumer.ex\n- platform constraint: NATS JetStream\n- known complication: a query plan that changes after statistics refresh\n\nBoth results are required, but they should remain independently reviewable. Keep public behavior and serialized data unchanged; 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":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"The behavior of AegisGarnetModalStore is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/aegis/web/components/FilterDrawer.vue. 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- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current WebGPU operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes 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":"AegisRavenSessionCoordinator: sequence, then ship","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} +{"prompt":"diff --git a/projects/aegis/src/sync/reconcile.ts b/projects/aegis/src/sync/reconcile.ts\nindex 62d71aa..90f3c1e 100644\n--- a/projects/aegis/src/sync/reconcile.ts\n+++ b/projects/aegis/src/sync/reconcile.ts\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 AegisRavenSessionFlow'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":"We need to move AegisBeaconStoreService from the legacy store to WebGPU. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"AegisAtlasSearchStore has four wrappers that only translate the same error enum. Collapse them into one adapter and preserve every public case, message, and metric label. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Match AegisMoonlitSDKService's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"AegisCinderAuthCoordinator: sequence, then ship","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} +{"prompt":"Design handed over a final pass for AegisLedgerGateService, and the basic data flow in projects/aegis/src/sync/reconcile.ts already works. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing PostgreSQL 17 deployment\n- keep the work scoped to AegisLedgerGateService and its direct tests\n\nThis repository spans payments, iOS, Kubernetes; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Polish the AegisEchoRegistryService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Beacon: # projects/aegis/db/migrations/20260730_events.sql\n[worker.aegistideworkerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegistideworkerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegistideworkerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisTideWorkerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41110\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/aegis/db/migrations/20260730_events.sql. 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":"Support wants the behavior in projects/aegis/ui/settings/PrivacyPane.tsx recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Cinder: We need to move AegisPineMetricsFlow from the legacy store to WebGPU. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Delta: // projects/aegis/services/ledger/replay.go\nfinal class AegisMosaicGridFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Split AegisMosaicGridFlow 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":"Read projects/aegis/db/migrations/20260730_events.sql and tell me whether AegisAmberFilterStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Make AegisFlintTimelineService keyboard navigable","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"AegisFernSnapshotCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Could the reasoning behind AegisAtlasSearchService's SQLite choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"AegisSpruceDaemonCoordinator needs a paired pass: lay out a staged migration for AegisSpruceDaemonCoordinator, plus then implement the bounded durable-cursor handler. Use projects/aegis/lib/codec/frame.cc as the source of truth, preserve the NATS JetStream contract, and avoid unrelated cleanup.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"AegisMapleQueueCoordinator needs a paired pass: lay out a staged migration for AegisMapleQueueCoordinator, plus then implement the bounded durable-cursor handler. Use projects/aegis/infra/modules/edge/main.tf as the source of truth, preserve the WebGPU contract, and avoid unrelated cleanup.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Ember: diff --git a/projects/aegis/services/ledger/replay.go b/projects/aegis/services/ledger/replay.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/aegis/services/ledger/replay.go\n+++ b/projects/aegis/services/ledger/replay.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is AegisGarnetModalFlow'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":"AegisRainfallDBStore occasionally exhibits cancellation being swallowed at the repository boundary, but only after a reconnect. Follow the data and cancellation paths in projects/aegis/Sources/App/SessionStore.swift and identify the cause before changing anything.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-41133: finish the compact AegisKiteSchedulerFlow filter experience\n\nRoute: /catalog/search\nSource: projects/aegis/packages/api/openapi.yaml\nFramework: SQLite\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 AegisKiteSchedulerFlow'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":"Frost: // projects/aegis/crates/index/src/segment.rs\nfinal class AegisCloudReconcilerCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 AegisCloudReconcilerCoordinator; 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":"Garnet: The AegisMosaicGridService empty state in projects/aegis/services/ledger/replay.go needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Release engineering needs a AegisVelaDrawerService 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":"AegisNimbusFormCoordinator: restructure, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"AegisEmberRelayService leaks tasks on shutdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Harbor: projects/aegis/config/staging.toml の AegisCoralUploadService で、SQLite の flow に断続的な問題が起きています。 queue、scheduler、cancel 経路を追い、仮説を比較して、変更前に原因を特定してください。\n\n制約:\n- SQLite を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は AegisCoralUploadService のみ","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"} +{"prompt":"Iris: The AegisBeaconStoreStore 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":"A copied hex color in AegisAcornWidgetStore lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Two asks around AegisDriftConsoleCoordinator: (1) assess ownership and failure handling in projects/aegis/workers/thumbnail/consumer.ex; (2) capture the contract and rollback note for consumers. Keep public behavior and serialized data unchanged, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Support wants the behavior in projects/aegis/services/ledger/replay.go recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Juniper: # projects/aegis/lib/codec/frame.cc\n[worker.aegiscopperbridgecoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegiscopperbridgecoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegiscopperbridgecoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisCopperBridgeCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41156\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/aegis/lib/codec/frame.cc and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"2026-07-30T08:14:11.409Z level=info service=aegisbasilrunnerflow pod=aegisbasilrunnerflow-7cf8 request_id=41127 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=aegisbasilrunnerflow request_id=41127 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=aegisbasilrunnerflow request_id=41127 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=aegisbasilrunnerflow request_id=41127 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=aegisbasilrunnerflow request_id=41127 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=aegisbasilrunnerflow request_id=41127 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=aegisbasilrunnerflow request_id=41127 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=aegisbasilrunnerflow request_id=41127 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nReconstruct the AegisBasilRunnerFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Ticket OPS-41157: retire the legacy replay path for AegisAsterWebhookCoordinator\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 AegisAsterWebhookCoordinator 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":"Split AegisCinderAuthStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"For AegisLumenChartCoordinator, lay out a staged migration for AegisLumenChartCoordinator; once that is complete, consolidate the duplicated normalization paths without changing behavior. Work from projects/aegis/Sources/App/SessionStore.swift, stay with Tokio, and keep public behavior and serialized data unchanged. Keep the two outcomes separately reviewable.","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Payments: Support wants the behavior in projects/aegis/app/src/main/SyncWorker.kt recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"AegisMosaicGridCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Give AegisKiteSchedulerService a loading skeleton","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-41143: finish the compact AegisCoralUploadFlow filter experience\n\nRoute: /catalog/search\nSource: projects/aegis/config/staging.toml\nFramework: SQLite\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring AegisCoralUploadFlow's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Kestrel: Split projects/aegis/packages/api/openapi.yaml by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"AegisWillowCodecCoordinator needs a paired pass: lay out a staged migration for AegisWillowCodecCoordinator, plus then implement the bounded durable-cursor handler. Use projects/aegis/cmd/exporter/main.py as the source of truth, preserve the Tokio contract, and avoid unrelated cleanup.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Ticket OPS-41126: retire the legacy replay path for AegisSpruceDaemonFlow\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\nDeliver the AegisSpruceDaemonFlow server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Corrige le timeout de AegisBasilRunnerStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"fr"} +{"prompt":"AegisMicaProfileCoordinator: document, then correct","purpose":"writing","secondary":"debugging","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Two deliverables are holding up AegisOspreyJobCoordinator. First, produce a consumer guide for AegisOspreyJobCoordinator. In the same workstream, correct the known stale timeout beside it. The relevant starting point is projects/aegis/config/staging.toml, which follows SQLite conventions and currently suffers from memory growth during hour-long imports. Keep public behavior and serialized data unchanged.\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":"writing","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Map AegisRavenSessionService's ownership split","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Incident timeline — INC-41129\n\n08:02 deploy AegisWillowCodecFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Turn the material above into a concise AegisWillowCodecFlow 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":"AegisSableParserCoordinator is blocking the next release because stale cursors when a page is resumed. I need two concrete outcomes from a single pass: finish AegisSableParserCoordinator's responsive empty and retry states, and capture the contract and rollback note for consumers. Use the existing PostgreSQL 17 conventions in projects/aegis/app/src/main/SyncWorker.kt; keep public behavior and serialized data unchanged. 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":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating a deadlock that appears only during shutdown in AegisRainfallDBFlow, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"The AegisFernSnapshotService surface in projects/aegis/ml/pipeline/features.py is stable now; turn its edge cases into API documentation with one successful example and one cancellation example.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Rename AegisLumenChartStore's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"projects/aegis/workers/thumbnail/consumer.ex の AegisJuniperCLIFlow で、NATS JetStream の flow に断続的な問題が起きています。 段階、互換性、metrics、rollback、ownership を提案し、コード変更の前で止めてください。\n\n制約:\n- NATS JetStream を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は AegisJuniperCLIFlow のみ","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"} +{"prompt":"Any races in AegisMicaProfileService?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"projects/aegis/src/sync/reconcile.ts has grown through several launches, and AegisTideWorkerStore now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing PostgreSQL 17 deployment\n- keep the work scoped to AegisTideWorkerStore and its direct tests\n\nThis repository spans payments, iOS, Kubernetes; use its existing conventions rather than importing a new abstraction.\n\nThe individual edits look tiny, but the semantic cleanup spans the repository and must preserve behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"AegisAmberFilterCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"For AegisKiteSchedulerCoordinator, ship the idempotent AegisKiteSchedulerCoordinator replay endpoint; once that is complete, capture the contract and rollback note for consumers. Work from projects/aegis/config/staging.toml, stay with SQLite, and keep public behavior and serialized data unchanged. Keep the two outcomes separately reviewable.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Lumen: # projects/aegis/engine/render/atlas.cpp\n[worker.aegisquartzplayerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.aegisquartzplayerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.aegisquartzplayerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.AegisQuartzPlayerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-41146\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/aegis/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.1,"slice":"pasted-context","lang":"en"} +{"prompt":"Summarize the AegisMapleQueueStore changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"The behavior of AegisOspreyJobService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/aegis/packages/api/openapi.yaml. 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- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current SQLite operational envelope\n\nSeveral teams work in this payments, iOS, Kubernetes 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":"Before touching projects/aegis/src/sync/reconcile.ts, 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":"Em projects/aegis/app/src/main/SyncWorker.kt, o AegisMarbleTokenStore tem um problema intermitente no fluxo de PostgreSQL 17. Finalize o layout responsivo, estados vazio e retry, foco por teclado, dark mode e reduced motion.\n\nRestrições:\n- continuar com PostgreSQL 17\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao AegisMarbleTokenStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"pt"} +{"prompt":"AegisAcornWidgetCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Any races in AegisPrismCacheService?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Queue AegisKiteSchedulerStore's expired sessions","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Maple: Ticket OPS-41140: retire the legacy replay path for AegisAmberFilterFlow\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 AegisAmberFilterFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Nimbus: Ticket OPS-41152: retire the legacy replay path for AegisPineMetricsCoordinator\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 AegisPineMetricsCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Investigate the AegisCinderAuthService hang","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} diff --git a/data/round2-02.jsonl b/data/round2-02.jsonl index 962b495..5b229cf 100644 --- a/data/round2-02.jsonl +++ b/data/round2-02.jsonl @@ -1,200 +1,200 @@ -{"prompt": "a consultant reviewed our compose code and left a list of \"performance issues\" that i'm not sure i believe — unstable lambdas, missing keys in lazy lists, derivedStateOf everywhere, and a claim that our whole schedule screen recomposes on every scroll tick. check the actual code and tell me which of those are real for us", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "our accessibility story on android is \"we ran the scanner once\". i'd like a plan for getting the booking flow to a state we could defend in a procurement review, and as a first step the slot picker fixed properly — content descriptions, touch targets, focus order, the lot", "purpose": "planning", "secondary": "frontendImpl", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "the retry delays array in constants.ts goes 1s 2s 4s 8s but the client only ever reads the first two, wire the rest up", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "appointment reminders stopped going out saturday night, here's the sidekiq log around then:\n\n2026-07-25T22:58:01.114Z pid=41 tid=9x8 class=ReminderJob jid=8f2b1c INFO: start\n2026-07-25T22:58:01.882Z pid=41 tid=9x8 class=ReminderJob jid=8f2b1c INFO: 412 reminders queued\n2026-07-25T23:00:00.004Z pid=41 tid=a02 class=ReminderJob jid=91cc40 INFO: start\n2026-07-25T23:00:00.119Z pid=41 tid=a02 class=ReminderJob jid=91cc40 INFO: 0 reminders queued\n2026-07-25T23:02:00.006Z pid=41 tid=b71 class=ReminderJob jid=aa1902 INFO: start\n2026-07-25T23:02:00.101Z pid=41 tid=b71 class=ReminderJob jid=aa1902 INFO: 0 reminders queued\n2026-07-26T00:00:00.008Z pid=41 tid=c19 class=ReminderJob jid=bb7711 INFO: start\n2026-07-26T00:00:00.093Z pid=41 tid=c19 class=ReminderJob jid=bb7711 INFO: 0 reminders queued\n\nno errors, it just decided there was nothing to send", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "we need the waitlist offer job written, here's what product agreed to:\n\n- triggered when an appointment is cancelled or a slot opens through a reschedule\n- eligible entries: same clinic, same day, provider matches or the entry says \"any\", not expired, not already holding an offer\n- FIFO by created_at, one offer at a time, 2-hour acceptance window (configurable per clinic)\n- offer goes out on the patient's preferred channel; if that channel fails, fall back to the other and record it\n- if the window passes, the offer moves to the next eligible entry automatically\n- if nobody accepts within 24 hours, the slot goes back to normal availability and we stop\n- everything must survive a redeploy mid-window\n\nrails, sidekiq, postgres — same patterns as the reminder job", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "a mid-size clinic reported that dragging an appointment to a new time occasionally moves a different appointment instead, maybe once a day, and we have no way to reproduce it. the drag layer keys blocks by index in some places and by id in others, which smells, but i can't connect that to what they're seeing", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "our error codes are documented nowhere and support guesses; produce the table from `app/errors/` with a human explanation per code", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "the endpoint for cancelling an appointment takes a reason enum that the mobile app doesn't send, so 40% of cancellations are `unspecified`, and product wants that fixed properly rather than defaulted", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "we have to support double-booking because three of our five pilot clinics deliberately overbook for no-show buffer, and our model currently forbids overlapping appointments at the database level with an exclusion constraint. i need to know what changes, how the schedule screen renders it, what the API says when someone books into an occupied slot, and how we let clinics that hate the idea keep the current behaviour", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "appointment blocks on the week grid are laid out with absolute positioning and magic offsets, so on a 13-inch laptop the 8am row is cut off and on a 4k monitor there's a band of dead space at the bottom. make the grid size to the viewport properly, keeping the existing look at the default zoom", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "compose theme file, inherited from a contractor. before i extend it for the dark palette i want to know what i'm dealing with:\n\n@Composable\nfun ClinicalTheme(\n darkTheme: Boolean = isSystemInDarkTheme(),\n dynamicColor: Boolean = true,\n content: @Composable () -> Unit\n) {\n val colorScheme = when {\n dynamicColor && Build.VERSION.SDK_INT >= Build.VERSION_CODES.S -> {\n val ctx = LocalContext.current\n if (darkTheme) dynamicDarkColorScheme(ctx) else dynamicLightColorScheme(ctx)\n }\n darkTheme -> DarkColors\n else -> LightColors\n }\n val view = LocalView.current\n if (!view.isInEditMode) {\n SideEffect {\n val window = (view.context as Activity).window\n window.statusBarColor = colorScheme.primary.toArgb()\n WindowCompat.getInsetsController(window, view).isAppearanceLightStatusBars = !darkTheme\n }\n }\n MaterialTheme(colorScheme = colorScheme, typography = ClinicalType, content = content)\n}", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "unity console after the build, the frame time doubled and i think one of these is the culprit:\n\n[Profiler] PlayerLoop 33.4ms\n ├ Update.ScriptRunBehaviourUpdate 21.8ms\n │ ├ EnemySpawner.Update() 14.2ms (GC.Alloc 1.4 MB)\n │ ├ PathfindingManager.Update() 5.1ms\n │ └ HUDController.Update() 2.4ms (GC.Alloc 220 KB)\n ├ PreLateUpdate.DirectorUpdate 3.1ms\n └ Render.OpaqueGeometry 7.6ms\n\nWarning: Instantiating 'Bullet(Clone)' 240 times this frame\nWarning: GameObject.FindWithTag called from EnemySpawner.Update()\nWarning: Camera.main accessed 240 times this frame\n[GC] Incremental GC collected 3.2 MB in 8.1ms", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "play console ANR cluster from last week's release, 0.9% of sessions:\n\nANR in io.clinicly.app (io.clinicly.app/.MainActivity)\nPID: 4471\nReason: Input dispatching timed out (Application does not respond)\n\n\"main\" prio=5 tid=1 Blocked\n | group=\"main\" sCount=1 dsCount=0 flags=1 obj=0x72b9c4d0\n at io.clinicly.data.SyncCoordinator.awaitIdle(SyncCoordinator.kt:88)\n - waiting to lock <0x0a11c3f2> (a java.lang.Object) held by thread 42\n at io.clinicly.data.AppointmentRepository.refresh(AppointmentRepository.kt:214)\n at io.clinicly.ui.ScheduleViewModel$load$1.invokeSuspend(ScheduleViewModel.kt:66)\n\n\"DefaultDispatcher-worker-3\" prio=5 tid=42 Native\n at android.database.sqlite.SQLiteConnection.nativeExecuteForChangedRowCount(Native method)\n at io.clinicly.data.local.AppointmentDao_Impl.upsertAll(AppointmentDao_Impl.java:181)\n\nlocked <0x0a11c3f2>", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "sentry issue, been firing since the timezone work went in:\n\nActiveRecord::StatementInvalid: PG::DatetimeFieldOverflow: ERROR: date/time field value out of range: \"2026-11-01 02:30:00\"\nHINT: Perhaps you need a different \"datestyle\" setting.\n\n app/models/clinic_hours.rb:41:in `slots_for'\n app/services/appointments/availability.rb:88:in `block in build'\n app/services/appointments/availability.rb:84:in `each'\n app/services/appointments/availability.rb:84:in `build'\n app/controllers/api/v2/availability_controller.rb:19:in `index'\n\n clinic_id: 4412 (America/Santiago)\n requested_date: 2026-11-01\n events: 1,204 in 6 days\n users affected: 38\n\nonly clinics in a handful of timezones, and always on specific dates", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "gradle keeps failing on CI only, works on my machine and on two other laptops:\n\n> Task :app:kaptGenerateStubsReleaseKotlin FAILED\ne: file:///home/runner/work/clinicly/app/src/main/java/io/clinicly/di/AppModule.kt:44:1 error: [Dagger/DuplicateBindings] io.clinicly.data.Clock is bound multiple times:\n @Provides @Singleton io.clinicly.data.Clock io.clinicly.di.AppModule.provideClock()\n @Provides @Singleton io.clinicly.data.Clock io.clinicly.di.TestClockModule.provideClock()\n\nFAILURE: Build failed with an exception.\n* What went wrong:\nExecution failed for task ':app:kaptGenerateStubsReleaseKotlin'.\n> A failure occurred while executing org.jetbrains.kotlin.gradle.internal.KaptExecution\n\n* Try:\n> Run with --stacktrace option to get the stack trace.\n\nBUILD FAILED in 4m 12s", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "PR i'm meant to approve today. it's from someone senior so i want a second opinion before i comment:\n\n@@ -12,6 +12,28 @@ class Appointment < ApplicationRecord\n belongs_to :clinic\n belongs_to :patient\n \n+ after_commit :sync_to_calendar, on: [:create, :update]\n+\n+ def sync_to_calendar\n+ CalendarSyncJob.perform_now(id)\n+ rescue => e\n+ Rails.logger.warn(\"calendar sync failed: #{e.message}\")\n+ end\n+\n+ def self.overlapping(clinic_id, range)\n+ where(clinic_id: clinic_id)\n+ .where(\"tstzrange(starts_at, ends_at) && tstzrange(?, ?)\", range.first, range.last)\n+ end\n+\n scope :upcoming, -> { where(\"starts_at > ?\", Time.current) }\n@@ -41,7 +63,7 @@ class Appointment < ApplicationRecord\n- validates :starts_at, presence: true\n+ validates :starts_at, presence: true, if: -> { !skip_validation }", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "das ist unsere Migration für die Mandantentrennung. Bevor wir sie ausführen: hältst du das für sicher?\n\nclass AddClinicScopeToAppointments < ActiveRecord::Migration[7.1]\n def change\n add_column :appointments, :clinic_id, :bigint\n add_index :appointments, :clinic_id, algorithm: :concurrently\n Appointment.reset_column_information\n Appointment.find_each do |a|\n a.update_column(:clinic_id, a.patient.clinic_id)\n end\n change_column_null :appointments, :clinic_id, false\n add_foreign_key :appointments, :clinics\n end\nend\n\nTabelle hat 22 Millionen Zeilen, Postgres 16, kein Wartungsfenster", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "de"} -{"prompt": "changelog time, we ship the android app thursday. commits since 3.4:\n\n* a81f22c feat(schedule): week view swipe gestures\n* 4409ba1 fix(sync): don't drop local edits when the server 409s\n* 77c0e19 fix(a11y): talkback reads slot times correctly now\n* 2b1904d chore: bump compose bom to 2026.06.00\n* 9911aa0 feat(booking): waitlist join from a full day\n* 31de770 perf(schedule): remove recomposition storm on day change\n* cc4102b fix(notifications): reminder deep link opened the wrong appointment\n* 6f2b901 chore: crashlytics ndk symbols upload\n* 0091ac4 fix(login): biometric prompt dismissed on first launch\n\nplay store listing, so friendly and short, no commit hashes", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "support macro draft below is terrible and i have to send something today. rewrite it:\n\n\"Hi, Thank you for contacting Clinicly Support. Regarding your issue with appointment reminders not being sent, this is caused by the clinic timezone setting being incorrect in your Clinic Settings page which needs to be set correctly by an administrator of your clinic account. Please navigate to Settings > Clinic > Regional and select the correct timezone from the dropdown list and then save the changes and reminders will be sent correctly going forward. Note that appointments already scheduled will not be updated retroactively. Thank you for your patience. Best regards, Clinicly Support Team\"\n\nkeep the facts, lose the bureaucracy, and add the bit about existing appointments needing a manual resend", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "app crashes on API 34 the moment you open notifications settings, and the fix is probably one line:\n\njava.lang.SecurityException: One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED should be specified when a receiver isn't being registered exclusively for system broadcasts\n\tat android.os.Parcel.createExceptionOrNull(Parcel.java:3057)\n\tat android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:1826)\n\tat io.clinicly.notifications.ReminderSettingsFragment.onStart(ReminderSettingsFragment.kt:44)\n\ntargetSdk went from 33 to 34 in the last release", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "pasted-context", "lang": "en"} -{"prompt": "HUD prefab is a mess of anchors and i've been asked to make it work on ultrawide and on steam deck. current layout values:\n\nCanvas: Scale With Screen Size, ref 1920x1080, match 0.5\nHealthBar: anchor min (0,1) max (0,1), pos (120, -60), size (240, 24)\nAmmoCounter: anchor min (1,1) max (1,1), pos (-140, -60), size (180, 40)\nMinimap: anchor min (1,0) max (1,0), pos (-160, 160), size (280, 280)\nWaveBanner: anchor min (0.5,1) max (0.5,1), pos (0, -40), size (600, 80)\nBossHealth: anchor min (0.5,1) max (0.5,1), pos (0, -140), size (900, 32)\n\nat 21:9 the minimap sits under the bezel on deck and the boss bar overlaps the wave banner", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "clinic phone number missing from the receipt", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "core", "lang": "en"} -{"prompt": "waitlist window default to 90 minutes", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "core", "lang": "en"} -{"prompt": "one slot-eligibility function, not three", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "kdoc on SyncCoordinator, please", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "is our tenant scoping actually enforced?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "schedule thing again", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "there is no document anywhere that says what happens to a patient's data when a clinic leaves us, and both legal and two prospects have now asked. from the code and the ops runbooks, work out what actually happens today — export format, deletion timeline, what stays in backups — and write it up as a page we can hand to a customer without lawyering it first", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "i'd like to understand how room assignment picks a room when two appointments could use the same one", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "compose app is one gradle module and builds take four minutes on the CI runners, which is starting to hurt. modularising is the obvious answer but i've seen it go badly — circular dependencies, dagger components everywhere, nobody agreeing where things live. what would a sane module structure look like for an app this size, and in what order would you carve it up", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "logcat from a tester's Pixel, the appointment list just goes blank:\n\nE/AndroidRuntime( 8812): FATAL EXCEPTION: main\nE/AndroidRuntime( 8812): Process: io.clinicly.app, PID: 8812\nE/AndroidRuntime( 8812): java.lang.IllegalStateException: Reading a state that was created after the snapshot was taken or in a snapshot that has not yet been applied\nE/AndroidRuntime( 8812): \tat androidx.compose.runtime.snapshots.SnapshotKt.readError(Snapshot.kt:2371)\nE/AndroidRuntime( 8812): \tat androidx.compose.runtime.snapshots.SnapshotStateList.get(SnapshotStateList.kt:88)\nE/AndroidRuntime( 8812): \tat io.clinicly.schedule.DayColumnKt$DayColumn$1$2.invoke(DayColumn.kt:141)\nE/AndroidRuntime( 8812): \tat androidx.compose.foundation.lazy.LazyListKt.items(LazyList.kt:212)\nE/AndroidRuntime( 8812): \tat io.clinicly.schedule.ScheduleScreenKt.ScheduleScreen(ScheduleScreen.kt:88)\nE/AndroidRuntime( 8812): \tat io.clinicly.MainActivity$onCreate$1.invoke(MainActivity.kt:52)\n\nonly reproduces after you rotate while the refresh is in flight", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "rspec is red on main and the diff that broke it is three commits back somewhere:\n\nFailures:\n\n 1) Appointments::Reschedule moves the slot and notifies the patient\n Failure/Error: expect(appointment.reload.starts_at).to eq(new_slot.starts_at)\n\n expected: 2026-08-03 14:00:00.000000000 +0000\n got: 2026-08-03 13:00:00.000000000 +0000\n\n (compared using ==)\n # ./spec/services/appointments/reschedule_spec.rb:41:in `block (2 levels)'\n\n 2) Appointments::Reschedule refuses a slot outside clinic hours\n Failure/Error: expect { subject }.to raise_error(OutsideClinicHours)\n expected OutsideClinicHours, got #\n # ./spec/services/appointments/reschedule_spec.rb:63:in `block (2 levels)'\n\nFinished in 1 minute 12.4 seconds (files took 6.1 seconds to load)\n412 examples, 2 failures\n\nboth of these passed on friday and nobody touched the scheduler", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "ログにこれが延々と出ていて、予約の同期が止まります。原因が分かりません:\n\nW/SyncWorker(3312): retrying sync attempt=4 delay=8000ms\nW/SyncWorker(3312): retrying sync attempt=5 delay=16000ms\nE/SyncWorker(3312): sync failed: retrofit2.HttpException: HTTP 409 Conflict\nE/SyncWorker(3312): \tat io.clinicly.net.ApiClient$sync$2.invokeSuspend(ApiClient.kt:141)\nE/SyncWorker(3312): \tat kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)\nI/WM-WorkerWrapper(3312): Worker result RETRY for Work [ id=8f21-c0aa-4771, tags={ sync } ]\nI/WM-Processor(3312): Processor stopping foreground work sync\nW/SyncWorker(3312): retrying sync attempt=6 delay=32000ms\n\nサーバー側のログでは 409 は「revision mismatch」と書いてあります", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "ja"} -{"prompt": "crash reporter groups these together but the stacks look unrelated to me:\n\nNullReferenceException: Object reference not set to an instance of an object\n at Clinicly.Game.WaveDirector.OnEnemyKilled (Clinicly.Game.Enemy e) [0x00021] in /Assets/Scripts/WaveDirector.cs:118\n at Clinicly.Game.Enemy.Die () [0x0000c] in /Assets/Scripts/Enemy.cs:88\n at Clinicly.Game.DamageSystem.Apply (Clinicly.Game.Enemy target, System.Single amount) [0x00044] in /Assets/Scripts/DamageSystem.cs:52\n at Clinicly.Game.Bullet.OnTriggerEnter (UnityEngine.Collider other) [0x0001a] in /Assets/Scripts/Bullet.cs:41\n\nMissingReferenceException: The object of type 'Transform' has been destroyed but you are still trying to access it.\n at UnityEngine.Transform.get_position ()\n at Clinicly.Game.HomingBullet.FixedUpdate () [0x00010] in /Assets/Scripts/HomingBullet.cs:33\n\n480 users, all on the wave-12 boss", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "detekt and the runtime disagree about this coroutine scope, and users see duplicate bookings:\n\nclass BookingViewModel(\n private val repo: AppointmentRepository,\n private val scope: CoroutineScope = CoroutineScope(SupervisorJob() + Dispatchers.Default)\n) : ViewModel() {\n\n fun book(slotId: String) {\n scope.launch {\n val result = repo.book(slotId)\n _state.update { it.copy(booked = result) }\n }\n }\n\n override fun onCleared() {\n super.onCleared()\n }\n}\n\ntapping book twice quickly creates two appointments about 30% of the time, and rotating the phone mid-book does it every time", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "security questionnaire from a hospital customer came back with this section and i need to answer honestly:\n\n7.3 — Does the application enforce role-based access control at the API layer, and are authorization decisions logged?\n7.4 — Are patient records segregated per tenant at the database level, and if so by what mechanism?\n7.5 — Describe session invalidation on password change and on administrative account suspension.\n7.6 — Are audit logs immutable and retained for at least six years?\n7.9 — Can a clinic administrator export all data for a single patient on request, and how long does that take?\n\ngo through our rails app and tell me what's actually true for each of these", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "someone's proposed this ECS refactor in the game repo and i can't tell if it's an improvement or just fashion:\n\n// current\npublic class Enemy : MonoBehaviour {\n public float speed; public int hp;\n void Update() { transform.position += dir * speed * Time.deltaTime; }\n}\n\n// proposed\npublic struct Position : IComponentData { public float3 Value; }\npublic struct Velocity : IComponentData { public float3 Value; }\npublic partial struct MoveSystem : ISystem {\n public void OnUpdate(ref SystemState state) {\n foreach (var (pos, vel) in SystemAPI.Query, RefRO>())\n pos.ValueRW.Value += vel.ValueRO.Value * SystemAPI.Time.DeltaTime;\n }\n}\n\nwe have maybe 300 enemies on screen at peak and a two-person team", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "accessibility audit output for the booking flow, tell me which of these are real problems and which are the tool being pedantic:\n\nsrc/booking/SlotPicker.tsx\n serious Buttons must have discernible text (button-name) — 14 nodes\n serious Form elements must have labels (label) — 3 nodes\n moderate Elements must have sufficient color contrast (color-contrast) — 22 nodes (4.1:1 vs required 4.5:1)\n minor Heading levels should only increase by one (heading-order) — 2 nodes\n\nsrc/booking/Confirmation.tsx\n critical element must have a lang attribute (html-has-lang)\n serious ARIA attributes must conform to valid values (aria-valid-attr-value) — aria-live=\"polite \" (trailing space)\n moderate Interactive controls must not be nested (nested-interactive) — 1 node\n\n47 total violations, 0 incomplete", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "here's the query the scheduling page runs every time someone changes the week. is 400ms reasonable for this or is something dumb happening?\n\nSELECT a.id, a.starts_at, a.ends_at, a.status,\n p.first_name, p.last_name, p.date_of_birth,\n pr.display_name AS provider_name,\n r.name AS room_name,\n (SELECT COUNT(*) FROM appointment_notes n WHERE n.appointment_id = a.id) AS note_count\nFROM appointments a\nJOIN patients p ON p.id = a.patient_id\nJOIN providers pr ON pr.id = a.provider_id\nLEFT JOIN rooms r ON r.id = a.room_id\nWHERE a.clinic_id = $1\n AND a.starts_at >= $2 AND a.starts_at < $3\n AND a.status <> 'cancelled'\nORDER BY a.starts_at ASC;\n\nindexes: appointments(clinic_id, starts_at), patients(id), providers(id)", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "two engineers wrote the same helper in the same sprint. which one would you keep, and why?\n\n// version A — utils/time.ts\nexport function slotsBetween(open: Date, close: Date, minutes: number): Date[] {\n const out: Date[] = []\n for (let t = open.getTime(); t + minutes * 60000 <= close.getTime(); t += minutes * 60000)\n out.push(new Date(t))\n return out\n}\n\n// version B — booking/slots.ts\nexport const buildSlots = ({ open, close, step, skip = [] }: SlotArgs) =>\n Array.from(\n { length: Math.floor((+close - +open) / (step * 60000)) },\n (_, i) => new Date(+open + i * step * 60000)\n ).filter(d => !skip.some(([s, e]) => d >= s && d < e))\n\nboth are used in production right now, on different screens", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "raw notes from the clinic onboarding call, turn them into the implementation guide we hand to new customers:\n\n- they get a CSV of patients from their old system, columns never match, we map by hand today\n- provider availability set up in the admin, but recurring blocks (lunch, admin time) are a separate screen nobody finds\n- rooms are optional; single-provider clinics skip them entirely\n- SMS reminders need their own twilio number, takes 2-3 days for approval, has to start before go-live\n- test appointment then a test reminder is how we prove it works\n- go-live is always a monday, they keep the old system read-only for a month\n- most common failure: nobody set the clinic timezone and every reminder goes out an hour off", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "api reference for the availability endpoint is one sentence long. here's the controller — write the real thing:\n\ndef index\n clinic = Clinic.find(params[:clinic_id])\n authorize! :read, clinic\n range = DateRange.parse!(params[:from], params[:to])\n raise TooWide if range.days > 62\n providers = clinic.providers.where(id: params[:provider_ids].presence || clinic.provider_ids)\n slots = Appointments::Availability.new(clinic:, providers:, range:, duration: params.fetch(:duration, 30).to_i).build\n render json: { data: slots.map { |s| SlotSerializer.new(s) }, meta: { timezone: clinic.timezone } }\nend\n\ncover the 30-day default, the 62-day cap, what duration does, and that all times come back in clinic-local ISO8601", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "escreve o texto do post-mortem a partir destas notas, formato: impacto, cronologia, causa, ações:\n\n14:02 — clientes reportam que a agenda aparece vazia\n14:06 — on-call confirma: API devolve 200 com lista vazia para clínicas com fuso -03\n14:11 — deploy das 13:40 identificado como suspeito (mudança no cálculo de intervalos)\n14:19 — rollback iniciado\n14:26 — rollback concluído, agendas voltam ao normal\n14:40 — confirmado: 61 clínicas afetadas durante 24 minutos, nenhuma consulta perdida\n15:10 — causa: o novo cálculo usava a data do servidor em UTC em vez do fuso da clínica\n\nações combinadas: teste de regressão com fusos negativos, alerta para respostas vazias acima de 5%", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "pasted-context", "lang": "pt"} -{"prompt": "kotlin file has zero kdoc and the next person will hate us. document the public surface based on what it does:\n\nclass SyncCoordinator(\n private val api: ApiClient,\n private val dao: AppointmentDao,\n private val clock: Clock,\n) {\n suspend fun pull(since: Instant?): SyncResult { /* ... */ }\n suspend fun push(pending: List): SyncResult { /* ... */ }\n suspend fun awaitIdle(timeout: Duration = 30.seconds)\n fun observeState(): Flow\n val lastSuccessfulSync: Instant?\n}\n\nthings worth capturing: pull with a null `since` does a full refresh and can take minutes on a big clinic; push is all-or-nothing per batch; awaitIdle throws on timeout; observeState never completes", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "i have to explain our offline behaviour to the app review team and to our own support staff. here's what the code does, in bullets, from my reading:\n\n- edits made offline go into a `pending_edits` room table with a local revision\n- on reconnect, push happens before pull, oldest first\n- a 409 from the server means the server version won, and the local edit is discarded silently\n- appointments created offline get a client-generated UUID that the server honours\n- if the app is killed mid-sync, the worker restarts the whole batch\n- there is no user-visible indication that a local edit was discarded\n\nturn that into two documents: one for the app review notes, one for support", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "README for the game repo hasn't been touched since the jam version. current state of things:\n\n- unity 6000.0.28f1, URP, addressables for the level packs\n- three scenes that matter: Boot, Hub, Run. everything else is test scaffolding\n- input via the new Input System, bindings in Assets/Settings/PlayerControls.inputactions\n- steam build via a bash script in tools/, needs SteamCMD on PATH and a `.env` with the app id\n- tests: EditMode only, playmode tests are broken and skipped in CI\n- known: opening Run directly from the editor bypasses save loading and softlocks after the first wave\n\nwrite it so a new contributor can get to a running build without asking anyone", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "ktlint is blocking the merge, all of it looks cosmetic:\n\napp/src/main/java/io/clinicly/ui/ScheduleScreen.kt:41:1: Wildcard import (cannot be auto-corrected)\napp/src/main/java/io/clinicly/ui/ScheduleScreen.kt:88:121: Exceeded max line length (120)\napp/src/main/java/io/clinicly/ui/ScheduleScreen.kt:141:5: Missing newline before \"}\"\napp/src/main/java/io/clinicly/data/SyncCoordinator.kt:19:1: Package name must not contain underscore\napp/src/main/java/io/clinicly/data/SyncCoordinator.kt:66:33: Unnecessary semicolon\napp/src/main/java/io/clinicly/di/AppModule.kt:12:1: Imports must be ordered in lexicographic order\n\n> Task :app:ktlintMainSourceSetCheck FAILED\n6 style violations", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "pasted-context", "lang": "en"} -{"prompt": "rubocop after the rebase, just get it green:\n\nOffenses:\n\napp/services/appointments/availability.rb:14:5: C: Metrics/MethodLength: Method has too many lines. [22/15]\napp/services/appointments/availability.rb:41:81: C: Layout/LineLength: Line is too long. [104/100]\napp/services/appointments/reschedule.rb:9:3: C: Style/Documentation: Missing top-level class documentation comment.\napp/models/clinic_hours.rb:33:11: W: Lint/UselessAssignment: Useless assignment to variable - `tz`.\napp/controllers/api/v2/availability_controller.rb:22:7: C: Style/GuardClause: Use a guard clause instead of wrapping the code inside a conditional expression.\nspec/factories/appointments.rb:5:1: C: Naming/VariableNumber: Use normalcase for symbol numbers.\n\n612 files inspected, 6 offenses detected, 3 offenses auto-correctable", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "pasted-context", "lang": "en"} -{"prompt": "dependency check flagged these in the rails app, pick the ones we should just bump today:\n\nName: nokogiri\nVersion: 1.16.2\nAdvisory: CVE-2026-11221\nCriticality: High\nSolution: upgrade to '>= 1.17.1'\n\nName: rack\nVersion: 3.0.9\nAdvisory: CVE-2026-10884\nCriticality: Medium\nTitle: Possible ReDoS in Rack::Request header parsing\nSolution: upgrade to '>= 3.0.11'\n\nName: image_processing\nVersion: 1.12.2\nAdvisory: GHSA-7x2f-9k1c\nCriticality: Low\nSolution: upgrade to '>= 1.13.0'\n\nVulnerabilities found!", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"} -{"prompt": "tsc is unhappy after the react 19 bump, and i think these are all the same mistake repeated:\n\nsrc/booking/SlotPicker.tsx:44:7 - error TS2322: Type '{ children: Element; ref: MutableRefObject; }' is not assignable to type 'IntrinsicAttributes & SlotGridProps'.\n Property 'ref' does not exist on type 'IntrinsicAttributes & SlotGridProps'.\n\nsrc/booking/Confirmation.tsx:19:23 - error TS2769: No overload matches this call.\n Argument of type '(e: React.FormEvent) => Promise' is not assignable to parameter of type 'FormEventHandler'.\n\nsrc/schedule/WeekGrid.tsx:88:11 - error TS2339: Property 'defaultProps' does not exist on type 'FunctionComponent'.\n\nFound 3 errors in 3 files.", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "a short note for the team explaining why we moved reminders off after_commit, for the decision log", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "our repository interfaces return `Result` in some places and throw in others; pick one and apply it, no behaviour change at the UI layer", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "the usual pre-release pass, you know the drill", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "appointment types are hardcoded as an enum in three languages: a rails enum, a kotlin sealed class, and a typescript union that's already out of date. how would you like to see this owned in one place? tell me the approach and then do the rails side", "purpose": "planning", "secondary": "refactor", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "we keep telling customers that appointment data syncs \"in near real time\" and i genuinely don't know if that's true anymore given the worker changes. read the sync path, work out what the actual guarantees are — latency, ordering, what happens on conflict — and write the honest version for the docs site, including the caveats we'd rather not advertise", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "a migration note for integrators about the v2 availability response shape, they need to know about the `meta.timezone` field", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "our CI runs the android lint task twice, once in the check job and once in the release job, drop one", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "the compose theme file came from a contractor and i've been told it's \"basically standard\" three times by people who haven't opened it. i'd like an actual assessment against how material 3 expects to be set up, particularly the dynamic colour branch and the status bar side effect, before i add a dark palette on top of it", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "we owe the partner an eligibility-check endpoint on our side by the end of the month: they call us with a patient reference and a payer id, we look up the patient, hit their sandbox, cache the answer for an hour, and return a normalised status. rate limit is 5 rps on their side and they penalise us for exceeding it", "purpose": "backendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "appointment durations over 4 hours render as a block with no end time, clamp it or show the end explicitly", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "config drift between the two staging clinics, one of them sends reminders at the wrong hour:\n\n# clinic 4412 (settings.yml)\nreminder_lead_hours: 24\nreminder_send_window: \"08:00-20:00\"\ntimezone: \"America/Santiago\"\nsms_enabled: true\nemail_enabled: true\nwaitlist_offer_window_minutes: 120\ndouble_booking_allowed: false\nslot_minutes: 30\n\n# clinic 4419 (settings.yml)\nreminder_lead_hours: 24\nreminder_send_window: \"08:00-20:00\"\ntimezone: \"UTC\"\nsms_enabled: true\nemail_enabled: false\nwaitlist_offer_window_minutes: 120\ndouble_booking_allowed: false\nslot_minutes: 15\n\n# production template both were cloned from\nreminder_lead_hours: 24\nreminder_send_window: \"08:00-20:00\"\ntimezone: null # must be set per clinic on creation\nsms_enabled: true\nemail_enabled: true\nwaitlist_offer_window_minutes: 120\ndouble_booking_allowed: false\nslot_minutes: 30\n\nboth were meant to be copies of that template and neither matches it", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "pasted-context", "lang": "en"} -{"prompt": "unity throws this every time the level loads and it's just noise in the console but it's hiding real errors:\n\nAssets/Scripts/UI/HUDController.cs(41,17): warning CS0618: 'Object.FindObjectOfType()' is obsolete: 'Object.FindObjectOfType has been deprecated. Use Object.FindFirstObjectByType instead or if finding any instance is acceptable the faster Object.FindAnyObjectByType'\nAssets/Scripts/WaveDirector.cs(88,9): warning CS0618: same\nAssets/Scripts/Audio/MusicManager.cs(22,13): warning CS0618: same\nAssets/Scripts/Save/SaveSystem.cs(112,21): warning CS0672: 'SaveSystem.Serialize(Stream)' overrides obsolete member\n\n41 warnings total, 12 of them this one", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "pasted-context", "lang": "en"} -{"prompt": "esta función se repite en tres pantallas casi igual. quiero una sola versión, sin cambiar el comportamiento:\n\n// SlotPicker.tsx\nconst isBookable = (s: Slot) =>\n !s.taken && s.startsAt > new Date() && !s.blocked && s.providerId === selectedProvider\n\n// WeekGrid.tsx\nfunction bookable(slot) {\n if (slot.taken) return false\n if (slot.blocked) return false\n if (new Date(slot.startsAt) <= new Date()) return false\n return !provider || slot.providerId === provider\n}\n\n// WaitlistSheet.tsx\nconst canOffer = (slot: Slot, providerId?: string) =>\n [!slot.taken, !slot.blocked, +new Date(slot.startsAt) > Date.now(),\n providerId ? slot.providerId === providerId : true].every(Boolean)", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "es"} -{"prompt": "this composable has grown a fifth responsibility and i want it split without changing a pixel:\n\n@Composable\nfun ScheduleScreen(vm: ScheduleViewModel = hiltViewModel()) {\n val state by vm.state.collectAsStateWithLifecycle()\n val snackbar = remember { SnackbarHostState() }\n LaunchedEffect(state.error) { state.error?.let { snackbar.showSnackbar(it) } }\n LaunchedEffect(Unit) { vm.trackScreenView() }\n Scaffold(\n topBar = { /* 40 lines of week picker, provider filter and overflow menu */ },\n snackbarHost = { SnackbarHost(snackbar) },\n floatingActionButton = { /* 20 lines with three conditional states */ },\n ) { padding ->\n when {\n state.loading -> ShimmerGrid(padding)\n state.days.isEmpty() -> EmptyDay(padding, onRefresh = vm::refresh)\n else -> /* 90 lines of day columns, drag-to-reschedule and overlap layout */\n }\n }\n}", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "service object that grew organically. same behaviour, better seams, and it needs to stay callable from the controller exactly as it is:\n\nclass Appointments::Reschedule\n def initialize(appointment, new_slot, actor:, notify: true, skip_validation: false)\n @appointment = appointment; @new_slot = new_slot; @actor = actor\n @notify = notify; @skip_validation = skip_validation\n end\n\n def call\n raise OutsideClinicHours unless @skip_validation || within_hours?\n raise SlotTaken if Appointment.overlapping(@appointment.clinic_id, @new_slot.range).where.not(id: @appointment.id).exists?\n ActiveRecord::Base.transaction do\n @appointment.update!(starts_at: @new_slot.starts_at, ends_at: @new_slot.ends_at)\n AuditLog.create!(actor: @actor, action: \"reschedule\", subject: @appointment)\n CalendarSyncJob.perform_later(@appointment.id)\n PatientMailer.rescheduled(@appointment).deliver_later if @notify\n SmsSender.new(@appointment.patient).rescheduled(@appointment) if @notify && sms?\n end\n @appointment\n end\nend", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "four scripts in the unity project all reach for the player the same way. i want one accessor and no behaviour change:\n\n// WaveDirector.cs\nvar player = GameObject.FindWithTag(\"Player\").GetComponent();\n\n// HomingBullet.cs\nvar player = GameObject.Find(\"Player\").transform;\n\n// HUDController.cs\nPlayerController player = FindObjectOfType();\n\n// SaveSystem.cs\nvar player = GameObject.FindGameObjectsWithTag(\"Player\").FirstOrDefault()?.GetComponent();\n\nall four are called from Update or from OnEnable, some of them every frame", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "test suite has this shape repeated 60-odd times and it's why nobody adds tests:\n\nRSpec.describe Appointments::Availability do\n let(:clinic) { create(:clinic, timezone: \"America/New_York\") }\n let(:provider) { create(:provider, clinic: clinic) }\n let!(:hours) { create(:clinic_hours, clinic: clinic, weekday: 1, opens_at: \"09:00\", closes_at: \"17:00\") }\n let(:range) { Date.new(2026, 8, 3)..Date.new(2026, 8, 3) }\n\n before do\n travel_to Time.zone.parse(\"2026-08-01 08:00\")\n allow(FeatureFlags).to receive(:enabled?).with(:waitlist).and_return(false)\n end\n\n after { travel_back }\n # ... 8 examples\nend\n\nsame five let blocks, same travel_to, same flag stub, in every scheduling spec", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "navigation in the app is half compose-navigation and half fragments, this is the current graph plus the leftovers:\n\nNavHost(navController, startDestination = \"schedule\") {\n composable(\"schedule\") { ScheduleScreen() }\n composable(\"booking/{slotId}\") { BookingScreen(it.arguments?.getString(\"slotId\")!!) }\n composable(\"patient/{id}\") { PatientScreen(it.arguments?.getString(\"id\")!!) }\n activity(\"legacy_settings\") { activityClass = SettingsActivity::class }\n}\n\n// still around\nclass PatientListFragment : Fragment() // reached from SettingsActivity\nclass ProviderPickerFragment : DialogFragment() // shown from ScheduleScreen via FragmentManager\nclass OnboardingActivity : AppCompatActivity() // launched from MainActivity.onCreate\n\nthe hybrid is why back handling is inconsistent. same destinations, one mechanism", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "un fichier de constantes qui a mal vieilli, je veux le réorganiser sans rien casser :\n\n// constants.ts\nexport const SLOT_MINUTES = 30\nexport const MAX_RANGE_DAYS = 62\nexport const API_BASE = process.env.NEXT_PUBLIC_API ?? \"https://api.clinicly.io\"\nexport const COLORS = { booked: \"#2f6fed\", blocked: \"#9aa0a6\", free: \"#ffffff\" }\nexport const REMINDER_LEAD_HOURS = 24\nexport const WAITLIST_WINDOW_MIN = 120\nexport const FEATURE_WAITLIST = true\nexport const DATE_FMT = \"yyyy-MM-dd\"\nexport const TZ_FALLBACK = \"UTC\"\nexport const SUPPORT_EMAIL = \"help@clinicly.io\"\nexport const RETRY_DELAYS = [1000, 2000, 4000, 8000]\nexport const LEGACY_SLOT_MINUTES = 15 // still used by the old week grid\n\nimporté par 41 fichiers", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "pasted-context", "lang": "fr"} -{"prompt": "discovery notes from the clinic visits last week. i need this turned into a roadmap with phases, not a feature list:\n\n- front desk staff use paper for the waitlist because the digital one takes too many taps\n- three of five clinics double-book deliberately for no-show buffer; our model forbids it\n- providers want to see their own day on a phone, receptionists want the whole clinic on a monitor\n- nobody uses the reporting screen; two clinics export to excel weekly instead\n- the biggest complaint is that cancelling requires four confirmations\n- one clinic runs two locations from one account and it half-works\n- insurance eligibility check is done outside our system entirely, on a separate portal", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "leadership handed down this constraint set for the mobile rewrite and i need a realistic sequencing before we commit to dates:\n\n- android and ios must ship the same features at the same time from Q4\n- the current android app is kotlin/compose, ios is a webview wrapper nobody maintains\n- team is four android engineers, one ios contractor starting in september\n- offline support is non-negotiable for both, clinics have bad wifi\n- the design system exists in figma but only android components are built\n- there is a hard deadline: a customer conference in march where both must demo\n- we cannot stop shipping android features in the meantime", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "game's save system is about to become a problem and i'd rather design now than patch later. current state:\n\n- SaveSystem.cs writes a JSON blob to Application.persistentDataPath every checkpoint\n- no versioning; loading an old save from before the wave rework silently zeroes progress\n- cloud saves via steam are on the roadmap for the 1.0 release\n- players have already reported losing runs when the game is force-quit mid-write\n- we want a run history screen eventually, which means multiple saves, not one blob\n\nwhat should the shape of this be, and what's the migration path for saves already in the wild", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "compliance ticket landed and i don't want to start coding before we agree the shape:\n\nCOMP-118 — Audit trail for patient record access\nEvery read of a patient record must be recorded: who, when, which record, from which client, and the stated reason where one is required. Records must be queryable by patient (for subject access requests) and by user (for internal investigations). Retention six years, tamper-evident. Must not measurably slow the schedule screen, which reads dozens of patient summaries per page load. Applies to API, admin panel and the mobile apps. Existing access is not backfilled.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "figma redlines for the new day column, build it in compose:\n\nDay column (phone, 360dp)\n- Header: weekday abbrev (labelMedium) over day number (headlineSmall). Today: number in a 32dp filled circle, onPrimary text.\n- Hour rows 64dp tall, 1dp divider at 12% onSurface. Half-hour: dotted divider, 6% opacity.\n- Appointment block: 8dp corner, 4dp inset from the column edges, 3dp leading accent bar coloured by appointment type. Title bodyMedium truncated to one line; patient name bodySmall, 70% alpha.\n- Overlaps: split the column evenly, 2dp gutter, max three side by side, then \"+N\" chip on the third.\n- Now line: 2dp accent, dot at the leading edge, only shown for today.\n- Drag to reschedule: block lifts 4dp with shadow, snaps to 15-minute steps, target row highlighted at 8% accent.\n- Empty state: centred \"Nothing booked\" bodyMedium at 50% alpha.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "ticket with the designer's notes attached, the waitlist sheet on web:\n\nWaitlist sheet (desktop modal, 480px)\n- Title \"Join the waitlist\" (20px semibold), subtitle with the chosen day in long form.\n- Provider select: our existing Select component, defaults to \"Any provider\", shows avatars.\n- Time-of-day preference: three toggle chips (Morning / Afternoon / Any), single select, \"Any\" default.\n- Contact preference: radio group, SMS / Email, prefilled from the patient record, with the masked contact shown next to each.\n- Footnote in 12px muted: \"We'll hold your spot for 2 hours once we offer it.\"\n- Primary \"Join waitlist\", secondary \"Cancel\". Primary disabled while submitting, spinner inside the button.\n- On success the modal is replaced in place by a confirmation state with a checkmark, no navigation.\n- Errors render above the buttons in a red inline alert, never a toast.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "这是设计稿标注，帮我把预约确认页写出来（React + Tailwind）：\n\n确认页（移动端 375px）\n- 顶部：诊所名称 16px 中等字重，下面是地址 13px 灰色，右侧是地图图标按钮 40x40。\n- 主卡片：圆角 12px，1px 边框，内边距 16px。第一行日期 20px 半粗，第二行时间段 15px。\n- 医生一行：32px 头像 + 姓名 + 科室，中间用 8px 间距。\n- 提醒开关：默认开启，副标题写「就诊前 24 小时短信提醒」。\n- 底部按钮：主按钮「确认预约」占满宽度 48px 高，次要按钮「取消」文字按钮。\n- 加载中：主按钮内显示 spinner，其余内容保持不动。\n- 出错时在按钮上方显示红色提示条，不要弹窗。", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "zh"} -{"prompt": "spec from the integration partner, build our side of it:\n\nPOST /v2/webhooks/eligibility\n headers: X-Partner-Signature (HMAC-SHA256 of the raw body, secret per partner), X-Partner-Id\n body: { request_id, patient_ref, payer_id, status: \"active\"|\"inactive\"|\"unknown\", copay_cents?, checked_at }\n we must respond 200 within 3 seconds or they retry with the same request_id for 24 hours\n duplicate request_id must be a no-op that still returns 200\n unknown patient_ref: respond 200 and record it, do not 404 (they treat 4xx as a hard failure and disable the hook)\n signature mismatch: 401, and we should alert\n they send roughly 40k of these a day, bursty around 06:00 clinic-local", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "reminder lead time to 48h", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "core", "lang": "en"} -{"prompt": "versionCode wasn't bumped for the hotfix", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "core", "lang": "en"} -{"prompt": "\"appointement\" in the confirmation email", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "core", "lang": "en"} -{"prompt": "proguard rule for the analytics SDK", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "strip the debug toast from BookingScreen", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "boundary", "lang": "en"} -{"prompt": "sentry DSN is still the staging one", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "boundary", "lang": "en"} -{"prompt": "delete the dead `LEGACY_SLOT_MINUTES`", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "boundary", "lang": "en"} -{"prompt": "el copy del botón dice «Reservar», debería ser «Confirmar»", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "boundary", "lang": "es"} -{"prompt": "nokogiri to 1.17.1 please", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "boundary", "lang": "en"} -{"prompt": "turn off dynamicColor for now", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "boundary", "lang": "en"} -{"prompt": "today's date needs a filled circle", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "pull-to-refresh on the day view", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "provider avatars in the week header", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "minimap clips on ultrawide", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "empty day needs an illustration", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "ボタンのタップ領域が小さすぎます", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "ja"} -{"prompt": "cancel confirmation should be one tap", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "slot chips wrap badly at 320dp", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "now-line should be accent, not red", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "boundary", "lang": "en"} -{"prompt": "HUD scale is wrong on deck", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "`ApptSvc` should read `AppointmentService`", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "lift the week picker out of ScheduleScreen", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "die Konstanten nach Bereichen gruppieren", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "de"} -{"prompt": "a nightly job that flags appointments whose provider no longer works at the clinic, so front desk can reassign them before the patient turns up", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "our staging data is a six-month-old production dump with names scrambled, which is why timezone bugs never show up before release. what should the test data story actually be", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "the changelog for the android app has been \"bug fixes and improvements\" for six releases, which is embarrassing given how much has actually changed. go through the commits since 3.0, write proper release notes for each version, and while you're in there fix the two entries in the existing changelog that describe features we cut", "purpose": "writing", "secondary": "quickFix", "mixed": true, "difficulty": 0.4, "slice": "mixed", "lang": "en"} -{"prompt": "collapse the two slot builders", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "`starts_at` naming, consistent everywhere", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "shared rspec context for scheduling specs", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "one player accessor for all scripts", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "inline `bookable`, it's used once", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "play store release notes, friendly tone", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "changelog entry for the waitlist", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "kurze Doku für den Reminder-Job", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "de"} -{"prompt": "summarise `Availability#build` for the wiki", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "PR body for the ANR fix", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "where does `skip_validation` come from?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "¿qué hace exactamente `SyncCoordinator.pull`?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "es"} -{"prompt": "which of these two helpers is safer?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "walk me through the offer job", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "any reason `after_commit` fires twice here?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "reminders went out an hour early", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "week view flickers on day change", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "booking twice creates two appointments", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "le calendrier reste vide après le login", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "fr"} -{"prompt": "soft-delete on appointments, rails side", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "plan the audit trail, then build phase one", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "scope the ios rewrite, then start the shell", "purpose": "planning", "secondary": "frontendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "same as yesterday", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "clean this up", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "vague-eval", "lang": "en"} -{"prompt": "go ahead with the waitlist", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "nicer", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "vague-eval", "lang": "en"} -{"prompt": "onboarding, but properly this time", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "weiter wie besprochen", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "de"} -{"prompt": "you know what to do", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "vague-eval", "lang": "en"} -{"prompt": "できるところまでお願いします", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "ja"} -{"prompt": "round two on the sync", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "make the wave feel meaner", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "do the needful on scheduling", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "tidy the theme file", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "vague-eval", "lang": "en"} -{"prompt": "o de sempre, mas para a agenda", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "pt"} -{"prompt": "clinics with two locations are running on one account and it half works today: shared provider list, shared patient records, but the schedule screen can only show one location's rooms at a time and reminders always use the first location's address. before we build multi-location properly i want to know whether that's a data model change or a permissions change, and what it does to every clinic already on the platform", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "insurance eligibility is checked on a separate portal today and front desk staff retype the result into a note. bringing it in-house means a partner API, PHI leaving our boundary in a new direction, and a support burden when the payer is down. i'd like the options laid out — full integration, deep link with prefill, or nothing — with what each costs us over a year", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "game needs a difficulty curve that isn't just hp multipliers and i keep going back and forth. we have wave composition, enemy stats, spawn rate, arena hazards and drop rates as knobs, plus a run-length target of about 25 minutes. sketch out how you'd structure the tuning so a designer can iterate without touching code, and what we'd need to log to know whether it's working", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "hospital group wants us on their infrastructure rather than our cloud, which we have never done. that means a deployment story, a licence story, an upgrade story and a support story, none of which exist. i want the shape of what we'd have to build and what we'd have to say no to, before sales promises anything in the next call", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "boundary", "lang": "en"} -{"prompt": "clinic staff turnover is high and every new receptionist gets trained by the last one, which is why nobody knows about half the features. i'd like a proper training guide: the daily workflow start to finish, the five things that go wrong most often and how to fix them, and a one-page cheat sheet they can print and stick on the monitor", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "android release process lives in one engineer's head: which branch, when to bump versionCode, the staged rollout percentages, when to promote, what to do when crashlytics spikes mid-rollout, and how to halt. write it down as a runbook that someone else could follow on a wednesday afternoon without asking them anything", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "steam page copy is three sentences and reads like a placeholder because it is one. the game is a roguelike with a clinic aesthetic, run-based, 25-minute runs, deck-of-treatments mechanic. write the store description, the short blurb, and the five bullet features, in a voice that isn't every other roguelike page", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "reading `Appointments::Availability` end to end took me an hour and i still couldn't tell you why the 62-day cap exists or what the `duration` parameter really does to slot boundaries. go through it and tell me what it does, where the surprises are, and which behaviours look intentional versus accidental", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "on-call docs claim the reminder job is idempotent and safe to re-run, and i want that verified rather than assumed before someone re-runs it during an incident at 3am. trace it properly: what it reads, what it writes, what happens if two copies run at once, and whether a patient could get two texts", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "schedule screen makes about forty network calls when you switch weeks quickly, one per day column, and half of them are cancelled mid-flight. the data layer is supposed to coalesce these. same behaviour on screen afterwards, but i want the fetching restructured so it's one request per week and cancellation is handled in one place", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "rails app has thirteen service objects under `app/services/appointments/` and four of them are wrappers around another one, which nobody can see without reading all thirteen. i'd like the layer flattened into something honest, same public entry points from the controllers, same behaviour, fewer indirections", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "every screen in the app builds its own retrofit call, its own loading boolean and its own error string, so the same three-state dance is written 20 times with subtle differences. i want one pattern applied everywhere without changing what any screen looks like or how it behaves offline", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "biggest source of paper cuts is that the confirmation modal, the sheet on mobile and the toast all render appointment times through different formatting helpers, so they disagree about am/pm and timezone suffixes. one helper, all three call sites, and the output should match the modal's current format", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "gradle config for the android app has accumulated flags from three years of stack overflow answers and nobody knows which are load-bearing. tidy it up, keep the build producing an identical APK, and tell me which flags you removed and why", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "before the multi-location work starts i want the current single-location assumptions written down — every place the code assumes one address, one timezone, one set of rooms — and then a phased plan for undoing them. the audit first, the plan second, both in one document if that reads better", "purpose": "planning", "secondary": "review", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "waitlist feature needs a design before code, but it also needs the offer expiry job soon or QA can't test anything. give me the design for the whole flow, then implement just the expiry worker against it so the rest can land behind it", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "das Sync-Verhalten der App ist weder dokumentiert noch besonders durchdacht: Push vor Pull, Konflikte gewinnt immer der Server, verworfene Änderungen sieht der Nutzer nie. Ich hätte gern erst ein Konzept, wie es aussehen sollte, und danach die Umsetzung des Konfliktfalls im Repository", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "de"} -{"prompt": "nobody outside the team understands what the sync worker does, and the parts i understand look wrong. write the explainer for the rest of engineering, and while you're in there work out whether a discarded local edit can ever take a patient's cancellation with it", "purpose": "writing", "secondary": "debugging", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "support has asked for a page explaining why a reminder might not arrive, which needs to cover the timezone setting, the send window, the twilio number status and the do-not-disturb flag on the patient record. write that, and separately confirm from the code that those four are actually the only reasons", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "audit-trail schema we sketched last week never made it into the repo, and the ticket is now in this sprint. put the design into `docs/adr/` properly, then stand up the migration and the write path for API reads only — the admin panel can follow later", "purpose": "writing", "secondary": "backendImpl", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "`SyncCoordinator` and `AppointmentRepository` overlap so much that i can never remember which one owns the pending-edit queue. merge the responsibilities sensibly, and afterwards write the class-level docs so the boundary is obvious to whoever touches it next", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "there are two spawn systems in the unity project, the jam-era one and the new director, and both are wired into the boot scene. delete the dead one carefully, and note in the design doc which behaviours we deliberately dropped so the designers aren't surprised", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "scheduling API returns 200 with an empty array when a clinic's timezone is unset, which is how we shipped a 24-minute outage. work out every endpoint with that failure mode, then make them fail loudly instead", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "patient search is a plain LIKE query and takes two seconds on the bigger clinics. i want fuzzy matching on name and date of birth, with the exact matches ranked first", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "recurring provider blocks — lunch, admin time, theatre lists — need to exist as real records rather than one-off appointments, with an end date and the ability to skip a single occurrence", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "an internal endpoint that returns a clinic's next 30 days of capacity as a single payload, for the reporting screen. cache it for five minutes, key on clinic and provider filter", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "run summary screen at the end of a game — time survived, waves cleared, treatments used, a graph of damage over time, and a share button that copies a text summary", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "drag-to-reschedule on the web week grid, snapping to 15 minutes, with the original position ghosted while dragging", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "toast messages stack up and cover the FAB when sync retries, needs a proper snackbar host with a queue", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "boss health bar overlaps the wave banner at 21:9, and both are anchored to the top centre", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "what's the actual difference between `pull(null)` and `pull(lastSync)` in terms of what the server sends back", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "opinions on the `after_commit` calendar sync in the appointment model — is that going to bite us under load?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "is there anything in the waitlist offer flow that could offer the same slot to two patients at once", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "could someone explain the difference between our `Slot` and `Availability` models to me, they seem to overlap completely", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "someone needs to explain, in writing, what our appointment status transitions are — the code has six statuses and the docs mention four", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "give me a plain-english account of what the eligibility webhook handler does with a duplicate request id", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "how does the save system decide a run is finished — i can see two places that write the final state", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "docs/scheduling.md describes the availability algorithm from two rewrites ago, bring it in line with the code", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "kdoc on our public data classes is copy-pasted from the field names and adds nothing, make it actually useful", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "`ClinicHours#slots_for` and `Availability#build` have grown into each other; separate the concerns without changing what the endpoint returns", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "pull the twilio and sendgrid calls behind one notification port so tests stop hitting HTTP stubs directly", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "enemy scripts each hold their own copy of the tuning numbers, move them to scriptable objects with the same values", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "rename the `booking` package to `appointments` across the android app, it's confused with the web team's `booking` for two years now", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "three components import `formatSlotTime` from three different files that all re-export the same function, collapse the chain", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "新しい医師を追加すると、既存の予約の色が全部変わってしまいます。色の割り当てを固定にできますか", "purpose": "quickFix", "secondary": "frontendImpl", "mixed": true, "difficulty": 0.35, "slice": "mixed", "lang": "ja"} -{"prompt": "deep links from a reminder open the app but land on the schedule root instead of the appointment, and it's been like that since the navigation change", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "we need a position on offline conflict resolution before the ios work starts, because copying android's silent server-wins would be a mistake to repeat twice", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "appointment reminders, waitlist offers and calendar sync all send messages, and each one built its own template handling. what would a single messaging layer look like here", "purpose": "planning", "secondary": "refactor", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "whatever's next on the schedule board", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "mobile confirmation sheet shows only the time right now, which is useless when a patient has appointments at two of the clinic's sites. it needs the clinic name, the street address under it, a map button that opens the native maps app, and the provider's name — without making the sheet taller than the detent it opens at", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "setting up a dev environment here takes a full day because the instructions are spread across a wiki page, a pinned slack message and one engineer's memory. we need one document: prerequisites, the database seed step, how to point the app at the local API, how to get test twilio credentials, and the three things that always go wrong on a new mac", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "internally nobody can describe how appointment sync works without drawing on a whiteboard, so it gets explained badly and differently every time. one document, covering the pull path, the push path, what the revision numbers mean, when the worker gives up, and what the user sees at each stage — diagrams are welcome but the prose has to stand alone", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "a patient who moved from Madrid to Mexico City still gets reminders on Spanish time as far as support can tell, and i want to know whether that's the code or the data. the reminder job reads the clinic timezone, not the patient's, so on paper it shouldn't matter — but the patient record has a timezone column that something must be using", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "sidekiq queue names drifted from the job class names over about two years, so `ReminderJob` runs on `default`, `CalendarSyncJob` runs on `mailers` of all things, and two jobs share a queue that's meant to be low priority. line them up with the class names, keep the priority weights we have today, and don't leave jobs stranded on the old queues during the deploy", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "providers keep asking for a view that's just their own day: their appointments only, defaulting to today, remembering the last provider they picked between launches, and usable one-handed while walking between rooms. it should open instantly from the local cache and refresh quietly behind that, with no spinner unless there's genuinely nothing cached", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "reporting is the screen clinics complain about most and also the one we understand least — five joins per row, no aggregates, and now they want twelve-month ranges. work out what it's really doing today and where the time goes, then propose whether we need a read model, a materialised view, or just better indexes. i want the analysis and the recommendation, not an implementation", "purpose": "planning", "secondary": "review", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "compose multiplatform versus two native codebases is the decision blocking our ios plan, and i'd rather see it reasoned through than argued about in standup. weigh it for our situation — four android engineers, one ios contractor, offline-first requirements, a design system that only exists for android — then draft the ADR whichever way it lands", "purpose": "planning", "secondary": "writing", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "bookings made close to midnight land on the wrong day for the provider but the right day for the patient, at least in Chile and probably anywhere with a negative offset. find out where the date gets derived from the wrong clock, and once you know, add the regression tests that would have caught it — parameterised over a few nasty timezones", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "i'd like someone to read the eligibility webhook handler with fresh eyes — signature check, replay handling, what happens when the patient reference is unknown — and tell me whether it matches the partner's spec. if the retry behaviour is as wrong as i suspect, fix the handler as part of the same pass", "purpose": "review", "secondary": "backendImpl", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "our appointment status transitions are documented as four states and implemented as six, and support has built workarounds around the undocumented ones. work out what the real state machine is from the code, then write the reference page that we should have had, flagging any transition that looks accidental", "purpose": "review", "secondary": "writing", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "`app/services/appointments/` has thirteen classes where four would do, and half of them are one-line wrappers. consolidate the layer so the controllers call the same entry points they call today, then update the service-layer section of the architecture doc, which describes a structure we abandoned last year", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "the slot picker fails almost every accessibility check we run — no content descriptions on the chips, 32dp touch targets, and a focus order that jumps between columns. bring it up to standard, and take a screenshot pass afterwards so i can put the before and after in the procurement questionnaire", "purpose": "frontendImpl", "secondary": "writing", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} +{"prompt":"Incident timeline — INC-42142\n\n08:02 deploy BorealNimbusFormFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current BorealNimbusFormFlow 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":"Release engineering needs a BorealFlintTimelineService 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":"Before we approve BorealGarnetModalStore, assess whether lost focus when the drawer animation finishes 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.5,"slice":"boundary","lang":"en"} +{"prompt":"PM needs a concise migration note for BorealOpalRouterService, 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":"BorealBirchMigratorCoordinator: handle the lingering thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Set BorealSlateEditorService's port to 8081","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Opal: # projects/boreal/services/ledger/replay.go\n[worker.borealravensessionflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.borealravensessionflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.borealravensessionflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.BorealRavenSessionFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-42143\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/boreal/services/ledger/replay.go and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Release verification found a single stale BorealIrisBatchService value; the cause, desired value, and affected assertion are already agreed. 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- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current Kafka operational envelope\n\nThe relevant code crosses computer vision, React, PostgreSQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Dedupe BorealOrbitSyncService's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Documente le contrat BorealRainfallDBStore","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"fr"} +{"prompt":"Why does BorealLumenChartService's Kafka worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Give BorealCraneWorkspaceService a loading skeleton","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Prism: // projects/boreal/Sources/App/SessionStore.swift\nfinal class BorealFrostPanelFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 BorealFrostPanelFlow'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":"BorealSummitProxyService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current Cloudflare Workers operational envelope\n\nThe relevant code crosses computer vision, React, PostgreSQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Quartz: // projects/boreal/crates/index/src/segment.rs\nfinal class BorealJuniperCLIFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 BorealJuniperCLIFlow; 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":"BorealFlintTimelineCoordinator: sort out the rough edge","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Ticket OPS-42115: retire the legacy replay path for BorealBeaconStoreFlow\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 BorealBeaconStoreFlow 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":"BorealJuniperCLICoordinator needs a paired pass: produce a consumer guide for BorealJuniperCLICoordinator, plus correct the known stale timeout beside it. Use projects/boreal/pkg/cache/lease.rs as the source of truth, preserve the Cloudflare Workers contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Raven: Incident timeline — INC-42136\n\n08:02 deploy BorealOspreyJobFlow 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 BorealOspreyJobFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"BorealQuartzPlayerCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"BorealMicaProfileCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Sable: Release verification found a single stale BorealAmberFilterStore value; the cause, desired value, and affected assertion are already agreed. 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- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current Kotlin coroutines operational envelope\n\nThe relevant code crosses computer vision, React, PostgreSQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'BorealEchoRegistryCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[BorealEchoRegistryCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/boreal/web/components/FilterDrawer.vue:144: error: -[BorealEchoRegistryCoordinatorTests 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 '-[BorealEchoRegistryCoordinatorTests 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 を維持し、根拠と判断を明確にしてください。 Use the UI evidence to complete BorealEchoRegistryCoordinator'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":"Introduce a durable deduplication key for BorealNimbusFormService 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":"Tide: projects/boreal/engine/render/atlas.cpp now contains BorealWillowCodecStore'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.4,"slice":"core","lang":"en"} +{"prompt":"Umbra: Incident timeline — INC-42140\n\n08:02 deploy BorealGarnetModalFlow 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 BorealGarnetModalFlow 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":"Give BorealMoonlitSDKStore'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.5,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'BorealKiteSchedulerCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[BorealKiteSchedulerCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/boreal/db/migrations/20260730_events.sql:144: error: -[BorealKiteSchedulerCoordinatorTests 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 '-[BorealKiteSchedulerCoordinatorTests 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\nReconstruct the BorealKiteSchedulerCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Vela: The destination for BorealWrenExportStore is broadly agreed; the missing piece is a reversible route from projects/boreal/workers/thumbnail/consumer.ex to that target. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealWrenExportStore\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Could the reasoning behind BorealDriftConsoleStore's Cloudflare Workers choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Walk through BorealFernSnapshotStore's atlas.cpp","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Compare the old and new BorealSpruceDaemonStore 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.6,"slice":"core","lang":"en"} +{"prompt":"Could the reasoning behind BorealCinderAuthStore's GraphQL choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-42157: retire the legacy replay path for BorealVelaDrawerCoordinator\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 BorealVelaDrawerCoordinator 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":"diff --git a/projects/boreal/ml/pipeline/features.py b/projects/boreal/ml/pipeline/features.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/boreal/ml/pipeline/features.py\n+++ b/projects/boreal/ml/pipeline/features.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 BorealNovaPickerFlow'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":"A previously stable test around BorealBirchMigratorService now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Dokumentiere BorealQuartzPlayerStore kurz","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"de"} +{"prompt":"For BorealHarborIndexCoordinator, separate BorealHarborIndexCoordinator's policy from transport without behavior changes; once that is complete, capture the contract and rollback note for consumers. Work from projects/boreal/internal/auth/refresh.go, stay with Kotlin coroutines, and leave generated files and vendored code alone. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Is BorealBeaconStoreService safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"On compact widths, BorealBasilRunnerFlow'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":"Two asks around BorealCedarPolicyCoordinator: (1) find the unknown cause of two validators with subtly different error strings; (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":"debugging","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"BorealSableParserService 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":"projects/boreal/lib/codec/frame.cc has grown through several launches, and BorealIrisBatchStore now mixes policy, transport, persistence, and metrics in one place. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- leave generated files and vendored code alone\n- stay compatible with the existing Kafka deployment\n- keep the work scoped to BorealIrisBatchStore and its direct tests\n\nSeveral teams work in this computer vision, React, PostgreSQL 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":"BorealSpruceDaemonCoordinator: could this be clearer","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"BorealSableParserCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","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_42122'\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_42122'::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 BorealFernSnapshotFlow 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":"BorealNimbusFormCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"BorealAcornWidgetCoordinator: correct, then assess","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"BorealSlateEditorCoordinator: sequence, then polish","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"BorealPrismCacheService's metric is misspelled as succesful_total in one declaration. Correct that literal and its exact test expectation, without renaming anything else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Move BorealSummitProxyFlow'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.5,"slice":"core","lang":"en"} +{"prompt":"Before touching projects/boreal/db/migrations/20260730_events.sql, 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":"The BorealDeltaCanvasStore empty state in projects/boreal/config/staging.toml needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current BorealEmberRelayService design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealEmberRelayService\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"On compact widths, BorealCinderAuthService'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":"BorealRainfallDBCoordinator needs a paired pass: separate BorealRainfallDBCoordinator's policy from transport without behavior changes, plus give the existing implementation a read-only safety pass. Use projects/boreal/ui/settings/PrivacyPane.tsx as the source of truth, preserve the Kafka contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current BorealDriftConsoleService design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealDriftConsoleService\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"This should remain a deliberately small patch: BorealMarbleTokenService has one known configuration mistake in projects/boreal/infra/modules/edge/main.tf, not an open-ended failure investigation. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- leave generated files and vendored code alone\n- stay compatible with the existing Kotlin coroutines deployment\n- keep the work scoped to BorealMarbleTokenService and its direct tests\n\nSeveral teams work in this computer vision, React, PostgreSQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-42128\n\n08:02 deploy BorealHarborIndexFlow 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 BorealHarborIndexFlow 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":"diff --git a/projects/boreal/cmd/exporter/main.py b/projects/boreal/cmd/exporter/main.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/boreal/cmd/exporter/main.py\n+++ b/projects/boreal/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\nRestructure BorealPineMetricsFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"In projects/boreal/app/src/main/SyncWorker.kt hat BorealAtlasSearchService ein sporadisches Problem im GraphQL-Ablauf. Vervollständige Responsive Layout, Empty- und Retry-State, Tastaturfokus, Dark Mode und Reduced Motion.\n\nRandbedingungen:\n- GraphQL weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf BorealAtlasSearchService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um BorealAtlasSearchService mit GraphQL kompatibel.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} +{"prompt":"Split BorealAsterWebhookStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"The name pendingAck means two different things across BorealMarbleTokenFlow's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"# projects/boreal/packages/api/openapi.yaml\n[worker.borealquartzplayerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.borealquartzplayerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.borealquartzplayerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.BorealQuartzPlayerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-42119\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/boreal/packages/api/openapi.yaml and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Dedupe BorealFrostPanelStore's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Stream BorealFernSnapshotService's audit events","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Does BorealOspreyJobStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists? I want your judgment and walkthrough, not new documentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"PM needs a concise migration note for BorealFlintTimelineStore, 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":"BorealOrbitSyncCoordinator is blocking the next release because cancellation being swallowed at the repository boundary. I need two concrete outcomes from a single pass: assess ownership and failure handling in projects/boreal/crates/index/src/segment.rs, and capture the contract and rollback note for consumers. Use the existing Cloudflare Workers conventions in projects/boreal/crates/index/src/segment.rs; 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":"review","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Ticket OPS-42114: retire the legacy replay path for BorealOrbitSyncFlow\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 BorealOrbitSyncFlow 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":"BorealOspreyJobCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Compare the old and new BorealVelaDrawerStore 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":"Remove BorealFrostPanelService's stray comma","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"BorealGarnetModalCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Willow: The BorealMicaProfileStore surface in projects/boreal/ml/pipeline/features.py is stable now; turn its edge cases into API documentation with one successful example and one cancellation example.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Xylem: projects/boreal/web/components/FilterDrawer.vue 里的 BorealRavenSessionStore 最近在 Kotlin coroutines 流程中出现间歇性问题。 请完成 responsive layout、空状态、retry、键盘焦点、dark mode 和 reduced motion。\n\n约束：\n- 继续使用 Kotlin coroutines\n- 保持兼容性和取消语义\n- 改动只限于 BorealRavenSessionStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"Two deliverables are holding up BorealBeaconStoreCoordinator. First, finish BorealBeaconStoreCoordinator's responsive empty and retry states. In the same workstream, correct the known stale timeout beside it. The relevant starting point is projects/boreal/cmd/exporter/main.py, which follows Spring Boot 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":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Yarrow: Two asks around BorealCraneWorkspaceCoordinator: (1) change BorealCraneWorkspaceCoordinator's known staging timeout from 15 to 30 seconds; (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":"quickFix","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Zephyr: Ticket OPS-42151: retire the legacy replay path for BorealEmberRelayCoordinator\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 BorealEmberRelayCoordinator 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":"Where did BorealHarborIndexService's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"thread 'tokio-runtime-worker' panicked at projects/boreal/infra/modules/edge/main.tf:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: borealbirchmigratorflow::scheduler::LeaseTask::flush\n at ./projects/boreal/infra/modules/edge/main.tf:217:18\n 4: borealbirchmigratorflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nFind the source of this BorealBirchMigratorFlow 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":"Test Suite 'BorealSpruceDaemonFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[BorealSpruceDaemonFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/boreal/config/staging.toml:144: error: -[BorealSpruceDaemonFlowTests 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 '-[BorealSpruceDaemonFlowTests 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\nDetermine why BorealSpruceDaemonFlow 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":"Before touching projects/boreal/engine/render/atlas.cpp, 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":"# CI job 42147: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: Kafka\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] BorealLumenChartFlowIntegration.replays_after_timeout ... ok\n[test] BorealLumenChartFlowIntegration.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 \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\nWire BorealLumenChartFlow'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":"Checkout: projects/boreal/src/sync/reconcile.ts now contains BorealKiteSchedulerFlow'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.4,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'BorealWrenExportFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[BorealWrenExportFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/boreal/ui/settings/PrivacyPane.tsx:144: error: -[BorealWrenExportFlowTests 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 '-[BorealWrenExportFlowTests 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 BorealWrenExportFlow'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":"Exporter: # projects/boreal/ui/settings/PrivacyPane.tsx\n[worker.borealprismcacheflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.borealprismcacheflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.borealprismcacheflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.BorealPrismCacheFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-42137\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. The intended correction is already known: change only the stale 15-second setting to 30 seconds in projects/boreal/ui/settings/PrivacyPane.tsx and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Scheduler: // projects/boreal/Sources/CLI/Commands/Doctor.swift\nfinal class BorealAsterWebhookFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 BorealAsterWebhookFlow 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":"Incident timeline — INC-42112\n\n08:02 deploy BorealIrisBatchFlow 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 BorealIrisBatchFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Ticket OPS-42129: retire the legacy replay path for BorealCopperBridgeFlow\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À partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Turn the artifact into a reversible BorealCopperBridgeFlow 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":"Outline a safer BorealCraneWorkspaceStore cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-42110: finish the compact BorealMosaicGridFlow filter experience\n\nRoute: /catalog/search\nSource: projects/boreal/Sources/CLI/Commands/Doctor.swift\nFramework: Spring Boot\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 BorealMosaicGridFlow 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":"diff --git a/projects/boreal/web/components/FilterDrawer.vue b/projects/boreal/web/components/FilterDrawer.vue\nindex 62d71aa..90f3c1e 100644\n--- a/projects/boreal/web/components/FilterDrawer.vue\n+++ b/projects/boreal/web/components/FilterDrawer.vue\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit BorealTideWorkerFlow 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":"BorealCinderAuthCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"How should BorealLedgerGateStore be decomposed?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Em projects/boreal/cmd/exporter/main.py, o BorealNovaPickerStore tem um problema intermitente no fluxo de Spring Boot. Proponha fases, compatibilidade, métricas, rollback e ownership; pare antes de alterar código.\n\nRestrições:\n- continuar com Spring Boot\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao BorealNovaPickerStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"pt"} +{"prompt":"Dashboard: Incident timeline — INC-42146\n\n08:02 deploy BorealCinderAuthFlow 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 BorealCinderAuthFlow 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":"A previously stable test around BorealOpalRouterStore now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Worker: The BorealWillowCodecFlow 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":"PM is preparing the BorealMosaicGridService rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealMosaicGridService\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"BorealMapleQueueStore returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/boreal/ml/pipeline/features.py and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"BorealAsterWebhookCoordinator needs a paired pass: change BorealAsterWebhookCoordinator's known staging timeout from 15 to 30 seconds, plus give the existing implementation a read-only safety pass. Use projects/boreal/Sources/App/SessionStore.swift as the source of truth, preserve the Spring Boot contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"BorealCopperBridgeService flakes under UTC","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"projects/boreal/services/ledger/replay.go の BorealRavenSessionService で、Kotlin coroutines の flow に断続的な問題が起きています。 responsive layout、empty/retry state、keyboard focus、dark mode、reduced motion を仕上げてください。\n\n制約:\n- Kotlin coroutines を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は BorealRavenSessionService のみ","purpose":"frontendImpl","secondary":"debugging","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"ja"} +{"prompt":"Please resist widening this one: BorealMarbleTokenStore works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealMarbleTokenStore\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Simulator: // projects/boreal/workers/thumbnail/consumer.ex\nfinal class BorealRainfallDBFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 BorealRainfallDBFlow; 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":"UI ticket DES-42134: finish the compact BorealOpalRouterFlow filter experience\n\nRoute: /catalog/search\nSource: projects/boreal/pkg/cache/lease.rs\nFramework: Cloudflare Workers\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 BorealOpalRouterFlow 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":"Walk through BorealJuniperCLIService's segment.rs","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"BorealPrismCacheCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"BorealDeltaCanvasCoordinator: ship a sensible version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Summarize the BorealWrenExportService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"BorealMoonlitSDKCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"diff --git a/projects/boreal/packages/api/openapi.yaml b/projects/boreal/packages/api/openapi.yaml\nindex 62d71aa..90f3c1e 100644\n--- a/projects/boreal/packages/api/openapi.yaml\n+++ b/projects/boreal/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 BorealDeltaCanvasFlow 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":"Match BorealPineMetricsService's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Incident timeline — INC-42158\n\n08:02 deploy BorealMarbleTokenCoordinator 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 BorealMarbleTokenCoordinator 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":"Release engineering needs a BorealDriftConsoleFlow 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":"Why is BorealLedgerGateService stalling?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"What sequence would let BorealDeltaCanvasService adopt Cloudflare Workers 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.8,"slice":"core","lang":"en"} +{"prompt":"Enforce BorealTideWorkerStore's idempotency key","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Ownership of BorealCoralUploadStore is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current GraphQL operational envelope\n\nThe relevant code crosses computer vision, React, PostgreSQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Documente o contrato de BorealRainfallDBService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"pt"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current BorealAmberFilterService design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealAmberFilterService\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Extract BorealCedarPolicyService's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Does BorealPineMetricsStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"projects/boreal/cmd/exporter/main.py has grown through several launches, and BorealBeaconStoreStore now mixes policy, transport, persistence, and metrics in one place. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- leave generated files and vendored code alone\n- stay compatible with the existing Spring Boot deployment\n- keep the work scoped to BorealBeaconStoreStore and its direct tests\n\nSeveral teams work in this computer vision, React, PostgreSQL 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":"Ticket OPS-42155: retire the legacy replay path for BorealMapleQueueCoordinator\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 BorealMapleQueueCoordinator 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":"Runbook: diff --git a/projects/boreal/web/components/FilterDrawer.vue b/projects/boreal/web/components/FilterDrawer.vue\nindex 62d71aa..90f3c1e 100644\n--- a/projects/boreal/web/components/FilterDrawer.vue\n+++ b/projects/boreal/web/components/FilterDrawer.vue\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Restructure BorealAmberFilterFlow 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":"BorealSableParserStore's staging timeout is already known to be wrong: change the single projects/boreal/infra/modules/edge/main.tf value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Release verification found a single stale BorealKiteSchedulerService value; the cause, desired value, and affected assertion are already agreed. 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- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current GraphQL operational envelope\n\nThe relevant code crosses computer vision, React, PostgreSQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Trace: Ticket OPS-42150: retire the legacy replay path for BorealBasilRunnerCoordinator\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 BorealBasilRunnerCoordinator 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"What does BorealJuniperCLIStore own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Outline a safer BorealAcornWidgetService cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Profiler: Incident timeline — INC-42144\n\n08:02 deploy BorealFlintTimelineFlow 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 BorealFlintTimelineFlow, 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":"Console: # projects/boreal/internal/auth/refresh.go\n[worker.borealacornwidgetflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.borealacornwidgetflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.borealacornwidgetflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.BorealAcornWidgetFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-42118\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/boreal/internal/auth/refresh.go. 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":"Workspace: projects/boreal/apps/console/routes/usage.svelte の BorealEmberRelayFlow で、GraphQL の flow に断続的な問題が起きています。 consumer 向けに contract、error、retry、コピー可能な例を含む文書を書き、handler は変更しないでください。\n\n制約:\n- GraphQL を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は BorealEmberRelayFlow のみ","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"ja"} +{"prompt":"Fresh release brief for BorealMosaicGridCoordinator:\n- primary outcome: finish BorealMosaicGridCoordinator's responsive empty and retry states\n- companion outcome: give the existing implementation a read-only safety pass\n- repository entry point: projects/boreal/Sources/App/SessionStore.swift\n- platform constraint: Spring Boot\n- known complication: two validators with subtly different error strings\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":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"PM is preparing the BorealVelaDrawerService rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealVelaDrawerService\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Repository: Release verification found a single stale BorealMosaicGridStore value; the cause, desired value, and affected assertion are already agreed. 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- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current Spring Boot operational envelope\n\nThe relevant code crosses computer vision, React, PostgreSQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Read projects/boreal/Sources/App/SessionStore.swift and tell me whether BorealGarnetModalService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Assess the BorealAcornWidgetStore diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"BorealLumenChartStore returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/boreal/ui/settings/PrivacyPane.tsx and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Give BorealEchoRegistryFlow'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":"Split projects/boreal/app/src/main/SyncWorker.kt by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Ownership of BorealBasilRunnerService is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current Spring Boot operational envelope\n\nThe relevant code crosses computer vision, React, PostgreSQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"BorealFrostPanelCoordinator: sequence, then restructure","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-42154\n\n08:02 deploy BorealDriftConsoleCoordinator 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 BorealDriftConsoleCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Documente le contrat BorealQuartzPlayerService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"fr"} +{"prompt":"How does BorealEchoRegistryStore propagate cancellation through the Kotlin coroutines boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"$ pnpm test --filter BorealAtlasSearchFlow\n RUN v3.2.4 /workspace/apps/console\n × BorealAtlasSearchFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=42111 phase=resume storedCursor=seg-0183\n session=42111 phase=fetch requestCursor=seg-0183 pageSize=200\n session=42111 phase=commit receivedCursor=seg-0184 itemCount=0\n session=42111 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nReconstruct the BorealAtlasSearchFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Pipeline: What is the safest way to split projects/boreal/apps/console/routes/usage.svelte into independently owned modules while BorealMoonlitSDKService's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"Add a bounded BorealBasilRunnerStore export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Two deliverables are holding up BorealIrisBatchCoordinator. First, separate BorealIrisBatchCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/boreal/lib/codec/frame.cc, which follows Kafka conventions and currently suffers from a misleading timeout name used in five packages. 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":"refactor","secondary":"review","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"For BorealPineMetricsCoordinator, finish BorealPineMetricsCoordinator's responsive empty and retry states; once that is complete, give the existing implementation a read-only safety pass. Work from projects/boreal/ml/pipeline/features.py, stay with Spring Boot, and leave generated files and vendored code alone. Keep the two outcomes separately reviewable.","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"En projects/boreal/apps/console/routes/usage.svelte, BorealAtlasSearchStore tiene un problema intermitente en el flujo de GraphQL. Separa responsabilidades y elimina duplicación, conservando API, wire values, orden y comportamiento observable.\n\nRestricciones:\n- seguir con GraphQL\n- conservar compatibilidad y cancelación\n- limitar el cambio a BorealAtlasSearchStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con GraphQL alrededor de BorealAtlasSearchStore.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"es"} +{"prompt":"BorealLumenChartCoordinator: give it a nicer flow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Two asks around BorealCopperBridgeCoordinator: (1) ship the idempotent BorealCopperBridgeCoordinator replay endpoint; (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":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Clarify BorealSlateEditorStore's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-42116: finish the compact BorealCoralUploadFlow filter experience\n\nRoute: /catalog/search\nSource: projects/boreal/db/migrations/20260730_events.sql\nFramework: GraphQL\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 BorealCoralUploadFlow 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":"core","lang":"en"} +{"prompt":"BorealTideWorkerCoordinator needs a paired pass: assess ownership and failure handling in projects/boreal/services/ledger/replay.go, plus capture the contract and rollback note for consumers. Use projects/boreal/services/ledger/replay.go as the source of truth, preserve the Kotlin coroutines contract, and avoid unrelated cleanup.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Clarify BorealCloudReconcilerService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"thread 'tokio-runtime-worker' panicked at projects/boreal/apps/console/routes/usage.svelte:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: borealmoonlitsdkflow::scheduler::LeaseTask::flush\n at ./projects/boreal/apps/console/routes/usage.svelte:217:18\n 4: borealmoonlitsdkflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nReconstruct the BorealMoonlitSDKFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Ticket OPS-42159: retire the legacy replay path for BorealSummitProxyCoordinator\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 BorealSummitProxyCoordinator 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":"BorealOpalRouterCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"BorealSpruceDaemonService's metric is misspelled as succesful_total in one declaration. Correct that literal and its exact test expectation, without renaming anything else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fresh release brief for BorealAmberFilterCoordinator:\n- primary outcome: separate BorealAmberFilterCoordinator's policy from transport without behavior changes\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/boreal/services/ledger/replay.go\n- platform constraint: Kotlin coroutines\n- known complication: stale cursors when a page is resumed\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":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Compare BorealHarborIndexStore's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"The BorealOspreyJobService 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":"BorealNovaPickerCoordinator: polish the last piece","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"For BorealCloudReconcilerCoordinator, finish BorealCloudReconcilerCoordinator's responsive empty and retry states; once that is complete, give the existing implementation a read-only safety pass. Work from projects/boreal/apps/console/routes/usage.svelte, stay with GraphQL, and leave generated files and vendored code alone. Keep the two outcomes separately reviewable.","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"The first BorealPrismCacheStore request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"BorealWrenExportCoordinator: ship, then document","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"diff --git a/projects/boreal/apps/console/routes/usage.svelte b/projects/boreal/apps/console/routes/usage.svelte\nindex 62d71aa..90f3c1e 100644\n--- a/projects/boreal/apps/console/routes/usage.svelte\n+++ b/projects/boreal/apps/console/routes/usage.svelte\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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Split BorealSlateEditorFlow 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":"Gateway: Ticket OPS-42131: retire the legacy replay path for BorealCloudReconcilerFlow\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 BorealCloudReconcilerFlow 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":"BorealLedgerGateCoordinator: restructure, then correct","purpose":"refactor","secondary":"backendImpl","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"projects/boreal/ml/pipeline/features.py 里的 BorealNovaPickerService 最近在 Spring Boot 流程中出现间歇性问题。 请写一份面向调用方的说明，包含 contract、错误、retry 和可复制示例，不要改 handler。\n\n约束：\n- 继续使用 Spring Boot\n- 保持兼容性和取消语义\n- 改动只限于 BorealNovaPickerService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"zh"} +{"prompt":"Rename BorealTideWorkerService's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-42145: retire the legacy replay path for BorealMicaProfileFlow\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，并明确说明证据和取舍。 Map a safe route from the current BorealMicaProfileFlow 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":"En projects/boreal/services/ledger/replay.go, BorealEchoRegistryService tiene un problema intermitente en el flujo de Kotlin coroutines. Lee el flujo actual y dime si ownership, cancelación y orden son seguros; solo necesito el análisis.\n\nRestricciones:\n- seguir con Kotlin coroutines\n- conservar compatibilidad y cancelación\n- limitar el cambio a BorealEchoRegistryService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"es"} +{"prompt":"BorealCoralUploadCoordinator: polish, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Persist BorealCoralUploadService's replay cursor","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"$ pnpm test --filter BorealCraneWorkspaceFlow\n RUN v3.2.4 /workspace/apps/console\n × BorealCraneWorkspaceFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=42132 phase=resume storedCursor=seg-0183\n session=42132 phase=fetch requestCursor=seg-0183 pageSize=200\n session=42132 phase=commit receivedCursor=seg-0184 itemCount=0\n session=42132 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nReconstruct the BorealCraneWorkspaceFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Incident timeline — INC-42138\n\n08:02 deploy BorealSableParserFlow 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 BorealSableParserFlow, 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":"A copied hex color in BorealMicaProfileService lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Please resist widening this one: BorealOrbitSyncStore works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside BorealOrbitSyncStore\n- leave generated files and vendored code alone\n\nThis repository spans computer vision, React, PostgreSQL; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"BorealAtlasSearchCoordinator is blocking the next release because memory growth during hour-long imports. I need two concrete outcomes from a single pass: change BorealAtlasSearchCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing GraphQL conventions in projects/boreal/apps/console/routes/usage.svelte; 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.7,"slice":"mixed","lang":"en"} +{"prompt":"Summarize the BorealCloudReconcilerStore changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Does BorealBirchMigratorStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists? I want your judgment and walkthrough, not new documentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"We expect BorealMapleQueueService to outgrow its current Spring Boot arrangement next quarter, but changing everything at once would be risky. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- leave generated files and vendored code alone\n- stay compatible with the existing Spring Boot deployment\n- keep the work scoped to BorealMapleQueueService and its direct tests\n\nSeveral teams work in this computer vision, React, PostgreSQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"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_42126'\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_42126'::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 BorealCedarPolicyFlow'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.8,"slice":"pasted-context","lang":"en"} +{"prompt":"BorealFernSnapshotCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"diff --git a/projects/boreal/engine/render/atlas.cpp b/projects/boreal/engine/render/atlas.cpp\nindex 62d71aa..90f3c1e 100644\n--- a/projects/boreal/engine/render/atlas.cpp\n+++ b/projects/boreal/engine/render/atlas.cpp\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 BorealWillowCodecCoordinator'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":"A copied hex color in BorealMapleQueueFlow lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Where did BorealCedarPolicyStore's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"Is there a cleaner way to separate BorealVelaDrawerFlow'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":"Dedupe BorealAsterWebhookService's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"We expect BorealSummitProxyStore to outgrow its current Cloudflare Workers arrangement next quarter, but changing everything at once would be risky. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- leave generated files and vendored code alone\n- stay compatible with the existing Cloudflare Workers deployment\n- keep the work scoped to BorealSummitProxyStore and its direct tests\n\nSeveral teams work in this computer vision, React, PostgreSQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Is BorealCopperBridgeStore safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"This should remain a deliberately small patch: BorealWillowCodecService has one known configuration mistake in projects/boreal/lib/codec/frame.cc, not an open-ended failure investigation. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- leave generated files and vendored code alone\n- stay compatible with the existing Kafka deployment\n- keep the work scoped to BorealWillowCodecService and its direct tests\n\nSeveral teams work in this computer vision, React, PostgreSQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"BorealRavenSessionCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Test Suite 'BorealLedgerGateFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[BorealLedgerGateFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/boreal/services/ledger/replay.go:144: error: -[BorealLedgerGateFlowTests 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 '-[BorealLedgerGateFlowTests 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 BorealLedgerGateFlow'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"} diff --git a/data/round2-03.jsonl b/data/round2-03.jsonl index 56eb403..4e5f505 100644 --- a/data/round2-03.jsonl +++ b/data/round2-03.jsonl @@ -1,200 +1,200 @@ -{"prompt": "a contractor is about to touch our authentication middleware and i'd like a second read on it first: how the tenant is resolved, what happens when the header is present but the token is for another tenant, and whether the viewer role can reach any write path", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "our error responses are a mix of plain strings, a `{error}` object and RFC 7807 problem details depending on the endpoint's age — pick the newest shape and apply it everywhere without changing status codes", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "the conflict drawer in the desktop app needs to actually show what changed, field by field, with a choice per conflict", "purpose": "frontendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "training run died overnight at epoch 31 of 60 and i lost the checkpoint:\n\nTraceback (most recent call last):\n File \"train.py\", line 212, in \n main(cfg)\n File \"train.py\", line 168, in main\n loss.backward()\n File \"/opt/conda/lib/python3.11/site-packages/torch/_tensor.py\", line 581, in backward\n torch.autograd.backward(self, gradient, retain_graph, create_graph, inputs=inputs)\n File \"/opt/conda/lib/python3.11/site-packages/torch/autograd/__init__.py\", line 347, in backward\n _engine_run_backward(\ntorch.OutOfMemoryError: CUDA out of memory. Tried to allocate 2.44 GiB. GPU 0 has a total capacity of 79.15 GiB of which 1.88 GiB is free. Process 41221 has 77.2 GiB memory in use. Of the allocated memory 71.44 GiB is allocated by PyTorch, and 4.91 GiB is reserved by PyTorch but unallocated.\n\nbatch size hasn't changed, and epochs 1 through 30 were fine on the same node", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "a walkthrough of how a route goes from saved to solved to dispatched, naming the services and queues involved, would save me a week", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "our error codes appear in three places and are documented in none; produce the reference table from `errors.rs` with a sentence per code", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "the whole reassignment flow, honestly", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "stop popover cuts off at the right edge", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "desktop app freezes after sleep", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "training script has config handling scattered through it and i keep breaking runs by changing a default. same behaviour, one place:\n\nparser.add_argument(\"--lr\", type=float, default=3e-4)\nparser.add_argument(\"--batch-size\", type=int, default=64)\n...\ncfg = yaml.safe_load(open(args.config))\nlr = args.lr or cfg.get(\"lr\", 3e-4)\nbs = int(os.environ.get(\"BATCH_SIZE\", args.batch_size))\nif cfg.get(\"scheduler\") == \"cosine\":\n warmup = cfg.get(\"warmup\", 500)\nelse:\n warmup = int(os.environ.get(\"WARMUP\", 0))\nseed = cfg.get(\"seed\") if \"seed\" in cfg else args.seed if args.seed else 42\ngrad_accum = cfg.get(\"grad_accum\", 1) * (2 if os.environ.get(\"BIG_NODE\") else 1)", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "an intermittent one, maybe once a day, from the desktop app's crash reporter:\n\nProcess: FleetDesk [4471]\nPath: /Applications/FleetDesk.app/Contents/MacOS/FleetDesk\nIdentifier: io.fleetdesk.app\nVersion: 2.8.1 (2810)\nCode Type: ARM-64\nCrashed Thread: 0 Dispatch queue: com.apple.main-thread\n\nException Type: EXC_BAD_ACCESS (SIGSEGV)\nException Subtype: KERN_INVALID_ADDRESS at 0x0000000000000010\n\nThread 0 Crashed:\n0 FleetDesk 0x104a2c118 node::Buffer::Data(v8::Local) + 24\n1 FleetDesk 0x104b19a44 better_sqlite3::Statement::Run(...) + 388\n2 FleetDesk 0x1051220c8 v8::internal::Builtin_HandleApiCall + 296\n\nalways within a minute of the app coming back from sleep", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "before i approve this, is the locking sound? two dispatchers can assign the same driver today:\n\n@Transactional\npublic Assignment assign(UUID routeId, UUID driverId) {\n Route route = routeRepo.findById(routeId).orElseThrow();\n Driver driver = driverRepo.findById(driverId).orElseThrow();\n if (assignmentRepo.existsByDriverIdAndDayAndStatus(driverId, route.getDay(), ACTIVE)) {\n throw new DriverAlreadyAssigned(driverId);\n }\n Assignment a = new Assignment(route, driver, ACTIVE, Instant.now());\n assignmentRepo.save(a);\n eventPublisher.publish(new AssignmentCreated(a.getId()));\n notificationClient.notifyDriver(driverId, a.getId());\n return a;\n}\n\npostgres, read committed, two app instances behind a load balancer", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "design doc paragraph that keeps getting quoted at me. is it still accurate given what we built?\n\n\"Route optimisation runs asynchronously. When a planner saves a route, we enqueue a solve job and return immediately with the previous solution. The client polls /v1/routes/{id} until `solution_version` increases. Solves are idempotent per (route_id, input_hash), so re-enqueueing the same inputs is free. A solve never blocks the planner's UI, and a failed solve leaves the last good solution in place.\"\n\nas far as i can tell the desktop app blocks on save, and we removed input_hash in march", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "same guard clause copy-pasted into nine handlers, and two of them have it subtly wrong:\n\n// handlers/assignments.rs\nif !ctx.tenant_id.is_some() { return Err(Error::Unauthorized) }\nif ctx.role != Role::Dispatcher && ctx.role != Role::Admin { return Err(Error::Forbidden) }\n\n// handlers/routes.rs\nif ctx.tenant_id.is_none() { return Err(Error::Unauthorized) }\nif !matches!(ctx.role, Role::Dispatcher | Role::Admin | Role::Planner) { return Err(Error::Forbidden) }\n\n// handlers/drivers.rs\nif ctx.tenant_id.is_none() { return Err(Error::Unauthorized) }\nif ctx.role == Role::Viewer { return Err(Error::Forbidden) }\n\nthe intent everywhere is the same: authenticated, and not a viewer", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "solver time limit to 12s in prod", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "core", "lang": "en"} -{"prompt": "planner screen, obviously", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "`stop_seq` naming, pick one spelling", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "desktop release cadence is monthly and every release has a scramble at the end for notarization, changelog and the update feed. i'd like the whole release process designed properly — what's automated, what's a human gate, how we do staged rollout for an electron app, and how we roll back a bad update that's already downloaded", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "ipc surface has grown one handler per screen and they all do the same three steps. same behaviour, one registration point:\n\nipcMain.handle('routes:list', async (_e, filter) => {\n const t0 = Date.now()\n try { return { ok: true, data: await routes.list(filter) } }\n catch (e) { log.error('routes:list', e); return { ok: false, error: String(e) } }\n finally { metrics.timing('ipc.routes.list', Date.now() - t0) }\n})\n\nipcMain.handle('drivers:list', async (_e, filter) => {\n const t0 = Date.now()\n try { return { ok: true, data: await drivers.list(filter) } }\n catch (e) { log.error('drivers:list', e); return { ok: false, error: String(e) } }\n finally { metrics.timing('ipc.drivers.list', Date.now() - t0) }\n})\n\n// ...eleven more of these", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "vehicle bands need alternating backgrounds", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "map legend overlaps the zoom control", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "driver list scrolls behind the header", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "one latlng converter across the packages", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "what does `--relax-windows` actually do?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "is our idempotency key tenant-scoped?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "we owe our biggest customer a written explanation of last week's four-hour degradation, and they will read it carefully because their SLA credits depend on it. the facts are in the incident channel and the timeline is in grafana. write the customer-facing version — honest, specific about impact, clear about what changes, no engineering jargon", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "assignment, route and trip mean three different things in the java service depending on which file you're in, and two of them are swapped relative to the public API. rename everything internal to match what the API calls things, leave the json field names untouched, and do it in a way that's reviewable rather than one 4000-line commit", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "feature building happens in the training script, the evaluation script and the inference service, and the three have quietly diverged. bring them onto one implementation, and once they agree, document which features exist and where each comes from", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "public API changelog needs an entry for the new `sequence` field on the ETA payload, and partners need to know it's monotonic per route", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "how should we version the partner-facing API once the ETA push exists — header, path, or something else? i want a recommendation with reasoning", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "stop-level ETAs should be persisted rather than recomputed on every read, and the reporting team wants the history", "purpose": "backendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "design spec for the route timeline in the desktop app, build it with our vue components:\n\nRoute timeline (desktop, 1440px+)\n- Horizontal band per vehicle, 44px tall, stacked with 8px gaps, virtualised past 40 vehicles.\n- Time axis pinned at the top, hour ticks, current time as a 2px accent line with a small label.\n- Stops render as blocks proportional to service time, minimum 12px wide, 2px radius; late stops get a hatched fill.\n- Hovering a stop shows a popover with address, window, ETA and delay; keyboard focus does the same.\n- Dragging a stop between bands reassigns it, with a drop shadow and a live delta badge showing the ETA change.\n- Selection: click selects, shift-click range selects within a band, escape clears.\n- Zoom control at 4 steps (whole day / 6h / 2h / 30m), keeps the pointer position anchored.\n- Empty band shows \"No stops assigned\" and stays droppable.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "solver returns empty on 900-stop routes", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "same as the last one but bigger", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "an intermittent report from two fleets that a stop occasionally shows on the wrong vehicle for a few seconds after a reassignment, then corrects itself. that smells like an optimistic update racing the pull, but i can't reproduce it and neither can support", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "planner grid is unusable with a screen reader according to a customer, and it's our own component rather than a library. make it keyboard navigable with a proper grid role, add a keyboard alternative to drag and drop, and stop using colour alone for the delay column", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "before we build the ETA push i want the design written — transport, sequencing, backpressure, what we do when a partner's endpoint is down — and then the outbound sender itself, against whatever we land on", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "routing service panicked in prod, first time in eight months:\n\nthread 'route-worker-3' panicked at src/solver/insertion.rs:212:34:\nindex out of bounds: the len is 0 but the index is 0\nstack backtrace:\n 0: rust_begin_unwind\n 1: core::panicking::panic_fmt\n 2: core::panicking::panic_bounds_check\n 3: fleetd::solver::insertion::best_insertion\n at ./src/solver/insertion.rs:212:34\n 4: fleetd::solver::Solver::improve\n at ./src/solver/mod.rs:88:21\n 5: fleetd::worker::handle_job\n at ./src/worker.rs:141:9\n 6: tokio::runtime::task::harness::Harness::poll\nnote: Some details are omitted, run with `RUST_BACKTRACE=full`\n\njob 88421, 0 stops, 4 vehicles — a depot with no deliveries scheduled, which shouldn't be a job at all", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "electron main process log from a customer whose app hangs on launch, macOS 15:\n\n[main] app ready in 412ms\n[main] creating BrowserWindow 1200x800\n[updater] checking https://releases.fleetdesk.io/latest-mac.yml\n[db] opening sqlite at /Users/x/Library/Application Support/FleetDesk/local.db\n[db] running migration 0041_add_route_cache\n[db] migration 0041 took 18441ms\n[main] window did-finish-load\n[renderer] hydrating 41 cached routes\n[renderer] Uncaught (in promise) Error: IPC channel closed\n at EventEmitter. (renderer.js:1:88112)\n[main] window unresponsive\n[main] window responsive\n[main] window unresponsive\n\nthey have about 90k rows in route_cache, most users have a few hundred", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "java service throwing these under load, about 40 a minute since the last deploy:\n\njava.util.concurrent.TimeoutException: Did not observe any item or terminal signal within 30000ms in 'flatMap' (and no fallback has been configured)\n\tat reactor.core.publisher.FluxTimeout$TimeoutMainSubscriber.handleTimeout(FluxTimeout.java:295)\n\tat io.fleet.dispatch.AssignmentService.assign(AssignmentService.java:141)\n\tat io.fleet.dispatch.DispatchController.postAssignment(DispatchController.java:66)\n\tSuppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException:\nError has been observed at the following site(s):\n\t*__checkpoint ⇢ Request to POST /v1/assignments [DispatchHandler]\nOriginal Stack Trace:\n\t\tat io.fleet.dispatch.AssignmentService.lambda$assign$4(AssignmentService.java:139)\n\nthe downstream geocoder it calls reports p99 of 80ms and no errors", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "mqtt broker log from the depot gateway, devices drop off in batches:\n\n1753843201: New client connected from 10.2.4.71 as gw-depot-04 (p2, c0, k60, u'depot')\n1753843261: Client gw-depot-04 has exceeded timeout, disconnecting.\n1753843262: New client connected from 10.2.4.71 as gw-depot-04 (p2, c0, k60, u'depot')\n1753843263: Client gw-depot-04 already connected, closing old connection.\n1753843323: Client gw-depot-04 has exceeded timeout, disconnecting.\n1753843324: New connection from 10.2.4.71 on port 8883.\n1753843324: Client gw-depot-04 disconnected due to protocol error.\n1753843384: Socket error on client gw-depot-11, disconnecting.\n1753843385: Client gw-depot-11 disconnected: Out of memory.\n\nbroker memory sits at 60% and the network graph is flat", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "git bisect finished and i don't believe the result:\n\n41c9e0b8f2a1d3e4c5a6b7c8d9e0f1a2b3c4d5e6 is the first bad commit\ncommit 41c9e0b8f2a1d3e4c5a6b7c8d9e0f1a2b3c4d5e6\nAuthor: dana \nDate: Tue Jul 14 09:12:44 2026 +0200\n\n chore: enable strict null checks in the shared package\n\n tsconfig.base.json | 3 ++-\n packages/shared/src/geo.ts | 12 +++++------\n 2 files changed, 8 insertions(+), 7 deletions(-)\n\nbisect run success\n\nthe symptom is that route ETAs are 3-4 minutes off in the desktop app but correct in the web app, and this commit doesn't touch either of them directly", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "kubectl describe on the training job pod, it never gets scheduled:\n\nEvents:\n Type Reason Age From Message\n ---- ------ ---- ---- -------\n Warning FailedScheduling 4m12s default-scheduler 0/14 nodes are available: 6 Insufficient nvidia.com/gpu, 8 node(s) had untolerated taint {workload: training}\n Normal NotTriggerScaleUp 3m50s cluster-autoscaler pod didn't trigger scale-up: 2 max node group size reached, 1 node(s) had volume node affinity conflict\n Warning FailedScheduling 2m01s default-scheduler 0/14 nodes are available: 6 Insufficient nvidia.com/gpu, 8 node(s) had untolerated taint {workload: training}\n\nrequests: nvidia.com/gpu: 4, memory: 200Gi\ntolerations: [{key: workload, operator: Equal, value: inference}]\n\nthe same manifest worked last week", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "des tests flaky depuis lundi, toujours les mêmes trois, jamais en local :\n\nFAILED tests/test_routing.py::test_two_vehicles_share_a_depot - AssertionError: assert 41.2 == approx(41.19999999 ± 1.0e-06)\nFAILED tests/test_routing.py::test_time_windows_respected - IndexError: list index out of range\nFAILED tests/test_eta.py::test_eta_matches_matrix - assert datetime(2026, 7, 27, 14, 3) == datetime(2026, 7, 27, 14, 2)\n\n=========================== short test summary info ============================\n3 failed, 1841 passed, 12 skipped in 214.88s\n\nrandom seed: 8412 (pytest-randomly)\nworkers: 8 (pytest-xdist)\n\nsur ma machine avec -p no:randomly tout passe", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "fr"} -{"prompt": "valgrind on the gateway firmware simulator, it leaks a few KB an hour in the field:\n\n==41221== HEAP SUMMARY:\n==41221== in use at exit: 84,112 bytes in 1,204 blocks\n==41221== total heap usage: 88,441 allocs, 87,237 frees, 12,884,112 bytes allocated\n==41221==\n==41221== 68,224 bytes in 1,066 blocks are definitely lost in loss record 41 of 44\n==41221== at 0x4C2FB0F: malloc (vg_replace_malloc.c:299)\n==41221== by 0x40A112: telemetry_frame_new (telemetry.c:88)\n==41221== by 0x40B4C0: on_publish_ack (mqtt_handlers.c:141)\n==41221== by 0x40C219: mqtt_loop (mqtt_client.c:412)\n==41221== by 0x401E77: main (main.c:66)\n==41221==\n==41221== LEAK SUMMARY:\n==41221== definitely lost: 68,224 bytes in 1,066 blocks\n==41221== indirectly lost: 15,888 bytes in 138 blocks", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "data loader someone added last sprint. does this actually shuffle the way we think it does?\n\nclass RouteDataset(IterableDataset):\n def __init__(self, shards, batch_size=64, shuffle_buffer=10_000):\n self.shards = shards\n self.batch_size = batch_size\n self.shuffle_buffer = shuffle_buffer\n\n def __iter__(self):\n info = get_worker_info()\n shards = self.shards if info is None else self.shards[info.id::info.num_workers]\n buf = []\n for shard in shards:\n for row in read_parquet_rows(shard):\n buf.append(row)\n if len(buf) >= self.shuffle_buffer:\n random.shuffle(buf)\n yield from batched(buf, self.batch_size)\n buf = []\n if buf:\n yield from batched(buf, self.batch_size)\n\nfour workers, 200 shards, and validation loss is suspiciously smooth", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "openapi we publish for partners, section for the assignment endpoint. does this match what a sane client would expect?\n\n /v1/assignments:\n post:\n operationId: createAssignment\n requestBody:\n required: true\n content:\n application/json:\n schema:\n type: object\n required: [route_id]\n properties:\n route_id: { type: string, format: uuid }\n driver_id: { type: string, format: uuid, nullable: true }\n force: { type: boolean, default: false }\n responses:\n '200': { description: created }\n '409': { description: conflict }\n '422': { description: unprocessable }\n default: { description: error }\n\nno schemas on any response, and `force` isn't described anywhere else either", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "benchmark numbers from the solver rewrite. is this a real win or did we just move the cost around?\n\n old new delta\nsolve_small (20 stops) 4.2ms 1.1ms -74%\nsolve_med (120 stops) 88ms 31ms -65%\nsolve_large (900 stops) 6.1s 7.8s +28%\nmemory_large 210MB 1.4GB +566%\nfirst_feasible_large 0.9s 4.4s +388%\nalloc_count_large 88k 2.1M +2286%\n\ncriterion, 100 samples, same machine, both release builds with lto=thin\n\nmost of our customers are in the 50-300 stop range but our three biggest accounts are all above 800", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "这是我们同事写的 IPC 层，我看着有点不安全，帮我判断一下：\n\nipcMain.handle('db:query', async (event, sql, params) => {\n const db = getDb()\n return db.prepare(sql).all(...(params ?? []))\n})\n\nipcMain.handle('fs:read', async (event, path) => {\n return fs.promises.readFile(path, 'utf8')\n})\n\nipcMain.on('window:setTitle', (event, title) => {\n BrowserWindow.fromWebContents(event.sender)?.setTitle(title)\n})\n\n// preload.js\ncontextBridge.exposeInMainWorld('api', {\n query: (sql, params) => ipcRenderer.invoke('db:query', sql, params),\n readFile: (p) => ipcRenderer.invoke('fs:read', p),\n})\n\n渲染进程会加载第三方的地图 SDK", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "zh"} -{"prompt": "github actions workflow for the model training image. anything here that explains why builds take 40 minutes?\n\njobs:\n build:\n runs-on: ubuntu-latest\n steps:\n - uses: actions/checkout@v4\n - uses: docker/setup-buildx-action@v3\n - run: pip install -r requirements-dev.txt\n - run: pytest -q\n - uses: docker/build-push-action@v6\n with:\n context: .\n push: true\n tags: ghcr.io/fleet/trainer:${{ github.sha }}\n - run: python tools/export_onnx.py --checkpoint artifacts/last.ckpt\n - uses: actions/upload-artifact@v4\n with:\n name: onnx\n path: artifacts/*.onnx\n\nno cache configuration anywhere, and requirements-dev.txt pins torch", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "a short internal note explaining why we're moving inference off the solver box, for the platform team's decision log", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "our health endpoint returns 200 while the solver queue is completely stalled, it should at least check the worker heartbeat", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "the sync indicator in the desktop titlebar has five states in the design and two in the code, so users see a spinner for offline, errors and conflicts alike. implement the full set — idle, syncing after a delay, offline with a pending count, conflict with an amber dot, and a failure state with a retry link — and make sure none of them rely on colour alone", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "training config is read from argparse, a yaml file and environment variables, with precedence that differs per field and one place where they're multiplied together. unify it into a single resolved config object, keep every current default exactly as it is, and make the precedence explicit and testable", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "a nightly export of closed routes to the customer's SFTP, csv, one file per depot, with a manifest and a checksum", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "our on-call rotation covers three services with wildly different failure modes, and the alerting was set up per-service by different people. what should a coherent alerting story look like?", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "the queue implementation has a claim TTL, a heartbeat, a dead-letter threshold and a release command, and every person on the team describes their interaction differently. read it and give me the actual semantics: when a claim expires, what happens to a job whose worker died mid-solve, whether a job can run twice, and what the dead-letter table really means", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "stop detail popover currently opens on hover, closes when the pointer leaves, and traps nothing, which means keyboard users never see it and touch users on the surface tablets get it stuck open. rework it as a proper popover with focus management, an escape key, a small delay before opening, and behaviour that makes sense when the underlying row moves because a sync landed", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "desktop app's local database has grown to a gigabyte for our biggest customers and i don't know whether that's the route cache, the telemetry buffer or something we forgot to prune. work out what's actually in there and which of it is load-bearing", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "training loss goes to NaN somewhere between step 4000 and 6000, but only when we enable the traffic features, and only on the multi-GPU runs. single GPU with the same config and seed is fine for a full epoch", "purpose": "debugging", "secondary": "planning", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "coverage report after the sprint, and management wants a number. what does this actually tell us?\n\nName Stmts Miss Cover Missing\n---------------------------------------------------------------\nfleet/solver/insertion.py 412 18 96% 88-91, 212-218\nfleet/solver/local_search.py 388 141 64% 102-188, 240-291\nfleet/eta/matrix.py 190 4 98% 77-80\nfleet/eta/traffic.py 144 144 0% 1-144\nfleet/api/routes.py 266 31 88% 41-52, 188-201\nfleet/api/assignments.py 180 12 93% 66-77\nfleet/jobs/nightly.py 121 121 0% 1-121\n---------------------------------------------------------------\nTOTAL 1701 471 72%\n\ntraffic.py and nightly.py are the two things that page us most often", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "endpoint below is what partners integrate against, and the only documentation is this handler. write the reference page:\n\n@PostMapping(\"/v1/assignments\")\npublic ResponseEntity post(@RequestBody @Valid AssignmentRequest req,\n @RequestHeader(\"Idempotency-Key\") String key) {\n if (req.driverId() == null && !req.force()) {\n throw new BadRequest(\"driver_id required unless force=true\");\n }\n var existing = idempotency.find(key);\n if (existing != null) return ResponseEntity.ok(existing);\n var a = service.assign(req.routeId(), req.driverId(), req.force());\n idempotency.put(key, a, Duration.ofHours(24));\n return ResponseEntity.status(201).body(AssignmentDto.from(a));\n}\n\nmention that force=true auto-selects the nearest available driver, that 200 means replayed and 201 means created, and that the key is scoped per tenant", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "protobuf schema for the telemetry stream, and partners keep asking what the fields mean. document it properly:\n\nmessage Telemetry {\n string device_id = 1;\n int64 captured_at_ms = 2;\n Position position = 3;\n optional float speed_kph = 4;\n optional float heading_deg = 5;\n optional int32 battery_pct = 6;\n repeated Event events = 7;\n reserved 8 to 11;\n string firmware = 12;\n}\n\nmessage Event {\n enum Kind { UNKNOWN = 0; HARSH_BRAKE = 1; IDLE_START = 2; IDLE_END = 3; DOOR_OPEN = 4; }\n Kind kind = 1;\n int64 at_ms = 2;\n map attrs = 3;\n}\n\nthings only we know: captured_at_ms is device clock and can be wrong by minutes; heading is absent when stationary; attrs keys are not stable across firmware versions", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "notas de la reunión con operaciones, hay que convertirlas en el documento de requisitos:\n\n- los conductores fichan desde el móvil pero el sistema no sabe si están en el depósito o en ruta\n- las rutas se cierran a las 22:00 aunque el conductor siga entregando, y luego hay que reabrirlas a mano\n- los cambios de última hora llegan por whatsapp al jefe de tráfico, nunca al sistema\n- quieren ver el retraso acumulado por ruta en tiempo real, hoy lo calculan en una hoja de cálculo\n- dos depósitos comparten flota los viernes y eso no se puede modelar\n- si un camión se avería, reasignar sus paradas lleva veinte minutos de trabajo manual", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "es"} -{"prompt": "model card is empty and legal wants one before this ships to customers. what we know:\n\n- gradient boosted model predicting stop service time from historical telemetry\n- trained on 14 months of data from 61 fleets, 8.2M stops, EU only\n- features: stop type, time of day, weekday, vehicle class, historical median for the location, weather bucket\n- excluded deliberately: driver identity, anything that could act as a proxy for it\n- MAE 2.1 minutes overall, 4.8 minutes for stops with fewer than 5 historical observations\n- known weakness: dense urban centres in cities not in the training set\n- retrained quarterly, no online learning, rollback is a config flag\n\nwrite the model card, audience is a customer's procurement team", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "support escalation thread, needs to become a known-issues entry:\n\n[09:12] tomas: three customers on 2.8.1 say the app freezes for 20-30s after waking the laptop\n[09:14] pri: reproduced on my mac, only when there are unsynced routes\n[09:20] tomas: the sqlite handle goes stale over sleep i think, we reopen it lazily\n[09:31] pri: confirmed, first query after wake blocks and the UI thread is doing it\n[09:44] tomas: workaround for support: quit and reopen the app, nothing is lost\n[10:02] pri: proper fix is reopening on wake and moving queries off the main thread, that's not this week\n[10:15] tomas: 2.8.2 will have the workaround banner at least\n\nwrite the entry the way our other known-issues entries read: symptom, affected versions, workaround, status", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "cli help output, and the manual page we ship is from two versions ago:\n\nfleetctl solve [OPTIONS] \n\nArguments:\n Route definition in JSON or CSV\n\nOptions:\n -t, --time-limit Stop after this long [default: 30]\n -s, --seed Deterministic seed for the metaheuristic\n --strategy [default: guided] [possible values: greedy, guided, exhaustive]\n --vehicles Override the vehicle count in the file\n --relax-windows Allow time window violations, penalised\n --emit-intermediate Print every improvement to stderr as it is found\n --matrix Precomputed distance matrix\n -o, --output Write the solution here [default: stdout]\n -v, --verbose... Increase logging\n\nrewrite the man page, and note that --exhaustive on more than 200 stops is not practical", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "draft the customer email about the maintenance window from these notes, it goes to 400 fleet managers:\n\n- saturday 09 aug, 01:00 to 05:00 UTC\n- the planning app will be read-only for the whole window, mobile driver app unaffected\n- routes already dispatched keep working, new routes cannot be created\n- reason: moving the route database to a new cluster, needed for the bigger fleets\n- if it overruns we'll extend to 07:00 and post on status.fleetdesk.io\n- no action needed from them, but they should avoid scheduling monday routes on saturday morning\n- support will be staffed throughout", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"} -{"prompt": "o README do repositório do modelo está desatualizado. o que existe hoje:\n\n- treino com `python train.py --config configs/base.yaml`, requer GPU com 40GB+\n- os dados vêm do bucket `fleet-ml-eu`, sincronizados com `make data` (precisa de credenciais AWS)\n- avaliação: `python eval.py --checkpoint --split test`, gera um relatório em `reports/`\n- exportação para ONNX é um passo separado e só funciona com opset 17\n- o serviço de inferência está noutro repositório e espera o modelo em `s3://fleet-models/service-time/vN/`\n- os notebooks em `notebooks/` estão obsoletos, ninguém os usa há um ano\n\nescreve o README para quem chega amanhã", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "pt"} -{"prompt": "cargo audit on the routing service, tell me which of these to bump now and which can wait:\n\nCrate: openssl\nVersion: 0.10.64\nTitle: Use-after-free in SSL session handling\nDate: 2026-06-11\nID: RUSTSEC-2026-0041\nSolution: Upgrade to >=0.10.68\n\nCrate: rustls\nVersion: 0.23.10\nTitle: Panic on malformed certificate chain\nDate: 2026-05-02\nID: RUSTSEC-2026-0033\nSolution: Upgrade to >=0.23.14\n\nCrate: time\nVersion: 0.3.34\nWarning: unmaintained branch\n\nerror: 2 vulnerabilities found, 1 warning", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"} -{"prompt": "typecheck is failing on the desktop app after the shared package change:\n\npackages/desktop/src/routes/RouteTable.tsx:88:24 - error TS2532: Object is possibly 'undefined'.\n88 const eta = route.stops[0].eta.toISOString()\n ~~~~~~~~~~~~~~~\npackages/desktop/src/routes/RouteTable.tsx:141:9 - error TS18048: 'driver' is possibly 'undefined'.\npackages/desktop/src/sync/pull.ts:41:15 - error TS2345: Argument of type 'string | undefined' is not assignable to parameter of type 'string'.\npackages/desktop/src/sync/pull.ts:66:7 - error TS18047: 'lastSync' is possibly 'null'.\n\nFound 4 errors in 2 files.\n\nstrict null checks got turned on in tsconfig.base.json last week", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"} -{"prompt": "prod config and staging config for the solver, one of these numbers is why staging never reproduces prod timeouts:\n\n# staging/solver.yaml\nsolver:\n time_limit_seconds: 30\n workers: 4\n max_stops_per_job: 2000\n matrix_cache_ttl_minutes: 60\n queue_claim_ttl_seconds: 900\n dead_letter_after: 3\n strategy: guided\n emit_intermediate: true\n heartbeat_seconds: 30\n\n# prod/solver.yaml\nsolver:\n time_limit_seconds: 8\n workers: 24\n max_stops_per_job: 2000\n matrix_cache_ttl_minutes: 5\n queue_claim_ttl_seconds: 900\n dead_letter_after: 3\n strategy: guided\n emit_intermediate: false\n heartbeat_seconds: 30\n\n# what the alert looks like in prod, never in staging\nsolver_job_timeout_total{env=\"prod\"} 41 in the last hour\nsolver_job_timeout_total{env=\"staging\"} 0 in the last 30 days", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "pasted-context", "lang": "en"} -{"prompt": "electron-builder config, notarization started failing after the mac runner upgrade:\n\n\"mac\": {\n \"category\": \"public.app-category.business\",\n \"hardenedRuntime\": true,\n \"gatekeeperAssess\": false,\n \"entitlements\": \"build/entitlements.mac.plist\",\n \"entitlementsInherit\": \"build/entitlements.mac.plist\",\n \"notarize\": { \"teamId\": \"8K4L2M9N\" },\n \"target\": [{ \"target\": \"dmg\", \"arch\": [\"arm64\", \"x64\"] }]\n},\n\nerror log:\n • signing file=dist/mac-arm64/FleetDesk.app\n ⨯ notarization failed reason=Team ID is required when using notarytool with an App Store Connect API key\n ⨯ /usr/bin/xcrun exited with code 1", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"} -{"prompt": "eslint on the vue frontend, mostly one rule repeated:\n\n/app/src/components/RouteMap.vue\n 41:3 error Component name \"map\" should always be multi-word vue/multi-word-component-names\n 88:11 error 'watchEffect' is defined but never used @typescript-eslint/no-unused-vars\n 112:7 warning Unexpected mutation of \"stops\" prop vue/no-mutating-props\n\n/app/src/components/StopList.vue\n 22:5 warning Unexpected mutation of \"stops\" prop vue/no-mutating-props\n 67:9 error v-for should have explicit key vue/require-v-for-key\n\n/app/src/views/PlannerView.vue\n 141:1 error Expected indentation of 2 spaces but found 4 vue/html-indent\n\n✖ 6 problems (4 errors, 2 warnings)", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "pasted-context", "lang": "en"} -{"prompt": "terraform plan output, i only wanted to change the instance type:\n\nTerraform will perform the following actions:\n\n # aws_instance.solver[0] must be replaced\n -/+ resource \"aws_instance\" \"solver\" {\n ~ instance_type = \"c6i.4xlarge\" -> \"c7i.4xlarge\" # forces replacement\n ~ private_ip = \"10.2.4.71\" -> (known after apply)\n ~ id = \"i-0a11c3f2\" -> (known after apply)\n }\n\n # aws_lb_target_group_attachment.solver[0] must be replaced\n -/+ resource \"aws_lb_target_group_attachment\" \"solver\" {\n ~ target_id = \"i-0a11c3f2\" -> (known after apply) # forces replacement\n }\n\n # aws_ebs_volume.solver_cache[0] will be destroyed\n - resource \"aws_ebs_volume\" \"solver_cache\" {\n - size = 500 -> null\n }\n\nPlan: 2 to add, 0 to change, 3 to destroy.", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "dockerfile for the trainer image, it's 14GB and takes forever to push:\n\nFROM nvidia/cuda:12.4.1-devel-ubuntu22.04\nRUN apt-get update && apt-get install -y python3.11 python3-pip git curl build-essential\nCOPY . /workspace\nWORKDIR /workspace\nRUN pip install -r requirements-dev.txt\nRUN pip install -r requirements.txt\nRUN python -c \"import torch; print(torch.__version__)\"\nRUN make data\nENV PYTHONPATH=/workspace\nCMD [\"python\", \"train.py\", \"--config\", \"configs/base.yaml\"]\n\nrequirements-dev.txt includes pytest, ruff, notebook and jupyterlab", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "three functions that convert between our coordinate types, in three files, all slightly different. one of them, please:\n\n// packages/shared/src/geo.ts\nexport const toLatLng = (p: Point): LatLng => ({ lat: p.y, lng: p.x })\n\n// packages/desktop/src/map/convert.ts\nexport function pointToLatLng(p: { x: number; y: number }) {\n return { lat: Number(p.y.toFixed(6)), lng: Number(p.x.toFixed(6)) }\n}\n\n// packages/web/src/lib/coords.ts\nexport const asLatLng = (p: Point | LatLng): LatLng =>\n 'lat' in p ? p : { lat: p.y, lng: p.x }\n\nthe rounding in the desktop one is deliberate — the map SDK chokes on more precision", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "pasted-context", "lang": "en"} -{"prompt": "this module has one function doing five things and i want the same output with seams i can test:\n\ndef build_features(stops, telemetry, weather, cfg):\n df = pd.DataFrame([s.__dict__ for s in stops])\n df[\"hour\"] = pd.to_datetime(df[\"arrived_at\"]).dt.hour\n df[\"weekday\"] = pd.to_datetime(df[\"arrived_at\"]).dt.weekday\n tel = pd.DataFrame(telemetry)\n tel = tel[tel[\"speed_kph\"] < 200]\n df = df.merge(tel.groupby(\"stop_id\").agg({\"idle_s\": \"sum\"}), on=\"stop_id\", how=\"left\")\n wx = pd.DataFrame(weather).rename(columns={\"t\": \"temp\"})\n df = df.merge(wx, on=[\"lat_bucket\", \"lon_bucket\", \"hour\"], how=\"left\")\n df[\"temp\"] = df[\"temp\"].fillna(df[\"temp\"].median())\n df[\"hist_median\"] = df.groupby(\"location_id\")[\"service_s\"].transform(\"median\")\n if cfg.drop_sparse:\n df = df[df.groupby(\"location_id\")[\"service_s\"].transform(\"count\") >= 5]\n return df.drop(columns=[\"arrived_at\", \"raw\"]), df[\"service_s\"]", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "legacy naming that predates the fleet/route split, i want it consistent across the java service:\n\nclass TripPlanner { ... } // actually plans routes\nclass RouteService { ... } // actually manages assignments\nclass AssignmentRepository { ... } // stores trips\ninterface TripRepository { ... } // stores routes\nrecord TripDto(...) { } // serialised as \"route\" in json\nenum TripStatus { PLANNED, DISPATCHED, DONE } // route status in the API\n\nthe json field names are public API and cannot change; everything internal should line up with what the API calls things", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "vier Konfigurationsklassen, die alle dasselbe tun. Bitte zusammenführen, ohne Verhalten zu ändern:\n\n@ConfigurationProperties(\"solver\")\npublic record SolverProps(int timeLimitSeconds, int workers) {}\n\n@Component\npublic class SolverConfig {\n @Value(\"${solver.time-limit-seconds:30}\") int timeLimit;\n @Value(\"${solver.workers:4}\") int workers;\n}\n\npublic class SolverSettings {\n public static int timeLimit() { return Integer.parseInt(System.getenv().getOrDefault(\"SOLVER_TIME_LIMIT\", \"30\")); }\n}\n\n@ConfigurationProperties(\"fleet.solver\")\npublic record LegacySolverProps(Integer timeLimit, Integer workerCount) {}\n\nalle vier werden irgendwo im Code gelesen", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "de"} -{"prompt": "quarterly planning input from ops, i need a technical roadmap out of it:\n\n- two new customers in Q4, one with 900 vehicles across 11 depots, one with 40\n- the big one wants live ETA updates pushed to their own customer app\n- ops wants to stop doing manual reassignment when a vehicle breaks down\n- finance wants per-route cost, which we don't compute at all today\n- the solver team wants six weeks to finish the large-instance work or they'll keep firefighting\n- we lose one backend engineer to parental leave in October\n- the desktop app has to keep shipping monthly regardless", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "architecture ticket, unassigned, and i want to think before someone picks it up:\n\nPLAT-204 — Split the monolith's dispatch module\nDispatch (assignment, driver state, notifications) shares a database and a deployment with planning (routes, solver jobs). Deploys of either block the other, and the assignment tables are the hottest thing in the database. The proposal on the table is a separate service with its own database and an event stream between them. Concerns raised so far: assignment reads join route data on every request; we have no event infrastructure; the mobile driver app talks to both; and there is one shared `tenants` table that everything reads.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "ML team's wishlist versus what we can actually run. sequence this for me:\n\n- retrain service-time model monthly instead of quarterly (needs a pipeline, currently a laptop job)\n- add traffic features from the new provider (contract signed, no integration)\n- online evaluation: compare predicted vs actual per fleet, alert on drift\n- move inference off the solver box (it's stealing CPU during solves)\n- a proper feature store, or at least stop recomputing features in three places\n- reproducible training runs — right now nobody can rebuild last quarter's model\n\ntwo ML engineers, one platform engineer at 50%", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "customer requirement doc, the part we haven't estimated:\n\n\"The System shall provide offline operation for the Planner desktop application. Planners must be able to view all routes for the current and following day, modify stop sequences, and reassign drivers while disconnected. Changes made offline must be reconciled automatically on reconnection with a clear indication of any conflict. The System shall retain at least 30 days of route history locally. Reconciliation must never silently discard a planner's change. The offline dataset shall not exceed 2 GB on disk.\"\n\nwe have none of this today and the contract is signed. i want the plan, the risks, and what we should push back on", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "ticket from design with the states enumerated, the sync indicator in the desktop titlebar:\n\nSync indicator\n- Idle: no icon, no text.\n- Syncing: 14px spinner, label \"Syncing…\" in secondary text, appears only after 400ms so quick syncs don't flash.\n- Offline: 14px cloud-slash icon, label \"Offline\", tooltip lists the number of pending changes.\n- Conflict: amber dot on the icon, label \"Needs attention\", clicking opens the conflict drawer.\n- Error: destructive icon, label \"Sync failed\", tooltip has the error and a Retry link.\n- Transitions between states fade over 150ms; the label width animates so the titlebar doesn't jump.\n- All states must be readable at 200% display scaling and must not rely on colour alone.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "accessibility ticket for the planner grid, from an actual customer complaint:\n\n\"Our dispatcher uses a screen reader and cannot use the planning grid at all. Tabbing moves focus into the grid and then it is trapped — arrow keys do nothing, and the only way out is to reload the page. Stop rows are announced as 'button' with no context. The delay column uses red and green only, which our colour-blind planner cannot distinguish. Drag and drop is the only way to reassign a stop, and there is no keyboard alternative.\"\n\nthe grid is our own component, `PlannerGrid.vue`, about 700 lines", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "モックの指示書です。配車画面の右パネルを実装してください:\n\n右パネル（幅 360px、折りたたみ可）\n- 見出しは「未割当の停車地」、件数をバッジで表示（0 件のときはバッジ非表示）。\n- 各行：住所（14px）、時間枠（12px、グレー）、右端に推定作業時間（12px）。行の高さ 56px、区切り線 1px、ホバーで背景 4%。\n- 行をドラッグするとタイムラインへ割当。ドラッグ中は行を 60% 不透明にし、ドロップ可能な車両バンドを 8% でハイライト。\n- 検索ボックスは上部に固定、入力から 200ms のデバウンス、住所・顧客名・伝票番号を対象。\n- 並び替え：時間枠が早い順 / 距離が近い順（トグル、既定は時間枠）。並び替えの状態は保存する。\n- 空状態：「未割当はありません」を中央にグレーで、上に 48px の余白。\n- パネルを折りたたむと 40px の縦タブになり、件数だけ表示。折りたたみ状態は次回起動時も維持。\n- 読み込み中：行のスケルトンを 6 件表示、スピナーは使わない。\n- エラー時：パネル上部に赤い帯で「読み込みに失敗しました」と再試行リンク（ダイアログは出さない）。\n- 200% の表示スケールでも文字が切れないこと。キーボードのみで行の選択と割当ができること。", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "ja"} -{"prompt": "partner spec for the ETA push they want, build our side:\n\nPOST to a URL they register, at most once every 30 seconds per route, only when the ETA moves by more than 2 minutes.\nbody: { route_id, vehicle_id, stops: [{ stop_id, eta, confidence, delay_minutes }], generated_at }\nauth: mutual TLS, their cert pinned; rotate without downtime twice a year\nretries: 3 attempts, exponential, then drop and count a metric — never queue indefinitely\nordering: they must be able to detect out-of-order delivery, so include a monotonically increasing sequence per route\nvolume: 900 vehicles, roughly 40 stops each, peak 08:00-10:00 local\nthey will disable the integration if we exceed 1 request per second sustained", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "schema we agreed in the design review, now needs building:\n\nCREATE TABLE route_costs (\n route_id uuid PRIMARY KEY REFERENCES routes(id) ON DELETE CASCADE,\n tenant_id uuid NOT NULL,\n distance_m bigint NOT NULL,\n drive_seconds bigint NOT NULL,\n service_seconds bigint NOT NULL,\n fuel_cents bigint NOT NULL,\n labour_cents bigint NOT NULL,\n toll_cents bigint NOT NULL DEFAULT 0,\n computed_at timestamptz NOT NULL,\n inputs_hash text NOT NULL\n);\n\ncosts are computed after a route is closed, from the vehicle's cost profile and the actual telemetry, and recomputed if telemetry arrives late. the recompute must be idempotent and must not fire the downstream reporting webhook twice for the same inputs_hash.", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "depot marker icon is the wrong asset", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "core", "lang": "en"} -{"prompt": "rustls to 0.23.14", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "core", "lang": "en"} -{"prompt": "csv export is missing the tenant column", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "matrix cache TTL back to 60 minutes", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "core", "lang": "en"} -{"prompt": "el tooltip dice «kilometros», falta la tilde", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "core", "lang": "es"} -{"prompt": "drop jupyterlab from the trainer image", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "lifecycle rule on the checkpoint bucket", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "unused `watchEffect` import in RouteMap", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "boundary", "lang": "en"} -{"prompt": "teamId belongs in the notarize block", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "dead letter threshold from 3 to 10", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "boundary", "lang": "en"} -{"prompt": "Feature-Flag `live_eta` in Staging aktivieren", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "boundary", "lang": "de"} -{"prompt": "a colleague's benchmark says the solver rewrite is a 65% improvement and the large-instance regression is \"a tuning issue\", and i'm not equipped to argue. look at the numbers and the code together and tell me whether the allocation explosion on big instances is inherent to the new approach or genuinely something we can tune away", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "our route map redraws every marker on every telemetry tick, which at 900 vehicles means the planner's fan spins up and the map stutters whenever anything moves. keep the visual result identical but only update what changed, and while you're in there the cluster expansion animation should not restart when an unrelated vehicle updates", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "the electron main process registers thirteen ipc handlers that each open with the same timing, try/catch and logging boilerplate, and two of them get the error shape subtly wrong so the renderer treats a failure as success. collapse them onto one registration helper with the current behaviour preserved, then make the two odd ones consistent with the rest", "purpose": "refactor", "secondary": "quickFix", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "late stops should be hatched, not red", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "collapse the right panel to a tab", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "loss curves need a log-scale toggle", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "タイトルバーの同期アイコンを小さくして", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "ja"} -{"prompt": "delay column needs an icon too", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "timeline jumps when the label widens", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "`TripPlanner` should be `RoutePlanner`", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "extract the guard clause from the handlers", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "split build_features into steps", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "les quatre classes de config, une seule", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "fr"} -{"prompt": "pull the retry policy into one helper", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "inline `asLatLng`, single caller now", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "move the ipc handlers into one registrar", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "docstrings for the telemetry proto fields", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "release notes for desktop 2.9", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "kurzer Blogpost über die neue Routenansicht", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "de"} -{"prompt": "man page for `fleetctl solve`", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "document the 409 on /v1/assignments", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "changelog line for the ETA webhook", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "quién llama a `RouteService.close`?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "es"} -{"prompt": "safe to expose `force` to partners?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "walk me through the claim TTL logic", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "does the shuffle buffer cross shards?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "ETAs drift after midnight UTC", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "warum verliert der Gateway alle 60s die Verbindung?", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "de"} -{"prompt": "webhook endpoint for driver check-ins", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "design the cost pipeline, then build the writer", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "map out the offline story, then start on storage", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "back to the routing thing", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "unbreak it", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "proceed", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "lo de siempre con las rutas", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "es"} -{"prompt": "make the numbers look better", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "pick up the depot work", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "another pass on the solver", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "whatever is quickest", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "次のスプリントの分、よろしく", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "ja"} -{"prompt": "tidy up before the demo", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "faz aquilo dos relatórios", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "pt"} -{"prompt": "one more look at this", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "live ETA push to a customer's own app is the thing that wins us the 900-vehicle account, and we've never pushed anything to anyone. i want to think through the transport, the fan-out, what we do when their endpoint is down for an hour, and how we avoid melting our own database recomputing ETAs every thirty seconds for forty thousand stops", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "per-route cost has been asked for by finance three quarters running and every time we discover another input we don't have — tolls, driver overtime bands, fuel prices that vary by depot, and vehicle depreciation that accounting computes differently from us. work out what a first version could honestly claim to measure, and what it would take to make it defensible", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "reproducibility of training runs is embarrassing: nobody can rebuild last quarter's model, the data snapshot isn't versioned, and the config that produced it lives in someone's shell history. lay out what we'd need — data versioning, run tracking, environment pinning — in an order where each step is useful on its own rather than a six-month platform project", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "breakdown reassignment is twenty minutes of manual work today and ops want it automatic, which sounds simple until you consider that stops have time windows, some drivers aren't certified for refrigerated loads, and the customer app has already told recipients an ETA. sketch how automatic reassignment should behave, including when it should refuse and ask a human", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "splitting dispatch out of the monolith keeps coming up and i want a position before the next architecture review. specifically: whether the shared tenants table is a blocker, what the event stream would need to guarantee, and whether we'd end up with a distributed monolith given how much assignment reads join route data", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "boundary", "lang": "en"} -{"prompt": "partners integrate against three endpoints and the only real documentation is a postman collection someone exported in 2024. write the integration guide: authentication, the assignment lifecycle, what each status means, idempotency, retry expectations, and a worked example from creating a route to receiving the completion webhook", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "solver has three strategies and the only place their differences are recorded is a comment that says \"guided is usually better\". document what each one does, when to use it, what the time limit means for each, and the fact that exhaustive is unusable past two hundred stops — for engineers, not for customers", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "telemetry ingest API is documented as \"see the proto file\", which is not documentation. write the reference: endpoint, auth, batching limits, what happens when the device clock is wrong, which fields are optional in practice versus in the schema, and the error codes with what a device should do about each", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "prospect's security team asked for our data flow documentation and we don't have any. from the code, work out what leaves our network — the geocoder, the traffic provider, the notification vendor — what fields go to each, and write it up in a form a security reviewer would accept", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "coordinate conversion helpers have drifted between the three packages and the desktop one rounds to six decimals on purpose, which nobody knew until today. consolidate them into the shared package with the rounding as an explicit option, update every call site, and keep the map SDK working exactly as it does now", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "nobody has been able to tell me what the solver does when two vehicles could serve the same stop at the same cost, and the tie-breaking matters for a customer who says their routes are non-deterministic. read the insertion and local-search code and explain the actual behaviour", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "gradle config aside, our CI is slow because the trainer image rebuilds torch every run, and i'd like both the diagnosis and the fix in one go — work out where the forty minutes actually goes, then restructure the workflow and the dockerfile so it's cached properly", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "we've agreed to do monthly retraining but not how, and the pipeline has to exist before october. i want the design for the whole loop first — data snapshot, training, evaluation gates, promotion — and then the snapshot step implemented so the data team can start using it", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "desktop app needs an offline mode and the contract says so, but the shape isn't decided. think it through with me — what we cache, how conflicts surface to the planner, the 2GB budget — and then set up the local schema so the sync work can start behind it", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "das Zusammenspiel von Solver und Queue ist nirgends beschrieben und gleichzeitig ziemlich verworren. Ich hätte gern erst ein Konzept, wie die Zuständigkeiten sauber getrennt wären, und danach den ersten Umbauschritt am Worker", "purpose": "planning", "secondary": "refactor", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "de"} -{"prompt": "partner-facing docs and our actual API have drifted far enough that support answers questions by reading code. write the corrected reference for the three public endpoints, and fix the two response payloads where the API is genuinely wrong rather than the docs", "purpose": "writing", "secondary": "quickFix", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "runbook for a stuck solve queue is one line and the real procedure lives in two people's heads. write the proper page — the checks, the release command, when to escalate — and add the `queue peek --stuck` output format to the CLI docs while you're there", "purpose": "writing", "secondary": "backendImpl", "mixed": true, "difficulty": 0.5, "slice": "mixed", "lang": "en"} -{"prompt": "escreve a documentação do endpoint de telemetria para os parceiros e, já agora, valida no código se os campos opcionais que documentamos são mesmo opcionais — desconfio que dois deles são obrigatórios na prática", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.55, "slice": "mixed", "lang": "pt"} -{"prompt": "ipc layer has thirteen near-identical handlers and no documentation of what a handler is allowed to do. collapse them into one registration helper, then write the short contributor note explaining how to add a new one", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.55, "slice": "mixed", "lang": "en"} -{"prompt": "i'd like an honest read of whether our assignment endpoint is safe under concurrent dispatchers — the existsBy check followed by a save looks like a classic race — and if it is broken, the fix with a test that fails without it", "purpose": "review", "secondary": "backendImpl", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "there are two ways to construct a `Route` in the java service, a builder and a static factory, and half the code uses each", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "python package has utils.py, helpers.py and common.py, which between them contain forty functions and no organising principle", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "quick sanity check on the electron preload script before we ship it to customers who load a third-party map SDK in the renderer", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "someone should explain what our model actually predicts before the customer call tomorrow, in terms that survive a procurement questionnaire", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "is the coverage number we're about to report to management meaningful given that our two most incident-prone modules are at zero?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "what guarantees does our telemetry ingest actually make about ordering, and is that written down anywhere a partner could read?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "before i extend the assignment API, a plain description of what the `force` flag does today and which clients rely on it", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "docs/architecture.md describes a synchronous solve that we replaced eighteen months ago, bring it in line with the queue-based flow", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "write the deprecation notice for the v0 telemetry endpoint, including the sunset date and what devices need to do", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "`--emit-intermediate` flag prints to stderr but the man page says stdout, and one of the two is wrong", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "vue linter complains about mutating the `stops` prop in two components, and in one of them it genuinely is a bug", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "vehicle band drag handler fires twice on trackpads, once from pointerup and once from click, and the stop lands in the wrong band", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "we need a testing strategy for the solver that isn't \"run it and see\", given that outputs are heuristic and change with every tuning pass", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "multi-depot fleets that share vehicles on fridays can't be modelled at all today, and two customers now need it — what's the smallest data model change that makes it possible?", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "an endpoint that returns a route's cost breakdown, computed on read from the stored components, cached until the telemetry changes", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "driver check-in needs to record depot vs on-route state, from the mobile app's geofence events, with a manual override for the dispatcher", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "same solve job can be claimed twice if a worker's heartbeat is late, so claims need a fencing token rather than a TTL alone", "purpose": "backendImpl", "secondary": "review", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "you pick, something small", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "vague-eval", "lang": "en"} -{"prompt": "planner grid renders every vehicle band eagerly, so a fleet with 400 vehicles takes eleven seconds to open and then scrolls at about four frames a second on the machines our customers actually use, which are five-year-old windows laptops docked to two monitors. virtualise it, keep the drag-and-drop working across the virtualised boundary, and don't change how it looks at 40 vehicles", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "training dashboard is three matplotlib images regenerated by a cron job and pasted into a static page, which is why nobody looks at it. build it properly in the web app: loss and validation curves with a log-scale toggle, a run selector that can overlay two runs, hyperparameters in a side panel, and a link to the checkpoint in object storage", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "conflict drawer is a placeholder that says \"3 conflicts\" and nothing else, which is worse than useless to a planner deciding whether to keep their change or the server's. show each conflict as a field-level comparison with the two values, who made the other change and when, and a per-conflict choice, defaulting to nothing so an accidental click can't discard work", "purpose": "frontendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "i've been asked to sign off on the assignment service before it goes to the customer with 900 vehicles, and my worry is what happens under concurrent dispatchers, but i also don't want to review it on vibes. go through the transaction boundaries, the existence check before save, the event publish and the notification call, and tell me which of those can leave inconsistent state", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "our data loader shuffles inside a buffer per worker, and validation loss has been suspiciously smooth for three weeks, which makes me think we're leaking ordering into the batches somehow. read the loader, the sharding and the sampler together and tell me whether the shuffle is doing what a person would assume from the name", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "there's a paragraph in the architecture doc about asynchronous solves that gets quoted in every design discussion, and i suspect at least half of it stopped being true when we removed the input hash in march. check each claim in it against the code and tell me which ones survive, because people are making decisions on this", "purpose": "review", "secondary": "writing", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "assignment, route and trip are used interchangeably across the java service and mean different things depending on the file, with two of them exactly swapped relative to what the public API calls them. rename everything internal to match the API vocabulary, leave the serialised field names alone, and split it into commits a reviewer can actually follow", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "stop sequence numbers get recalculated in the planner grid, in the mapper that reads solver output, and again in the mobile app's local model, and the three implementations have quietly drifted, which is why a stop occasionally shows as number seven in one place and eight in another. one implementation, shared, with the current server behaviour as the reference", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "error responses across the API are a museum: the oldest endpoints return a bare string, the middle ones return `{\"error\": \"...\"}`, and the newest return problem details with a type URI. bring them all to the newest shape without changing a single status code, and keep the string form working for the two partners who parse it, behind a header if that's cleanest", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "feature construction exists three times — in the training script, in the offline evaluation script, and in the inference service — and they have drifted enough that a model scores differently depending on which path builds its inputs. bring them onto one implementation with the training version as the source of truth, and prove the other two produce identical outputs on a sample", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "deployment guide for the routing service stops at \"run the migration\" and says nothing about rollback, which matters because the last two rollbacks were improvised at two in the morning. write the full procedure including the pre-deploy checks, the migration order, what to do when the solver queue has in-flight claims, and how to roll back once the new schema has been written to", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "public status page lists three components with no descriptions and four incident severities that nobody can distinguish, so we've had customers escalate a degraded-performance notice as an outage. write the component descriptions and the severity definitions in language a fleet manager understands, with an example of what each severity feels like from their side", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "we're deprecating the v0 telemetry endpoint in six months and roughly 12,000 devices still use it, most of them on firmware we can't remotely update. write the deprecation notice for the docs, the email to fleet operators explaining what they need to do and by when, and the short internal note about which customers will need hand-holding", "purpose": "writing", "secondary": "planning", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "the CLI's man page has been wrong since at least version 2: it documents `--emit-intermediate` as writing to stdout when the binary writes to stderr, it never mentions that exhaustive search is impractical past two hundred stops, and the default time limit changed last year. fix the page against the actual behaviour, and where the behaviour is the wrong one, say so rather than documenting the bug", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "health endpoint returns 200 whenever the process is up, which is how we managed to have a completely stalled solve queue for forty minutes while every dashboard was green. it should check the worker heartbeat and the queue depth, fail when nothing has been claimed in five minutes, and keep the response cheap enough to be hit every two seconds by the load balancer", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "a fleet reported that route costs were missing for three tenants after last tuesday's nightly run, and the job reported success, which means our error handling swallowed something. no alert fired, nothing in sentry, and the only trace is the absence of rows. work out how a tenant can be skipped silently and what the job would have to log for us to catch it next time", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "stop-level ETAs are recomputed on every read, which is fine at our current size and won't be once the ETA push exists, and separately the reporting team wants the history of what we predicted versus what happened. persist them with a sensible retention, keep reads fast, and think about whether history belongs in the same table before you write anything", "purpose": "backendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "how should the partner API be versioned once the ETA push exists? we have three endpoints in the wild, two partners who never upgrade anything, and a push integration where the version has to be negotiated rather than requested. i'd like a recommendation with the reasoning, plus what it means for the endpoints we already shipped without a version at all", "purpose": "planning", "secondary": "writing", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "testing the solver is currently \"run it and look at the numbers\", which is why every tuning pass costs a week of nervous manual checking. i want a strategy that gives us confidence without pretending heuristic output is deterministic — golden instances with quality bounds, invariant checks, performance regression gates, whatever fits — and a view on what we'd run per commit versus nightly", "purpose": "planning", "secondary": "review", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} +{"prompt":"CalderaKiteSchedulerStore's FilterDrawer.vue needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Ist CalderaCinderAuthStore sicher?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"de"} +{"prompt":"What sequence would let CalderaOrbitSyncService adopt Swift 6 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.8,"slice":"core","lang":"en"} +{"prompt":"Two asks around CalderaDriftConsoleCoordinator: (1) separate CalderaDriftConsoleCoordinator's policy from transport without behavior changes; (2) capture the contract and rollback note for consumers. Do not introduce another runtime dependency, 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":"Renderer: Ticket OPS-43138: retire the legacy replay path for CalderaBeaconStoreFlow\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 CalderaBeaconStoreFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"CalderaWrenExportCoordinator: give it a nicer flow","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"CalderaAmberFilterStore's staging timeout is already known to be wrong: change the single projects/caldera/Sources/App/SessionStore.swift value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Indexer: The CalderaCedarPolicyStore empty state in projects/caldera/web/components/FilterDrawer.vue needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-43123\n\n08:02 deploy CalderaBasilRunnerFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current CalderaBasilRunnerFlow 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":"Architect a gradual ownership transfer for CalderaFernSnapshotStore 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":"// projects/caldera/cmd/exporter/main.py\nfinal class CalderaSableParserFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 CalderaSableParserFlow; 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":"Cadre la migration de CalderaDriftConsoleStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"fr"} +{"prompt":"Apparently: diff --git a/projects/caldera/cmd/exporter/main.py b/projects/caldera/cmd/exporter/main.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/cmd/exporter/main.py\n+++ b/projects/caldera/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\nRead the artifact above as a skeptical reviewer. Is CalderaHarborIndexCoordinator'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":"Fresh release brief for CalderaNimbusFormCoordinator:\n- primary outcome: assess ownership and failure handling in projects/caldera/packages/api/openapi.yaml\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/caldera/packages/api/openapi.yaml\n- platform constraint: gRPC\n- known complication: out-of-order events after consumer rebalancing\n\nBoth results are required, but they should remain independently reviewable. Do not introduce another runtime dependency; 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.8,"slice":"mixed","lang":"en"} +{"prompt":"CalderaBirchMigratorCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Lately: We expect CalderaMoonlitSDKStore to outgrow its current FastAPI 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- do not introduce another runtime dependency\n- stay compatible with the existing FastAPI deployment\n- keep the work scoped to CalderaMoonlitSDKStore and its direct tests\n\nThe relevant code crosses embedded, Go services, 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":"I inherited CalderaPrismCacheService and need a careful read of projects/caldera/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- do not introduce another runtime dependency\n- stay compatible with the existing gRPC deployment\n- keep the work scoped to CalderaPrismCacheService and its direct tests\n\nThe relevant code crosses embedded, Go services, Android. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Corrige le timeout de CalderaCinderAuthService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"fr"} +{"prompt":"CalderaBeaconStoreService's staging timeout is already known to be wrong: change the single projects/caldera/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":"The destination for CalderaGarnetModalStore is broadly agreed; the missing piece is a reversible route from projects/caldera/ui/settings/PrivacyPane.tsx to that target. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside CalderaGarnetModalStore\n- do not introduce another runtime dependency\n\nSeveral teams work in this embedded, Go services, Android monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Support wants the behavior in projects/caldera/ml/pipeline/features.py recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"One contained cleanup in projects/caldera/cmd/exporter/main.py: remove the obsolete CalderaHarborIndexStore import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Please resist widening this one: CalderaRavenSessionStore works, but staging still carries a setting that production corrected last month. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside CalderaRavenSessionStore\n- do not introduce another runtime dependency\n\nSeveral teams work in this embedded, Go services, Android monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-43155: finish the compact CalderaCraneWorkspaceCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/caldera/config/staging.toml\nFramework: gRPC\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 CalderaCraneWorkspaceCoordinator'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":"projects/caldera/config/staging.toml 里的 CalderaIrisBatchService 最近在 gRPC 流程中出现间歇性问题。 请写一份面向调用方的说明，包含 contract、错误、retry 和可复制示例，不要改 handler。\n\n约束：\n- 继续使用 gRPC\n- 保持兼容性和取消语义\n- 改动只限于 CalderaIrisBatchService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"zh"} +{"prompt":"This should remain a deliberately small patch: CalderaHarborIndexService has one known configuration mistake in projects/caldera/ml/pipeline/features.py, not an open-ended failure investigation. Correct the known literal and the test that intentionally mirrors it; the final diff should stay local enough for an on-call engineer to verify at a glance.\n\nConstraints:\n- do not introduce another runtime dependency\n- stay compatible with the existing OpenTelemetry deployment\n- keep the work scoped to CalderaHarborIndexService and its direct tests\n\nThe relevant code crosses embedded, Go services, 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":"CalderaFernSnapshotCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"For CalderaEchoRegistryCoordinator, separate CalderaEchoRegistryCoordinator's policy from transport without behavior changes; once that is complete, give the existing implementation a read-only safety pass. Work from projects/caldera/Sources/CLI/Commands/Doctor.swift, stay with OpenTelemetry, and do not introduce another runtime dependency. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"CalderaSlateEditorCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"CalderaCinderAuthCoordinator: restructure, then correct","purpose":"refactor","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"CalderaBeaconStoreCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"CalderaOrbitSyncCoordinator: sort out the rough edge","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"# CI job 43116: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: OpenTelemetry\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] CalderaRavenSessionFlowIntegration.replays_after_timeout ... ok\n[test] CalderaRavenSessionFlowIntegration.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 \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\nWire CalderaRavenSessionFlow'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":"diff --git a/projects/caldera/lib/codec/frame.cc b/projects/caldera/lib/codec/frame.cc\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/lib/codec/frame.cc\n+++ b/projects/caldera/lib/codec/frame.cc\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure CalderaPineMetricsFlow 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":"Split projects/caldera/services/ledger/replay.go by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"The behavior of CalderaCraneWorkspaceService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/caldera/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- do not introduce another runtime dependency\n- retain the current gRPC operational envelope\n\nThis repository spans embedded, Go services, Android; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"En projects/caldera/ui/settings/PrivacyPane.tsx, CalderaAsterWebhookService tiene un problema intermitente en el flujo de Room. La causa ya está clara: cambia solo el timeout de staging de 15 a 30 segundos y ajusta su assertion.\n\nRestricciones:\n- seguir con Room\n- conservar compatibilidad y cancelación\n- limitar el cambio a CalderaAsterWebhookService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"es"} +{"prompt":"Oddly: diff --git a/projects/caldera/packages/api/openapi.yaml b/projects/caldera/packages/api/openapi.yaml\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/packages/api/openapi.yaml\n+++ b/projects/caldera/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\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Read the artifact above as a skeptical reviewer. Is CalderaFernSnapshotFlow'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":"Currently: projects/caldera/ml/pipeline/features.py の CalderaHarborIndexFlow で、OpenTelemetry の flow に断続的な問題が起きています。 responsive layout、empty/retry state、keyboard focus、dark mode、reduced motion を仕上げてください。\n\n制約:\n- OpenTelemetry を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は CalderaHarborIndexFlow のみ","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"} +{"prompt":"Test Suite 'CalderaPrismCacheFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[CalderaPrismCacheFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/caldera/crates/index/src/segment.rs:144: error: -[CalderaPrismCacheFlowTests 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 '-[CalderaPrismCacheFlowTests 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 CalderaPrismCacheFlow'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":"Compare the old and new CalderaCraneWorkspaceStore 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":"CalderaCedarPolicyCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Today: Is there a cleaner way to separate CalderaCraneWorkspaceFlow'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":"Dedupe CalderaKiteSchedulerService's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Support wants the behavior in projects/caldera/apps/console/routes/usage.svelte recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"# CI job 43122: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: Swift 6\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] CalderaSpruceDaemonFlowIntegration.replays_after_timeout ... ok\n[test] CalderaSpruceDaemonFlowIntegration.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 \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\nReconstruct the CalderaSpruceDaemonFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Architect a gradual ownership transfer for CalderaOpalRouterFlow 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":"CalderaPrismCacheCoordinator is blocking the next release because a misleading timeout name used in five packages. I need two concrete outcomes from a single pass: ship the idempotent CalderaPrismCacheCoordinator replay endpoint, and capture the contract and rollback note for consumers. Use the existing gRPC conventions in projects/caldera/pkg/cache/lease.rs; do not introduce another runtime dependency. 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":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"CalderaWillowCodecCoordinator needs a paired pass: produce a consumer guide for CalderaWillowCodecCoordinator, plus give the existing implementation a read-only safety pass. Use projects/caldera/config/staging.toml as the source of truth, preserve the gRPC contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Two deliverables are holding up CalderaSableParserCoordinator. First, separate CalderaSableParserCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/caldera/ml/pipeline/features.py, which follows OpenTelemetry conventions and currently suffers from stale cursors when a page is resumed. Do not introduce another runtime dependency.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"CalderaJuniperCLICoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"PM is preparing the CalderaTideWorkerService 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 CalderaTideWorkerService\n- do not introduce another runtime dependency\n\nSeveral teams work in this embedded, Go services, 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":"Context: The data is already available in projects/caldera/internal/auth/refresh.go; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"A flaky failure around CalderaDeltaCanvasService survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. Reconstruct the failing timeline from logs and tests, identify which invariant first breaks, and distinguish causal signals from effects or cleanup noise.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside CalderaDeltaCanvasService\n- do not introduce another runtime dependency\n\nSeveral teams work in this embedded, Go services, Android monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Why does CalderaOpalRouterStore's Swift 6 worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Background: projects/caldera/src/sync/reconcile.ts now contains CalderaQuartzPlayerStore'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.4,"slice":"core","lang":"en"} +{"prompt":"Collapse the CalderaMosaicGridStore wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Question: The behavior of CalderaNovaPickerService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/caldera/lib/codec/frame.cc. 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- do not introduce another runtime dependency\n- retain the current Room operational envelope\n\nThis repository spans embedded, Go services, Android; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Design handed over a final pass for CalderaCloudReconcilerService, and the basic data flow in projects/caldera/internal/auth/refresh.go already works. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- do not introduce another runtime dependency\n- stay compatible with the existing FastAPI deployment\n- keep the work scoped to CalderaCloudReconcilerService and its direct tests\n\nThe relevant code crosses embedded, Go services, Android. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Does CalderaEmberRelayStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Before touching projects/caldera/crates/index/src/segment.rs, 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.9,"slice":"core","lang":"en"} +{"prompt":"Introduce a durable deduplication key for CalderaBeaconStoreStore 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":"# projects/caldera/src/sync/reconcile.ts\n[worker.calderasummitproxyflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.calderasummitproxyflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.calderasummitproxyflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.CalderaSummitProxyFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-43132\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/caldera/src/sync/reconcile.ts. 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":"Observation: The first CalderaAcornWidgetStore request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Constraint: # projects/caldera/workers/thumbnail/consumer.ex\n[worker.calderagarnetmodalflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.calderagarnetmodalflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.calderagarnetmodalflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.CalderaGarnetModalFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-43113\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 CalderaGarnetModalFlow'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":"Two asks around CalderaMosaicGridCoordinator: (1) produce a consumer guide for CalderaMosaicGridCoordinator; (2) give the existing implementation a read-only safety pass. Do not introduce another runtime dependency, and leave a clear boundary between the resulting artifacts or edits.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"CalderaSpruceDaemonCoordinator: restructure, then correct","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Clarify CalderaSpruceDaemonService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"CalderaFrostPanelCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Ticket OPS-43136: retire the legacy replay path for CalderaAmberFilterFlow\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 CalderaAmberFilterFlow 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":"Request: # projects/caldera/pkg/cache/lease.rs\n[worker.calderawrenexportflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.calderawrenexportflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.calderawrenexportflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.CalderaWrenExportFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-43140\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 CalderaWrenExportFlow'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":"For CalderaSummitProxyCoordinator, ship the idempotent CalderaSummitProxyCoordinator replay endpoint; once that is complete, give the existing implementation a read-only safety pass. Work from projects/caldera/db/migrations/20260730_events.sql, stay with Swift 6, and do not introduce another runtime dependency. Keep the two outcomes separately reviewable.","purpose":"backendImpl","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"CalderaMarbleTokenCoordinator needs a paired pass: lay out a staged migration for CalderaMarbleTokenCoordinator, plus consolidate the duplicated normalization paths without changing behavior. Use projects/caldera/ml/pipeline/features.py as the source of truth, preserve the OpenTelemetry contract, and avoid unrelated cleanup.","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"CalderaRainfallDBStore needs an idempotent replay endpoint backed by gRPC; accept a cursor, cap each page at 500 items, and return a stable continuation token.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"The CalderaCoralUploadService empty state in projects/caldera/web/components/FilterDrawer.vue needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Fresh release brief for CalderaDeltaCanvasCoordinator:\n- primary outcome: separate CalderaDeltaCanvasCoordinator's policy from transport without behavior changes\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/caldera/db/migrations/20260730_events.sql\n- platform constraint: Swift 6\n- known complication: cancellation being swallowed at the repository boundary\n\nBoth results are required, but they should remain independently reviewable. Do not introduce another runtime dependency; 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":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"projects/caldera/workers/thumbnail/consumer.ex 里的 CalderaFrostPanelStore 最近在 Room 流程中出现间歇性问题。 请写一份面向调用方的说明，包含 contract、错误、retry 和可复制示例，不要改 handler。\n\n约束：\n- 继续使用 Room\n- 保持兼容性和取消语义\n- 改动只限于 CalderaFrostPanelStore","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"zh"} +{"prompt":"Why is CalderaLumenChartStore stalling?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Outline a safer CalderaFlintTimelineService cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Rename CalderaSummitProxyService's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Incident timeline — INC-43131\n\n08:02 deploy CalderaMarbleTokenFlow 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 CalderaMarbleTokenFlow, 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":"Split CalderaBirchMigratorStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Decouple CalderaSummitProxyStore's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Clarify CalderaMapleQueueStore's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Give CalderaAsterWebhookStore'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":"Release verification found a single stale CalderaNimbusFormStore 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- do not introduce another runtime dependency\n- retain the current gRPC operational envelope\n\nThis repository spans embedded, Go services, 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":"Trace CalderaMarbleTokenService's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"CalderaMapleQueueCoordinator needs a paired pass: finish CalderaMapleQueueCoordinator's responsive empty and retry states, plus capture the contract and rollback note for consumers. Use projects/caldera/engine/render/atlas.cpp as the source of truth, preserve the Room contract, and avoid unrelated cleanup.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Our support and SDK teams keep answering the same questions about CalderaGarnetModalService, but the current prose in projects/caldera/workers/thumbnail/consumer.ex 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- do not introduce another runtime dependency\n- stay compatible with the existing Room deployment\n- keep the work scoped to CalderaGarnetModalService and its direct tests\n\nThe relevant code crosses embedded, Go services, 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":"We expect CalderaFlintTimelineStore to outgrow its current Swift 6 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- do not introduce another runtime dependency\n- stay compatible with the existing Swift 6 deployment\n- keep the work scoped to CalderaFlintTimelineStore and its direct tests\n\nThe relevant code crosses embedded, Go services, 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":"Pin CalderaBasilRunnerStore's Room dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-43154: retire the legacy replay path for CalderaCloudReconcilerCoordinator\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 CalderaCloudReconcilerCoordinator 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":"Store CalderaMapleQueueService's delivery receipts","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-43115\n\n08:02 deploy CalderaNimbusFormFlow 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 CalderaNimbusFormFlow 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":"Sequence CalderaBasilRunnerService's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Map CalderaEchoRegistryService's ownership split","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Goal: Two asks around CalderaEmberRelayCoordinator: (1) change CalderaEmberRelayCoordinator's known staging timeout from 15 to 30 seconds; (2) capture the contract and rollback note for consumers. Do not introduce another runtime dependency, and leave a clear boundary between the resulting artifacts or edits.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"diff --git a/projects/caldera/src/sync/reconcile.ts b/projects/caldera/src/sync/reconcile.ts\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/src/sync/reconcile.ts\n+++ b/projects/caldera/src/sync/reconcile.ts\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure CalderaDeltaCanvasFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Test Suite 'CalderaLumenChartFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[CalderaLumenChartFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/caldera/pkg/cache/lease.rs:144: error: -[CalderaLumenChartFlowTests 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 '-[CalderaLumenChartFlowTests 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 CalderaLumenChartFlow'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":"Does CalderaLedgerGateStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"CalderaAmberFilterCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"CalderaQuartzPlayerCoordinator: could this be clearer","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"CalderaPineMetricsCoordinator: polish the last piece","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump CalderaMoonlitSDKService's timeout to 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Symptom: // projects/caldera/infra/modules/edge/main.tf\nfinal class CalderaMoonlitSDKFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 CalderaMoonlitSDKFlow; 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":"Pin CalderaWillowCodecService's gRPC dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Two deliverables are holding up CalderaMoonlitSDKCoordinator. First, change CalderaMoonlitSDKCoordinator's known staging timeout from 15 to 30 seconds. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/caldera/internal/auth/refresh.go, which follows FastAPI conventions and currently suffers from a deadlock that appears only during shutdown. Do not introduce another runtime dependency.\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":"quickFix","secondary":"debugging","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"The first CalderaOspreyJobFlow request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"How should CalderaSpruceDaemonStore be decomposed?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"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_43121'\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_43121'::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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Determine why CalderaBirchMigratorFlow 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":"Give CalderaNimbusFormService a loading skeleton","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Headsup: Ticket OPS-43158: retire the legacy replay path for CalderaNovaPickerCoordinator\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for CalderaNovaPickerCoordinator, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"What does CalderaMosaicGridService own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"CalderaLedgerGateCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"projects/caldera/apps/console/routes/usage.svelte has grown through several launches, and CalderaOpalRouterService now mixes policy, transport, persistence, and metrics in one place. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- do not introduce another runtime dependency\n- stay compatible with the existing Swift 6 deployment\n- keep the work scoped to CalderaOpalRouterService and its direct tests\n\nThe relevant code crosses embedded, Go services, Android. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Could the reasoning behind CalderaTideWorkerFlow's OpenTelemetry choices be captured as an ADR for engineers joining the project next quarter? The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Read projects/caldera/engine/render/atlas.cpp and tell me whether CalderaPineMetricsStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"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_43149'\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_43149'::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\nReconstruct the CalderaCedarPolicyFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Em projects/caldera/packages/api/openapi.yaml, o CalderaIrisBatchStore tem um problema intermitente no fluxo de gRPC. Leia o fluxo atual e avalie ownership, cancelamento e ordem; preciso apenas da análise.\n\nRestrições:\n- continuar com gRPC\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao CalderaIrisBatchStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"pt"} +{"prompt":"FYI: # projects/caldera/services/ledger/replay.go\n[worker.calderakiteschedulerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.calderakiteschedulerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.calderakiteschedulerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.CalderaKiteSchedulerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-43129\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Make the one confirmed configuration correction in projects/caldera/services/ledger/replay.go. 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":"In projects/caldera/cmd/exporter/main.py hat CalderaSableParserService ein sporadisches Problem im OpenTelemetry-Ablauf. Trenne Verantwortlichkeiten und entferne Duplikate, ohne API, Wire-Werte, Reihenfolge oder sichtbares Verhalten zu ändern.\n\nRandbedingungen:\n- OpenTelemetry weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf CalderaSableParserService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um CalderaSableParserService mit OpenTelemetry kompatibel.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} +{"prompt":"CalderaAtlasSearchCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"CalderaPineMetricsService 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":"Match CalderaVelaDrawerStore's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"# CI job 43143: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: Room\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] CalderaFrostPanelFlowIntegration.replays_after_timeout ... ok\n[test] CalderaFrostPanelFlowIntegration.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 \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\nReconstruct the CalderaFrostPanelFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Clarify CalderaVelaDrawerService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Please turn CalderaJuniperCLIStore's existing tests into a short contract reference, covering pagination, malformed input, authorization, and retry semantics without copying test code. The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"CalderaMicaProfileCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Meanwhile: Incident timeline — INC-43159\n\n08:02 deploy CalderaOspreyJobCoordinator 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 CalderaOspreyJobCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Ticket OPS-43146: retire the legacy replay path for CalderaLedgerGateFlow\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 CalderaLedgerGateFlow 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":"Set CalderaEchoRegistryStore's port to 8081","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"CalderaDriftConsoleService é seguro?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"pt"} +{"prompt":"Two asks around CalderaVelaDrawerCoordinator: (1) assess ownership and failure handling in projects/caldera/pkg/cache/lease.rs; (2) capture the contract and rollback note for consumers. Do not introduce another runtime dependency, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Production says CalderaOspreyJobStore is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current FastAPI operational envelope\n\nThis repository spans embedded, Go services, Android; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"projects/caldera/engine/render/atlas.cpp has grown through several launches, and CalderaNovaPickerStore now mixes policy, transport, persistence, and metrics in one place. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- do not introduce another runtime dependency\n- stay compatible with the existing Room deployment\n- keep the work scoped to CalderaNovaPickerStore and its direct tests\n\nThe relevant code crosses embedded, Go services, Android. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"CalderaLumenChartCoordinator: sequence, then polish","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"CalderaCoralUploadCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"The name pendingAck means two different things across CalderaAtlasSearchService's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Read projects/caldera/Sources/CLI/Commands/Doctor.swift and tell me whether CalderaTideWorkerStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Any races in CalderaMicaProfileStore?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-43125\n\n08:02 deploy CalderaWillowCodecFlow 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 CalderaWillowCodecFlow, 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":"Bring CalderaAsterWebhookFlow'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":"Locally: 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_43135'\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_43135'::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\nFind the source of this CalderaIrisBatchFlow symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Set CalderaLumenChartService's port to 8081","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-43117\n\n08:02 deploy CalderaFlintTimelineFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current CalderaFlintTimelineFlow 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":"Add a bounded CalderaNovaPickerFlow export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-43137: retire the legacy replay path for CalderaOrbitSyncFlow\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. Assess CalderaOrbitSyncFlow 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":"CalderaFlintTimelineCoordinator: correct, then assess","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Production: Incident timeline — INC-43119\n\n08:02 deploy CalderaCinderAuthFlow 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 CalderaCinderAuthFlow 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":"Staging: The data is already available in projects/caldera/Sources/CLI/Commands/Doctor.swift; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"CI: Incident timeline — INC-43147\n\n08:02 deploy CalderaJuniperCLIFlow 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 CalderaJuniperCLIFlow 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":"Atlas: Incident timeline — INC-43130\n\n08:02 deploy CalderaVelaDrawerFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nDetermine why CalderaVelaDrawerFlow 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":"Test Suite 'CalderaEmberRelayFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[CalderaEmberRelayFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/caldera/internal/auth/refresh.go:144: error: -[CalderaEmberRelayFlowTests 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 '-[CalderaEmberRelayFlowTests 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\nFinish the visible CalderaEmberRelayFlow 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":"Nobody is asking for code changes yet; we first need to understand whether the current CalderaOspreyJobService 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 CalderaOspreyJobService\n- do not introduce another runtime dependency\n\nSeveral teams work in this embedded, Go services, 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":"Ownership of CalderaCopperBridgeService 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- do not introduce another runtime dependency\n- retain the current Swift 6 operational envelope\n\nThis repository spans embedded, Go services, 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":"CalderaCloudReconcilerFlow's staging timeout is already known to be wrong: change the single projects/caldera/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":"CalderaAcornWidgetCoordinator: handle the lingering thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"How does CalderaFernSnapshotService propagate cancellation through the gRPC boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"The name pendingAck means two different things across CalderaLedgerGateService's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"CalderaBasilRunnerCoordinator: polish, then correct","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Could CalderaCopperBridgeStore show the active Swift 6 sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Before touching projects/caldera/db/migrations/20260730_events.sql, 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":"diff --git a/projects/caldera/crates/index/src/segment.rs b/projects/caldera/crates/index/src/segment.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/crates/index/src/segment.rs\n+++ b/projects/caldera/crates/index/src/segment.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit CalderaRainfallDBCoordinator 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":"2026-07-30T08:14:11.409Z level=info service=calderacoraluploadflow pod=calderacoraluploadflow-7cf8 request_id=43139 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=calderacoraluploadflow request_id=43139 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=calderacoraluploadflow request_id=43139 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=calderacoraluploadflow request_id=43139 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=calderacoraluploadflow request_id=43139 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=calderacoraluploadflow request_id=43139 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=calderacoraluploadflow request_id=43139 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=calderacoraluploadflow request_id=43139 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nDetermine why CalderaCoralUploadFlow 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":"CalderaGarnetModalCoordinator is blocking the next release because a feature flag whose default differs between environments. I need two concrete outcomes from a single pass: change CalderaGarnetModalCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing Room conventions in projects/caldera/ui/settings/PrivacyPane.tsx; do not introduce another runtime dependency. 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.5,"slice":"mixed","lang":"en"} +{"prompt":"Three teams extended CalderaDeltaCanvasStore independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current Swift 6 operational envelope\n\nThis repository spans embedded, Go services, Android; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Extract CalderaMarbleTokenStore's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Drop CalderaRavenSessionService's unused import","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Responsive layout for CalderaBirchMigratorService","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Beacon: Ticket OPS-43134: retire the legacy replay path for CalderaAtlasSearchFlow\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 CalderaAtlasSearchFlow 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":"For CalderaKiteSchedulerCoordinator, produce a consumer guide for CalderaKiteSchedulerCoordinator; once that is complete, correct the known stale timeout beside it. Work from projects/caldera/web/components/FilterDrawer.vue, stay with FastAPI, and do not introduce another runtime dependency. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current CalderaRainfallDBService 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 CalderaRainfallDBService\n- do not introduce another runtime dependency\n\nSeveral teams work in this embedded, Go services, 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":"Draft CalderaMicaProfileService's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"// projects/caldera/Sources/App/SessionStore.swift\nfinal class CalderaEchoRegistryFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 CalderaEchoRegistryFlow; 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":"Support wants the behavior in projects/caldera/services/ledger/replay.go recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary. The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Cinder: // projects/caldera/ml/pipeline/features.py\nfinal class CalderaAcornWidgetFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 CalderaAcornWidgetFlow 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":"En projects/caldera/ml/pipeline/features.py, CalderaSableParserStore tiene un problema intermitente en el flujo de OpenTelemetry. Termina el layout responsive, estados vacío y retry, foco por teclado, dark mode y reduced motion.\n\nRestricciones:\n- seguir con OpenTelemetry\n- conservar compatibilidad y cancelación\n- limitar el cambio a CalderaSableParserStore","purpose":"frontendImpl","secondary":"debugging","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"es"} +{"prompt":"Delta: projects/caldera/ui/settings/PrivacyPane.tsx の CalderaFrostPanelService で、Room の flow に断続的な問題が起きています。 queue、scheduler、cancel 経路を追い、仮説を比較して、変更前に原因を特定してください。\n\n制約:\n- Room を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は CalderaFrostPanelService のみ","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"} +{"prompt":"Ember: The minimum supported FastAPI version in projects/caldera/infra/modules/edge/main.tf 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":"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_43156'\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_43156'::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\nFind the source of this CalderaTideWorkerCoordinator symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Frost: The API work is done; what remains for CalderaPrismCacheStore 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 CalderaPrismCacheStore\n- do not introduce another runtime dependency\n\nSeveral teams work in this embedded, Go services, Android monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Where did CalderaWillowCodecStore's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Read projects/caldera/internal/auth/refresh.go and tell me whether CalderaSlateEditorService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/caldera/engine/render/atlas.cpp b/projects/caldera/engine/render/atlas.cpp\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/engine/render/atlas.cpp\n+++ b/projects/caldera/engine/render/atlas.cpp\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 CalderaMicaProfileFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"Garnet: The CalderaRainfallDBFlow 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":"Harbor: diff --git a/projects/caldera/lib/codec/frame.cc b/projects/caldera/lib/codec/frame.cc\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/lib/codec/frame.cc\n+++ b/projects/caldera/lib/codec/frame.cc\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nWire CalderaMapleQueueFlow'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.8,"slice":"pasted-context","lang":"en"} +{"prompt":"// projects/caldera/internal/auth/refresh.go\nfinal class CalderaSlateEditorFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 CalderaSlateEditorFlow; 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":"Serve CalderaEmberRelayService health checks","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Release engineering needs a CalderaQuartzPlayerService 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":"What is the safest way to split projects/caldera/apps/console/routes/usage.svelte into independently owned modules while CalderaOrbitSyncStore's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Iris: diff --git a/projects/caldera/db/migrations/20260730_events.sql b/projects/caldera/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/caldera/db/migrations/20260730_events.sql\n+++ b/projects/caldera/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure CalderaQuartzPlayerFlow 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":"UI ticket DES-43127: finish the compact CalderaDriftConsoleFlow filter experience\n\nRoute: /catalog/search\nSource: projects/caldera/apps/console/routes/usage.svelte\nFramework: Swift 6\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 CalderaDriftConsoleFlow 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":"core","lang":"en"} +{"prompt":"CalderaIrisBatchCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-43153\n\n08:02 deploy CalderaAsterWebhookCoordinator 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Capture the CalderaAsterWebhookCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Ticket OPS-43152: retire the legacy replay path for CalderaCopperBridgeCoordinator\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 CalderaCopperBridgeCoordinator rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Could CalderaWrenExportService show the active gRPC 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":"thread 'tokio-runtime-worker' panicked at projects/caldera/workers/thumbnail/consumer.ex:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: calderamosaicgridflow::scheduler::LeaseTask::flush\n at ./projects/caldera/workers/thumbnail/consumer.ex:217:18\n 4: calderamosaicgridflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nDetermine why CalderaMosaicGridFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Juniper: // projects/caldera/app/src/main/SyncWorker.kt\nfinal class CalderaOpalRouterCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 CalderaOpalRouterCoordinator 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":"CalderaRavenSessionCoordinator: restructure, then correct","purpose":"refactor","secondary":"backendImpl","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Before we approve CalderaSlateEditorStore, assess whether two validators with subtly different error strings is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} diff --git a/data/round2-04.jsonl b/data/round2-04.jsonl index 1dbacff..3a7c6cb 100644 --- a/data/round2-04.jsonl +++ b/data/round2-04.jsonl @@ -1,200 +1,200 @@ -{"prompt": "our changelog needs an entry for the removal of `wal_sync: never`, with the migration advice for anyone using it", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "the events panel in the admin console refreshes every ten seconds by replacing the whole list, which resets the scroll position and makes it useless during an incident when you're trying to read something. keep the polling but merge new events in without moving what the user is looking at, and show a \"3 new events\" pill when they're scrolled away from the top", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "message ordering guarantee we advertise, and the code that's meant to implement it. do they match?\n\ndocs: \"Messages within a thread are delivered to all devices in the order the server accepted them. Across threads, no ordering is guaranteed.\"\n\n// fanout.go\nfunc (f *Fanout) Publish(ctx context.Context, m Message) error {\n\tdevices, err := f.devices.For(ctx, m.ThreadID)\n\tif err != nil { return err }\n\tvar g errgroup.Group\n\tfor _, d := range devices {\n\t\td := d\n\t\tg.Go(func() error { return f.push.Send(ctx, d, m) })\n\t}\n\treturn g.Wait()\n}\n\n// accept path assigns m.ServerTS = time.Now() before enqueueing to a per-shard channel", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "our health endpoint counts a stalled compaction as healthy, so nothing pages until customers notice", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "the reply bar's offline behaviour is currently that everything looks normal until you background the app and the message vanishes, which is the worst possible outcome. sent-but-unacknowledged messages should show a clock glyph, failed ones a retry affordance, and the bar itself should never lie about whether something has been delivered", "purpose": "frontendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "is this actually a race or am i misreading the memory ordering?\n\nstd::atomic latest_lsn_{0};\n\nvoid WalWriter::Append(const Record& r) {\n auto lsn = next_lsn_.fetch_add(1, std::memory_order_relaxed);\n buffer_->Write(lsn, r);\n latest_lsn_.store(lsn, std::memory_order_release);\n}\n\nuint64_t WalWriter::Durable() const {\n return latest_lsn_.load(std::memory_order_acquire);\n}\n\nbool Reader::Visible(uint64_t lsn) const {\n return lsn <= writer_->Durable();\n}\n\nfour writer threads share one WalWriter, readers call Visible on their own threads", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "a customer's engineer sent this and support forwarded it to me. answer it as a docs page rather than an email:\n\n\"We're running the operator in a cluster with a strict pod security admission policy (restricted). Your StatefulSet requests runAsUser: 0 and a hostPort, both of which are rejected. Is running as root actually required? Is the hostPort required, or is it there because of the old deployment model? We'd also like to know the minimum RBAC the operator needs — the ClusterRole in your chart grants * on everything, which our security team will not approve.\"", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "design review ticket, i want the thinking done before the meeting:\n\nLUM-460 — Read-your-writes without pinning reads to the leader\nToday a client that needs to read its own write sends `X-Read-Your-Writes` and we route to the leader, which is why the leader is 70% of read traffic on chatty threads. Proposal is per-client LSN tracking with follower reads that wait for the LSN, bounded by a timeout after which we fall back to the leader. Concerns: clients are mobile and reconnect constantly; LSN would have to survive a reconnect; a slow follower could hold a request for the whole timeout; we have no way to observe per-client staleness today.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "support ticket volumes for the last quarter, by category. what would you fix first and why:\n\n retention misconfiguration 182 tickets avg 41 min to resolve\n push registration failures 141 tickets avg 88 min\n pod evictions / storage 96 tickets avg 130 min\n upgrade gone wrong 44 tickets avg 4.2 hours\n \"messages out of order\" 38 tickets avg 2.1 hours, 12 unresolved\n RBAC / install problems 31 tickets avg 55 min\n everything else 77 tickets\n\nengineering capacity for this is about one person for a quarter, and support is asking for docs rather than fixes on at least half of these", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "we need the spool rotation the incident asked for. current behaviour and the requirement:\n\n- broker appends every unacknowledged message to /tmp/spool/.log, no rotation, no cap\n- on restart the whole spool is replayed in order; the file has reached 41GB on a busy shard\n- required: rotate at 2GB, keep at most 4 segments per shard, drop the oldest with a loud metric and a warning log\n- replay must still be in order across segments, and must skip segments whose checksum fails rather than crashing\n- the operator sets the cap via `tuning.spool_max_mb`, defaulting to 8192 total per shard\n- none of this may block the write path, which currently appends synchronously", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "message bubbles clip at large type sizes", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "operator reconcile loop is hot-looping and i can't see why from the logs:\n\nI0729 11:02:14.881 1 controller.go:212] \"Reconciling\" cluster=\"lumen-prod\" generation=41 observedGeneration=41\nI0729 11:02:14.902 1 status.go:88] \"Updating status\" phase=\"Ready\" replicas=3 readyReplicas=3\nI0729 11:02:14.918 1 controller.go:212] \"Reconciling\" cluster=\"lumen-prod\" generation=41 observedGeneration=41\nI0729 11:02:14.941 1 status.go:88] \"Updating status\" phase=\"Ready\" replicas=3 readyReplicas=3\nI0729 11:02:14.958 1 controller.go:212] \"Reconciling\" cluster=\"lumen-prod\" generation=41 observedGeneration=41\nW0729 11:02:15.002 1 reflector.go:539] watch of *v1alpha1.MessageCluster ended with: too old resource version\nI0729 11:02:15.021 1 controller.go:212] \"Reconciling\" cluster=\"lumen-prod\" generation=41 observedGeneration=41\n\nabout 60 reconciles a second, CPU pinned, nothing in the cluster is actually changing", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "push notifications stopped for ios users on tuesday, apns feedback:\n\n{\"reason\":\"BadDeviceToken\",\"timestamp\":1753843201} count=41221\n{\"reason\":\"Unregistered\",\"timestamp\":1753843261} count=8814\n{\"reason\":\"TopicDisallowed\"} count=2201\n{\"reason\":\"ExpiredProviderToken\"} count=1\n\nour side:\n push_send_total{result=\"error\"} 52,236 in 24h\n push_send_total{result=\"ok\"} 1,102 in 24h\n last successful send: 2026-07-27T23:58:02Z\n\nwe did rotate the signing key on monday but the ExpiredProviderToken count is 1, not 52 thousand", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "go vet after the operator refactor, all in one file:\n\n./internal/controller/cluster_controller.go:88:2: loop variable c captured by func literal\n./internal/controller/cluster_controller.go:141:12: the cancel function returned by context.WithTimeout should be called, not discarded, to avoid a context leak\n./internal/controller/cluster_controller.go:212:5: unreachable code\n./internal/controller/status.go:41:9: result of fmt.Sprintf call not used\n\nvet: exit status 1\nmake: *** [Makefile:22: vet] Error 1", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "pasted-context", "lang": "en"} -{"prompt": "one timestamp helper, not three", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "what does `wal_sync: batch` promise? write it down", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "why does compaction stall at 12%?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "thread screen has eleven hardcoded colours and three magic paddings; move it onto the design tokens without changing how it looks", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "design handoff for the thread screen's reply bar, react native:\n\nReply bar\n- Pinned to the keyboard, 52pt minimum height, grows to 5 lines then scrolls internally.\n- Leading: attach button 32pt, tinted secondary; long-press opens the media sheet.\n- Text input: 16pt, placeholder \"Message\", no border, 8pt vertical padding.\n- Trailing: send button appears only when there's text, 28pt circle, scales in over 120ms.\n- Reply-to state: a 40pt strip above the input with a 2pt accent bar, the quoted text truncated to one line, and an X to clear.\n- Typing indicator sits above the bar, fades in after 400ms of a peer typing, out after 3s of silence.\n- Safe area: the bar must sit above the home indicator, and the keyboard animation must not cause a jump on iOS 18.\n- Offline: the bar stays usable, sent messages show a clock glyph until acknowledged.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "is our eviction fallback safe?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "support burden is dominated by three things — retention misconfiguration, push registration failures and pod evictions — and support keeps asking for documentation rather than fixes, which i suspect is the wrong instinct for at least two of them. work through each one and tell me whether the answer is docs, better defaults, a validating webhook, or actual engineering, with the reasoning laid out", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "a customer's security team asked why the operator needs cluster-admin and the honest answer is that nobody trimmed the ClusterRole after the prototype. work out the minimum permissions the operator actually uses from the code, then write the page explaining each permission and why it's needed, in the tone of someone who expects to be challenged on every line", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "we tell customers that messages within a thread are delivered in server-accept order, and i now think that's a claim about the accept path that the fanout path doesn't honour. rather than change the code first, i want the actual guarantee written down accurately — what holds, under what conditions it doesn't, and what a client should do if it cares", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "messages arrive out of order for maybe one user in a thousand, here's a trace from one of them:\n\nsend msg=01HR9K2M seq=4118 client_ts=11:02:14.221 server_ts=11:02:14.402 shard=7\nsend msg=01HR9K2N seq=4119 client_ts=11:02:14.318 server_ts=11:02:14.396 shard=7\nfanout msg=01HR9K2N to=4 devices at=11:02:14.441\nfanout msg=01HR9K2M to=4 devices at=11:02:14.512\nack msg=01HR9K2N device=ios-88a1 at=11:02:14.602\nack msg=01HR9K2M device=ios-88a1 at=11:02:14.688\nrender order on device: 01HR9K2N then 01HR9K2M\n\nthe client sorts by server_ts, and as you can see the later message got the earlier server timestamp", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "le CI est rouge une fois sur cinq, toujours sur le même test d'intégration :\n\n--- FAIL: TestOperatorScalesDownIdleClusters (30.12s)\n operator_test.go:141: expected 1 replica after idle timeout, got 3\n operator_test.go:148: last reconcile at 2026-07-29T11:04:02Z, idle since 2026-07-29T11:02:31Z\n operator_test.go:152: envtest apiserver logs:\n W0729 11:04:01.882 1 dispatcher.go:210] slow webhook response: 4.1s\n W0729 11:04:02.114 1 admission.go:88] mutating webhook \"defaults.lumen.io\" timed out\nFAIL\nFAIL github.com/lumen/operator/internal/controller 62.441s\n\nen local, avec -count=20, jamais d'échec", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "fr"} -{"prompt": "CRD we're about to publish. once this is in customers' clusters we can't take it back:\n\nspec:\n versions:\n - name: v1alpha1\n served: true\n storage: true\n schema:\n openAPIV3Schema:\n type: object\n properties:\n spec:\n type: object\n properties:\n replicas: { type: integer }\n retention: { type: string }\n storage: { type: string }\n tuning:\n type: object\n x-kubernetes-preserve-unknown-fields: true\n required: [replicas]\n subresources: {}\n\nno status subresource, no defaulting, retention is a free-form string", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "on-call handover notes for the week, turn them into something the next person can actually use:\n\n- broker pods evicting on ephemeral storage, spool file is unbounded, ticket LUM-441, workaround is a cron that truncates it (yes really)\n- push delivery to ios is degraded, apple's feedback says BadDeviceToken en masse, suspect the token migration, dana is on it\n- compaction on shard 7 stalls if you let the flush queue fill, restart the node, it recovers in about 4 minutes\n- do not scale the operator deployment above 1, leader election is broken and two of them fight\n- the staging cluster's certs expire on the 12th, renewal is manual, instructions are in dana's dms somewhere\n- alert `BrokerLagHigh` fires nightly at 02:00 during compaction and is safe to ignore for 20 minutes", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "storage config knobs we expose, and no documentation anywhere. write the operator's tuning reference:\n\ntuning:\n block_cache_mb: 4096 # default 512\n write_buffer_mb: 256 # default 64\n max_write_buffers: 4 # default 2\n compaction_threads: 8 # default 2\n level0_stall_threshold: 8 # default 12\n bloom_bits_per_key: 10 # default 10\n compression: zstd # none | lz4 | zstd\n wal_sync: batch # always | batch | never\n\nthings the team knows: block_cache_mb above 60% of container memory gets you OOMKilled; wal_sync=never loses acknowledged writes on power loss; compaction_threads above the core count makes stalls worse, not better", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "upgrade notes needed for the retention change, here's what actually happens:\n\n- before: `retention` was a free-form string, we parsed \"7d\", \"1 week\", \"168h\" and silently defaulted to 7 days on anything we couldn't parse\n- after: only ISO-8601 durations are accepted, the CRD rejects everything else at admission\n- on upgrade, a migration job rewrites existing values it can parse and marks clusters it can't as `Degraded` with a message\n- clusters stuck in Degraded keep serving, they just refuse spec changes until retention is fixed\n- there's no automatic rollback; downgrading the operator leaves ISO values that the old parser reads as 7 days\n\nwrite the upgrade guide for self-hosted operators", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "detox config and the CI job disagree about the simulator, so e2e never runs on CI:\n\n// .detoxrc.js\ndevices: {\n simulator: { type: 'ios.simulator', device: { type: 'iPhone 16' } }\n},\nconfigurations: {\n 'ios.sim.debug': { device: 'simulator', app: 'ios.debug' }\n}\n\n# .github/workflows/e2e.yml\n- run: xcrun simctl list devices available | grep \"iPhone 15\"\n- run: yarn detox build --configuration ios.sim.release\n- run: yarn detox test --configuration ios.sim.release --cleanup\n\nerror: Failed to find a device by type = \"iPhone 16\"\nDetox can only run on: iPhone 15, iPhone 15 Pro, iPad Air (5th generation)", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "pasted-context", "lang": "en"} -{"prompt": "three components render the same message row and they've drifted. one component, same visuals:\n\n// MessageBubble.tsx — used in the thread\n\n {m.body}\n {formatTimestamp(m.serverTs)}\n\n\n// SearchResultRow.tsx\n\n {m.body}\n {format(m.serverTs, 'HH:mm')}\n\n\n// PinnedMessage.tsx\n\n {m.body}\n {relativeTime(m.serverTs)}\n\n\nthree timestamp helpers too, all in different files", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "navigation params are typed three different ways and it's why the deep link bug keeps coming back:\n\n// AppNavigator.tsx\nexport type RootStackParamList = {\n ThreadList: undefined\n Thread: { threadId: string; highlight?: string }\n Profile: { userId: string }\n}\n\n// ThreadScreen.tsx\ntype Props = { route: { params: { threadId: string; highlightMessage?: string } } }\n\n// deeplink.ts\nconst parse = (url: string): { screen: string; params: Record } => ...\n\nthe highlight param is called `highlight` in one place and `highlightMessage` in another", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "pasted-context", "lang": "en"} -{"prompt": "test helpers duplicated across three packages, with the usual small differences:\n\n// internal/controller/testutil.go\nfunc newCluster(name string, replicas int32) *v1alpha1.MessageCluster { ... }\n\n// internal/webhook/helpers_test.go\nfunc makeCluster(ns, name string) *v1alpha1.MessageCluster { ... } // sets defaults\n\n// test/e2e/fixtures.go\nfunc Cluster(opts ...ClusterOpt) *v1alpha1.MessageCluster { ... } // sets defaults + status\n\nabout 60 call sites between them, and the webhook one sets a field the others don't", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "spool cap default to 8GB", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "core", "lang": "en"} -{"prompt": "el placeholder dice «Mensage», falta una j", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "core", "lang": "es"} -{"prompt": "mobile team wants to drop the old react native architecture and they can't until the notification module is rewritten, which nobody has scoped. before anyone starts, i'd like the migration mapped out: what depends on the old module, what the new one has to do, how we ship it without a big-bang release, and what we do about the two native modules a contractor wrote and nobody understands", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "an audit is booked for october and it will produce findings we can't predict, which is a bad way to spend a quarter. i'd rather we found the obvious things first: how would you scope a pre-audit review of the message path, the operator's RBAC, the mobile token storage and the admin tooling, given about two weeks of one engineer's time", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "consistency model is implemented and undocumented, which means every customer question about it gets a slightly different answer depending on who replies. write the public page: what a write acknowledgement means, what a read can and cannot see, what happens during an election, and be explicit about the guarantees we do not offer rather than quietly omitting them", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "tuning knobs we expose through the CRD are documented as a list of field names with no explanation, and the dangerous ones look exactly like the harmless ones. write the tuning reference: what each knob does, sensible ranges, the interactions between them, and a prominent warning on the two that can lose acknowledged writes or get the pod OOMKilled", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "operator's finalizer logic looks fine to me and yet we have three clusters stuck terminating for two days. work out whether the teardown path can genuinely fail forever, whether removing the finalizer before the update lands is possible, and what state a partially torn-down cluster leaves behind", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "admin console's cluster detail page is unusable on a phone, which is exactly where people open it during an incident, and the stat tiles overflow into a horizontal scroll that hides the conditions table entirely. make it work down to 320px without building a separate mobile view", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "i want an honest read on whether our WAL's relaxed ordering is correct with four writer threads, and if it isn't, the fix — with a test that fails reliably on the current code under tsan", "purpose": "review", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "scan and iterator both know about page pinning, and neither can be tested without a real page cache", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "how does the client decide a message is undelivered — is that a timeout, an ack, or the absence of one", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "go vet is failing on a captured loop var", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "operator replicas back to 1 for now", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "one device-lookup source for fanout", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "why is the leader taking 70% of reads?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "push registration retries on every failure code including permanent ones, which is how we spent a day hammering apple with dead tokens", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "what does `has_more` actually mean on the messages endpoint when a page ends exactly on the last message", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "our alerting was assembled per-service by different people and pages for things that resolve themselves nightly, what would a coherent set of alerts look like", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "the admin console needs a proper empty state for a namespace with no clusters, because right now you get a bare table header and people assume it's broken and file a ticket. design and build it: an explanation, the kubectl command that creates one, a link to the getting-started page, and the same treatment for a filtered view that matches nothing", "purpose": "frontendImpl", "secondary": "writing", "mixed": true, "difficulty": 0.45, "slice": "mixed", "lang": "en"} -{"prompt": "message row component, shared across screens", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "our cluster status pill uses four colours that are nearly indistinguishable on a projector and identical in greyscale, which came up when someone screenshared during an incident. give each status a distinct shape or glyph as well as a colour, keep the pill compact enough for the table, and make sure the degraded and progressing states read differently at a glance", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "the spool file format and its replay behaviour are known to exactly two people, and one of them is on parental leave from November. write the internal reference: the on-disk layout, how segments are ordered, what happens on a checksum failure, what replay does with a partially written record, and what an operator can safely delete when a disk fills up", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "is the session object in AsyncStorage a problem on a rooted device, or am i worrying about the wrong thing", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "a plain description of what happens between a client sending and every device rendering would help me a lot", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "design system tokens we're meant to be using, and the thread screen ignores half of them:\n\ncolors.surface #0E1116 (dark) / #FFFFFF (light)\ncolors.surfaceRaised #161B22 / #F6F8FA\ncolors.textPrimary #E6EDF3 / #1F2328\ncolors.textSecondary #8B949E / #59636E\ncolors.accent #2F81F7\nspacing 4 / 8 / 12 / 16 / 24 / 32\nradius sm 6, md 10, lg 16, pill 999\ntype body 16/22, caption 13/18, title 20/26\n\nthe thread screen has 11 hardcoded hex values, three magic paddings and its own font sizes. bring it onto the tokens without changing how it looks beyond what the tokens force", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "support is guessing at what our error codes mean and inventing explanations for customers. build the reference table from the code, and where a code is genuinely unhelpful — three of them just say \"internal\" — change the message to something a human could act on", "purpose": "writing", "secondary": "quickFix", "mixed": true, "difficulty": 0.5, "slice": "mixed", "lang": "en"} -{"prompt": "thread list shows a stale last-message preview for about ten seconds after sending, then corrects itself", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "message reactions need a server-side aggregate rather than counting rows on every read, and the mobile team wants it this sprint", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "we need a way to mark a device's push token dead after a permanent failure code, and stop sending to it", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "metro bundler is fine but the app white-screens on android release builds only:\n\nFATAL EXCEPTION: mqt_native_modules\nProcess: chat.lumen.app, PID: 9912\ncom.facebook.react.common.JavascriptException: TypeError: Cannot read property 'prototype' of undefined\n\nThis error is located at:\n in ThreadListScreen (created by SceneView)\n in SceneView (created by NativeStackView)\n in RNSScreenContentWrapper\n in NativeStackNavigator\n in AppNavigator (created by App)\n\n at com.facebook.react.modules.core.ExceptionsManagerModule.reportException(ExceptionsManagerModule.java:65)\n at java.lang.reflect.Method.invoke(Native Method)\n at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372)\n\ndebug builds are perfectly fine, and it started after we enabled hermes", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "query planner picks a different plan in prod than in staging for the identical query and stats:\n\n staging:\n Index Scan using idx_messages_thread_created on messages (cost=0.56..812.44 rows=412 width=88)\n Index Cond: ((thread_id = $1) AND (created_at > $2))\n Filter: (deleted_at IS NULL)\n\n prod:\n Bitmap Heap Scan on messages (cost=4412.10..214882.31 rows=88214 width=88)\n Recheck Cond: (thread_id = $1)\n Filter: ((created_at > $2) AND (deleted_at IS NULL))\n Rows Removed by Filter: 1204118\n -> Bitmap Index Scan on idx_messages_thread (cost=0.00..4390.05 rows=88214 width=0)\n\nsame postgres version, same indexes, ANALYZE run this morning on both", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "sanitizer output from the storage engine tests, only under -j16:\n\n==41221==ERROR: AddressSanitizer: heap-use-after-free on address 0x60700000dfb8 at pc 0x0000004c1a2f\nREAD of size 8 at 0x60700000dfb8 thread T7\n #0 0x4c1a2f in lumen::store::PageCache::pin(uint64_t) src/store/page_cache.cc:141\n #1 0x4c88c0 in lumen::store::Iterator::next() src/store/iterator.cc:88\n #2 0x4d1102 in lumen::exec::ScanNode::Next() src/exec/scan.cc:52\n\n0x60700000dfb8 is located 8 bytes inside of 72-byte region\nfreed by thread T3 here:\n #0 0x49a112 in operator delete(void*)\n #1 0x4c0f40 in lumen::store::PageCache::evict(uint64_t) src/store/page_cache.cc:212\n\npreviously allocated by thread T3 here:\n #1 0x4c0221 in lumen::store::PageCache::load(uint64_t) src/store/page_cache.cc:88\n\nsingle-threaded runs are clean, and this has probably been there for months", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "pods get evicted every few hours and the events are not telling me much:\n\nEvents:\n Type Reason Age From Message\n ---- ------ ---- ---- -------\n Warning Evicted 32m kubelet The node was low on resource: ephemeral-storage. Container broker was using 41Gi, which exceeds its request of 2Gi.\n Normal Killing 32m kubelet Stopping container broker\n Warning Evicted 18m kubelet The node was low on resource: ephemeral-storage. Container broker was using 39Gi, which exceeds its request of 2Gi.\n Normal Pulled 17m kubelet Container image \"ghcr.io/lumen/broker:2.11.4\" already present on machine\n Warning BackOff 4m (x12 over 16m) kubelet Back-off restarting failed container\n\nthe broker writes a spool file to /tmp and we thought that was bounded", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "react native app drops frames scrolling long threads, here's the profiler summary:\n\nJS thread: 41 fps avg, 12 fps min\nUI thread: 58 fps avg\n\nTop offenders (self time, 10s sample):\n MessageBubble render 2841ms (3,912 renders)\n useThreadMessages selector 1102ms (3,912 calls)\n formatTimestamp 884ms (11,736 calls)\n Animated.timing 412ms\n FlatList onViewableItemsChanged 388ms\n\nRe-render reasons for MessageBubble:\n props.message changed 12%\n props.onLongPress changed 71%\n context value changed 17%\n\nthe list has 400 items and windowSize is at the default", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "nightly compaction stalled and the only clue is this:\n\n[compaction] level=1 files=41 target=L2 started\n[compaction] level=1 read 2.1GB in 41s\n[compaction] level=2 merge started, output sst=00041.sst\n[compaction] level=2 merge progress 12% after 300s\n[compaction] level=2 merge progress 12% after 600s\n[compaction] level=2 merge progress 12% after 900s\n[bg] flush queue depth 8 (max 8), writes stalled\n[bg] write stall total 14m22s\n[compaction] level=2 merge progress 13% after 1200s\n\nthe machine is not CPU bound, iostat shows 4% utilisation, and there is 400GB free", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "someone's proposed this for the operator's finalizer handling. sound?\n\nfunc (r *ClusterReconciler) Reconcile(ctx context.Context, req ctrl.Request) (ctrl.Result, error) {\n\tvar c v1alpha1.MessageCluster\n\tif err := r.Get(ctx, req.NamespacedName, &c); err != nil {\n\t\treturn ctrl.Result{}, client.IgnoreNotFound(err)\n\t}\n\tif !c.DeletionTimestamp.IsZero() {\n\t\tif err := r.teardown(ctx, &c); err != nil {\n\t\t\treturn ctrl.Result{RequeueAfter: 10 * time.Second}, nil\n\t\t}\n\t\tcontrollerutil.RemoveFinalizer(&c, finalizerName)\n\t\treturn ctrl.Result{}, r.Update(ctx, &c)\n\t}\n\tcontrollerutil.AddFinalizer(&c, finalizerName)\n\tif err := r.Update(ctx, &c); err != nil {\n\t\treturn ctrl.Result{}, err\n\t}\n\treturn r.reconcileNormal(ctx, &c)\n}", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "por favor, revisa este helm chart antes de que lo subamos al repo público:\n\napiVersion: apps/v1\nkind: StatefulSet\nspec:\n replicas: {{ .Values.replicas }}\n template:\n spec:\n securityContext:\n runAsUser: 0\n containers:\n - name: broker\n image: \"ghcr.io/lumen/broker:{{ .Values.tag | default \"latest\" }}\"\n env:\n - name: ADMIN_TOKEN\n value: {{ .Values.adminToken | quote }}\n ports:\n - containerPort: 9092\n hostPort: 9092\n volumeMounts:\n - name: spool\n mountPath: /tmp/spool\n volumes:\n - name: spool\n emptyDir: {}\n\nlo van a instalar clientes en sus propios clústeres", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "es"} -{"prompt": "hook that every screen uses. i keep being told it's fine and the app disagrees:\n\nexport function useThreadMessages(threadId: string) {\n const [messages, setMessages] = useState([])\n const { socket } = useSocket()\n\n useEffect(() => {\n let cancelled = false\n api.messages(threadId).then(m => { if (!cancelled) setMessages(m) })\n const off = socket.on('message', (m: Message) => {\n if (m.threadId === threadId) setMessages(prev => [...prev, m].sort(byServerTs))\n })\n return () => { cancelled = true; off() }\n }, [threadId, socket])\n\n const onLongPress = (id: string) => actions.openMenu(id)\n return { messages, onLongPress }\n}", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "buffer pool eviction policy, inherited and never questioned:\n\nPage* PageCache::Evict() {\n std::lock_guard g(mu_);\n auto victim = lru_.back();\n while (victim && victim->pin_count.load() > 0) {\n victim = victim->prev;\n }\n if (!victim) {\n victim = lru_.back(); // give up, take the last one anyway\n }\n lru_.erase(victim);\n map_.erase(victim->page_id);\n return victim;\n}\n\nis the fallback there for a reason anyone can defend, and what does it do to a pinned page under load?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "security asked about our token handling in the mobile app and this is what i found:\n\n// auth/storage.ts\nimport AsyncStorage from '@react-native-async-storage/async-storage'\n\nexport const saveSession = (s: Session) =>\n AsyncStorage.setItem('session', JSON.stringify(s))\n\nexport const loadSession = async (): Promise => {\n const raw = await AsyncStorage.getItem('session')\n return raw ? JSON.parse(raw) : null\n}\n\n// api/client.ts\nconst client = axios.create({ baseURL: API })\nclient.interceptors.request.use(async cfg => {\n const s = await loadSession()\n if (s) cfg.headers.Authorization = `Bearer ${s.accessToken}`\n return cfg\n})\n\nrefresh tokens live in the same object, ttl 90 days", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "raw notes from the incident call, we owe the customer a written explanation by tomorrow:\n\n- 09:12 customer reports messages not arriving on ios\n- 09:20 we confirm push failures at 98%, android unaffected\n- 09:31 rotated the apns key on monday, suspicion falls there\n- 09:52 rules out the key, the error is BadDeviceToken not auth\n- 10:14 discover the token migration job re-encoded tokens as base64 twice\n- 10:31 stopped the job, 41k tokens affected out of 220k\n- 11:02 re-registration push sent via a silent notification, most devices recover\n- 12:40 remaining 6k devices need to open the app to re-register\n- no messages were lost, they were queued and delivered on re-registration", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "my commit is ready and i always write terrible messages. the diff:\n\ndiff --git a/src/exec/scan.cc b/src/exec/scan.cc\n@@ -41,12 +41,19 @@ Status ScanNode::Next(Batch* out) {\n- while (out->size() < batch_size_) {\n- auto page = cache_->Pin(iter_->page_id());\n- out->Append(iter_->Value());\n- cache_->Unpin(page);\n- iter_->Next();\n- }\n+ auto page = cache_->Pin(iter_->page_id());\n+ auto guard = absl::MakeCleanup([&] { cache_->Unpin(page); });\n+ while (out->size() < batch_size_) {\n+ if (iter_->page_id() != page->id) {\n+ cache_->Unpin(page);\n+ page = cache_->Pin(iter_->page_id());\n+ }\n+ out->Append(iter_->Value());\n+ iter_->Next();\n+ }\n return Status::OK();\n }\n\nwe use conventional commits and the body should explain why, not what", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"} -{"prompt": "schreib bitte die Release Notes für 2.12 aus diesen Tickets:\n\nLUM-402 Broker: Spool-Datei wird jetzt bei 2 GB rotiert statt unbegrenzt zu wachsen\nLUM-417 Operator: Leader Election repariert, mehrere Replicas sind jetzt unterstützt\nLUM-421 Storage: Kompaktierung blockiert nicht mehr, wenn die Flush-Queue voll ist\nLUM-433 API: `retention` akzeptiert jetzt nur noch ISO-8601-Dauern, alte Werte werden beim Upgrade migriert\nLUM-441 Mobile: Push-Registrierung wird bei ungültigem Token automatisch erneuert\nLUM-448 Breaking: `tuning.wal_sync=never` wurde entfernt\n\nZielgruppe sind Betreiber, die selbst hosten", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "de"} -{"prompt": "gostava de ter um documento sobre o modelo de consistência, a partir do que está no código:\n\n- as escritas vão para o líder do shard e são replicadas para dois seguidores\n- o ack ao cliente acontece depois de um seguidor confirmar, não os dois\n- as leituras podem ir para qualquer réplica, exceto quando o cliente envia o cabeçalho `X-Read-Your-Writes`\n- nesse caso a leitura vai para o líder e espera pelo LSN indicado pelo cliente\n- durante uma eleição, as escritas falham com 503 durante 2 a 5 segundos\n- não há garantia de leitura monotónica entre réplicas diferentes\n\nescreve isto como página de documentação pública, com os avisos que forem precisos", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "pt"} -{"prompt": "eslint and the react compiler disagree about our hooks, and i just want a green build:\n\nsrc/hooks/useThreadMessages.ts\n 14:6 warning React Hook useEffect has a missing dependency: 'api' react-hooks/exhaustive-deps\n 22:9 error Ref values ('cancelled.current') should not be read during render react-hooks/react-compiler\n\nsrc/screens/ThreadListScreen.tsx\n 41:11 error Component definition is missing display name react/display-name\n 88:3 warning Fast refresh only works when a file only exports components react-refresh/only-export-components\n\nsrc/components/MessageBubble.tsx\n 102:5 error 'onLongPress' changes on every render, wrap it in useCallback react-hooks/react-compiler\n\n✖ 5 problems (3 errors, 2 warnings)", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"} -{"prompt": "clang-tidy on the storage engine, the new checks are noisy but two look real:\n\nsrc/store/page_cache.cc:141:10: warning: 'pin' is called on a possibly-null pointer [bugprone-unchecked-optional-access]\nsrc/store/page_cache.cc:212:5: warning: loop variable 'victim' is copied but only used as const reference [performance-for-range-copy]\nsrc/exec/scan.cc:88:22: warning: narrowing conversion from 'size_t' to 'int' [bugprone-narrowing-conversions]\nsrc/wal/writer.cc:44:9: warning: atomic operation on 'latest_lsn_' uses relaxed ordering, consider seq_cst [concurrency-mt-unsafe]\nsrc/util/arena.cc:19:1: warning: function 'Allocate' exceeds recommended size/complexity thresholds [readability-function-size]\n\n5 warnings generated, CI treats them as errors since last week", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "kustomize diff between our two environments, one of these is why prod restarts more:\n\n--- base/broker/statefulset.yaml\n+++ overlays/prod/statefulset.yaml\n@@\n resources:\n requests:\n- memory: 2Gi\n- ephemeral-storage: 2Gi\n+ memory: 8Gi\n+ ephemeral-storage: 2Gi\n limits:\n- memory: 4Gi\n+ memory: 8Gi\n@@\n env:\n- - name: BLOCK_CACHE_MB\n- value: \"512\"\n+ - name: BLOCK_CACHE_MB\n+ value: \"6144\"\n@@\n terminationGracePeriodSeconds: 30\n+ # prod only\n+ livenessProbe:\n+ initialDelaySeconds: 5\n+ periodSeconds: 5\n+ failureThreshold: 2", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "prometheus rule that pages us every night at 02:00 and is always benign:\n\n- alert: BrokerLagHigh\n expr: max by (shard) (broker_consumer_lag) > 10000\n for: 2m\n labels:\n severity: page\n annotations:\n summary: \"broker lag on shard {{ $labels.shard }}\"\n\nnightly pattern:\n 02:00 lag climbs to ~40k during compaction\n 02:18 lag drains to under 1k\n 02:19 alert resolves\n\nduring a real incident in june, lag went to 400k and stayed there for an hour", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"} -{"prompt": "dependabot on the mobile app, four PRs open and i want to merge what's safe:\n\nreact-native 0.79.2 -> 0.80.0 (major-ish, they don't do semver properly)\n@react-navigation/native 6.1.18 -> 7.0.2 (breaking: linking config shape changed)\naxios 1.7.4 -> 1.11.2 (advisory GHSA-jr83, SSRF via redirect)\ndate-fns 3.6.0 -> 4.1.0 (breaking: timezone handling moved to a separate package)\n\nour app pins react-native in three places: package.json, ios/Podfile.lock and the expo config plugin", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "this reconciler does everything and i want the same behaviour in pieces i can test:\n\nfunc (r *ClusterReconciler) reconcileNormal(ctx context.Context, c *v1alpha1.MessageCluster) (ctrl.Result, error) {\n\t// 40 lines: ensure statefulset, diff spec, update if drifted\n\t// 30 lines: ensure service, headless service, and the ingress if enabled\n\t// 25 lines: ensure configmap from spec.tuning with defaults applied inline\n\t// 35 lines: ensure PVCs, resize if storage grew, refuse if it shrank\n\t// 50 lines: compute status from pod conditions and write it back\n\t// 20 lines: emit events for every transition\n\treturn ctrl.Result{RequeueAfter: time.Minute}, nil\n}\n\n200 lines in one function, one test that spins up envtest and asserts on the end state", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "error handling in the storage layer, three styles in one file:\n\nStatus PageCache::Load(uint64_t id, Page** out) {\n if (!map_.contains(id)) return Status::NotFound(\"page\");\n ...\n}\n\nPage* PageCache::Pin(uint64_t id) {\n auto it = map_.find(id);\n if (it == map_.end()) { LOG(FATAL) << \"pin of unknown page \" << id; }\n ...\n}\n\nabsl::StatusOr PageCache::Fetch(uint64_t id) {\n ...\n}\n\nsame class, three conventions, and one of them crashes the process on a bad id", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "quatre endroits construisent la même requête de fanout, avec des différences subtiles :\n\n// fanout.go\ndevices, _ := f.devices.For(ctx, m.ThreadID)\n\n// presence.go\nrows, _ := db.Query(ctx, `SELECT device_id FROM devices WHERE thread_id = $1 AND active`, tid)\n\n// admin/tools/resend.go\nrows, _ := db.Query(ctx, `SELECT device_id FROM devices WHERE thread_id = $1`, tid)\n\n// push/retry.go\ndevices := cache.Devices(tid) // peut être périmé de 5 minutes\n\nune seule source, s'il te plaît, et sans changer le comportement du chemin critique", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "fr"} -{"prompt": "config plumbing in the operator, currently five layers deep:\n\ndefaults := DefaultTuning()\nif c.Spec.Tuning != nil {\n merged := mergeMaps(defaults.AsMap(), c.Spec.Tuning.AsMap())\n if env := os.Getenv(\"LUMEN_TUNING_OVERRIDE\"); env != \"\" {\n var override map[string]any\n _ = json.Unmarshal([]byte(env), &override)\n merged = mergeMaps(merged, override)\n }\n if cm, err := r.getLegacyConfigMap(ctx, c); err == nil {\n merged = mergeMaps(cm.Data, merged) // note: legacy loses\n }\n tuning = TuningFromMap(merged)\n} else {\n tuning = defaults\n}\n\nsame resolved values, one obvious precedence order", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "fr"} -{"prompt": "quarter planning, and this is what landed in my inbox. i need a sequenced plan out of it:\n\n- self-hosted customers want a supported upgrade path between minor versions; today they redeploy and hope\n- two customers have asked for multi-region, one of them contractually\n- the mobile team wants to drop the old architecture and cannot until the notification module is rewritten\n- storage wants six weeks to finish the compaction work, otherwise the stalls continue\n- support burden is dominated by three things: retention config, push registration, and pod evictions\n- we have one platform engineer and they're on parental leave from November\n- there's a security audit booked for October that will produce work we can't predict", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "customer requirement we've signed up to, and nobody has thought about how:\n\n\"Message data for EU tenants must remain within the EU, including backups, logs and any derived data such as search indexes. Cross-region replication is permitted only between EU regions. Support staff outside the EU must not be able to read message content, though they may see metadata necessary for support. The customer requires evidence of this control, not an assurance.\"\n\nwe currently have one region, logs go to a US SaaS, and support has a debug tool that dumps message bodies. i want the plan and an honest list of what we'd have to give up", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "spec for the cluster detail page in our admin console, build it in react:\n\nCluster detail\n- Header: cluster name, namespace as a muted subtitle, a status pill (Ready / Progressing / Degraded / Unknown) and a kebab menu with Edit, Restart and Delete.\n- Summary strip: four stat tiles — replicas ready, storage used vs requested, message rate, consumer lag — each with a 24h sparkline and a click-through to metrics.\n- Conditions table: type, status, reason, message, last transition, newest first, with long messages truncated and expandable.\n- Events panel: last 50 events, warning ones flagged, auto-refreshing every 10 seconds without jumping the scroll position.\n- Degraded state: a banner above the summary explaining the condition in plain language with a link to the matching docs page.\n- Everything must be readable at 320px wide because people open this on phones during incidents.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "accessibility findings from a customer's audit of our mobile app, prioritise and implement:\n\n1. Message bubbles are announced as \"button, text\" with no sender or timestamp; VoiceOver users cannot tell who wrote what.\n2. The send button has no accessibility label, only an icon.\n3. Contrast on the timestamp text is 2.8:1 against the bubble background.\n4. The typing indicator is announced repeatedly, interrupting reading.\n5. Long-press is the only way to react to a message; there is no accessible alternative.\n6. Dynamic Type above the default clips the reply bar and hides the send button entirely.\n7. Focus order in the thread jumps from the header to the reply bar, skipping the message list.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "api spec we agreed with the mobile team, needs building on the server:\n\nGET /v2/threads/{id}/messages\n query: before (message id), after (message id), limit (default 50, max 200)\n exactly one of before/after may be given; neither means newest page\n response: { data: Message[], has_more: boolean, oldest_id, newest_id }\n Message: { id, thread_id, author_id, body, server_ts, edited_at?, deleted: bool, reactions: {emoji: count} }\n deleted messages come back with body omitted and deleted: true, they still occupy a position\n reads must be consistent within a page — no message may appear twice across pages if nothing changed\n a client with X-Read-Your-Writes: must not see a page missing its own just-sent message", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "axios advisory bump on the mobile app", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "unread badge counts deleted messages", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "detox targets iPhone 15 on CI", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "BrokerLagHigh needs a 20 minute for-clause", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "drop hostPort from the broker chart", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "context cancel is discarded in the reconciler", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "block cache 6GB in an 8GB limit", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "le champ `retention` accepte encore n'importe quoi", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "fr"} -{"prompt": "typing indicator should fade, not pop", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "our getting-started guide assumes a cluster with cluster-admin, a default storage class and no admission policies, which describes approximately none of our self-hosted customers. rewrite it for someone installing into a restricted namespace, including the values they'll need to override, and be explicit about what will fail and how the failure looks", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "the iterator rewrite makes sequential scans twice as fast and point-lookup misses nearly three times slower, with allocations up by an order of magnitude on mixed workloads. our production traffic is mostly point lookups. read the code alongside the benchmark and tell me whether the regression is inherent to the design or an artefact of how the batch buffer is sized", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "send button needs a label for VoiceOver", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "pinned message strip above the list", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "status pill colours are too similar", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "sparklines on the cluster stat tiles", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "die Zeitstempel sind zu blass", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "de"} -{"prompt": "reply bar jumps when the keyboard opens", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "events panel scroll jumps on refresh", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "conditions table needs a newest-first sort", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "`highlightMessage` everywhere, pick one name", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "split reconcileNormal into steps", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "les helpers de test dans un seul paquet", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "fr"} -{"prompt": "`PageCache::Fetch` naming, be consistent", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "pull the tuning merge into one function", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "inline `makeCluster`, one caller left", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "comment the memory ordering in wal/writer", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "upgrade notes for the retention change", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "resumo do incidente de push, em português", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "pt"} -{"prompt": "document the minimum RBAC we need", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "PR description for the spool rotation", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "who pins pages during a scan?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "¿el fanout garantiza el orden por hilo?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "es"} -{"prompt": "walk me through leader election here", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "threads reorder themselves on reconnect", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "release build white-screens, debug is fine", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "reconcile loop spins at 60/s", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "warum verlieren wir jede Nacht Push-Tokens?", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "de"} -{"prompt": "presence endpoint for a thread", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "design the EU-only story, then start on logs", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "shape the upgrade path, then write the migration", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "back on the push thing", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "finish what dana started", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "smoother", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "vague-eval", "lang": "en"} -{"prompt": "operator, again", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "do the thing from the handover notes", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "algo rápido antes de la demo", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "es"} -{"prompt": "next chunk of the storage work", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "whatever unblocks QA", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "tidy before review", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "same treatment as the thread screen", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "もう一度、あの通知の件", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "ja"} -{"prompt": "keep going on the console", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "plan for next quarter", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "anything you think matters", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "multi-region is now contractual for one customer and vaguely promised to another, and we've never run more than one region. i need to understand what it means for us before anyone commits to a date: whether we replicate at the storage layer or the application layer, what happens to message ordering across regions, how a client picks a region, and what our failover story would actually be when the network partitions rather than when a region cleanly disappears", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "self-hosted customers currently upgrade by redeploying the chart and hoping, which has gone badly twice this quarter, both times because a CRD field changed shape. i want a real upgrade story designed: version skew we support, how CRD migrations run, what the operator does when it finds resources it doesn't understand, whether we can roll back at all, and how a customer knows it worked", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "read-your-writes currently pins reads to the leader, which is why the leader carries most of our read traffic on the busiest threads. the proposal is per-client LSN tracking with follower reads that wait, and i can see three ways it goes wrong with mobile clients that reconnect constantly. talk me through the design space and what you'd actually recommend for our size", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "boundary", "lang": "en"} -{"prompt": "on-call handover happens verbally on a friday afternoon and the notes are a slack message that scrolls away. from this week's incidents and the current known issues, write the handover document template plus this week's filled-in version, in a form where the person picking it up can tell what is on fire, what is smouldering, and what they can ignore", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "nobody can explain why the buffer pool sometimes evicts a pinned page, and the code has a fallback branch with no comment that appears to do exactly that. i don't want it changed yet — read it, work out what happens to a scan holding that page, and tell me whether the crash we saw last month is explained by it", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "ordering trace from a customer shows a later message getting an earlier server timestamp, which either means our clocks are wrong or our accept path is doing something i don't understand. before we call it a bug, go through how server_ts is assigned, how the shard channel orders, and whether two messages on the same shard can be timestamped out of order", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "three components render a message row with their own timestamp helper, their own truncation rules and their own styles, which is why search results look subtly different from the thread. consolidate them into one component with props for the variations, keeping each screen looking exactly as it does today, and delete the two helpers that fall out", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "storage layer uses three error conventions in the same class — a Status return, a StatusOr, and a LOG(FATAL) that takes the process down on a bad page id — and callers handle whichever they happen to hit. pick the convention the newest code uses, apply it throughout, and make sure no path can still abort the process on bad input", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "tuning resolution in the operator goes through defaults, the spec, an environment override and a legacy configmap, merged in an order that surprises everyone including the person who wrote it. make the precedence explicit and testable, keep the resolved values identical for every cluster we have in the field, and leave the legacy path working until we can remove it", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "messages occasionally arrive out of order on ios but not android, roughly one user in a thousand, and both clients sort by the same field. i've stared at the fanout code and the push path and can't see it. before assuming it's the client, i'd like the whole path from accept to render examined properly", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "e2e tests fail about one run in five on CI and never locally, always on the test that waits for an idle cluster to scale down. the envtest logs mention a slow admission webhook right before the failure, which may or may not be related", "purpose": "debugging", "secondary": "review", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "CI installs the whole toolchain from scratch on every job because someone disabled caching to debug something in march and never turned it back on, and the mobile job now takes 22 minutes. turn caching back on for yarn, pods and gradle, verify the builds are still reproducible, and note what you changed", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "data residency for EU tenants is contractual and we currently have one region, logs in a US SaaS and a support tool that dumps message bodies. i want the design for what compliant looks like, and then the first piece implemented: keeping message content out of the logs entirely", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.9, "slice": "mixed", "lang": "en"} -{"prompt": "before the mobile rewrite starts i'd like the notification module's responsibilities mapped out properly — registration, token refresh, delivery receipts, deep links — and then the registration piece built against the new architecture so we can prove the approach works", "purpose": "planning", "secondary": "frontendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "spool needs rotation and we also need to decide what \"drop the oldest\" means for delivery guarantees, because right now we'd be silently losing messages. think through the semantics first, write them down, then implement rotation with whatever loud signals you decide on", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "unsere Retention-Konfiguration ist ein Freitextfeld und die Migration auf ISO-8601 steht an. Ich hätte gern zuerst einen Plan, wie wir bestehende Cluster migrieren, ohne dass jemand in Degraded landet, und danach den Validierungs-Webhook dafür", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "de"} -{"prompt": "consistency model needs writing up for customers and i suspect the act of writing it will surface at least one place where the code doesn't match the claim. do both: the public page, and a list of every claim you couldn't verify from the code", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "escreve o guia de instalação para clientes que alojam o produto, e valida no chart se o que dizemos sobre permissões é verdade — desconfio que pedimos muito mais do que precisamos", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "pt"} -{"prompt": "test helpers are duplicated across three packages with subtly different defaults, which is why a test can pass in one package and fail in another with the same input. unify them, then document the fixture conventions so the next person doesn't add a fourth", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.55, "slice": "mixed", "lang": "en"} -{"prompt": "navigation params are typed in three places with two different names for the same field, and the deep link bug keeps coming back because of it. fix the types properly, then add the short note to the contributing guide about where params are declared", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.5, "slice": "mixed", "lang": "en"} -{"prompt": "go packages are organised by layer — models, services, handlers — and every feature touches all three, so nothing is local", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "rename `MessageCluster` to `Cluster` in the CRD group, it reads terribly in kubectl output", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "mobile app has both a `utils` and a `helpers` folder, imported interchangeably, thirty files between them", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "could someone explain what happens to in-flight messages when a shard leader changes, i can't tell from the code", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "i'd like a read on the new iterator benchmarks before we merge, particularly the point-lookup miss regression", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "why does the reply bar re-render when a peer starts typing in a different thread", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "is it normal for the operator to log a status update on every reconcile even when nothing changed", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "someone should sanity check our CRD before it ships, particularly the free-form tuning field and the missing status subresource", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "docs/consistency.md describes two followers acknowledging before we ack the client, which is not what the code does", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "a short note for the team about why we're capping the spool, for the decision log", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "CRD field descriptions are empty, which means `kubectl explain` tells operators nothing at all", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "write the docs page answering \"why is my cluster Degraded\", covering all six conditions we can set", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "liveness probe on the prod overlay has a 5 second delay and 2 failures, which restarts pods mid-compaction", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "operator's default retention is 7 days in code and 30 days in the docs, and one of them has to change", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "push retries use a fixed 30 second delay with no jitter, so every failure lands in the same second", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "la búsqueda de mensajes ignora los acentos, y en español eso rompe la mitad de las consultas", "purpose": "quickFix", "secondary": "backendImpl", "mixed": true, "difficulty": 0.4, "slice": "mixed", "lang": "es"} -{"prompt": "one shard's consumer lag climbs steadily every night and drains by morning, and nobody knows whether that's compaction or a slow consumer", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "what should our story be for customers who want to run us on ARM nodes? two have asked and we've never built for it", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "i want a position on whether search belongs in the storage engine or as a separate index before anyone starts building it", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "how should we handle schema evolution for the message format now that self-hosted customers can be six months behind us", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "an endpoint that returns a device's pending messages since a given LSN, for the reconnect path", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "admin debug tool should redact message bodies unless the operator holds a break-glass role", "purpose": "backendImpl", "secondary": "review", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "per-thread rate limiting on the send path, since one automated client can currently saturate a shard", "purpose": "backendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "cluster list page needs filtering by status and namespace, and it should remember what you picked", "purpose": "frontendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.5, "slice": "mixed", "lang": "en"} -{"prompt": "whatever's least embarrassing before friday", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "pick up where the doc left off", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "thread list is a FlatList that re-renders every row whenever any thread updates, which on a busy account means the whole list rebuilds several times a second and scrolling turns to mush. keep the rows visually identical but make each one independent, memoise the row callbacks properly, and fix the last-message preview so it updates without dragging the rest of the list with it", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "message reactions currently open a long-press menu that appears under the thumb and covers the message being reacted to, and there's no way to reach them at all with a keyboard or a switch control. rework the interaction: an accessible affordance on each row, the picker positioned so it never covers its own message, and a sensible focus return when it closes", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "support answers \"why is my push not arriving\" from scratch every time, usually badly, because the answer depends on the token state, the apns feedback, whether the device has opened the app recently, and our own retry state. write the troubleshooting page that walks through those in order, with what to check and what each outcome means", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.55, "slice": "mixed", "lang": "en"} -{"prompt": "the mobile app stores its session, including a ninety-day refresh token, as plain JSON in AsyncStorage, and an interceptor reads it on every request. before i take this to the security review, i want an assessment of what that actually exposes on a compromised device, what the platform keychain would change, and whether the ninety days is the bigger problem", "purpose": "review", "secondary": "planning", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "our go packages are split by layer, so a single feature touches models, services and handlers and nothing is ever local to one directory. restructure by feature instead, keeping the public API and every behaviour identical, and do it in a sequence where the build stays green after each step rather than one enormous move commit", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "scan and iterator both know about page pinning, which means neither can be unit tested without a real page cache and a real file, and our tests are correspondingly slow and flaky. introduce a seam so the iterator can be tested against a fake, without changing the hot path's performance characteristics or its current behaviour", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "search across message bodies is being asked for by three customers and we have no plan for it. i'd like the options weighed — in the storage engine, a separate index, or a managed service — against our EU data residency commitment, our self-hosted customers who won't run another component, and the fact that we have nobody with search experience", "purpose": "planning", "secondary": "review", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "customers running us on ARM nodes have asked twice now and we've never built for it, which means images, the storage engine's intrinsics, and whatever assumptions our chart makes about node labels. work out what supporting ARM would actually involve and whether it's a week or a quarter, then start on the multi-arch image build if it's the former", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "we need an endpoint the mobile clients hit on reconnect that returns everything they missed since a given LSN, bounded so a device offline for a month doesn't pull a gigabyte. cap it, tell the client when it's been truncated so it can fall back to a fresh sync, and make sure it works when the LSN is from a shard that has since been split", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} +{"prompt":"Kestrel: projects/dovetail/apps/console/routes/usage.svelte 里的 DovetailLumenChartStore 最近在 Playwright 流程中出现间歇性问题。 请完成 responsive layout、空状态、retry、键盘焦点、dark mode 和 reduced motion。\n\n约束：\n- 继续使用 Playwright\n- 保持兼容性和取消语义\n- 改动只限于 DovetailLumenChartStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"Does DovetailSableParserService enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Is there a cleaner way to separate DovetailSummitProxyStore'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":"Test Suite 'DovetailEmberRelayFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[DovetailEmberRelayFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/dovetail/ml/pipeline/features.py:144: error: -[DovetailEmberRelayFlowTests 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 '-[DovetailEmberRelayFlowTests 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\nFinish the visible DovetailEmberRelayFlow 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":"Lumen: # projects/dovetail/src/sync/reconcile.ts\n[worker.dovetailnimbusformflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetailnimbusformflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetailnimbusformflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailNimbusFormFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44138\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/dovetail/src/sync/reconcile.ts and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"The behavior of DovetailWrenExportService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/dovetail/apps/console/routes/usage.svelte. 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- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Playwright operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS 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":"DovetailFlintTimelineCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Maple: The DovetailVelaDrawerFlow surface in projects/dovetail/app/src/main/SyncWorker.kt 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":"Security flagged DovetailMarbleTokenService for a read-only pass because its Terraform boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Terraform operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-44128: finish the compact DovetailCraneWorkspaceFlow filter experience\n\nRoute: /catalog/search\nSource: projects/dovetail/db/migrations/20260730_events.sql\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\nBring DovetailCraneWorkspaceFlow'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":"How does DovetailAmberFilterFlow propagate cancellation through the Terraform boundary, and are there code paths where ownership becomes ambiguous? Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Em projects/dovetail/web/components/FilterDrawer.vue, o DovetailDeltaCanvasStore tem um problema intermitente no fluxo de Redis Streams. A causa já é conhecida: mude apenas o timeout de staging de 15 para 30 segundos e ajuste a assertion.\n\nRestrições:\n- continuar com Redis Streams\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao DovetailDeltaCanvasStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"pt"} +{"prompt":"For DovetailPrismCacheCoordinator, assess ownership and failure handling in projects/dovetail/app/src/main/SyncWorker.kt; once that is complete, capture the contract and rollback note for consumers. Work from projects/dovetail/app/src/main/SyncWorker.kt, stay with Playwright, and make rollback possible without deleting user data. Keep the two outcomes separately reviewable.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Incident timeline — INC-44148\n\n08:02 deploy DovetailWillowCodecFlow 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 DovetailWillowCodecFlow 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":"DovetailJuniperCLICoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"What is the safest way to split projects/dovetail/cmd/exporter/main.py into independently owned modules while DovetailMoonlitSDKService's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Rename DovetailTideWorkerStore's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Ticket OPS-44133: retire the legacy replay path for DovetailPrismCacheFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for DovetailPrismCacheFlow, 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":"thread 'tokio-runtime-worker' panicked at projects/dovetail/web/components/FilterDrawer.vue:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: dovetailcopperbridgeflow::scheduler::LeaseTask::flush\n at ./projects/dovetail/web/components/FilterDrawer.vue:217:18\n 4: dovetailcopperbridgeflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nFind the source of this DovetailCopperBridgeFlow 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":"Does DovetailBasilRunnerService enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"DovetailCedarPolicyCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Nimbus: Ticket OPS-44111: retire the legacy replay path for DovetailBeaconStoreFlow\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 DovetailBeaconStoreFlow 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":"Opal: What does DovetailOspreyJobService own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Is DovetailTideWorkerService safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Release verification found a single stale DovetailSlateEditorStore value; the cause, desired value, and affected assertion are already agreed. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Core Data operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Prism: Incident timeline — INC-44116\n\n08:02 deploy DovetailFrostPanelFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current DovetailFrostPanelFlow 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":"Could the reasoning behind DovetailDriftConsoleStore's Redis Streams choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"DovetailFlintTimelineService 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":"Two asks around DovetailCopperBridgeCoordinator: (1) find the unknown cause of stale cursors when a page is resumed; (2) give the existing implementation a read-only safety pass. Make rollback possible without deleting user data, and leave a clear boundary between the resulting artifacts or edits.","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"DovetailPineMetricsCoordinator: ship, then document","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Describe DovetailFernSnapshotStore's error envelope","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Quartz: Ticket OPS-44149: retire the legacy replay path for DovetailEchoRegistryFlow\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 DovetailEchoRegistryFlow 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":"En projects/dovetail/config/staging.toml, DovetailBeaconStoreStore tiene un problema intermitente en el flujo de React 19. La causa ya está clara: cambia solo el timeout de staging de 15 a 30 segundos y ajusta su assertion.\n\nRestricciones:\n- seguir con React 19\n- conservar compatibilidad y cancelación\n- limitar el cambio a DovetailBeaconStoreStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"es"} +{"prompt":"DovetailRavenSessionService's metric is misspelled as succesful_total in one declaration. Correct that literal and its exact test expectation, without renaming anything else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Raven: Incident timeline — INC-44118\n\n08:02 deploy DovetailFernSnapshotFlow 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 DovetailFernSnapshotFlow 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":"Fresh release brief for DovetailAcornWidgetCoordinator:\n- primary outcome: assess ownership and failure handling in projects/dovetail/engine/render/atlas.cpp\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/dovetail/engine/render/atlas.cpp\n- platform constraint: Terraform\n- known complication: an empty state that flashes before cached data arrives\n\nBoth results are required, but they should remain independently reviewable. Make rollback possible without deleting user data; 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.8,"slice":"mixed","lang":"en"} +{"prompt":"DovetailCoralUploadCoordinator is blocking the next release because a deadlock that appears only during shutdown. I need two concrete outcomes from a single pass: find the unknown cause of a deadlock that appears only during shutdown, and capture the contract and rollback note for consumers. Use the existing Core Data conventions in projects/dovetail/Sources/CLI/Commands/Doctor.swift; make rollback possible without deleting user data. Keep the outcomes distinct so reviewers can see which evidence supports the assessment and which files or prose satisfy the requested change.\n\nConstraints:\n- preserve public wire values and tenant boundaries\n- cover cancellation and retry behavior\n- avoid generated code and unrelated cleanup\n- include a rollback trigger that an on-call engineer can measure\n\nThis is a fresh workstream for the release, so derive everything from the repository and the context here.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"# projects/dovetail/pkg/cache/lease.rs\n[worker.dovetailasterwebhookflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetailasterwebhookflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetailasterwebhookflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailAsterWebhookFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44126\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/dovetail/pkg/cache/lease.rs and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"On compact widths, DovetailCinderAuthService'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.4,"slice":"core","lang":"en"} +{"prompt":"Sable: Incident timeline — INC-44156\n\n08:02 deploy DovetailMosaicGridCoordinator 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 DovetailMosaicGridCoordinator 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":"Tide: Ticket OPS-44143: retire the legacy replay path for DovetailLumenChartFlow\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 DovetailLumenChartFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"A previously stable test around DovetailWillowCodecStore 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":"diff --git a/projects/dovetail/ui/settings/PrivacyPane.tsx b/projects/dovetail/ui/settings/PrivacyPane.tsx\nindex 62d71aa..90f3c1e 100644\n--- a/projects/dovetail/ui/settings/PrivacyPane.tsx\n+++ b/projects/dovetail/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\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Read the artifact above as a skeptical reviewer. Is DovetailTideWorkerFlow'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":"DovetailMicaProfileCoordinator: polish the last piece","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Support wants the behavior in projects/dovetail/web/components/FilterDrawer.vue recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Ticket OPS-44113: retire the legacy replay path for DovetailWrenExportFlow\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\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Add the bounded DovetailWrenExportFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Umbra: Ticket OPS-44136: retire the legacy replay path for DovetailGarnetModalFlow\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 DovetailGarnetModalFlow 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":"DovetailFernSnapshotCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Corrija o timeout de DovetailCloudReconcilerService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"pt"} +{"prompt":"Before we approve DovetailNimbusFormService, assess whether lost focus when the drawer animation finishes is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"DovetailKiteSchedulerFlow needs an idempotent replay endpoint backed by Core Data; accept a cursor, cap each page at 500 items, and return a stable continuation token.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"DovetailSpruceDaemonCoordinator: ship a sensible version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"The next client release depends on a new DovetailCoralUploadService capability in projects/dovetail/Sources/App/SessionStore.swift, with Core Data already chosen by the platform group. Implement the endpoint and durable cursor, enforce tenant authorization and idempotency, emit useful spans, cap work per request, and include focused tests for retries, cancellation, and malformed cursors.\n\nConstraints:\n- make rollback possible without deleting user data\n- stay compatible with the existing Core Data deployment\n- keep the work scoped to DovetailCoralUploadService and its direct tests\n\nThis repository spans game tooling, data pipelines, macOS; use its existing conventions rather than importing a new abstraction.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Vela: The data is already available in projects/dovetail/pkg/cache/lease.rs; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Parse DovetailHarborIndexStore's signed cursor","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Two deliverables are holding up DovetailWrenExportCoordinator. First, find the unknown cause of out-of-order events after consumer rebalancing. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/dovetail/app/src/main/SyncWorker.kt, which follows Playwright conventions and currently suffers from out-of-order events after consumer rebalancing. Make rollback possible without deleting user data.\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":"DovetailSpruceDaemonService returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/dovetail/web/components/FilterDrawer.vue and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Willow: Ticket OPS-44141: retire the legacy replay path for DovetailMicaProfileFlow\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 DovetailMicaProfileFlow 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":"// projects/dovetail/infra/modules/edge/main.tf\nfinal class DovetailFlintTimelineFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 DovetailFlintTimelineFlow; 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":"DovetailWillowCodecCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"PM is preparing the DovetailIrisBatchService rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside DovetailIrisBatchService\n- make rollback possible without deleting user data\n\nThe relevant code crosses game tooling, data pipelines, macOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Split DovetailJuniperCLIStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-44154\n\n08:02 deploy DovetailMarbleTokenCoordinator 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 DovetailMarbleTokenCoordinator, 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":"DovetailSlateEditorCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"A copied hex color in DovetailEmberRelayService lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"DovetailTideWorkerCoordinator needs a paired pass: assess ownership and failure handling in projects/dovetail/workers/thumbnail/consumer.ex, plus capture the contract and rollback note for consumers. Use projects/dovetail/workers/thumbnail/consumer.ex as the source of truth, preserve the Terraform contract, and avoid unrelated cleanup.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Xylem: # projects/dovetail/cmd/exporter/main.py\n[worker.dovetailslateeditorflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetailslateeditorflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetailslateeditorflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailSlateEditorFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44117\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/dovetail/cmd/exporter/main.py and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Yarrow: Two asks around DovetailNovaPickerCoordinator: (1) lay out a staged migration for DovetailNovaPickerCoordinator; (2) also add the visible loading and offline states. Make rollback possible without deleting user data, and leave a clear boundary between the resulting artifacts or edits.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"In projects/dovetail/packages/api/openapi.yaml hat DovetailBeaconStoreService 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 DovetailBeaconStoreService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um DovetailBeaconStoreService mit React 19 kompatibel.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"de"} +{"prompt":"DovetailFrostPanelCoordinator: correct, then assess","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Outline a safer DovetailCedarPolicyStore cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-44150\n\n08:02 deploy DovetailDriftConsoleCoordinator 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 DovetailDriftConsoleCoordinator 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":"Fresh release brief for DovetailBeaconStoreCoordinator:\n- primary outcome: separate DovetailBeaconStoreCoordinator's policy from transport without behavior changes\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/dovetail/config/staging.toml\n- platform constraint: React 19\n- known complication: a feature flag whose default differs between environments\n\nBoth results are required, but they should remain independently reviewable. Make rollback possible without deleting user data; 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":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"thread 'tokio-runtime-worker' panicked at projects/dovetail/pkg/cache/lease.rs:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: dovetailbasilrunnerflow::scheduler::LeaseTask::flush\n at ./projects/dovetail/pkg/cache/lease.rs:217:18\n 4: dovetailbasilrunnerflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nFind the source of this DovetailBasilRunnerFlow symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Describe DovetailJuniperCLIService's error envelope","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"The DovetailEchoRegistryService empty state in projects/dovetail/ui/settings/PrivacyPane.tsx needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Zephyr: projects/dovetail/internal/auth/refresh.go now contains DovetailFlintTimelineStore'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":"DovetailRainfallDBCoordinator: restructure, then document","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Release verification found a single stale DovetailOrbitSyncService value; the cause, desired value, and affected assertion are already agreed. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Redis Streams operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Flip DovetailNovaPickerStore's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Please resist widening this one: DovetailCoralUploadStore works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside DovetailCoralUploadStore\n- make rollback possible without deleting user data\n\nThe relevant code crosses game tooling, data pipelines, macOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"DovetailRavenSessionCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating two validators with subtly different error strings in DovetailCinderAuthStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Flip DovetailPrismCacheService's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"DovetailEchoRegistryCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating two validators with subtly different error strings in DovetailBirchMigratorService, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add a bounded DovetailBirchMigratorStore export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'DovetailSummitProxyCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[DovetailSummitProxyCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/dovetail/services/ledger/replay.go:144: error: -[DovetailSummitProxyCoordinatorTests 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 '-[DovetailSummitProxyCoordinatorTests 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 DovetailSummitProxyCoordinator's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"How should DovetailQuartzPlayerService be decomposed?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"Ticket OPS-44123: retire the legacy replay path for DovetailRainfallDBFlow\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 DovetailRainfallDBFlow 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":"Checkout: A flaky failure around DovetailAmberFilterStore survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside DovetailAmberFilterStore\n- make rollback possible without deleting user data\n\nThe relevant code crosses game tooling, data pipelines, macOS. Prefer evidence from the repository and make any assumption explicit.\n\nA real symptom is present, so follow evidence to a cause rather than stopping at a walkthrough.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Exporter: Ticket OPS-44151: retire the legacy replay path for DovetailMapleQueueCoordinator\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 DovetailMapleQueueCoordinator 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":"Design handed over a final pass for DovetailWrenExportStore, and the basic data flow in projects/dovetail/app/src/main/SyncWorker.kt already works. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- make rollback possible without deleting user data\n- stay compatible with the existing Playwright deployment\n- keep the work scoped to DovetailWrenExportStore and its direct tests\n\nThis repository spans game tooling, data pipelines, macOS; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Queue DovetailOpalRouterStore's expired sessions","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"# projects/dovetail/src/sync/reconcile.ts\n[worker.dovetailirisbatchcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetailirisbatchcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetailirisbatchcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailIrisBatchCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44158\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/dovetail/src/sync/reconcile.ts. 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":"PM needs a concise migration note for DovetailIrisBatchFlow, 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":"Give DovetailEchoRegistryStore'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.5,"slice":"core","lang":"en"} +{"prompt":"Scheduler: // projects/dovetail/Sources/App/SessionStore.swift\nfinal class DovetailCoralUploadFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 DovetailCoralUploadFlow'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":"Please resist widening this one: DovetailQuartzPlayerStore works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside DovetailQuartzPlayerStore\n- make rollback possible without deleting user data\n\nThe relevant code crosses game tooling, data pipelines, macOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Memory attributed to DovetailDriftConsoleFlow rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"En projects/dovetail/app/src/main/SyncWorker.kt, DovetailVelaDrawerService tiene un problema intermitente en el flujo de Playwright. Separa responsabilidades y elimina duplicación, conservando API, wire values, orden y comportamiento observable.\n\nRestricciones:\n- seguir con Playwright\n- conservar compatibilidad y cancelación\n- limitar el cambio a DovetailVelaDrawerService Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con Playwright alrededor de DovetailVelaDrawerService.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"es"} +{"prompt":"Bring DovetailVelaDrawerStore'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.5,"slice":"core","lang":"en"} +{"prompt":"Three teams extended DovetailMapleQueueService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current React 19 operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Extract DovetailFrostPanelService's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"DovetailMoonlitSDKCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Dashboard: projects/dovetail/app/src/main/SyncWorker.kt の DovetailLumenChartService で、Playwright の flow に断続的な問題が起きています。 段階、互換性、metrics、rollback、ownership を提案し、コード変更の前で止めてください。\n\n制約:\n- Playwright を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は DovetailLumenChartService のみ","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"} +{"prompt":"DovetailOspreyJobCoordinator needs a paired pass: finish DovetailOspreyJobCoordinator's responsive empty and retry states, plus give the existing implementation a read-only safety pass. Use projects/dovetail/Sources/CLI/Commands/Doctor.swift as the source of truth, preserve the Core Data contract, and avoid unrelated cleanup.","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Two deliverables are holding up DovetailOrbitSyncCoordinator. First, find the unknown cause of cancellation being swallowed at the repository boundary. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/dovetail/infra/modules/edge/main.tf, which follows Redis Streams conventions and currently suffers from cancellation being swallowed at the repository boundary. Make rollback possible without deleting user data.\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":"For DovetailHarborIndexCoordinator, assess ownership and failure handling in projects/dovetail/lib/codec/frame.cc; once that is complete, capture the contract and rollback note for consumers. Work from projects/dovetail/lib/codec/frame.cc, stay with Terraform, and make rollback possible without deleting user data. Keep the two outcomes separately reviewable.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Worker: Incident timeline — INC-44144\n\n08:02 deploy DovetailBirchMigratorFlow 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 DovetailBirchMigratorFlow 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":"Where did DovetailOspreyJobStore's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"For DovetailCloudReconcilerCoordinator, separate DovetailCloudReconcilerCoordinator's policy from transport without behavior changes; once that is complete, correct the known stale timeout beside it. Work from projects/dovetail/cmd/exporter/main.py, stay with Core Data, and make rollback possible without deleting user data. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"I inherited DovetailFrostPanelStore and need a careful read of projects/dovetail/pkg/cache/lease.rs before I can sign off on the next release. 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- make rollback possible without deleting user data\n- stay compatible with the existing React 19 deployment\n- keep the work scoped to DovetailFrostPanelStore and its direct tests\n\nThis repository spans game tooling, data pipelines, macOS; use its existing conventions rather than importing a new abstraction.\n\nNothing is reported broken, so judge and explain current behavior without inventing a failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Read projects/dovetail/db/migrations/20260730_events.sql and tell me whether DovetailWillowCodecService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-44131: retire the legacy replay path for DovetailNovaPickerFlow\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 DovetailNovaPickerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"# projects/dovetail/ml/pipeline/features.py\n[worker.dovetailcloudreconcilerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetailcloudreconcilerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetailcloudreconcilerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailCloudReconcilerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44127\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 DovetailCloudReconcilerFlow'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":"Test Suite 'DovetailLedgerGateFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[DovetailLedgerGateFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/dovetail/workers/thumbnail/consumer.ex:144: error: -[DovetailLedgerGateFlowTests 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 '-[DovetailLedgerGateFlowTests 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\nFind the source of this DovetailLedgerGateFlow 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":"Simulator: Test Suite 'DovetailAmberFilterCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[DovetailAmberFilterCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/dovetail/workers/thumbnail/consumer.ex:144: error: -[DovetailAmberFilterCoordinatorTests 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 '-[DovetailAmberFilterCoordinatorTests 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\nFinish the visible DovetailAmberFilterCoordinator 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Summarize the DovetailRainfallDBService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Runbook: Test Suite 'DovetailVelaDrawerCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[DovetailVelaDrawerCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/dovetail/apps/console/routes/usage.svelte:144: error: -[DovetailVelaDrawerCoordinatorTests 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 '-[DovetailVelaDrawerCoordinatorTests 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 を維持し、根拠と判断を明確にしてください。 Finish the visible DovetailVelaDrawerCoordinator 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":"Is there a cleaner way to separate DovetailEmberRelayStore'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":"Style DovetailCopperBridgeService's offline state","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Security flagged DovetailIrisBatchStore for a read-only pass because its Playwright boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Playwright operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS monorepo, so keep ownership and handoff points understandable in a small review.\n\nNothing is reported broken, so judge and explain current behavior without inventing a failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Two asks around DovetailCraneWorkspaceCoordinator: (1) produce a consumer guide for DovetailCraneWorkspaceCoordinator; (2) correct the known stale timeout beside it. Make rollback possible without deleting user data, and leave a clear boundary between the resulting artifacts or edits.","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"The destination for DovetailKiteSchedulerService is broadly agreed; the missing piece is a reversible route from projects/dovetail/Sources/CLI/Commands/Doctor.swift to that target. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside DovetailKiteSchedulerService\n- make rollback possible without deleting user data\n\nThe relevant code crosses game tooling, data pipelines, macOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Support wants the behavior in projects/dovetail/ml/pipeline/features.py recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"What sequence would let DovetailMicaProfileService adopt React 19 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":"Production says DovetailAcornWidgetStore is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Reconstruct the failing timeline from logs and tests, identify which invariant first breaks, and distinguish causal signals from effects or cleanup noise.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Terraform operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS monorepo, so keep ownership and handoff points understandable in a small review.\n\nA real symptom is present, so follow evidence to a cause rather than stopping at a walkthrough.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"DovetailNimbusFormCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Trace: projects/dovetail/config/staging.toml の DovetailMapleQueueFlow で、React 19 の flow に断続的な問題が起きています。 現在の flow を読み、ownership、cancel、順序が安全か評価してください。分析だけで十分です。\n\n制約:\n- React 19 を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は DovetailMapleQueueFlow のみ","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"ja"} +{"prompt":"Move DovetailMapleQueueStore'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":"Compare the old and new DovetailAtlasSearchFlow adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Please resist widening this one: DovetailSummitProxyService works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside DovetailSummitProxyService\n- make rollback possible without deleting user data\n\nThe relevant code crosses game tooling, data pipelines, macOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Diff: projects/dovetail/services/ledger/replay.go 里的 DovetailDeltaCanvasService 最近在 Redis Streams 流程中出现间歇性问题。 请拆分职责并去掉重复，同时保持 API、wire value、顺序和可观察行为不变。\n\n约束：\n- 继续使用 Redis Streams\n- 保持兼容性和取消语义\n- 改动只限于 DovetailDeltaCanvasService","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"Profiler: projects/dovetail/infra/modules/edge/main.tf has grown through several launches, and DovetailOrbitSyncStore now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- make rollback possible without deleting user data\n- stay compatible with the existing Redis Streams deployment\n- keep the work scoped to DovetailOrbitSyncStore and its direct tests\n\nThis repository spans game tooling, data pipelines, macOS; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Where did DovetailAsterWebhookService's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Compare DovetailCraneWorkspaceService's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"How should DovetailNovaPickerService be decomposed?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-44124: finish the compact DovetailHarborIndexFlow filter experience\n\nRoute: /catalog/search\nSource: projects/dovetail/engine/render/atlas.cpp\nFramework: Terraform\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 DovetailHarborIndexFlow'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":"2026-07-30T08:14:11.409Z level=info service=dovetailsprucedaemonflow pod=dovetailsprucedaemonflow-7cf8 request_id=44145 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=dovetailsprucedaemonflow request_id=44145 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=dovetailsprucedaemonflow request_id=44145 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=dovetailsprucedaemonflow request_id=44145 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=dovetailsprucedaemonflow request_id=44145 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=dovetailsprucedaemonflow request_id=44145 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=dovetailsprucedaemonflow request_id=44145 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=dovetailsprucedaemonflow request_id=44145 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Reconstruct the DovetailSpruceDaemonFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"The data is already available in projects/dovetail/db/migrations/20260730_events.sql; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Collapse the DovetailFernSnapshotService wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Console: The name pendingAck means two different things across DovetailMarbleTokenFlow's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Split projects/dovetail/ui/settings/PrivacyPane.tsx by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Read projects/dovetail/crates/index/src/segment.rs and tell me whether DovetailGarnetModalService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Map DovetailRainfallDBStore's ownership split","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"projects/dovetail/crates/index/src/segment.rs now contains DovetailBasilRunnerStore'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":"Could DovetailMosaicGridStore show the active React 19 sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/dovetail/services/ledger/replay.go b/projects/dovetail/services/ledger/replay.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/dovetail/services/ledger/replay.go\n+++ b/projects/dovetail/services/ledger/replay.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate DovetailQuartzPlayerFlow'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":"Split projects/dovetail/services/ledger/replay.go by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"DovetailSableParserCoordinator: handle the lingering thing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"DovetailCinderAuthCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-44130\n\n08:02 deploy DovetailOpalRouterFlow 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 DovetailOpalRouterFlow, 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":"Could DovetailAsterWebhookStore migrate incrementally?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} +{"prompt":"Polish the DovetailCopperBridgeStore toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"DovetailLumenChartCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"On compact widths, DovetailSableParserStore'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":"Workspace: Split DovetailCedarPolicyService without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"thread 'tokio-runtime-worker' panicked at projects/dovetail/workers/thumbnail/consumer.ex:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: dovetailravensessionflow::scheduler::LeaseTask::flush\n at ./projects/dovetail/workers/thumbnail/consumer.ex:217:18\n 4: dovetailravensessionflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nReconstruct the DovetailRavenSessionFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Extract DovetailHarborIndexService's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Repository: // projects/dovetail/config/staging.toml\nfinal class DovetailPineMetricsFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Wire DovetailPineMetricsFlow'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":"Release verification found a single stale DovetailAtlasSearchService value; the cause, desired value, and affected assertion are already agreed. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Core Data operational envelope\n\nSeveral teams work in this game tooling, data pipelines, macOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Unifie les validateurs de DovetailCloudReconcilerStore","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"fr"} +{"prompt":"DovetailAsterWebhookCoordinator needs a paired pass: produce a consumer guide for DovetailAsterWebhookCoordinator, plus give the existing implementation a read-only safety pass. Use projects/dovetail/crates/index/src/segment.rs as the source of truth, preserve the React 19 contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"DovetailQuartzPlayerCoordinator is blocking the next release because a flaky snapshot caused by locale-dependent sorting. I need two concrete outcomes from a single pass: finish DovetailQuartzPlayerCoordinator's responsive empty and retry states, and capture the contract and rollback note for consumers. Use the existing Redis Streams conventions in projects/dovetail/web/components/FilterDrawer.vue; make rollback possible without deleting user data. 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":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"DovetailDeltaCanvasCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-44134\n\n08:02 deploy DovetailSableParserFlow 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 DovetailSableParserFlow 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":"Does DovetailSlateEditorService preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"# projects/dovetail/lib/codec/frame.cc\n[worker.dovetailacornwidgetflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetailacornwidgetflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetailacornwidgetflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailAcornWidgetFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44114\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/dovetail/lib/codec/frame.cc and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"DovetailBasilRunnerCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"DovetailBirchMigratorCoordinator: rethink this area","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Before we approve DovetailGarnetModalStore, assess whether lost focus when the drawer animation finishes is an actual correctness risk or merely confusing structure. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Our support and SDK teams keep answering the same questions about DovetailMosaicGridService, but the current prose in projects/dovetail/pkg/cache/lease.rs only describes the happy path. 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- make rollback possible without deleting user data\n- stay compatible with the existing React 19 deployment\n- keep the work scoped to DovetailMosaicGridService and its direct tests\n\nThis repository spans game tooling, data pipelines, macOS; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"DovetailLedgerGateCoordinator: polish, then correct","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Is there a cleaner way to separate DovetailMicaProfileStore'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":"Pipeline: diff --git a/projects/dovetail/cmd/exporter/main.py b/projects/dovetail/cmd/exporter/main.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/dovetail/cmd/exporter/main.py\n+++ b/projects/dovetail/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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Add the bounded DovetailMoonlitSDKFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"This should remain a deliberately small patch: DovetailDriftConsoleService has one known configuration mistake in projects/dovetail/infra/modules/edge/main.tf, not an open-ended failure investigation. 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- make rollback possible without deleting user data\n- stay compatible with the existing Redis Streams deployment\n- keep the work scoped to DovetailDriftConsoleService and its direct tests\n\nThis repository spans game tooling, data pipelines, macOS; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"For DovetailOpalRouterCoordinator, change DovetailOpalRouterCoordinator's known staging timeout from 15 to 30 seconds; once that is complete, capture the contract and rollback note for consumers. Work from projects/dovetail/infra/modules/edge/main.tf, stay with Redis Streams, and make rollback possible without deleting user data. Keep the two outcomes separately reviewable.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Gateway: projects/dovetail/lib/codec/frame.cc now contains DovetailMarbleTokenStore'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.4,"slice":"core","lang":"en"} +{"prompt":"DovetailGarnetModalCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Renderer: # projects/dovetail/Sources/CLI/Commands/Doctor.swift\n[worker.dovetailcinderauthflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetailcinderauthflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetailcinderauthflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailCinderAuthFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44142\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 DovetailCinderAuthFlow'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":"Indexer: Split DovetailOpalRouterService without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Documente le contrat DovetailLedgerGateService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"fr"} +{"prompt":"diff --git a/projects/dovetail/Sources/App/SessionStore.swift b/projects/dovetail/Sources/App/SessionStore.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/dovetail/Sources/App/SessionStore.swift\n+++ b/projects/dovetail/Sources/App/SessionStore.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is DovetailOspreyJobFlow'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":"Apparently: Incident timeline — INC-44157\n\n08:02 deploy DovetailAtlasSearchCoordinator 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nReconstruct the DovetailAtlasSearchCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Lately: # projects/dovetail/services/ledger/replay.go\n[worker.dovetaildeltacanvasflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.dovetaildeltacanvasflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.dovetaildeltacanvasflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.DovetailDeltaCanvasFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-44135\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/dovetail/services/ledger/replay.go and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"The data is already available in projects/dovetail/Sources/App/SessionStore.swift; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Walk through DovetailCraneWorkspaceStore's reconcile.ts","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Trace DovetailAcornWidgetService's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Oddly: Incident timeline — INC-44110\n\n08:02 deploy DovetailOrbitSyncFlow 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 DovetailOrbitSyncFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Currently: // projects/dovetail/Sources/App/SessionStore.swift\nfinal class DovetailKiteSchedulerCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 DovetailKiteSchedulerCoordinator 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":"Sketch the DovetailPineMetricsService migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Drop DovetailPineMetricsStore's unused import","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Today: Incident timeline — INC-44120\n\n08:02 deploy DovetailJuniperCLIFlow 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 DovetailJuniperCLIFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Translate the DovetailPrismCacheStore setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Context: Incident timeline — INC-44122\n\n08:02 deploy DovetailCedarPolicyFlow 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 DovetailCedarPolicyFlow 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":"Two engineers disagree about whether DovetailAtlasSearchStore's cache is authoritative. Walk the reads and writes in projects/dovetail/cmd/exporter/main.py and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"We expect DovetailAmberFilterService to outgrow its current Terraform arrangement next quarter, but changing everything at once would be risky. 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- make rollback possible without deleting user data\n- stay compatible with the existing Terraform deployment\n- keep the work scoped to DovetailAmberFilterService and its direct tests\n\nThis repository spans game tooling, data pipelines, macOS; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"DovetailEmberRelayCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Ist DovetailLedgerGateStore sicher?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"de"} diff --git a/data/round2-05.jsonl b/data/round2-05.jsonl index 98f6b95..d9ff5e7 100644 --- a/data/round2-05.jsonl +++ b/data/round2-05.jsonl @@ -1,200 +1,200 @@ -{"prompt": "a pull request that touches the player's ABR logic. i'd rather understand it than approve it:\n\n@@ -88,14 +88,22 @@ export class AbrController {\n- private pickLevel(bandwidth: number): number {\n- return this.levels.findLastIndex(l => l.bitrate < bandwidth * 0.8)\n- }\n+ private pickLevel(bandwidth: number): number {\n+ const buffer = this.media.buffered.length\n+ ? this.media.buffered.end(0) - this.media.currentTime\n+ : 0\n+ const factor = buffer > 20 ? 0.95 : buffer > 8 ? 0.8 : 0.5\n+ const idx = this.levels.findLastIndex(l => l.bitrate < bandwidth * factor)\n+ if (idx < this.currentLevel - 1) return this.currentLevel - 1\n+ return idx\n+ }\n\nthe stated goal is fewer rebuffers; the risk i can see is that we never drop more than one level at a time", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "our API changelog needs an entry for the stream key header change, with what integrators must do before october", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "the QoE dashboard's session sampler shows twenty random sessions with no way to see what happened in one, which is exactly what you want during an incident. build the session timeline view — events on a time axis, bitrate switches, rebuffers, errors — and decide with me first whether it belongs as a drawer or its own route", "purpose": "frontendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "a tidy-up pass, nothing risky", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "our stream keys appear in the ingest access logs because they're in the path, which security flagged this morning", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "the reconciliation method recomputes an account balance from every journal entry ever posted and then writes a snapshot, and it's called from a page that refreshes every ten seconds. before i touch it i want to know what it costs on our largest account and whether the snapshot write can race with a concurrent posting", "purpose": "review", "secondary": "planning", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "invoice posting throws this maybe twice a week in production, never in test:\n\nSystem.Data.SqlClient.SqlException (0x80131904): Transaction (Process ID 88) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.\n at Ledger.Posting.PostingService.PostAsync(PostingBatch batch, CancellationToken ct) in /src/Ledger.Posting/PostingService.cs:line 212\n at Ledger.Api.Controllers.InvoicesController.Post(InvoiceRequest req) in /src/Ledger.Api/Controllers/InvoicesController.cs:line 88\n at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.TaskOfIActionResultExecutor.Execute(...)\n\nClientConnectionId:8f2b1c40-9a11-4c02-b771-041ac0aa7719\nError Number:1205,State:51,Class:13\n\nthe deadlock graph shows two sessions on the same page of `JournalEntries`, both doing an insert then an update to `Accounts.Balance`", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "one currency conversion helper, five callers", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "transcode workers keep dying on a subset of uploads and ffmpeg's output is all i have:\n\n[hls @ 0x55d1a2] Opening 'seg_00041.ts' for writing\n[libx264 @ 0x55d3f0] frame= 4118 fps=118 q=28.0 size= 204800kB\n[mpegts @ 0x55d880] Non-monotonous DTS in output stream 0:1; previous: 8412000, current: 8409600; changing to 8412001. This may result in incorrect timestamps in the output file.\n[mpegts @ 0x55d880] Non-monotonous DTS in output stream 0:1; previous: 8412001, current: 8409601; changing to 8412002.\n[aac @ 0x55e110] Queue input is backward in time\nav_interleaved_write_frame(): Invalid argument\n[hls @ 0x55d1a2] Could not write header for output file #0 (incorrect codec parameters ?): Invalid argument\nConversion failed!\n\nexit status 1, worker restarts, next attempt fails the same way. always the same 40 or so source files", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "extension breaks on exactly one customer's intranet and their IT sent us the console:\n\nUncaught (in promise) Error: Extension context invalidated.\n at chrome-extension://hkpmbaflnkkcgnbjcplkflmpjeaeblnc/content.js:1:44112\nRefused to connect to 'https://api.lumenclip.io/v1/sync' because it violates the following Content Security Policy directive: \"connect-src 'self' https://intranet.corp.example\"\ncontent.js:1 Uncaught (in promise) TypeError: Failed to fetch\nservice-worker.js:1 Unchecked runtime.lastError: The message port closed before a response was received.\nservice-worker.js:1 Uncaught (in promise) Error: No tab with id: 4118.\n\nmanifest v3, and this works on every other site we've tried", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "CDN origin sees a thundering herd every ten minutes and i can't work out from these logs whether it's us or them:\n\n11:00:00 GET /hls/8812/master.m3u8 200 cache=MISS age=0 origin=142ms\n11:00:00 GET /hls/8812/master.m3u8 200 cache=MISS age=0 origin=141ms\n11:00:00 GET /hls/8812/master.m3u8 200 cache=MISS age=0 origin=188ms\n(… 1,204 identical lines in the same second …)\n11:00:01 GET /hls/8812/720p/seg_00041.ts 200 cache=HIT age=8\n11:10:00 GET /hls/8812/master.m3u8 200 cache=MISS age=0 origin=904ms\n11:10:00 GET /hls/8812/master.m3u8 500 cache=MISS origin=timeout\n\ncache-control on the playlist is max-age=600, and the players all refresh on a fixed schedule", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "extension's service worker keeps getting killed mid-sync, chrome's internals page shows:\n\nService worker registration: chrome-extension://hkpmbaflnkkcgnbjcplkflmpjeaeblnc/\nStatus: STOPPED\nRunning status: STOPPED\nLast activity: 2026-07-29 11:04:41 (32s)\nTermination reason: idle timeout after 30s\nPending events: 2 (alarm 'sync', message from tab 4118)\n\nlog before termination:\n [sync] starting, 41 clips pending\n [sync] uploaded 12/41\n [sync] worker suspended\n [sync] starting, 29 clips pending\n [sync] uploaded 9/29\n\nevery restart re-uploads the ones that were in flight", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "ingest API's public docs are a curl example and nothing else. this is what the handler accepts:\n\nPOST /v1/ingest/{stream_key}\n content-type: application/octet-stream or multipart/form-data\n headers: X-Segment-Sequence (required, monotonic per stream), X-Segment-Duration-Ms (required),\n X-Discontinuity (optional, \"1\" to mark a discontinuity), Content-MD5 (optional but checked when present)\n behaviour: out-of-order sequences within 3 are buffered for up to 2s; beyond that they are rejected with 409\n a repeated sequence with the same Content-MD5 is a no-op 200; with a different one it is a 409\n segments over 30s are rejected with 413; the stream is terminated after 3 consecutive rejections\n auth is the stream key in the path, which is why it must never appear in logs or referrer headers\n\nwrite the reference page, and be explicit about the retry semantics because every partner gets them wrong", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "player's event emitter has grown three ways to subscribe and i want one, without breaking integrators:\n\nplayer.on('ready', cb) // 3.x style, still used by everyone\nplayer.addEventListener('ready', cb) // added in 4.0 to look DOM-like\nplayer.events.subscribe('ready', cb) // added in 4.2 by someone who likes rxjs\n\ninternally all three end up in the same map, except `events.subscribe` returns an unsubscribe function and the other two don't, and `addEventListener` supports the `once` option which the others ignore", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "QoE dashboard spec from our SRE, build it in the internal console:\n\nQoE overview\n- Time range picker (15m / 1h / 6h / 24h / 7d), defaults to 1h, persists per user.\n- Four headline tiles: rebuffer ratio, startup time p95, error rate, average bitrate. Each with a delta against the previous period and a sparkline.\n- Breakdown table: by CDN edge, by ISP, by player version, switchable with a segmented control. Sortable columns, 20 rows with a \"show all\".\n- Session sampler: 20 random sessions matching the current filters, click to open a session timeline with events plotted on a time axis.\n- Live streams get a separate section with a row per stream, ordered by concurrent viewers, updating every 10 seconds.\n- Anything above the rebuffer threshold is highlighted, but the threshold is configurable and must not be hardcoded.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "live playlist TTL to 2 seconds", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "what does `scenecut: 0` cost us?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "is the outbox write in the same transaction?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "invoice PDF footer shows last year's VAT id", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "core", "lang": "en"} -{"prompt": "one fetch wrapper for the extension", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "month-end close produced numbers that don't tie out, and this is the reconciliation report:\n\nAccount GL Balance Subledger Difference\n1200 AR 1,204,118.42 1,204,118.42 0.00\n2100 AP 882,441.10 882,437.60 3.50\n4000 Revenue 2,118,904.00 2,118,904.00 0.00\n5000 COGS 1,441,220.18 1,441,220.18 0.00\n2200 VAT 188,412.55 188,409.05 3.50\n\nJournal 88412 posted 2026-07-31 23:59:58 by [system]\nJournal 88413 posted 2026-08-01 00:00:02 by [system]\n\nboth journals are for the same invoice batch, and the 3.50 is a rounding line that appears once in the subledger and twice in the GL", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "ADR someone wrote for the packager rewrite. does the reasoning hold up?\n\n## Context\nThe packager keeps one goroutine per live stream, holding the muxer state and the playlist in memory. At 300 streams this is fine; at 3,000 it will not be.\n\n## Decision\nMove packaging into a stateless service. Segment state goes to redis, playlists are rendered on demand from redis, and any instance can serve any stream.\n\n## Consequences\n- Horizontal scaling becomes trivial.\n- Redis becomes a hard dependency on the live path.\n- Playlist rendering moves from once per segment to once per request.\n\n## Alternatives considered\nSharding by stream id was rejected as \"operationally complex\".", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "VAT rounding helper, which is now the subject of an audit finding:\n\npublic static decimal RoundVat(decimal net, decimal rate, RoundingMode mode = RoundingMode.HalfUp)\n{\n var raw = net * rate;\n return mode switch\n {\n RoundingMode.HalfUp => Math.Round(raw, 2, MidpointRounding.AwayFromZero),\n RoundingMode.HalfEven => Math.Round(raw, 2, MidpointRounding.ToEven),\n RoundingMode.Truncate => Math.Truncate(raw * 100) / 100,\n _ => Math.Round(raw, 2)\n };\n}\n\ncredit notes pass a negative net; the default mode is used almost everywhere; and the German tax rules we're being assessed against say to round the absolute value", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "support handover notes about the extension, needs to become a real troubleshooting page:\n\n- \"extension context invalidated\" almost always means they updated the extension while a tab was open, tell them to reload the tab\n- clips not syncing: check the service worker is alive in chrome://serviceworker-internals, it dies after 30s idle and our alarm is set to 5 minutes\n- corporate networks with a strict CSP block our api entirely, there is no workaround, they need to allowlist api.lumenclip.io\n- if the popup is blank, it's usually a failed fetch of the clip list; the popup has no error state at all\n- duplicated clips happen when the worker restarts mid-upload, we dedupe server-side within an hour\n- the \"sign in again\" loop is a cookie partitioning thing on chrome 121+, resolved by opening the site once in the same profile", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "internal wiki page for the close process is three years old. reality according to the team:\n\n- close starts when the last bank statement is imported, usually the 2nd or 3rd\n- the revaluation job must run before any accruals are posted, and it's manual\n- there's a checklist in a spreadsheet that four people maintain differently\n- the \"period lock\" button doesn't stop the system journals, which is how we ended up with entries dated after the lock\n- reopening a period requires a database update, there is no UI for it\n- the whole thing takes 4-6 days and the finance team works weekends for it\n\nwrite the page as it should be, and flag the two things that are process problems rather than documentation problems", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "test project has three ways of building an invoice and every new test picks one at random:\n\nvar invoice = new Invoice { CustomerId = 1, Lines = { new InvoiceLine { Net = 100m, Vat = 19m } } };\n\nvar invoice = InvoiceBuilder.New().ForCustomer(1).WithLine(100m, TaxCode.Standard).Build();\n\nvar invoice = TestData.Invoices.Simple(); // fixture file, 4 hardcoded invoices\n\nabout 400 tests between them; the builder is the newest and the only one that computes VAT the way production does", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "finance team's list of what the legacy billing service still does, and we want it gone by december:\n\n- recurring invoice generation for 1,400 subscriptions on the old plan structure\n- the dunning schedule (3, 7, 14 days) including the emails, which use its own templates\n- revenue recognition postings, which the new service does differently and finance hasn't signed off on\n- a nightly export to the tax filing provider, in a fixed-width format nobody remembers the spec for\n- the customer portal's invoice PDF, generated by a library that only exists in that codebase\n- roughly 200 stored procedures, of which we believe 40 are actually called\n\nwhat's the order, what's the risk, and where would you cut scope", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "design doc stub for the DVR change, i want the thinking before the implementation:\n\nCurrent: DVR window is 2 hours, held as segments in the packager's memory plus S3, playlist rendered from an in-memory ring buffer.\nAsked for: 12 hours, with seeking anywhere in the window, on live streams with up to 40,000 concurrent viewers.\nConstraints: segment storage cost triples if we keep the current bitrate ladder for the whole window; the playlist for a 12-hour window is about 10,000 entries and clients parse it on every refresh; our current CDN caches playlists for 2 seconds; and a stream that restarts mid-event must not lose the earlier part of the window.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "tax lines wrap badly at 1280px", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "docs for the ingest retry semantics", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "why is origin seeing 1200 playlist requests/s?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "packager thing again", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "invoices, the usual", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "ledger domain has accumulated three years of small decisions and is now a single project with sixty classes, no obvious seams, and a test suite that needs a database. i keep being told to \"just refactor it\", but i'd rather agree a target shape first: what the modules should be, what depends on what, and which pieces we'd move in what order without stopping feature work", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "en"} -{"prompt": "player SDK's events table in our docs lists an event that never existed and omits the two that every integrator actually wants for quality metrics. correct the table, explain the difference between a recoverable error and a fatal one, and note which events only fire on live streams — integrators are web developers who will copy whatever we publish", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "an auditor has asked six questions about journal immutability, period locks, numbering gaps, rate sourcing, retention and attachment deletion, and answering them properly means writing the controls document we never had. work each answer out from the code rather than from what we'd like to be true, and mark anything you can't substantiate", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "segment uploader retries with a sleep of attempt seconds, which is zero on the first retry, and it retries with the same reader for live segments", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "we need a position on whether the extension should keep its own sync engine or move to the same one the web app uses", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "CDN config has the playlist TTL wrong for live and it's a two-line change, but i want a sanity check:\n\ncurrent:\n - path: \"*.m3u8\"\n cache: { ttl: 600, stale_while_revalidate: 0 }\n\nproposed:\n - path: \"/live/*/*.m3u8\"\n cache: { ttl: 2, stale_while_revalidate: 4 }\n - path: \"/vod/*/*.m3u8\"\n cache: { ttl: 86400, stale_while_revalidate: 600 }\n\nlive playlists are rewritten every 4 seconds, VOD ones never change once published, and origin currently sees about 1,200 requests per second on playlists alone", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"} -{"prompt": "extension talks to the API from three places, each with its own auth handling:\n\n// content.js\nconst res = await fetch(`${API}/v1/clips`, { headers: { Authorization: `Bearer ${token}` } })\n\n// service-worker.js\nconst res = await fetch(`${API}/v1/sync`, {\n method: 'POST',\n credentials: 'include',\n headers: { 'Content-Type': 'application/json' },\n body: JSON.stringify(payload),\n})\n\n// popup.js\nconst token = await chrome.storage.local.get('token')\nconst res = await fetch(`${API}/v1/clips?limit=50`, { headers: { Authorization: `Bearer ${token.token}` } })\n\none of them uses cookies, two use a bearer token, and only the popup handles a 401", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "live badge needs a text label", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "QoE tiles should show a delta", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "transcode fails on 40 specific files", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "ingest API's retry semantics are the single biggest source of partner integration bugs — repeated sequences, buffering windows, when a 409 is fatal and when it isn't — and none of it is written down anywhere outside the handler. write the reference page a partner engineer could implement against without asking us a single question, including a worked example of a reconnect after a network drop", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "extension's permissions are far wider than what it does, and the store review is friday. work out the minimum set from the code, then narrow the manifest and content script matches accordingly — and tell me what functionality we lose, if any", "purpose": "planning", "secondary": "quickFix", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "what happens to an in-flight ingest when a stream key is rotated — does the session survive or drop?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "is the reconciliation method safe to call from a page that refreshes every ten seconds on an account with 300k entries", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "player's control bar hides itself after three seconds regardless of whether the pointer is still over it, and on touch devices it disappears while you're reaching for the seek bar. rework the auto-hide so it respects hover and recent touch, stays visible whenever a control has focus, and never hides while the settings menu is open", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "pprof from the packager service, memory climbs until the pod is killed:\n\nShowing nodes accounting for 6.14GB, 94.12% of 6.52GB total\n flat flat% sum% cum cum%\n 3.88GB 59.51% 59.51% 3.88GB 59.51% bytes.growSlice\n 1.42GB 21.78% 81.29% 5.30GB 81.29% lumen/packager.(*Muxer).WriteSegment\n 0.61GB 9.36% 90.65% 0.61GB 9.36% lumen/packager.(*Playlist).Render\n 0.23GB 3.53% 94.18% 0.23GB 3.53% encoding/json.Marshal\n\ngoroutines: 41,882\ntop goroutine stack:\n lumen/packager.(*Session).watch\n /src/packager/session.go:141 +0x88\n created by lumen/packager.(*Manager).Start in goroutine 1\n\nwe start one session per live stream and we have about 300 live streams", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "seit dem letzten Deploy stimmen die Umsatzsteuer-Beträge bei Gutschriften nicht mehr:\n\nRechnung 88412 netto 1.000,00 USt 19% = 190,00 brutto 1.190,00 ✓\nGutschrift 88413 netto -1.000,00 USt 19% = -190,00 brutto -1.190,00 ✓\nRechnung 88420 netto 840,34 USt 19% = 159,66 brutto 1.000,00 ✓\nGutschrift 88421 netto -840,34 USt 19% = -159,67 brutto -1.000,01 ✗\n\nDie Differenz von einem Cent tritt nur bei Beträgen auf, die aus einem Bruttobetrag zurückgerechnet wurden. Betroffen sind etwa 200 Belege seit Freitag.", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "de"} -{"prompt": "a broadcaster wants a twelve-hour DVR window and we currently do two, which sounds like a config change until you consider that the playlist becomes ten thousand entries that every client re-parses on each refresh, that keeping the full bitrate ladder for twelve hours triples our storage bill, and that a stream restarting mid-event must not lose what came before. i want the shape of a solution and the trade-offs written down before anyone starts moving segments around", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "our on-call covers ingest, packaging and delivery with alerts written by three different people, and half of them page for things that self-resolve", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "the proration calculation exists four times with four different day-count conventions, and finance considers only the subscriptions one correct. consolidate onto it, work out which historical invoices would have been different under each of the others, and be explicit about whether we're correcting anything retroactively or only going forward", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "a walkthrough of how an invoice becomes a journal entry, naming the services involved, would help before i touch posting", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "our clip editor's trim handles are mouse-only, they don't snap on touch, and there's no keyboard path to adjusting a trim point at all, which came up in the same accessibility review as the player controls. make the handles work with pointer events across devices, keep the 0.1 second snapping, and add the arrow-key nudging the spec asked for", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "the extension's storage is split across chrome.storage.local, chrome.storage.sync and an indexeddb wrapper with no rule about what goes where, which is part of why the sign-in loop happens on some profiles. rationalise it into one layer with an explicit policy, then document the policy where the next person will find it", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "invoice list needs saved filters per user, since finance re-applies the same four every morning", "purpose": "frontendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.5, "slice": "mixed", "lang": "en"} -{"prompt": "one more sweep", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "nightly revaluation job silently produced nothing for two currencies:\n\n[00:15:02] revaluation started, base=EUR, rates_as_of=2026-07-30\n[00:15:02] loaded 41 currencies from provider\n[00:15:03] revaluing 1,204 open items in USD ... 1,204 posted\n[00:15:07] revaluing 882 open items in GBP ... 882 posted\n[00:15:09] revaluing 118 open items in CHF ... 0 posted\n[00:15:09] revaluing 41 open items in SEK ... 0 posted\n[00:15:10] revaluation complete, 2,086 postings, 0 errors\n\nCHF and SEK rates came back from the provider as strings rather than numbers this time, and nothing complained", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "i'm meant to approve this before the release, and the retry loop bothers me:\n\nfunc (u *Uploader) Put(ctx context.Context, key string, r io.Reader) error {\n\tfor attempt := 0; attempt < 5; attempt++ {\n\t\terr := u.s3.Upload(ctx, key, r)\n\t\tif err == nil {\n\t\t\treturn nil\n\t\t}\n\t\tif errors.Is(err, context.Canceled) {\n\t\t\treturn err\n\t\t}\n\t\ttime.Sleep(time.Duration(attempt) * time.Second)\n\t}\n\treturn fmt.Errorf(\"upload %s failed after 5 attempts\", key)\n}\n\ncallers pass an *os.File for small segments and a pipe reader for live ones", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "posting service's transaction scope, which i inherited. is this doing what the comment claims?\n\n// Posts the batch atomically; either every entry lands or none do.\npublic async Task PostAsync(PostingBatch batch, CancellationToken ct)\n{\n using var scope = new TransactionScope(TransactionScopeAsyncFlowOption.Enabled);\n foreach (var entry in batch.Entries)\n {\n await _entries.InsertAsync(entry, ct);\n await _accounts.AdjustBalanceAsync(entry.AccountId, entry.Amount, ct);\n }\n await _outbox.EnqueueAsync(new BatchPosted(batch.Id), ct);\n scope.Complete();\n}\n\n_entries and _accounts use separate DbContext instances from DI, and _outbox writes to the same database", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "manifest for our extension, about to go through store review. anything here that will bounce?\n\n{\n \"manifest_version\": 3,\n \"name\": \"Lumen Clip\",\n \"version\": \"3.4.1\",\n \"permissions\": [\"tabs\", \"storage\", \"scripting\", \"webRequest\", \"cookies\", \"downloads\"],\n \"host_permissions\": [\"\"],\n \"background\": { \"service_worker\": \"service-worker.js\", \"type\": \"module\" },\n \"content_scripts\": [{ \"matches\": [\"\"], \"js\": [\"content.js\"], \"run_at\": \"document_idle\" }],\n \"externally_connectable\": { \"matches\": [\"*://*.lumenclip.io/*\"] },\n \"content_security_policy\": { \"extension_pages\": \"script-src 'self' 'wasm-unsafe-eval'; object-src 'self'\" }\n}\n\nwe only actually need to read the page title and the video element's src", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "cache rules from our CDN config, and origin load has doubled since we shipped them:\n\nrules:\n - path: \"*.m3u8\"\n cache: { ttl: 600, stale_while_revalidate: 0, key: [path, query] }\n - path: \"*.ts\"\n cache: { ttl: 86400, stale_while_revalidate: 60, key: [path] }\n - path: \"/api/*\"\n cache: { ttl: 0 }\n - path: \"*\"\n cache: { ttl: 300, key: [path, query, header:Authorization] }\n\nlive playlists change every 4 seconds; VOD playlists never change after publish; both match the first rule", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "这是我们对账服务的核心方法，接手之后一直没敢动，先帮我看看它到底在做什么、有没有隐患：\n\npublic decimal Reconcile(int accountId, DateTime asOf)\n{\n var entries = _db.JournalEntries\n .Where(e => e.AccountId == accountId && e.PostedAt <= asOf)\n .ToList();\n var balance = entries.Sum(e => e.Amount);\n var snapshot = _db.Balances.FirstOrDefault(b => b.AccountId == accountId && b.AsOf == asOf.Date);\n if (snapshot == null)\n {\n _db.Balances.Add(new Balance { AccountId = accountId, AsOf = asOf.Date, Amount = balance });\n _db.SaveChanges();\n }\n else if (snapshot.Amount != balance)\n {\n snapshot.Amount = balance;\n _db.SaveChanges();\n }\n return balance;\n}\n\n这个方法在报表页面上每次刷新都会被调用，账户的分录有几十万条", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "zh"} -{"prompt": "notas de la sesión de diseño, hay que convertirlas en el documento que se manda a los clientes:\n\n- el nuevo modelo de facturación recurrente permite ciclos mensuales, trimestrales y anuales\n- el prorrateo se calcula por días naturales, no por días laborables\n- si un cliente cambia de plan a mitad de ciclo se emite una nota de crédito por la parte no consumida\n- los impuestos se recalculan siempre en la fecha de emisión, nunca en la fecha del cambio\n- las facturas fallidas se reintentan tres veces: a los 3, 7 y 14 días\n- tras el tercer intento la suscripción pasa a estado suspendido, no cancelado\n- la reactivación no genera una factura nueva, se reintenta la pendiente\n\nel público son administradores financieros, no técnicos", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "es"} -{"prompt": "changelog for the player SDK, from the commits since 4.2:\n\n88f21c0 feat(abr): buffer-aware level selection\n41ba190 fix(hls): handle discontinuity tags in live playlists\nc0aa774 fix(abr): don't drop more than one level per switch\n2e91b45 feat(api): expose `currentLevel` and `levels` on the player instance\naa30f19 fix(ios): audio desync after backgrounding\n9c1d004 perf: reuse the segment buffer instead of allocating per segment\n4410bb7 chore: drop support for Safari 15\nb77e910 fix(dvr): seeking past the live edge no longer stalls\n30cc219 docs: correct the events table\n\nintegrators are web developers; breaking changes need to be obvious and there is one", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "auditor's question list arrived, and answering it well is basically writing the doc we never wrote:\n\n1. How are journal entries prevented from being modified after posting?\n2. Which roles can post to a closed period, and how is that recorded?\n3. Describe the numbering scheme for journals and how gaps are prevented.\n4. How are foreign currency rates sourced, stored and evidenced?\n5. What is the retention period for the audit trail, and where is it stored?\n6. Can a user delete an attachment from a posted invoice?\n\nanswer each from the code, and write it as a controls document rather than a list of replies", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "runbook for a stuck live stream is currently a slack thread. what we actually do:\n\n- viewer reports a stall; first check is the packager session for that stream id in grafana\n- if `segment_lag_seconds` is above 12 the ingest side is behind, and that's the encoder's problem, not ours\n- if lag is fine but the playlist isn't advancing, the muxer goroutine is wedged; `lumenctl session restart ` recovers it in about 8 seconds with a visible glitch\n- never restart the whole packager pod during a live event, you take out every stream on that instance\n- if redis latency is above 5ms the playlist renders will queue and everything looks broken\n- after any restart, check the DVR window is intact before telling the customer it's fixed", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "o texto atual do aviso de descontinuação está mau e sai amanhã:\n\n\"A partir de 1 de Outubro a versão 3 da API de ingestão deixará de estar disponível. Os clientes devem migrar para a versão 4. A versão 4 tem várias diferenças. Contacte o suporte para mais informações.\"\n\nfactos: a v3 aceita segmentos até 30s, a v4 até 10s; a v3 usa a chave no caminho, a v4 usa um cabeçalho; a v4 exige o Content-MD5; existem 340 clientes na v3, dos quais 12 representam 80% do tráfego; a data limite é firme por causa do desligamento do CDN antigo\n\nreescreve o aviso e o email para os 12 clientes grandes", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "pt"} -{"prompt": "SDK's events table in the docs versus what the code emits. reconcile them into one correct table:\n\ndocs list: ready, play, pause, seeking, seeked, levelswitch, error, ended\ncode emits: ready, play, pause, seeking, seeked, levelSwitching, levelSwitched, error, fatalError, ended, rebufferStart, rebufferEnd, dvrWindowChanged\n\nnotes: `levelswitch` in the docs never existed; `error` is non-fatal and recoverable while `fatalError` tears down the player; `rebufferStart`/`rebufferEnd` were added in 4.1 and are what everyone actually wants for QoE metrics; `dvrWindowChanged` only fires on live streams", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "pasted-context", "lang": "en"} -{"prompt": "dotnet build warnings, treat-warnings-as-errors goes on next sprint:\n\n/src/Ledger.Posting/PostingService.cs(88,17): warning CS8602: Dereference of a possibly null reference.\n/src/Ledger.Posting/PostingService.cs(212,9): warning CS4014: Because this call is not awaited, execution of the current method continues before the call is completed.\n/src/Ledger.Domain/Money.cs(41,26): warning CS0659: 'Money' overrides Object.Equals(object o) but does not override Object.GetHashCode()\n/src/Ledger.Api/Controllers/InvoicesController.cs(66,13): warning CS0168: The variable 'ex' is declared but never used\n/src/Ledger.Infrastructure/RateProvider.cs(22,32): warning CS8618: Non-nullable property 'Client' must contain a non-null value when exiting constructor\n\n5 warnings, and CS4014 in a posting service is the one keeping me awake", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "npm audit on the extension, and the store review is on friday:\n\n# npm audit report\n\nesbuild <=0.24.2\nModerate: esbuild enables any website to send requests to the development server\nfix available via `npm audit fix --force`\nWill install esbuild@0.25.9, which is a breaking change\n\nws 8.0.0 - 8.17.0\nHigh: ws affected by a DoS when handling a request with many HTTP headers\nfix available via `npm audit fix`\n\nzod 3.22.0 - 3.23.7\nLow: inefficient regular expression complexity\nfix available via `npm audit fix`\n\n3 vulnerabilities (1 low, 1 moderate, 1 high)\n\nesbuild is a devDependency, ws is used by the dev server only, zod ships in the bundle", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"} -{"prompt": "nginx config for the origin, someone noticed this while debugging the herd:\n\nproxy_cache_path /var/cache/nginx/segments levels=1:2 keys_zone=segments:100m max_size=200g inactive=24h;\n\nupstream packager {\n server packager-0.packager:8080 max_fails=3 fail_timeout=10s;\n server packager-1.packager:8080 max_fails=3 fail_timeout=10s;\n keepalive 64;\n}\n\nlocation ~ \\.m3u8$ {\n proxy_pass http://packager;\n proxy_cache off;\n proxy_read_timeout 5s;\n add_header Cache-Control \"max-age=600\";\n add_header X-Cache-Status $upstream_cache_status;\n}\n\nlocation ~ \\.ts$ {\n proxy_pass http://packager;\n proxy_cache segments;\n proxy_cache_valid 200 1d;\n proxy_cache_lock on;\n proxy_cache_lock_timeout 5s;\n proxy_cache_use_stale updating error timeout;\n add_header Cache-Control \"public, max-age=86400, immutable\";\n add_header X-Cache-Status $upstream_cache_status;\n}\n\nthe playlist location has no proxy_cache_lock, no upstream caching at all, and a 5 second read timeout that the packager occasionally exceeds under load", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"} -{"prompt": "github actions matrix for the .NET service, and the windows leg has been broken for a month:\n\nstrategy:\n matrix:\n os: [ubuntu-latest, windows-latest]\n dotnet: ['8.0.x', '9.0.x']\nsteps:\n - uses: actions/setup-dotnet@v4\n with: { dotnet-version: ${{ matrix.dotnet }} }\n - run: dotnet test --logger trx --collect:\"XPlat Code Coverage\"\n\nfailure on windows:\n error MSB4019: The imported project \"C:\\Program Files\\dotnet\\sdk\\9.0.100\\Sdks\\Microsoft.NET.Sdk\\Sdk.props\" was not found\n error NU1101: Unable to find package Ledger.Testing.Fixtures\n\nnobody deploys to windows and nobody has fixed it either", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"} -{"prompt": "两个环境的转码参数不一样，线上的画质投诉可能就是这个原因：\n\n# staging/transcode.yaml\ntranscode:\n preset: slow\n crf: 21\n keyint: 48\n min_keyint: 48\n scenecut: 40\n bframes: 3\n audio_codec: aac\n audio_bitrate: 192k\n ladder: [240p, 480p, 720p, 1080p]\n two_pass: true\n\n# production/transcode.yaml\ntranscode:\n preset: veryfast\n crf: 26\n keyint: 250\n min_keyint: 25\n scenecut: 0\n bframes: 0\n audio_codec: aac\n audio_bitrate: 96k\n ladder: [240p, 480p, 720p, 1080p]\n two_pass: false\n\n# 相关指标（过去 7 天）\n 平均转码时长/分钟素材：staging 44s，production 11s\n 画质投诉工单：本月 38 件，去年同期 4 件\n 出网流量：同比 -22%\n\n线上是去年为了赶一个活动临时改的，之后就没人动过，也没有人记得当时的取舍", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "zh"} -{"prompt": "feature flag defaults across our three services, one of these is not like the others:\n\n# packager/config/flags.yaml\nflags:\n buffer_aware_abr: true\n redis_playlists: false\n dvr_enabled: true\n multi_cdn_selection: false\n segment_reuse_buffer: true\n\n# api/config/flags.yaml\nflags:\n buffer_aware_abr: true\n redis_playlists: true\n dvr_enabled: true\n multi_cdn_selection: false\n segment_reuse_buffer: true\n\n# player-config service — what clients actually receive\nflags:\n buffer_aware_abr: false\n redis_playlists: false\n dvr_enabled: true\n multi_cdn_selection: false\n segment_reuse_buffer: false\n\n# experiment dashboard, week 3\n rebuffer ratio, control: 1.82%\n rebuffer ratio, treatment: 1.81%\n sessions in treatment: 412,118\n\nwe've been measuring the ABR change for three weeks and wondering why the numbers didn't move", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "pasted-context", "lang": "en"} -{"prompt": "same currency conversion appears in five services with four different rounding behaviours. one implementation, please:\n\n// billing\nvar converted = Math.Round(amount * rate, 2, MidpointRounding.AwayFromZero);\n\n// reporting\nvar converted = decimal.Round(amount * rate, 2);\n\n// api\nvar converted = (decimal)Math.Round((double)(amount * rate), 2);\n\n// export\nvar converted = Math.Floor(amount * rate * 100) / 100;\n\n// legacy\nvar converted = amount * rate; // rounded at render time, sometimes\n\nthe billing one is the behaviour the auditors signed off on", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "this session manager holds four responsibilities and a mutex. i want the same behaviour, decomposed:\n\ntype Manager struct {\n\tmu sync.Mutex\n\tsessions map[string]*Session\n\tmuxers map[string]*Muxer\n\tplaylists map[string]*Playlist\n\tuploads map[string]*Uploader\n\tmetrics *Metrics\n}\n\nfunc (m *Manager) Start(id string) error {\n\t// creates the session, muxer, playlist and uploader\n\t// starts a goroutine per session that watches for segments\n\t// updates metrics inline\n\t// on error, tears down whichever of the four were created\n}\n\nfunc (m *Manager) Stop(id string) error { /* the reverse, holding mu the whole time */ }\n\nStop holds the mutex while waiting for goroutines to finish, which is why a slow upload blocks every other stream", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "controller does validation, mapping, business logic and persistence. same API contract, better shape:\n\n[HttpPost]\npublic async Task Post(InvoiceRequest req)\n{\n if (req.Lines == null || req.Lines.Count == 0) return BadRequest(\"lines required\");\n if (req.Lines.Any(l => l.Quantity <= 0)) return BadRequest(\"quantity must be positive\");\n var customer = await _db.Customers.FindAsync(req.CustomerId);\n if (customer == null) return NotFound();\n var invoice = new Invoice { CustomerId = customer.Id, IssuedAt = DateTime.UtcNow };\n foreach (var l in req.Lines)\n {\n var net = l.Quantity * l.UnitPrice;\n var vat = RoundVat(net, TaxTable.RateFor(customer.Country, l.TaxCode));\n invoice.Lines.Add(new InvoiceLine { Net = net, Vat = vat, ... });\n }\n invoice.Total = invoice.Lines.Sum(x => x.Net + x.Vat);\n _db.Invoices.Add(invoice);\n await _db.SaveChangesAsync();\n await _mail.SendInvoiceAsync(invoice);\n return CreatedAtAction(nameof(Get), new { id = invoice.Id }, InvoiceDto.From(invoice));\n}", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "quatre variantes du même calcul de prorata dans le code de facturation :\n\n// subscriptions/proration.cs\nvar days = (end - start).Days;\nvar factor = (decimal)days / DateTime.DaysInMonth(start.Year, start.Month);\n\n// billing/upgrade.cs\nvar factor = (decimal)(end - start).TotalDays / 30m;\n\n// api/preview.cs\nvar factor = (decimal)(end - start).Days / (decimal)(cycleEnd - cycleStart).Days;\n\n// legacy/prorate.cs\nvar factor = Math.Round((decimal)(end - start).Days / 30.4375m, 4);\n\ncelle de subscriptions est celle que la finance considère correcte", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "fr"} -{"prompt": "quarterly input from the business, and i need to turn it into something sequenced:\n\n- a broadcaster wants live DVR with a 12-hour window, currently we do 2 hours\n- finance wants us off the legacy billing service by december, it's the last thing on the old database\n- the player SDK has to support the new codec by Q1 or we lose a deal\n- support says the top three tickets are all about the extension's sign-in loop\n- the packager rewrite is half done and blocked on a decision about redis\n- one backend engineer leaves in september, the replacement starts in november\n- we have a CDN contract renewal in october that changes our cost model per GB", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "ticket that needs a plan rather than an implementation:\n\nLMN-812 — Multi-CDN delivery\nWe currently deliver from a single CDN. Contract renewal in October gives us an opportunity to go multi-CDN, and one large customer has asked for it explicitly after our June incident. Requirements as understood: per-session CDN selection, ability to shift traffic during an incident within minutes, consistent QoE measurement across providers, and no change to how customers embed the player. Unknowns: token authentication differs between the two candidate providers, cache warming would double our origin egress, and our QoE metrics are currently derived from one provider's logs.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "design handoff for the clip editor in the extension popup, build it:\n\nClip editor (popup, 400x600)\n- Video preview at the top, 16:9, poster from the captured frame, no controls beyond play/pause.\n- Trim bar under the preview: 48px tall, waveform if we have audio, two draggable handles, current position as a 2px line. Handles snap to 0.1s and show a time label while dragging.\n- Title field: single line, autofocused, character counter at 80, error state past 100.\n- Tag input: chips with an X, autocomplete from the user's recent tags, enter or comma commits.\n- Footer: \"Save clip\" primary, \"Discard\" text button, both disabled while uploading, with a determinate progress bar replacing the footer during upload.\n- Offline: the editor still works, the save button says \"Save for later\" and the clip queues.\n- Keyboard: space toggles playback, arrow keys nudge the nearest handle by 0.1s, shift+arrow by 1s.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "UI-Abnahme für die Rechnungsansicht, bitte umsetzen:\n\nRechnungsansicht (Desktop, ab 1280px)\n- Kopfbereich: Rechnungsnummer (20px, halbfett), Status-Badge rechts daneben (Entwurf / Gebucht / Storniert / Überfällig).\n- Zwei Spalten: links Rechnungsempfänger, rechts Datum, Fälligkeit, Zahlungsbedingungen. Beschriftungen 12px grau, Werte 14px.\n- Positionstabelle: Menge rechtsbündig, Einzelpreis rechtsbündig, Steuersatz zentriert, Betrag rechtsbündig und fett. Zeilenhöhe 40px.\n- Summenblock rechts unten: Netto, Steuer je Satz einzeln aufgeführt, Brutto in 18px halbfett.\n- Bei stornierten Rechnungen liegt ein diagonales Wasserzeichen über der Tabelle, die Werte bleiben lesbar.\n- Aktionen oben rechts: Buchen, PDF, Stornieren. Buchen ist deaktiviert, wenn die Periode geschlossen ist, mit Tooltip.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "de"} -{"prompt": "accessibility report for the player's controls, from a customer's audit:\n\n- The play/pause button toggles its icon but not its accessible name, so it always announces \"play\".\n- The seek bar is a div with mouse handlers; keyboard users cannot seek at all.\n- Volume is a custom slider with no role, no aria-valuenow, and no keyboard support.\n- The captions menu opens on hover only and is unreachable by keyboard.\n- Focus is never visible on any control; the outline is removed globally in the SDK's stylesheet.\n- The live indicator conveys state with a red dot and no text.\n- When an error occurs, the message appears visually but is not announced.\n\nour SDK ships these controls to every customer, so whatever we do here lands everywhere", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "partner integration spec that we have to implement on our side:\n\nPOST /v1/webhooks/tax-filing\n they call us when a filing is accepted or rejected by the tax authority\n headers: X-Filing-Signature (HMAC-SHA512 over the raw body with a shared secret, hex, lowercase)\n body: { filing_id, period, status: \"accepted\"|\"rejected\"|\"partially_accepted\", messages: [{code, severity, text}], received_at }\n we must respond 200 within 5 seconds; they retry for 72 hours with exponential backoff\n a rejected filing must move the period back to open and notify the finance team\n partially_accepted means some documents were rejected; those ids come in messages with severity=error\n duplicate deliveries are expected and must be idempotent on filing_id + status\n their sandbox signs with a different secret and sends `X-Filing-Environment: sandbox`", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "schema we agreed for stream credentials, now it needs building:\n\nCREATE TABLE stream_keys (\n id uuid PRIMARY KEY,\n tenant_id uuid NOT NULL,\n stream_id uuid NOT NULL REFERENCES streams(id) ON DELETE CASCADE,\n key_hash bytea NOT NULL,\n prefix text NOT NULL,\n created_at timestamptz NOT NULL DEFAULT now(),\n expires_at timestamptz,\n revoked_at timestamptz,\n last_used_at timestamptz,\n UNIQUE (stream_id, prefix)\n);\n\nkeys are shown once at creation, validated on every ingest request (about 400/s at peak), rotate without interrupting an in-flight stream, and the ingest path must not do a database round trip per segment", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "crf back to 21 in prod", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "zod bump before store review", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "core", "lang": "en"} -{"prompt": "drop the windows leg from CI", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "`buffer_aware_abr` is false in player-config", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "remove the `cookies` permission from the manifest", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "GetHashCode missing on Money", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "proxy_cache_lock on the playlist location", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "das Sync-Intervall der Extension auf 60s", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "de"} -{"prompt": "unawaited task in PostingService", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "waveform under the trim bar", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "focus outlines are removed globally", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "cancelled invoices need a watermark", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "popup is blank when the fetch fails", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "a short decision note about why we're keeping the DVR window in S3 rather than memory", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "our stream key validation is described in the design doc as a constant-time comparison against a hash, and i'd like that verified rather than believed, along with what the ingest path does when the cache is cold and whether a revoked key can still be used by an in-flight session for some window", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "the dunning schedule is 3, 7 and 14 days in the code and 3, 7 and 10 on the customer-facing pricing page, and support has been quoting whichever they saw last. work out which one finance actually agreed, change the other, and check whether any in-flight dunning runs would shift as a result", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "清晰度切换的菜单太窄了", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "zh"} -{"prompt": "seek bar can't be used with a keyboard", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "trim handles don't snap on touch", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "`Manager.Stop` shouldn't hold the mutex", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "pull the VAT maths out of the controller", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "`levelSwitching` naming across the SDK", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "InvoiceBuilder everywhere in the tests", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "inline the one-line `RateFor` wrapper", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "split the packager's session watcher", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "release notes for player SDK 4.3", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "nota interna sobre el cierre de periodo", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "es"} -{"prompt": "document what `X-Discontinuity` does", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "summarise the DVR design for the team", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "PR description for the ABR change", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "welche Berechtigungen braucht die Extension wirklich?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "de"} -{"prompt": "can the uploader retry a consumed pipe?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "walk me through the dunning schedule", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "credit notes are a cent off", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "clips upload twice after a worker restart", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "la revalorización nocturna no postea CHF", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "es"} -{"prompt": "signed playback URLs, one hour expiry", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "scope the multi-CDN work, then start on selection", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "map the legacy billing exit, then take the first slice", "purpose": "planning", "secondary": "refactor", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "carry on from friday", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "crisper", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "vague-eval", "lang": "en"} -{"prompt": "make it not embarrassing", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "weiter mit dem Player", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "de"} -{"prompt": "sort the extension out", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "do what makes sense here", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "pick this back up please", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "月末のあれ、進めておいて", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "ja"} -{"prompt": "rest of the ticket", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "start on the next bit", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "packager rewrite is half finished and stalled on whether playlists live in redis, which nobody wants to decide because it makes redis a hard dependency on the live path. lay out the options properly — stateless with redis, sharded by stream id with consistent hashing, or leaving it as it is and scaling vertically — with what each costs us operationally at three thousand concurrent streams rather than three hundred", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "finance wants us off the legacy billing service by december and it still owns recurring invoicing, dunning, revenue recognition, the tax export and the PDF generator, plus two hundred stored procedures of which maybe forty are live. i need a sequenced exit plan that keeps invoicing running every month it's being migrated, with an honest view of what we should refuse to port and simply rebuild instead", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "CDN contract renews in october and the cost model changes per gigabyte, which makes the multi-CDN question urgent rather than theoretical. i'd like to understand what per-session CDN selection would require of us — token differences between providers, cache warming doubling origin egress, and the fact that our QoE numbers currently come from one provider's logs — before we negotiate anything", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "extension, our player SDK and our web app all reimplement session handling because they were written by different people in different years, and the sign-in loop bug exists in two of them. before touching any code i want a view on whether these should share a package, what that package would own, and whether the browser constraints make it impossible in practice", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "close process takes finance four to six days and the wiki page describing it is three years out of date, which means new joiners learn it by shadowing someone in a bad mood. write the current process properly, in order, with who does what, and flag clearly the two steps that are broken processes rather than missing documentation", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "we're deprecating v3 of the ingest API on the first of october and the current notice is four sentences that tell customers nothing actionable. write the replacement: what changes concretely, what a migrating customer has to do, why the date is firm, and a separate shorter email for the twelve customers who account for most of the traffic", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "transcode ladder and encoder settings differ between staging and production because of a rush change last year, which is probably why we get quality complaints that we can never reproduce internally. before changing anything, read both configs and the ladder logic and tell me what each difference actually does to output quality and cost", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "ADR proposing a stateless packager argues that sharding by stream id is \"operationally complex\" and moves on, which feels like the interesting option being waved away. read the ADR against the code and tell me whether its consequences section is honest, particularly about rendering playlists on every request instead of once per segment", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "VAT rounding helper defaults to half-up on the raw product, and credit notes pass a negative net through it, which the German rules we're being assessed against apparently handle differently. i want to understand exactly what the current code does with negative amounts before we decide whether the audit finding is right", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "packager's session manager holds one mutex across creation, teardown and metrics, and Stop waits for goroutines while holding it, which is why one slow upload stalls every other stream on the instance. decompose it so the lifecycle, the muxing and the uploading are separable, with the same externally observable behaviour and no new races", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "currency conversion exists five times across our services with four different rounding behaviours, and only the billing one has been signed off by the auditors. consolidate onto that behaviour, update every caller, and where a service's numbers will change as a result, list exactly which reports are affected so finance hears it from us first", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "invoices controller does validation, mapping, tax calculation, persistence and email in one method, and the tax part is the bit that's actually subtle. pull it apart without changing the API contract or the emails anyone receives, and make the tax calculation testable on its own because that's where the audit findings keep landing", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "internal console, the customer portal and the extension popup each have their own copy of the clip list rendering, and they've drifted enough that the same clip shows three different durations. work out which one is right, unify them behind a shared component, and keep each surface's styling as it is today", "purpose": "refactor", "secondary": "frontendImpl", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "playback stalls for about four percent of sessions on one edge, that edge reports perfect availability, and our own telemetry shows the player dropping two levels and still timing out. i don't know whether to look at the CDN, the ABR logic or our segment sizes, and i'd like someone to work through it properly rather than guess", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "month-end didn't tie out by three fifty, and the difference traces to a rounding line that appears once in the subledger and twice in the general ledger, from two system journals posted two seconds either side of midnight. work out how that duplicate arises before we adjust anything, because finance will ask whether it's happened before", "purpose": "debugging", "secondary": "review", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "QoE dashboard has a hardcoded rebuffer threshold, four tiles with no comparison to the previous period, and a breakdown table that can't be sorted, which is why the SRE team still uses a spreadsheet. bring it up to the spec they wrote, and make the threshold configurable per environment rather than baked into the bundle", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "before we build multi-CDN i want the selection strategy designed — how a session picks an edge, how we shift traffic during an incident, how QoE is measured consistently across providers — and then the selection service itself stood up behind a flag so we can shadow it against real traffic", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.9, "slice": "mixed", "lang": "en"} -{"prompt": "ledger project needs breaking up and i'd rather agree the module boundaries with you first, then have you actually move the first module — posting, probably — so we can see whether the boundary survives contact with the build", "purpose": "planning", "secondary": "refactor", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "les règles de cache du CDN sont incohérentes entre le direct et le VOD, et l'origine en souffre. j'aimerais d'abord une vraie stratégie de cache écrite noir sur blanc, puis la mise à jour de la configuration en conséquence", "purpose": "planning", "secondary": "quickFix", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "fr"} -{"prompt": "tax filing webhook needs building and there are decisions in it we haven't made — what a rejected filing does to a closed period, who gets notified, whether partially accepted reopens anything. decide those with me, write them down, then implement the handler", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "support answers the same six extension questions every week from a slack thread that scrolls away. write the troubleshooting page properly, and while you're in it, give the popup an actual error state instead of rendering blank when the clip list fails", "purpose": "writing", "secondary": "frontendImpl", "mixed": true, "difficulty": 0.5, "slice": "mixed", "lang": "en"} -{"prompt": "live-stream runbook lives in one engineer's memory and a slack thread. write it as a proper page, and confirm from the code whether `lumenctl session restart` really is safe mid-event or whether that's folklore", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.55, "slice": "mixed", "lang": "en"} -{"prompt": "escribe la documentación del nuevo modelo de facturación recurrente para los clientes, y comprueba en el código si el prorrateo se calcula realmente por días naturales como decimos", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "es"} -{"prompt": "player SDK has three subscription styles that have to keep working, and only one of them returns an unsubscribe function. unify the internals behind one mechanism, then document which style we recommend and what the others do differently", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "test project builds invoices three different ways and only the builder computes VAT like production does. move everything onto the builder, then write the short note on test data conventions so the next person doesn't add a fourth", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.5, "slice": "mixed", "lang": "en"} -{"prompt": "deadlock in the posting service happens twice a week and everyone has a theory. i want an actual diagnosis from the deadlock graph and the code, and then the ordering fixed so it can't recur", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": ".NET solution has three projects that all define a `Money` type, and the conversions between them are implicit", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "extension's storage layer mixes chrome.storage.local, sync and an indexeddb wrapper with no rule about which goes where", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "rename the `Trip`-era types in the packager, they date from before we called them streams", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "config is read from appsettings, environment variables and a database table, with different precedence per service", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "SDK exports 40 symbols from its index and most of them are internal helpers nobody should import", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "i'd like to understand how period locking actually prevents postings, because system journals seem to ignore it", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "someone should look at whether our ABR change can get stuck at a low level once it drops, given it only steps one at a time", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "why does the extension's service worker restart mid-sync, and is our alarm interval the reason", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "could you explain what our cache key configuration does with the Authorization header on the catch-all rule", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "is it expected that our playlist requests bypass the upstream cache entirely, or has someone misread the nginx config", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "what does the packager actually do when redis is slow — does it queue, drop, or block the live path", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "docs/ingest.md still documents the 30 second segment limit that we lowered to 10 in v4", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "内部向けに、配信の障害対応フローを一枚にまとめてほしい", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "ja"} -{"prompt": "xml docs on the posting service describe atomicity guarantees that the code doesn't provide", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "write the store listing description for the extension, the current one is a feature list nobody reads", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "health check on the packager returns healthy while every session is wedged, which is how the outage lasted an hour", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "dunning emails go out at 3, 7 and 14 days in code but the customer-facing page says 3, 7 and 10", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "segment upload retries have no jitter, so a CDN blip produces a perfectly synchronised retry storm", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "发票导出的 CSV 用的是逗号分隔，德国客户打开全是乱的，能不能按区域设置切换", "purpose": "quickFix", "secondary": "backendImpl", "mixed": true, "difficulty": 0.4, "slice": "mixed", "lang": "zh"} -{"prompt": "live edge drifts about two seconds later every hour on long streams, and restarting the session resets it", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "one customer's invoices occasionally get two numbers, and it correlates with them clicking post twice quickly", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "how should we structure the SDK's public surface now that we support three subscription styles and can't break any of them", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "what's the right approach to storing tax rates that change by jurisdiction and date, given we currently hardcode a table", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "an endpoint that returns the DVR window's start and end for a live stream, cheap enough for the player to poll", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "period locking needs to apply to system journals too, with an explicit override that records who used it", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "a job that expires stream keys that haven't been used in ninety days, with a warning email a week before", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "ingest path should validate stream keys from a cache rather than the database on every segment", "purpose": "backendImpl", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "clip uploads need resumable support, because the extension's worker dies every thirty seconds of idle", "purpose": "backendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "anything that stops the pager going off", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "doc, finish it off", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "quality menu is too narrow", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "invoice list renders every row's tax breakdown eagerly, which on a month with four thousand invoices means the page takes eight seconds to become interactive and finance has started exporting to excel instead. virtualise the table, keep the column layout and the sticky totals row exactly as they are, and make sure the print stylesheet still produces the full list", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "player's controls fail almost every item in a customer's accessibility audit — no accessible name on the play toggle, a seek bar that's a div with mouse handlers, a volume slider with no role, and focus outlines removed globally in our stylesheet. this ships to every customer, so fix it properly and tell me which parts of the design will visibly change", "purpose": "frontendImpl", "secondary": "writing", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "nobody can tell me what happens to a live session when the packager loses its redis connection for ten seconds — whether playlists go stale, the muxer blocks, or viewers see an error — and the code paths for it are spread across three files. work through it and give me the actual behaviour, including what the viewer experiences at each stage", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "stream keys are in the ingest request path, which means they land in access logs, referrer headers and any proxy in between, and security noticed this morning. move them to a header for v4, keep the path form working until october's deprecation, and scrub the existing logs' retention as far as we're able", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "the changelog for the ingest API has no entry for the stream key moving from the path to a header, which is the most disruptive change we've made in two years. write it, plus the migration note explaining what a client has to change and how to tell whether they're still on the old form", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "we need the ingest path to validate stream keys without a database round trip per segment, which at four hundred segments a second is currently a meaningful share of our database load. cache the validated keys with a sensible invalidation on revoke, and make sure a revoked key stops working within seconds rather than whenever the cache happens to expire", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "our tax rate table is hardcoded per country in a static class, which was fine when we sold in three countries and is now the reason every rate change is a deploy. i'd like the approach agreed first — effective-dated rows, jurisdiction hierarchy, where the source of truth lives — and then the schema and loader built", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} +{"prompt":"Corrige le timeout de EquinoxBasilRunnerService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"fr"} +{"prompt":"// projects/equinox/cmd/exporter/main.py\nfinal class EquinoxDriftConsoleFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 EquinoxDriftConsoleFlow'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":"Ticket OPS-45111: retire the legacy replay path for EquinoxNimbusFormFlow\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 EquinoxNimbusFormFlow for durability, tenant isolation, races, and misleading observability. Separate blockers from questions and do not produce a patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"A copied hex color in EquinoxAcornWidgetStore lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Two deliverables are holding up EquinoxCinderAuthCoordinator. First, assess ownership and failure handling in projects/equinox/workers/thumbnail/consumer.ex. In the same workstream, capture the contract and rollback note for consumers. The relevant starting point is projects/equinox/workers/thumbnail/consumer.ex, which follows PostgreSQL 17 conventions and currently suffers from timestamps rendered one day ahead near UTC midnight. Preserve cancellation and back-pressure semantics.\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":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Incident timeline — INC-45115\n\n08:02 deploy EquinoxCinderAuthFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current EquinoxCinderAuthFlow 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":"Background: # projects/equinox/pkg/cache/lease.rs\n[worker.equinoxravensessionflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.equinoxravensessionflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.equinoxravensessionflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.EquinoxRavenSessionFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-45112\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/equinox/pkg/cache/lease.rs. 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":"EquinoxCedarPolicyCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Does EquinoxWrenExportStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"EquinoxBeaconStoreCoordinator: polish the last piece","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Question: Incident timeline — INC-45119\n\n08:02 deploy EquinoxBasilRunnerFlow 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 EquinoxBasilRunnerFlow release note and operator runbook section. State impact, detection, rollback, and the client-visible contract; do not modify code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} +{"prompt":"Design handed over a final pass for EquinoxCinderAuthStore, and the basic data flow in projects/equinox/workers/thumbnail/consumer.ex already works. 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- preserve cancellation and back-pressure semantics\n- stay compatible with the existing PostgreSQL 17 deployment\n- keep the work scoped to EquinoxCinderAuthStore and its direct tests\n\nSeveral teams work in this identity, Rust CLI, Vue 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":"A flaky failure around EquinoxMoonlitSDKService survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxMoonlitSDKService\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Em projects/equinox/workers/thumbnail/consumer.ex, o EquinoxCoralUploadStore tem um problema intermitente no fluxo de PostgreSQL 17. Separe responsabilidades e remova duplicação sem mudar API, wire values, ordem ou comportamento observável.\n\nRestrições:\n- continuar com PostgreSQL 17\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao EquinoxCoralUploadStore","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"pt"} +{"prompt":"Please resist widening this one: EquinoxCraneWorkspaceService works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxCraneWorkspaceService\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Observation: Two deliverables are holding up EquinoxRavenSessionCoordinator. First, assess ownership and failure handling in projects/equinox/crates/index/src/segment.rs. In the same workstream, capture the contract and rollback note for consumers. The relevant starting point is projects/equinox/crates/index/src/segment.rs, which follows WebGPU conventions and currently suffers from an empty state that flashes before cached data arrives. Preserve cancellation and back-pressure semantics.\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":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"EquinoxNovaPickerFlow 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.4,"slice":"core","lang":"en"} +{"prompt":"On compact widths, EquinoxSlateEditorService'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.4,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-45130: retire the legacy replay path for EquinoxAtlasSearchFlow\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 EquinoxAtlasSearchFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Extract EquinoxIrisBatchService's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Check EquinoxEmberRelayStore's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"projects/equinox/infra/modules/edge/main.tf now contains EquinoxPrismCacheFlow'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":"Constraint: Ticket OPS-45144: retire the legacy replay path for EquinoxPineMetricsFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for EquinoxPineMetricsFlow, 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":"Pin EquinoxDriftConsoleService's SQLite dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"EquinoxFernSnapshotCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"EquinoxEchoRegistryStore leaks tasks on shutdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"Compare the old and new EquinoxCedarPolicyService adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"$ pnpm test --filter EquinoxJuniperCLIFlow\n RUN v3.2.4 /workspace/apps/console\n × EquinoxJuniperCLIFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=45143 phase=resume storedCursor=seg-0183\n session=45143 phase=fetch requestCursor=seg-0183 pageSize=200\n session=45143 phase=commit receivedCursor=seg-0184 itemCount=0\n session=45143 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nDetermine why EquinoxJuniperCLIFlow 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":"Ownership of EquinoxPrismCacheService is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current NATS JetStream operational envelope\n\nThe relevant code crosses identity, Rust CLI, Vue. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"EquinoxAcornWidgetCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"EquinoxWillowCodecCoordinator: document, then correct","purpose":"writing","secondary":"debugging","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Request: projects/equinox/services/ledger/replay.go の EquinoxCraneWorkspaceFlow で、NATS JetStream の flow に断続的な問題が起きています。 consumer 向けに contract、error、retry、コピー可能な例を含む文書を書き、handler は変更しないでください。\n\n制約:\n- NATS JetStream を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は EquinoxCraneWorkspaceFlow のみ","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"ja"} +{"prompt":"Goal: A flaky failure around EquinoxBirchMigratorStore survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxBirchMigratorStore\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Symptom: // projects/equinox/ml/pipeline/features.py\nfinal class EquinoxFlintTimelineFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Restructure EquinoxFlintTimelineFlow 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":"EquinoxRainfallDBService's staging timeout is already known to be wrong: change the single projects/equinox/infra/modules/edge/main.tf value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Milestones for replacing EquinoxSpruceDaemonService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"EquinoxMapleQueueCoordinator needs a paired pass: lay out a staged migration for EquinoxMapleQueueCoordinator, plus also add the visible loading and offline states. Use projects/equinox/db/migrations/20260730_events.sql as the source of truth, preserve the Tokio contract, and avoid unrelated cleanup.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Headsup: // projects/equinox/db/migrations/20260730_events.sql\nfinal class EquinoxNovaPickerCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 EquinoxNovaPickerCoordinator; 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":"Incident timeline — INC-45121\n\n08:02 deploy EquinoxWillowCodecFlow 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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Find the source of this EquinoxWillowCodecFlow symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Before we approve EquinoxBeaconStoreStore, assess whether lost focus when the drawer animation finishes is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"EquinoxDriftConsoleCoordinator: correct, then document","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"FYI: // projects/equinox/src/sync/reconcile.ts\nfinal class EquinoxMapleQueueFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 EquinoxMapleQueueFlow; 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":"The behavior of EquinoxGarnetModalService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/equinox/app/src/main/SyncWorker.kt. 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- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current Tokio operational envelope\n\nThe relevant code crosses identity, Rust CLI, Vue. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"EquinoxSlateEditorCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Test Suite 'EquinoxTideWorkerCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[EquinoxTideWorkerCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/equinox/pkg/cache/lease.rs:144: error: -[EquinoxTideWorkerCoordinatorTests 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 '-[EquinoxTideWorkerCoordinatorTests 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\nFinish the visible EquinoxTideWorkerCoordinator 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":"Document EquinoxCinderAuthService's cancellation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Two asks around EquinoxAmberFilterCoordinator: (1) finish EquinoxAmberFilterCoordinator's responsive empty and retry states; (2) capture the contract and rollback note for consumers. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"diff --git a/projects/equinox/infra/modules/edge/main.tf b/projects/equinox/infra/modules/edge/main.tf\nindex 62d71aa..90f3c1e 100644\n--- a/projects/equinox/infra/modules/edge/main.tf\n+++ b/projects/equinox/infra/modules/edge/main.tf\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure EquinoxRainfallDBFlow 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":"Meanwhile: Two engineers disagree about whether EquinoxHarborIndexStore's cache is authoritative. Walk the reads and writes in projects/equinox/packages/api/openapi.yaml and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"EquinoxQuartzPlayerCoordinator: ship a sensible version","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Locally: // projects/equinox/web/components/FilterDrawer.vue\nfinal class EquinoxCraneWorkspaceCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 EquinoxCraneWorkspaceCoordinator 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":"EquinoxPineMetricsCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Document EquinoxMosaicGridStore's cancellation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Rename EquinoxSummitProxyStore's staleLease state","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"EquinoxNimbusFormCoordinator is blocking the next release because out-of-order events after consumer rebalancing. I need two concrete outcomes from a single pass: finish EquinoxNimbusFormCoordinator's responsive empty and retry states, and capture the contract and rollback note for consumers. Use the existing NATS JetStream conventions in projects/equinox/services/ledger/replay.go; preserve cancellation and back-pressure semantics. 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":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"EquinoxAcornWidgetService's metric is misspelled as succesful_total in one declaration. Correct that literal and its exact test expectation, without renaming anything else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Architect a gradual ownership transfer for EquinoxOpalRouterFlow across two teams, including module seams, temporary interfaces, observability, handoff criteria, and rollback responsibility. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Collapse the EquinoxBirchMigratorService wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"# projects/equinox/internal/auth/refresh.go\n[worker.equinoxlumenchartflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.equinoxlumenchartflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.equinoxlumenchartflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.EquinoxLumenChartFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-45116\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/equinox/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":"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_45140'\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_45140'::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 EquinoxSlateEditorFlow 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":"Ticket OPS-45136: retire the legacy replay path for EquinoxWrenExportFlow\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 EquinoxWrenExportFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Set EquinoxMapleQueueStore's port to 8081","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Production: Ticket OPS-45128: retire the legacy replay path for EquinoxSummitProxyFlow\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 EquinoxSummitProxyFlow 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":"Production says EquinoxRavenSessionService is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. 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- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current WebGPU operational envelope\n\nThe relevant code crosses identity, Rust CLI, Vue. Prefer evidence from the repository and make any assumption explicit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Move EquinoxGarnetModalFlow'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.5,"slice":"core","lang":"en"} +{"prompt":"Security flagged EquinoxLumenChartStore for a read-only pass because its NATS JetStream boundary mixes tenant data, retries, and cancellation in subtle ways. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current NATS JetStream operational envelope\n\nThe relevant code crosses identity, Rust CLI, Vue. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"For EquinoxKiteSchedulerCoordinator, assess ownership and failure handling in projects/equinox/ui/settings/PrivacyPane.tsx; once that is complete, capture the contract and rollback note for consumers. Work from projects/equinox/ui/settings/PrivacyPane.tsx, stay with PostgreSQL 17, and preserve cancellation and back-pressure semantics. Keep the two outcomes separately reviewable.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"The next client release depends on a new EquinoxGarnetModalStore capability in projects/equinox/apps/console/routes/usage.svelte, with Tokio already chosen by the platform group. Wire the schema, repository, handler, and worker so duplicate deliveries return the original result and shutdown never acknowledges uncommitted work.\n\nConstraints:\n- preserve cancellation and back-pressure semantics\n- stay compatible with the existing Tokio deployment\n- keep the work scoped to EquinoxGarnetModalStore and its direct tests\n\nSeveral teams work in this identity, Rust CLI, Vue monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Two asks around EquinoxMosaicGridCoordinator: (1) produce a consumer guide for EquinoxMosaicGridCoordinator; (2) give the existing implementation a read-only safety pass. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Pin EquinoxWillowCodecStore's NATS dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Staging: // projects/equinox/packages/api/openapi.yaml\nfinal class EquinoxSableParserCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 EquinoxSableParserCoordinator; 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":"CI: The API work is done; what remains for EquinoxSableParserService is the visible interaction layer across loading, offline, empty, and success cases. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxSableParserService\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Set EquinoxAmberFilterStore's port to 8081","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"PM is preparing the EquinoxDeltaCanvasStore rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxDeltaCanvasStore\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"# projects/equinox/pkg/cache/lease.rs\n[worker.equinoxamberfilterflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.equinoxamberfilterflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.equinoxamberfilterflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.EquinoxAmberFilterFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-45132\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 EquinoxAmberFilterFlow'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":"Please resist widening this one: EquinoxNovaPickerService works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxNovaPickerService\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"In projects/equinox/web/components/FilterDrawer.vue hat EquinoxNimbusFormService ein sporadisches Problem im NATS JetStream-Ablauf. Die Ursache ist klar: Ändere nur das Staging-Timeout von 15 auf 30 Sekunden und passe die Assertion an.\n\nRandbedingungen:\n- NATS JetStream weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf EquinoxNimbusFormService begrenzen","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"de"} +{"prompt":"Atlas: The public surface of EquinoxFlintTimelineService is frozen, but its internal ownership in projects/equinox/ml/pipeline/features.py is difficult to test and even harder to change safely. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxFlintTimelineService\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-45129: finish the compact EquinoxMosaicGridFlow filter experience\n\nRoute: /catalog/search\nSource: projects/equinox/app/src/main/SyncWorker.kt\nFramework: Tokio\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Use the UI evidence to complete EquinoxMosaicGridFlow'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":"thread 'tokio-runtime-worker' panicked at projects/equinox/apps/console/routes/usage.svelte:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: equinoxgarnetmodalcoordinator::scheduler::LeaseTask::flush\n at ./projects/equinox/apps/console/routes/usage.svelte:217:18\n 4: equinoxgarnetmodalcoordinator::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nReconstruct the EquinoxGarnetModalCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Match EquinoxEchoRegistryService's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Bring EquinoxFrostPanelService'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.5,"slice":"core","lang":"en"} +{"prompt":"Could EquinoxSlateEditorStore show the active PostgreSQL 17 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":"Why is EquinoxSummitProxyService stalling?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"EquinoxAtlasSearchStore leaks tasks on shutdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Ownership of EquinoxMoonlitSDKStore is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current PostgreSQL 17 operational envelope\n\nThe relevant code crosses identity, Rust CLI, Vue. Prefer evidence from the repository and make any assumption explicit.\n\nReturn the restructuring sequence and decision points, not the edits themselves.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-45150: retire the legacy replay path for EquinoxCloudReconcilerCoordinator\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for EquinoxCloudReconcilerCoordinator, 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":"Decouple EquinoxMapleQueueService's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/equinox/internal/auth/refresh.go b/projects/equinox/internal/auth/refresh.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/equinox/internal/auth/refresh.go\n+++ b/projects/equinox/internal/auth/refresh.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate EquinoxPrismCacheCoordinator'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":"A previously stable test around EquinoxNovaPickerStore now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"A previously stable test around EquinoxWrenExportService now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"EquinoxLumenChartCoordinator: diagnose, then correct","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Beacon: Ticket OPS-45134: retire the legacy replay path for EquinoxBeaconStoreFlow\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 EquinoxBeaconStoreFlow 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":"How does EquinoxCedarPolicyStore propagate cancellation through the PostgreSQL 17 boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Is EquinoxEmberRelayService safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"For EquinoxIrisBatchCoordinator, ship the idempotent EquinoxIrisBatchCoordinator replay endpoint; once that is complete, correct the known stale timeout beside it. Work from projects/equinox/services/ledger/replay.go, stay with NATS JetStream, and preserve cancellation and back-pressure semantics. Keep the two outcomes separately reviewable.","purpose":"backendImpl","secondary":"quickFix","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Could the reasoning behind EquinoxRainfallDBStore's NATS JetStream choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/equinox/Sources/App/SessionStore.swift b/projects/equinox/Sources/App/SessionStore.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/equinox/Sources/App/SessionStore.swift\n+++ b/projects/equinox/Sources/App/SessionStore.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit EquinoxSpruceDaemonFlow 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":"Split EquinoxWillowCodecService without behavior changes","purpose":"refactor","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 EquinoxMicaProfileStore design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside EquinoxMicaProfileStore\n- preserve cancellation and back-pressure semantics\n\nThis repository spans identity, Rust CLI, Vue; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"EquinoxCoralUploadCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Rename EquinoxMicaProfileService's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Unifie les validateurs de EquinoxMarbleTokenStore","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"fr"} +{"prompt":"EquinoxOrbitSyncCoordinator needs a paired pass: find the unknown cause of lease renewal code copied across three workers, plus give the existing implementation a read-only safety pass. Use projects/equinox/cmd/exporter/main.py as the source of truth, preserve the SQLite contract, and avoid unrelated cleanup.","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"The name pendingAck means two different things across EquinoxLedgerGateService's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"EquinoxBasilRunnerCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Skizziere die EquinoxBasilRunnerStore-Migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"de"} +{"prompt":"What is the safest way to split projects/equinox/app/src/main/SyncWorker.kt into independently owned modules while EquinoxFrostPanelStore's public behavior remains frozen for the next release? Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Cinder: Ticket OPS-45153: retire the legacy replay path for EquinoxOpalRouterCoordinator\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 を維持し、根拠と判断を明確にしてください。 Assess EquinoxOpalRouterCoordinator 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":"EquinoxMicaProfileCoordinator is blocking the next release because lost focus when the drawer animation finishes. I need two concrete outcomes from a single pass: lay out a staged migration for EquinoxMicaProfileCoordinator, and consolidate the duplicated normalization paths without changing behavior. Use the existing Tokio conventions in projects/equinox/src/sync/reconcile.ts; preserve cancellation and back-pressure semantics. 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.9,"slice":"mixed","lang":"en"} +{"prompt":"We need to move EquinoxBeaconStoreService from the legacy store to Tokio. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"// projects/equinox/config/staging.toml\nfinal class EquinoxMarbleTokenFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 EquinoxMarbleTokenFlow 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":"Delta: A copied hex color in EquinoxOspreyJobFlow lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-45114\n\n08:02 deploy EquinoxMicaProfileFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nReconstruct the EquinoxMicaProfileFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Ember: A copied hex color in EquinoxSableParserStore lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'EquinoxQuartzPlayerFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[EquinoxQuartzPlayerFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/equinox/Sources/App/SessionStore.swift:144: error: -[EquinoxQuartzPlayerFlowTests 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 '-[EquinoxQuartzPlayerFlowTests 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 EquinoxQuartzPlayerFlow'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":"EquinoxWrenExportCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Ticket OPS-45135: retire the legacy replay path for EquinoxCoralUploadFlow\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 EquinoxCoralUploadFlow 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":"Center the EquinoxSpruceDaemonStore modal","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Frost: diff --git a/projects/equinox/packages/api/openapi.yaml b/projects/equinox/packages/api/openapi.yaml\nindex 62d71aa..90f3c1e 100644\n--- a/projects/equinox/packages/api/openapi.yaml\n+++ b/projects/equinox/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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Read the artifact above as a skeptical reviewer. Is EquinoxAcornWidgetFlow'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":"EquinoxFrostPanelCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"EquinoxQuartzPlayerService 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":"Garnet: projects/equinox/db/migrations/20260730_events.sql now contains EquinoxPineMetricsStore'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":"Harbor: projects/equinox/crates/index/src/segment.rs has grown through several launches, and EquinoxTideWorkerService now mixes policy, transport, persistence, and metrics in one place. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- preserve cancellation and back-pressure semantics\n- stay compatible with the existing WebGPU deployment\n- keep the work scoped to EquinoxTideWorkerService and its direct tests\n\nSeveral teams work in this identity, Rust CLI, Vue 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":"Does EquinoxPrismCacheStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Spell EquinoxKiteSchedulerStore's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"EquinoxJuniperCLICoordinator: sort out the rough edge","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","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_45148'\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_45148'::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\nAdd the bounded EquinoxCopperBridgeFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Add a bounded EquinoxCloudReconcilerStore export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Since the last release, EquinoxOspreyJobService has shown timestamps rendered one day ahead near UTC midnight; nobody on the team can reproduce it reliably on a laptop. Reconstruct the failing timeline from logs and tests, identify which invariant first breaks, and distinguish causal signals from effects or cleanup noise.\n\nConstraints:\n- preserve cancellation and back-pressure semantics\n- stay compatible with the existing PostgreSQL 17 deployment\n- keep the work scoped to EquinoxOspreyJobService and its direct tests\n\nSeveral teams work in this identity, Rust CLI, Vue monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Release engineering needs a EquinoxCopperBridgeStore 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":"En projects/equinox/cmd/exporter/main.py, EquinoxOpalRouterService tiene un problema intermitente en el flujo de SQLite. Termina el layout responsive, estados vacío y retry, foco por teclado, dark mode y reduced motion.\n\nRestricciones:\n- seguir con SQLite\n- conservar compatibilidad y cancelación\n- limitar el cambio a EquinoxOpalRouterService","purpose":"frontendImpl","secondary":"debugging","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"es"} +{"prompt":"Give EquinoxOspreyJobStore'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.5,"slice":"core","lang":"en"} +{"prompt":"The next client release depends on a new EquinoxRavenSessionStore capability in projects/equinox/crates/index/src/segment.rs, with WebGPU already chosen by the platform group. Wire the schema, repository, handler, and worker so duplicate deliveries return the original result and shutdown never acknowledges uncommitted work.\n\nConstraints:\n- preserve cancellation and back-pressure semantics\n- stay compatible with the existing WebGPU deployment\n- keep the work scoped to EquinoxRavenSessionStore and its direct tests\n\nSeveral teams work in this identity, Rust CLI, Vue monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Support wants the behavior in projects/equinox/web/components/FilterDrawer.vue recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Test Suite 'EquinoxEmberRelayFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[EquinoxEmberRelayFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/equinox/lib/codec/frame.cc:144: error: -[EquinoxEmberRelayFlowTests 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 '-[EquinoxEmberRelayFlowTests 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 EquinoxEmberRelayFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":"debugging","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Iris: Test Suite 'EquinoxEchoRegistryFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[EquinoxEchoRegistryFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/equinox/crates/index/src/segment.rs:144: error: -[EquinoxEchoRegistryFlowTests 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 '-[EquinoxEchoRegistryFlowTests 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\nFinish the visible EquinoxEchoRegistryFlow 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":"Design the EquinoxOrbitSyncService rollback","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"EquinoxEmberRelayCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"# projects/equinox/services/ledger/replay.go\n[worker.equinoxfernsnapshotflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.equinoxfernsnapshotflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.equinoxfernsnapshotflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.EquinoxFernSnapshotFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-45141\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 EquinoxFernSnapshotFlow'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":"Could the reasoning behind EquinoxDeltaCanvasFlow's SQLite choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Flip EquinoxLumenChartService's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Ownership of EquinoxFlintTimelineStore is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current SQLite operational envelope\n\nThe relevant code crosses identity, Rust CLI, Vue. Prefer evidence from the repository and make any assumption explicit.\n\nReturn the restructuring sequence and decision points, not the edits themselves.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Add a bounded EquinoxLedgerGateStore export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Polish the EquinoxVelaDrawerService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"How does EquinoxFernSnapshotService propagate cancellation through the NATS JetStream boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Collapse the EquinoxIrisBatchStore wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"We expect EquinoxDeltaCanvasService to outgrow its current SQLite arrangement next quarter, but changing everything at once would be risky. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- preserve cancellation and back-pressure semantics\n- stay compatible with the existing SQLite deployment\n- keep the work scoped to EquinoxDeltaCanvasService and its direct tests\n\nSeveral teams work in this identity, Rust CLI, Vue monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Juniper: # projects/equinox/crates/index/src/segment.rs\n[worker.equinoxledgergateflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.equinoxledgergateflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.equinoxledgergateflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.EquinoxLedgerGateFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-45142\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/equinox/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":"Kestrel: We need to move EquinoxTideWorkerStore from the legacy store to WebGPU. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Responsive layout for EquinoxOrbitSyncStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-45149\n\n08:02 deploy EquinoxAsterWebhookFlow 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 EquinoxAsterWebhookFlow 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":"EquinoxMarbleTokenCoordinator needs a paired pass: produce a consumer guide for EquinoxMarbleTokenCoordinator, plus correct the known stale timeout beside it. Use projects/equinox/packages/api/openapi.yaml as the source of truth, preserve the WebGPU contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Lumen: Incident timeline — INC-45155\n\n08:02 deploy EquinoxOspreyJobCoordinator 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 EquinoxOspreyJobCoordinator migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Wire a EquinoxOpalRouterStore background task in projects/equinox/ml/pipeline/features.py that expires abandoned sessions, records an OpenTelemetry span, and yields cleanly when shutdown begins.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Read projects/equinox/lib/codec/frame.cc and tell me whether EquinoxCloudReconcilerFlow can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"EquinoxAtlasSearchCoordinator needs a paired pass: separate EquinoxAtlasSearchCoordinator's policy from transport without behavior changes, plus give the existing implementation a read-only safety pass. Use projects/equinox/lib/codec/frame.cc as the source of truth, preserve the PostgreSQL 17 contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Maple: Incident timeline — INC-45133\n\n08:02 deploy EquinoxOrbitSyncFlow 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 EquinoxOrbitSyncFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"EquinoxRainfallDBCoordinator: give it a nicer flow","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Nimbus: projects/equinox/cmd/exporter/main.py の EquinoxJuniperCLIService で、SQLite の flow に断続的な問題が起きています。 原因は判明済みです。staging timeout だけを 15 秒から 30 秒へ変え、対応する assertion を直してください。\n\n制約:\n- SQLite を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は EquinoxJuniperCLIService のみ","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"ja"} +{"prompt":"UI ticket DES-45139: finish the compact EquinoxFrostPanelFlow filter experience\n\nRoute: /catalog/search\nSource: projects/equinox/apps/console/routes/usage.svelte\nFramework: Tokio\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring EquinoxFrostPanelFlow'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":"For EquinoxSummitProxyCoordinator, separate EquinoxSummitProxyCoordinator's policy from transport without behavior changes; once that is complete, capture the contract and rollback note for consumers. Work from projects/equinox/Sources/App/SessionStore.swift, stay with SQLite, and preserve cancellation and back-pressure semantics. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"EquinoxHarborIndexCoordinator: handle the lingering thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"diff --git a/projects/equinox/Sources/App/SessionStore.swift b/projects/equinox/Sources/App/SessionStore.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/equinox/Sources/App/SessionStore.swift\n+++ b/projects/equinox/Sources/App/SessionStore.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is EquinoxDeltaCanvasCoordinator'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":"EquinoxAsterWebhookCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"// projects/equinox/web/components/FilterDrawer.vue\nfinal class EquinoxIrisBatchFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 EquinoxIrisBatchFlow 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":"How should EquinoxAtlasSearchService be decomposed?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Fresh release brief for EquinoxMoonlitSDKCoordinator:\n- primary outcome: lay out a staged migration for EquinoxMoonlitSDKCoordinator\n- companion outcome: then implement the bounded durable-cursor handler\n- repository entry point: projects/equinox/lib/codec/frame.cc\n- platform constraint: PostgreSQL 17\n- known complication: a deadlock that appears only during shutdown\n\nBoth results are required, but they should remain independently reviewable. Preserve cancellation and back-pressure semantics; retain serialization and authorization boundaries; cover cancellation, idempotent retries, and rollback; and avoid drive-by cleanup. Use the code as the source of truth, call out assumptions, and state how an on-call engineer can tell that either part is unsafe to ship.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Fresh release brief for EquinoxFlintTimelineCoordinator:\n- primary outcome: assess ownership and failure handling in projects/equinox/cmd/exporter/main.py\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/equinox/cmd/exporter/main.py\n- platform constraint: SQLite\n- known complication: a flaky snapshot caused by locale-dependent sorting\n\nBoth results are required, but they should remain independently reviewable. Preserve cancellation and back-pressure semantics; 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":"EquinoxBirchMigratorCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"EquinoxCopperBridgeCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"On compact widths, EquinoxQuartzPlayerStore'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":"Memory attributed to EquinoxPineMetricsService rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Could the reasoning behind EquinoxTideWorkerFlow's WebGPU choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"EquinoxSpruceDaemonCoordinator: document, then correct","purpose":"writing","secondary":"backendImpl","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Ticket OPS-45117: retire the legacy replay path for EquinoxBirchMigratorFlow\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 EquinoxBirchMigratorFlow 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":"EquinoxEchoRegistryCoordinator: sequence, then ship","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"diff --git a/projects/equinox/infra/modules/edge/main.tf b/projects/equinox/infra/modules/edge/main.tf\nindex 62d71aa..90f3c1e 100644\n--- a/projects/equinox/infra/modules/edge/main.tf\n+++ b/projects/equinox/infra/modules/edge/main.tf\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate EquinoxVelaDrawerFlow'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":"The behavior of EquinoxCloudReconcilerService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/equinox/lib/codec/frame.cc. 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- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current PostgreSQL 17 operational envelope\n\nThe relevant code crosses identity, Rust CLI, Vue. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Ticket OPS-45110: retire the legacy replay path for EquinoxMoonlitSDKFlow\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 EquinoxMoonlitSDKFlow 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":"Compare the old and new EquinoxAsterWebhookStore 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":"En projects/equinox/services/ledger/replay.go, EquinoxNimbusFormStore tiene un problema intermitente en el flujo de NATS JetStream. Propón fases, compatibilidad, métricas, rollback y ownership; detente antes de tocar código.\n\nRestricciones:\n- seguir con NATS JetStream\n- conservar compatibilidad y cancelación\n- limitar el cambio a EquinoxNimbusFormStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con NATS JetStream alrededor de EquinoxNimbusFormStore.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"es"} +{"prompt":"Sketch the EquinoxVelaDrawerStore migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Bring EquinoxCraneWorkspaceStore'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":"EquinoxAsterWebhookService returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/equinox/app/src/main/SyncWorker.kt and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"The EquinoxCopperBridgeService 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":"Sequence EquinoxMosaicGridService's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-45147\n\n08:02 deploy EquinoxHarborIndexFlow 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 EquinoxHarborIndexFlow, 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":"EquinoxLedgerGateCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Flip EquinoxAmberFilterService's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Make EquinoxDriftConsoleStore keyboard navigable","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"projects/equinox/ml/pipeline/features.py 里的 EquinoxJuniperCLIStore 最近在 SQLite 流程中出现间歇性问题。 请实现幂等 endpoint，包含持久 cursor、tenant 鉴权、spans 和 retry 测试。\n\n约束：\n- 继续使用 SQLite\n- 保持兼容性和取消语义\n- 改动只限于 EquinoxJuniperCLIStore","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"zh"} +{"prompt":"Documente o contrato de EquinoxMarbleTokenService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"pt"} +{"prompt":"Opal: projects/equinox/ui/settings/PrivacyPane.tsx 里的 EquinoxCoralUploadService 最近在 PostgreSQL 17 流程中出现间歇性问题。 请阅读现有流程，判断 ownership、取消和顺序是否安全，只需要分析。\n\n约束：\n- 继续使用 PostgreSQL 17\n- 保持兼容性和取消语义\n- 改动只限于 EquinoxCoralUploadService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"zh"} +{"prompt":"Remove EquinoxKiteSchedulerService's stray comma","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Two asks around EquinoxVelaDrawerCoordinator: (1) separate EquinoxVelaDrawerCoordinator's policy from transport without behavior changes; (2) correct the known stale timeout beside it. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Prism: The EquinoxHarborIndexService surface in projects/equinox/config/staging.toml 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":"Quartz: // projects/equinox/workers/thumbnail/consumer.ex\nfinal class EquinoxKiteSchedulerFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nDeliver the EquinoxKiteSchedulerFlow server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Raven: Incident timeline — INC-45145\n\n08:02 deploy EquinoxCedarPolicyFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Map a safe route from the current EquinoxCedarPolicyFlow 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":"How does EquinoxSableParserFlow propagate cancellation through the WebGPU boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} diff --git a/data/round2-06.jsonl b/data/round2-06.jsonl index 9f3351e..f564e98 100644 --- a/data/round2-06.jsonl +++ b/data/round2-06.jsonl @@ -1,200 +1,200 @@ -{"prompt": "payroll run 2026-07 blew up halfway through and left 400 employees unpaid:\n\norg.springframework.dao.DeadlockLoserDataAccessException: PreparedStatementCallback; SQL [update payslip set net_cents=?, status=? where id=?]; Deadlock found when trying to get lock; try restarting transaction\n\tat org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTranslator.doTranslate(SQLErrorCodeSQLExceptionTranslator.java:263)\n\tat io.paycrest.payroll.PayslipRepository.updateNet(PayslipRepository.java:141)\n\tat io.paycrest.payroll.RunProcessor.processEmployee(RunProcessor.java:212)\n\tat io.paycrest.payroll.RunProcessor.lambda$run$3(RunProcessor.java:88)\n\tat java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373)\nCaused by: java.sql.SQLTransactionRollbackException: Deadlock found when trying to get lock\n\nrun 88412, 1,204 employees, parallel stream over the employee list, 8 threads", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "indexer falls behind head every few hours and never catches up without a restart:\n\n2026-07-29T11:02:14Z INFO indexer: processing block 21,104,882 (lag 2 blocks)\n2026-07-29T11:04:02Z INFO indexer: processing block 21,104,918 (lag 41 blocks)\n2026-07-29T11:08:11Z WARN indexer: rpc request took 8.4s method=eth_getLogs range=1000\n2026-07-29T11:08:19Z WARN indexer: rpc request took 11.2s method=eth_getLogs range=1000\n2026-07-29T11:12:44Z WARN indexer: reorg detected at 21,104,801, rolling back 12 blocks\n2026-07-29T11:12:58Z INFO indexer: reprocessing from 21,104,789 (lag 214 blocks)\n2026-07-29T11:31:02Z WARN indexer: postgres connection pool exhausted (20/20), waiting\n2026-07-29T11:44:18Z INFO indexer: processing block 21,104,912 (lag 604 blocks)\n\nthe RPC provider says our request rate is well within limits", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "our safety concept document has to go to the auditor in november, and writing it will expose where our latency budget doesn't close. produce the document, and give me a separate honest list of the numbers that don't add up so we can decide what to fix first", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "the payroll module ignores half our design tokens and its warning colour fails contrast on the row background it's used with. bring it onto the tokens, fix the contrast, and note in the design system docs which token pairs are safe on which surfaces there are fourteen hardcoded colours in there, six of them near-misses of a real token.", "purpose": "frontendImpl", "secondary": "writing", "mixed": true, "difficulty": 0.5, "slice": "mixed", "lang": "en"} -{"prompt": "angular app throws this on the timesheet screen for about one user in fifty:\n\nERROR RangeError: Maximum call stack size exceeded\n at Object.eval [as updateDirectives] (TimesheetGridComponent.html:41:9)\n at Module.debugUpdateDirectives (core.mjs:44112:12)\n at checkAndUpdateView (core.mjs:41882:5)\n at callViewAction (core.mjs:42214:21)\nERROR Error: NG0100: ExpressionChangedAfterItHasBeenCheckedError: Expression has changed after it was checked. Previous value for 'ngClass': 'row-warning'. Current value: 'row-error'.\n at throwErrorIfNoChangesMode (core.mjs:12044:11)\n\nthe grid has a getter in the template that computes the row state from the entries, and users with more than about 200 entries in a week hit it", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "indexer pool size up to 40", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "payroll thing", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "our angular app pulls fontawesome and moment into the initial bundle for three date formats and four icons, which is most of the budget overrun. replace both, keep the rendering identical, and check the print stylesheet still works", "purpose": "quickFix", "secondary": "refactor", "mixed": true, "difficulty": 0.45, "slice": "mixed", "lang": "en"} -{"prompt": "the payroll run has no alert when it sits in RUNNING for more than an hour, which is how we found out at breakfast", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "robot stops mid-path maybe once a day, and this is what the diagnostics dump:\n\nros2 topic hz /scan\n average rate: 9.412 min: 0.104s max: 0.882s std dev: 0.14112s window: 50\nros2 topic hz /odom\n average rate: 49.881 min: 0.019s max: 0.021s std dev: 0.00041s window: 50\n\n[nav2_controller]: Control loop missed its desired rate of 20.0000Hz... the loop actually took 0.2841 seconds\n[nav2_controller]: Invalid path, Path is empty.\n[behavior_server]: Running backup\n[bt_navigator]: Behavior tree threw exception: Action server timed out\n\nthe lidar is meant to publish at 10Hz and the CPU on the nav box sits at 60%", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "payslip PDF still says 2025 tax year", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "core", "lang": "en"} -{"prompt": "a spanish customer signs in september and we support four countries, none of them spain, which means social security bands, a different absence model and a filing format we've never produced. before anyone opens the calculator i want a plan: what a country pack actually has to contain, how much of spain is data versus code, and whether we can get there without touching the other four countries' behaviour at all", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "we owe a customer a written explanation for why four hundred people were paid late, and their HR director's actual question is why we didn't know until the morning. write the incident report: what happened, what the impact was, why our monitoring missed it, and what changes — without hiding behind the word \"deadlock\"", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "angular component behind our slowest screen. is the getter the whole problem or just part of it?\n\n@Component({\n selector: 'timesheet-grid',\n template: `\n \n {{ formatHours(day) }}\n {{ totalFor(row) }}\n `\n})\nexport class TimesheetGridComponent {\n @Input() entries: Entry[] = []\n get rows() { return this.groupByEmployee(this.entries) }\n rowState(r: Row) { return r.days.some(d => this.hasConflict(d)) ? 'row-error' : 'row-warning' }\n totalFor(r: Row) { return r.days.reduce((a, d) => a + this.minutes(d), 0) / 60 }\n hasConflict(d: Day) { return this.entries.filter(e => e.day === d.date).length > 1 }\n}", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "before this goes anywhere near a payroll run, tell me what's wrong with it:\n\n@Transactional\npublic void run(UUID runId) {\n PayrollRun run = runs.findById(runId).orElseThrow();\n run.getEmployees().parallelStream().forEach(emp -> {\n Payslip slip = calculator.calculate(emp, run.getPeriod());\n payslips.save(slip);\n run.addTotal(slip.getNetCents());\n });\n run.setStatus(COMPLETED);\n runs.save(run);\n events.publish(new PayrollCompleted(runId, run.getTotalCents()));\n}\n\nrun.addTotal mutates a long field on the entity; calculator hits the database for tax bands per employee", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "three services in the ROS graph each do their own transform lookup, with their own error handling:\n\n// pick_place_node.cpp\ntry { tf_buffer_->lookupTransform(\"base_link\", \"tool0\", tf2::TimePointZero); }\ncatch (const tf2::TransformException& e) { RCLCPP_WARN(get_logger(), \"%s\", e.what()); return; }\n\n// perception_node.cpp\nauto tf = tf_buffer_->lookupTransform(\"base_link\", \"camera_link\", msg->header.stamp,\n tf2::durationFromSec(0.1)); // throws on timeout\n\n// safety_node.cpp\nif (!tf_buffer_->canTransform(\"base_link\", \"lidar\", tf2::TimePointZero)) { return last_known_; }\n\none returns stale data on failure, one drops the message, one throws into a callback", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "absence type dropdown is missing bereavement", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "core", "lang": "en"} -{"prompt": "one date-range validator for all controllers", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "what happens when a tax table is missing?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "is `IsSafe` thread-safe as written?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "robot cell has to pass certification in november and our own numbers don't obviously add up — the perception pipeline alone measures 180ms against a 250ms budget, and the safety check shares a process with the motion controller. work through what the architecture would need to look like to actually satisfy the requirement, and what evidence we'd have to produce alongside it", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "payslip generation, PDF rendering and the bank file writer all live in one class called `PayrollService`", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "a walkthrough of how an absence becomes a deduction line would help before i touch the calculator", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "we need bank file generation to be resumable, because a 40MB export currently regenerates from scratch on every poll", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "arm drifts a few centimetres over a shift and we recalibrate every morning as a workaround:\n\n[ INFO] [1753843201.114]: joint_state_publisher: publishing at 50Hz\n[ WARN] [1753843261.882]: TF_REPEATED_DATA ignoring data with redundant timestamp for frame base_link at time 1753843261.880\n[ WARN] [1753843262.114]: TF_REPEATED_DATA ignoring data with redundant timestamp for frame tool0 at time 1753843262.112\n[ WARN] [1753843321.441]: Lookup would require extrapolation into the past. Requested time 1753843321.401 but the earliest data is at time 1753843321.412\n[ERROR] [1753843382.002]: Trajectory execution aborted: goal tolerance violated on joint_4 (0.0142 > 0.0100)\n[ INFO] [1753843382.114]: controller reset, resuming\n\nsim is perfect, and it only happens on the two cells with the newer controllers", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "webhooks to our customers' HR systems started failing on tuesday, only for two of them:\n\nPOST https://hr.customer-a.example/webhooks/paycrest\n → 200 OK in 412ms\n\nPOST https://api.customer-b.example/paycrest\n → SSL routines:ssl3_read_bytes:sslv3 alert handshake failure\n → retry 1: same\n → retry 2: same\n → giving up after 3 attempts, event queued\n\nPOST https://hooks.customer-c.example/in\n → 421 Misdirected Request\n → retry 1: 421\n → giving up\n\nwe upgraded the base image on monday, from debian bookworm to trixie", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "reorg handling, which i inherited and don't trust:\n\nasync fn handle_block(&mut self, block: Block) -> Result<()> {\n let parent = self.db.get_block(block.number - 1).await?;\n if parent.hash != block.parent_hash {\n let depth = self.find_common_ancestor(&block).await?;\n self.db.delete_blocks_from(depth + 1).await?;\n self.cursor = depth;\n return Ok(());\n }\n let logs = self.rpc.get_logs(block.number, block.number).await?;\n let mut tx = self.db.begin().await?;\n self.db.insert_block(&mut tx, &block).await?;\n for log in logs { self.apply_log(&mut tx, log).await?; }\n tx.commit().await?;\n self.cursor = block.number;\n Ok(())\n}\n\nfind_common_ancestor walks back one block at a time; delete_blocks_from cascades to the balances table", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "this is the safety check on our motion controller and i want another pair of eyes before the certification audit:\n\nbool MotionController::IsSafe(const State& s) const {\n if (estop_pressed_.load()) return false;\n if (s.velocity.norm() > max_velocity_) return false;\n if (last_heartbeat_age() > std::chrono::milliseconds(250)) return false;\n for (const auto& obstacle : obstacles_) {\n if ((s.position - obstacle.position).norm() < safety_radius_) return false;\n }\n return true;\n}\n\nobstacles_ is refreshed by the perception callback on another thread; last_heartbeat_age reads a member updated in the same callback; there is no mutex anywhere in this class", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "RFC for our new payout scheduling. does the reasoning survive contact with reality?\n\n## Proposal\nMove payroll runs from a single nightly batch to a queue of per-employee jobs. Each job is independently retryable, and a run completes when every job reports success.\n\n## Rationale\nA single failing employee currently fails the whole run, and we cannot restart from the middle.\n\n## Consequences\n- Partial runs become visible to customers, who will ask what \"partially paid\" means.\n- Totals can no longer be computed in the same transaction as the slips.\n- Retry storms are possible if the tax service is down.\n\n## Open\nWhether a run can be approved before all jobs complete.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "safety documentation for the cell, which the auditor will read line by line. what we have:\n\n- e-stop cuts power to the servo drives directly, software is not in the loop\n- the software safety check runs at 100Hz and stops motion if the heartbeat is older than 250ms\n- obstacle detection comes from two lidars, fused, with a 200mm safety radius around the tool\n- reduced-speed mode is entered when a human is detected in the cell, at 250mm/s\n- the perception pipeline has a measured worst-case latency of 180ms\n- recovery from a safety stop requires a physical reset, not a software command\n\nwrite the safety concept document; where our numbers don't add up against a 250ms budget, say so rather than smoothing it over", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "changelog for the indexer, from the commits since v0.9:\n\n41c9e0b feat(reorg): handle reorgs deeper than 12 blocks\n88f21c0 fix(logs): decode indexed value parameters on Transfer\nc0aa774 perf(rpc): batch eth_getLogs into 200-block ranges\n2e91b45 fix(db): don't hold a transaction across an RPC call\naa30f19 feat(api): expose /v1/balances/{address} with block-height parameter\n9c1d004 chore: bump alloy to 0.8\n4410bb7 fix(cursor): persist the cursor after commit, not before\nb77e910 feat(metrics): per-contract indexing lag\n\nour users are other teams who run this themselves; two of these change behaviour in ways that need explaining", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "pasted-context", "lang": "en"} -{"prompt": "support keeps getting asked this and answering differently each time. from the code, write the definitive page:\n\ncustomer question: \"When exactly does an absence affect pay? We entered sick leave on the 28th for the period that closed on the 25th, and the employee was paid in full, then a correction appeared the following month with no explanation on the payslip.\"\n\nwhat the code does: absences in a closed period are accepted with retro=true; the next run generates a correction line; the correction line's description is the absence type only, with no dates; the payslip PDF renders corrections in a separate block at the bottom; and if the employee leaves before the next run, the correction is silently dropped", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "same date-range validation lives in four controllers with four different error messages:\n\n// AbsenceController\nif (req.getEnd().isBefore(req.getStart())) throw new BadRequest(\"end before start\");\n\n// TimesheetController\nif (!req.getEnd().isAfter(req.getStart())) throw new BadRequest(\"invalid range\");\n\n// ReportController\nif (req.getStart().plusYears(1).isBefore(req.getEnd())) throw new BadRequest(\"range too wide\");\nif (req.getEnd().isBefore(req.getStart())) throw new BadRequest(\"end before start\");\n\n// PayrollController\nAssert.isTrue(req.getStart().compareTo(req.getEnd()) <= 0, \"bad range\");\n\nthe API contract says a range where start equals end is valid, and two of these disagree", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "pasted-context", "lang": "en"} -{"prompt": "indexer's event decoding is a match arm per contract and there are now 40 of them:\n\nmatch (log.address, log.topics[0]) {\n (addr, topic) if addr == USDC && topic == TRANSFER => decode_transfer_indexed(log),\n (addr, topic) if addr == DAI && topic == TRANSFER => decode_transfer(log),\n (addr, topic) if addr == WETH && topic == TRANSFER => decode_transfer(log),\n (addr, topic) if addr == USDC && topic == APPROVAL => decode_approval(log),\n // ... 36 more\n _ => Ok(None),\n}\n\nadding a token means editing this match, and half the arms differ only in whether the value parameter is indexed", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "design spec for the timesheet week view, angular, replacing the grid that falls over:\n\nWeek view (desktop, 1280px+)\n- Employee rows, sticky first column with name and role, 7 day columns plus a total column.\n- Cells show hours as a decimal to one place; empty cells show an em dash at 40% opacity.\n- Conflicts (two entries on the same day) render an amber left border on the cell and a tooltip listing both.\n- Cells are editable inline: click focuses an input, enter commits and moves down, escape reverts, tab moves right.\n- Unsaved edits show a small dot in the corner; a failed save turns the cell's border destructive with a retry affordance.\n- The total column recalculates optimistically as you type.\n- Above 500 rows the table virtualises, but the sticky column and the totals must stay correct while scrolling.\n- Keyboard-only operation must be possible for the whole grid, including conflict resolution.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "run progress bar needs an elapsed timer", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "why does startup take four minutes?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "whatever the auditor needs", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "timesheet screen is the top support complaint and the obvious fix is virtualising the grid, but i suspect the real problem is that the component recomputes everything in template getters. before committing to a rewrite i want a view on whether this is a restructure of the existing component or a genuine redesign, and what each would cost", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "nobody can tell me whether our motion controller's safety check is actually safe, because the obstacle list and the heartbeat are written by a perception callback on another thread and there isn't a mutex in the class. read it properly and tell me what can go wrong, how likely it is, and whether the certification auditor would accept it", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "employee portal fails most of an accessibility audit and our public sector customers will ask about it at renewal. fix the concrete items — the payslip iframe, the calendar keyboard navigation, form error association — and write the accessibility statement we can publish afterwards the statement has to be specific enough that a procurement reviewer can check it.", "purpose": "frontendImpl", "secondary": "writing", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "i want a position on whether the robot's perception and safety should share a computer at all", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "one tf lookup helper for the three nodes", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "three more chains are on the indexer's roadmap and each one is a week of work plus permanent RPC cost, while the existing chain already falls behind after every reorg. i'd rather we agreed what \"supporting a chain\" means for us — backfill, lag SLOs, cost per chain — before saying yes to any of them, and then decided which of the three is actually worth doing first", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "before we build spanish payroll i want the country-pack boundary agreed — what's data, what's code, how tax years are versioned — and then the boundary proven by moving one existing country onto it, ideally the simplest one, so we find out what's wrong with the design before spain lands", "purpose": "planning", "secondary": "refactor", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "is the reporting query's correlated subquery the reason it times out, or is it the left join on payslips", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "what guarantees does the export endpoint make when two of the customer's servers poll it at once", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "absence approval endpoint should reject approvals from someone in the requester's own reporting line", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "les cotisations sociales sont fausses pour trois salariés et je ne vois pas pourquoi :\n\nSalarié 4412 brut 3 200,00 plafond SS 3 864,00 tranche A 3 200,00 tranche B 0,00 ✓\nSalarié 4418 brut 4 100,00 plafond SS 3 864,00 tranche A 3 864,00 tranche B 236,00 ✓\nSalarié 4421 brut 4 100,00 plafond SS 3 864,00 tranche A 4 100,00 tranche B 0,00 ✗\nSalarié 4429 brut 5 000,00 plafond SS 3 864,00 tranche A 3 864,00 tranche B 1 136,00 ✓\nSalarié 4433 brut 4 100,00 plafond SS 3 864,00 tranche A 4 100,00 tranche B 0,00 ✗\n\nles trois salariés en erreur ont tous eu un avenant au contrat en cours de mois, et le plafond devrait être proratisé", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "fr"} -{"prompt": "balances in the indexer disagree with the chain for exactly four addresses:\n\naddress indexed on-chain diff\n0x8f21c0aa774119a2b3c4d5e6f7a8b9c0d1e2f3a4 1,204.118401 1,204.118401 0\n0x41ba190c0aa7741192b3c4d5e6f7a8b9c0d1e2f3 882.441000 882.437600 0.0034\n0x2e91b45aa30f199c1d0044410bb7b77e91030cc2 0.000000 12.400000 12.4\n0xc0aa7741ba190882e91b452e91b45aa30f199c1d 4,118.220000 4,118.220000 0\n0xaa30f199c1d0044410bb7b77e91030cc219e1f0a 41.000000 40.999999 0.000001\n\nreconciliation job output:\n checked 41,882 addresses across 12 tokens\n mismatches: 4 (all on token 0x9c1d0044410bb7b77e91030cc219e1f0a8f21c0a)\n first divergence at block 21,041,882\n last full agreement at block 21,041,881\n\nthe token's ABI:\n event Transfer(address indexed from, address indexed to, uint256 indexed value)\n\nevery other token we index declares value as a non-indexed parameter, and all four addresses received from this contract", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "payroll engine migration has two months of parallel running left and has to finish before year end, but the diff process is a gist, the sign-off is an email, and nobody has defined what a clean month looks like. i'd like the remaining migration planned properly, including the cutover criteria, what we do if month four fails, and how we prove to an auditor afterwards that the numbers matched", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "indexer decodes events through a forty-arm match on address and topic, where most arms differ only in whether the value parameter is indexed, and adding a token means editing it. replace it with a registry that's data rather than code, keeping the decoding behaviour byte-identical for every contract we currently index", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "our javadoc claims the run is atomic, which stopped being true when we parallelised it", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "the payroll run has no alert while it sits in RUNNING, which is why a failure at two in the morning was found at six by a human. add the alerting, and tell me what else in that pipeline has the same shape — a state that can be entered and never left without anyone noticing", "purpose": "quickFix", "secondary": "review", "mixed": true, "difficulty": 0.5, "slice": "mixed", "lang": "en"} -{"prompt": "angular build warnings that have been ignored for a year and now break the budget:\n\nWarning: bundle initial exceeded maximum budget. Budget 1.00 MB was not met by 412.11 kB with a total of 1.40 MB.\nWarning: src/app/timesheet/timesheet-grid.component.ts depends on 'moment'. CommonJS or AMD dependencies can cause optimization bailouts.\nWarning: src/app/shared/icons.ts depends on '@fortawesome/fontawesome-free'. CommonJS or AMD dependencies can cause optimization bailouts.\nWarning: src/app/payroll/payroll.module.ts is part of the declarations of 2 modules\n\nError: Budget exceeded, build failed\n\nmoment is used in three files for date formatting only", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "indexer needs a story for backfilling a single contract after a decoding bug, without reindexing everything or touching other contracts' data. think it through with me — cursor per contract, ranges, how balances get recomputed — then implement the range-reprocessing command ranges have to be resumable, because one contract's history is months of blocks.", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "payroll calculator is one class with a branch per country, two hundred lines each, and the proposal on the table is a rules engine with country packs loaded at runtime. i can see why, and i can also see auditors asking which rules produced a payslip three years ago. weigh the options honestly, including the boring one where it stays code but gets restructured", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "en"} -{"prompt": "our health endpoint reports the indexer healthy while it's six hundred blocks behind head", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "the `dual_write` flag governs the whole payroll migration and nobody can say precisely what it switches any more. work out what it actually does from the code, then write the page describing it, including what happens if someone turns it off halfway through a run", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.55, "slice": "mixed", "lang": "en"} -{"prompt": "robot cell repo has a two-line readme and a twenty-minute manual calibration procedure documented in a scanned pdf. write the readme a new engineer could actually follow to a moving robot, including the vendored driver patch, the realtime kernel requirement, and the launch-order problem that bites everyone on hardware assume the reader has used ROS before but has never seen this cell.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "payslip viewer should let people download the PDF without opening the iframe at all", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "a short note for the team on why balances are becoming a sum over deltas", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "we need to decide whether the timesheet week view keeps its own state or moves to the store the rest of the app uses", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "angular modules call the API three different ways depending on which year they were written, three components forget to unsubscribe, and only one handles the error case. bring all fourteen onto the newest pattern, keep every screen behaving as it does now, and make the error handling consistent rather than absent fourteen components in total, and the newest pattern is the one we want to end up on.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "spring boot app takes 4 minutes to start in prod and 20 seconds locally:\n\n2026-07-29T11:02:14.881Z INFO 1 --- [main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 8080 (http)\n2026-07-29T11:02:18.114Z INFO 1 --- [main] o.h.jpa.internal.util.LogHelper : HHH000204: Processing PersistenceUnitInfo [name: default]\n2026-07-29T11:04:41.882Z INFO 1 --- [main] o.h.e.j.e.i.LobCreatorBuilderImpl : HHH000424: Disabling contextual LOB creation as createClob() method threw error\n2026-07-29T11:05:52.114Z INFO 1 --- [main] o.s.o.j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default'\n2026-07-29T11:06:02.441Z INFO 1 --- [main] i.p.config.TaxTableLoader : loaded 41,882 tax bands\n2026-07-29T11:06:14.002Z INFO 1 --- [main] i.paycrest.Application : Started Application in 241.118 seconds\n\nthe gap between 11:02:18 and 11:04:41 is where it sits doing nothing visible", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "gazebo sim passes, real robot fails the same test, and the only difference i can find is timing:\n\n[component_container]: Failed to load component: Package 'gripper_driver' not found\n[component_container]: Component loaded: force_sensor_node\n[force_sensor_node]: Publishing /wrench at 500Hz\n[gripper_action_server]: Waiting for /wrench...\n[gripper_action_server]: Waiting for /wrench...\n[gripper_action_server]: Timed out waiting for /wrench after 5.0s\n[pick_place_node]: Aborting: gripper action server unavailable\n[pick_place_node]: Retrying (1/3)\n[gripper_action_server]: Received first /wrench message\n\nthe force sensor node comes up about 6 seconds after the gripper server on hardware, instantly in sim", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "der Kollege hat das für die Lohnabrechnung geschrieben, bitte einmal drüberschauen:\n\npublic BigDecimal berechneSteuer(BigDecimal brutto, Steuerklasse klasse, int jahr) {\n var tabelle = tabellen.get(jahr);\n if (tabelle == null) {\n tabelle = tabellen.get(jahr - 1); // Fallback auf das Vorjahr\n }\n var band = tabelle.stream()\n .filter(b -> brutto.compareTo(b.von()) >= 0 && brutto.compareTo(b.bis()) <= 0)\n .findFirst()\n .orElse(tabelle.get(tabelle.size() - 1));\n return brutto.multiply(band.satz()).setScale(2, RoundingMode.HALF_UP);\n}\n\ndie Tabellen für 2026 sind noch nicht eingepflegt, und die Klasse wird nirgends verwendet", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "de"} -{"prompt": "sql the reporting screen runs, which times out for our biggest customer:\n\nSELECT e.id, e.full_name, d.name AS department,\n SUM(p.gross_cents) AS ytd_gross,\n SUM(p.tax_cents) AS ytd_tax,\n (SELECT COUNT(*) FROM absences a WHERE a.employee_id = e.id AND a.starts_at >= $2) AS absence_count,\n (SELECT MAX(pr.paid_at) FROM payslips pr WHERE pr.employee_id = e.id) AS last_paid\nFROM employees e\nJOIN departments d ON d.id = e.department_id\nLEFT JOIN payslips p ON p.employee_id = e.id AND p.period >= $2\nWHERE e.org_id = $1 AND e.terminated_at IS NULL\nGROUP BY e.id, e.full_name, d.name\nORDER BY e.full_name;\n\n41,000 employees, payslips has 4.1M rows, and there's an index on payslips(employee_id, period)", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "ROS launch file, which nobody wants to touch. what does it actually guarantee about startup order?\n\ndef generate_launch_description():\n return LaunchDescription([\n Node(package='lidar_driver', executable='lidar_node', output='screen'),\n Node(package='force_sensor', executable='force_node', output='screen'),\n Node(package='gripper_driver', executable='gripper_action_server', output='screen'),\n TimerAction(period=5.0, actions=[\n Node(package='nav2_bringup', executable='navigation_launch', output='screen'),\n ]),\n Node(package='pick_place', executable='pick_place_node', output='screen',\n parameters=[{'wrench_timeout': 5.0}]),\n ])\n\non hardware the force sensor takes about six seconds to enumerate over USB", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "payroll's parallel-run notes from the migration, they need to become a proper runbook:\n\n- we run the old and new engines on the same period and diff the payslips\n- differences under 2 cents are ignored, anything above goes in a spreadsheet\n- the diff script lives in a gist, takes a run id, and needs read access to both databases\n- known acceptable differences: rounding on pension contributions, and the order of deduction lines\n- if more than 5 employees differ we don't cut over that month\n- the finance lead signs off by replying to an email, which is our only record\n- we've done this for three months and have two months to go", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "public API for absences, documented by nobody. this is what the controller does:\n\n@PostMapping(\"/v2/absences\")\npublic AbsenceDto create(@RequestBody @Valid AbsenceRequest req, @AuthenticationPrincipal Principal p) {\n // employee must belong to the caller's org, else 404 (deliberately not 403)\n // overlapping absences of the same type are rejected with 409\n // overlapping absences of different types are allowed and both count\n // half days are expressed as 0.5 in `days`, quarter days are not supported\n // absences in a closed payroll period are accepted but flagged `retro: true`\n // a retro absence triggers a correction on the next run, never a rerun\n // the `approver_id` is ignored on create and set by the approval endpoint\n}\n\nwrite the reference page, and be explicit about the 404-instead-of-403 because integrators keep filing bugs about it", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "incident notes from the failed payroll run, and 400 people were paid late. we owe the customer a write-up:\n\n02:14 run 88412 starts, 1,204 employees\n02:31 run fails with a database deadlock, status stuck at RUNNING\n02:33 automatic retry starts, fails identically\n06:02 on-call notices during the morning check, not from an alert\n06:40 we establish 804 payslips were written and 400 were not\n07:15 decision: complete the run manually rather than restart it\n09:52 remaining 400 payslips generated, bank file submitted\n11:30 bank confirms the second file, employees paid same day but late\n14:00 root cause: parallel processing of employees updating a shared run total row\n\nthe customer's HR director wants to know why we didn't know until the morning", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "escribe la guía de despliegue a partir de estas notas, que hoy están en la cabeza de una persona:\n\n- el indexador se despliega con helm, pero antes hay que parar el reorg handler manualmente\n- si no se para, la migración de la tabla `blocks` se bloquea y hay que matar la conexión a mano\n- las migraciones se aplican con `sqlx migrate run` desde un pod temporal, no en el arranque\n- después del despliegue hay que verificar que el cursor avanza; si no avanza en dos minutos, rollback\n- el rollback es volver al chart anterior y reiniciar desde el último checkpoint, se pierden unos 10 minutos de datos\n- nunca desplegar durante una reorganización en curso, se corrompen los saldos\n- hay un feature flag `dual_write` que debe estar activo durante toda la migración", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "es"} -{"prompt": "README for the robot cell repo, currently two lines. what a new person needs:\n\n- ROS 2 Jazzy, ubuntu 24.04, colcon workspace, three packages plus a vendored driver\n- the vendored gripper driver has a patch on top of upstream that must be reapplied after any update, patch is in patches/\n- simulation: `ros2 launch cell_bringup sim.launch.py`, works on any machine\n- hardware: needs the realtime kernel, the user in the dialout group, and the safety PLC in maintenance mode\n- the calibration procedure is a 20 minute manual process documented in a pdf someone scanned\n- tests: unit tests run anywhere, integration tests need either sim or hardware and are not in CI\n- known issue: the force sensor enumerates slowly on hardware, which breaks the launch order\n\nwrite the readme so someone can get to a moving robot without a tap on the shoulder", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "o texto do email que vai para 1.400 empregados está mau, reescreve-o:\n\n\"Caro colaborador, Informamos que devido a uma incidência técnica no processamento do vencimento referente ao mês de Julho, o pagamento poderá ter sido efetuado com atraso relativamente à data habitual. A situação encontra-se resolvida. Agradecemos a compreensão. Departamento de Recursos Humanos.\"\n\nfactos: o pagamento chegou no mesmo dia mas várias horas mais tarde; não houve erro nos valores; ninguém precisa de fazer nada; quem tenha tido encargos bancários por causa do atraso deve contactar o RH e será reembolsado", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "pt"} -{"prompt": "checkstyle and spotbugs after the merge, and the build gate goes on next week:\n\n[ERROR] PayslipRepository.java:141: Method length is 88 lines (max allowed is 50). [MethodLength]\n[ERROR] RunProcessor.java:88: 'if' construct must use '{}'s. [NeedBraces]\n[WARNING] TaxTableLoader.java:22: Found reliance on default encoding: new FileReader(String) [DM_DEFAULT_ENCODING]\n[WARNING] AbsenceService.java:66: Possible null pointer dereference of approver in AbsenceService.approve() [NP_NULL_ON_SOME_PATH]\n[WARNING] Money.java:41: Class defines equals() but not hashCode() [HE_EQUALS_USE_HASHCODE]\n\n2 errors, 3 warnings", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"} -{"prompt": "clippy on the indexer, some of these look like they matter:\n\nwarning: this `.await` holds a non-Send type across an await point\n --> src/indexer/handler.rs:88:9\nwarning: large enum variant\n --> src/types.rs:41:1\n |\n41 | enum Event { Transfer(TransferEvent), Approval(Box), Raw([u8; 4096]) }\nwarning: this loop never actually loops\n --> src/rpc/retry.rs:22:5\nwarning: called `unwrap` on a `Result` value in an async fn\n --> src/db/cursor.rs:141:32\n\nwarning: `indexer` (bin \"indexer\") generated 18 warnings", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "connection pool settings across our services, and the indexer is the one that exhausts:\n\n# api\nspring.datasource.hikari.maximum-pool-size: 40\nspring.datasource.hikari.connection-timeout: 30000\n\n# worker\nspring.datasource.hikari.maximum-pool-size: 20\nspring.datasource.hikari.connection-timeout: 30000\n\n# indexer (rust, sqlx)\nmax_connections: 20\nacquire_timeout: 30s\nidle_timeout: 600s\n\n# postgres\nmax_connections = 100\nreserved_connections = 3\n\nthe indexer opens a transaction per block and holds it across the RPC call for logs", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "docker base image bump broke outbound TLS to two customers, here's the difference:\n\n# before (bookworm)\nopenssl version: OpenSSL 3.0.11\nMinProtocol = TLSv1.2\nCipherString = DEFAULT@SECLEVEL=2\n\n# after (trixie)\nopenssl version: OpenSSL 3.5.0\nMinProtocol = TLSv1.2\nCipherString = DEFAULT@SECLEVEL=3\n\ncustomer-b's endpoint:\n TLSv1.2, ECDHE-RSA-AES128-SHA, RSA 2048, SHA1 signature\ncustomer-c's endpoint:\n TLSv1.2, cipher fine, but the certificate chain is missing an intermediate", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "パラメータの設定が本番とステージングで違っていて、実機だけ止まる原因かもしれません:\n\n# staging (sim) — config/controller.sim.yaml\ncontroller:\n loop_rate: 20.0\n goal_tolerance: 0.02\n lidar_rate_expected: 10.0\n wrench_timeout: 5.0\n tf_buffer_duration: 10.0\n use_sim_time: true\n max_velocity: 0.5\n\n# production (hardware) — config/controller.hw.yaml\ncontroller:\n loop_rate: 20.0\n goal_tolerance: 0.01\n lidar_rate_expected: 10.0\n wrench_timeout: 5.0\n tf_buffer_duration: 1.0\n use_sim_time: false\n max_velocity: 0.5\n\n# 実機のログ（抜粋、1 時間に 40 回ほど）\n[ WARN] Lookup would require extrapolation into the past. Requested time 1753843321.401 but the earliest data is at time 1753843321.412\n[ERROR] Trajectory execution aborted: goal tolerance violated on joint_4 (0.0142 > 0.0100)\n[ INFO] controller reset, resuming\n\ntf_buffer_duration は去年、メモリ使用量を下げるために変更したものです。goal_tolerance を誰が変えたのかは記録が残っていません", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "ja"} -{"prompt": "github action for the rust indexer, cache never hits:\n\n- uses: actions/checkout@v4\n- uses: dtolnay/rust-toolchain@stable\n- uses: actions/cache@v4\n with:\n path: |\n ~/.cargo/registry\n target\n key: ${{ runner.os }}-cargo-${{ github.sha }}\n- run: cargo build --release\n- run: cargo test --all-features\n- run: cargo clippy -- -D warnings\n\nevery run: \"Cache not found for input keys: Linux-cargo-\"\nbuild time: 14 minutes", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "pasted-context", "lang": "en"} -{"prompt": "this calculator has grown a parameter every time a country was added. same numbers out, better shape:\n\npublic Payslip calculate(Employee e, Period p, boolean includeBonus, boolean prorate,\n Country country, TaxYear year, boolean applyPensionCap,\n BigDecimal overrideRate, boolean skipSocial, List extra) {\n if (country == Country.FR && prorate) { /* 40 lines */ }\n else if (country == Country.DE) { /* 60 lines, ignores prorate */ }\n else if (country == Country.PT) { /* 30 lines, uses overrideRate if set */ }\n else { /* the original UK path, 80 lines */ }\n}\n\nfour call sites pass different combinations, and two of them pass nulls for parameters the branch ignores", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "unser Angular-Code hat drei Wege, dieselbe API zu rufen. Bitte vereinheitlichen, ohne Verhalten zu ändern:\n\n// altes Modul\nthis.http.get('/api/v2/absences').subscribe(a => this.absences = a)\n\n// neueres Modul\nthis.absenceService.list().pipe(takeUntilDestroyed()).subscribe(a => this.absences.set(a))\n\n// neuestes Modul\nabsences = toSignal(inject(AbsenceService).list(), { initialValue: [] })\n\nvierzehn Komponenten insgesamt, drei davon vergessen das Abmelden, und der Fehlerfall wird nur in einem behandelt", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "de"} -{"prompt": "test fixtures for payroll are four builders that disagree about defaults:\n\nEmployee e1 = TestEmployees.uk(); // salaried, tax code 1257L, no pension\nEmployee e2 = new EmployeeBuilder().build(); // salaried, no tax code at all\nEmployee e3 = Fixtures.employee(FR); // hourly, with a pension scheme\nEmployee e4 = anEmployee().withSalary(50000).build(); // salaried, UK, pension at 5%\n\nabout 900 tests, and a test that passes with one builder often fails with another because of the pension default", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "planning input for the half, and i need a sequence rather than a wish list:\n\n- payroll engine migration has two months of parallel running left, and it has to finish before year end\n- a customer in Spain signs in september and we don't support Spanish social security at all\n- the timesheet screen is the top support complaint and is unusable above 200 entries\n- the indexer team wants to add three chains, each of which is a week of work plus ongoing RPC cost\n- our robot cell customer needs the certification audit passed by november or the deployment slips a year\n- two engineers are shared between payroll and the indexer and are context-switching badly\n- there's a compliance deadline in january for real-time payroll reporting in one country", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "architecture ticket that needs thinking, not code:\n\nPAY-620 — Multi-country payroll calculation\nThe calculator is one class with a country branch and 200 lines per country. Adding Spain means a fifth branch. Proposal is a rules engine with country packs loaded at runtime, so a country can be added without a deploy. Concerns raised: payroll rules change annually and must be versioned by tax year; auditors need to see exactly which rules produced a given payslip, years later; a rules engine makes the calculation harder to unit test than a plain class; and two of our countries have rules that genuinely need arbitrary code, not data.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "indexer's roadmap request from the teams that depend on it:\n\n- three more chains, with the same API surface\n- historical backfill on demand rather than the current \"reindex everything\" script\n- per-contract lag metrics so a team can alert on their own contract falling behind\n- a way to reprocess a range after a decoding bug, without touching other contracts' data\n- read replicas, because the reporting queries are now competing with indexing writes\n- some story for reorgs deeper than our current 12-block assumption\n\none engineer, one quarter. what would you do and in what order", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "customer requirement for the robot cell, and the certification audit is in november:\n\n\"The safety function shall bring the manipulator to a controlled stop within 250 ms of a human entering the collaborative workspace. Detection shall be redundant, with no single sensor failure defeating the function. The safety function shall be independent of the application software and shall be verifiable without disassembly. Evidence shall include a documented worst-case latency analysis covering sensing, processing, communication and actuation.\"\n\nour perception pipeline alone measures 180ms worst case, the safety check runs in the same process as the motion controller, and we have two lidars but they feed one fusion node", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "spec for the payroll run screen, which is what customers stare at on the 25th:\n\nRun detail\n- Header: period, status (Draft / Calculating / Ready / Approved / Paid / Failed), employee count, total net. Status drives a coloured left border on the whole card.\n- Progress: during Calculating, a determinate bar with \"812 of 1,204 payslips\", updating over websocket, plus an elapsed timer.\n- Employee table: name, gross, deductions, net, a warning glyph where the payslip differs from last period by more than 20%.\n- Filters: only warnings, only changes, by department. Filters persist for the session.\n- Approve is a primary button, disabled unless status is Ready, with a confirmation dialog that restates the total and the employee count.\n- Failed state shows which employees failed, why, and a Retry failed button that does not touch the successful ones.\n- Everything must degrade gracefully when the websocket drops — fall back to polling, never show stale progress as live.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "accessibility audit of the employee portal, which our public sector customers care about:\n\n- The payslip PDF viewer is an iframe with no title and no text alternative; screen reader users get nothing.\n- The absence calendar is a table of divs; dates are not announced and arrow-key navigation does nothing.\n- Form errors appear only as red text under the field, not associated with the input and not announced.\n- The \"submit timesheet\" flow uses colour alone to indicate which days are incomplete.\n- Focus is lost to the top of the page after every modal closes.\n- Session timeout warning appears visually with a countdown that is never announced.\n- Contrast fails on the secondary button in both themes (3.1:1).", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "design tokens versus what the payroll module actually uses:\n\ntokens:\n color.text.default #1B1F23\n color.text.muted #5A6672\n color.status.warning #B26A00\n color.status.danger #B3261E\n space.1..6 4 8 12 16 24 32\n radius.sm/md/lg 4 8 12\n font.size.body 14/20\n font.size.caption 12/16\n\npayroll module: 14 hardcoded hex values, six of which are near-misses of the token colours; paddings of 6, 10 and 18px; two font sizes not in the scale; and a warning colour that fails contrast on the row background it's used with\n\nbring it onto the tokens and fix the contrast failure while you're there", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "integration spec our customer's HR system expects from us:\n\nGET /v2/exports/payroll?period=2026-07&format=sepa-xml\n auth: mutual TLS with a client cert we issue, plus an API key header\n response: 200 with the file, or 202 with a Location header if generation takes longer than 5 seconds\n the 202 path must be pollable and the result cached for 24 hours\n the file must be byte-identical on repeated requests for the same period unless a correction was posted\n a correction invalidates the cache and increments a `revision` in the filename\n they poll every 30 seconds from three of their servers, so concurrent identical requests must not generate the file three times\n file sizes are up to 40MB and they cannot handle chunked encoding", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "schema we agreed for reorg-safe balances, needs implementing in the indexer:\n\nCREATE TABLE balance_deltas (\n id bigserial PRIMARY KEY,\n address bytea NOT NULL,\n token bytea NOT NULL,\n delta numeric(78,0) NOT NULL,\n block_number bigint NOT NULL,\n log_index int NOT NULL,\n UNIQUE (block_number, log_index)\n);\nCREATE INDEX ON balance_deltas (address, token, block_number);\n\nbalances become a sum over deltas up to a block height; a reorg deletes deltas above the fork point; the /v1/balances endpoint must answer at any height without scanning the whole history, and it's currently answering from a mutable balances table that reorgs corrupt", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "drop moment from the timesheet module", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "cargo cache key uses the sha", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "lower the indexer's batch to 200 blocks", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "la fecha del recibo sale en formato americano", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "core", "lang": "es"} -{"prompt": "seclevel back to 2 for the outbound client", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "tf buffer duration to 10s on hardware", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "hashCode missing on the Money class", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "payroll calculator takes ten parameters, four of which are ignored on three of the four country paths, and two call sites pass nulls into branches that never read them. restructure it so each country's rules live somewhere coherent, with identical output for every payslip in the last twelve months as the acceptance criterion the last twelve months of payslips are the regression suite, so nothing may move by a cent.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "indexer holds a database transaction across an RPC call, which is why the pool exhausts whenever the provider is slow", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "our on-call has no alerting on payroll runs at all, and the obvious alerts would have caught tuesday's failure four hours earlier", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "the tax table loader falls back to the previous year when the current year's bands aren't loaded, silently, and the 2026 bands are not in yet. before we change anything i want to know exactly what that fallback produces on a real payslip and how we'd have noticed if a customer hadn't told us", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "das Bundle-Budget auf 1,5 MB anheben", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "de"} -{"prompt": "unwrap in db/cursor.rs, make it fallible", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "warning glyph on payslips that jumped 20%", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "sticky name column on the week view", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "empty cells should show an em dash", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "core", "lang": "en"} -{"prompt": "chain selector in the indexer console", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "休暇カレンダーの矢印キー操作が効きません", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "ja"} -{"prompt": "secondary button contrast fails in both themes", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "focus jumps to the top after a modal closes", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "conflict border should be amber, not red", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "boundary", "lang": "en"} -{"prompt": "totals row scrolls away", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "`RunProcessor` per-country strategies", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "decode table instead of 40 match arms", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "un seul builder pour les tests de paie", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "fr"} -{"prompt": "`gross_cents` naming, everywhere", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "pull the retry policy out of the rpc client", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "inline `minutes()`, one caller", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "signals everywhere in the absence module", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "javadoc on the payroll calculator, please", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "changelog entry for the reorg fix", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "kurze Notiz zur Parallelabrechnung", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "de"} -{"prompt": "document the retro absence behaviour", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "summarise the safety concept for the auditor", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "PR body for the balance deltas change", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "¿el indexador maneja bien las reorganizaciones?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "es"} -{"prompt": "can two runs touch the same payslip?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "walk me through the approval flow", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "payslips missing for 400 employees", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "arm drifts over a shift", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "webhooks to two customers fail TLS", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "warum hängt der Indexer nach einer Reorg?", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "de"} -{"prompt": "endpoint for per-contract indexing lag", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "algo pequeno para hoje", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "pt"} -{"prompt": "carry on where that left off", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "tidier, please", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "grid, you know", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "next one on the list", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "same but for Spain", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "unblock the robot people", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "faster, ideally", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "another look at that screen", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "finish the migration bit", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "le truc d'hier, la suite", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "fr"} -{"prompt": "start wherever you like", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "absences API is integrated against by six customers and documented nowhere, which is why we get the same three bugs filed repeatedly — the 404 instead of 403, the retro flag, and half days. write the reference page from the controller's actual behaviour, with the surprising parts called out rather than buried in a table", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "deployment procedure for the indexer lives in one engineer's head and includes at least two steps that will corrupt balances if skipped. write it up as a runbook: the pre-deploy checks, the manual stop, the migration step, how to tell within two minutes whether it worked, and exactly what rollback costs us in lost data", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "support answers \"when does an absence affect pay\" differently every time, and the honest answer involves retro flags, corrections on the next run, and a case where the correction is silently dropped. write the page that settles it, in language an HR administrator understands, and be explicit about the dropped-correction case rather than omitting it", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "reorg handler walks back one block at a time to find a common ancestor and deletes forward with a cascade to balances, and i want to understand what that does during a twelve-block reorg while the indexer is already behind. no changes yet — i want to know what actually happens, including what a reader sees mid-rollback", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "en"} -{"prompt": "RFC proposing per-employee payroll jobs mentions that partial runs become customer-visible and then moves on, which is the part i'd have thought hardest. read it against how runs work today and tell me whether the consequences section is complete, particularly around approval before all jobs finish i would rather know now than after we have built the queue.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "four addresses have balances that disagree with the chain, all of them holding a token whose Transfer event indexes the value parameter, unlike every other token we index. work out whether our decoder is silently producing zero for those, and how many other contracts we index have the same shape i also want to know how many other contracts we index emit the same event shape.", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "timesheet grid needs to survive five hundred rows without falling over, which means virtualising it, but the sticky employee column and the optimistic totals have to keep working while scrolling. rebuild it to the spec, keep inline editing and keyboard navigation exactly as designed, and make sure conflicts are still visible when a row is partially scrolled", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "payroll run screen shows progress over a websocket and simply freezes when the socket drops, which during a run is indistinguishable from the run being stuck. add a polling fallback, make stale progress visibly stale rather than silently wrong, and keep the approve button's guard conditions exactly as they are it should also survive the tab being backgrounded for ten minutes and brought back.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "safety architecture needs redesigning for certification and there's a piece we can start regardless: separating the safety check into its own process with its own watchdog. give me the design for the whole thing first, then do that separation so we have something to measure assume the auditor will ask for the latency budget in writing, with measurements.", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.9, "slice": "mixed", "lang": "en"} -{"prompt": "unsere Zeiterfassung ist auf Wochenbasis gebaut und ein Kunde braucht Schichtmodelle über Mitternacht hinweg. Ich hätte gern zuerst ein Konzept, wie das Datenmodell aussehen müsste, und danach die Migration der bestehenden Einträge", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "de"} -{"prompt": "real-time payroll reporting becomes a legal requirement in one country in january and we currently report monthly in a batch. map out what compliance means for our architecture, then start on whichever piece has the longest lead time — my guess is the submission client, but tell me if it isn't", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "parallel-run process for the payroll migration exists only as folklore and a gist. write it up properly as a runbook, and while you're in the diff script, make it fail loudly when it can't reach one of the two databases instead of reporting zero differences the finance lead's email sign-off should become something we can actually find later.", "purpose": "writing", "secondary": "quickFix", "mixed": true, "difficulty": 0.55, "slice": "mixed", "lang": "en"} -{"prompt": "escreve a documentação da API de exportação para o cliente e confirma no código se o ficheiro é mesmo idêntico entre pedidos repetidos, porque é isso que estamos a prometer", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "pt"} -{"prompt": "three employees got the wrong social security bands and all three had a contract amendment mid-month, which suggests the cap isn't being prorated. confirm that from the code, then fix it and tell me how many past payslips are affected i would also like to know whether mid-month terminations hit the same proration bug.", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "robot stops mid-path about once a day and the lidar's publishing rate is wildly variable in the logs. work out whether that's the sensor, the USB bus or our own callback blocking, and once you know, put the diagnostic in place that would tell us next time without a manual dump", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "i'd like to understand what our launch file actually guarantees about node startup order on hardware", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "is it expected that the indexer's cursor is persisted before the commit rather than after", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "docs/payroll.md describes the old sequential run and the retry semantics we removed", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "api changelog needs an entry for the balances endpoint's block-height parameter", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "write the customer-facing note about the late payment, apologetic but factual, one paragraph", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "necesitamos documentar qué hace el flag `dual_write` durante la migración, nadie se acuerda", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "es"} -{"prompt": "dates differ between the UI and PDF", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "goal tolerance on hardware is half what it is in sim, and nobody knows who changed it or why", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "per-contract cursors in the indexer, so one slow contract doesn't hold up everything else", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "how should we version country payroll rules so an auditor can reproduce a payslip from three years ago", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "what's the right way to test payroll calculations, given that a wrong answer is a legal problem rather than a bug", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "two engineers are split across payroll and the indexer and neither project is moving, what would you do about the allocation", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "what should the story be for customers who want their payroll data in their own warehouse, three have asked now", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "run detail screen needs the failed-employee list with a retry that skips the successful ones", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "absence calendar should show public holidays for the employee's country, greyed and non-selectable", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "indexer console needs a reorg history view, so we can see when balances were rolled back", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "reporting screen times out on our biggest customer and the obvious fix is pagination, which finance will hate", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "whatever is on fire", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "other half of that", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "deduction-line ordering differs between the old and new payroll engines, which the migration diff flags every month and we've been waving through as cosmetic. work out whether the order is actually meaningful for the payslip PDF and the bank file, make the new engine match wherever it is, and then write down what \"acceptable difference\" means so the next person isn't guessing", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "topic names are hardcoded as string literals in forty places across the ROS packages, with two typos that only bite in one launch configuration. centralise them properly, and while you're there tell me whether the two typo'd topics were ever connected to anything or have been silently dead since the port to Jazzy", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "`PayrollService` does payslip generation, PDF rendering and bank file writing in one class of about nine hundred lines, and the bank file part is the bit under audit. split it along those three responsibilities, then document which class owns what so the auditor's questions have an obvious answer", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "our angular error handling is three parsers deep because each spring service invented its own error shape. unify the server side onto one shape, and confirm from the client code which of the three parsers is still reachable before you delete anything", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "employee test fixtures exist in four flavours with different pension defaults, which is why moving a test between packages changes its outcome. consolidate onto one builder, then write the short note on fixture conventions that should have existed before the fourth one appeared about nine hundred tests depend on these, so the migration has to be mechanical.", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.5, "slice": "mixed", "lang": "en"} -{"prompt": "i want to know whether a parallel stream over employees can corrupt the run total — the entity has a mutable long that every thread adds to — and if it can, the fix, with a test that reproduces it reliably rather than one that passes by luck the run total is a mutable long on the entity, which is the part that worries me.", "purpose": "review", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "angular timesheet grid recomputes row state in a template getter on every change detection pass, which i think explains both the stack overflow and the changed-after-checked error. confirm the mechanism from the code, then tell me the smallest change that fixes it without the rewrite we've been putting off", "purpose": "review", "secondary": "planning", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "before i touch the calculator i'd like to understand how an absence becomes a deduction line — which service decides the daily rate, what happens with a half day, and where the retro flag enters — and then have the tax table cache invalidation documented, because i can't find the call at all", "purpose": "review", "secondary": "writing", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "we need per-contract cursors in the indexer so one slow contract doesn't hold up the rest, but that changes what \"indexed up to block N\" means for the API and for our lag alerts. decide the semantics with me first, then implement the cursor split", "purpose": "backendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "error responses differ per spring service — some return a problem-details object, some a bare string, one an html error page from the container — and the angular client has grown a parser for each. settle on one shape across the services, keep every status code as it is, and make sure the html case can't happen at all", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "payslip generation, PDF rendering and bank file writing share one class and one set of tests, so a change to the PDF layout requires understanding the bank file format. separate them with the same public entry points, and keep the generated output byte-identical for the last three periods as the acceptance test", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "nobody can tell me how a payslip correction gets matched back to the absence that caused it, which matters because the correction line on the PDF shows only the absence type. trace it through and explain the matching, including what happens when two absences of the same type land in the same closed period", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "leavers keep their portal access until the next payroll run processes their termination, which HR has now raised as a compliance problem rather than an inconvenience. revoke access at the termination date instead, keep payslip access for the statutory period, and make sure a termination entered in error can be reversed without a support ticket", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "a nightly job should flag employees whose net pay has moved more than twenty percent since the last period, before the run is approved rather than after someone complains. thresholds per organisation, an obvious way to acknowledge a flag, and the flags need to survive a recalculation of the run without being silently cleared", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "the `Run` entity collides with three other Runs across the java service — the payroll one, an import run, a robot cell test run — and every import block has to disambiguate. rename the payroll one throughout, including the JPA table mapping if that can be done without a migration, and check nothing depends on the class name reflectively", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "who else defines a `Run` type?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "why does row state recompute constantly?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "one employee builder for the tests", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} +{"prompt":"I inherited FoxglovePineMetricsStore and need a careful read of projects/foxglove/services/ledger/replay.go 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- cover the awkward empty and retry states\n- stay compatible with the existing Kafka deployment\n- keep the work scoped to FoxglovePineMetricsStore and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"FoxgloveLumenChartStore returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/foxglove/cmd/exporter/main.py and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"FoxgloveNimbusFormCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Two asks around FoxgloveSableParserCoordinator: (1) assess ownership and failure handling in projects/foxglove/db/migrations/20260730_events.sql; (2) capture the contract and rollback note for consumers. Cover the awkward empty and retry states, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"What does FoxgloveHarborIndexStore own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Sable: Two deliverables are holding up FoxgloveFernSnapshotCoordinator. First, assess ownership and failure handling in projects/foxglove/Sources/App/SessionStore.swift. In the same workstream, capture the contract and rollback note for consumers. The relevant starting point is projects/foxglove/Sources/App/SessionStore.swift, which follows Cloudflare Workers conventions and currently suffers from an accessibility label that reads the internal enum. Cover the awkward empty and retry states.\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":"review","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Tide: projects/foxglove/ui/settings/PrivacyPane.tsx の FoxgloveSummitProxyFlow で、GraphQL の flow に断続的な問題が起きています。 現在の flow を読み、ownership、cancel、順序が安全か評価してください。分析だけで十分です。\n\n制約:\n- GraphQL を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は FoxgloveSummitProxyFlow のみ","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"ja"} +{"prompt":"Release engineering needs a FoxgloveKiteSchedulerService 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":"For FoxgloveGarnetModalCoordinator, change FoxgloveGarnetModalCoordinator's known staging timeout from 15 to 30 seconds; once that is complete, give the existing implementation a read-only safety pass. Work from projects/foxglove/internal/auth/refresh.go, stay with Kafka, and cover the awkward empty and retry states. Keep the two outcomes separately reviewable.","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Incident timeline — INC-46118\n\n08:02 deploy FoxgloveCedarPolicyFlow 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 FoxgloveCedarPolicyFlow 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":"FoxgloveAcornWidgetCoordinator is blocking the next release because an empty state that flashes before cached data arrives. I need two concrete outcomes from a single pass: change FoxgloveAcornWidgetCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing Spring Boot conventions in projects/foxglove/db/migrations/20260730_events.sql; cover the awkward empty and retry states. 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.5,"slice":"mixed","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_46157'\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_46157'::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\nDeliver the FoxgloveBeaconStoreCoordinator server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Pin FoxgloveAsterWebhookService's Kafka dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Umbra: Ticket OPS-46155: retire the legacy replay path for FoxgloveAmberFilterCoordinator\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 FoxgloveAmberFilterCoordinator 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":"Split FoxgloveCedarPolicyStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"FoxgloveBasilRunnerCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Bring FoxgloveMapleQueueStore'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":"Vela: Two deliverables are holding up FoxgloveQuartzPlayerCoordinator. First, separate FoxgloveQuartzPlayerCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/foxglove/ui/settings/PrivacyPane.tsx, which follows GraphQL conventions and currently suffers from a flaky snapshot caused by locale-dependent sorting. Cover the awkward empty and retry states.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"FoxgloveBirchMigratorCoordinator: handle the lingering thing","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Test Suite 'FoxglovePrismCacheFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[FoxglovePrismCacheFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/foxglove/cmd/exporter/main.py:144: error: -[FoxglovePrismCacheFlowTests 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 '-[FoxglovePrismCacheFlowTests 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 FoxglovePrismCacheFlow'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":"debugging","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Willow: The first FoxgloveAtlasSearchFlow request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"FoxgloveVelaDrawerCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Xylem: Ticket OPS-46141: retire the legacy replay path for FoxgloveSpruceDaemonFlow\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 FoxgloveSpruceDaemonFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Three teams extended FoxgloveAmberFilterService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- cover the awkward empty and retry states\n- retain the current Spring Boot operational envelope\n\nThis repository spans observability, SwiftUI, Redis; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"FoxgloveHarborIndexCoordinator: restructure, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Yarrow: The API work is done; what remains for FoxgloveAcornWidgetStore 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 FoxgloveAcornWidgetStore\n- cover the awkward empty and retry states\n\nSeveral teams work in this observability, SwiftUI, Redis monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Zephyr: Two asks around FoxgloveMoonlitSDKCoordinator: (1) finish FoxgloveMoonlitSDKCoordinator's responsive empty and retry states; (2) give the existing implementation a read-only safety pass. Cover the awkward empty and retry states, and leave a clear boundary between the resulting artifacts or edits.","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"A previously stable test around FoxgloveOrbitSyncFlow now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"FoxgloveRainfallDBCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Checkout: Incident timeline — INC-46130\n\n08:02 deploy FoxgloveSableParserFlow 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 FoxgloveSableParserFlow 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":"For FoxglovePrismCacheCoordinator, finish FoxglovePrismCacheCoordinator's responsive empty and retry states; once that is complete, correct the known stale timeout beside it. Work from projects/foxglove/ml/pipeline/features.py, stay with Cloudflare Workers, and cover the awkward empty and retry states. Keep the two outcomes separately reviewable.","purpose":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Does FoxgloveCoralUploadFlow enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"// projects/foxglove/pkg/cache/lease.rs\nfinal class FoxgloveCinderAuthFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveCinderAuthFlow 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":"FoxgloveBeaconStoreFlow returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/foxglove/services/ledger/replay.go and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Exporter: Incident timeline — INC-46150\n\n08:02 deploy FoxgloveMarbleTokenCoordinator 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 FoxgloveMarbleTokenCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Why does FoxgloveBeaconStoreStore's Kafka worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Scheduler: Incident timeline — INC-46124\n\n08:02 deploy FoxgloveCraneWorkspaceFlow 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 FoxgloveCraneWorkspaceFlow 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":"Extract FoxgloveFernSnapshotService's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"A copied hex color in FoxgloveWrenExportFlow lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fresh release brief for FoxgloveLedgerGateCoordinator:\n- primary outcome: produce a consumer guide for FoxgloveLedgerGateCoordinator\n- companion outcome: give the existing implementation a read-only safety pass\n- repository entry point: projects/foxglove/apps/console/routes/usage.svelte\n- platform constraint: Spring Boot\n- known complication: lease renewal code copied across three workers\n\nBoth results are required, but they should remain independently reviewable. Cover the awkward empty and retry states; 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":"writing","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Spell FoxgloveGarnetModalStore's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"FoxgloveDriftConsoleCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"FoxgloveTideWorkerCoordinator needs a paired pass: produce a consumer guide for FoxgloveTideWorkerCoordinator, plus give the existing implementation a read-only safety pass. Use projects/foxglove/app/src/main/SyncWorker.kt as the source of truth, preserve the Spring Boot contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"The FoxgloveMicaProfileStore surface in projects/foxglove/services/ledger/replay.go 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":"Why does FoxgloveVelaDrawerStore's Cloudflare Workers worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"# projects/foxglove/ui/settings/PrivacyPane.tsx\n[worker.foxglovecopperbridgeflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.foxglovecopperbridgeflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.foxglovecopperbridgeflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.FoxgloveCopperBridgeFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-46121\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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. The intended correction is already known: change only the stale 15-second setting to 30 seconds in projects/foxglove/ui/settings/PrivacyPane.tsx and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"We need to move FoxgloveFlintTimelineStore from the legacy store to GraphQL. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"FoxgloveCloudReconcilerCoordinator: polish, then correct","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Give FoxgloveAsterWebhookStore a README example","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Release engineering needs a FoxgloveBirchMigratorStore 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":"We need to move FoxgloveMarbleTokenStore from the legacy store to Spring Boot. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"What sequence would let FoxgloveSpruceDaemonStore adopt GraphQL 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.8,"slice":"core","lang":"en"} +{"prompt":"Could the reasoning behind FoxgloveBirchMigratorService's Spring Boot choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"PM is preparing the FoxgloveFrostPanelService 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 FoxgloveFrostPanelService\n- cover the awkward empty and retry states\n\nSeveral teams work in this observability, SwiftUI, Redis monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Dashboard: projects/foxglove/ui/settings/PrivacyPane.tsx has grown through several launches, and FoxgloveSummitProxyService now mixes policy, transport, persistence, and metrics in one place. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- cover the awkward empty and retry states\n- stay compatible with the existing GraphQL deployment\n- keep the work scoped to FoxgloveSummitProxyService and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/foxglove/internal/auth/refresh.go b/projects/foxglove/internal/auth/refresh.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/foxglove/internal/auth/refresh.go\n+++ b/projects/foxglove/internal/auth/refresh.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is FoxgloveBasilRunnerFlow'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":"Worker: // projects/foxglove/config/staging.toml\nfinal class FoxgloveAtlasSearchCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Walk through what the artifact proves about FoxgloveAtlasSearchCoordinator; 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":"FoxgloveSpruceDaemonCoordinator: could this be clearer","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Ticket OPS-46137: retire the legacy replay path for FoxgloveMicaProfileFlow\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 FoxgloveMicaProfileFlow, 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":"Simulator: // projects/foxglove/infra/modules/edge/main.tf\nfinal class FoxgloveFrostPanelFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveFrostPanelFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"FoxgloveLumenChartCoordinator: give it a nicer flow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current FoxgloveJuniperCLIStore 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 FoxgloveJuniperCLIStore\n- cover the awkward empty and retry states\n\nSeveral teams work in this observability, SwiftUI, Redis 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":"FoxgloveEmberRelayCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-46152\n\n08:02 deploy FoxgloveMosaicGridCoordinator 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 FoxgloveMosaicGridCoordinator, 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":"Style FoxgloveLedgerGateService's offline state","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"FoxgloveDeltaCanvasCoordinator needs a paired pass: ship the idempotent FoxgloveDeltaCanvasCoordinator replay endpoint, plus capture the contract and rollback note for consumers. Use projects/foxglove/ui/settings/PrivacyPane.tsx as the source of truth, preserve the GraphQL contract, and avoid unrelated cleanup.","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Serve FoxglovePrismCacheService health checks","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-46122: retire the legacy replay path for FoxgloveAsterWebhookFlow\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 FoxgloveAsterWebhookFlow 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":"Runbook: projects/foxglove/infra/modules/edge/main.tf now contains FoxgloveBasilRunnerStore's normalization branch three times. Consolidate it behind one private helper, keep call ordering identical, and avoid touching generated code. Please preserve behavior. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"FoxgloveFlintTimelineCoordinator: sort out the rough edge","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Compare the old and new FoxgloveAmberFilterStore 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":"Since the last release, FoxgloveSlateEditorService 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- cover the awkward empty and retry states\n- stay compatible with the existing Kotlin coroutines deployment\n- keep the work scoped to FoxgloveSlateEditorService and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Trace: projects/foxglove/app/src/main/SyncWorker.kt 里的 FoxgloveRavenSessionService 最近在 Spring Boot 流程中出现间歇性问题。 请写一份面向调用方的说明，包含 contract、错误、retry 和可复制示例，不要改 handler。\n\n约束：\n- 继续使用 Spring Boot\n- 保持兼容性和取消语义\n- 改动只限于 FoxgloveRavenSessionService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"zh"} +{"prompt":"FoxgloveAsterWebhookCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Diff: projects/foxglove/services/ledger/replay.go has grown through several launches, and FoxgloveBeaconStoreService now mixes policy, transport, persistence, and metrics in one place. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- cover the awkward empty and retry states\n- stay compatible with the existing Kafka deployment\n- keep the work scoped to FoxgloveBeaconStoreService and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Before we approve FoxgloveCinderAuthStore, assess whether two validators with subtly different error strings is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"The FoxgloveAmberFilterFlow surface in projects/foxglove/apps/console/routes/usage.svelte 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":"FoxgloveCedarPolicyCoordinator: diagnose, then correct","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Profiler: The FoxgloveLumenChartService empty state in projects/foxglove/ml/pipeline/features.py needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating an accessibility label that reads the internal enum in FoxgloveMosaicGridStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Does FoxgloveCloudReconcilerService preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Extract FoxgloveOspreyJobStore's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"FoxgloveAtlasSearchStore's metric is misspelled as succesful_total in one declaration. Correct that literal and its exact test expectation, without renaming anything else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"// projects/foxglove/engine/render/atlas.cpp\nfinal class FoxgloveFlintTimelineFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveFlintTimelineFlow 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":"Introduce a durable deduplication key for FoxgloveDriftConsoleService 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":"FoxgloveSlateEditorCoordinator is blocking the next release because timestamps rendered one day ahead near UTC midnight. I need two concrete outcomes from a single pass: assess ownership and failure handling in projects/foxglove/packages/api/openapi.yaml, and capture the contract and rollback note for consumers. Use the existing Kotlin coroutines conventions in projects/foxglove/packages/api/openapi.yaml; cover the awkward empty and retry states. 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":"review","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"FoxgloveCopperBridgeCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Make FoxgloveJuniperCLIService keyboard navigable","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Console: # projects/foxglove/ml/pipeline/features.py\n[worker.foxglovewrenexportcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.foxglovewrenexportcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.foxglovewrenexportcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.FoxgloveWrenExportCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-46159\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/foxglove/ml/pipeline/features.py. 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":"FoxgloveCinderAuthCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"FoxglovePineMetricsCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Give FoxgloveEchoRegistryStore'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":"Decouple FoxgloveDeltaCanvasService's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Summarize the FoxgloveCopperBridgeService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"The behavior of FoxgloveLedgerGateStore is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/foxglove/apps/console/routes/usage.svelte. 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- cover the awkward empty and retry states\n- retain the current Spring Boot operational envelope\n\nThis repository spans observability, SwiftUI, Redis; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Describe FoxgloveOpalRouterService's error envelope","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"// projects/foxglove/engine/render/atlas.cpp\nfinal class FoxgloveJuniperCLIFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveJuniperCLIFlow'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":"Workspace: Ticket OPS-46131: retire the legacy replay path for FoxgloveDeltaCanvasFlow\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 FoxgloveDeltaCanvasFlow 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":"Por que FoxgloveNovaPickerService trava?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"pt"} +{"prompt":"FoxgloveKiteSchedulerCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Store FoxgloveCloudReconcilerStore's delivery receipts","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"FoxgloveRavenSessionCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Repository: // projects/foxglove/infra/modules/edge/main.tf\nfinal class FoxgloveGarnetModalFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveGarnetModalFlow 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":"Release engineering needs a FoxgloveMosaicGridFlow 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":"Pipeline: # projects/foxglove/src/sync/reconcile.ts\n[worker.foxgloveacornwidgetflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.foxgloveacornwidgetflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.foxgloveacornwidgetflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.FoxgloveAcornWidgetFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-46110\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 FoxgloveAcornWidgetFlow'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":"En projects/foxglove/ui/settings/PrivacyPane.tsx, FoxgloveQuartzPlayerStore tiene un problema intermitente en el flujo de GraphQL. Propón fases, compatibilidad, métricas, rollback y ownership; detente antes de tocar código.\n\nRestricciones:\n- seguir con GraphQL\n- conservar compatibilidad y cancelación\n- limitar el cambio a FoxgloveQuartzPlayerStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con GraphQL alrededor de FoxgloveQuartzPlayerStore.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"es"} +{"prompt":"Gateway: Ticket OPS-46135: retire the legacy replay path for FoxgloveRavenSessionFlow\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 FoxgloveRavenSessionFlow 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":"Renderer: The name pendingAck means two different things across FoxgloveNimbusFormService's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"For FoxgloveOpalRouterCoordinator, assess ownership and failure handling in projects/foxglove/engine/render/atlas.cpp; once that is complete, capture the contract and rollback note for consumers. Work from projects/foxglove/engine/render/atlas.cpp, stay with GraphQL, and cover the awkward empty and retry states. Keep the two outcomes separately reviewable.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"FoxgloveEchoRegistryCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Compare the old and new FoxgloveVelaDrawerService 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":"Read projects/foxglove/Sources/App/SessionStore.swift and tell me whether FoxgloveWillowCodecService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Could FoxgloveMarbleTokenFlow show the active Spring Boot sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Since the last release, FoxgloveCoralUploadStore has shown a misleading timeout name used in five packages; 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- cover the awkward empty and retry states\n- stay compatible with the existing Kotlin coroutines deployment\n- keep the work scoped to FoxgloveCoralUploadStore and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Center the FoxgloveTideWorkerStore modal","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Spell FoxgloveCraneWorkspaceStore's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-46123: retire the legacy replay path for FoxgloveCloudReconcilerFlow\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 FoxgloveCloudReconcilerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"FoxgloveJuniperCLICoordinator: ship, then document","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Two asks around FoxgloveNovaPickerCoordinator: (1) change FoxgloveNovaPickerCoordinator's known staging timeout from 15 to 30 seconds; (2) capture the contract and rollback note for consumers. Cover the awkward empty and retry states, and leave a clear boundary between the resulting artifacts or edits.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"FoxgloveKiteSchedulerStore's staging timeout is already known to be wrong: change the single projects/foxglove/pkg/cache/lease.rs value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Trace FoxgloveHarborIndexService's memory growth","purpose":"debugging","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 FoxgloveWrenExportService 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 FoxgloveWrenExportService\n- cover the awkward empty and retry states\n\nSeveral teams work in this observability, SwiftUI, Redis 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":"Two asks around FoxgloveCraneWorkspaceCoordinator: (1) find the unknown cause of a deadlock that appears only during shutdown; (2) correct the known stale timeout beside it. Cover the awkward empty and retry states, 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":"UI ticket DES-46154: finish the compact FoxgloveIrisBatchCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/foxglove/Sources/CLI/Commands/Doctor.swift\nFramework: Cloudflare Workers\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 FoxgloveIrisBatchCoordinator 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":"Indexer: // projects/foxglove/Sources/CLI/Commands/Doctor.swift\nfinal class FoxgloveFernSnapshotFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nAdd the bounded FoxgloveFernSnapshotFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"diff --git a/projects/foxglove/ml/pipeline/features.py b/projects/foxglove/ml/pipeline/features.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/foxglove/ml/pipeline/features.py\n+++ b/projects/foxglove/ml/pipeline/features.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\nRead the artifact above as a skeptical reviewer. Is FoxgloveLumenChartFlow'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":"Incident timeline — INC-46126\n\n08:02 deploy FoxgloveOpalRouterFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current FoxgloveOpalRouterFlow 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":"The data is already available in projects/foxglove/Sources/CLI/Commands/Doctor.swift; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Split FoxgloveOspreyJobService without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"FoxgloveMapleQueueCoordinator: polish the last piece","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Apparently: # projects/foxglove/apps/console/routes/usage.svelte\n[worker.foxgloveechoregistryflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.foxgloveechoregistryflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.foxgloveechoregistryflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.FoxgloveEchoRegistryFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-46145\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 The intended correction is already known: change only the stale 15-second setting to 30 seconds in projects/foxglove/apps/console/routes/usage.svelte and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Milestones for replacing FoxglovePineMetricsService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Does FoxglovePrismCacheStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"This should remain a deliberately small patch: FoxgloveAcornWidgetService has one known configuration mistake in projects/foxglove/src/sync/reconcile.ts, 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- cover the awkward empty and retry states\n- stay compatible with the existing Spring Boot deployment\n- keep the work scoped to FoxgloveAcornWidgetService and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"// projects/foxglove/Sources/App/SessionStore.swift\nfinal class FoxgloveWillowCodecFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveWillowCodecFlow; 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":"Fresh release brief for FoxgloveFrostPanelCoordinator:\n- primary outcome: change FoxgloveFrostPanelCoordinator'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/foxglove/internal/auth/refresh.go\n- platform constraint: Kafka\n- known complication: lost focus when the drawer animation finishes\n\nBoth results are required, but they should remain independently reviewable. Cover the awkward empty and retry states; 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.6,"slice":"mixed","lang":"en"} +{"prompt":"Ticket OPS-46143: retire the legacy replay path for FoxgloveEmberRelayFlow\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 FoxgloveEmberRelayFlow 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":"diff --git a/projects/foxglove/ml/pipeline/features.py b/projects/foxglove/ml/pipeline/features.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/foxglove/ml/pipeline/features.py\n+++ b/projects/foxglove/ml/pipeline/features.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 FoxgloveRainfallDBFlow'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":"Release engineering needs a FoxgloveNimbusFormStore 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":"FoxgloveMicaProfileCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Give FoxgloveMapleQueueService'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":"Warum hängt FoxgloveRainfallDBStore?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"de"} +{"prompt":"Lately: // projects/foxglove/engine/render/atlas.cpp\nfinal class FoxgloveOrbitSyncCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveOrbitSyncCoordinator 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":"Oddly: diff --git a/projects/foxglove/app/src/main/SyncWorker.kt b/projects/foxglove/app/src/main/SyncWorker.kt\nindex 62d71aa..90f3c1e 100644\n--- a/projects/foxglove/app/src/main/SyncWorker.kt\n+++ b/projects/foxglove/app/src/main/SyncWorker.kt\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure FoxgloveLedgerGateFlow 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":"Map FoxgloveCopperBridgeStore's ownership split","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Dedupe FoxgloveCedarPolicyService's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"On compact widths, FoxgloveIrisBatchFlow'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":"The minimum supported GraphQL version in projects/foxglove/engine/render/atlas.cpp 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":"Incident timeline — INC-46134\n\n08:02 deploy FoxgloveNimbusFormFlow 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 FoxgloveNimbusFormFlow, 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":"Design the FoxgloveGarnetModalService rollback","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Corrige le timeout de FoxgloveNovaPickerStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"fr"} +{"prompt":"Move FoxgloveSpruceDaemonService'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":"Store FoxgloveTideWorkerService's delivery receipts","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Pin FoxgloveSableParserService's Spring dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"projects/foxglove/packages/api/openapi.yaml の FoxgloveEmberRelayService で、Kotlin coroutines の flow に断続的な問題が起きています。 段階、互換性、metrics、rollback、ownership を提案し、コード変更の前で止めてください。\n\n制約:\n- Kotlin coroutines を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は FoxgloveEmberRelayService のみ","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"ja"} +{"prompt":"Please resist widening this one: FoxgloveSlateEditorStore works, but staging still carries a setting that production corrected last month. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside FoxgloveSlateEditorStore\n- cover the awkward empty and retry states\n\nSeveral teams work in this observability, SwiftUI, Redis monorepo, so keep ownership and handoff points understandable in a small review.\n\nThe cause and exact value change are already known, so keep this as a contained correction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-46128: finish the compact FoxgloveOspreyJobFlow filter experience\n\nRoute: /catalog/search\nSource: projects/foxglove/crates/index/src/segment.rs\nFramework: Kotlin coroutines\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 FoxgloveOspreyJobFlow'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":"core","lang":"en"} +{"prompt":"Why does FoxgloveSummitProxyStore's GraphQL worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'FoxgloveVelaDrawerFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[FoxgloveVelaDrawerFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/foxglove/cmd/exporter/main.py:144: error: -[FoxgloveVelaDrawerFlowTests 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 '-[FoxgloveVelaDrawerFlowTests 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 FoxgloveVelaDrawerFlow'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":"Currently: diff --git a/projects/foxglove/workers/thumbnail/consumer.ex b/projects/foxglove/workers/thumbnail/consumer.ex\nindex 62d71aa..90f3c1e 100644\n--- a/projects/foxglove/workers/thumbnail/consumer.ex\n+++ b/projects/foxglove/workers/thumbnail/consumer.ex\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 FoxgloveQuartzPlayerFlow 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":"Today: // projects/foxglove/db/migrations/20260730_events.sql\nfinal class FoxgloveBirchMigratorFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxgloveBirchMigratorFlow'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":"FoxgloveOspreyJobCoordinator needs a paired pass: produce a consumer guide for FoxgloveOspreyJobCoordinator, plus give the existing implementation a read-only safety pass. Use projects/foxglove/pkg/cache/lease.rs as the source of truth, preserve the Kotlin coroutines contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Context: # projects/foxglove/workers/thumbnail/consumer.ex\n[worker.foxglovesummitproxycoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.foxglovesummitproxycoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.foxglovesummitproxycoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.FoxgloveSummitProxyCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-46151\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/foxglove/workers/thumbnail/consumer.ex and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Background: projects/foxglove/config/staging.toml 里的 FoxgloveEmberRelayStore 最近在 Kotlin coroutines 流程中出现间歇性问题。 请给出阶段、兼容层、指标、rollback 和 ownership，先不要修改代码。\n\n约束：\n- 继续使用 Kotlin coroutines\n- 保持兼容性和取消语义\n- 改动只限于 FoxgloveEmberRelayStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"FoxgloveMosaicGridService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- cover the awkward empty and retry states\n- retain the current Kafka operational envelope\n\nThis repository spans observability, SwiftUI, Redis; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Question: diff --git a/projects/foxglove/config/staging.toml b/projects/foxglove/config/staging.toml\nindex 62d71aa..90f3c1e 100644\n--- a/projects/foxglove/config/staging.toml\n+++ b/projects/foxglove/config/staging.toml\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure FoxgloveMoonlitSDKFlow 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":"Observation: Incident timeline — INC-46120\n\n08:02 deploy FoxgloveHarborIndexFlow 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\nFind the source of this FoxgloveHarborIndexFlow symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Constraint: The public surface of FoxgloveMarbleTokenService is frozen, but its internal ownership in projects/foxglove/db/migrations/20260730_events.sql 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 FoxgloveMarbleTokenService\n- cover the awkward empty and retry states\n\nSeveral teams work in this observability, SwiftUI, Redis 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":"Before touching projects/foxglove/engine/render/atlas.cpp, 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":"Request: The public surface of FoxgloveOrbitSyncService is frozen, but its internal ownership in projects/foxglove/lib/codec/frame.cc 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 FoxgloveOrbitSyncService\n- cover the awkward empty and retry states\n\nSeveral teams work in this observability, SwiftUI, Redis 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":"Goal: # projects/foxglove/apps/console/routes/usage.svelte\n[worker.foxglovetideworkerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.foxglovetideworkerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.foxglovetideworkerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.FoxgloveTideWorkerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-46125\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 FoxgloveTideWorkerFlow'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":"Symptom: // projects/foxglove/web/components/FilterDrawer.vue\nfinal class FoxglovePineMetricsFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 FoxglovePineMetricsFlow; 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":"FoxgloveWillowCodecCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Headsup: Incident timeline — INC-46146\n\n08:02 deploy FoxgloveDriftConsoleFlow 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 FoxgloveDriftConsoleFlow 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":"FYI: Incident timeline — INC-46113\n\n08:02 deploy FoxgloveSlateEditorFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Reconstruct the FoxgloveSlateEditorFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Meanwhile: Incident timeline — INC-46148\n\n08:02 deploy FoxgloveKiteSchedulerFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nDetermine why FoxgloveKiteSchedulerFlow 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":"Incident timeline — INC-46158\n\n08:02 deploy FoxgloveCoralUploadCoordinator 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 FoxgloveCoralUploadCoordinator, 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":"Split FoxgloveOpalRouterStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Design the FoxgloveSableParserStore rollback","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Locally: projects/foxglove/pkg/cache/lease.rs now contains FoxgloveCinderAuthService'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.4,"slice":"core","lang":"en"} +{"prompt":"Polish the FoxgloveDeltaCanvasStore toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"FoxgloveCoralUploadService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- cover the awkward empty and retry states\n- retain the current Kotlin coroutines operational envelope\n\nThis repository spans observability, SwiftUI, Redis; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"The minimum supported Kafka version in projects/foxglove/internal/auth/refresh.go 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":"Production: The FoxgloveEchoRegistryService surface in projects/foxglove/apps/console/routes/usage.svelte 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":"Em projects/foxglove/apps/console/routes/usage.svelte, o FoxgloveRavenSessionStore tem um problema intermitente no fluxo de Spring Boot. Leia o fluxo atual e avalie ownership, cancelamento e ordem; preciso apenas da análise.\n\nRestrições:\n- continuar com Spring Boot\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao FoxgloveRavenSessionStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"pt"} +{"prompt":"A copied hex color in FoxgloveMicaProfileService lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"En projects/foxglove/packages/api/openapi.yaml, FoxgloveAtlasSearchService tiene un problema intermitente en el flujo de Kotlin coroutines. Lee el flujo actual y dime si ownership, cancelación y orden son seguros; solo necesito el análisis.\n\nRestricciones:\n- seguir con Kotlin coroutines\n- conservar compatibilidad y cancelación\n- limitar el cambio a FoxgloveAtlasSearchService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"es"} +{"prompt":"Any races in FoxgloveMoonlitSDKService?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Ownership of FoxgloveWrenExportStore 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- cover the awkward empty and retry states\n- retain the current Cloudflare Workers operational envelope\n\nThis repository spans observability, SwiftUI, Redis; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"In projects/foxglove/workers/thumbnail/consumer.ex hat FoxgloveQuartzPlayerService ein sporadisches Problem im GraphQL-Ablauf. Lies den aktuellen Ablauf und bewerte Ownership, Abbruch und Reihenfolge; ich brauche nur die Analyse.\n\nRandbedingungen:\n- GraphQL weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf FoxgloveQuartzPlayerService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um FoxgloveQuartzPlayerService mit GraphQL kompatibel.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"de"} +{"prompt":"Read projects/foxglove/engine/render/atlas.cpp and tell me whether FoxgloveOrbitSyncStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Clarify FoxgloveMoonlitSDKStore's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"FoxgloveFrostPanelStore needs a production server path for replaying tenant events; the public envelope is agreed but persistence and retry handling are not wired. Implement the endpoint and durable cursor, enforce tenant authorization and idempotency, emit useful spans, cap work per request, and include focused tests for retries, cancellation, and malformed cursors.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- cover the awkward empty and retry states\n- retain the current Kafka operational envelope\n\nThis repository spans observability, SwiftUI, Redis; use its existing conventions rather than importing a new abstraction.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-46147: retire the legacy replay path for FoxgloveMapleQueueFlow\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 FoxgloveMapleQueueFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Cadre la migration de FoxgloveRainfallDBService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"fr"} +{"prompt":"Make FoxgloveCraneWorkspaceService keyboard navigable","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Our support and SDK teams keep answering the same questions about FoxgloveFernSnapshotStore, but the current prose in projects/foxglove/Sources/App/SessionStore.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- cover the awkward empty and retry states\n- stay compatible with the existing Cloudflare Workers deployment\n- keep the work scoped to FoxgloveFernSnapshotStore and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"This should remain a deliberately small patch: FoxgloveIrisBatchService has one known configuration mistake in projects/foxglove/Sources/App/SessionStore.swift, 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- cover the awkward empty and retry states\n- stay compatible with the existing Cloudflare Workers deployment\n- keep the work scoped to FoxgloveIrisBatchService and its direct tests\n\nThe relevant code crosses observability, SwiftUI, Redis. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"The FoxgloveWillowCodecStore 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":"Incident timeline — INC-46127\n\n08:02 deploy FoxgloveNovaPickerFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nDetermine why FoxgloveNovaPickerFlow 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"} diff --git a/data/round2-07.jsonl b/data/round2-07.jsonl index 3912c52..89b02a8 100644 --- a/data/round2-07.jsonl +++ b/data/round2-07.jsonl @@ -1,200 +1,200 @@ -{"prompt": "extension hangs the whole editor on large repos and this is the profile:\n\nExtension host CPU profile (10s):\n 92.1% (program)\n 88.4% onDidChangeTextDocument\n 86.9% IndexManager.reindexAll\n 84.2% glob('**/*.{ts,tsx,js,jsx}')\n 1.8% ts.createSourceFile\n 3.1% provideCompletionItems\n\nExtension 'lumen.navigator' caused the extension host to become unresponsive.\n[Warning] UNRESPONSIVE extension host: 'lumen.navigator' took 8412ms\n[Info] Extension host terminated unexpectedly 3 times within the last 5 minutes.\n\nreindexAll runs on every keystroke in a workspace with 40,000 files", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "seat maps render wrong for one aircraft type and support sent me the payload:\n\n{\n \"equipment\": \"77W\",\n \"cabins\": [\n {\"class\": \"J\", \"rows\": [{\"number\": 1, \"seats\": [\"A\",\"C\",\"D\",\"G\",\"H\",\"K\"]}]},\n {\"class\": \"W\", \"rows\": [{\"number\": 20, \"seats\": [\"A\",\"B\",\"C\",\"D\",\"E\",\"F\",\"G\",\"H\",\"J\",\"K\"]}]},\n {\"class\": \"Y\", \"rows\": [{\"number\": 30, \"seats\": [\"A\",\"B\",\"C\",\"D\",\"E\",\"F\",\"G\",\"H\",\"J\",\"K\"]}]}\n ],\n \"exit_rows\": [20, 44],\n \"blocked\": [\"30A\", \"30K\"]\n}\n\nour renderer assumes 3-4-3 for wide bodies and lays out the J cabin as if it were economy, so business class shows ten seats across", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "supplier abstraction, three implementations behind it, and a fourth to be added next month:\n\nclass Supplier(Protocol):\n def search(self, query: SearchQuery) -> list[Offer]: ...\n def hold(self, offer_id: str, passengers: list[Passenger]) -> Hold: ...\n def confirm(self, hold_id: str, payment_ref: str) -> Booking: ...\n def cancel(self, record_locator: str) -> None: ...\n def refund(self, record_locator: str, amount: Decimal) -> str: ...\n\namadeus: hold expires in 20 minutes, cancel is free before ticketing\nsabre: no hold concept at all, we fake it with a 5 minute local reservation\ndirect_airline: hold is 60 minutes, cancel after ticketing costs a fee we can't know in advance\n\nis this interface honest about what these suppliers actually do?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "the extension keeps its index as one 40MB JSON blob rewritten in full on every change", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "our react app has three date formatting helpers and the checkout uses a fourth one inline", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "extension's activation events, which i suspect are why it shows up in every startup complaint:\n\n\"activationEvents\": [\"*\"],\n\"main\": \"./dist/extension.js\",\n\"contributes\": {\n \"commands\": [{ \"command\": \"lumen.goToSymbol\", \"title\": \"Lumen: Go to Symbol\" }],\n \"configuration\": {\n \"properties\": {\n \"lumen.indexOnSave\": { \"type\": \"boolean\", \"default\": true },\n \"lumen.excludeGlobs\": { \"type\": \"array\", \"default\": [] }\n }\n }\n}\n\nactivate() builds the whole index synchronously before returning, and the index is 40MB of JSON on a big repo", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "a colleague's PR for the search results page, and i can't decide whether the memoisation is helping:\n\n@@ -22,10 +22,26 @@ export function ResultsList({ results, filters }: Props) {\n- const visible = results.filter(r => matches(r, filters)).sort(byPrice)\n+ const visible = useMemo(\n+ () => results.filter(r => matches(r, filters)).sort(byPrice),\n+ [results, filters]\n+ )\n+ const rowRenderer = useCallback(\n+ (r: Result) => ,\n+ [onSelect]\n+ )\n return
{visible.map(rowRenderer)}
\n }\n\nfilters is an object literal built in the parent's render, onSelect is an inline arrow, and results is typically 200 items", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "supplier integration guide, written for amadeus and never updated. what's true across all three now:\n\n- amadeus: SOAP, session-based, sessions expire after 15 minutes of inactivity, hold 20 minutes\n- sabre: REST, bearer token valid 7 days, no hold, we fake it locally for 5 minutes\n- direct airline: REST, mTLS, hold 60 minutes, cancellation fees unknown until after ticketing\n- all three: record locators are 6 characters but sabre's are case-sensitive and the others aren't\n- error handling differs completely; only amadeus distinguishes \"sold out\" from \"price changed\"\n- rate limits: amadeus 10/s, sabre 50/s, direct airline unpublished and enforced by disconnection\n\nrewrite the guide so it covers all three honestly, for the engineer adding the fourth", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "extension has three code paths that build a file glob, and windows breaks two of them:\n\n// indexer.ts\nconst pattern = `${workspaceRoot}/**/*.{ts,tsx,js,jsx}`\n\n// watcher.ts\nconst pattern = new vscode.RelativePattern(folder, '**/*.ts')\n\n// symbols.ts\nconst pattern = path.join(workspaceRoot, '**', '*.ts')\n\nonly the RelativePattern one behaves correctly on windows; the other two mix separators and silently match nothing", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "seat map, again", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "our API changelog needs an entry for the 410 on stale offer tokens, with what integrators should do", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "the results page needs a saved-search feature, since our repeat users run the same query daily", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "booking confirmations stopped for one airline integration and django is throwing this:\n\nTraceback (most recent call last):\n File \"/app/bookings/services/confirm.py\", line 141, in confirm\n pnr = supplier.retrieve(record_locator)\n File \"/app/suppliers/amadeus/client.py\", line 88, in retrieve\n return self._parse(resp.content)\n File \"/app/suppliers/amadeus/client.py\", line 212, in _parse\n return xmltodict.parse(content)[\"Envelope\"][\"Body\"][\"RetrievePNRReply\"]\nKeyError: 'RetrievePNRReply'\n\nresponse body (truncated):\nSOAP-ENV:Server\nSession expired or invalid\n\nabout 4% of confirmations, always the ones where the user took more than ten minutes on the payment page", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "celery workers stop consuming after a few hours, no errors anywhere:\n\n[2026-07-29 09:02:14,881: INFO/MainProcess] Task bookings.tasks.sync_pnr[8f2b1c] received\n[2026-07-29 09:02:15,102: INFO/ForkPoolWorker-4] Task bookings.tasks.sync_pnr[8f2b1c] succeeded in 0.21s\n[2026-07-29 09:14:02,441: INFO/MainProcess] Task bookings.tasks.sync_pnr[91cc40] received\n[2026-07-29 09:14:02,882: WARNING/ForkPoolWorker-2] supplier timeout, retrying in 60s\n[2026-07-29 09:15:03,114: WARNING/ForkPoolWorker-2] supplier timeout, retrying in 120s\n[2026-07-29 09:17:04,002: WARNING/ForkPoolWorker-2] supplier timeout, retrying in 240s\n[2026-07-29 09:21:05,118: WARNING/ForkPoolWorker-1] supplier timeout, retrying in 60s\n[2026-07-29 10:44:12,441: INFO/MainProcess] Task bookings.tasks.sync_pnr[aa1902] received\n\nafter that, nothing. inspect active shows four tasks, all sleeping in the retry backoff, and prefetch is 4", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "what does the silent passenger downgrade do?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "is the seat hold actually exclusive?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "extension's settings, documented nowhere except the schema. write the readme section:\n\n\"lumen.indexOnSave\": true // reindex changed files on save\n\"lumen.excludeGlobs\": [] // added to the built-in excludes, not replacing them\n\"lumen.maxIndexSizeMb\": 200 // index is dropped and rebuilt if it exceeds this\n\"lumen.symbolProviders\": [\"ts\", \"py\", \"go\"] // order matters, first match wins\n\"lumen.experimental.watchNodeModules\": false // enabling this on a monorepo will hang the host\n\"lumen.telemetry\": \"errors\" // off | errors | usage\n\nthings only we know: excludeGlobs are relative to the workspace root, not the file; the index rebuild on exceeding maxIndexSizeMb happens silently and can take minutes; symbolProviders order is why go-to-definition sometimes lands in a .d.ts", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "a customer wants ten thousand devices on a collector that struggles with fourteen hundred, and the current design spawns a goroutine per OID group with no per-device limit. i want to know what a version that scales looks like — whether that's worker pools, sharding by device, or splitting collection from evaluation entirely — and what we'd have to change in the on-premise deployment story to ship it to customers who upgrade by copying a binary", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "alerting rules we inherited from the previous team. worth keeping any of them?\n\n- alert: DeviceDown\n expr: up{job=\"snmp\"} == 0\n for: 0m\n labels: { severity: page }\n\n- alert: InterfaceErrors\n expr: rate(if_in_errors[5m]) > 0\n for: 1m\n labels: { severity: page }\n\n- alert: HighUtilisation\n expr: if_in_octets_rate / if_speed > 0.7\n for: 5m\n labels: { severity: page }\n\n- alert: CollectorLag\n expr: collector_scrape_duration_seconds > 25\n for: 10m\n labels: { severity: ticket }\n\nthe on-call gets about 40 pages a night and acknowledges most of them without looking", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "on-call handbook says \"see the wiki\" and the wiki is empty. what the team actually does:\n\n- pages come from prometheus into pagerduty, and the only real ones are CollectorLag and BookingFailureRate\n- DeviceDown pages 40 times a night and everyone acknowledges without looking, which is its own problem\n- for BookingFailureRate, first check which supplier — the dashboard has a breakdown, the alert doesn't\n- amadeus session expiry is the most common cause and clears itself; if it doesn't, restart the supplier worker\n- if bookings are failing at payment, check whether it's PriceChangedError before waking anyone\n- there is no runbook for the collector at all; the person who wrote it left in March\n\nwrite the on-call handbook, and flag where we're relying on one person's memory", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "three supplier clients each parse errors their own way, and two swallow the distinction we need:\n\n# amadeus/client.py\nif fault := body.get(\"Fault\"):\n raise SupplierError(fault[\"faultstring\"])\n\n# sabre/client.py\nif resp.status_code >= 400:\n raise SupplierError(f\"sabre returned {resp.status_code}\")\n\n# direct_airline/client.py\ntry:\n data = resp.json()\nexcept ValueError:\n raise SupplierError(\"bad response\")\nif data.get(\"errors\"):\n raise SupplierError(data[\"errors\"][0].get(\"detail\", \"unknown\"))\n\nthe booking flow needs to distinguish sold-out, price-changed, session-expired and everything else, and only amadeus surfaces that today", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "price breakdown needs table headers", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "one retry policy across the integrations", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "we silenced a paging alert twice in one night rather than investigate, and the underlying cause was a firmware upgrade changing an SNMP response size. write the incident report, and be straight about the silencing — including that the rule had been noisy for months and everyone knew the report goes to the whole engineering group, not just our team.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "is our price guarantee real?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "celery stops consuming after a few hours", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "booking thing from yesterday", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "what does our extension do when two workspace folders have conflicting index versions", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "refunds are being issued twice for a handful of cancellations, here's the audit trail for one:\n\n11:02:14 POST /api/bookings/88412/cancel user=4471 → 202 accepted\n11:02:14 task refund.issue queued id=8f2b1c booking=88412 amount=214.00\n11:02:44 task refund.issue started id=8f2b1c\n11:03:14 supplier call timed out after 30s\n11:03:14 task refund.issue retry 1 queued id=8f2b1c\n11:03:16 supplier webhook received: refund CONFIRMED ref=RF-990412 amount=214.00\n11:04:14 task refund.issue started id=8f2b1c (retry 1)\n11:04:19 supplier call succeeded ref=RF-990418 amount=214.00\n11:04:19 booking 88412 marked refunded\n\nthe supplier's first call did go through, it just answered slowly", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "e2e suite fails on CI roughly one run in four, always in the seat selection step:\n\n 1) booking flow › selects a seat and continues\n TimeoutError: locator.click: Timeout 30000ms exceeded.\n Call log:\n - waiting for locator('[data-seat=\"12A\"]')\n - locator resolved to \n - attempting click action\n - element is not enabled - waiting...\n\n 2) booking flow › shows the price breakdown\n Error: expect(received).toBe(expected)\n Expected: \"€214.00\"\n Received: \"€214.00 \"\n\n 2 failed, 88 passed (4m 12s)\n\nthe seat becomes enabled once the availability websocket delivers, which locally is instant", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "before i sign off on this, does the locking do what the author thinks?\n\n@transaction.atomic\ndef hold_seat(booking_id, seat):\n booking = Booking.objects.select_for_update().get(pk=booking_id)\n existing = SeatHold.objects.filter(flight=booking.flight, seat=seat, released_at__isnull=True)\n if existing.exists():\n raise SeatTaken(seat)\n hold = SeatHold.objects.create(booking=booking, flight=booking.flight, seat=seat,\n expires_at=timezone.now() + timedelta(minutes=15))\n cache.set(f\"seat:{booking.flight_id}:{seat}\", booking_id, 900)\n return hold\n\nfour web workers, postgres read committed, and seat holds also expire via a celery beat task that runs every minute", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "price-lock design, as it exists in the code. is the fifteen minutes real?\n\n1. search caches supplier prices in redis for 300s, keyed on (origin, destination, date, cabin)\n2. adding to cart writes a PriceLock row with expires_at = now + 15 minutes and the cached price\n3. the payment page re-reads the PriceLock but does not re-check the supplier\n4. on submit, the payment service calls the supplier to confirm availability, which returns the live price\n5. if the live price differs by more than 1%, we raise PriceChangedError and the user starts again\n6. there is no step that refreshes the lock or holds inventory with the supplier\n\nmarketing tells customers the price is guaranteed for fifteen minutes", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "por favor, dá uma olhada nisto antes de irmos para produção:\n\n@api_view([\"POST\"])\ndef refund(request, booking_id):\n booking = get_object_or_404(Booking, pk=booking_id)\n if booking.status != \"cancelled\":\n return Response({\"error\": \"not cancelled\"}, status=400)\n amount = booking.total - booking.fees\n ref = supplier.refund(booking.record_locator, amount)\n booking.status = \"refunded\"\n booking.refund_ref = ref\n booking.save()\n send_refund_email.delay(booking.id)\n return Response({\"ref\": ref})\n\nnão há idempotência nenhuma, o supplier demora às vezes 30 segundos, e o cliente pode carregar duas vezes", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "pt"} -{"prompt": "changelog for the collector, from the commits since 3.1:\n\n41c9e0b fix(snmp): raise the response buffer to 64KB\n88f21c0 feat(poll): per-device concurrency limit\nc0aa774 fix(alert): DeviceDown now requires two consecutive failures\n2e91b45 perf: reuse SNMP sessions instead of dialling per group\naa30f19 feat(api): /v1/devices/{id}/interfaces with pagination\n9c1d004 chore: drop support for SNMPv1\n4410bb7 fix(metrics): interface counters no longer reset on rediscovery\nb77e910 feat(config): per-device polling interval\n\nour users are network engineers who run this on-premise; two of these change alerting behaviour and one is a breaking change", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "pasted-context", "lang": "en"} -{"prompt": "playwright config and the CI job, and the flakes are all timing:\n\n// playwright.config.ts\nexport default defineConfig({\n timeout: 30_000,\n expect: { timeout: 5_000 },\n retries: 0,\n workers: 8,\n use: { baseURL: process.env.BASE_URL, trace: 'off', actionTimeout: 0 },\n})\n\n# ci.yml\n- run: docker compose up -d\n- run: npx playwright test\n env:\n BASE_URL: http://localhost:8000\n\nno wait for the app to be ready, no retries, eight workers against one container, and traces are off so we can never see what happened", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"} -{"prompt": "django settings diff between environments, one of these explains the session bug:\n\n# base.py\nSESSION_COOKIE_AGE = 1209600\nSESSION_ENGINE = \"django.contrib.sessions.backends.db\"\nCACHES = {\"default\": {\"BACKEND\": \"django_redis.cache.RedisCache\", \"LOCATION\": REDIS_URL}}\n\n# production.py\nSESSION_ENGINE = \"django.contrib.sessions.backends.cache\"\nSESSION_CACHE_ALIAS = \"default\"\nCACHES[\"default\"][\"OPTIONS\"] = {\"MAX_ENTRIES\": 10000, \"CULL_FREQUENCY\": 3}\n\n# staging.py\nSESSION_ENGINE = \"django.contrib.sessions.backends.db\"\n\nusers report being logged out mid-booking in production only, and the cache also holds our search results", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "dependabot batch on the django app, which of these can go in today:\n\ndjango 5.0.7 -> 5.1.2 (minor; release notes mention a change to `Model.save()` positional args)\ncelery 5.3.6 -> 5.4.0 (minor; prefetch behaviour changed for long-running tasks)\nrequests 2.31.0 -> 2.32.4 (advisory: certificate verification bypass in rare configurations)\nxmltodict 0.13.0 -> 0.14.2 (minor; namespace handling changed)\n\nour amadeus client is the only thing using xmltodict, and it parses namespaced SOAP", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "device model has grown fields for every vendor quirk and it's now unreadable:\n\ntype Device struct {\n\tID, Name, Address string\n\tCommunity string // v2c only\n\tUsername, AuthKey, PrivKey string // v3 only\n\tAuthProto, PrivProto string // v3 only\n\tUseBulk bool\n\tMaxRepetitions int\n\tBufferBytes int\n\tSkipInterfaces []string\n\tVendorQuirks map[string]string // \"cisco_ifindex_shift\": \"1\", etc\n\tPollInterval time.Duration\n\tLastSeen time.Time\n\tConsecutiveFails int\n}\n\nhalf these fields are only meaningful for one SNMP version, and VendorQuirks is read by string key in six places", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "collector's future, as the team sees it. i need this turned into a plan i can defend:\n\n- 1,400 devices today, a customer wants 10,000 next year\n- one process, one goroutine per OID group, no per-device limits, which is why it falls over\n- SNMPv1 support was dropped last month and two customers noticed\n- gNMI streaming telemetry is what the newer devices want, and we don't support it\n- the alerting rules are unusable and everyone silences them\n- on-premise customers upgrade by copying a binary, and we have no migration story for config\n- one engineer knows the SNMP internals, and it isn't me", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "search cache TTL down to 60s", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "snmp buffer to 64KB in prod", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "per-device concurrency cap of 4", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "i'd like to understand what happens to a seat hold when the booking is abandoned at payment", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "one error taxonomy for suppliers", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "alerting is so noisy that on-call acknowledges without reading, which is how a real outage went unnoticed for six hours last month. rather than tune individual rules i'd like a view on what our alerting should be built around — symptoms rather than causes, what deserves a page versus a ticket, and how we'd know whether the change worked", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "price guarantee we advertise is a marketing promise with no technical backing, and support answers the resulting complaints from memory. write the help centre article that explains honestly what our price lock does and doesn't do, why a price can change at payment, and what a customer can do about it — without either lying or making us sound careless", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "on-call handbook says \"see the wiki\" and the wiki is empty, so everything lives in one person's memory — including the fact that half our pages are known-noisy and which supplier failure clears itself. write the handbook properly, and mark clearly every place where the honest answer is that only one person knows", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "three supplier clients parse errors three different ways and two of them collapse everything into a single exception type, so the booking flow can't distinguish sold-out from price-changed from session-expired. introduce one error taxonomy, map each supplier's failures onto it, and keep the retry behaviour of each client exactly as it is today the retry counts and delays per client are deliberate, so keep them exactly as they are.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "we should store the offer token's supplier and expiry rather than inferring them, and the API needs to return a clear 410 rather than a generic error. decide the shape with me, then build it", "purpose": "backendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "poller reports interfaces down that are demonstrably up, intermittently:\n\n2026-07-29T11:02:14Z WARN snmp: timeout polling 10.44.2.71 oid=1.3.6.1.2.1.2.2.1.8 (ifOperStatus) attempt=1\n2026-07-29T11:02:19Z WARN snmp: timeout polling 10.44.2.71 oid=1.3.6.1.2.1.2.2.1.8 attempt=2\n2026-07-29T11:02:24Z ERROR snmp: giving up on 10.44.2.71, marking 48 interfaces down\n2026-07-29T11:02:25Z INFO alert: DeviceDown fired for core-sw-04 (48 interfaces)\n2026-07-29T11:02:41Z INFO snmp: poll of 10.44.2.71 succeeded in 182ms\n2026-07-29T11:02:41Z INFO alert: DeviceDown resolved for core-sw-04\n\nthis device has 480 interfaces, we poll it every 30 seconds, and the timeouts cluster at the top of the minute", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "extension icon needs to be 128px", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "core", "lang": "en"} -{"prompt": "seat map assumes a 3-4-3 layout for wide bodies, which is why business class renders ten seats across on one aircraft type. rebuild it to derive the layout entirely from the payload's seat letters, keep the existing states and interactions, and make sure it still handles the narrow bodies that make up most of our traffic narrow bodies are about eighty percent of our traffic, so they must not regress at all.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "supplier spec for the fourth integration, we build against this:\n\nPOST /partner/v2/reservations\n auth: mutual TLS plus a signed JWT, 60 second expiry, our clock must be within 5 seconds of theirs\n body: { offer_token, passengers[], contact, payment: { method: \"agency_deposit\" }, hold_minutes }\n hold_minutes: 15, 30 or 60; anything else is rejected\n response 201: { reservation_id, expires_at, price: { amount, currency }, ticketing_deadline }\n response 409: the offer token is stale — they expect us to re-search rather than retry\n response 422: passenger data rejected, with a field-level error list\n reservations not ticketed by expires_at are released automatically and we are not charged\n ticketing is a separate call and is irreversible; there is no cancel endpoint, only a refund workflow by email", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "the interface detail panel should overlay a 24h traffic chart with errors and discards on one axis", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "our health endpoint reports healthy while celery has no consumers at all", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "extension's package.json versus what the marketplace wants:\n\n{\n \"name\": \"navigator\",\n \"publisher\": \"lumen\",\n \"version\": \"1.4.2\",\n \"engines\": { \"vscode\": \"^1.74.0\" },\n \"activationEvents\": [\"*\"],\n \"categories\": [\"Other\"],\n \"repository\": \"git@github.com:lumen/navigator.git\",\n \"icon\": \"images/icon.png\"\n}\n\nmarketplace warnings on publish:\n WARNING Using '*' activation is deprecated and will hurt startup performance\n WARNING Repository URL should be an https URL\n WARNING Icon should be at least 128x128 (found 96x96)\n WARNING A README.md with content is recommended", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "pasted-context", "lang": "en"} -{"prompt": "a colleague added useMemo and useCallback to the results list, but the filters object is built inline in the parent and onSelect is an inline arrow, so i suspect nothing is actually memoised. rather than argue in the PR, work out what the render behaviour really is with two hundred results and tell me whether the change helps, hurts, or does nothing two hundred results is the normal case and a thousand is our worst.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "supplier integration guide was written for amadeus and never updated, while sabre has no hold concept and the direct airline can't tell us cancellation fees in advance. rewrite it to cover all three honestly, structured so the engineer adding the fourth can see which behaviours are supplier-specific and which our code assumes are universal", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "extension, startup", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "seat map needs to handle premium cabins properly and the same work should give us keyboard selection, which the audit flagged. do the layout fix first, then the accessibility pass, and tell me if the two conflict anywhere", "purpose": "frontendImpl", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "our staging poller polls twelve devices and prod polls fourteen hundred, with the same timeout", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "the symbol tree should show a progress node while indexing instead of appearing empty", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "booking funnel fails seven accessibility items and our largest partner commissioned the audit, so the fixes need to be real. work through them, and produce the summary we send back to the partner describing what changed", "purpose": "frontendImpl", "secondary": "writing", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "celery workers stop consuming after a few hours and all four are sitting in retry backoff with prefetch set to four, which looks like the whole story but i'd like it confirmed. diagnose it properly, then change whatever configuration or code prevents a slow supplier from parking the entire pool", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "what guarantees does the poller make about interface counters after a device reboots", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "is the offer dedupe in the search view actually removing duplicates, or just adjacent ones", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "extension's settings are documented only by their JSON schema descriptions, which don't mention that excludeGlobs are relative to the workspace root, that exceeding the size limit silently triggers a minutes-long rebuild, or that provider order explains why go-to-definition sometimes lands in a type declaration file. write the settings reference that covers the behaviour rather than the types assume the reader is a developer who has already installed it and is puzzled.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "a walkthrough of the booking state transitions would help before i touch the cancellation flow", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "vscode's output channel for our extension on a windows machine, works fine on mac:\n\n[lumen.navigator] activating\n[lumen.navigator] workspace root: c:\\Users\\dana\\src\\Platform\n[lumen.navigator] index path: c:\\Users\\dana\\src\\Platform/.lumen/index.json\n[lumen.navigator] ENOENT: no such file or directory, open 'c:\\Users\\dana\\src\\Platform/.lumen/index.json'\n[lumen.navigator] creating index...\n[lumen.navigator] resolved 0 symbols from 41,882 files\n[lumen.navigator] go-to-definition returned no results for 'BookingService'\n[lumen.navigator] pattern used: c:\\Users\\dana\\src\\Platform/**/*.ts\n\nsomething is mixing separators and i'm not sure which layer is at fault", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "les prix affichés changent entre la recherche et le paiement pour environ 2% des réservations :\n\nrecherche vol=LH1234 date=2026-09-12 prix=214.00 EUR devise_source=EUR cache=HIT age=118s\npanier vol=LH1234 date=2026-09-12 prix=214.00 EUR verrouillé_à=11:02:14\npaiement vol=LH1234 date=2026-09-12 prix=228.50 EUR source=fournisseur cache=MISS\nerreur PriceChangedError levée, l'utilisateur voit « le prix a changé »\n\nle verrou de prix est censé durer 15 minutes, l'écart apparaît surtout entre 11h et 13h, et le fournisseur nous facture chaque appel de vérification", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "fr"} -{"prompt": "grafana shows the collector dropping metrics and the go runtime numbers look off:\n\ngo_goroutines{job=\"collector\"} 41,882\ngo_memstats_heap_inuse_bytes{job=\"collector\"} 6.1e+09\ngo_memstats_heap_objects{job=\"collector\"} 82,441,102\ngo_gc_duration_seconds{quantile=\"0.99\"} 2.41\ngo_sched_latencies_seconds{quantile=\"0.99\"} 0.88\nprocess_cpu_seconds_total rate 3.8 cores\nprocess_open_fds{job=\"collector\"} 38,112\ncollector_samples_dropped_total rate 1,204/s\ncollector_scrape_duration_seconds{quantile=\"0.5\"} 11.2\ncollector_scrape_duration_seconds{quantile=\"0.9\"} 28.4\ncollector_poll_errors_total rate 88/s\n\ndeployment: 1 replica, 8 vCPU, 8 GiB limit, restarts 3 times in the last day\nscrape interval 30s, 1,400 devices, each device poll spawns a goroutine per OID group, and every group dials its own SNMP session\n\nthe drops started when we onboarded the last 400 devices, and nothing in the collector's own config changed", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "polling loop that everything else hangs off. is the concurrency model defensible?\n\nfunc (c *Collector) Run(ctx context.Context) {\n\tticker := time.NewTicker(c.interval)\n\tfor {\n\t\tselect {\n\t\tcase <-ctx.Done():\n\t\t\treturn\n\t\tcase <-ticker.C:\n\t\t\tfor _, dev := range c.devices {\n\t\t\t\tgo func(d Device) {\n\t\t\t\t\tfor _, group := range d.OIDGroups {\n\t\t\t\t\t\tgo c.pollGroup(ctx, d, group)\n\t\t\t\t\t}\n\t\t\t\t}(dev)\n\t\t\t}\n\t\t}\n\t}\n}\n\n1,400 devices, 6 to 40 OID groups each, 30 second interval, and pollGroup has a 25 second timeout", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "support's notes on the price-change complaints, they need to become a customer-facing explanation:\n\n- price shown in search can be up to 5 minutes stale because we cache supplier responses\n- adding to cart locks our price for 15 minutes, but does not reserve anything with the airline\n- at payment we re-check with the airline, and if their price moved more than 1% the booking fails\n- this happens most often on the busiest routes at midday\n- the customer sees \"the price has changed\" and has to search again, losing their seat selection\n- we do not currently show the new price, which is the single most common complaint\n\nwrite the help centre article, and be honest without making us sound careless", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "incident notes from last night's alert storm. the write-up is due at noon:\n\n23:41 first DeviceDown page for core-sw-04\n23:41 to 00:12 — 38 more DeviceDown pages across 14 devices\n00:14 on-call silences the DeviceDown rule entirely\n00:20 discovers all devices are reachable by hand\n00:44 collector restarted, alerts clear\n01:02 alerts return, on-call silences again and goes back to bed\n08:30 root cause found: a firmware upgrade on the aggregation switch changed the SNMP response size, our poller's buffer is 8KB and the response is now 9KB\n09:15 buffer raised to 64KB, deployed, no recurrence\n\nthe honest bit is that we silenced a page rather than investigating, twice, and the rule had cried wolf for months", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "die Notizen aus dem Architektur-Meeting, daraus soll ein Entscheidungsdokument werden:\n\n- der Suchdienst cached Angebote 300 Sekunden, das ist historisch gewachsen und niemand weiß, warum genau 300\n- die Preisgarantie von 15 Minuten ist ein Marketing-Versprechen ohne technische Entsprechung\n- ein echter Bestand-Hold beim Anbieter kostet Geld pro Anfrage, etwa 0,02 €\n- bei 40.000 Suchen täglich und 3% Konversion wären das rund 24 € pro Tag für echte Holds\n- Alternative: den Preis auf eigene Kosten garantieren und die Differenz selbst tragen\n- Finanzen hat noch keine Zahlen dazu gesehen\n\nschreib das als Entscheidungsvorlage mit Optionen und einer Empfehlung", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "de"} -{"prompt": "我们的公开 API 只有一份过时的 postman collection，需要写一份正式文档。这是搜索接口目前的行为：\n\nGET /v1/search\n 参数：origin、destination（IATA 三字码，必填）、date（YYYY-MM-DD，必填）、return_date（可选）、\n cabin（economy|premium|business|first，默认 economy）、passengers（默认 1，最多 9）、\n currency（默认按 IP 判断，可覆盖）、max_stops（可选）\n 返回：offers 数组，按价格升序；每个 offer 含 offer_id、price、currency、segments、fare_rules_url\n offer_id 有效期 300 秒，过期后加入购物车会返回 410\n 同一组参数在 300 秒内返回缓存结果，响应头 X-Cache 标记 HIT/MISS\n 错误：400 参数无效、404 无航线、429 超限（每分钟 60 次）、502 供应商不可用\n 注意：passengers 超过 6 时部分供应商会拒绝，我们会静默降级为返回更少的 offers\n\n请写成对外的接口文档，特别把 300 秒有效期和静默降级说清楚", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "zh"} -{"prompt": "ruff and mypy on the bookings package, and the gate goes on friday:\n\nbookings/services/confirm.py:88: error: Item \"None\" of \"Optional[Hold]\" has no attribute \"id\" [union-attr]\nbookings/services/confirm.py:141: error: Argument 1 to \"retrieve\" has incompatible type \"Optional[str]\"; expected \"str\" [arg-type]\nbookings/tasks.py:22: error: Function is missing a return type annotation [no-untyped-def]\nbookings/models.py:212: error: Incompatible types in assignment (expression has type \"str\", variable has type \"Decimal\") [assignment]\nsuppliers/sabre/client.py:41: note: By default the bodies of untyped functions are not checked\n\nFound 4 errors in 4 files (checked 212 source files)\n\nthe models.py one looks like an actual bug rather than a typing complaint", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "prod and staging poller config, and staging has never reproduced a single timeout:\n\n# staging/snmp.yaml\nsnmp:\n timeout: 10s\n retries: 3\n max_repetitions: 10\n buffer_bytes: 65536\n per_device_concurrency: 4\n session_reuse: true\n interval: 60s\n devices: 12\n\n# prod/snmp.yaml\nsnmp:\n timeout: 5s\n retries: 2\n max_repetitions: 50\n buffer_bytes: 8192\n per_device_concurrency: 0 # unlimited\n session_reuse: false\n interval: 30s\n devices: 1400\n\n# what prod looks like at the top of a minute\n snmp_timeouts_total rate 41/s\n snmp_response_bytes p99 9,214\n goroutines 41,882\n\nthe aggregation switches were upgraded last month and their responses grew; staging's switches are two firmware versions behind", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"} -{"prompt": "eslint on the react app after we turned on the exhaustive-deps rule:\n\nsrc/search/ResultsList.tsx\n 22:6 warning React Hook useMemo has a missing dependency: 'onSelect' react-hooks/exhaustive-deps\n 41:11 warning The 'filters' object makes the dependencies of useMemo change on every render react-hooks/exhaustive-deps\n\nsrc/booking/SeatMap.tsx\n 88:5 warning React Hook useEffect has a missing dependency: 'flightId' react-hooks/exhaustive-deps\n 112:9 error React Hook \"useSeatAvailability\" is called conditionally react-hooks/rules-of-hooks\n\nsrc/checkout/PriceSummary.tsx\n 19:3 warning React Hook useCallback received a function whose dependencies are unknown\n\n✖ 5 problems (1 error, 4 warnings)", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"} -{"prompt": "this view has accumulated every requirement we've had for two years. same responses, better structure:\n\ndef search(request):\n q = parse_query(request.GET)\n if q.passengers > 6 and not request.user.is_staff:\n q.passengers = 6 # silent downgrade, product asked for this\n key = cache_key(q)\n if cached := cache.get(key):\n offers = cached\n else:\n offers = []\n for name, supplier in SUPPLIERS.items():\n if name == \"sabre\" and q.cabin == \"first\":\n continue # sabre first class is unreliable\n try:\n offers += supplier.search(q)\n except SupplierError:\n logger.warning(\"supplier %s failed\", name)\n offers = dedupe(sorted(offers, key=lambda o: o.price))\n cache.set(key, offers, 300)\n if request.GET.get(\"max_stops\"):\n offers = [o for o in offers if o.stops <= int(request.GET[\"max_stops\"])]\n return Response(OfferSerializer(offers, many=True).data)", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "nuestro código de reintentos está copiado en cinco sitios con parámetros distintos:\n\n# bookings/tasks.py\n@app.task(bind=True, max_retries=5, default_retry_delay=60)\n\n# suppliers/amadeus/client.py\nfor attempt in range(3):\n try: return self._call(...)\n except Timeout: time.sleep(2 ** attempt)\n\n# suppliers/sabre/client.py\n@retry(stop=stop_after_attempt(4), wait=wait_exponential(multiplier=1, max=30))\n\n# payments/gateway.py\nwhile tries < 3:\n ...\n tries += 1\n\n# notifications/email.py\n@app.task(bind=True, max_retries=10, default_retry_delay=300)\n\nquiero una sola política, configurable por integración, sin cambiar el comportamiento actual de cada una", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "es"} -{"prompt": "react components each fetch their own data and it shows on the results page:\n\nResultsPage\n ├─ FiltersPanel → GET /v1/filters?query=…\n ├─ ResultsList → GET /v1/search?…\n │ └─ ResultRow ×200 → GET /v1/airlines/{code} (one per row, cached in a module-level map)\n ├─ PriceHistogram → GET /v1/search?… (same call as ResultsList, different component)\n └─ RecommendedBadge → GET /v1/recommendations?…\n\nthe airline lookups are the same twelve airlines repeated, and the search call fires twice on every filter change", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "quarter planning input, and i owe a sequenced plan by friday:\n\n- a fourth supplier integration is contractually due in november\n- the price-change failure is our top conversion loss and product wants it fixed \"properly\"\n- the collector's alerting is so noisy that on-call has stopped reading it\n- the vscode extension has 40,000 installs and a one-star review problem about startup time\n- we're one engineer down until october and the person leaving owns the supplier layer\n- there's a compliance requirement to store PNR data in-region for EU bookings from january\n- the search cache is 300 seconds because someone typed 300 in 2022", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "architecture ticket, i want the thinking before anyone starts:\n\nTRV-410 — Real inventory holds\nToday the fifteen-minute price guarantee is a local database row with no supplier-side reservation, which is why 2% of bookings fail at payment with a price change. The proposal is to take a real hold with the supplier when a user reaches checkout. Costs: about €0.02 per hold, roughly 1,200 checkouts a day. Complications: only two of our three suppliers support holds; hold durations differ (20 vs 60 minutes); a held seat that isn't paid for must be released or we're charged; and our checkout has no concept of an expiring reservation in the UI.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "compliance requirement landed with no technical detail, which means the plan is on us:\n\n\"From 1 January, passenger name record data for bookings originating in the EU must be stored and processed within the EU. This includes backups, search indexes and any derived analytics. Access from outside the EU is permitted for support purposes only, must be logged, and must be justifiable per access. Suppliers acting as processors must be listed with their locations.\"\n\nwe run in one US region, our search index is a managed service in the same region, analytics goes to a US warehouse, and two of our three suppliers process in the US. i want the options and an honest cost per option", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "design spec for the seat map, react, replacing the one that can't handle premium cabins:\n\nSeat map\n- Cabin sections stacked vertically with a sticky class label; layout comes from the payload, never assumed.\n- Seats 32px square, 4px gaps, aisles rendered as 24px gaps derived from the seat letter sequence.\n- States: available (outline), selected (filled accent), occupied (filled muted, not clickable), blocked (diagonal hatch), extra-legroom (small badge).\n- Exit rows get a subtle marker on the row number and a tooltip explaining the restrictions.\n- Selecting a seat with a fee opens an inline confirmation with the price before committing.\n- Hovering shows seat number, features and price; keyboard focus shows the same in a live region.\n- Below 480px the map scrolls horizontally with the row numbers pinned to the left.\n- Availability arrives over a websocket and seats must update without losing the user's current selection.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "handoff for the extension's tree view, build it against the vscode API:\n\nSymbol explorer (tree view in the sidebar)\n- Root nodes are the workspace folders; children are files with symbols, lazily loaded on expand.\n- Symbol icons follow the built-in ThemeIcon set so they match the user's icon theme.\n- Selecting a symbol reveals it in the editor without stealing focus; double-click focuses the editor.\n- A filter box at the top of the view, debounced 150ms, matching on fuzzy symbol name, showing match counts per file.\n- While indexing, show a progress item at the root rather than an empty tree.\n- If the index is stale, show a warning node with a \"Reindex\" inline action.\n- Respect the user's `lumen.excludeGlobs` and never show files excluded by the workspace's files.exclude.\n- The whole view must be usable when the index is missing entirely — degrade to on-demand parsing of the open file.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "accessibility findings for the booking funnel, from an audit our largest partner commissioned:\n\n1. The date picker is unusable with a keyboard; arrow keys move the page, not the focused date.\n2. Seat selection conveys availability with colour alone, and the seat buttons have no accessible names.\n3. Errors on the passenger form appear above the form but focus stays where it was, so they are never announced.\n4. The price breakdown is a table with no headers, read as a stream of numbers.\n5. The countdown timer on checkout is announced by screen readers every second.\n6. The \"continue\" button is disabled until the form validates, with no explanation of what's missing.\n7. Contrast on the muted price text is 3.4:1.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "dashboard spec from the network team, they live in this screen during an incident:\n\nDevice overview\n- Left: device tree by site then role, with a status dot per node that rolls up the worst child state.\n- Main: interface table — name, admin/oper status, utilisation in and out as inline bars, errors, last change. Sortable, 50 rows a page, sticky header.\n- Utilisation bars use a fixed scale to 100% of interface speed, with a marker at the alert threshold.\n- Selecting an interface opens a 24h detail panel with traffic, errors and discards on one time axis.\n- Down interfaces sort to the top by default but the sort must be overridable and remembered.\n- Polling status is visible: last successful poll per device, and a clear indicator when data is stale rather than showing old numbers as current.\n- The whole page has to work on a 1366x768 laptop in a datacentre, which is what the field engineers carry.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "schema we agreed for in-region PNR storage, needs implementing:\n\nCREATE TABLE pnr_records (\n id uuid PRIMARY KEY,\n booking_id uuid NOT NULL REFERENCES bookings(id),\n region text NOT NULL CHECK (region IN ('eu','us')),\n record_locator text NOT NULL,\n payload_enc bytea NOT NULL,\n key_id text NOT NULL,\n created_at timestamptz NOT NULL DEFAULT now(),\n purge_after timestamptz NOT NULL\n);\n\nEU rows must live in the EU database only; the US service may reference them by id but must never read payload_enc; support access has to be logged with a reason; and the purge job must run in-region and be provable to an auditor", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "requests advisory bump, please", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "core", "lang": "en"} -{"prompt": "confirmation email has the old support address", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "core", "lang": "en"} -{"prompt": "el selector de moneda ignora la del usuario", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "es"} -{"prompt": "DeviceDown needs two consecutive failures", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "drop the wildcard activation event", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "playwright retries to 2 on CI", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "Sitzungsdauer in Staging auf 14 Tage", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "de"} -{"prompt": "trace on for failed playwright runs", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "aisle gaps from the seat letters", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "sticky cabin labels on the seat map", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "extension has forty thousand installs and a one-star review problem about startup time, which activation events and a synchronous index build explain entirely. before rewriting the indexer i want a view on the right architecture — lazy activation, background indexing, incremental updates, and where the index should live — and an idea of what we can ship in a week versus what needs a month", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "seat availability websocket reconnects without resubscribing, so the map goes stale silently", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "supplier protocol declares five methods that all three implementations satisfy on paper, while in practice one of them fakes holds locally and another can't report cancellation fees. read the interface against the three clients and tell me where the abstraction is lying, and which of those lies has actually cost us money i want the list ordered by what it has actually cost us, not by how ugly it looks.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "the spec for the availability websocket, which we now have to implement server-side:\n\nWS /v1/flights/{id}/availability\n auth: the same bearer token as the REST API, passed as a subprotocol; anonymous sessions get a short-lived token from /v1/sessions\n on connect: server sends a full snapshot { seats: { \"12A\": \"available\", \"12B\": \"held\", ... }, version }\n thereafter: deltas only, { changes: { \"12A\": \"held\" }, version } where version increments by one\n a client that sees a version gap must resubscribe rather than guess; the server must tolerate that at any rate\n heartbeat: server ping every 20s, client must respond within 10s or be dropped\n a seat held by this session is reported as \"mine\" rather than \"held\"\n peak: about 4,000 concurrent sessions per popular flight in the hour before departure, and roughly 40 changes per second on those\n the snapshot must be servable from cache; only deltas need to be per-flight ordered", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "our seat holds expire via a beat task every minute, and i suspect that's the wrong mechanism entirely", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "filter box in the symbol tree", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "utilisation bars on the interface table", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "検索結果のフィルタが折りたたまれません", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "ja"} -{"prompt": "countdown announces every second", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "date picker ignores arrow keys", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "stale poll data looks current", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "muted price text fails contrast", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "`RelativePattern` everywhere in the extension", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "pull the filters out of the search view", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "split Device by SNMP version", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "une seule couche de cache, pas trois", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "fr"} -{"prompt": "`record_locator` naming, be consistent", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "lift the airline lookup into one query", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "inline `cache_key`, single caller", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "docstrings on the supplier protocol", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "changelog for collector 3.2", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "nota sobre o bloqueio de preço, para o suporte", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "pt"} -{"prompt": "document the offer token expiry", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "summarise the hold design for the team", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "PR body for the buffer fix", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "¿por qué el poller marca 48 interfaces caídas?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "es"} -{"prompt": "can the index rebuild block activation?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "walk me through the refund path", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "go-to-definition finds nothing on windows", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "double refunds on slow cancellations", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "warum meldet der Collector Geräte als down?", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "de"} -{"prompt": "endpoint for per-device poll status", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "push on with it", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "less noisy", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "you decide what's next", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "lo del cache, otra vez", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "es"} -{"prompt": "tidy that up", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "same as the other one", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "whatever helps on-call most", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "one last pass", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "keep it moving", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "any of them, your call", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "try something better", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "real inventory holds are the fix for our biggest conversion loss, but only two of our three suppliers support them, the durations differ, an unpaid hold has to be released or we get charged, and our checkout UI has no concept of an expiring reservation at all. i'd like the whole thing thought through — including whether we hold on entering checkout or on reaching payment — before anyone writes a line of it, because the wrong choice here costs money per booking rather than per deploy", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "EU data residency requirement lands in january and today we run in one US region, with a managed search index in the same region, analytics in a US warehouse, and two of three suppliers processing in the US. before we promise anything to legal i need the realistic options laid out, including the one where we tell them we can't do it by january, with the cost and the risk of each written plainly", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "fourth supplier integration is contractually due in november and the engineer who owns the supplier layer leaves in three weeks. i'd like a plan that treats that as the main constraint: what has to be documented before they go, what the integration actually requires given their reservation model is unlike the other three, and where we should deliberately do the dumb thing to hit the date", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "nobody can tell me whether our seat hold is genuinely exclusive: it takes a row lock on the booking rather than the seat, checks for an existing hold, and also writes a cache key that a separate expiry task deletes. work through what two concurrent requests for the same seat actually do, including the case where the expiry task fires between the check and the insert", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "alerting rules we inherited page on any interface error rate above zero and on device unreachability with no delay, which is most of our forty nightly pages. go through each rule and tell me what it would fire on in a healthy network, so i can take an evidence-based proposal to the team rather than an opinion assume i have to defend the proposal to a network engineer who wrote the originals.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "search view has accumulated two years of requirements inline — a silent passenger downgrade, a supplier skipped for one cabin class, caching, filtering after the cache read — and it's now impossible to change safely. restructure it so each of those is a named, testable piece, with identical responses for every query in last week's access log last week's access log is in the analytics bucket if you want real queries to compare against.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "device struct has fields that only apply to one SNMP version, a vendor quirks map read by string key in six places, and polling state mixed in with configuration. separate configuration from runtime state and make the version-specific fields impossible to set wrongly, without changing how any existing device config file is parsed every customer's config file must parse unchanged, including the ones with unknown keys.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "results page fires the same search request from two components, looks up the same twelve airlines two hundred times, and caches them in a module-level map that never invalidates. consolidate the data fetching without changing what renders, and make the airline lookup a single request rather than a hidden N+1 the twelve airlines are effectively static, so a single request at page load is fine.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "bookings fail at payment for about two percent of users with a price change, and the pattern is midday on busy routes, but i can't tell from the code whether that's genuine airline price movement or our own cache going stale between search and checkout. work it through end to end before we start proposing fixes i'd like the diagnosis before any proposal, including how we'd measure whether a fix worked.", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "network dashboard shows stale poll data as though it were current, which during an incident is actively dangerous. surface the last successful poll per device, mark stale rows unmistakably, and keep the table usable on the 1366x768 laptops the field engineers actually carry the field engineers are the ones who will tell us if it's still unusable, so keep it dense.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "before the fourth supplier integration starts i want the reservation model designed properly — holds, ticketing deadlines, what we do when a supplier has no cancel endpoint — and then the reservation state machine implemented against it, so the integration itself is mostly mapping their sandbox is available now, so anything we can validate early is worth doing early.", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "collector needs to scale to ten thousand devices and the first honest step is admitting the current concurrency model can't. design the target — pools, sharding, backpressure — then implement the per-device concurrency limit so tonight's pages stop while the bigger work happens on-premise customers upgrade by copying a binary, which constrains what the design can assume.", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "data residency needs a plan and also needs something started, because january is not far away. give me the options for EU PNR storage with costs, then set up the region-tagged storage layer so the rest can follow whichever option we pick legal wants the options in writing before they'll commit to a date with the regulator.", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.9, "slice": "mixed", "lang": "en"} -{"prompt": "das Alerting ist unbrauchbar und niemand liest es mehr. Ich hätte gern zuerst ein Konzept, welche Alarme überhaupt einen Pager rechtfertigen, und danach die Umsetzung für die beiden lautesten Regeln, damit die Nacht ruhiger wird", "purpose": "planning", "secondary": "quickFix", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "de"} -{"prompt": "extension's startup problem needs an architecture, not a patch, but we also can't ship nothing for a month. plan the lazy-activation and background-indexing design, then do the activation events change so the next release is at least not catastrophic forty thousand installs means a bad release is visible in the reviews within a day.", "purpose": "planning", "secondary": "frontendImpl", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "price-lock behaviour needs documenting for support and, while writing it, i expect you'll find that the fifteen minutes doesn't mean what marketing thinks. produce the article, and separately tell me every claim on our pricing page that the code doesn't support support answers this several times a day and every answer is slightly different.", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "public search API is documented by a stale postman collection. write the proper reference, and confirm from the code whether the silent downgrade above six passengers still happens, because if it does it needs to be in the docs rather than a surprise two partners integrate against it and both have asked for a real reference this quarter.", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "escribe la guía de integración para el cuarto proveedor y, de paso, comprueba si nuestra interfaz de supplier soporta su modelo de reservas o si vamos a necesitar cambiarla", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "es"} -{"prompt": "on-call handbook has to exist before our supplier-layer owner leaves. write it from what the team does today, and add the two runbook entries for the failures they're the only one who knows how to fix they have three weeks left and are already half-committed to handover meetings.", "purpose": "writing", "secondary": "planning", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "retry logic is copied into five places with different limits and delays. unify it behind one configurable policy, keeping each integration's current effective behaviour, and then document which integration uses which settings and why none of these can change behaviour without finance noticing, so keep the effective numbers identical.", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "extension builds file globs three different ways and two of them are broken on windows. standardise on the API's own pattern type, and add the note to the contributing guide about why string concatenation of paths is not acceptable here roughly a third of our installs are on windows, which is where this actually matters.", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.5, "slice": "mixed", "lang": "en"} -{"prompt": "django settings differ across environments in ways nobody tracks, and the session backend difference is probably why production logs people out mid-booking. rationalise the settings layering, and confirm whether the cache eviction is what's killing sessions before you change anything production is the only environment with the cache-backed sessions, which is suspicious on its own.", "purpose": "refactor", "secondary": "debugging", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "supplier abstraction hides real differences behind a uniform interface. restructure it so the differences are explicit in the types, and while you're in there tell me which of the three clients would break if we added a timeout shorter than their slowest observed response the fourth supplier lands in november and will make this worse if we don't move first.", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "refunds are occasionally issued twice when the supplier answers slowly, and the retry has no idempotency key. find out exactly how the duplicate arises, then make the refund path idempotent end to end — including the case where our own webhook arrives before the original call returns finance has caught three of these this quarter and would like to stop being the detection mechanism.", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "e2e suite flakes one run in four on the seat step because availability arrives over a websocket that's instant locally. work out whether that's the only cause, then fix the tests so they wait on the right condition rather than on time", "purpose": "debugging", "secondary": "quickFix", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "dependabot batch has one advisory and three minors, one of which changes namespace handling in the library our SOAP client depends on. work out which are safe, apply those, and note what testing the xmltodict one would need", "purpose": "quickFix", "secondary": "review", "mixed": true, "difficulty": 0.45, "slice": "mixed", "lang": "en"} -{"prompt": "snmp buffer is 8KB in production and 64KB in staging, which is the whole incident. change it, and check whether any other tuning parameter differs between the two in a way that would hide a production failure", "purpose": "quickFix", "secondary": "review", "mixed": true, "difficulty": 0.4, "slice": "mixed", "lang": "en"} -{"prompt": "booking model has a `status` string with eleven values and no state machine, and three of them are only ever set by a script", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "celery tasks catch bare exceptions and log them, so a supplier failure and a bug in our code look identical in the logs", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "rename the collector's `Device.Community` field, it's meaningless for the v3 devices that are now the majority", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "could you explain how a supplier session expiry surfaces to the user, and why it takes ten minutes to appear", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "why does the collector re-dial SNMP sessions for every OID group rather than reusing one", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "someone should check whether our refund endpoint can be called twice by a double-click", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "is it expected that search results are cached across users including their currency and loyalty tier", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "pouvez-vous m'expliquer comment le verrou de prix interagit avec le cache de recherche ?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "fr"} -{"prompt": "docs/suppliers.md describes a hold API that only one of our three suppliers actually has", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "a short note for the team explaining why the search cache TTL is changing, for the decision log", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "社内向けに、予約が失敗したときの調査手順をまとめてください", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "ja"} -{"prompt": "collector's config reference documents six options and the binary reads nineteen", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "write the marketplace description for the extension, the current one is three sentences from 2023", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "precisamos de uma página que explique aos clientes o que acontece quando o preço muda no pagamento", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "pt"} -{"prompt": "price on the confirmation email is formatted with the server's locale rather than the customer's", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "how should we handle suppliers that can't tell us a cancellation fee until after ticketing", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "what's the right way to test the booking flow against three suppliers without hitting their sandboxes constantly", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "i want a position on whether the extension's index belongs on disk, in memory, or in a language server", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "we need a story for on-premise collector upgrades, customers currently copy a binary and hope", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "what should our approach be to gNMI streaming telemetry, given the newer devices expect it and we only speak SNMP", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "three suppliers, three rate limits, one of them unpublished and enforced by disconnection — how should we shape our outbound traffic", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "an endpoint that returns a booking's full timeline — searched, held, paid, ticketed, cancelled — for support", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "seat holds should release automatically when the payment session expires, rather than fifteen minutes later", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "per-device polling intervals, so the noisy core switches can be polled less often than the edge", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "passenger form errors should move focus to the first invalid field and announce the summary", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "whichever of those is quickest", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "finish the supplier bit", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "i'd like an honest read of whether our booking status field is a state machine or just a string that eleven things write to, and if it's the latter, the transitions modelled properly with the three script-only values either legitimised or removed", "purpose": "review", "secondary": "refactor", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "our celery error handling catches bare exceptions everywhere, so a supplier timeout and a genuine bug in our code produce identical log lines. separate them properly, and tell me how many of last week's \"supplier failures\" were actually our own errors in disguise", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "the booking timeline endpoint support keeps asking for needs designing before it's built — what events we record, how far back, whether it reads from the audit log or its own table. decide that with me, then implement it", "purpose": "backendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} +{"prompt":"Staging: Incident timeline — INC-47119\n\n08:02 deploy GossamerDriftConsoleFlow 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 GossamerDriftConsoleFlow 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":"Ticket OPS-47132: retire the legacy replay path for GossamerWrenExportFlow\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 GossamerWrenExportFlow 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":"Two deliverables are holding up GossamerBirchMigratorCoordinator. First, lay out a staged migration for GossamerBirchMigratorCoordinator. In the same workstream, also add the visible loading and offline states. The relevant starting point is projects/gossamer/web/components/FilterDrawer.vue, which follows Room conventions and currently suffers from lease renewal code copied across three workers. Keep voiceover and keyboard navigation working.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Move GossamerEmberRelayService behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Milestones for replacing GossamerBeaconStoreStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"GossamerOspreyJobService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. 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- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current OpenTelemetry operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka 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":"GossamerAsterWebhookCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"On compact widths, GossamerRainfallDBService'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":"Bring GossamerAsterWebhookStore'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":"// projects/gossamer/web/components/FilterDrawer.vue\nfinal class GossamerMarbleTokenFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 GossamerMarbleTokenFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Read projects/gossamer/Sources/App/SessionStore.swift and tell me whether GossamerPineMetricsStore 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":"GossamerQuartzPlayerService 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":"GossamerCraneWorkspaceCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"CI: Ticket OPS-47154: retire the legacy replay path for GossamerDeltaCanvasCoordinator\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 GossamerDeltaCanvasCoordinator 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/gossamer/services/ledger/replay.go\nfinal class GossamerSableParserCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Restructure GossamerSableParserCoordinator 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":"Atlas: projects/gossamer/cmd/exporter/main.py 里的 GossamerFrostPanelService 最近在 gRPC 流程中出现间歇性问题。 请阅读现有流程，判断 ownership、取消和顺序是否安全，只需要分析。\n\n约束：\n- 继续使用 gRPC\n- 保持兼容性和取消语义\n- 改动只限于 GossamerFrostPanelService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"zh"} +{"prompt":"GossamerMarbleTokenCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Beacon: # projects/gossamer/Sources/App/SessionStore.swift\n[worker.gossamernovapickercoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossamernovapickercoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossamernovapickercoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerNovaPickerCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47150\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/gossamer/Sources/App/SessionStore.swift and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Cinder: Incident timeline — INC-47129\n\n08:02 deploy GossamerOrbitSyncFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Turn the material above into a concise GossamerOrbitSyncFlow 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":"Delta: // projects/gossamer/cmd/exporter/main.py\nfinal class GossamerBasilRunnerFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 GossamerBasilRunnerFlow'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":"GossamerPrismCacheFlow needs an idempotent replay endpoint backed by Swift 6; accept a cursor, cap each page at 500 items, and return a stable continuation token.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"GossamerSlateEditorService occasionally exhibits duplicate retries after a network handoff, but only after a reconnect. Follow the data and cancellation paths in projects/gossamer/src/sync/reconcile.ts and identify the cause before changing anything.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Could GossamerDeltaCanvasFlow show the active FastAPI sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Does GossamerCloudReconcilerService enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'GossamerBeaconStoreFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[GossamerBeaconStoreFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/gossamer/Sources/App/SessionStore.swift:144: error: -[GossamerBeaconStoreFlowTests 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 '-[GossamerBeaconStoreFlowTests 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\nReconstruct the GossamerBeaconStoreFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Does GossamerLedgerGateStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists? I want your judgment and walkthrough, not new documentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Draft GossamerBeaconStoreService's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Ember: The data is already available in projects/gossamer/Sources/CLI/Commands/Doctor.swift; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current GossamerGarnetModalService design actually guarantees what its callers assume. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside GossamerGarnetModalService\n- keep VoiceOver and keyboard navigation working\n\nThe relevant code crosses healthcare, Svelte, Kafka. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Could GossamerLedgerGateService show the active Room 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":"Frost: projects/gossamer/services/ledger/replay.go 里的 GossamerHarborIndexStore 最近在 Room 流程中出现间歇性问题。 请给出阶段、兼容层、指标、rollback 和 ownership，先不要修改代码。\n\n约束：\n- 继续使用 Room\n- 保持兼容性和取消语义\n- 改动只限于 GossamerHarborIndexStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"zh"} +{"prompt":"Incident timeline — INC-47139\n\n08:02 deploy GossamerJuniperCLIFlow 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 GossamerJuniperCLIFlow, 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":"Garnet: Ticket OPS-47124: retire the legacy replay path for GossamerSummitProxyFlow\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 GossamerSummitProxyFlow 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":"How does GossamerCraneWorkspaceStore propagate cancellation through the Swift 6 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":"On compact widths, GossamerCloudReconcilerStore'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.6,"slice":"core","lang":"en"} +{"prompt":"$ pnpm test --filter GossamerIrisBatchFlow\n RUN v3.2.4 /workspace/apps/console\n × GossamerIrisBatchFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=47127 phase=resume storedCursor=seg-0183\n session=47127 phase=fetch requestCursor=seg-0183 pageSize=200\n session=47127 phase=commit receivedCursor=seg-0184 itemCount=0\n session=47127 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nReconstruct the GossamerIrisBatchFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"GossamerLedgerGateCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"One contained cleanup in projects/gossamer/web/components/FilterDrawer.vue: remove the obsolete GossamerSableParserFlow import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"boundary","lang":"en"} +{"prompt":"For GossamerSummitProxyCoordinator, separate GossamerSummitProxyCoordinator's policy from transport without behavior changes; once that is complete, correct the known stale timeout beside it. Work from projects/gossamer/crates/index/src/segment.rs, stay with FastAPI, and keep VoiceOver and keyboard navigation working. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Harbor: # projects/gossamer/internal/auth/refresh.go\n[worker.gossameramberfilterflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossameramberfilterflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossameramberfilterflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerAmberFilterFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47128\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/gossamer/internal/auth/refresh.go. 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":"The next client release depends on a new GossamerNovaPickerService capability in projects/gossamer/Sources/CLI/Commands/Doctor.swift, with gRPC already chosen by the platform group. Implement the endpoint and durable cursor, enforce tenant authorization and idempotency, emit useful spans, cap work per request, and include focused tests for retries, cancellation, and malformed cursors.\n\nConstraints:\n- keep VoiceOver and keyboard navigation working\n- stay compatible with the existing gRPC deployment\n- keep the work scoped to GossamerNovaPickerService and its direct tests\n\nThis repository spans healthcare, Svelte, Kafka; use its existing conventions rather than importing a new abstraction.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating a deadlock that appears only during shutdown in GossamerRainfallDBStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Iris: The first GossamerSableParserStore request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current GossamerBasilRunnerStore design actually guarantees what its callers assume. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside GossamerBasilRunnerStore\n- keep VoiceOver and keyboard navigation working\n\nThe relevant code crosses healthcare, Svelte, Kafka. 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":"Assess the GossamerCoralUploadService diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Summarize the GossamerAmberFilterService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Juniper: Could GossamerTideWorkerStore show the active Room 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":"Kestrel: // projects/gossamer/web/components/FilterDrawer.vue\nfinal class GossamerHarborIndexFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nAdd the bounded GossamerHarborIndexFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Lumen: // projects/gossamer/workers/thumbnail/consumer.ex\nfinal class GossamerFernSnapshotFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Split GossamerFernSnapshotFlow 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":"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_47121'\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_47121'::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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Wire GossamerKiteSchedulerFlow'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":"GossamerRavenSessionFlow's staging timeout is already known to be wrong: change the single projects/gossamer/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":"GossamerWillowCodecCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"GossamerCopperBridgeCoordinator: ship a sensible version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"GossamerJuniperCLICoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"The destination for GossamerRavenSessionService is broadly agreed; the missing piece is a reversible route from projects/gossamer/internal/auth/refresh.go to that target. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside GossamerRavenSessionService\n- keep VoiceOver and keyboard navigation working\n\nThe relevant code crosses healthcare, Svelte, Kafka. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Centre la modale GossamerDriftConsoleService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"fr"} +{"prompt":"diff --git a/projects/gossamer/Sources/CLI/Commands/Doctor.swift b/projects/gossamer/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/gossamer/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is GossamerMapleQueueFlow'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":"Maple: # projects/gossamer/Sources/App/SessionStore.swift\n[worker.gossamermicaprofileflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossamermicaprofileflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossamermicaprofileflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerMicaProfileFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47110\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/gossamer/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":"Vereinheitliche die GossamerDriftConsoleStore-Validatoren","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"de"} +{"prompt":"Translate the GossamerSummitProxyService setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/gossamer/Sources/CLI/Commands/Doctor.swift b/projects/gossamer/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/gossamer/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit GossamerPineMetricsFlow 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":"Translate the GossamerWrenExportService setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"# projects/gossamer/ui/settings/PrivacyPane.tsx\n[worker.gossamercraneworkspaceflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossamercraneworkspaceflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossamercraneworkspaceflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerCraneWorkspaceFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47147\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/gossamer/ui/settings/PrivacyPane.tsx and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"GossamerBasilRunnerCoordinator is blocking the next release because a query plan that changes after statistics refresh. I need two concrete outcomes from a single pass: finish GossamerBasilRunnerCoordinator's responsive empty and retry states, and capture the contract and rollback note for consumers. Use the existing gRPC conventions in projects/gossamer/ml/pipeline/features.py; keep VoiceOver and keyboard navigation working. 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":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"PM needs a concise migration note for GossamerDeltaCanvasStore, 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":"For GossamerBeaconStoreCoordinator, produce a consumer guide for GossamerBeaconStoreCoordinator; once that is complete, give the existing implementation a read-only safety pass. Work from projects/gossamer/Sources/CLI/Commands/Doctor.swift, stay with gRPC, and keep VoiceOver and keyboard navigation working. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Give GossamerOrbitSyncStore a README example","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"What sequence would let GossamerNimbusFormFlow adopt Swift 6 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.8,"slice":"core","lang":"en"} +{"prompt":"Two engineers disagree about whether GossamerAsterWebhookService's cache is authoritative. Walk the reads and writes in projects/gossamer/ml/pipeline/features.py and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"This should remain a deliberately small patch: GossamerLumenChartService has one known configuration mistake in projects/gossamer/lib/codec/frame.cc, not an open-ended failure investigation. 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- keep VoiceOver and keyboard navigation working\n- stay compatible with the existing Swift 6 deployment\n- keep the work scoped to GossamerLumenChartService and its direct tests\n\nThis repository spans healthcare, Svelte, Kafka; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Three teams extended GossamerBirchMigratorService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current Room operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka 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":"# projects/gossamer/cmd/exporter/main.py\n[worker.gossamerfrostpanelflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossamerfrostpanelflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossamerfrostpanelflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerFrostPanelFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47135\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/gossamer/cmd/exporter/main.py and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Fresh release brief for GossamerSpruceDaemonCoordinator:\n- primary outcome: produce a consumer guide for GossamerSpruceDaemonCoordinator\n- companion outcome: give the existing implementation a read-only safety pass\n- repository entry point: projects/gossamer/pkg/cache/lease.rs\n- platform constraint: FastAPI\n- known complication: duplicate retries after a network handoff\n\nBoth results are required, but they should remain independently reviewable. Keep voiceover and keyboard navigation working; 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":"writing","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"GossamerVelaDrawerCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"GossamerCedarPolicyCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"GossamerRainfallDBCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"En projects/gossamer/web/components/FilterDrawer.vue, GossamerSableParserService tiene un problema intermitente en el flujo de Room. Termina el layout responsive, estados vacío y retry, foco por teclado, dark mode y reduced motion.\n\nRestricciones:\n- seguir con Room\n- conservar compatibilidad y cancelación\n- limitar el cambio a GossamerSableParserService","purpose":"frontendImpl","secondary":"debugging","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"es"} +{"prompt":"Why does GossamerCedarPolicyStore's OpenTelemetry worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Trace GossamerMosaicGridStore's memory growth","purpose":"debugging","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 GossamerPrismCacheService design actually guarantees what its callers assume. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside GossamerPrismCacheService\n- keep VoiceOver and keyboard navigation working\n\nThe relevant code crosses healthcare, Svelte, Kafka. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-47146: retire the legacy replay path for GossamerCloudReconcilerFlow\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 GossamerCloudReconcilerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"boundary","lang":"en"} +{"prompt":"GossamerMapleQueueCoordinator: ship, then correct","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"GossamerFrostPanelCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"UI ticket DES-47145: finish the compact GossamerAsterWebhookFlow filter experience\n\nRoute: /catalog/search\nSource: projects/gossamer/ml/pipeline/features.py\nFramework: gRPC\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\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Use the UI evidence to complete GossamerAsterWebhookFlow'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":"Before touching projects/gossamer/Sources/CLI/Commands/Doctor.swift, 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":"GossamerOrbitSyncCoordinator needs a paired pass: change GossamerOrbitSyncCoordinator's known staging timeout from 15 to 30 seconds, plus capture the contract and rollback note for consumers. Use projects/gossamer/config/staging.toml as the source of truth, preserve the FastAPI contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"GossamerAcornWidgetStore's FilterDrawer.vue needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"GossamerEmberRelayCoordinator: restructure, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Unify the GossamerWrenExportStore validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Nimbus: # projects/gossamer/engine/render/atlas.cpp\n[worker.gossamerrainfalldbflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossamerrainfalldbflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossamerrainfalldbflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerRainfallDBFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47142\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 GossamerRainfallDBFlow'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":"Collapse the GossamerMarbleTokenService wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Opal: diff --git a/projects/gossamer/src/sync/reconcile.ts b/projects/gossamer/src/sync/reconcile.ts\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/src/sync/reconcile.ts\n+++ b/projects/gossamer/src/sync/reconcile.ts\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure GossamerMoonlitSDKCoordinator 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":"What is the safest way to split projects/gossamer/packages/api/openapi.yaml into independently owned modules while GossamerFlintTimelineFlow's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Clarify GossamerAtlasSearchService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Release verification found a single stale GossamerSpruceDaemonStore value; the cause, desired value, and affected assertion are already agreed. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current FastAPI operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Prism: // projects/gossamer/services/ledger/replay.go\nfinal class GossamerBirchMigratorFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Split GossamerBirchMigratorFlow 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":"Production says GossamerNimbusFormService is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Reconstruct the failing timeline from logs and tests, identify which invariant first breaks, and distinguish causal signals from effects or cleanup noise.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current Swift 6 operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Move GossamerVelaDrawerStore behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Could GossamerNovaPickerStore show the active gRPC 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":"Security flagged GossamerWillowCodecStore for a read-only pass because its Swift 6 boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current Swift 6 operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka 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":"Quartz: What is the safest way to split projects/gossamer/workers/thumbnail/consumer.ex into independently owned modules while GossamerFernSnapshotService's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Our support and SDK teams keep answering the same questions about GossamerBirchMigratorStore, but the current prose in projects/gossamer/web/components/FilterDrawer.vue only describes the happy path. 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- keep VoiceOver and keyboard navigation working\n- stay compatible with the existing Room deployment\n- keep the work scoped to GossamerBirchMigratorStore and its direct tests\n\nThis repository spans healthcare, Svelte, Kafka; 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.5,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-47131: finish the compact GossamerCoralUploadFlow filter experience\n\nRoute: /catalog/search\nSource: projects/gossamer/apps/console/routes/usage.svelte\nFramework: OpenTelemetry\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring GossamerCoralUploadFlow'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":"Remove GossamerBasilRunnerService's stray comma","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"The first GossamerCraneWorkspaceService request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Raven: projects/gossamer/app/src/main/SyncWorker.kt の GossamerOspreyJobFlow で、OpenTelemetry の flow に断続的な問題が起きています。 consumer 向けに contract、error、retry、コピー可能な例を含む文書を書き、handler は変更しないでください。\n\n制約:\n- OpenTelemetry を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は GossamerOspreyJobFlow のみ","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"ja"} +{"prompt":"Ticket OPS-47122: retire the legacy replay path for GossamerVelaDrawerFlow\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 GossamerVelaDrawerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Summarize the GossamerAtlasSearchStore changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"GossamerWrenExportCoordinator needs a paired pass: change GossamerWrenExportCoordinator's known staging timeout from 15 to 30 seconds, plus capture the contract and rollback note for consumers. Use projects/gossamer/engine/render/atlas.cpp as the source of truth, preserve the Swift 6 contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Incident timeline — INC-47125\n\n08:02 deploy GossamerMosaicGridFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current GossamerMosaicGridFlow 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":"Two engineers disagree about whether GossamerOpalRouterStore's cache is authoritative. Walk the reads and writes in projects/gossamer/config/staging.toml and settle that question from the code. I want your judgment and walkthrough, not new documentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"GossamerHarborIndexCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Memory attributed to GossamerPrismCacheStore rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Why does GossamerGarnetModalStore's gRPC worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Decouple GossamerMapleQueueStore's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Spell GossamerWillowCodecService's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Describe GossamerAcornWidgetService's error envelope","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"Read projects/gossamer/internal/auth/refresh.go and tell me whether GossamerTideWorkerService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"GossamerDriftConsoleCoordinator: restructure, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"GossamerAtlasSearchCoordinator needs a paired pass: finish GossamerAtlasSearchCoordinator's responsive empty and retry states, plus give the existing implementation a read-only safety pass. Use projects/gossamer/src/sync/reconcile.ts as the source of truth, preserve the OpenTelemetry contract, and avoid unrelated cleanup.","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Em projects/gossamer/ml/pipeline/features.py, o GossamerFrostPanelStore tem um problema intermitente no fluxo de gRPC. Finalize o layout responsivo, estados vazio e retry, foco por teclado, dark mode e reduced motion.\n\nRestrições:\n- continuar com gRPC\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao GossamerFrostPanelStore","purpose":"frontendImpl","secondary":"debugging","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"pt"} +{"prompt":"projects/gossamer/web/components/FilterDrawer.vue の GossamerHarborIndexService で、Room の flow に断続的な問題が起きています。 原因は判明済みです。staging timeout だけを 15 秒から 30 秒へ変え、対応する assertion を直してください。\n\n制約:\n- Room を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は GossamerHarborIndexService のみ","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"ja"} +{"prompt":"projects/gossamer/db/migrations/20260730_events.sql has grown through several launches, and GossamerMoonlitSDKService now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- keep VoiceOver and keyboard navigation working\n- stay compatible with the existing OpenTelemetry deployment\n- keep the work scoped to GossamerMoonlitSDKService and its direct tests\n\nThis repository spans healthcare, Svelte, Kafka; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"GossamerEchoRegistryStore crashes after reconnect","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/gossamer/lib/codec/frame.cc b/projects/gossamer/lib/codec/frame.cc\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/lib/codec/frame.cc\n+++ b/projects/gossamer/lib/codec/frame.cc\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 GossamerPrismCacheCoordinator 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":"Bring GossamerCedarPolicyService'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":"GossamerFernSnapshotStore returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/gossamer/ui/settings/PrivacyPane.tsx and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Sable: Ticket OPS-47116: retire the legacy replay path for GossamerEmberRelayFlow\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 GossamerEmberRelayFlow 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":"Incident timeline — INC-47155\n\n08:02 deploy GossamerGarnetModalCoordinator 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current GossamerGarnetModalCoordinator 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":"Tide: Ticket OPS-47126: retire the legacy replay path for GossamerAtlasSearchFlow\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 GossamerAtlasSearchFlow 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":"GossamerPineMetricsCoordinator: polish the last piece","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Draft GossamerVelaDrawerService's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"For GossamerAcornWidgetCoordinator, separate GossamerAcornWidgetCoordinator's policy from transport without behavior changes; once that is complete, correct the known stale timeout beside it. Work from projects/gossamer/web/components/FilterDrawer.vue, stay with Room, and keep VoiceOver and keyboard navigation working. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Could GossamerCopperBridgeService show the active FastAPI sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Does GossamerMoonlitSDKFlow enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists? I want your judgment and walkthrough, not new documentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"The behavior of GossamerRavenSessionStore is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/gossamer/infra/modules/edge/main.tf. 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- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current Room operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka monorepo, so keep ownership and handoff points understandable in a small review.\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":"GossamerLumenChartCoordinator is blocking the next release because an accessibility label that reads the internal enum. I need two concrete outcomes from a single pass: finish GossamerLumenChartCoordinator's responsive empty and retry states, and capture the contract and rollback note for consumers. Use the existing Swift 6 conventions in projects/gossamer/engine/render/atlas.cpp; keep VoiceOver and keyboard navigation working. 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":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Sketch the GossamerEchoRegistryService migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"thread 'tokio-runtime-worker' panicked at projects/gossamer/src/sync/reconcile.ts:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: gossamerslateeditorflow::scheduler::LeaseTask::flush\n at ./projects/gossamer/src/sync/reconcile.ts:217:18\n 4: gossamerslateeditorflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nReconstruct the GossamerSlateEditorFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Two deliverables are holding up GossamerMicaProfileCoordinator. First, assess ownership and failure handling in projects/gossamer/Sources/CLI/Commands/Doctor.swift. In the same workstream, capture the contract and rollback note for consumers. The relevant starting point is projects/gossamer/Sources/CLI/Commands/Doctor.swift, which follows gRPC conventions and currently suffers from lost focus when the drawer animation finishes. Keep voiceover and keyboard navigation working.\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":"review","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"GossamerEchoRegistryCoordinator: diagnose, then document","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Umbra: # projects/gossamer/infra/modules/edge/main.tf\n[worker.gossamerravensessioncoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossamerravensessioncoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossamerravensessioncoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerRavenSessionCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47158\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/gossamer/infra/modules/edge/main.tf. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-47118: retire the legacy replay path for GossamerEchoRegistryFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for GossamerEchoRegistryFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"Vela: // projects/gossamer/apps/console/routes/usage.svelte\nfinal class GossamerCinderAuthFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 GossamerCinderAuthFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"GossamerCloudReconcilerCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"In projects/gossamer/apps/console/routes/usage.svelte hat GossamerCinderAuthService ein sporadisches Problem im OpenTelemetry-Ablauf. Verfolge Queue, Scheduler und Abbruch, vergleiche Hypothesen und finde die Ursache vor jeder Änderung.\n\nRandbedingungen:\n- OpenTelemetry weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf GossamerCinderAuthService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um GossamerCinderAuthService mit OpenTelemetry kompatibel.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} +{"prompt":"UI ticket DES-47151: finish the compact GossamerOspreyJobCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/gossamer/apps/console/routes/usage.svelte\nFramework: OpenTelemetry\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 GossamerOspreyJobCoordinator'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":"Pin GossamerOrbitSyncService's FastAPI dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Exponha retryAfter em GossamerIrisBatchService","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"pt"} +{"prompt":"GossamerQuartzPlayerCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Willow: Incident timeline — INC-47141\n\n08:02 deploy GossamerCedarPolicyFlow 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 GossamerCedarPolicyFlow 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":"GossamerSlateEditorCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current GossamerFlintTimelineStore design actually guarantees what its callers assume. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside GossamerFlintTimelineStore\n- keep VoiceOver and keyboard navigation working\n\nThe relevant code crosses healthcare, Svelte, Kafka. 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":"Xylem: Incident timeline — INC-47157\n\n08:02 deploy GossamerNimbusFormCoordinator 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 GossamerNimbusFormCoordinator, 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":"diff --git a/projects/gossamer/workers/thumbnail/consumer.ex b/projects/gossamer/workers/thumbnail/consumer.ex\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/workers/thumbnail/consumer.ex\n+++ b/projects/gossamer/workers/thumbnail/consumer.ex\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 GossamerWillowCodecFlow'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":"GossamerJuniperCLIService'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":"Spell GossamerCoralUploadStore's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"On compact widths, GossamerQuartzPlayerStore'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.6,"slice":"core","lang":"en"} +{"prompt":"Assess the GossamerKiteSchedulerStore diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating a misleading timeout name used in five packages in GossamerMoonlitSDKStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Yarrow: diff --git a/projects/gossamer/crates/index/src/segment.rs b/projects/gossamer/crates/index/src/segment.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/crates/index/src/segment.rs\n+++ b/projects/gossamer/crates/index/src/segment.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nAdd the bounded GossamerQuartzPlayerFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Two asks around GossamerCoralUploadCoordinator: (1) separate GossamerCoralUploadCoordinator's policy from transport without behavior changes; (2) give the existing implementation a read-only safety pass. Keep voiceover and keyboard navigation working, and leave a clear boundary between the resulting artifacts or edits.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Fresh release brief for GossamerCinderAuthCoordinator:\n- primary outcome: lay out a staged migration for GossamerCinderAuthCoordinator\n- companion outcome: then implement the bounded durable-cursor handler\n- repository entry point: projects/gossamer/app/src/main/SyncWorker.kt\n- platform constraint: OpenTelemetry\n- known complication: timestamps rendered one day ahead near UTC midnight\n\nBoth results are required, but they should remain independently reviewable. Keep voiceover and keyboard navigation working; retain serialization and authorization boundaries; cover cancellation, idempotent retries, and rollback; and avoid drive-by cleanup. Use the code as the source of truth, call out assumptions, and state how an on-call engineer can tell that either part is unsafe to ship.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"GossamerOspreyJobStore's metric is misspelled as succesful_total in one declaration. Correct that literal and its exact test expectation, without renaming anything else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Zephyr: Two asks around GossamerAmberFilterCoordinator: (1) assess ownership and failure handling in projects/gossamer/infra/modules/edge/main.tf; (2) capture the contract and rollback note for consumers. Keep voiceover and keyboard navigation working, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"En projects/gossamer/app/src/main/SyncWorker.kt, GossamerCinderAuthStore tiene un problema intermitente en el flujo de OpenTelemetry. Separa responsabilidades y elimina duplicación, conservando API, wire values, orden y comportamiento observable.\n\nRestricciones:\n- seguir con OpenTelemetry\n- conservar compatibilidad y cancelación\n- limitar el cambio a GossamerCinderAuthStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con OpenTelemetry alrededor de GossamerCinderAuthStore.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"es"} +{"prompt":"GossamerFernSnapshotCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"What sequence would let GossamerJuniperCLIStore adopt FastAPI 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.8,"slice":"core","lang":"en"} +{"prompt":"Checkout: # projects/gossamer/crates/index/src/segment.rs\n[worker.gossamersprucedaemonflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossamersprucedaemonflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossamersprucedaemonflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerSpruceDaemonFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47114\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/gossamer/crates/index/src/segment.rs and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"We expect GossamerEmberRelayStore to outgrow its current OpenTelemetry arrangement next quarter, but changing everything at once would be risky. 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- keep VoiceOver and keyboard navigation working\n- stay compatible with the existing OpenTelemetry deployment\n- keep the work scoped to GossamerEmberRelayStore and its direct tests\n\nThis repository spans healthcare, Svelte, Kafka; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'GossamerCopperBridgeFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[GossamerCopperBridgeFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/gossamer/pkg/cache/lease.rs:144: error: -[GossamerCopperBridgeFlowTests 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 '-[GossamerCopperBridgeFlowTests 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\nDetermine why GossamerCopperBridgeFlow 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":"PM is preparing the GossamerLumenChartStore rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside GossamerLumenChartStore\n- keep VoiceOver and keyboard navigation working\n\nThe relevant code crosses healthcare, Svelte, Kafka. Prefer evidence from the repository and make any assumption explicit.\n\nProduce durable prose rather than a code assessment or implementation change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Corrige le timeout de GossamerIrisBatchStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"fr"} +{"prompt":"Sketch the GossamerSummitProxyStore migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-47159: finish the compact GossamerFlintTimelineCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/gossamer/config/staging.toml\nFramework: FastAPI\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 GossamerFlintTimelineCoordinator 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":"diff --git a/projects/gossamer/internal/auth/refresh.go b/projects/gossamer/internal/auth/refresh.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/internal/auth/refresh.go\n+++ b/projects/gossamer/internal/auth/refresh.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate GossamerTideWorkerFlow'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":"Support wants the behavior in projects/gossamer/workers/thumbnail/consumer.ex recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-47138: retire the legacy replay path for GossamerLedgerGateFlow\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 GossamerLedgerGateFlow 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":"GossamerTideWorkerCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Our support and SDK teams keep answering the same questions about GossamerFlintTimelineService, but the current prose in projects/gossamer/packages/api/openapi.yaml only describes the happy path. 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- keep VoiceOver and keyboard navigation working\n- stay compatible with the existing FastAPI deployment\n- keep the work scoped to GossamerFlintTimelineService and its direct tests\n\nThis repository spans healthcare, Svelte, Kafka; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Compare GossamerMarbleTokenStore's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Security flagged GossamerMicaProfileService for a read-only pass because its gRPC boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current gRPC operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka 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":"This should remain a deliberately small patch: GossamerMicaProfileStore has one known configuration mistake in projects/gossamer/Sources/CLI/Commands/Doctor.swift, not an open-ended failure investigation. 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- keep VoiceOver and keyboard navigation working\n- stay compatible with the existing gRPC deployment\n- keep the work scoped to GossamerMicaProfileStore and its direct tests\n\nThis repository spans healthcare, Svelte, Kafka; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Outline a safer GossamerKiteSchedulerService cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"The GossamerOpalRouterService surface in projects/gossamer/packages/api/openapi.yaml 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":"Exporter: Two asks around GossamerMosaicGridCoordinator: (1) ship the idempotent GossamerMosaicGridCoordinator replay endpoint; (2) give the existing implementation a read-only safety pass. Keep voiceover and keyboard navigation working, and leave a clear boundary between the resulting artifacts or edits.","purpose":"backendImpl","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"# projects/gossamer/packages/api/openapi.yaml\n[worker.gossameropalrouterflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossameropalrouterflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossameropalrouterflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerOpalRouterFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47149\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/gossamer/packages/api/openapi.yaml. 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":"# projects/gossamer/services/ledger/replay.go\n[worker.gossameracornwidgetflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.gossameracornwidgetflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.gossameracornwidgetflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.GossamerAcornWidgetFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-47133\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 GossamerAcornWidgetFlow'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":"Add a bounded GossamerCopperBridgeStore export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"For GossamerIrisBatchCoordinator, produce a consumer guide for GossamerIrisBatchCoordinator; once that is complete, give the existing implementation a read-only safety pass. Work from projects/gossamer/workers/thumbnail/consumer.ex, stay with Swift 6, and keep VoiceOver and keyboard navigation working. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Check GossamerMapleQueueService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"GossamerKiteSchedulerCoordinator: restructure, then correct","purpose":"refactor","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"GossamerGarnetModalFlow returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/gossamer/ml/pipeline/features.py and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Decouple GossamerSpruceDaemonService's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"GossamerOpalRouterCoordinator: sort out the rough edge","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Three teams extended GossamerDeltaCanvasService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep VoiceOver and keyboard navigation working\n- retain the current FastAPI operational envelope\n\nSeveral teams work in this healthcare, Svelte, Kafka 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":"Scheduler: diff --git a/projects/gossamer/lib/codec/frame.cc b/projects/gossamer/lib/codec/frame.cc\nindex 62d71aa..90f3c1e 100644\n--- a/projects/gossamer/lib/codec/frame.cc\n+++ b/projects/gossamer/lib/codec/frame.cc\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 GossamerLumenChartFlow'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":"Investigate the GossamerMosaicGridService hang","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Could the reasoning behind GossamerSlateEditorStore's OpenTelemetry choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Does GossamerAmberFilterStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} diff --git a/data/round2-08.jsonl b/data/round2-08.jsonl index 7de7388..c6b4cb0 100644 --- a/data/round2-08.jsonl +++ b/data/round2-08.jsonl @@ -1,200 +1,200 @@ -{"prompt": "the agent one", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "claims stopped auto-assigning overnight and there's nothing obviously wrong:\n\nActiveJob::DeserializationError: Error while trying to deserialize arguments: Couldn't find Claim with 'id'=88412\n from /app/vendor/bundle/ruby/3.3.0/gems/activejob-7.2.1/lib/active_job/arguments.rb:88:in `deserialize_global_id'\n from /app/app/jobs/auto_assign_job.rb:12:in `perform'\n\nSidekiq::Job dead: AutoAssignJob args=[gid://claims/Claim/88412] retries=25\nDead set size: 4,118\n\nclaims created in the last hour: 1,204\nclaims assigned: 0\nclaims table max id: 88,401\n\nsomething is enqueuing jobs for claims that don't exist yet", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "claim documents upload fine and then can't be downloaded, about 1 in 200:\n\nAws::S3::Errors::NoSuchKey (The specified key does not exist.):\n app/services/documents/fetch.rb:41:in `download'\n app/controllers/documents_controller.rb:22:in `show'\n\nupload log for the same document:\n 11:02:14 direct upload started key=claims/88412/scan-001.pdf size=4.1MB\n 11:02:19 direct upload completed etag=\"9c1d0044410bb7b77e91030cc219e1f0\"\n 11:02:19 Document record created id=41882 key=claims/88412/scan-001.pdf\n 11:02:20 antivirus scan queued\n 11:02:44 antivirus scan passed\n 11:02:44 document moved to claims/88412/clean/scan-001.pdf\n\nthe Document row still points at the pre-scan key", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "pipeline caches restore into the wrong workspace occasionally and builds fail bizarrely:\n\ncache key: deps-{{ checksum \"go.sum\" }}-linux-amd64\nrestored from: deps-9c1d0044410bb7b77e91030cc219e1f0a-linux-amd64\nrestore path: /workspace/.cache/go-build\n\nbuild output:\n # github.com/lumen/claims/internal/rating\n internal/rating/table.go:41:2: cannot find package \"github.com/lumen/claims/internal/tariff\"\n note: module github.com/lumen/claims requires go >= 1.24, running go1.22\n\nagent reports:\n workspace /workspace reused from previous job (pipeline 8f2b1c, repo lumen/billing)\n cleanup: skipped (fast-path enabled)", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "our claims dashboard times out for the largest broker and the correlated subqueries are the obvious suspect, but i'd like the actual profile before rewriting. work out where the time goes, then restructure the query so the page loads for a broker with four hundred thousand claims", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "the pipeline parser validates inconsistently, ignores some problems silently, and duplicates the API's own validation. consolidate it, and while you're there confirm whether any currently-accepted pipeline would start failing — i'd rather know than find out from a customer customers write these files by hand, so a newly-rejected pipeline is a support ticket.", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "plugin host segfaults during automation recording, roughly once an hour:\n\nProgram received signal SIGSEGV, Segmentation fault.\n0x00007ffff7a2c118 in juce::AudioProcessorValueTreeState::Parameter::setValueNotifyingHost(float) ()\n(gdb) bt\n#0 juce::AudioProcessorValueTreeState::Parameter::setValueNotifyingHost(float)\n#1 0x0000555555601a44 in AutomationRecorder::processBlock(juce::AudioBuffer&) at src/AutomationRecorder.cpp:141\n#2 0x00005555556220c8 in PluginProcessor::processBlock(juce::AudioBuffer&) at src/PluginProcessor.cpp:88\n#3 0x00007ffff7b0a112 in juce::AudioProcessorGraph::processBlock()\n(gdb) info threads\n Id Target Id Frame\n* 1 Thread (audio) setValueNotifyingHost\n 2 Thread (message) juce::MessageManager::runDispatchLoop\n\nsetValueNotifyingHost is being called from the audio thread, which the docs say not to do", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "claim rating engine's caching, which i inherited last week:\n\nclass Rating::Engine\n CACHE = {}\n\n def self.rate(claim)\n CACHE[claim.id] ||= begin\n policy = claim.policy.version_at(claim.incident_at)\n factors = policy.factors.map { |f| f.evaluate(claim) }\n Money.new(factors.sum { |f| f.amount_cents }, policy.currency)\n end\n end\nend\n\npuma with four workers and five threads each, claims are rated on every page view of the claim detail screen, and policy versions change when an underwriter edits them", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "pipeline definition format, which customers write by hand. is it as unambiguous as we think?\n\nsteps:\n - name: test\n image: golang:1.24\n commands: [\"go test ./...\"]\n cache:\n key: deps-{{ checksum \"go.sum\" }}\n paths: [\"/go/pkg/mod\", \".cache/go-build\"]\n - name: build\n image: golang:1.24\n depends_on: [test]\n commands: [\"go build -o bin/app\"]\n artifacts: [\"bin/app\"]\n - name: deploy\n when: { branch: main, event: push }\n image: alpine\n commands: [\"./deploy.sh\"]\n secrets: [DEPLOY_TOKEN]\n\nthe cache key doesn't include the image or the architecture; `when` on one step doesn't skip its dependents; and secrets are available to any command in the step, including ones that print the environment", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "claims API, integrated by four brokers, documented in a spreadsheet. this is the create endpoint:\n\nPOST /api/v2/claims\n auth: broker API key, scoped to the broker's policies\n body: { policy_number, incident_at, description, claimant: {...}, documents: [{ name, url }] }\n policy_number must exist and be active at incident_at, else 422 policy_not_in_force\n incident_at more than 90 days ago is accepted but flagged for manual review\n documents are fetched asynchronously from the given URLs; a fetch failure does not fail the claim\n the response is 202 with a claim reference, not 201, because assignment happens asynchronously\n duplicate submissions within 24h with the same policy and incident_at return the original reference\n\nwrite the API reference, and make the 202 and the deduplication behaviour impossible to miss", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "our API changelog needs an entry for the claim deduplication window, brokers keep asking", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "three ways of describing a step's status in our codebase, and the API leaks all three:\n\n// internal/agent\ntype StepState int // 0 pending, 1 running, 2 done, 3 failed, 4 killed\n\n// internal/api\ntype StepStatus string // \"queued\" | \"in_progress\" | \"success\" | \"failure\" | \"cancelled\"\n\n// database\nstatus smallint -- 0..4, but 5 and 6 exist in production rows from an old version\n\nthe mapping lives in three switch statements, one of which is missing a case and silently produces \"queued\" for anything unknown", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "what does the blocklist actually block?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "a regulator has asked six questions about rating reproducibility, post-closure edits, document retention, broker isolation, policy corrections and data replication. answer each from the code rather than from what we'd like to be true, and write it as a controls document with anything unsubstantiated clearly marked as such our compliance lead will read it before the regulator does and prefers plain statements.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "plugin SDK has no documentation beyond one example file, and the behaviours third-party developers keep tripping over are exactly the ones we've never written down: the version check that fails silently, the parameter cap that drops the extras, the blocklist after two crashes, and the thirty-second scan timeout counting as a crash. write the integration guide that covers all of it three developers are waiting on this and two of them have already shipped against guesses.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "audio drops out for a few hundred milliseconds when a plugin scan finishes, users are furious:\n\n[audio] callback 512 frames @ 48000 (10.67ms budget)\n[audio] xrun: callback took 24.11ms\n[audio] xrun: callback took 31.88ms\n[scan] plugin scan finished, 412 plugins, 88 new\n[scan] posting to message thread: refreshPluginList()\n[audio] xrun: callback took 41.02ms\n[audio] xrun: callback took 18.44ms\n[audio] 4 dropouts in 200ms\n[ui] plugin list rebuilt, 412 items\n\nrefreshPluginList swaps the shared array the audio thread reads from, under a std::mutex that the audio callback also takes", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "design doc for our session format, written before the plugin work. does it still hold?\n\n## Session file\nA session is a single JSON document containing tracks, clips, automation and a plugin manifest. Plugins are referenced by their UID and version. On load, missing plugins are replaced by a placeholder that preserves the parameter state so the session can round-trip.\n\n## Assumptions\n- Sessions are small (< 5MB) and can be parsed on the message thread at load.\n- Plugin UIDs are stable across versions.\n- Automation is sparse enough to store as a list of (time, value) pairs.\n\n## Not covered\nCollaborative editing. Partial loading. Sessions referencing external audio files that have moved.\n\nsessions from our heaviest users are now 40-80MB, and the placeholder path is what's crashing on iOS", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "prod and staging agent config, and staging has never wedged:\n\n# staging/agent.yaml\nagent:\n slots: 2\n fast_path: false\n hard_timeout: 20m\n soft_timeout: 10m\n reaper_interval: 1m\n runtime: docker\n workspace_root: /var/lib/agent/ws\n cleanup_on_release: true\n\n# prod/agent.yaml\nagent:\n slots: 8\n fast_path: true\n hard_timeout: 20m\n soft_timeout: 10m\n reaper_interval: 5m\n runtime: runc\n workspace_root: /mnt/nvme/ws\n cleanup_on_release: false\n\n# prod agent metrics over the last day\n agent_slots_reserved 4 (steady, no running steps)\n agent_steps_started_total rate 0/s for 3h\n agent_reaper_runs_total 12\n agent_reaper_errors_total 12 (\"container not found\")\n\nprod agents have 8 cores; fast_path went on last year to cut build times and nobody has revisited it since", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "one smoothing helper for all processors", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "is the ring buffer safe with std::function?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "i'd like an honest read on whether our rating cache can serve one claim's rating for another under puma's threading, and if it can, the fix — with a test that fails on the current code", "purpose": "review", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "we have two audio buffer pool implementations, one in the engine and one in the plugin host", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "three third-party developers are blocked on a plugin SDK document that doesn't exist, and writing it will force us to decide which of our current behaviours are the contract and which are accidents — the silent parameter cap, the blocklist, the scan timeout. i want the plan for what we commit to publicly before anyone writes prose", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "what does the antivirus step do with a document it can't scan at all", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "a walkthrough of the plugin scan process would help before i touch the blocklist", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "webhook receiver drops events under load and the numbers don't add up:\n\nnginx access log (1 minute sample):\n POST /webhooks/insurer 200 count=8,412\n POST /webhooks/insurer 499 count=1,204\n POST /webhooks/insurer 502 count=118\n\napp side:\n WebhookEvent.where(created_at: 1.minute.ago..).count => 8,180\n Sidekiq queue :webhooks depth => 41,882\n Sidekiq latency :webhooks => 812 seconds\n\npuma: 4 workers × 5 threads, and the receiver writes the event row synchronously before enqueueing\n\nthe insurer retries anything that isn't a 200 within 30 seconds, which is where the 499s come from", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "before this lands, is the lock-free queue actually lock-free the way it's used?\n\ntemplate \nclass RingBuffer {\n std::array data_;\n std::atomic head_{0}, tail_{0};\npublic:\n bool push(const T& v) { // called from the message thread\n auto t = tail_.load(std::memory_order_relaxed);\n auto next = (t + 1) % Capacity;\n if (next == head_.load(std::memory_order_acquire)) return false;\n data_[t] = v; // T is std::function\n tail_.store(next, std::memory_order_release);\n return true;\n }\n bool pop(T& out) { /* mirror, called from the audio thread */ }\n};\n\nthe queue carries std::function objects that capture by value, and the audio thread invokes them", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "agent's step execution, and i want to know whether the cleanup can be skipped safely:\n\nfunc (a *Agent) runStep(ctx context.Context, s Step) error {\n\tws, err := a.workspaces.Acquire(s.PipelineID)\n\tif err != nil { return err }\n\tif !a.fastPath {\n\t\tdefer a.workspaces.Clean(ws)\n\t}\n\tdefer a.workspaces.Release(ws)\n\tid, err := a.runtime.Create(ctx, s.Image, ws.Path)\n\tif err != nil { return err }\n\tdefer a.runtime.Remove(context.Background(), id)\n\tctx, cancel := context.WithTimeout(ctx, s.HardTimeout)\n\tdefer cancel()\n\treturn a.runtime.Wait(ctx, id)\n}\n\nfastPath is on in production, workspaces are reused across pipelines, and Release is also called by a reaper goroutine on timeout", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "la política de reintentos del receptor de webhooks, ¿tiene sentido?\n\nclass WebhooksController < ApplicationController\n skip_before_action :verify_authenticity_token\n\n def insurer\n event = WebhookEvent.create!(payload: params.to_unsafe_h, source: \"insurer\")\n ProcessWebhookJob.perform_later(event.id)\n head :ok\n rescue ActiveRecord::RecordNotUnique\n head :ok\n rescue => e\n Sentry.capture_exception(e)\n head :internal_server_error\n end\nend\n\n# ProcessWebhookJob\nclass ProcessWebhookJob < ApplicationJob\n queue_as :webhooks\n retry_on StandardError, wait: :polynomially_longer, attempts: 25\n\n def perform(id)\n event = WebhookEvent.find(id)\n Insurer::Apply.new(event).call\n event.update!(processed_at: Time.current)\n end\nend\n\nla aseguradora reintenta cualquier respuesta que no sea 200 durante 24 horas y sin espera entre intentos, el payload puede tener 2 MB con adjuntos en base64, y por la mañana nos llegan 40.000 eventos en veinte minutos", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "es"} -{"prompt": "support notes about the plugin scan, they need to become a proper help article:\n\n- first launch scans every plugin on the machine, which for a big library is 10-40 minutes\n- the scan runs in a separate process so a crashing plugin doesn't take the app down\n- a plugin that crashes twice is blocklisted and hidden from the browser, with no visible message\n- users find their plugin \"missing\" and reinstall it, which doesn't help because the blocklist survives\n- the blocklist is in a plist that we've never documented, and clearing it requires the terminal\n- rescanning individual plugins is possible from a preference pane most users never open\n- audio dropouts during the scan are a known issue we're working on\n\nwrite the article, including how to clear the blocklist without making it sound like a defect", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "regulator's question list arrived and answering it properly is the documentation we never wrote:\n\n1. How is a claim's assessed value calculated, and is the calculation reproducible for a claim closed two years ago?\n2. Which roles can alter a claim after it has been closed, and how is that recorded?\n3. How long are claim documents retained, and how is deletion evidenced?\n4. Describe the controls preventing a broker from seeing another broker's claims.\n5. What happens to a claim if the policy version it was rated against is later corrected?\n6. Where is claimant personal data replicated, including backups and analytics?\n\nwork each answer out from the code and write it as a controls document, marking anything you can't substantiate", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "stem export filenames drop the track number", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "queue alert needs a 30 minute window", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "document thumbnails need type badges", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "scan progress strip at the top", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "step status is colour-only in the graph", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "why do sessions take eight seconds to open?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "agents wedge at full capacity", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "session format design doc assumed sessions under five megabytes and stable plugin UIDs, and both assumptions have quietly failed — our heaviest users have eighty megabyte sessions and the placeholder path crashes on iOS. read the doc against the current loader and tell me which of its assumptions still hold i'd like the answer in terms of what breaks next rather than what's already broken.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "audio team's list, which i need to turn into a plan with the september release in mind:\n\n- move all plugin scanning off any lock the audio thread touches\n- lazy session loading, because 80MB sessions block the message thread for seconds\n- fix the MIDI timing drift, which is a rounding bug in the scheduler and probably a day's work\n- replace the three copies of plugin state with one owner\n- automation recording currently calls host APIs from the audio thread, which is why it segfaults\n- surface the plugin blocklist in the UI instead of hiding it in a plist\n\nthe release is in six weeks, and QA needs two of those", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "design spec for the plugin browser, which is currently a flat list of 400 items:\n\nPlugin browser\n- Left rail: categories (Instruments, Effects, Utility) with counts, plus Favourites and Recently Used.\n- Grid of cards, 160x120, showing the plugin name, vendor, format badge (VST3/AU/AAX) and a favourite star.\n- Virtualised; scrolling 2,000 plugins must stay at 60fps on a 2019 MacBook.\n- Search filters as you type with a 120ms debounce, matching name and vendor, highlighting the match.\n- Blocklisted plugins appear greyed with a warning glyph, a tooltip explaining why, and a Rescan action.\n- While a scan is running, a progress strip at the top shows the current plugin name and a Cancel button.\n- Drag a card onto a track to instantiate; the drag image is the card at 60% opacity.\n- Keyboard: type-ahead selection, enter instantiates on the selected track, space previews.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "one owner for the plugin list", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "i'd like to understand how a claim's assessed value is recalculated when the policy version changes", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "is our session loader doing anything on the audio thread, or is that just where it crashes", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "prod agents run eight slots on eight cores, which is why steps time out rather than queue", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "we need a plan for supporting AAX, which means a different SDK, signing, and a certification process", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "build agents wedge on a subset of pipelines and the only trace is this:\n\ntime=2026-07-29T11:02:14Z level=info msg=\"step started\" pipeline=8f2b1c step=test image=golang:1.24\ntime=2026-07-29T11:02:15Z level=info msg=\"container created\" id=a11c3f2 runtime=runc\ntime=2026-07-29T11:12:15Z level=warn msg=\"step exceeded soft timeout\" elapsed=10m0s\ntime=2026-07-29T11:22:15Z level=warn msg=\"step exceeded hard timeout, sending SIGTERM\" elapsed=20m0s\ntime=2026-07-29T11:22:45Z level=error msg=\"container did not exit, sending SIGKILL\"\ntime=2026-07-29T11:22:45Z level=error msg=\"kill failed\" err=\"container not found: a11c3f2\"\ntime=2026-07-29T11:22:45Z level=info msg=\"agent marked step failed, releasing slot\"\ntime=2026-07-29T11:22:46Z level=error msg=\"slot release failed: slot already released\"\n\nafter this the agent reports capacity 4/4 forever and takes no new work", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "iOS build of our sampler crashes on launch for some users only:\n\nException Type: EXC_BAD_ACCESS (SIGSEGV)\nException Subtype: KERN_INVALID_ADDRESS at 0x0000000000000018\nTermination Reason: SIGNAL 11 Segmentation fault: 11\n\nThread 0 Crashed:\n0 Sampler 0x104a2c118 juce::AudioProcessorGraph::rebuild() + 216\n1 Sampler 0x104b19a44 SamplerEngine::loadSession(juce::File const&) + 388\n2 Sampler 0x1051220c8 SessionRestore::restoreLast() + 296\n3 Sampler 0x104f0a112 -[AppDelegate application:didFinishLaunchingWithOptions:] + 148\n\nonly users whose last session referenced a plugin that has since been deleted from the device", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "das MIDI-Timing driftet bei langen Sessions, hier die Messwerte:\n\nEvent-Nr Soll (ms) Ist (ms) Abweichung\n1 0.00 0.02 +0.02\n1000 125000.00 125041.10 +41.10\n5000 625000.00 625208.44 +208.44\n10000 1250000.00 1250417.02 +417.02\n20000 2500000.00 2500834.88 +834.88\n\nSample-Rate 48000, Buffer 512, Host-Tempo 120 BPM konstant\ndie Abweichung wächst linear, etwa 0,33 ms pro 1000 Events\nwir rechnen die Event-Zeit in Samples um und runden dabei auf ganze Samples ab", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "de"} -{"prompt": "rails app leaks memory in production and restarts every six hours on the memory limit:\n\nrss over 6 hours: 420MB → 2.8GB, linear\nobjects allocated (GC.stat[:total_allocated_objects]) at restart: 4.1e9\nheap_live_slots: 41,882,104\n\nderailed exec perf:mem_over_time top allocations:\n app/services/rating/engine.rb:88 1.2GB Hash allocations\n app/models/claim.rb:212 0.8GB String allocations\n activerecord (7.2.1) query cache 0.4GB\n\nrating/engine.rb:88 is inside a loop over policy versions, memoising into a class-level hash keyed by claim id", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "the claim detail screen needs the document virus-scan states visible, and support needs the help article explaining what a rejected document means. do both, and keep the read-only broker view free of edit affordances", "purpose": "frontendImpl", "secondary": "writing", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "claims stopped auto-assigning overnight", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "claim reference is lowercase in emails", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "core", "lang": "en"} -{"prompt": "pipeline parser has grown organically and validation is scattered through it:\n\nfunc Parse(b []byte) (*Pipeline, error) {\n\tvar p Pipeline\n\tif err := yaml.Unmarshal(b, &p); err != nil { return nil, err }\n\tfor i, s := range p.Steps {\n\t\tif s.Name == \"\" { return nil, fmt.Errorf(\"step %d: name required\", i) }\n\t\tif !nameRe.MatchString(s.Name) { return nil, fmt.Errorf(\"step %s: bad name\", s.Name) }\n\t\tif s.Image == \"\" && s.Plugin == \"\" { return nil, fmt.Errorf(\"step %s: image required\", s.Name) }\n\t\tfor _, d := range s.DependsOn {\n\t\t\tif !p.has(d) { return nil, fmt.Errorf(\"step %s: unknown dependency %s\", s.Name, d) }\n\t\t}\n\t\tif s.Cache.Key != \"\" && len(s.Cache.Paths) == 0 { /* silently ignored */ }\n\t\tp.Steps[i] = applyDefaults(s)\n\t}\n\treturn &p, detectCycles(&p)\n}\n\nerror messages are inconsistent, some problems are silently ignored, and the same validation is duplicated in the API's own request validator", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "our health check reports the agent healthy while it has zero free slots and no running steps", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "the claims UI uses eleven hardcoded colours and three custom focus styles, one of which removes the ring. move it onto the tokens, and tell me which status colours will visibly change for adjusters who have used this for years", "purpose": "frontendImpl", "secondary": "review", "mixed": true, "difficulty": 0.55, "slice": "mixed", "lang": "en"} -{"prompt": "plugin browser is a flat list of four hundred items that scrolls badly on older machines, and it's the first thing every reviewer complains about. build the browser to the new spec — categories, virtualised card grid, search with highlighting, blocklist state visible — and keep drag-to-instantiate working exactly as it does today our oldest supported machine is a 2019 MacBook Pro, which is what the 60fps target refers to.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "claim documents are occasionally unreachable after upload, and the pattern seems to be that the antivirus step moves the object while the database row keeps the original key. i'd like that confirmed properly rather than assumed, including what happens when the scan fails and whether any documents are currently orphaned roughly one in two hundred, and support has three examples with timestamps if that helps.", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "pipeline YAML format has grown features that interact badly — `when` not skipping dependents, cache keys that ignore the image, secrets visible to every command in a step — and customers write these by hand. before we add anything else i'd like a view on whether this is a versioned format change or a set of fixes we can make compatibly", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "claims thing", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "our on-premise CI customers upgrade by replacing a binary and have no migration story for config", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "three query objects each define what \"this broker's claims\" means, two of them interpolate the search term straight into SQL, and they disagree about whether closed claims are included. consolidate them into one scope with one definition, keep the exported CSV byte-identical for a sample of brokers, and get rid of the interpolation while you're in there the export is what brokers reconcile against, so a changed row count would be noticed immediately.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "what guarantees does the agent make about artifact upload when a step is killed mid-write", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "a short note explaining why sessions are moving to lazy loading, for the decision log", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "plugin SDK document has to exist before we can onboard the three developers waiting on it, and writing it will surface behaviours we should probably change rather than document. write the guide, and give me the separate list of things you'd rather fix than commit to the silent version check is the one i'd most like to stop defending in writing.", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "SQL behind our claims dashboard, which times out for the largest broker:\n\nSELECT c.id, c.reference, c.status, c.incident_at,\n p.number AS policy_number, b.name AS broker,\n (SELECT SUM(amount_cents) FROM payments pm WHERE pm.claim_id = c.id) AS paid,\n (SELECT COUNT(*) FROM documents d WHERE d.claim_id = c.id) AS docs,\n (SELECT MAX(created_at) FROM claim_notes n WHERE n.claim_id = c.id) AS last_note\nFROM claims c\nJOIN policies p ON p.id = c.policy_id\nJOIN brokers b ON b.id = p.broker_id\nWHERE b.id = $1 AND c.status <> 'closed'\nORDER BY c.incident_at DESC\nLIMIT 50;\n\nclaims 2.1M rows, payments 8.4M, documents 12M, and the broker in question has 400k claims", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "concurrency model in our scheduler, which decides which agent gets which step:\n\nfunc (s *Scheduler) assign() {\n\ts.mu.Lock()\n\tdefer s.mu.Unlock()\n\tfor _, step := range s.pending {\n\t\tfor _, agent := range s.agents {\n\t\t\tif agent.Free() >= step.Slots && agent.Matches(step.Tags) {\n\t\t\t\tagent.Reserve(step.Slots)\n\t\t\t\tgo s.dispatch(agent, step)\n\t\t\t\ts.remove(step)\n\t\t\t\tbreak\n\t\t\t}\n\t\t}\n\t}\n}\n\nassign runs every second and on every agent heartbeat; dispatch can take up to 30 seconds; Reserve is in-memory only and the agent may already be running steps it accepted from a previous scheduler instance", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "public pipeline YAML reference is a single example with no prose. this is what the parser accepts:\n\nsteps[].name required, unique within the file, [a-z0-9-]{1,40}\nsteps[].image required unless `plugin` is set\nsteps[].commands list of strings, run with `set -e` in a shell\nsteps[].depends_on list of step names; a cycle is a parse error\nsteps[].when map of branch/event/path filters, all must match\nsteps[].cache.key template string, `{{ checksum \"file\" }}` and `{{ env \"VAR\" }}` supported\nsteps[].cache.paths list, relative paths are relative to the workspace root\nsteps[].artifacts list of globs, uploaded on success only\nsteps[].secrets list of secret names, injected as environment variables\nsteps[].matrix map of name to list; expands the step, `matrix.` available in templates\n\nwrite the reference documentation, including that `when` doesn't skip dependents and that cache keys don't include the image", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "o resumo do incidente de ontem, para os corretores. estes são os factos:\n\n09:12 as participações deixam de ser atribuídas automaticamente\n09:31 detetamos que a fila de jobs está a rejeitar tudo com erro de desserialização\n10:02 causa identificada: o job é enfileirado dentro da transação, antes do commit\n10:20 correção aplicada em produção\n10:40 reprocessamento das 1.204 participações em atraso\n11:15 tudo normalizado; nenhuma participação perdida, o atraso máximo foi de duas horas\n\nos corretores viram participações \"por atribuir\" durante duas horas e alguns telefonaram para o apoio; não houve perda de dados nem prazos regulamentares ultrapassados", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "pt"} -{"prompt": "changelog for the desktop app, from the release branch:\n\n41c9e0b fix(audio): plugin scan no longer takes the audio lock\n88f21c0 feat(session): sessions load lazily, large sessions open in under a second\nc0aa774 fix(ios): sessions referencing deleted plugins no longer crash on launch\n2e91b45 feat(midi): sample-accurate event scheduling, fixes long-session drift\naa30f19 fix(browser): blocklisted plugins now show with an explanation and a rescan button\n9c1d004 perf(ui): plugin list virtualised\n4410bb7 chore: minimum macOS is now 13\nb77e910 feat(export): stem export with per-track naming templates\n\nour users are musicians, not engineers; two of these are things they've been complaining about for a year and one is a breaking change", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "pasted-context", "lang": "en"} -{"prompt": "runbook for a wedged agent is \"restart it\", which loses running builds. what the team actually does:\n\n- symptom is an agent reporting full capacity with no running steps, usually after a container disappears\n- `agentctl slots ` shows the reserved slots and which pipeline reserved them\n- `agentctl release ` frees one, and the scheduler picks up within a second\n- restarting the agent kills any genuinely running builds, which is why we avoid it\n- if the reaper is the thing that's stuck, its goroutine dump shows it blocked on the runtime socket\n- the underlying bug is that slot release is not idempotent, and we've known that for months\n\nturn this into a runbook page, and be clear about which steps are safe during working hours", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "我们的插件开发文档只有一页示例代码，需要正式的接入说明。目前 SDK 的实际行为如下：\n\n- 插件必须导出 `lumen_plugin_entry`，返回描述结构体；结构体里的 `abi_version` 必须与 SDK 主版本号一致，否则宿主会静默跳过，不打印任何日志\n- 参数上限为 512 个，超出的部分在注册阶段被丢弃，既不报错也不警告\n- `processBlock` 在音频线程调用，禁止分配内存、加锁、访问文件系统或调用任何宿主 API\n- `getStateInformation` 返回的数据会原样写入会话文件；没有硬性大小限制，但超过 1MB 会明显拖慢会话加载\n- `setStateInformation` 可能在音频线程停止之前被调用，插件必须自行处理并发\n- 插件连续崩溃两次后进入黑名单，黑名单保存在用户目录的 plist 文件里，我们从未对外说明过，用户只会发现插件“消失了”\n- 扫描在独立进程中进行，单个插件超时时间是 30 秒，超时同样计入崩溃次数\n- 参数自动化的写入频率上限是每个采样块一次，超过的调用会被静默合并\n\n请写成面向第三方开发者的接入文档，把黑名单、超时和参数上限这三件事写清楚，其余按常规接口说明组织\n\n目前的示例代码就是这一段，文档里也只有这些：\n\nextern \"C\" LumenPluginDescription* lumen_plugin_entry(void) {\n static LumenPluginDescription d = {\n .abi_version = LUMEN_ABI_VERSION,\n .uid = \"com.example.reverb\",\n .name = \"Example Reverb\",\n .vendor = \"Example Audio\",\n .num_parameters = 4,\n .create = &create_instance,\n .destroy = &destroy_instance,\n };\n return &d;\n}\n\nstatic void process_block(LumenPlugin* self, float** io, int channels, int frames) {\n // 这里不能分配内存、不能加锁、不能调用宿主 API\n}", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "zh"} -{"prompt": "rubocop and brakeman before the gate goes on:\n\napp/controllers/webhooks_controller.rb:12:5: W: Rails/SkipsModelValidations: Avoid using `update_all`\napp/services/rating/engine.rb:8:3: C: Style/ClassVars: Class variable @@cache is used\napp/models/claim.rb:141:9: C: Metrics/AbcSize: Assignment Branch Condition size for assign is too high. [<12, 28, 9> 32.08/17]\n\nBrakeman:\n Confidence: High\n Category: Mass Assignment\n Check: MassAssignment\n Message: Parameters should be whitelisted for mass assignment\n File: app/controllers/webhooks_controller.rb\n Line: 6\n\n Confidence: Medium\n Category: SQL Injection\n Check: SQL\n Message: Possible SQL injection\n File: app/queries/claims_search.rb\n Line: 88", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "clang-tidy on the audio engine, and two of these are the ones that bite:\n\nsrc/AutomationRecorder.cpp:141:9: warning: function 'processBlock' calls 'setValueNotifyingHost' which may allocate [audio-thread-safety]\nsrc/SamplerEngine.cpp:88:22: warning: 'std::function' invoked on the audio thread may allocate on copy [performance-no-automatic-move]\nsrc/SessionRestore.cpp:41:5: warning: 'get' on possibly null pointer [bugprone-unchecked-optional-access]\nsrc/PluginScanner.cpp:212:13: warning: lock acquired in a real-time context [audio-thread-safety]\nsrc/UI/PluginList.cpp:19:1: warning: function exceeds recommended size [readability-function-size]\n\n5 warnings; the two audio-thread-safety ones correspond exactly to our two worst crash clusters", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "CI for the audio engine takes 50 minutes and most of it is this:\n\njobs:\n build:\n strategy:\n matrix:\n os: [macos-14, macos-15, ubuntu-24.04, windows-2022]\n config: [Debug, Release]\n steps:\n - uses: actions/checkout@v4\n with: { submodules: recursive }\n - run: cmake -B build -DCMAKE_BUILD_TYPE=${{ matrix.config }}\n - run: cmake --build build --parallel\n - run: ctest --test-dir build --output-on-failure\n\nno ccache, no build cache action, JUCE is a submodule that gets fully rebuilt every time, and Debug builds are only ever looked at when something fails", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "bundler audit on the rails app, which of these go in today:\n\nName: rack\nVersion: 3.0.9\nAdvisory: CVE-2026-10884\nCriticality: Medium\nSolution: upgrade to >= 3.0.11\n\nName: nokogiri\nVersion: 1.16.2\nAdvisory: CVE-2026-11221\nCriticality: High\nSolution: upgrade to >= 1.17.1\n\nName: sidekiq\nVersion: 7.2.0\nAdvisory: GHSA-4c8f (web UI XSS in the busy page)\nCriticality: Medium\nSolution: upgrade to >= 7.3.2\n\nour sidekiq web UI is behind SSO and only reachable from the office network", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"} -{"prompt": "terraform for our build agents, someone spotted this during an unrelated review:\n\nresource \"aws_instance\" \"agent\" {\n count = var.agent_count\n instance_type = \"c7i.4xlarge\"\n vpc_security_group_ids = [aws_security_group.agent.id]\n user_data = templatefile(\"agent.sh.tpl\", { token = var.agent_token })\n metadata_options {\n http_tokens = \"optional\"\n }\n}\n\nresource \"aws_security_group_rule\" \"agent_ssh\" {\n type challenge = \"ingress\"\n from_port = 22\n to_port = 22\n cidr_blocks = [\"0.0.0.0/0\"]\n}\n\nthe agent token is a long-lived credential that can register new agents", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "agent's configuration, documented by its flag help and nothing else:\n\n --workspace-root string where job workspaces are created (default \"/var/lib/agent/ws\")\n --fast-path reuse workspaces between jobs without cleaning (default false)\n --slots int concurrent steps this agent will accept (default 4)\n --tags strings labels used for step matching\n --hard-timeout duration kill a step after this (default 20m)\n --soft-timeout duration warn after this (default 10m)\n --reaper-interval duration how often to look for orphaned containers (default 1m)\n --runtime string runc | docker | podman (default \"runc\")\n\nwhat operators actually need to know: fast-path is why one customer's builds see another repo's files; slots above the core count causes step timeouts rather than queueing; the reaper is the only thing that recovers a leaked slot, and it doesn't handle the case where the container is already gone\n\nwrite the operator's configuration guide", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "les seuils d'alerte de la file d'attente, on nous réveille pour rien :\n\n- alert: WebhookQueueDepth\n expr: sidekiq_queue_size{queue=\"webhooks\"} > 1000\n for: 1m\n labels: { severity: page }\n\n- alert: WebhookQueueLatency\n expr: sidekiq_queue_latency{queue=\"webhooks\"} > 60\n for: 1m\n labels: { severity: page }\n\ncomportement normal : chaque matin à 6h l'assureur envoie un lot de 40 000 événements, la file monte à 40 000 et se vide en vingt minutes\nincident réel du mois dernier : la file est restée à 200 000 pendant six heures sans que personne ne le remarque, parce que tout le monde avait coupé les alertes", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "fr"} -{"prompt": "same parameter-smoothing code exists in four processors with different time constants:\n\n// Gain.cpp\nsmoothed = smoothed * 0.99f + target * 0.01f;\n\n// Filter.cpp\nconst float coeff = std::exp(-1.0f / (0.05f * sampleRate));\nsmoothed = target + (smoothed - target) * coeff;\n\n// Delay.cpp\nsmoothed += (target - smoothed) * (1.0f / 64.0f);\n\n// Reverb.cpp\njuce::SmoothedValue smoothed; // ramp length 0.02s, set once in prepareToPlay\n\nthree of them are sample-rate dependent in ways their authors probably didn't intend, and only the reverb one is reset on prepareToPlay", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "this service object has grown to 400 lines and the tests take a database. same behaviour, testable pieces:\n\nclass Claims::Assign\n def initialize(claim, actor: nil, force: false)\n @claim, @actor, @force = claim, actor, force\n end\n\n def call\n return if @claim.assigned? && !@force\n candidates = Adjuster.active.where(region: @claim.region)\n candidates = candidates.where(specialism: @claim.peril) if @claim.complex?\n candidates = candidates.reject { |a| a.workload > a.capacity }\n chosen = candidates.min_by { |a| [a.workload, a.last_assigned_at] }\n raise NoAdjusterAvailable if chosen.nil?\n @claim.update!(adjuster: chosen, assigned_at: Time.current)\n AuditLog.create!(subject: @claim, actor: @actor || \"system\", action: \"assign\")\n AdjusterMailer.assigned(chosen, @claim).deliver_later\n Slack.notify(chosen.slack_id, \"New claim #{@claim.reference}\") if chosen.slack_id\n Metrics.increment(\"claims.assigned\", tags: [\"region:#{@claim.region}\"])\n end\nend", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "unsere Zustandsverwaltung im Plugin-Browser ist dreifach vorhanden:\n\n// PluginList.cpp — hält eine eigene sortierte Kopie\nstd::vector items;\n\n// PluginScanner.cpp — hält die Rohliste plus Blockliste\nstd::vector scanned;\nstd::set blocked;\n\n// SessionRestore.cpp — hält eine Map von UID auf Beschreibung\nstd::map byUid;\n\ndrei Kopien derselben Daten, die über Callbacks synchron gehalten werden, und der Audio-Thread liest zwei davon", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "de"} -{"prompt": "query objects each build their own filtering and they've drifted:\n\n# claims_search.rb\nscope = Claim.where(broker_id: broker.id)\nscope = scope.where(\"reference ILIKE ?\", \"%#{params[:q]}%\") if params[:q]\n\n# claims_export.rb\nscope = Claim.joins(:policy).where(policies: { broker_id: broker.id })\nscope = scope.where(\"claims.reference ILIKE :q OR claimants.surname ILIKE :q\", q: \"%#{params[:q]}%\")\n\n# api/v2/claims_controller.rb\nscope = current_broker.claims\nscope = scope.search(params[:q]) if params[:q].present?\n\nthree different definitions of \"this broker's claims\" and two of them interpolate the search term directly", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "half-year planning input, i need it turned into something sequenced:\n\n- the audio dropout problem is our worst review driver and the fix touches the plugin scanner, the session loader and the UI\n- a regulator audit of the claims platform is booked for february and we have no controls documentation\n- the CI platform's biggest customer wants isolated agents, which fast-path workspace reuse makes impossible\n- ios sessions crash on launch for a small but vocal group of users\n- one engineer is shared across the audio engine and the CI agent and is the only person who understands either\n- we owe a plugin SDK document to three third-party developers who are blocked without it\n- there's a macOS release in september that we cannot move", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "architecture ticket for the CI platform, needs thinking before code:\n\nCI-330 — Workspace isolation\nAgents currently reuse workspaces between jobs with cleanup disabled for speed, which is why one customer occasionally sees another repo's files. The proposal is a workspace per job on an overlay filesystem, with the lower layer being a warm cache of dependencies. Concerns: build times went up 40% in a naive experiment; the overlay approach ties us to specific kernels which our on-premise customers may not have; artifacts and caches currently assume a stable path; and we have no way to prove isolation to a customer once we've claimed it.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "regulator's expectations, as our compliance lead summarised them:\n\n\"Rating decisions must be reproducible for the lifetime of the claim plus seven years. Where a policy version is corrected, claims rated against the earlier version must be identifiable and re-rateable, with both results retained. Personal data of claimants must be deletable on request without destroying the audit trail of the claim itself. Access to claim data by staff must be logged with a business reason, and the log must not be alterable by those staff.\"\n\nwe memoise ratings in a process-local hash, we hard-delete claimant records on request, and our audit log is a table any admin can update. i want the plan, in order of regulatory risk", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "spec for the claim detail screen, the one adjusters live in all day:\n\nClaim detail\n- Header: reference, status pill, policy number, incident date, assessed value. Status drives the pill colour and a left border.\n- Three-column layout above 1440px, two below, single column under 900px. The columns are Summary, Documents, Activity.\n- Documents: thumbnail grid with type badges, drag to upload, virus-scan state per document (scanning / clean / rejected), and a rejected document must explain why.\n- Activity: reverse chronological, mixing notes, status changes, payments and emails, with filters per type that persist per user.\n- Notes: inline composer at the top of Activity, markdown, @mention autocomplete of adjusters, optimistic insert with a failure state.\n- Assessed value is editable inline by adjusters only, with the previous value shown on hover and every change recorded.\n- The whole screen must be usable read-only for brokers, with edit affordances absent rather than disabled.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "accessibility findings for our pipeline view, from an enterprise customer's review:\n\n1. The pipeline graph is an SVG with no text alternative; screen reader users cannot tell what ran or what failed.\n2. Step status is conveyed by colour only — green, red, grey circles with no label or shape difference.\n3. Live log output is announced continuously by screen readers, making the page unusable during a build.\n4. The log viewer traps focus; escape does nothing and tab cycles within it forever.\n5. Timestamps are rendered as relative text (\"2m ago\") that never updates and has no absolute value available.\n6. The retry button on a failed step is a div with a click handler.\n7. Contrast on the dimmed log text is 2.9:1.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "insurer's integration spec, we implement the receiving side:\n\nPOST to our endpoint, one event per request, at up to 2,000 requests per second during their morning batch\n headers: X-Insurer-Signature (HMAC-SHA256, hex), X-Insurer-Event-Id (UUID), X-Insurer-Sent-At\n body: up to 2MB of JSON, including base64 document attachments in some event types\n we must respond within 5 seconds; anything else is retried for 24 hours with no backoff\n duplicate event ids are expected (their retries) and must be idempotent\n events must be applied in `sent_at` order per policy, but arrive in any order\n a rejected event (signature failure) should be a 401, which they alert on\n they will disable our endpoint if our error rate exceeds 5% over an hour", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "schema we agreed for reproducible ratings, now it needs building:\n\nCREATE TABLE rating_runs (\n id uuid PRIMARY KEY,\n claim_id bigint NOT NULL REFERENCES claims(id),\n policy_version bigint NOT NULL REFERENCES policy_versions(id),\n engine_version text NOT NULL,\n inputs jsonb NOT NULL,\n result_cents bigint NOT NULL,\n currency char(3) NOT NULL,\n created_at timestamptz NOT NULL DEFAULT now(),\n superseded_by uuid REFERENCES rating_runs(id)\n);\n\nevery rating must be recorded, never mutated; re-rating creates a new row and links the old one; the claim detail screen shows the current rating and its history; and a rating must be reproducible from `inputs` plus `engine_version` seven years later, which means the engine's behaviour has to be versioned rather than just its code", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "design tokens versus what the claims UI actually uses:\n\ntokens:\n color.surface #FFFFFF / #14171A\n color.border #E1E4E8 / #2A2F35\n color.text.default #1B1F23 / #E6EDF3\n color.status.open #0969DA\n color.status.closed #6E7781\n color.status.urgent #CF222E\n space 4/8/12/16/24/32, radius 4/8/12, focus ring 2px offset 2px\n\nthe claims UI: eleven hardcoded colours, four of them near-misses; three custom focus styles, one of which removes the ring entirely; paddings of 6, 10, 14 and 18; and a status colour set that predates the tokens and doesn't match any of them\n\nbring it onto the tokens, keeping the status colours recognisable to adjusters who have used this for years", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "reaper interval back to 1m in prod", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "nokogiri advisory bump", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "core", "lang": "en"} -{"prompt": "ccache in the CMake CI job", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "el estado «cerrado» sale en inglés", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "core", "lang": "es"} -{"prompt": "ssh open to the world on agents", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "turn fast-path off on prod agents", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "IMDSv2 required on the agent instances", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "Debug-Builds nur noch bei Fehlern bauen", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "de"} -{"prompt": "class variable in the rating engine", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "the claims models have twelve callbacks between them and the order they fire in is load-bearing", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "claims platform has one engineer who understands the rating engine and a regulator audit in february, which is a risk in itself. what would you do about the knowledge concentration, given that the honest options are documentation, pairing, or restructuring the engine so it's less clever — and we can probably afford one of them", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "claim assignment does candidate selection, persistence, audit, email, slack and metrics in one method, and the selection logic is the only part anyone wants to test. split it, then document the assignment rules for the operations team who currently guess at them operations currently guess at the rules, and their guesses are wrong in at least two ways.", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "pipeline view fails an enterprise customer's accessibility review on seven counts, including a graph with no text alternative and live log output that screen readers read continuously. work through the findings, and where a fix changes the visual design, tell me before you commit to it they've asked for a remediation date, so a rough ordering by effort would help too.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "our audit log is a table any admin can update, which the regulator will notice in february", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "the claim reference in the PDF is generated with a different padding than the one in the UI", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "virtualise the plugin grid", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "format badges on the plugin cards", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "activity feed filters should persist", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "ログビューアからフォーカスが抜けません", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "ja"} -{"prompt": "relative timestamps never update", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "retry button is a div", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "dimmed log text fails contrast", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "pull the notifications out of Claims::Assign", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "one step-status type end to end", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "une seule définition de « sinistres du courtier »", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "fr"} -{"prompt": "`incident_at` naming across the app", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "move parser validation into one place", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "inline the one-line `has()` helper", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "split the 400-line assign service", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "doc comments on the plugin SDK entry point", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "release notes for the september build", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "nota para corretores sobre o incidente", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "pt"} -{"prompt": "document the 202 on claim creation", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "summarise the isolation proposal for the team", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "PR description for the scan fix", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "¿la caché de tarifas es segura entre hilos?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "es"} -{"prompt": "can a slot leak twice?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "walk me through claim assignment", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "dropouts whenever a scan finishes", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "warum wächst der Speicher linear?", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "de"} -{"prompt": "endpoint for a claim's rating history", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "keep going on that one", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "quieter", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "browser again please", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "your call on the order", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "sort out the mess", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "as before", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "audit stuff", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "encore une passe rapide", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "fr"} -{"prompt": "anything for the release", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "look at it again", "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": "more of the same", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "biggest CI customer wants isolated agents and our fast-path workspace reuse makes that impossible, but turning it off in a naive experiment made builds forty percent slower. i'd like the options for real isolation worked through — overlay filesystems, per-job volumes, or something else — with attention to our on-premise customers whose kernels we don't control, and to the awkward fact that we'd then be making an isolation claim we have to be able to prove", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "regulator expects rating decisions to be reproducible for the life of the claim plus seven years, and today we memoise ratings in a process-local hash and version nothing. work out what reproducibility actually requires of us — inputs, engine versioning, storage, re-rating after a policy correction — and give me the plan ordered by regulatory risk rather than by engineering convenience", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "september release is fixed and the audio team has six weeks minus two for QA, with six candidate items ranging from a day's rounding fix to restructuring who owns plugin state. sequence them for me with the dropout problem as the priority, and be explicit about which items i should cut rather than half-finish", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "operators configure the build agent from flag help alone, which is why one customer ran with fast-path on for a year without knowing what it meant. write the configuration guide, covering what each option does, which combinations are dangerous, and the fact that the reaper is the only thing that recovers a leaked slot some of them run us on hardware we've never seen, so avoid assuming our own topology.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "support explains the plugin blocklist several times a week and users reinstall plugins that were never the problem. write the help article that explains what the scan does, why a plugin disappears, and how to bring it back — pitched at a musician rather than an engineer, and without making our crash handling sound like a defect the article should stand alone without requiring a terminal, if that's at all possible.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "nobody can tell me whether our ring buffer is genuinely safe given that it carries std::function objects the audio thread invokes, and the copy on push may allocate. read it carefully and tell me exactly which operations can allocate or block, and whether the memory ordering is right for the single-producer single-consumer use we actually have", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "scheduler reserves slots in memory and dispatches in a goroutine that can take thirty seconds, while agents may already be running work accepted from a previous scheduler instance. work through what happens across a scheduler restart and tell me whether double-assignment is possible, and if so how often it would show up as the wedging we see", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "en"} -{"prompt": "claims API is integrated by four brokers off a spreadsheet, and the two things they get wrong every time are the 202 response and the 24-hour deduplication window. write the reference documentation properly, structured so those two are impossible to miss, with a worked example of a submission and its follow-up polling assume the reader is integrating for the first time and has our sandbox credentials.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "parameter smoothing is implemented four times across our processors, three of them sample-rate dependent in ways the authors probably didn't intend, and only one resets properly on prepareToPlay. consolidate onto one implementation with an explicit time constant, and keep each processor's audible behaviour at 48kHz indistinguishable from today's the reverb is the reference implementation as far as anyone remembers.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "step status exists as an int in the agent, a string in the API and a smallint in the database, with three switch statements mapping between them and one missing case that silently reports \"queued\". unify on one representation, handle the two legacy values that exist in production rows, and keep the public API strings exactly as they are there are two production rows with values five and six that predate the current enum.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "before the audio work starts i want the threading model written down properly — what the audio thread may touch, how state gets to it, what the message thread owns — and then the plugin scanner moved off the shared lock as the first piece of evidence that the model works the scanner is the piece we can ship first, and the release is in six weeks.", "purpose": "planning", "secondary": "refactor", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "workspace isolation needs a decision and also needs progress. lay out the options with their build-time cost, then implement per-job workspaces behind a flag so we can measure the real impact rather than argue about the naive experiment the naive experiment's forty percent slowdown is the number everyone will quote at us.", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "rating reproducibility is a february problem that needs starting now. give me the design — what we record, how the engine is versioned, what re-rating means — and then the rating_runs table and write path so new ratings start being recorded while the rest is designed the regulator's wording is about the life of the claim plus seven years, not about our schema.", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.9, "slice": "mixed", "lang": "en"} -{"prompt": "die Session-Datei ist inzwischen 80 MB groß und blockiert beim Laden den Message-Thread. Ich hätte gern zuerst ein Konzept für inkrementelles Laden und danach die Umsetzung des Track-Lazy-Loadings, damit die Startzeit vor dem Release besser wird", "purpose": "planning", "secondary": "frontendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "de"} -{"prompt": "webhook receiver needs to stop dropping events during the insurer's morning batch, and the fix probably changes our whole ingestion shape. think through the design — accept fast, persist cheaply, order per policy — then implement the accept path so tomorrow's batch survives their batch starts at six and they retry anything that isn't a 200 for a full day.", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "agent configuration guide needs writing, and while going through the flags i expect you'll find at least one whose documented default doesn't match the binary. produce the guide, and list every discrepancy you find between help text and behaviour operators run this on hardware we've never seen, so defaults matter more than usual.", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "escribe la documentación de la API de siniestros para los corredores y comprueba en el código si la deduplicación de 24 horas funciona como decimos, porque uno de ellos dice que recibe referencias distintas", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "es"} -{"prompt": "wedged-agent runbook should be a page rather than folklore, and the underlying non-idempotent slot release should stop being a footnote. write the runbook, then make release idempotent so the runbook's main entry becomes unnecessary the non-idempotent release has been a known footnote for months and it keeps costing us nights.", "purpose": "writing", "secondary": "backendImpl", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "plugin state lives in three places kept in sync by callbacks, two of which the audio thread reads. give it one owner, and write the short note explaining the new ownership so the next person doesn't add a fourth copy two of the three copies are read on the audio thread, which is the part that frightens me.", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "automation recorder calls host APIs from the audio thread, which explains the segfaults, but i want that confirmed before we restructure it. diagnose it properly, then move the parameter updates onto the message thread without changing the recorded result", "purpose": "debugging", "secondary": "refactor", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "MIDI events drift by about a third of a millisecond per thousand events, which smells like accumulated rounding in the sample conversion. confirm the mechanism, then fix the scheduling so long sessions stay accurate, and tell me whether existing sessions need anything", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "queue alerts page for the normal morning batch and stayed silent through a six-hour genuine backlog. work out what the rules should be from the actual traffic pattern, then change them", "purpose": "quickFix", "secondary": "planning", "mixed": true, "difficulty": 0.5, "slice": "mixed", "lang": "en"} -{"prompt": "agents should register with short-lived credentials rather than the long-lived token baked into user data. design the enrolment flow, then implement the token exchange", "purpose": "backendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "audio engine's parameter classes each reimplement denormal protection, three of them slightly wrong", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "go services each parse their own config with a different precedence between flags, env and file", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "rename `StepState` to `StepPhase` in the agent, it's confused with the API's status everywhere", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "could you explain what happens to a running build when the scheduler restarts", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "why does our cache key not include the container image, and has that ever bitten us", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "someone should check whether a broker can reach another broker's documents by guessing an id", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "is it expected that a step's secrets are visible to every command in that step", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "docs/rating.md describes a synchronous rating call that we made asynchronous last year", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "SDK header comments claim processBlock may allocate \"if necessary\", which is precisely wrong", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "write the migration note for operators about the minimum macOS version change", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "precisamos de uma página que explique aos corretores como funciona a atribuição automática", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "pt"} -{"prompt": "scan timeout counts as a crash toward the blocklist, which nobody intended", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "how should we version the pipeline YAML format now that we need to change three of its behaviours", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "what's the right approach to testing audio code where the failure mode is an audible glitch", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "three brokers want webhooks from us and we've only ever consumed them, what should our outbound story be", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "what should happen to in-flight builds when a customer's plan is downgraded mid-pipeline", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "an endpoint that returns a step's log with byte-range support, for the viewer's infinite scroll", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "claim documents should be served through signed URLs that expire, rather than proxied through rails", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "per-broker rate limits on the claims API, since one broker's batch job saturates our workers", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "session file should record the host sample rate so we can warn on mismatch at load", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "log viewer needs to follow output without pinning the scroll when the user has scrolled up", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "pipeline graph should collapse matrix expansions into one node with a count", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "documents grid needs a drag-to-upload target that works on the whole panel", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "stem export needs a naming template field with a live preview of the resulting filenames", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "whichever is least risky today", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "pick up the scanner work", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "our go services each parse configuration with a different precedence between flags, environment variables and the config file, and two of them silently ignore the file when a flag is present. settle on one precedence, apply it across all four services, and tell me which deployed configurations would resolve differently afterwards so we can warn the operators who run them", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "a broker's support ticket claims they can see a document that isn't theirs, which if true is the worst bug we could have. before anyone panics, trace how document authorisation actually works — the controller, the signed URL, and whether the scan-moved key is checked against the claim's broker at all", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "we need per-broker rate limiting on the claims API, because one broker's nightly batch job saturates the worker pool and everyone else's submissions queue behind it. limits per broker with a burst allowance, a clear 429 with a retry-after, and the limits themselves configurable without a deploy since account managers negotiate them individually", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "the claims models carry twelve callbacks whose firing order is load-bearing, which is why nobody dares add a thirteenth. untangle them into explicit service calls, keep the observable behaviour identical including the side effects on save, and document the order the old callbacks ran in so we can prove nothing was lost", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "denormal protection is reimplemented in each parameter class and three of the four are subtly wrong, which we only noticed because one processor gets slower with quiet input. consolidate it, and confirm from measurements rather than reasoning that the CPU behaviour is unchanged on the processors that were already correct", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "i'd like an honest read of whether our audit log can be altered by the admins it's meant to hold accountable, and if it can, the smallest change that fixes it before february rather than the ideal one", "purpose": "review", "secondary": "planning", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "prod agents run eight slots on eight cores, which is why steps time out instead of queueing, and the fix is a number in a config file. change it, and tell me what else in the agent's defaults assumes a machine larger than the one it runs on", "purpose": "quickFix", "secondary": "review", "mixed": true, "difficulty": 0.45, "slice": "mixed", "lang": "en"} +{"prompt":"HinterlandMicaProfileCoordinator needs a paired pass: assess ownership and failure handling in projects/hinterland/workers/thumbnail/consumer.ex, plus capture the contract and rollback note for consumers. Use projects/hinterland/workers/thumbnail/consumer.ex as the source of truth, preserve the Playwright contract, and avoid unrelated cleanup.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Ticket OPS-48127: retire the legacy replay path for HinterlandDeltaCanvasFlow\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 HinterlandDeltaCanvasFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"thread 'tokio-runtime-worker' panicked at projects/hinterland/src/sync/reconcile.ts:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: hinterlanddriftconsoleflow::scheduler::LeaseTask::flush\n at ./projects/hinterland/src/sync/reconcile.ts:217:18\n 4: hinterlanddriftconsoleflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nFind the source of this HinterlandDriftConsoleFlow symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Clarify HinterlandPrismCacheService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Dashboard: # projects/hinterland/crates/index/src/segment.rs\n[worker.hinterlandwillowcodecflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandwillowcodecflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandwillowcodecflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandWillowCodecFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48140\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/hinterland/crates/index/src/segment.rs and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Corrige le timeout de HinterlandDeltaCanvasStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"fr"} +{"prompt":"En projects/hinterland/workers/thumbnail/consumer.ex, HinterlandBeaconStoreService tiene un problema intermitente en el flujo de Playwright. Redacta una guía para consumidores con contrato, errores, retry y un ejemplo copiable; no cambies el handler.\n\nRestricciones:\n- seguir con Playwright\n- conservar compatibilidad y cancelación\n- limitar el cambio a HinterlandBeaconStoreService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} +{"prompt":"Worker: # projects/hinterland/workers/thumbnail/consumer.ex\n[worker.hinterlandnovapickerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandnovapickerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandnovapickerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandNovaPickerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48123\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 HinterlandNovaPickerFlow'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":"Simulator: # projects/hinterland/ui/settings/PrivacyPane.tsx\n[worker.hinterlandmicaprofileflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandmicaprofileflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandmicaprofileflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandMicaProfileFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48133\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/hinterland/ui/settings/PrivacyPane.tsx. 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":"Runbook: projects/hinterland/packages/api/openapi.yaml 里的 HinterlandLumenChartService 最近在 Redis Streams 流程中出现间歇性问题。 请给出阶段、兼容层、指标、rollback 和 ownership，先不要修改代码。\n\n约束：\n- 继续使用 Redis Streams\n- 保持兼容性和取消语义\n- 改动只限于 HinterlandLumenChartService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"The minimum supported React 19 version in projects/hinterland/Sources/CLI/Commands/Doctor.swift is one patch behind the lockfile. Align that single value and regenerate only the affected metadata.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Wire a HinterlandQuartzPlayerFlow background task in projects/hinterland/app/src/main/SyncWorker.kt that expires abandoned sessions, records an OpenTelemetry span, and yields cleanly when shutdown begins.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Two asks around HinterlandSableParserCoordinator: (1) assess ownership and failure handling in projects/hinterland/Sources/App/SessionStore.swift; (2) capture the contract and rollback note for consumers. Avoid a schema migration in this release, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"HinterlandEchoRegistryCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"HinterlandWillowCodecCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"HinterlandCinderAuthCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Could HinterlandFlintTimelineService migrate incrementally?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"Sketch the HinterlandCopperBridgeService migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Design handed over a final pass for HinterlandWrenExportService, and the basic data flow in projects/hinterland/config/staging.toml already works. 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- avoid a schema migration in this release\n- stay compatible with the existing Redis Streams deployment\n- keep the work scoped to HinterlandWrenExportService and its direct tests\n\nSeveral teams work in this search, Terraform, Flutter 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":"Test Suite 'HinterlandSlateEditorCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[HinterlandSlateEditorCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/hinterland/services/ledger/replay.go:144: error: -[HinterlandSlateEditorCoordinatorTests 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 '-[HinterlandSlateEditorCoordinatorTests 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 HinterlandSlateEditorCoordinator's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Support wants the behavior in projects/hinterland/apps/console/routes/usage.svelte recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary. The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Is HinterlandRavenSessionStore safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"HinterlandLedgerGateCoordinator is blocking the next release because lease renewal code copied across three workers. I need two concrete outcomes from a single pass: produce a consumer guide for HinterlandLedgerGateCoordinator, and give the existing implementation a read-only safety pass. Use the existing React 19 conventions in projects/hinterland/cmd/exporter/main.py; avoid a schema migration in this release. Keep the outcomes distinct so reviewers can see which evidence supports the assessment and which files or prose satisfy the requested change.\n\nConstraints:\n- preserve public wire values and tenant boundaries\n- cover cancellation and retry behavior\n- avoid generated code and unrelated cleanup\n- include a rollback trigger that an on-call engineer can measure\n\nThis is a fresh workstream for the release, so derive everything from the repository and the context here.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Trace: # projects/hinterland/db/migrations/20260730_events.sql\n[worker.hinterlandflinttimelineflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandflinttimelineflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandflinttimelineflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandFlintTimelineFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48132\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 HinterlandFlintTimelineFlow'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":"Responsive layout for HinterlandNimbusFormStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"For HinterlandPrismCacheCoordinator, lay out a staged migration for HinterlandPrismCacheCoordinator; once that is complete, then implement the bounded durable-cursor handler. Work from projects/hinterland/packages/api/openapi.yaml, stay with Redis Streams, and avoid a schema migration in this release. Keep the two outcomes separately reviewable.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Extract HinterlandAsterWebhookStore's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Outline a safer HinterlandGarnetModalService cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"HinterlandSlateEditorService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- avoid a schema migration in this release\n- retain the current Terraform operational envelope\n\nThe relevant code crosses search, Terraform, Flutter. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Does HinterlandIrisBatchStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"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_48135'\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_48135'::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 HinterlandLumenChartFlow'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.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating two validators with subtly different error strings in HinterlandBirchMigratorService, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Give HinterlandFlintTimelineStore a loading skeleton","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Style HinterlandMoonlitSDKService's offline state","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/hinterland/ui/settings/PrivacyPane.tsx b/projects/hinterland/ui/settings/PrivacyPane.tsx\nindex 62d71aa..90f3c1e 100644\n--- a/projects/hinterland/ui/settings/PrivacyPane.tsx\n+++ b/projects/hinterland/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\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Read the artifact above as a skeptical reviewer. Is HinterlandPineMetricsFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Two engineers disagree about whether HinterlandWrenExportStore's cache is authoritative. Walk the reads and writes in projects/hinterland/packages/api/openapi.yaml and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"We need to move HinterlandWillowCodecService from the legacy store to Redis Streams. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Why is HinterlandMicaProfileService stalling?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"HinterlandNovaPickerCoordinator: polish, then document","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"// projects/hinterland/services/ledger/replay.go\nfinal class HinterlandEmberRelayFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandEmberRelayFlow; 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":"projects/hinterland/Sources/CLI/Commands/Doctor.swift now contains HinterlandMarbleTokenService'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.4,"slice":"core","lang":"en"} +{"prompt":"The destination for HinterlandFernSnapshotService is broadly agreed; the missing piece is a reversible route from projects/hinterland/pkg/cache/lease.rs to that target. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandFernSnapshotService\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-48125: retire the legacy replay path for HinterlandPrismCacheFlow\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 HinterlandPrismCacheFlow 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":"HinterlandSableParserService's Doctor.swift needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Diff: The public surface of HinterlandPineMetricsService is frozen, but its internal ownership in projects/hinterland/ui/settings/PrivacyPane.tsx is difficult to test and even harder to change safely. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandPineMetricsService\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"HinterlandBirchMigratorCoordinator: rethink this area","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Ownership of HinterlandIrisBatchService is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- avoid a schema migration in this release\n- retain the current Redis Streams operational envelope\n\nThe relevant code crosses search, Terraform, Flutter. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Profiler: // projects/hinterland/Sources/App/SessionStore.swift\nfinal class HinterlandBirchMigratorFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandBirchMigratorFlow 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":"Could the reasoning behind HinterlandDriftConsoleService's Core Data choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Console: Ticket OPS-48119: retire the legacy replay path for HinterlandCloudReconcilerFlow\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 HinterlandCloudReconcilerFlow 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":"Workspace: diff --git a/projects/hinterland/ui/settings/PrivacyPane.tsx b/projects/hinterland/ui/settings/PrivacyPane.tsx\nindex 62d71aa..90f3c1e 100644\n--- a/projects/hinterland/ui/settings/PrivacyPane.tsx\n+++ b/projects/hinterland/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\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Wire HinterlandBeaconStoreCoordinator'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":"HinterlandHarborIndexStore is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- avoid a schema migration in this release\n- retain the current React 19 operational envelope\n\nThe relevant code crosses search, Terraform, Flutter. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Repository: Could the reasoning behind HinterlandWillowCodecStore's Redis Streams choices be captured as an ADR for engineers joining the project next quarter? The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Assess the HinterlandCedarPolicyService diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"We need to move HinterlandAcornWidgetFlow from the legacy store to React 19. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Move HinterlandEchoRegistryStore'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":"Pipeline: // projects/hinterland/Sources/App/SessionStore.swift\nfinal class HinterlandHarborIndexFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandHarborIndexFlow 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":"HinterlandMapleQueueCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"PM is preparing the HinterlandCedarPolicyStore rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandCedarPolicyStore\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.\n\nThe server contract is the subject, but the requested output is documentation rather than handler code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Find HinterlandCraneWorkspaceService's duplicate retry source","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Gateway: diff --git a/projects/hinterland/ml/pipeline/features.py b/projects/hinterland/ml/pipeline/features.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/hinterland/ml/pipeline/features.py\n+++ b/projects/hinterland/ml/pipeline/features.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\nRead the artifact above as a skeptical reviewer. Is HinterlandRavenSessionFlow'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":"HinterlandVelaDrawerCoordinator: give it a nicer flow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"I inherited HinterlandRainfallDBStore and need a careful read of projects/hinterland/config/staging.toml before I can sign off on the next release. 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- avoid a schema migration in this release\n- stay compatible with the existing Redis Streams deployment\n- keep the work scoped to HinterlandRainfallDBStore and its direct tests\n\nSeveral teams work in this search, Terraform, Flutter 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":"HinterlandAtlasSearchService'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":"Split HinterlandAsterWebhookService without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Renderer: // projects/hinterland/db/migrations/20260730_events.sql\nfinal class HinterlandJuniperCLIFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandJuniperCLIFlow 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":"Since the last release, HinterlandOrbitSyncService has shown duplicate retries after a network handoff; nobody on the team can reproduce it reliably on a laptop. Reconstruct the failing timeline from logs and tests, identify which invariant first breaks, and distinguish causal signals from effects or cleanup noise.\n\nConstraints:\n- avoid a schema migration in this release\n- stay compatible with the existing Core Data deployment\n- keep the work scoped to HinterlandOrbitSyncService and its direct tests\n\nSeveral teams work in this search, Terraform, Flutter monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-48138\n\n08:02 deploy HinterlandBasilRunnerFlow 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 HinterlandBasilRunnerFlow, 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":"Indexer: diff --git a/projects/hinterland/apps/console/routes/usage.svelte b/projects/hinterland/apps/console/routes/usage.svelte\nindex 62d71aa..90f3c1e 100644\n--- a/projects/hinterland/apps/console/routes/usage.svelte\n+++ b/projects/hinterland/apps/console/routes/usage.svelte\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 HinterlandCopperBridgeFlow'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":"HinterlandBasilRunnerCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"HinterlandOspreyJobCoordinator needs a paired pass: separate HinterlandOspreyJobCoordinator's policy from transport without behavior changes, plus give the existing implementation a read-only safety pass. Use projects/hinterland/internal/auth/refresh.go as the source of truth, preserve the Terraform contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Release engineering needs a HinterlandDriftConsoleStore changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition. The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"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_48151'\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_48151'::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\nFind the source of this HinterlandAmberFilterCoordinator symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Sequence HinterlandOspreyJobStore's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Investigate the HinterlandOspreyJobService hang","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Apparently: projects/hinterland/workers/thumbnail/consumer.ex の HinterlandMapleQueueService で、Playwright の flow に断続的な問題が起きています。 現在の flow を読み、ownership、cancel、順序が安全か評価してください。分析だけで十分です。\n\n制約:\n- Playwright を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は HinterlandMapleQueueService のみ","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"ja"} +{"prompt":"HinterlandAsterWebhookCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"HinterlandMarbleTokenCoordinator: handle the lingering thing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-48118\n\n08:02 deploy HinterlandAsterWebhookFlow 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 HinterlandAsterWebhookFlow 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":"Lately: Incident timeline — INC-48154\n\n08:02 deploy HinterlandCoralUploadCoordinator 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 HinterlandCoralUploadCoordinator 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":"HinterlandLumenChartCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"How does HinterlandEmberRelayStore propagate cancellation through the Terraform boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Oddly: Incident timeline — INC-48146\n\n08:02 deploy HinterlandMarbleTokenFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nDetermine why HinterlandMarbleTokenFlow 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":"Translate the HinterlandMoonlitSDKStore setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"For HinterlandRavenSessionCoordinator, separate HinterlandRavenSessionCoordinator's policy from transport without behavior changes; once that is complete, capture the contract and rollback note for consumers. Work from projects/hinterland/cmd/exporter/main.py, stay with React 19, and avoid a schema migration in this release. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"HinterlandKiteSchedulerCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Currently: projects/hinterland/ui/settings/PrivacyPane.tsx 里的 HinterlandMapleQueueStore 最近在 Playwright 流程中出现间歇性问题。 请追踪 queue、scheduler 和取消路径，对比假设，先定位原因再提修改。\n\n约束：\n- 继续使用 Playwright\n- 保持兼容性和取消语义\n- 改动只限于 HinterlandMapleQueueStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"Today: // projects/hinterland/apps/console/routes/usage.svelte\nfinal class HinterlandQuartzPlayerCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandQuartzPlayerCoordinator; 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":"Context: # projects/hinterland/Sources/CLI/Commands/Doctor.swift\n[worker.hinterlandsableparserflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandsableparserflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandsableparserflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandSableParserFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48126\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 HinterlandSableParserFlow'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":"projects/hinterland/crates/index/src/segment.rs now contains HinterlandIrisBatchFlow'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.4,"slice":"core","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current HinterlandAmberFilterService design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandAmberFilterService\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"The data is already available in projects/hinterland/lib/codec/frame.cc; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Background: Incident timeline — INC-48122\n\n08:02 deploy HinterlandOpalRouterFlow 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 HinterlandOpalRouterFlow 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":"How does HinterlandVelaDrawerStore propagate cancellation through the Redis Streams boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"I inherited HinterlandFrostPanelService and need a careful read of projects/hinterland/engine/render/atlas.cpp before I can sign off on the next release. 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- avoid a schema migration in this release\n- stay compatible with the existing Playwright deployment\n- keep the work scoped to HinterlandFrostPanelService and its direct tests\n\nSeveral teams work in this search, Terraform, Flutter 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":"Move HinterlandSpruceDaemonService'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.5,"slice":"core","lang":"en"} +{"prompt":"Could HinterlandCoralUploadStore show the active Terraform 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":"HinterlandSpruceDaemonCoordinator: ship a sensible version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current HinterlandCopperBridgeStore design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandCopperBridgeStore\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"# projects/hinterland/ml/pipeline/features.py\n[worker.hinterlandledgergateflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandledgergateflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandledgergateflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandLedgerGateFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48111\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 HinterlandLedgerGateFlow'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":"Read projects/hinterland/engine/render/atlas.cpp and tell me whether HinterlandBasilRunnerStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-48124: finish the compact HinterlandOspreyJobFlow filter experience\n\nRoute: /catalog/search\nSource: projects/hinterland/infra/modules/edge/main.tf\nFramework: Terraform\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring HinterlandOspreyJobFlow'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":"HinterlandMosaicGridCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Compare the old and new HinterlandSpruceDaemonStore 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":"Center the HinterlandNovaPickerStore modal","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"For HinterlandGarnetModalCoordinator, separate HinterlandGarnetModalCoordinator's policy from transport without behavior changes; once that is complete, capture the contract and rollback note for consumers. Work from projects/hinterland/lib/codec/frame.cc, stay with Playwright, and avoid a schema migration in this release. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"HinterlandCopperBridgeCoordinator: sequence, then restructure","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Two deliverables are holding up HinterlandJuniperCLICoordinator. First, finish HinterlandJuniperCLICoordinator's responsive empty and retry states. In the same workstream, correct the known stale timeout beside it. The relevant starting point is projects/hinterland/src/sync/reconcile.ts, which follows Core Data conventions and currently suffers from duplicate retries after a network handoff. Avoid a schema migration in this release.\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":"# CI job 48121: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: React 19\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] HinterlandTideWorkerFlowIntegration.replays_after_timeout ... ok\n[test] HinterlandTideWorkerFlowIntegration.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 \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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Add the bounded HinterlandTideWorkerFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","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_48137'\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_48137'::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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Determine why HinterlandSpruceDaemonFlow 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":"Collapse the HinterlandOpalRouterService wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Describe HinterlandOpalRouterStore's error envelope","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Fresh release brief for HinterlandFernSnapshotCoordinator:\n- primary outcome: finish HinterlandFernSnapshotCoordinator's responsive empty and retry states\n- companion outcome: give the existing implementation a read-only safety pass\n- repository entry point: projects/hinterland/crates/index/src/segment.rs\n- platform constraint: Redis Streams\n- known complication: an accessibility label that reads the internal enum\n\nBoth results are required, but they should remain independently reviewable. Avoid a schema migration in this release; 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":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"A copied hex color in HinterlandWrenExportFlow lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"HinterlandAcornWidgetService needs a production server path for replaying tenant events; the public envelope is agreed but persistence and retry handling are not wired. Add signed cursor parsing, bounded pagination, key rotation, tenant checks, and a resumable background path with metrics for lag, retries, and terminal failures.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- avoid a schema migration in this release\n- retain the current React 19 operational envelope\n\nThe relevant code crosses search, Terraform, Flutter. Prefer evidence from the repository and make any assumption explicit.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-48144: retire the legacy replay path for HinterlandKiteSchedulerFlow\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 HinterlandKiteSchedulerFlow 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":"Does HinterlandBasilRunnerService enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"The minimum supported Terraform version in projects/hinterland/infra/modules/edge/main.tf 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":"Flip HinterlandTideWorkerService's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"A copied hex color in HinterlandEmberRelayService lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Cadre la migration de HinterlandCloudReconcilerService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"fr"} +{"prompt":"Ticket OPS-48129: retire the legacy replay path for HinterlandMoonlitSDKFlow\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À partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. From this evidence, draft consumer-facing migration guidance for HinterlandMoonlitSDKFlow, 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":"HinterlandAtlasSearchCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Test Suite 'HinterlandWrenExportCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[HinterlandWrenExportCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/hinterland/packages/api/openapi.yaml:144: error: -[HinterlandWrenExportCoordinatorTests 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 '-[HinterlandWrenExportCoordinatorTests 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\nFinish the visible HinterlandWrenExportCoordinator 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":"Question: The next client release depends on a new HinterlandSlateEditorStore capability in projects/hinterland/services/ledger/replay.go, with Terraform already chosen by the platform group. Wire the schema, repository, handler, and worker so duplicate deliveries return the original result and shutdown never acknowledges uncommitted work.\n\nConstraints:\n- avoid a schema migration in this release\n- stay compatible with the existing Terraform deployment\n- keep the work scoped to HinterlandSlateEditorStore and its direct tests\n\nSeveral teams work in this search, Terraform, Flutter monorepo, so keep ownership and handoff points understandable in a small review.\n\nThe contract notes are context; the requested outcome is the working server path.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"HinterlandEmberRelayCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"This should remain a deliberately small patch: HinterlandJuniperCLIStore has one known configuration mistake in projects/hinterland/src/sync/reconcile.ts, not an open-ended failure investigation. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- avoid a schema migration in this release\n- stay compatible with the existing Core Data deployment\n- keep the work scoped to HinterlandJuniperCLIStore and its direct tests\n\nSeveral teams work in this search, Terraform, Flutter monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Collapse the HinterlandNimbusFormService wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Release engineering needs a HinterlandAcornWidgetStore 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 HinterlandBeaconStoreFlow'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.5,"slice":"core","lang":"en"} +{"prompt":"Observation: Move HinterlandTideWorkerStore behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Two asks around HinterlandFlintTimelineCoordinator: (1) assess ownership and failure handling in projects/hinterland/src/sync/reconcile.ts; (2) capture the contract and rollback note for consumers. Avoid a schema migration in this release, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Constraint: // projects/hinterland/db/migrations/20260730_events.sql\nfinal class HinterlandOrbitSyncCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nDeliver the HinterlandOrbitSyncCoordinator server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"HinterlandCloudReconcilerCoordinator: sequence, then ship","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"HinterlandOpalRouterCoordinator: ship, then correct","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"} +{"prompt":"Remove HinterlandGarnetModalStore's stray comma","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Request: # projects/hinterland/Sources/App/SessionStore.swift\n[worker.hinterlandacornwidgetcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandacornwidgetcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandacornwidgetcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandAcornWidgetCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48156\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 HinterlandAcornWidgetCoordinator'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":"Split projects/hinterland/apps/console/routes/usage.svelte by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Vereinheitliche die HinterlandCloudReconcilerStore-Validatoren","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"de"} +{"prompt":"# projects/hinterland/engine/render/atlas.cpp\n[worker.hinterlandgarnetmodalflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandgarnetmodalflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandgarnetmodalflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandGarnetModalFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48128\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/hinterland/engine/render/atlas.cpp and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"HinterlandNimbusFormCoordinator needs a paired pass: separate HinterlandNimbusFormCoordinator's policy from transport without behavior changes, plus give the existing implementation a read-only safety pass. Use projects/hinterland/crates/index/src/segment.rs as the source of truth, preserve the Redis Streams contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"$ pnpm test --filter HinterlandSummitProxyFlow\n RUN v3.2.4 /workspace/apps/console\n × HinterlandSummitProxyFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=48147 phase=resume storedCursor=seg-0183\n session=48147 phase=fetch requestCursor=seg-0183 pageSize=200\n session=48147 phase=commit receivedCursor=seg-0184 itemCount=0\n session=48147 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nReconstruct the HinterlandSummitProxyFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Find HinterlandSableParserStore's duplicate retry source","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"HinterlandSummitProxyCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Fresh release brief for HinterlandPineMetricsCoordinator:\n- primary outcome: produce a consumer guide for HinterlandPineMetricsCoordinator\n- companion outcome: give the existing implementation a read-only safety pass\n- repository entry point: projects/hinterland/workers/thumbnail/consumer.ex\n- platform constraint: Playwright\n- known complication: a query plan that changes after statistics refresh\n\nBoth results are required, but they should remain independently reviewable. Avoid a schema migration in this release; 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":"writing","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Please turn HinterlandAmberFilterStore'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":"The data is already available in projects/hinterland/infra/modules/edge/main.tf; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Polish the HinterlandNovaPickerService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating a misleading timeout name used in five packages in HinterlandOrbitSyncFlow, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Goal: Ticket OPS-48149: retire the legacy replay path for HinterlandAtlasSearchFlow\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 HinterlandAtlasSearchFlow 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":"HinterlandHarborIndexCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Symptom: The name pendingAck means two different things across HinterlandFrostPanelFlow's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Where did HinterlandCraneWorkspaceStore's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current HinterlandQuartzPlayerService design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandQuartzPlayerService\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Persist HinterlandAtlasSearchStore delivery attempts in projects/hinterland/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":"// projects/hinterland/crates/index/src/segment.rs\nfinal class HinterlandCraneWorkspaceFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandCraneWorkspaceFlow'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":"Polish the HinterlandRavenSessionService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Headsup: A flaky failure around HinterlandCoralUploadService survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandCoralUploadService\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"FYI: // projects/hinterland/internal/auth/refresh.go\nfinal class HinterlandCinderAuthFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandCinderAuthFlow 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":"Meanwhile: A copied hex color in HinterlandVelaDrawerService lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"HinterlandRainfallDBService flakes under UTC","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Describe HinterlandHarborIndexService's error envelope","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"HinterlandCinderAuthService's staging timeout is already known to be wrong: change the single projects/hinterland/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":"Move HinterlandSlateEditorFlow'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":"2026-07-30T08:14:11.409Z level=info service=hinterlandmosaicgridflow pod=hinterlandmosaicgridflow-7cf8 request_id=48148 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=hinterlandmosaicgridflow request_id=48148 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=hinterlandmosaicgridflow request_id=48148 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=hinterlandmosaicgridflow request_id=48148 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=hinterlandmosaicgridflow request_id=48148 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=hinterlandmosaicgridflow request_id=48148 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=hinterlandmosaicgridflow request_id=48148 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=hinterlandmosaicgridflow request_id=48148 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nFind the source of this HinterlandMosaicGridFlow symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"How should HinterlandPrismCacheStore be decomposed?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"HinterlandCraneWorkspaceCoordinator: sequence, then restructure","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Locally: # projects/hinterland/internal/auth/refresh.go\n[worker.hinterlandcedarpolicyflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandcedarpolicyflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandcedarpolicyflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandCedarPolicyFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48114\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 HinterlandCedarPolicyFlow'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":"Read projects/hinterland/internal/auth/refresh.go and tell me whether HinterlandKiteSchedulerStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"HinterlandTideWorkerCoordinator: sequence, then polish","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-48110\n\n08:02 deploy HinterlandFernSnapshotFlow 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 HinterlandFernSnapshotFlow 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":"Test Suite 'HinterlandMapleQueueFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[HinterlandMapleQueueFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/hinterland/workers/thumbnail/consumer.ex:144: error: -[HinterlandMapleQueueFlowTests 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 '-[HinterlandMapleQueueFlowTests 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\nFinish the visible HinterlandMapleQueueFlow 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":"One contained cleanup in projects/hinterland/cmd/exporter/main.py: remove the obsolete HinterlandEchoRegistryService import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"What is the safest way to split projects/hinterland/app/src/main/SyncWorker.kt into independently owned modules while HinterlandSummitProxyService's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"Test Suite 'HinterlandEchoRegistryFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[HinterlandEchoRegistryFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/hinterland/cmd/exporter/main.py:144: error: -[HinterlandEchoRegistryFlowTests 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 '-[HinterlandEchoRegistryFlowTests 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 HinterlandEchoRegistryFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"The HinterlandCinderAuthStore 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":"Could HinterlandMosaicGridService show the active Playwright 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":"Is there a cleaner way to separate HinterlandBeaconStoreStore'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":"En projects/hinterland/cmd/exporter/main.py, HinterlandLedgerGateStore tiene un problema intermitente en el flujo de React 19. Separa responsabilidades y elimina duplicación, conservando API, wire values, orden y comportamiento observable.\n\nRestricciones:\n- seguir con React 19\n- conservar compatibilidad y cancelación\n- limitar el cambio a HinterlandLedgerGateStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con React 19 alrededor de HinterlandLedgerGateStore.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"es"} +{"prompt":"Three teams extended HinterlandPineMetricsStore independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- avoid a schema migration in this release\n- retain the current Playwright operational envelope\n\nThe relevant code crosses search, Terraform, Flutter. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"HinterlandCedarPolicyCoordinator is blocking the next release because two validators with subtly different error strings. I need two concrete outcomes from a single pass: lay out a staged migration for HinterlandCedarPolicyCoordinator, and consolidate the duplicated normalization paths without changing behavior. Use the existing Terraform conventions in projects/hinterland/infra/modules/edge/main.tf; avoid a schema migration in this release. 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.9,"slice":"mixed","lang":"en"} +{"prompt":"Two deliverables are holding up HinterlandRainfallDBCoordinator. First, produce a consumer guide for HinterlandRainfallDBCoordinator. In the same workstream, correct the known stale timeout beside it. The relevant starting point is projects/hinterland/config/staging.toml, which follows Redis Streams conventions and currently suffers from memory growth during hour-long imports. Avoid a schema migration in this release.\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":"writing","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Em projects/hinterland/config/staging.toml, o HinterlandLumenChartStore tem um problema intermitente no fluxo de Redis Streams. Siga queue, scheduler e cancelamento, compare hipóteses e encontre a causa antes de mudar código.\n\nRestrições:\n- continuar com Redis Streams\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao HinterlandLumenChartStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"pt"} +{"prompt":"Two asks around HinterlandMoonlitSDKCoordinator: (1) assess ownership and failure handling in projects/hinterland/services/ledger/replay.go; (2) capture the contract and rollback note for consumers. Avoid a schema migration in this release, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Drop HinterlandMicaProfileStore's unused import","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-48130\n\n08:02 deploy HinterlandNimbusFormFlow 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 HinterlandNimbusFormFlow 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":"HinterlandDriftConsoleCoordinator: sort out the rough edge","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Production: // projects/hinterland/packages/api/openapi.yaml\nfinal class HinterlandRainfallDBFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 HinterlandRainfallDBFlow; 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":"Staging: # projects/hinterland/lib/codec/frame.cc\n[worker.hinterlandfrostpanelcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.hinterlandfrostpanelcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.hinterlandfrostpanelcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.HinterlandFrostPanelCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-48158\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/hinterland/lib/codec/frame.cc and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"HinterlandFernSnapshotStore is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- avoid a schema migration in this release\n- retain the current Redis Streams operational envelope\n\nThe relevant code crosses search, Terraform, Flutter. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"// projects/hinterland/config/staging.toml\nfinal class HinterlandVelaDrawerFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Walk through what the artifact proves about HinterlandVelaDrawerFlow; 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":"HinterlandDeltaCanvasCoordinator needs a paired pass: change HinterlandDeltaCanvasCoordinator's known staging timeout from 15 to 30 seconds, plus give the existing implementation a read-only safety pass. Use projects/hinterland/apps/console/routes/usage.svelte as the source of truth, preserve the Core Data contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"CI: The behavior of HinterlandJuniperCLIService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/hinterland/db/migrations/20260730_events.sql. 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- touch generated artifacts only through their checked-in generator\n- avoid a schema migration in this release\n- retain the current Core Data operational envelope\n\nThe relevant code crosses search, Terraform, Flutter. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"PM needs a concise migration note for HinterlandOrbitSyncStore, 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":"Nobody is asking for code changes yet; we first need to understand whether the current HinterlandFrostPanelStore design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside HinterlandFrostPanelStore\n- avoid a schema migration in this release\n\nThis repository spans search, Terraform, Flutter; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Documente o contrato de HinterlandDeltaCanvasService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"pt"} +{"prompt":"The name pendingAck means two different things across HinterlandMarbleTokenStore's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Atlas: projects/hinterland/cmd/exporter/main.py の HinterlandAmberFilterFlow で、React 19 の flow に断続的な問題が起きています。 queue、scheduler、cancel 経路を追い、仮説を比較して、変更前に原因を特定してください。\n\n制約:\n- React 19 を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は HinterlandAmberFilterFlow のみ","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"} +{"prompt":"In projects/hinterland/ml/pipeline/features.py hat HinterlandLedgerGateService ein sporadisches Problem im React 19-Ablauf. Verfolge Queue, Scheduler und Abbruch, vergleiche Hypothesen und finde die Ursache vor jeder Änderung.\n\nRandbedingungen:\n- React 19 weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf HinterlandLedgerGateService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um HinterlandLedgerGateService mit React 19 kompatibel.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} +{"prompt":"Beacon: Incident timeline — INC-48150\n\n08:02 deploy HinterlandIrisBatchCoordinator 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 HinterlandIrisBatchCoordinator 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"} diff --git a/data/round2-09.jsonl b/data/round2-09.jsonl index de35791..c4a6e80 100644 --- a/data/round2-09.jsonl +++ b/data/round2-09.jsonl @@ -1,200 +1,200 @@ -{"prompt": "the exam thing", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "our staging kafka has one partition and prod has twelve, which is why ordering bugs never show up first", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "attempt state machine is spread across four files as boolean columns and ad-hoc checks:\n\nattempt.startedAt // set on create\nattempt.submittedAt // set on submit, also set by the nightly auto-submit job\nattempt.gradedAt // set by the grading worker\nattempt.voidedAt // set by support scripts only\nattempt.mergedIntoId // set by the merge script, and the old attempt keeps its submittedAt\n\nchecks like `if (attempt.submittedAt && !attempt.gradedAt)` appear in eleven places, three of which forget voidedAt, and the review screen's definition of \"latest attempt\" is different again", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "one grading calculation, three call sites", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "our exam load is 40,000 concurrent students for two hours twice a year and idle the rest of the time", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "the WMS has two definitions of \"aisle available\" — the dispatcher's, which asks whether any robot could enter, and the console's, which asks whether a human could — and during maintenance they disagree in the dangerous direction. reconcile them into one predicate with an explicit meaning, keep the console's display identical for the normal case, and tell me which existing callers change behaviour", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "quiz submissions vanish for a handful of students each exam and this is all we get:\n\nPrismaClientKnownRequestError:\nInvalid `prisma.submission.create()` invocation:\n\nUnique constraint failed on the fields: (`attemptId`,`questionId`)\n at RequestHandler.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:6412)\n at async POST (/app/app/api/attempts/[id]/answers/route.ts:41:22)\n\n attemptId: 'atmp_01HR9K2M'\n questionId: 'q_88412'\n studentId: 'usr_4471'\n retryCount: 2\n clientTimestamp: 2026-07-29T11:02:14.881Z\n serverTimestamp: 2026-07-29T11:02:19.114Z\n\nthe client retries on a slow response, and the student sees their answer disappear from the review screen afterwards", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "detection rules stopped firing overnight and the pipeline claims everything is healthy:\n\n[ingest] 2026-07-29T02:00:04Z bulk index 8,412 docs into logs-edr-2026.07.29 took 412ms\n[ingest] 2026-07-29T02:00:09Z bulk index 8,118 docs took 388ms\n[rules] 2026-07-29T02:01:00Z executing 141 rules over window [01:56:00, 02:01:00]\n[rules] 2026-07-29T02:01:04Z 0 alerts generated (previous run: 22)\n[rules] 2026-07-29T02:06:00Z executing 141 rules over window [02:01:00, 02:06:00]\n[rules] 2026-07-29T02:06:03Z 0 alerts generated\n[ingest] 2026-07-29T02:07:11Z index logs-edr-2026.07.30 created\n\nthe index for tomorrow's date appearing at 02:07 is the only odd thing i can see, and our rules query `logs-edr-*` with a `@timestamp` range", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "robot cards should sort problems first", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "what counts as the latest attempt?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "a district's procurement requires WCAG 2.2 AA conformance, per-student time extensions and a VPAT within six weeks, and we have none of those. i want the realistic plan: what we can genuinely fix, what we have to declare as a gap with a remediation date, and how we word a VPAT that is honest without losing the contract", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "one enrichment provider interface", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "attempt state as an enum, not five columns", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "task API is what the robot firmware integrates against, documented in a wiki page from 2023:\n\nGET /v1/tasks/next?robot_id=&capabilities=\n long-polls for up to 30 seconds; returns 204 when nothing is available\n a returned task is leased for 90 seconds and must be acked or it returns to the queue\nPOST /v1/tasks/{id}/ack { robot_id, accepted: bool, reason? }\nPOST /v1/tasks/{id}/progress { robot_id, node, percent }\nPOST /v1/tasks/{id}/complete { robot_id, outcome: \"done\"|\"failed\"|\"aborted\", detail? }\n completing a task that has already been requeued returns 409 and the robot must stop\n progress after the lease expires is accepted but ignored, which firmware treats as success\n\nwrite the integration reference; the lease semantics and the ignored-progress behaviour are what firmware keeps getting wrong", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "three places compute a student's grade and they disagree in the third decimal:\n\n// app/lib/grades.ts — student view\nconst grade = assessments.reduce((sum, a) =>\n sum + Math.round(scoreFor(a) * 10) / 10 * a.weight, 0)\n\n// GradeService.java — teacher view\ntotal = total.add(s.getScore().multiply(a.getWeight())); // BigDecimal, rounded once at the end\n\n-- exports/grades.sql\nSELECT round(sum(s.score * a.weight)::numeric, 1) FROM ...\n\nthe teacher view is the one the institution treats as authoritative, and all three are visible to different users on the same day", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "rule engine has three ways to express the same condition and analysts use all of them:\n\n# style 1 — lucene string\nquery: 'event.code:5145 and winlog.event_data.ShareName:\"\\\\\\\\*\\\\IPC$\"'\n\n# style 2 — elasticsearch DSL, raw\nquery_dsl: { bool: { filter: [ { term: { \"event.code\": \"5145\" } } ] } }\n\n# style 3 — our own yaml shorthand, added last year\nmatch:\n event.code: 5145\n winlog.event_data.ShareName: \"*IPC$\"\n\nall three go through different code paths, only style 3 validates field names, and style 2 lets an analyst write a query that scans every index we have", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "is our tenant filter applied everywhere?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "exam week is three weeks away, lost answers are our most damaging bug, and the attempt model has assumptions in it that stopped being true when students started using two devices. i'd like the plan for what we change before exams and what we deliberately leave until after, with the risk of each decision written down so nobody relitigates it at midnight during the exam support has forty tickets from last term's exams if you want the failure patterns.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "we need a position on how the LMS syncs with student information systems, given opaque ids that change each academic year and a district that rate limits us to ten requests a second. design it, then implement the resumable sync loop so we can test against their sandbox their sandbox is available and their ids change every august, which is the awkward part.", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "detection rule for lateral movement, which the security team says has too many false positives:\n\nname: Suspicious SMB session enumeration\nindex: logs-edr-*\nquery: |\n event.code:5145 and winlog.event_data.ShareName:\"\\\\\\\\*\\\\IPC$\"\n and winlog.event_data.RelativeTargetName:(\"srvsvc\" or \"wkssvc\" or \"samr\")\ninterval: 5m\nwindow: 5m\nthreshold:\n field: source.ip\n value: 10\nseverity: high\nsuppression: none\n\nfires about 40 times a day, almost always from the same six management servers, and nobody has tuned it since it was imported from a blog post", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "robot one, again", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "a student's grade is computed three times in three languages and the three disagree in the third decimal, with the teacher's view treated as authoritative by the institution. consolidate onto that behaviour, keep the exports byte-identical where they already agree, and list every student whose displayed grade will change as a result the institution treats the teacher's view as authoritative and will not accept a change to it.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "quiz player has to survive exam conditions, which means an autosave state that never lies, a keyboard-operable navigator, a timer that doesn't shout every second, and a graceful fallback when javascript dies mid-exam. build it to the spec, and tell me which of those the current player gets wrong today forty thousand students sit exams in the same two-hour window twice a year.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "what does a bulk index rejection actually do to the events in that batch — are they lost or retried", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "inventory counts drift from reality by a few units a day and reconciliation can't explain it:\n\ntask 88401 PICK sku=SKU-4471 qty=3 from=A7-03-02 robot=R-041 status=COMPLETED at=11:02:14\ntask 88402 PICK sku=SKU-4471 qty=2 from=A7-03-02 robot=R-018 status=COMPLETED at=11:02:16\ninventory event sku=SKU-4471 location=A7-03-02 delta=-3 source=task-88401 at=11:02:19\ninventory event sku=SKU-4471 location=A7-03-02 delta=-2 source=task-88402 at=11:02:19\ncycle count sku=SKU-4471 location=A7-03-02 counted=4 system=2 at=18:00:00\n\nboth picks were dispatched from a snapshot showing 5 units, and the location physically held 5", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "robots collide at aisle intersections about once a week and the traffic manager logs look reasonable:\n\n11:02:14.101 [traffic] R-041 requests reservation for node N-A7-INT (aisle A7 intersection)\n11:02:14.104 [traffic] reservation granted to R-041, expires 11:02:44\n11:02:14.112 [traffic] R-018 requests reservation for node N-A7-INT\n11:02:14.115 [traffic] reservation denied, held by R-041\n11:02:14.118 [traffic] R-018 enters waiting state\n11:02:29.881 [traffic] R-041 heartbeat missed (last 11:02:14.104)\n11:02:29.884 [traffic] reservation for N-A7-INT released (holder unresponsive)\n11:02:29.887 [traffic] reservation granted to R-018\n11:02:31.114 [traffic] R-041 heartbeat resumed, continues along reserved path\n\nR-041 kept moving through the intersection during those fifteen seconds", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "elasticsearch rejects writes during our morning peak and the cluster looks healthy otherwise:\n\n{\n \"error\": {\n \"type\": \"es_rejected_execution_exception\",\n \"reason\": \"rejected execution of coordinating operation [coordinating_and_primary_bytes=0, replica_bytes=0, all_bytes=0, coordinating_operation_bytes=104857600, max_coordinating_and_primary_bytes=104857600]\"\n },\n \"status\": 429\n}\n\nnode stats:\n indexing.index_current: 412\n thread_pool.write.queue: 200 (capacity 200)\n thread_pool.write.rejected: 41,882\n jvm.mem.heap_used_percent: 71\n indices.indexing.index_time_in_millis rate: 88ms/doc\n\nwe bulk index in 50MB batches from four ingest workers", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "reservation logic in the traffic manager, which decides whether robots can enter a node:\n\npublic boolean tryReserve(String nodeId, String robotId, Duration ttl) {\n Reservation existing = reservations.get(nodeId);\n if (existing != null && !existing.isExpired(clock.instant())) {\n return false;\n }\n reservations.put(nodeId, new Reservation(robotId, clock.instant().plus(ttl)));\n return true;\n}\n\npublic void heartbeat(String robotId) {\n lastSeen.put(robotId, clock.instant());\n}\n\n// separate thread, every second\nreservations.entrySet().removeIf(e ->\n Duration.between(lastSeen.getOrDefault(e.getValue().robotId(), Instant.EPOCH), clock.instant()).getSeconds() > 15);\n\nis releasing a reservation on a missed heartbeat sound, given a robot that's still physically moving?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "design doc for our attempt model, written before the exam pilot. does it survive contact with 40,000 students?\n\n## Attempts\nAn attempt is created when a student opens a quiz and holds every answer as a row. Answers are upserted as the student progresses, so a lost connection loses nothing. An attempt is submitted once; submission is idempotent.\n\n## Assumptions\n- A student has one attempt open at a time.\n- Answers are small and can be written on every keystroke pause.\n- The client is authoritative for question order.\n\n## Not covered\nProctoring. Offline attempts. Two devices on the same attempt.\n\nstudents routinely open a quiz on a laptop and a phone, and \"upserted\" is a create in the code", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "kafka consumer config for the robot fleet, which rebalances constantly:\n\nmax.poll.records: 500\nmax.poll.interval.ms: 300000\nsession.timeout.ms: 10000\nheartbeat.interval.ms: 3000\nenable.auto.commit: true\nauto.commit.interval.ms: 5000\nfetch.min.bytes: 1\ngroup.instance.id: (unset)\n\ntwelve robots, each a consumer in the same group, each processing a task for up to 90 seconds; robots go offline briefly when they pass through the racking in aisle A7", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "npm audit before the exam period freeze, what goes in:\n\nnext 14.2.0 - 14.2.29\nSevere: Server-Side Request Forgery in Next.js image optimisation\nfix available via `npm audit fix --force`\nWill install next@15.4.2, which is a breaking change\n\n@prisma/client 5.14.0 - 5.19.1\nModerate: Prisma Client leaks connection strings in error messages\nfix available via `npm audit fix`\n\nsharp 0.32.0 - 0.33.4\nHigh: Denial of service via crafted image\nfix available via `npm audit fix`\n\n4 vulnerabilities (1 moderate, 2 high, 1 severe)\n\nwe are three weeks from exam week and the next major is a two-day migration", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "enrichment providers each handle failure differently, which is why one slow provider stalls everything:\n\n# asn.py\nresp = requests.get(url) # no timeout at all\nreturn resp.json()[\"asn\"]\n\n# geo.py\ntry:\n resp = requests.get(url, timeout=2)\nexcept requests.Timeout:\n return None # silently unenriched\n\n# threatintel.py\nfor attempt in range(5):\n try: return requests.get(url, timeout=10).json()\n except Exception: time.sleep(attempt) # up to 10 seconds of sleeping in the pipeline\n\n# internal_assets.py\nreturn self.cache[ip] # KeyError propagates and kills the batch", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "accessibility requirement from a district's procurement, which we have to answer honestly:\n\n\"The platform shall conform to WCAG 2.2 AA. All assessment activities shall be completable using a keyboard alone and with a screen reader. Time limits shall be adjustable or extendable by an instructor for individual students. Content shall not rely on colour alone to convey meaning. The supplier shall provide a current VPAT and a remediation plan for any non-conformance.\"\n\nour quiz navigation is mouse-only in two places, time limits are per-assessment with no per-student override, and we have never produced a VPAT. i want the plan, the honest gaps, and what we can claim by the deadline in six weeks", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "bulk batches down to 5MB", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "alert list should support j and k", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "triage view needs a dark theme default", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "why does the group rebalance so often?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "aisle screen", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "teachers are dealing with duplicate attempts, an auto-submit job they don't know about and a review screen that shows only the latest attempt, and every one of those has generated support tickets this term. write the page that explains attempts as they actually work, in language a teacher will read the week before exams rather than during them the page should be readable in five minutes by someone who has never filed a support ticket.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "warehouse runbook still describes the conveyor system that was removed two years ago, and the robot procedures live in the shift supervisors' heads. write the runbook for the robot fleet, ordered by what someone woken at three in the morning needs first, and be explicit about which actions are never safe during operations the supervisors printing this will have it laminated, so keep it short and ordered.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "an auditor has asked six questions about telemetry collection, retention, tenant isolation, alert deletion, rule versioning and orphaned alerts, and at least three of our honest answers are unflattering. write the controls document from the code, marking what we can't substantiate rather than smoothing over it our compliance lead reads it first and would rather see a gap than a confident half-truth.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "nobody can tell me whether a robot that loses wifi mid-aisle can have its reservation given away while it is still moving, or whether some other interlock saves us. read the traffic manager, the heartbeat handling and the sweep together, and tell me exactly what sequence of events produces the situation we saw in May", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "i'd like an honest read of whether our tenant isolation can be bypassed by a crafted rule, given that rules can specify their own index pattern, and the fix if it can", "purpose": "review", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "instructor dashboard times out for two institutions that are up for renewal, and i want the diagnosis before the rewrite. work out where the time actually goes, then restructure the query so it returns in under a second at their size both institutions are up for renewal, so a number i can quote would help.", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "rule versioning needs designing and starting in the same quarter. give me the model — immutable versions, alert references, what deletion means — then build the versions table and the write path so new alerts start carrying a version immediately", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "task API reference has to exist for the firmware team, and while writing it i'd like confirmation that late progress reports really are accepted and ignored, because the firmware treats that as success", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "three prisma query styles for a teacher's courses disagree about archived courses and one bypasses row-level security entirely. unify them, and tell me whether that raw query has been leaking other teachers' courses this whole time", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "is the grading recalculation safe to run concurrently for the same enrolment, or are we relying on luck", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "exam timer keeps counting while the browser tab is backgrounded on ios, which it shouldn't", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "we need a plan for running two warehouse sites from one WMS instance without them affecting each other", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "the aisle drain command should refuse while robots are inside and report which ones are blocking, rather than draining tasks and leaving the robots stranded mid-aisle as it does today. it also needs to be safe to call repeatedly from the console by a supervisor who is watching the screen rather than reading the response", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "our ingestion, enrichment and rules services each define their own dataclasses for the same event schema, which is why a field rename last month silently dropped enrichment for one event type. give them one shared schema definition with versioning, and confirm from a day of production events that nothing is parsed differently afterwards a field rename last month silently dropped enrichment for one event type and nobody noticed for a week.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "attempt design doc claims answers are upserted and submission is idempotent, and neither is true in the code as far as i can tell. go through the doc claim by claim against the current implementation and tell me which parts are aspirational, because exam week is close and i need to know what we actually have exam week is close enough that i need to know what we actually have rather than what we meant.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "one query style for detection rules", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "our three LMS components each implement optimistic updates with a different rollback strategy, and the quiz one rolls back to a value that may already be stale. unify them behind one approach, and while you're in there tell me whether the quiz rollback has ever silently discarded a saved answer", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "the course cache is a module-level Map with no eviction and it is most of our memory growth in production. put a bound and a TTL on it, then confirm from the request pattern whether caching there is worth keeping at all", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.55, "slice": "mixed", "lang": "en"} -{"prompt": "quiz navigator and the drag-to-order questions both fail the accessibility audit and both need keyboard alternatives. fix them, and write the VPAT section covering assessment activities", "purpose": "frontendImpl", "secondary": "writing", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "detection rules are written in three different syntaxes because we added a friendlier one without removing the others, and only the newest validates field names. before consolidating i want a view on whether we can migrate existing rules automatically, what we'd break for analysts who write raw DSL, and whether the friendlier syntax is expressive enough for the rules that matter", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "robot firmware team integrates against our task API from a wiki page written in 2023, and the two things they consistently get wrong are lease expiry and the fact that late progress reports are accepted but ignored. write the reference documentation with those two impossible to misread, including what a robot should do when it gets a 409 the firmware release cycle is six weeks, so anything ambiguous costs us a quarter.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "what guarantees does our nightly sync make when the district's API returns a partial page", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "a walkthrough of how a pick becomes an inventory movement would help before i touch reconciliation", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "one aisle stops receiving tasks", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "attempt lifecycle is five nullable timestamp columns and eleven ad-hoc checks, three of which forget the voided case entirely. model it as an explicit state machine, migrate the existing rows including the merged ones, and keep every current query returning the same rows it does today the merged attempts from the support scripts are the awkward rows, and there are about two hundred.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "pick tasks stop flowing to one aisle every few days, kafka side looks fine to me:\n\n2026-07-29T11:02:14Z INFO [task-dispatcher] assigning task 88412 to robot R-041 aisle=A7\n2026-07-29T11:02:14Z INFO [task-dispatcher] produced to topic wms.tasks partition=3 offset=41882104\n2026-07-29T11:02:44Z WARN [task-dispatcher] no ack from R-041 after 30s, task 88412 requeued\n2026-07-29T11:03:14Z WARN [task-dispatcher] no ack from R-041 after 30s, task 88412 requeued\n2026-07-29T11:03:44Z ERROR [task-dispatcher] task 88412 exceeded requeue limit, dead-lettered\n2026-07-29T11:03:45Z INFO [consumer-group wms-robots] rebalance triggered, 12 members\n2026-07-29T11:03:52Z INFO [consumer-group wms-robots] rebalance complete, R-041 assigned partitions [3]\n\nrebalances happen every few minutes and R-041's logs show it never received the task at all", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "course player buffers on video for one school district and nobody else:\n\nnetwork tab, same lesson, two sites:\n district A: GET /media/lesson-4471/hls/720p/seg_00041.ts 200 1.2MB ttfb 2,841ms total 8,112ms\n district B: GET /media/lesson-4471/hls/720p/seg_00041.ts 200 1.2MB ttfb 88ms total 214ms\n\nresponse headers (district A):\n x-cache: MISS\n age: 0\n cf-ray: 8f2b1c40-ORD\n vary: Origin, Accept-Encoding, Cookie\n\ndistrict A's proxy adds a `Cookie` header to every media request, district B's doesn't", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "SIEM's enrichment lookups time out under load and the queue backs up:\n\npy-spy dump --pid 41221:\nThread 0x7f1a (active): \"MainThread\"\n _wait_for_tstate_lock (threading.py:1116)\n join (threading.py:1096)\n enrich_batch (enrichment/pipeline.py:141)\n process (enrichment/pipeline.py:88)\nThread 0x7f2b (idle): \"enrich-0\"\n read (socket.py:718)\n _read_status (http/client.py:280)\n getresponse (http/client.py:1428)\n lookup_asn (enrichment/providers/asn.py:41)\n\n... 63 more idle threads, all in lookup_asn\n\nthe ASN provider has no timeout set on its session, and we spawn one thread per event in a batch of 500", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "las notas calculadas no coinciden con las que ven los profesores, aquí un caso:\n\nalumno 4471, curso \"Álgebra II\"\n tarea 1 nota 8,5 peso 20%\n tarea 2 nota 7,0 peso 20%\n examen nota 6,5 peso 60%\n\ncálculo esperado: 8,5*0,2 + 7,0*0,2 + 6,5*0,6 = 7,00\ncálculo mostrado en el panel del profesor: 7,00\ncálculo mostrado al alumno: 7,33\ncálculo en el export CSV: 7,0\n\nel panel del alumno redondea antes de ponderar, y el export usa una consulta distinta escrita hace dos años", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "es"} -{"prompt": "next.js app leaks memory in production and the pod restarts every few hours:\n\nheap snapshot comparison (30 min apart):\n (array) +412 MB +1,204,118 objects\n Prisma.QueryEngine +188 MB\n (closure) +141 MB +882,441 objects\n Response +88 MB\n Map +41 MB\n\nretainers for the largest (array):\n global → cacheMap → Map → entries → Array\n app/lib/courseCache.ts:22\n\ncourseCache is a module-level Map keyed by course id, populated on every request, never evicted, and the server runs in a long-lived node process", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "grading service's concurrency, which i'd like a second opinion on before we scale it up:\n\n@Transactional\npublic Grade recalculate(Long enrolmentId) {\n Enrolment e = enrolments.findById(enrolmentId).orElseThrow();\n List subs = submissions.findByEnrolment(e.getId());\n BigDecimal total = BigDecimal.ZERO;\n for (Assessment a : e.getCourse().getAssessments()) {\n Submission s = subs.stream().filter(x -> x.getAssessmentId().equals(a.getId()))\n .max(comparing(Submission::getAttempt)).orElse(null);\n if (s == null) continue;\n total = total.add(s.getScore().multiply(a.getWeight()));\n }\n e.setGrade(total.setScale(2, RoundingMode.HALF_UP));\n return grades.save(new Grade(e, total));\n}\n\nthis runs on submission, on assessment weight changes, and nightly for every enrolment in the institution", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "bitte einmal drüberschauen, bevor das in die Prüfungsphase geht:\n\nexport async function POST(req: Request, { params }: { params: { id: string } }) {\n const body = await req.json()\n const attempt = await prisma.attempt.findUnique({ where: { id: params.id } })\n if (!attempt) return new Response(\"not found\", { status: 404 })\n if (attempt.submittedAt) return new Response(\"already submitted\", { status: 409 })\n await prisma.answer.create({\n data: { attemptId: attempt.id, questionId: body.questionId, value: body.value },\n })\n return Response.json({ ok: true })\n}\n\nder Client sendet bei langsamer Verbindung erneut, und es gibt keinen Idempotenzschlüssel; in der Prüfungswoche sind das 40.000 gleichzeitige Versuche", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "de"} -{"prompt": "ingestion pipeline's batching, which i suspect is why elasticsearch rejects us:\n\ndef run(self):\n batch = []\n for event in self.source:\n batch.append(self.transform(event))\n if len(batch) >= self.batch_size: # batch_size = 10_000\n self.es.bulk(body=batch, request_timeout=120)\n batch = []\n if batch:\n self.es.bulk(body=batch, request_timeout=120)\n\nfour workers run this, batch_size is 10,000 documents which averages 50MB, there's no retry on 429, and a rejected bulk loses the whole batch silently because we don't check the per-item response", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "query behind the instructor dashboard, which times out for our largest institution:\n\nSELECT c.id, c.title, count(distinct e.student_id) AS students,\n avg(g.value) FILTER (WHERE g.value IS NOT NULL) AS avg_grade,\n count(*) FILTER (WHERE s.submitted_at IS NULL AND a.due_at < now()) AS overdue,\n (SELECT count(*) FROM messages m WHERE m.course_id = c.id AND m.read_at IS NULL) AS unread\nFROM courses c\nJOIN enrolments e ON e.course_id = c.id\nLEFT JOIN grades g ON g.enrolment_id = e.id\nLEFT JOIN assessments a ON a.course_id = c.id\nLEFT JOIN submissions s ON s.assessment_id = a.id AND s.student_id = e.student_id\nWHERE c.institution_id = $1 AND c.archived_at IS NULL\nGROUP BY c.id, c.title;\n\n1,200 courses, 88,000 enrolments, 4.1M submissions for that institution", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "support's notes on the exam-week incidents, they need to become a page teachers can read:\n\n- students on flaky wifi sometimes see \"answer not saved\" and refresh, which creates a second attempt\n- teachers then see two attempts and don't know which is authoritative — it's the one with the later submittedAt\n- an attempt with no submittedAt after the exam window closes is auto-submitted by a nightly job, which teachers don't know exists\n- the review screen shows answers from the latest attempt only, which is why students say answers \"disappeared\"\n- teachers can merge attempts through a support ticket, which takes a day and a database script\n- none of this is in any documentation, and exam week is in three weeks\n\nwrite the page for teachers, and separately tell me which of these are documentation problems and which are product problems", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "notes from the security team's rule review, i need to turn them into a rule-writing guide for analysts:\n\n- every rule needs an owner, a rationale and an expected volume, and today most have none\n- rules imported from blog posts are the biggest source of noise; the SMB one fires 40 times a day\n- suppression by source.ip for known management hosts should be the default, not an afterthought\n- thresholds are absolute counts, so a rule tuned for one customer's volume is wrong for another\n- rules query `logs-*` by habit, which now includes tomorrow's index and non-EDR data\n- there's no test procedure; analysts write a rule and see if it fires in production\n- a rule that generates zero alerts for a week should be reviewed, not left running\n\nwrite the guide, aimed at analysts who write rules but don't operate the platform", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "o resumo do incidente de ontem, para as escolas afetadas:\n\n09:12 professores relatam que as notas mostradas aos alunos não coincidem com o painel\n09:40 confirmamos: o painel do aluno arredonda antes de ponderar\n10:05 verificamos que o export CSV usa uma consulta diferente, escrita há dois anos\n10:30 três cálculos distintos identificados para a mesma nota\n11:15 decidimos que o painel do professor é a fonte de verdade\n12:00 correção aplicada aos outros dois; nenhuma nota gravada estava errada\n\nnenhum aluno foi avaliado incorretamente, mas alguns viram um valor diferente durante cerca de três horas; as escolas querem saber se as notas finais foram afetadas", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "pt"} -{"prompt": "WMS operator's manual covers the old conveyor system and nothing about the robots. what's true now:\n\n- tasks are dispatched from the WMS to a robot fleet over kafka, with a 90 second lease\n- a robot that loses connectivity keeps executing its current task and reports on reconnect\n- the traffic manager grants node reservations; a robot without a reservation stops and waits\n- an aisle can be put into maintenance mode from the console, which drains tasks but does not recall robots already inside\n- cycle counts run nightly and discrepancies over 2 units page the shift supervisor\n- there is a physical e-stop per aisle that the software cannot override, and a software pause that it can\n- recovering a stuck robot means driving it manually from the console, which requires a role most supervisors don't have\n\nwrite the operator's manual section for the robot fleet", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "changelog for the LMS release, from the commits since 6.3:\n\n41c9e0b fix(attempts): answers are upserted rather than created, fixing lost answers on retry\n88f21c0 feat(grading): one grading path for the student view, teacher view and export\nc0aa774 fix(media): media requests no longer vary on Cookie, restoring CDN caching\n2e91b45 feat(exams): attempts can be merged from the teacher's screen\naa30f19 perf(dashboard): instructor dashboard query rewritten, 8s to 400ms\n9c1d004 chore: minimum node version is now 22\n4410bb7 fix(a11y): quiz navigation is keyboard operable\nb77e910 feat(api): institution-scoped API tokens\n\nour readers are school IT administrators; two of these change behaviour they'll notice and one needs action from them", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "pasted-context", "lang": "en"} -{"prompt": "auditor's questions about our SIEM deployment, which we've never had to answer in writing:\n\n1. What data is collected from endpoints, and can a customer see the full list?\n2. How long is raw telemetry retained, and where?\n3. Who can read another tenant's alerts, and how is that prevented?\n4. Can an analyst delete an alert, and is that recorded?\n5. How are detection rules versioned, and can you show which rule version produced a given alert?\n6. What happens to alerts when a rule is deleted?\n\nour rules live in a git repo but alerts store only the rule name; deleting a rule leaves orphaned alerts; and tenant isolation is a filter applied in the query layer\n\nwrite the controls document, marking clearly what we cannot currently substantiate", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "我们的告警规则文档只有一个示例，运维和分析师都在猜。目前规则引擎的实际行为如下：\n\n- 规则每 5 分钟执行一次，查询窗口默认也是 5 分钟，两者不一致时以窗口为准\n- 窗口是左闭右开，边界上的事件会在两个窗口中被计算一次还是零次，取决于 `@timestamp` 的精度\n- 阈值是绝对值，不随数据量缩放；同一条规则在不同租户下的表现完全不同\n- 抑制（suppression）只按字段去重,不做时间衰减，抑制窗口固定 1 小时且不可配置\n- 规则被删除后，已产生的告警仍然保留，但无法回溯到规则内容\n- 规则里写 `index: logs-*` 会匹配到未来日期的索引，这在跨时区部署里会导致漏报\n\n请写成给分析师看的规则编写文档，把窗口边界和抑制这两点讲清楚\n\n目前规则文件长这样，文档里也只有这一个例子：\n\nname: Suspicious SMB session enumeration\nindex: logs-edr-*\ninterval: 5m\nwindow: 5m\nquery: |\n event.code:5145 and winlog.event_data.ShareName:\"\\\\\\\\*\\\\IPC$\"\nthreshold:\n field: source.ip\n value: 10\nsuppression:\n by: [source.ip]\n window: 1h # 实际上这个字段被忽略，永远是 1 小时\nseverity: high\nowner: (empty)\n\n另外，规则删除后 alerts 表里的 rule_name 还在，但 rule body 无法追溯", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "zh"} -{"prompt": "on-call runbook for the warehouse is a laminated sheet from the conveyor era. what the team does now:\n\n- \"aisle stopped\" is the most common page; first check whether it's an e-stop (physical) or a software pause\n- if the traffic manager is granting reservations but robots aren't moving, restart the dispatcher, not the traffic manager\n- restarting the traffic manager during operations releases every reservation at once, which is how we had the near-miss in May\n- a robot that missed its heartbeat but is still moving is the dangerous case; the only safe action is the aisle e-stop\n- kafka consumer lag above 500 on wms.tasks means the dispatcher is behind and picks will be late, not lost\n- never drain an aisle that has robots inside it; drain, then wait for the aisle to report empty\n\nwrite the runbook, ordered by what a supervisor at 3am would need first", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "eslint and tsc on the LMS app, the gate goes on next sprint:\n\napp/lib/courseCache.ts:22:14 - error TS7034: Variable 'cacheMap' implicitly has type 'any' in some locations\napp/api/attempts/[id]/answers/route.ts:41:22 - error TS2345: Argument of type 'string | null' is not assignable to parameter of type 'string'\napp/components/QuizNav.tsx:88:5 - warning: Static HTML elements with event handlers require a role (jsx-a11y/no-static-element-interactions)\napp/components/QuizNav.tsx:112:9 - warning: Visible, non-interactive elements with click handlers must have at least one keyboard listener\napp/lib/grades.ts:141:3 - error TS2554: Expected 2 arguments, but got 3\n\n3 errors, 2 warnings", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"} -{"prompt": "spotbugs on the WMS service, two of these look real:\n\nM C RCN: Nullcheck of value previously dereferenced in TrafficManager.tryReserve(String, String, Duration)\nM P UPM: Private method TaskDispatcher.requeue(Task) is never called\nH C IS2: Inconsistent synchronization of TrafficManager.reservations; locked 60% of time\nM D DM: TaskDispatcher.assign() invokes inefficient new String() constructor\nH C EC: Call to equals() comparing Robot and String in FleetRegistry.find(String)\n\n5 warnings, and IS2 on the reservations map is the one i keep thinking about", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "index lifecycle policy versus what we actually keep, one of these is wrong:\n\nPUT _ilm/policy/edr-logs\n{\n \"policy\": {\n \"phases\": {\n \"hot\": { \"actions\": { \"rollover\": { \"max_primary_shard_size\": \"50gb\", \"max_age\": \"1d\" } } },\n \"warm\": { \"min_age\": \"7d\", \"actions\": { \"shrink\": { \"number_of_shards\": 1 } } },\n \"cold\": { \"min_age\": \"30d\", \"actions\": { \"searchable_snapshot\": { \"snapshot_repository\": \"s3\" } } },\n \"delete\": { \"min_age\": \"90d\", \"actions\": { \"delete\": {} } }\n }\n }\n}\n\nour contract with two customers says 12 months of searchable telemetry, and our marketing page says 13 months", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "CDN config for lesson media, which is why one district gets no caching at all:\n\ncache_rules:\n - path: \"/media/*\"\n cache: { ttl: 604800, key: [path, query, header:Cookie, header:Origin] }\n - path: \"/api/*\"\n cache: { ttl: 0 }\n\norigin response headers:\n cache-control: public, max-age=604800\n vary: Origin, Accept-Encoding, Cookie\n\nthe media is identical for every student and requires a signed URL in the query string, which is already in the cache key", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"} -{"prompt": "kafka consumer settings, prod versus the values the vendor recommends:\n\n# ours\nsession.timeout.ms: 10000\nheartbeat.interval.ms: 3000\nmax.poll.interval.ms: 300000\ngroup.instance.id: unset\npartition.assignment.strategy: RangeAssignor\n\n# vendor's recommendation for mobile consumers\nsession.timeout.ms: 45000\nheartbeat.interval.ms: 15000\nmax.poll.interval.ms: 300000\ngroup.instance.id: \npartition.assignment.strategy: CooperativeStickyAssignor\n\nour robots drop off wifi for 5-20 seconds when they pass through racking, and every drop triggers a full group rebalance", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "les seuils d'alerte du WMS, on est réveillés pour rien mais on rate les vrais problèmes :\n\n- alert: ConsumerLag\n expr: kafka_consumergroup_lag{group=\"wms-robots\"} > 100\n for: 1m\n labels: { severity: page }\n\n- alert: RobotOffline\n expr: up{job=\"robot\"} == 0\n for: 0m\n labels: { severity: page }\n\n- alert: TaskDeadLettered\n expr: increase(wms_tasks_dead_lettered_total[1h]) > 0\n for: 0m\n labels: { severity: ticket }\n\nles robots passent hors ligne 5 à 20 secondes en traversant les rayonnages, le lag dépasse 100 à chaque vague de commandes, et le vrai incident de mai (une réservation libérée sous un robot en mouvement) n'a déclenché aucune alerte", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "fr"} -{"prompt": "this dispatcher has grown five responsibilities and a scheduled executor. same behaviour, separable pieces:\n\npublic class TaskDispatcher {\n // builds the pick list from open orders\n // chooses a robot by capability, distance and current load\n // produces to kafka and tracks the lease\n // requeues on missed ack, dead-letters after three attempts\n // emits metrics and writes an audit row per assignment\n // runs a scheduled sweep every second for expired leases\n}\n\n800 lines, one test that boots the whole spring context and a real kafka container, and the lease sweep is the part we most need to change", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "drei Stellen bauen dieselbe Prisma-Abfrage für „Kurse eines Lehrers\", leicht unterschiedlich:\n\n// app/api/courses/route.ts\nprisma.course.findMany({ where: { teacherId, archivedAt: null }, include: { assessments: true } })\n\n// app/dashboard/page.tsx\nprisma.course.findMany({ where: { teacherId }, include: { assessments: true, enrolments: true } })\n\n// lib/reports.ts\nprisma.$queryRaw`SELECT * FROM courses WHERE teacher_id = ${teacherId} AND archived_at IS NULL`\n\ndie zweite vergisst archivierte Kurse auszuschließen, die dritte umgeht das Row-Level-Security-Setup komplett", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "de"} -{"prompt": "planning input for the term, and i need it sequenced against exam week:\n\n- exam week is in three weeks and lost answers are our most damaging bug\n- the instructor dashboard times out for our two largest institutions, both of whom are up for renewal\n- the WMS traffic manager has a safety-adjacent bug that legal wants addressed before the next site goes live\n- the SIEM's detection rules are noisy enough that the customer's SOC has started ignoring them\n- two engineers are shared across the LMS and the WMS, and neither product is moving\n- a customer wants 12 months of searchable telemetry, we currently delete at 90 days\n- there's a node major version upgrade we've deferred twice", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "architecture ticket, and i want the thinking before anyone starts:\n\nWMS-702 — Safety-critical reservation handling\nThe traffic manager releases a node reservation when a robot's heartbeat is missed for 15 seconds, on the assumption that a silent robot has stopped. In May a robot passed through racking, lost wifi, kept moving, and its reservation was granted to another robot. Nobody was hurt and no goods were damaged. The proposal is to require positive confirmation of a stop before releasing, which means a robot that genuinely dies blocks its node until a human intervenes. Constraints: robots have no independent radio; the aisle e-stop is the only guaranteed stop; and throughput targets assume reservations are released within seconds.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.95, "slice": "pasted-context", "lang": "en"} -{"prompt": "SIEM team's wishlist, one engineer, one quarter:\n\n- rule versioning, so an alert can be traced to the rule text that produced it\n- a test harness for rules against recorded telemetry, instead of writing to production\n- per-tenant thresholds, because absolute counts don't work across customers of different sizes\n- suppression that decays rather than a fixed one-hour window\n- retention to 12 months for two contracts, which is a storage and cost question as much as a technical one\n- the ingestion pipeline stops losing whole batches when elasticsearch rejects them\n\nwhat's the order, and which of these is secretly the biggest", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "design spec for the quiz player, which has to work under exam conditions:\n\nQuiz player\n- One question per screen on mobile, optional all-questions view on desktop; the choice persists per student.\n- Question navigator: a grid of numbers, showing answered / unanswered / flagged, always reachable by keyboard.\n- Autosave indicator: a small text state — \"Saved 11:02\", \"Saving…\", \"Not saved — retrying\" — never a spinner that lies.\n- Offline: answers queue locally and the banner says exactly what is unsaved; the submit button is disabled while anything is queued.\n- Timer: fixed at the top, warns at five minutes and one minute, announced politely rather than continuously.\n- Submission: a confirmation listing unanswered questions, which is the only blocking dialog in the flow.\n- Everything keyboard operable, focus visible, and no interaction that requires a hover.\n- Must degrade to a plain form if JavaScript fails mid-exam, because it has happened.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "spec for the warehouse console's aisle view, which supervisors watch all shift:\n\nAisle view\n- Top-down schematic of one aisle, racking either side, robots as arrows showing heading, updating at 4Hz over websocket.\n- Node reservations drawn as translucent overlays with the holding robot's id; expiring reservations pulse in the last three seconds.\n- Robot cards along the right: id, battery, current task, lease remaining, last heartbeat age. Cards sort by problem state first.\n- A robot with a missed heartbeat is unmistakable — not just a colour, but a striped overlay and a persistent banner.\n- Controls: software pause per aisle, drain, and per-robot manual drive, all behind a role check with the button absent rather than disabled.\n- The e-stop state is displayed but never controllable from software.\n- Everything must be legible from two metres on a wall-mounted screen, and must not depend on hover for any information.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "accessibility audit of the LMS, which a district commissioned before renewal:\n\n1. Quiz question navigation is mouse-only; the number grid cannot be reached or operated by keyboard.\n2. The autosave state is conveyed by a coloured dot with no text alternative.\n3. The exam timer is announced by screen readers on every tick, making the page unusable.\n4. Drag-to-order questions have no keyboard alternative at all.\n5. Focus is lost to the document body after every question transition.\n6. Error messages on the submission dialog are not associated with the controls they refer to.\n7. Contrast on the \"flagged\" question state is 2.7:1 against the grid background.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "analyst console's alert triage screen, spec from the SOC team who use it eight hours a day:\n\nTriage view\n- Alert list on the left, virtualised, grouped by rule with counts; keyboard j/k moves, enter opens, e escalates, s suppresses.\n- Detail pane: the matched events in a table, the rule text as it was at match time, and the enrichment results with their source and age.\n- Enrichment that failed must say so explicitly rather than showing an empty field.\n- Timeline of related alerts for the same entity within 24 hours, on one axis, clickable.\n- Bulk actions on a selection, with an undo window of ten seconds rather than a confirmation dialog.\n- Every action records who, when and why; the why is a required free-text field for escalation and suppression.\n- Dark theme is the default because the SOC runs with the lights down, and both themes must pass contrast.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "integration spec a district's student information system expects from us:\n\nOneRoster 1.2 REST, we implement the consumer side\n GET /ims/oneroster/rostering/v1p2/orgs/{id}/classes paginated, up to 20k classes\n GET .../classes/{id}/students and .../classes/{id}/teachers\n sync nightly; the district publishes changes at 02:00 local time and expects us current by 07:00\n enrolment removals are soft — a student disappearing from a class must not delete their submissions\n the district's ids are opaque strings and are not stable across academic years\n they rate limit us to 10 requests per second and will not raise it\n a partial sync must be resumable, and a failed sync must not leave students without access at 08:00", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "schema we agreed for rule versioning, now it needs building:\n\nCREATE TABLE rule_versions (\n id uuid PRIMARY KEY,\n rule_id uuid NOT NULL,\n version int NOT NULL,\n body jsonb NOT NULL,\n author text NOT NULL,\n created_at timestamptz NOT NULL DEFAULT now(),\n active_from timestamptz,\n active_to timestamptz,\n UNIQUE (rule_id, version)\n);\n\nalerts must reference the rule_version that produced them; deleting a rule must not orphan alerts; an analyst editing a rule creates a new version rather than mutating; and the triage screen has to show the rule text as it was when the alert fired, which means versions are immutable once any alert references them", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "retention to 12 months on the EDR policy", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "sharp bump before the freeze", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "drop Cookie from the media cache key", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "the console lets a supervisor drive a robot manually and i genuinely don't know what happens if they do that while the robot holds a node reservation and has an active task lease. work through the interaction between manual drive, the traffic manager and the dispatcher, and tell me which of the three thinks it is in charge", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "our python services load configuration three different ways and the SIEM one reads environment variables at import time, which is why a config change needs a restart nobody expects. unify the loading, then document the new precedence so operators stop guessing", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "certificate email says \"Congradulations\"", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "core", "lang": "en"} -{"prompt": "session timeout to 45s for the robots", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "el botón de entrega sigue en inglés", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "core", "lang": "es"} -{"prompt": "stable group.instance.id per robot", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "rules should query logs-edr-* not logs-*", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "add a timeout to the ASN lookup", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "Kurs-Cache begrenzen, er wächst unbegrenzt", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "de"} -{"prompt": "RobotOffline needs a 30 second delay", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "question navigator grid, keyboard operable", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "autosave state needs text, not a dot", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "reservation overlays on the aisle view", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "failed enrichment shows an empty field", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "試験タイマーが毎秒読み上げられます", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "ja"} -{"prompt": "flagged state fails contrast", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "focus is lost between questions", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "pull the lease sweep out of the dispatcher", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "une seule requête pour « cours du professeur »", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "fr"} -{"prompt": "`enrolment` spelling, pick one", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "extract the rule query builder", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "inline the single-use `scoreFor`", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "docstrings for the task lease API", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "release notes for LMS 6.4", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "nota para as escolas sobre as notas", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "pt"} -{"prompt": "document the auto-submit job for teachers", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "summarise the reservation proposal", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "PR body for the grading unification", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "can a reservation outlive a moving robot?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "¿por qué las reglas dejaron de disparar?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "es"} -{"prompt": "walk me through the nightly auto-submit", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "answers disappear from the review screen", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "elasticsearch rejects our morning writes", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "warum wächst der Heap bis zum Neustart?", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "de"} -{"prompt": "endpoint for a rule's version history", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "onwards with that", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "calmer alerts", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "whatever helps before exams", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "neaten it up", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "like last week", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "audit answers", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "encore le tableau de bord", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "fr"} -{"prompt": "something quick", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "give it another read", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "優先度はお任せします", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "ja"} -{"prompt": "usual for this sprint", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "traffic manager releases a node reservation when a robot's heartbeat has been missing for fifteen seconds, on the assumption that a silent robot has stopped, and in May that assumption was wrong in the most alarming possible way. i want the options for making this safe worked through properly — positive stop confirmation, independent sensing, aisle-level interlocks — with an honest view of what each does to throughput and what happens when a robot genuinely dies mid-aisle legal has asked for this in writing before the next site goes live, so the reasoning matters as much as the answer.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.95, "slice": "core", "lang": "en"} -{"prompt": "SOC has started ignoring our alerts, which makes the whole product pointless regardless of how good the detection is. work through what would actually restore trust — rule versioning, testing against recorded telemetry, per-tenant thresholds, decaying suppression — and tell me which of those is secretly the biggest piece of work rather than the most obviously useful their own metric is alerts investigated per shift, which has halved since january.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "two of our contracts promise twelve months of searchable telemetry and our lifecycle policy deletes at ninety days, which somebody is going to notice during an investigation rather than during a review. work out what twelve months actually costs across hot, warm and cold tiers at our current volume, and what the honest options are including renegotiating", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "analysts write detection rules by copying blog posts and seeing what fires in production, which is how we ended up with forty false positives a day from one rule. write the rule-authoring guide — ownership, rationale, expected volume, suppression, thresholds, testing — aimed at analysts who write rules but never operate the platform the SMB rule is the example everyone recognises, so it's worth walking through it.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "detection rules stopped generating alerts overnight and the only unusual event was tomorrow's index being created at seven minutes past two. work through how the rules resolve indices and time windows, and tell me whether that index explains it or whether it's a coincidence i've latched onto the deployment spans three timezones, if that turns out to matter.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "enrichment providers each invent their own failure handling — one has no timeout, one silently returns nothing, one sleeps ten seconds inside the pipeline, one throws and kills the batch. give them one interface with explicit timeouts and failure semantics, keeping each provider's successful output exactly as it is today the ASN provider is the one currently taking the pipeline down, so start the analysis there.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "inventory drifts by a few units a day and the two picks in the sample were dispatched from the same snapshot of five units, which smells like the dispatcher reading availability without reserving it. work through the ordering of the task, the pick and the inventory event before we propose anything reconciliation runs at eighteen hundred and the discrepancies are always small and always negative.", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "aisle view is what supervisors watch all shift and it currently conveys a missed heartbeat with a colour change nobody notices from two metres. build the view to the new spec, with the problem states unmistakable and the e-stop state visible but never controllable from software the screens are wall-mounted at about two metres and nobody is going to hover over anything.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "before we touch the traffic manager i want the safety argument written down — what we assume, what guarantees each layer provides, where a single failure is tolerated — and then the heartbeat handling changed to whatever that argument says is defensible the May near-miss is the case the argument has to explain, not just the happy path.", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.95, "slice": "mixed", "lang": "en"} -{"prompt": "attempt model needs to handle two devices and flaky connections properly, which is a design question, and it needs to stop losing answers before exams, which is urgent. do the design first, then the idempotent answer write against it students routinely start on a laptop and finish on a phone, which nobody designed for.", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "die Anreicherungspipeline blockiert regelmäßig komplett, wenn ein Anbieter langsam ist. Ich hätte gern zuerst ein Konzept für Timeouts, Nebenläufigkeit und Rückstau und danach die Umsetzung für den ASN-Anbieter, weil der uns gerade am häufigsten umbringt", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "de"} -{"prompt": "teachers need the attempts page written for them before exam week, and writing it will make obvious which parts are product bugs rather than missing documentation. produce the page, and give me the separate list of things we should fix instead of explaining last term generated forty support tickets, most of them the same three questions.", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "escribe la documentación del motor de reglas para los analistas y comprueba en el código si la ventana de supresión es realmente fija en una hora, porque el equipo cree que es configurable", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "es"} -{"prompt": "warehouse runbook needs writing and the aisle-drain procedure needs fixing, because draining an aisle with robots inside is currently possible from the console. write the runbook, then put the guard in", "purpose": "writing", "secondary": "backendImpl", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "task dispatcher does five things and the lease sweep is the one we need to change for safety reasons. separate them, then document the new boundaries so the next change doesn't have to understand all five", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "rule engine's three query syntaxes should become one. migrate the existing rules, and write the note explaining to analysts what changed and which of their rules were rewritten", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "one district gets no CDN caching on lesson media and the Vary header is the obvious suspect, but their proxy adds a Cookie to every request so it may be their side. confirm which it is, then fix whichever end we control every other district on the same build is fine, which is what makes me suspect their proxy.", "purpose": "debugging", "secondary": "quickFix", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "robots rebalance constantly and one aisle periodically stops receiving tasks, which i think are the same problem. diagnose it properly, then change the consumer configuration to whatever the diagnosis says rather than what the vendor's blog recommends", "purpose": "debugging", "secondary": "quickFix", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "triage screen needs bulk actions with an undo window, and the SOC wants to know what \"undo\" means for an escalation that already paged someone. design that interaction with me, then build it", "purpose": "frontendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "npm audit has one severe finding whose fix is a major version we can't take three weeks before exams. work out the exposure honestly, apply what's safe, and tell me what compensating control covers the rest", "purpose": "quickFix", "secondary": "review", "mixed": true, "difficulty": 0.55, "slice": "mixed", "lang": "en"} -{"prompt": "per-tenant thresholds need to exist before the next customer onboards, and the shape matters — absolute, relative to baseline, or both. decide with me, then implement", "purpose": "backendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "rename `Task` in the WMS service, it collides with the scheduler's Task and the API's TaskDto", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "could you explain what happens to an attempt when a student opens the same quiz on a second device", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "why does our SMB rule fire forty times a day from the same six servers", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "someone should check whether an analyst can delete an alert without leaving a trace", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "is it expected that a robot keeps executing a task it can no longer report progress on", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "docs/attempts.md says answers are upserted, which stopped being true in the rewrite", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "a short note explaining why the lease sweep is moving out of the dispatcher, for the decision log", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "API changelog needs an entry for institution-scoped tokens and what they replace", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "javadoc on tryReserve promises exclusivity that the sweep thread quietly breaks", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "write the customer note about telemetry retention changing from 90 days to 12 months", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "precisamos de uma página que explique aos professores como funcionam as tentativas", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "pt"} -{"prompt": "health endpoint reports the rules engine healthy while it has produced zero alerts for six hours", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "dead-letter alert only fires on an increase over an hour, so a steady trickle is invisible", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "how should we handle student ids that change between academic years without losing submission history", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "what's the right way to test the traffic manager, given that the failure mode is two robots in one place", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "i want a position on whether detection rules belong in git or in the database now that they need versions", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "three districts want single sign-on with three different identity providers, what should our approach be", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "what should happen to alerts when a customer offboards, given the contract says we delete their data", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "an endpoint that returns an attempt's full answer history including superseded values, for teachers", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "bulk indexer should check per-item responses and retry only the rejected documents", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "alert timeline should show related alerts for the same entity within 24 hours on one axis", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "instructor dashboard needs a loading skeleton that doesn't shift the layout when data arrives", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "robot cards should show lease remaining as a countdown rather than an absolute timestamp", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "quiz submission dialog should list unanswered questions as links, not just a count", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "anything that survives exam week", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "back to the rules engine", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "i'd like to understand what happens to a task lease when kafka rebalances mid-execution, because a robot that keeps working while its partition moves is exactly the shape of the aisle-stall bug. trace the interaction properly and tell me whether the lease and the partition assignment can ever disagree about who owns a task", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "submissions need a client-supplied idempotency key so that a retry on a slow connection cannot create a second answer row, which is the mechanism behind the answers students say disappear. design the key's scope and lifetime, implement the write path, and make sure an old client without the header still works during exam week", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "exam week needs the health endpoint to stop lying about the rules engine, and it needs an alert when zero alerts have been produced for an hour. do both, and tell me what else in our monitoring reports healthy while producing nothing", "purpose": "quickFix", "secondary": "review", "mixed": true, "difficulty": 0.5, "slice": "mixed", "lang": "en"} -{"prompt": "nobody has been able to tell me what the grading worker does when an assessment's weight changes after grades have been published — whether it recalculates silently, waits for the nightly run, or leaves the published grade alone. read the recalculation path and the nightly job together and tell me what a student would actually see in each case", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "our LMS notification code sends email, in-app and push from three different places with three different templating approaches, and a student who has muted a course still gets the push. bring them behind one notification service with preferences applied in one place, keeping every existing message identical in wording and timing", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "the SIEM's alert model carries both the matched documents and a denormalised copy of the entity fields, which have drifted apart since the enrichment rewrite. settle on one representation, migrate the existing alerts, and keep the triage screen showing exactly what it shows today for alerts that predate the change", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "we need an endpoint that returns a student's full submission history for a course, including superseded answers and the attempt each came from, because teachers currently ask support for a database export. it has to be paginated, cheap enough to call from the teacher's screen, and must not expose other students' data through a guessable id", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} +{"prompt":"Split projects/isotope/ml/pipeline/features.py by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-49139: finish the compact IsotopeHarborIndexFlow filter experience\n\nRoute: /catalog/search\nSource: projects/isotope/ui/settings/PrivacyPane.tsx\nFramework: Tokio\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nFinish the visible IsotopeHarborIndexFlow state described above: responsive layout, correct selection restoration, keyboard focus, accessible labels, dark mode, and reduced-motion behavior.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"IsotopeSummitProxyCoordinator: restructure, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Center the IsotopeAmberFilterService modal","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Walk through IsotopeIrisBatchStore's SyncWorker.kt","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/isotope/Sources/App/SessionStore.swift b/projects/isotope/Sources/App/SessionStore.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/Sources/App/SessionStore.swift\n+++ b/projects/isotope/Sources/App/SessionStore.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure IsotopeCloudReconcilerFlow so duplicated normalization and shutdown ownership have one home. Preserve public behavior, wire values, logging fields, and ordering; extend characterization coverage first.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Wire a IsotopeFlintTimelineFlow background task in projects/isotope/services/ledger/replay.go that expires abandoned sessions, records an OpenTelemetry span, and yields cleanly when shutdown begins.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Production says IsotopeFlintTimelineService is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current PostgreSQL 17 operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Cinder: The IsotopeLedgerGateService feature flag default should be false in test, exactly like production; correct that config entry and nothing else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"IsotopeSableParserCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Teach IsotopeOpalRouterStore to verify signed continuation tokens, reject cross-tenant cursors, and rotate keys without invalidating tokens issued during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"// projects/isotope/crates/index/src/segment.rs\nfinal class IsotopeBeaconStoreFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nWalk through what the artifact proves about IsotopeBeaconStoreFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Could IsotopeNovaPickerService show the active NATS JetStream sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"IsotopeKiteSchedulerCoordinator: correct, then assess","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Delta: projects/isotope/packages/api/openapi.yaml の IsotopeGarnetModalFlow で、NATS JetStream の flow に断続的な問題が起きています。 責務を分離して重複をなくし、API、wire value、順序、観測可能な動作は変えないでください。\n\n制約:\n- NATS JetStream を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は IsotopeGarnetModalFlow のみ","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"ja"} +{"prompt":"Ember: Incident timeline — INC-49124\n\n08:02 deploy IsotopeAmberFilterFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nDetermine why IsotopeAmberFilterFlow produces this result. Trace ordering, cancellation, shared state, and scheduler behavior; identify the root cause before suggesting a patch.","purpose":"debugging","secondary":"planning","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"diff --git a/projects/isotope/Sources/CLI/Commands/Doctor.swift b/projects/isotope/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/isotope/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit IsotopeSlateEditorFlow by responsibility and make cancellation ownership explicit. Characterize the current sequence before moving code and keep callers unchanged.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"PM needs a concise migration note for IsotopeCloudReconcilerStore, including the user impact, rollback trigger, and the one configuration key operators must change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"IsotopeWrenExportCoordinator needs a paired pass: produce a consumer guide for IsotopeWrenExportCoordinator, plus give the existing implementation a read-only safety pass. Use projects/isotope/db/migrations/20260730_events.sql as the source of truth, preserve the SQLite contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Frost: The first IsotopeBirchMigratorFlow request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Garnet: Two asks around IsotopeAmberFilterCoordinator: (1) separate IsotopeAmberFilterCoordinator's policy from transport without behavior changes; (2) capture the contract and rollback note for consumers. Keep the patch readable for a small on-call review, and leave a clear boundary between the resulting artifacts or edits.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"A previously stable test around IsotopeDeltaCanvasFlow now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"IsotopeMosaicGridCoordinator: polish, then assess","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Harbor: Two asks around IsotopeFernSnapshotCoordinator: (1) assess ownership and failure handling in projects/isotope/apps/console/routes/usage.svelte; (2) capture the contract and rollback note for consumers. Keep the patch readable for a small on-call review, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Ticket OPS-49148: retire the legacy replay path for IsotopePrismCacheFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nTurn the material above into a concise IsotopePrismCacheFlow release note and operator runbook section. State impact, detection, rollback, and the client-visible contract; do not modify code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"Split IsotopeOrbitSyncService without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Clarify IsotopeMapleQueueService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Compare IsotopeMosaicGridStore's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Translate the IsotopeEchoRegistryService setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"The minimum supported WebGPU version in projects/isotope/Sources/App/SessionStore.swift is one patch behind the lockfile. Align that single value and regenerate only the affected metadata.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Fresh release brief for IsotopeDriftConsoleCoordinator:\n- primary outcome: find the unknown cause of stale cursors when a page is resumed\n- companion outcome: correct the known stale timeout beside it\n- repository entry point: projects/isotope/services/ledger/replay.go\n- platform constraint: PostgreSQL 17\n- known complication: stale cursors when a page is resumed\n\nBoth results are required, but they should remain independently reviewable. Keep the patch readable for a small on-call review; retain serialization and authorization boundaries; cover cancellation, idempotent retries, and rollback; and avoid drive-by cleanup. Use the code as the source of truth, call out assumptions, and state how an on-call engineer can tell that either part is unsafe to ship.","purpose":"debugging","secondary":"quickFix","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"UI ticket DES-49159: finish the compact IsotopeBirchMigratorCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/isotope/ui/settings/PrivacyPane.tsx\nFramework: Tokio\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring IsotopeBirchMigratorCoordinator's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"IsotopeRavenSessionStore has four wrappers that only translate the same error enum. Collapse them into one adapter and preserve every public case, message, and metric label.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Two engineers disagree about whether IsotopeCinderAuthFlow's cache is authoritative. Walk the reads and writes in projects/isotope/cmd/exporter/main.py and settle that question from the code. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Iris: Split projects/isotope/config/staging.toml by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Juniper: The public surface of IsotopeMapleQueueStore is frozen, but its internal ownership in projects/isotope/crates/index/src/segment.rs is difficult to test and even harder to change safely. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeMapleQueueStore\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Two asks around IsotopeQuartzPlayerCoordinator: (1) lay out a staged migration for IsotopeQuartzPlayerCoordinator; (2) then implement the bounded durable-cursor handler. Keep the patch readable for a small on-call review, and leave a clear boundary between the resulting artifacts or edits.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Does IsotopeCopperBridgeStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists? Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"We need to move IsotopeTideWorkerService from the legacy store to Tokio. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Responsive layout for IsotopeAcornWidgetStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"IsotopeLedgerGateCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"IsotopeSpruceDaemonCoordinator is blocking the next release because duplicate retries after a network handoff. I need two concrete outcomes from a single pass: find the unknown cause of duplicate retries after a network handoff, and capture the contract and rollback note for consumers. Use the existing PostgreSQL 17 conventions in projects/isotope/internal/auth/refresh.go; keep the patch readable for a small on-call review. Keep the outcomes distinct so reviewers can see which evidence supports the assessment and which files or prose satisfy the requested change.\n\nConstraints:\n- preserve public wire values and tenant boundaries\n- cover cancellation and retry behavior\n- avoid generated code and unrelated cleanup\n- include a rollback trigger that an on-call engineer can measure\n\nThis is a fresh workstream for the release, so derive everything from the repository and the context here.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Incident timeline — INC-49113\n\n08:02 deploy IsotopeWillowCodecFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. From this evidence, draft consumer-facing migration guidance for IsotopeWillowCodecFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"IsotopeCraneWorkspaceCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Add a bounded IsotopeCloudReconcilerService export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Add a bounded IsotopePineMetricsService export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Compare IsotopeIrisBatchService's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'IsotopeWrenExportFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[IsotopeWrenExportFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/isotope/src/sync/reconcile.ts:144: error: -[IsotopeWrenExportFlowTests testRestoresSelectionAfterBackgrounding] : XCTAssertEqual failed: (\"Optional(4)\") is not equal to (\"Optional(3)\")\nAccessibility hierarchy at failure:\n Application, 0x104c, pid: 812\n Window, identifier: \"main\"\n NavigationStack, identifier: \"catalog\"\n Button, label: \"Filters\", value: \"2 active\"\n CollectionView, identifier: \"results-grid\", rows: 24\n Sheet, identifier: \"filter-sheet\"\n TextField, label: \"Search filters\", value: \"\"\n Switch, label: \"Available offline\", value: \"1\"\n Button, label: \"Apply\", enabled: true\nTest Case '-[IsotopeWrenExportFlowTests testRestoresSelectionAfterBackgrounding]' failed (4.812 seconds).\n\nSimulator: iPhone 17 Pro, iOS 27.0, en_US, content size XXXL, Reduce Motion enabled. The screenshot looks correct. The mismatch is the internal selected-segment index after the scene becomes active; tapping Apply a second time makes it three again.\n\nUse the UI evidence to complete IsotopeWrenExportFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"The IsotopeCedarPolicyStore surface in projects/isotope/cmd/exporter/main.py is stable now; turn its edge cases into API documentation with one successful example and one cancellation example.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Cadre la migration de IsotopeMarbleTokenService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"fr"} +{"prompt":"Test Suite 'IsotopeAtlasSearchFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[IsotopeAtlasSearchFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/isotope/Sources/App/SessionStore.swift:144: error: -[IsotopeAtlasSearchFlowTests testRestoresSelectionAfterBackgrounding] : XCTAssertEqual failed: (\"Optional(4)\") is not equal to (\"Optional(3)\")\nAccessibility hierarchy at failure:\n Application, 0x104c, pid: 812\n Window, identifier: \"main\"\n NavigationStack, identifier: \"catalog\"\n Button, label: \"Filters\", value: \"2 active\"\n CollectionView, identifier: \"results-grid\", rows: 24\n Sheet, identifier: \"filter-sheet\"\n TextField, label: \"Search filters\", value: \"\"\n Switch, label: \"Available offline\", value: \"1\"\n Button, label: \"Apply\", enabled: true\nTest Case '-[IsotopeAtlasSearchFlowTests testRestoresSelectionAfterBackgrounding]' failed (4.812 seconds).\n\nSimulator: iPhone 17 Pro, iOS 27.0, en_US, content size XXXL, Reduce Motion enabled. The screenshot looks correct. The mismatch is the internal selected-segment index after the scene becomes active; tapping Apply a second time makes it three again.\n\nUse the UI evidence to complete IsotopeAtlasSearchFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Release verification found a single stale IsotopeDriftConsoleStore value; the cause, desired value, and affected assertion are already agreed. Change the staging timeout from 15 seconds to 30, adjust the adjacent assertion that encodes that value, and avoid unrelated formatting, renames, dependency bumps, or cleanup.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current PostgreSQL 17 operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Please resist widening this one: IsotopeEmberRelayService works, but staging still carries a setting that production corrected last month. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeEmberRelayService\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-49158: retire the legacy replay path for IsotopeLumenChartCoordinator\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nAssess IsotopeLumenChartCoordinator for durability, tenant isolation, races, and misleading observability. Separate blockers from questions and do not produce a patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"En projects/isotope/packages/api/openapi.yaml, IsotopeBasilRunnerStore tiene un problema intermitente en el flujo de NATS JetStream. Propón fases, compatibilidad, métricas, rollback y ownership; detente antes de tocar código.\n\nRestricciones:\n- seguir con NATS JetStream\n- conservar compatibilidad y cancelación\n- limitar el cambio a IsotopeBasilRunnerStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con NATS JetStream alrededor de IsotopeBasilRunnerStore.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"es"} +{"prompt":"Summarize the IsotopeSlateEditorStore changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"IsotopeAtlasSearchService flakes under UTC","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Find IsotopeFernSnapshotStore's duplicate retry source","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Kestrel: Test Suite 'IsotopeTideWorkerFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[IsotopeTideWorkerFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/isotope/lib/codec/frame.cc:144: error: -[IsotopeTideWorkerFlowTests testRestoresSelectionAfterBackgrounding] : XCTAssertEqual failed: (\"Optional(4)\") is not equal to (\"Optional(3)\")\nAccessibility hierarchy at failure:\n Application, 0x104c, pid: 812\n Window, identifier: \"main\"\n NavigationStack, identifier: \"catalog\"\n Button, label: \"Filters\", value: \"2 active\"\n CollectionView, identifier: \"results-grid\", rows: 24\n Sheet, identifier: \"filter-sheet\"\n TextField, label: \"Search filters\", value: \"\"\n Switch, label: \"Available offline\", value: \"1\"\n Button, label: \"Apply\", enabled: true\nTest Case '-[IsotopeTideWorkerFlowTests testRestoresSelectionAfterBackgrounding]' failed (4.812 seconds).\n\nSimulator: iPhone 17 Pro, iOS 27.0, en_US, content size XXXL, Reduce Motion enabled. The screenshot looks correct. The mismatch is the internal selected-segment index after the scene becomes active; tapping Apply a second time makes it three again.\n\nBring IsotopeTideWorkerFlow's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"diff --git a/projects/isotope/app/src/main/SyncWorker.kt b/projects/isotope/app/src/main/SyncWorker.kt\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/app/src/main/SyncWorker.kt\n+++ b/projects/isotope/app/src/main/SyncWorker.kt\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is IsotopeFernSnapshotFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Assess the IsotopeMosaicGridService diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Teach IsotopeOspreyJobService to verify signed continuation tokens, reject cross-tenant cursors, and rotate keys without invalidating tokens issued during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Lumen: diff --git a/projects/isotope/crates/index/src/segment.rs b/projects/isotope/crates/index/src/segment.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/crates/index/src/segment.rs\n+++ b/projects/isotope/crates/index/src/segment.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate IsotopeNovaPickerFlow's parallel adapters behind a single internal boundary, with no changes to API, timing, serialization, metrics, or error text.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Maple: Ticket OPS-49112: retire the legacy replay path for IsotopeEmberRelayFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nTurn the material above into a concise IsotopeEmberRelayFlow release note and operator runbook section. State impact, detection, rollback, and the client-visible contract; do not modify code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"Our support and SDK teams keep answering the same questions about IsotopeLumenChartStore, but the current prose in projects/isotope/db/migrations/20260730_events.sql only describes the happy path. Draft an ADR plus migration note that records the decision, rejected alternatives, compatibility window, observability signals, and the exact action required from consumers.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing SQLite deployment\n- keep the work scoped to IsotopeLumenChartStore and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"projects/isotope/app/src/main/SyncWorker.kt 里的 IsotopeCraneWorkspaceStore 最近在 SQLite 流程中出现间歇性问题。 请阅读现有流程，判断 ownership、取消和顺序是否安全，只需要分析。\n\n约束：\n- 继续使用 SQLite\n- 保持兼容性和取消语义\n- 改动只限于 IsotopeCraneWorkspaceStore","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"zh"} +{"prompt":"Release engineering needs a IsotopeNovaPickerStore changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Flip IsotopeWrenExportService's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"IsotopeHarborIndexCoordinator: handle the lingering thing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"IsotopeTideWorkerCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Korrigiere den IsotopeMarbleTokenStore-Timeout","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"de"} +{"prompt":"This should remain a deliberately small patch: IsotopeCinderAuthService has one known configuration mistake in projects/isotope/cmd/exporter/main.py, not an open-ended failure investigation. Correct the known literal and the test that intentionally mirrors it; the final diff should stay local enough for an on-call engineer to verify at a glance.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing WebGPU deployment\n- keep the work scoped to IsotopeCinderAuthService and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Nimbus: The destination for IsotopeDeltaCanvasService is broadly agreed; the missing piece is a reversible route from projects/isotope/internal/auth/refresh.go to that target. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeDeltaCanvasService\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Any races in IsotopeSummitProxyStore?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Sketch the IsotopeQuartzPlayerStore migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Opal: Test Suite 'IsotopeRainfallDBFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[IsotopeRainfallDBFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/isotope/db/migrations/20260730_events.sql:144: error: -[IsotopeRainfallDBFlowTests testRestoresSelectionAfterBackgrounding] : XCTAssertEqual failed: (\"Optional(4)\") is not equal to (\"Optional(3)\")\nAccessibility hierarchy at failure:\n Application, 0x104c, pid: 812\n Window, identifier: \"main\"\n NavigationStack, identifier: \"catalog\"\n Button, label: \"Filters\", value: \"2 active\"\n CollectionView, identifier: \"results-grid\", rows: 24\n Sheet, identifier: \"filter-sheet\"\n TextField, label: \"Search filters\", value: \"\"\n Switch, label: \"Available offline\", value: \"1\"\n Button, label: \"Apply\", enabled: true\nTest Case '-[IsotopeRainfallDBFlowTests testRestoresSelectionAfterBackgrounding]' failed (4.812 seconds).\n\nSimulator: iPhone 17 Pro, iOS 27.0, en_US, content size XXXL, Reduce Motion enabled. The screenshot looks correct. The mismatch is the internal selected-segment index after the scene becomes active; tapping Apply a second time makes it three again.\n\nBring IsotopeRainfallDBFlow's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"diff --git a/projects/isotope/db/migrations/20260730_events.sql b/projects/isotope/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/db/migrations/20260730_events.sql\n+++ b/projects/isotope/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is IsotopeVelaDrawerFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"# projects/isotope/ml/pipeline/features.py\n[worker.isotopecinderauthcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.isotopecinderauthcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.isotopecinderauthcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.IsotopeCinderAuthCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-49157\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nThe intended correction is already known: change only the stale 15-second setting to 30 seconds in projects/isotope/ml/pipeline/features.py and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"IsotopeOspreyJobCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"IsotopeIrisBatchCoordinator: diagnose, then assess","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"What sequence would let IsotopeFlintTimelineStore adopt PostgreSQL 17 with dual reads but no dual writes? Include data validation, canary scope, and the decision that ends compatibility mode.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Prism: Two asks around IsotopeCoralUploadCoordinator: (1) lay out a staged migration for IsotopeCoralUploadCoordinator; (2) then implement the bounded durable-cursor handler. Keep the patch readable for a small on-call review, and leave a clear boundary between the resulting artifacts or edits.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Quartz: # projects/isotope/workers/thumbnail/consumer.ex\n[worker.isotopeacornwidgetflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.isotopeacornwidgetflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.isotopeacornwidgetflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.IsotopeAcornWidgetFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-49129\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Make the one confirmed configuration correction in projects/isotope/workers/thumbnail/consumer.ex. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"pasted-context","lang":"en"} +{"prompt":"Sketch the IsotopeAtlasSearchStore migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Dedupe IsotopeDriftConsoleService's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-49111\n\n08:02 deploy IsotopeBasilRunnerFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCapture the IsotopeBasilRunnerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Two deliverables are holding up IsotopeEchoRegistryCoordinator. First, lay out a staged migration for IsotopeEchoRegistryCoordinator. In the same workstream, also add the visible loading and offline states. The relevant starting point is projects/isotope/lib/codec/frame.cc, which follows Tokio conventions and currently suffers from a misleading timeout name used in five packages. Keep the patch readable for a small on-call review.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"IsotopeFrostPanelStore's openapi.yaml needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"$ pnpm test --filter IsotopeNimbusFormCoordinator\n RUN v3.2.4 /workspace/apps/console\n × IsotopeNimbusFormCoordinator > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=49153 phase=resume storedCursor=seg-0183\n session=49153 phase=fetch requestCursor=seg-0183 pageSize=200\n session=49153 phase=commit receivedCursor=seg-0184 itemCount=0\n session=49153 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Find the source of this IsotopeNimbusFormCoordinator symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"We need to move IsotopeRavenSessionFlow from the legacy store to Tokio. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"IsotopeRainfallDBCoordinator: give it a nicer flow","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Raven: Incident timeline — INC-49125\n\n08:02 deploy IsotopeOrbitSyncFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nFrom this evidence, draft consumer-facing migration guidance for IsotopeOrbitSyncFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Give IsotopeNimbusFormStore's detail pane a sticky action bar, fluid type at narrow widths, and a keyboard-safe scroll region that still works at 200% zoom.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"IsotopeHarborIndexStore's metric is misspelled as succesful_total in one declaration. Correct that literal and its exact test expectation, without renaming anything else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Sable: projects/isotope/apps/console/routes/usage.svelte の IsotopeCraneWorkspaceService で、SQLite の flow に断続的な問題が起きています。 責務を分離して重複をなくし、API、wire value、順序、観測可能な動作は変えないでください。\n\n制約:\n- SQLite を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は IsotopeCraneWorkspaceService のみ","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"} +{"prompt":"Correct the IsotopeKiteSchedulerService flag default","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Bump IsotopeSlateEditorService's timeout to 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating a deadlock that appears only during shutdown in IsotopeRainfallDBStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Read projects/isotope/db/migrations/20260730_events.sql and tell me whether IsotopeRainfallDBService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"IsotopeOpalRouterCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Fresh release brief for IsotopeEmberRelayCoordinator:\n- primary outcome: lay out a staged migration for IsotopeEmberRelayCoordinator\n- companion outcome: then implement the bounded durable-cursor handler\n- repository entry point: projects/isotope/Sources/App/SessionStore.swift\n- platform constraint: WebGPU\n- known complication: two validators with subtly different error strings\n\nBoth results are required, but they should remain independently reviewable. Keep the patch readable for a small on-call review; retain serialization and authorization boundaries; cover cancellation, idempotent retries, and rollback; and avoid drive-by cleanup. Use the code as the source of truth, call out assumptions, and state how an on-call engineer can tell that either part is unsafe to ship.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Check IsotopeBeaconStoreService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"IsotopeCloudReconcilerCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-49117\n\n08:02 deploy IsotopeKiteSchedulerFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCapture the IsotopeKiteSchedulerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"The public surface of IsotopeWillowCodecStore is frozen, but its internal ownership in projects/isotope/apps/console/routes/usage.svelte is difficult to test and even harder to change safely. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeWillowCodecStore\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"IsotopePineMetricsCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"In projects/isotope/config/staging.toml hat IsotopeBasilRunnerService ein sporadisches Problem im NATS JetStream-Ablauf. Verfasse eine Consumer-Doku mit Vertrag, Fehlern, Retry und einem kopierbaren Beispiel; ändere keinen Handler.\n\nRandbedingungen:\n- NATS JetStream weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf IsotopeBasilRunnerService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um IsotopeBasilRunnerService mit NATS JetStream kompatibel.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"de"} +{"prompt":"Tide: // projects/isotope/apps/console/routes/usage.svelte\nfinal class IsotopeIrisBatchFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nSplit IsotopeIrisBatchFlow by responsibility and make cancellation ownership explicit. Characterize the current sequence before moving code and keep callers unchanged.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"I inherited IsotopeKiteSchedulerStore and need a careful read of projects/isotope/cmd/exporter/main.py before I can sign off on the next release. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing WebGPU deployment\n- keep the work scoped to IsotopeKiteSchedulerStore and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.\n\nNothing is reported broken, so judge and explain current behavior without inventing a failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"The first IsotopeOspreyJobStore request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"IsotopeNovaPickerCoordinator: polish the last piece","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"diff --git a/projects/isotope/infra/modules/edge/main.tf b/projects/isotope/infra/modules/edge/main.tf\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/infra/modules/edge/main.tf\n+++ b/projects/isotope/infra/modules/edge/main.tf\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit IsotopeDeltaCanvasCoordinator by responsibility and make cancellation ownership explicit. Characterize the current sequence before moving code and keep callers unchanged.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"IsotopeJuniperCLICoordinator: sort out the rough edge","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Ownership of IsotopeEmberRelayStore is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Give me a staged design with ownership boundaries, compatibility seams, migration order, telemetry, failure drills, rollback criteria, and explicit decisions we can defer; stop before implementation.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current WebGPU operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Umbra: Incident timeline — INC-49141\n\n08:02 deploy IsotopeAsterWebhookFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current IsotopeAsterWebhookFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Our support and SDK teams keep answering the same questions about IsotopeEchoRegistryStore, but the current prose in projects/isotope/lib/codec/frame.cc only describes the happy path. Draft an ADR plus migration note that records the decision, rejected alternatives, compatibility window, observability signals, and the exact action required from consumers.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing Tokio deployment\n- keep the work scoped to IsotopeEchoRegistryStore and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"En projects/isotope/apps/console/routes/usage.svelte, IsotopeNimbusFormService tiene un problema intermitente en el flujo de SQLite. Sigue queue, scheduler y cancelación, compara hipótesis y encuentra la causa antes de proponer cambios.\n\nRestricciones:\n- seguir con SQLite\n- conservar compatibilidad y cancelación\n- limitar el cambio a IsotopeNimbusFormService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"es"} +{"prompt":"projects/isotope/web/components/FilterDrawer.vue 里的 IsotopeJuniperCLIService 最近在 PostgreSQL 17 流程中出现间歇性问题。 请完成 responsive layout、空状态、retry、键盘焦点、dark mode 和 reduced motion。\n\n约束：\n- 继续使用 PostgreSQL 17\n- 保持兼容性和取消语义\n- 改动只限于 IsotopeJuniperCLIService","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"zh"} +{"prompt":"Milestones for replacing IsotopeWrenExportStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Flip IsotopeVelaDrawerStore's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Security flagged IsotopeBirchMigratorStore for a read-only pass because its Tokio boundary mixes tenant data, retries, and cancellation in subtle ways. Trace ownership, ordering, error propagation, and cancellation; call out concrete risks with file references, but do not edit the implementation or turn the answer into a replacement design.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current Tokio operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.\n\nNothing is reported broken, so judge and explain current behavior without inventing a failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"IsotopePrismCacheCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"# CI job 49130: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: PostgreSQL 17\n\n[setup] restoring cache key deps-a2f91c ... hit\n[setup] starting postgres:17 ... healthy after 4.2s\n[setup] starting redis:8 ... healthy after 0.8s\n[test] shard 3/8 selected 412 tests\n[test] IsotopeQuartzPlayerFlowIntegration.replays_after_timeout ... ok\n[test] IsotopeQuartzPlayerFlowIntegration.cancels_orphaned_batch ... FAILED\n\nExpected:\n pending_jobs{queue=\"replay\"} 0\nActual:\n pending_jobs{queue=\"replay\"} 1\n\nCaptured spans:\n batch.receive 2.1ms status=ok\n storage.transaction 44.8ms status=cancelled\n batch.nack \n\nteardown warning: resource still in use: redis connection pool (1 borrower)\nretry 1/2 with identical seed ... passed\nretry 2/2 with identical seed ... passed\n\nThe failure began after the test suite was sharded, but it sometimes appears on an unsharded nightly run. There are no wall-clock sleeps in this test; it advances the fake scheduler until idle.\n\nDeliver the IsotopeQuartzPlayerFlow server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Vela: // projects/isotope/engine/render/atlas.cpp\nfinal class IsotopeEchoRegistryFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nWalk through what the artifact proves about IsotopeEchoRegistryFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Willow: diff --git a/projects/isotope/Sources/CLI/Commands/Doctor.swift b/projects/isotope/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/isotope/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nWire IsotopeMoonlitSDKCoordinator's schema, storage, handler, and worker path so continuation is signed, duplicate delivery is stable, and shutdown cannot acknowledge uncommitted work.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Our support and SDK teams keep answering the same questions about IsotopeGarnetModalService, but the current prose in projects/isotope/packages/api/openapi.yaml only describes the happy path. Draft an ADR plus migration note that records the decision, rejected alternatives, compatibility window, observability signals, and the exact action required from consumers.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing NATS JetStream deployment\n- keep the work scoped to IsotopeGarnetModalService and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Xylem: # projects/isotope/engine/render/atlas.cpp\n[worker.isotoperavensessioncoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.isotoperavensessioncoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.isotoperavensessioncoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.IsotopeRavenSessionCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-49154\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nThe intended correction is already known: change only the stale 15-second setting to 30 seconds in projects/isotope/engine/render/atlas.cpp and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current IsotopeMicaProfileService design actually guarantees what its callers assume. Follow one successful request and each early exit through the code, then rank findings by impact and state which apparent hazards are already ruled out by invariants.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeMicaProfileService\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"IsotopeMapleQueueCoordinator: assess, then document","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"PM needs a concise migration note for IsotopeMicaProfileStore, including the user impact, rollback trigger, and the one configuration key operators must change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"IsotopeFrostPanelCoordinator needs a paired pass: find the unknown cause of stale cursors when a page is resumed, plus capture the contract and rollback note for consumers. Use projects/isotope/packages/api/openapi.yaml as the source of truth, preserve the NATS JetStream contract, and avoid unrelated cleanup.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Yarrow: The IsotopeGarnetModalStore empty state in projects/isotope/config/staging.toml needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Zephyr: Incident timeline — INC-49147\n\n08:02 deploy IsotopeOspreyJobFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current IsotopeOspreyJobFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Sequence IsotopeFernSnapshotService's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Release verification found a single stale IsotopeLumenChartService value; the cause, desired value, and affected assertion are already agreed. Change the staging timeout from 15 seconds to 30, adjust the adjacent assertion that encodes that value, and avoid unrelated formatting, renames, dependency bumps, or cleanup.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current SQLite operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Memory attributed to IsotopeLedgerGateStore rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"IsotopeCopperBridgeCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"PM is preparing the IsotopeBirchMigratorService rollout and needs prose that works for both application developers and the operators who will carry the pager. Turn the repository behavior into a compact reference with prerequisites, request and response examples, failure semantics, a rollback note, and links to the authoritative config keys.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeBirchMigratorService\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"IsotopeVelaDrawerCoordinator: polish, then assess","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Polish the IsotopeQuartzPlayerService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"One contained cleanup in projects/isotope/ui/settings/PrivacyPane.tsx: remove the obsolete IsotopeHarborIndexService import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Security flagged IsotopeMoonlitSDKService for a read-only pass because its WebGPU boundary mixes tenant data, retries, and cancellation in subtle ways. Trace ownership, ordering, error propagation, and cancellation; call out concrete risks with file references, but do not edit the implementation or turn the answer into a replacement design.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current WebGPU operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"How does IsotopeOpalRouterService propagate cancellation through the PostgreSQL 17 boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-49110\n\n08:02 deploy IsotopeSpruceDaemonFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nReconstruct the IsotopeSpruceDaemonFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Before we approve IsotopeTideWorkerStore, assess whether an accessibility label that reads the internal enum is an actual correctness risk or merely confusing structure. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Em projects/isotope/services/ledger/replay.go, o IsotopeJuniperCLIStore tem um problema intermitente no fluxo de PostgreSQL 17. Siga queue, scheduler e cancelamento, compare hipóteses e encontre a causa antes de mudar código.\n\nRestrições:\n- continuar com PostgreSQL 17\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao IsotopeJuniperCLIStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"pt"} +{"prompt":"diff --git a/projects/isotope/pkg/cache/lease.rs b/projects/isotope/pkg/cache/lease.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/pkg/cache/lease.rs\n+++ b/projects/isotope/pkg/cache/lease.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate IsotopeMapleQueueFlow's parallel adapters behind a single internal boundary, with no changes to API, timing, serialization, metrics, or error text.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Design handed over a final pass for IsotopeSpruceDaemonService, and the basic data flow in projects/isotope/infra/modules/edge/main.tf already works. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing PostgreSQL 17 deployment\n- keep the work scoped to IsotopeSpruceDaemonService and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"For IsotopeAcornWidgetCoordinator, assess ownership and failure handling in projects/isotope/ui/settings/PrivacyPane.tsx; once that is complete, capture the contract and rollback note for consumers. Work from projects/isotope/ui/settings/PrivacyPane.tsx, stay with Tokio, and keep the patch readable for a small on-call review. Keep the two outcomes separately reviewable.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Checkout: Incident timeline — INC-49131\n\n08:02 deploy IsotopeFrostPanelFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nTurn the artifact into a reversible IsotopeFrostPanelFlow rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"IsotopeDeltaCanvasStore's staging timeout is already known to be wrong: change the single projects/isotope/infra/modules/edge/main.tf value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-49135: finish the compact IsotopeJuniperCLIFlow filter experience\n\nRoute: /catalog/search\nSource: projects/isotope/web/components/FilterDrawer.vue\nFramework: PostgreSQL 17\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring IsotopeJuniperCLIFlow's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"IsotopeWillowCodecCoordinator is blocking the next release because memory growth during hour-long imports. I need two concrete outcomes from a single pass: produce a consumer guide for IsotopeWillowCodecCoordinator, and give the existing implementation a read-only safety pass. Use the existing SQLite conventions in projects/isotope/apps/console/routes/usage.svelte; keep the patch readable for a small on-call review. Keep the outcomes distinct so reviewers can see which evidence supports the assessment and which files or prose satisfy the requested change.\n\nConstraints:\n- preserve public wire values and tenant boundaries\n- cover cancellation and retry behavior\n- avoid generated code and unrelated cleanup\n- include a rollback trigger that an on-call engineer can measure\n\nThis is a fresh workstream for the release, so derive everything from the repository and the context here.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"For IsotopeBeaconStoreCoordinator, separate IsotopeBeaconStoreCoordinator's policy from transport without behavior changes; once that is complete, give the existing implementation a read-only safety pass. Work from projects/isotope/pkg/cache/lease.rs, stay with NATS JetStream, and keep the patch readable for a small on-call review. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"# projects/isotope/ml/pipeline/features.py\n[worker.isotopecedarpolicyflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.isotopecedarpolicyflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.isotopecedarpolicyflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.IsotopeCedarPolicyFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-49137\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Align IsotopeCedarPolicyFlow's staging timeout with the shown production value and refresh only the focused config test; nothing else in the paste should move.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"IsotopePrismCacheStore's staging timeout is already known to be wrong: change the single projects/isotope/db/migrations/20260730_events.sql value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Style IsotopeSummitProxyService's offline state","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Drop IsotopeAmberFilterStore's unused import","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Give IsotopeAcornWidgetService a README example","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-49136: retire the legacy replay path for IsotopePineMetricsFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nUsing this as the starting evidence, propose a staged IsotopePineMetricsFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"This should remain a deliberately small patch: IsotopeRavenSessionService has one known configuration mistake in projects/isotope/lib/codec/frame.cc, not an open-ended failure investigation. Correct the known literal and the test that intentionally mirrors it; the final diff should stay local enough for an on-call engineer to verify at a glance.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing Tokio deployment\n- keep the work scoped to IsotopeRavenSessionService and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-49127\n\n08:02 deploy IsotopeCoralUploadFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nTurn the material above into a concise IsotopeCoralUploadFlow release note and operator runbook section. State impact, detection, rollback, and the client-visible contract; do not modify code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} +{"prompt":"IsotopePrismCacheService has four wrappers that only translate the same error enum. Collapse them into one adapter and preserve every public case, message, and metric label.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-49143: retire the legacy replay path for IsotopeCraneWorkspaceFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nAssess IsotopeCraneWorkspaceFlow for durability, tenant isolation, races, and misleading observability. Separate blockers from questions and do not produce a patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Flip IsotopeBeaconStoreStore's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"The IsotopeCinderAuthStore empty state in projects/isotope/ml/pipeline/features.py needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"IsotopeAtlasSearchCoordinator: restructure, then correct","purpose":"refactor","secondary":"debugging","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"diff --git a/projects/isotope/internal/auth/refresh.go b/projects/isotope/internal/auth/refresh.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/internal/auth/refresh.go\n+++ b/projects/isotope/internal/auth/refresh.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate IsotopeCopperBridgeFlow's parallel adapters behind a single internal boundary, with no changes to API, timing, serialization, metrics, or error text.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Exporter: Ticket OPS-49134: retire the legacy replay path for IsotopeLedgerGateFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for IsotopeLedgerGateFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"} +{"prompt":"UI ticket DES-49149: finish the compact IsotopeSableParserFlow filter experience\n\nRoute: /catalog/search\nSource: projects/isotope/workers/thumbnail/consumer.ex\nFramework: Tokio\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nUse the UI evidence to complete IsotopeSableParserFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":"debugging","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Scheduler: Ticket OPS-49120: retire the legacy replay path for IsotopeSummitProxyFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nCapture the IsotopeSummitProxyFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Is there a cleaner way to separate IsotopeSableParserStore's transport, persistence, and retry policy without changing its API or timing behavior? Go ahead and make that structural change.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Check IsotopeVelaDrawerService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Dashboard: For IsotopeSlateEditorCoordinator, change IsotopeSlateEditorCoordinator's known staging timeout from 15 to 30 seconds; once that is complete, give the existing implementation a read-only safety pass. Work from projects/isotope/Sources/App/SessionStore.swift, stay with WebGPU, and keep the patch readable for a small on-call review. Keep the two outcomes separately reviewable.","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Worker: diff --git a/projects/isotope/pkg/cache/lease.rs b/projects/isotope/pkg/cache/lease.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/pkg/cache/lease.rs\n+++ b/projects/isotope/pkg/cache/lease.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit IsotopeMicaProfileCoordinator by responsibility and make cancellation ownership explicit. Characterize the current sequence before moving code and keep callers unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Our support and SDK teams keep answering the same questions about IsotopeWillowCodecService, but the current prose in projects/isotope/app/src/main/SyncWorker.kt only describes the happy path. Draft an ADR plus migration note that records the decision, rejected alternatives, compatibility window, observability signals, and the exact action required from consumers.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing SQLite deployment\n- keep the work scoped to IsotopeWillowCodecService and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"IsotopeOrbitSyncCoordinator needs a paired pass: produce a consumer guide for IsotopeOrbitSyncCoordinator, plus give the existing implementation a read-only safety pass. Use projects/isotope/web/components/FilterDrawer.vue as the source of truth, preserve the PostgreSQL 17 contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Simulator: PM is preparing the IsotopeSpruceDaemonStore rollout and needs prose that works for both application developers and the operators who will carry the pager. Turn the repository behavior into a compact reference with prerequisites, request and response examples, failure semantics, a rollback note, and links to the authoritative config keys.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeSpruceDaemonStore\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Responsive layout for IsotopeFrostPanelService","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Could IsotopeCopperBridgeService show the active PostgreSQL 17 sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Runbook: diff --git a/projects/isotope/web/components/FilterDrawer.vue b/projects/isotope/web/components/FilterDrawer.vue\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/web/components/FilterDrawer.vue\n+++ b/projects/isotope/web/components/FilterDrawer.vue\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is IsotopeDriftConsoleFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"IsotopeMarbleTokenCoordinator: sequence, then restructure","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"// projects/isotope/packages/api/openapi.yaml\nfinal class IsotopeMosaicGridFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Deliver the IsotopeMosaicGridFlow server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Trace: Ticket OPS-49119: retire the legacy replay path for IsotopeMarbleTokenFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nAssess IsotopeMarbleTokenFlow for durability, tenant isolation, races, and misleading observability. Separate blockers from questions and do not produce a patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"A copied hex color in IsotopeNimbusFormFlow lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Two deliverables are holding up IsotopeBasilRunnerCoordinator. First, separate IsotopeBasilRunnerCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/isotope/packages/api/openapi.yaml, which follows NATS JetStream conventions and currently suffers from a query plan that changes after statistics refresh. Keep the patch readable for a small on-call review.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Profiler: Incident timeline — INC-49145\n\n08:02 deploy IsotopeOpalRouterFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Using this as the starting evidence, propose a staged IsotopeOpalRouterFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"IsotopeAsterWebhookCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"IsotopeLumenChartFlow has four wrappers that only translate the same error enum. Collapse them into one adapter and preserve every public case, message, and metric label.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"IsotopeCoralUploadService é seguro?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"pt"} +{"prompt":"Console: // projects/isotope/config/staging.toml\nfinal class IsotopeGarnetModalCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nRestructure IsotopeGarnetModalCoordinator so duplicated normalization and shutdown ownership have one home. Preserve public behavior, wire values, logging fields, and ordering; extend characterization coverage first.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"A previously stable test around IsotopeMicaProfileFlow now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Teach IsotopeAsterWebhookService to verify signed continuation tokens, reject cross-tenant cursors, and rotate keys without invalidating tokens issued during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Workspace: projects/isotope/crates/index/src/segment.rs now contains IsotopePineMetricsStore's normalization branch three times. Consolidate it behind one private helper, keep call ordering identical, and avoid touching generated code. Please preserve behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Document IsotopeOrbitSyncStore's cancellation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Documente le contrat IsotopeCoralUploadStore","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"fr"} +{"prompt":"The first IsotopeSableParserService request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"IsotopeCedarPolicyCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Repository: The name pendingAck means two different things across IsotopeMoonlitSDKStore's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Pipeline: // projects/isotope/web/components/FilterDrawer.vue\nfinal class IsotopeFlintTimelineCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nConsolidate IsotopeFlintTimelineCoordinator's parallel adapters behind a single internal boundary, with no changes to API, timing, serialization, metrics, or error text.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} diff --git a/data/round2-10.jsonl b/data/round2-10.jsonl index f241ecb..6d9bc21 100644 --- a/data/round2-10.jsonl +++ b/data/round2-10.jsonl @@ -1,200 +1,200 @@ -{"prompt": "the agent stops reporting on some hosts after a kernel upgrade:\n\nlevel=info msg=\"loading eBPF programs\" kernel=6.11.0-19-generic btf=/sys/kernel/btf/vmlinux\nlevel=error msg=\"failed to load program\" prog=tcp_connect err=\"field Sport: can't resolve field: not found\"\nlevel=error msg=\"failed to load program\" prog=tcp_close err=\"field Sport: can't resolve field: not found\"\nlevel=warn msg=\"falling back to procfs polling\" interval=10s\nlevel=info msg=\"agent started\" mode=degraded programs_loaded=3/9\n\nsame binary, same config, works on 6.8 hosts. the struct sock layout changed and we compile with CO-RE, which was supposed to handle exactly this", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "agent CPU spikes to a full core on hosts with many containers and stays there:\n\nperf top -p 41221:\n 38.11% [kernel] [k] bpf_prog_a11c3f2_tcp_connect\n 21.44% agent [.] lumen/agent/proc.(*Resolver).containerFor\n 14.02% agent [.] runtime.mapaccess2_faststr\n 9.88% agent [.] os.ReadFile\n 4.11% [kernel] [k] __d_lookup\n\ncontainerFor reads /proc//cgroup on every event and parses it; the host runs 400 containers and about 12,000 events a second", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "our go modules define three `Meta` types that are converted between at every boundary", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "listing search returns nothing for one region and the logs are unhelpful:\n\nElasticsearch::Transport::Transport::Errors::BadRequest ([400] {\"error\":{\"root_cause\":[{\"type\":\"query_shard_exception\",\"reason\":\"failed to create query: [geo_bounding_box] field [location] is not a geo_point field\"}],\"type\":\"search_phase_execution_exception\",\"phase\":\"query\",\"grouped\":true}})\n app/queries/listing_search.rb:88:in `execute'\n app/controllers/api/v3/listings_controller.rb:22:in `index'\n\nindex mapping for listings-2026-07:\n \"location\": { \"type\": \"object\", \"properties\": { \"lat\": {\"type\":\"float\"}, \"lon\": {\"type\":\"float\"} } }\n\nindex mapping for listings-2026-06:\n \"location\": { \"type\": \"geo_point\" }\n\nthe july index was created by a rollover after someone deleted the index template last month", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "agent's memory grows on busy hosts until the OOM killer takes it:\n\nrss: 180MB → 2.1GB over 4 hours\nbpf map usage:\n connections max_entries=65536 current=65536 (full)\n sockets max_entries=65536 current=65536 (full)\n events (ringbuf) 16MB, consumer lag 14MB\n\ngo heap profile:\n flat flat% cum cum%\n 1.4GB 62.1% 1.4GB 62.1% lumen/agent/enrich.(*Cache).Put\n 0.4GB 17.8% 0.4GB 17.8% encoding/json.Marshal\n\nCache is keyed by (pid, fd) with no eviction, and on this host processes churn thousands of short-lived connections a second", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "agent config across environments, and only prod fills its maps:\n\n# staging\nmap_sizes: { connections: 65536, sockets: 65536 }\nsample_rate: 1.0\nenrich: { container: true, k8s: false, process_tree: false }\ncpu_limit_percent: 10\nhosts: 40\n\n# prod\nmap_sizes: { connections: 65536, sockets: 65536 }\nsample_rate: 1.0\nenrich: { container: true, k8s: true, process_tree: true }\ncpu_limit_percent: 10\nhosts: 40000\n\nstaging hosts run 5 containers each, prod hosts run up to 400, and process_tree is the option that doubles memory", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "the map screen", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "our API changelog needs an entry for the fixed page size and what partners should do about it", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "saved searches fire notifications for listings that don't match, here's one:\n\nsaved_search 4471:\n bbox: [-0.21, 51.48, -0.09, 51.53]\n min_beds: 2\n max_price_cents: 65000000\n property_type: [\"flat\", \"maisonette\"]\n\nlisting 88412 that triggered it:\n location: { lat: 51.61, lon: -0.19 }\n beds: 2\n price_cents: 62000000\n property_type: \"house\"\n\nthe matcher runs as a percolator query built from the saved search, and both the bbox and the type are wrong here", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "what does the ringbuffer do when full?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "a customer needs the agent on 5.4 kernels, which we dropped in 2.4 because CO-RE and ring buffers made everything simpler. i'd like an honest view of what supporting them again costs — a compatibility layer, a separate build, or declining the business — and what it means for the next two years of kernel support the deal is worth about a fifth of our ARR, so \"no\" needs to be well argued.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "agent's configuration, which customers deploy across their fleets with no documentation beyond a sample file:\n\nagent:\n endpoint: https://ingest.lumen.io\n tenant_key: \n sample_rate: 1.0 # events per second per process, 0 disables\n programs: [tcp, dns, file, exec]\n map_sizes: { connections: 65536, sockets: 65536 }\n ringbuf_bytes: 16777216\n enrich: { container: true, k8s: true, process_tree: false }\n fallback_procfs: true\n cpu_limit_percent: 10\n\nthings only we know: sample_rate is per process, not per host, so a host with 500 processes is not sampled at all; cpu_limit_percent is advisory and enforced by our own scheduler, not cgroups; map_sizes above 65536 need a kernel with BPF_MAP_TYPE_LRU_HASH support; and turning on process_tree roughly doubles memory", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "listing count says \"1 results\"", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "core", "lang": "en"} -{"prompt": "compiler miscompiles one function under -O2 and i've reduced it this far:\n\nerror: internal compiler error: broken MIR in Item DefId(0:412 ~ lumenc[a11c]::opt::fold)\n --> src/opt/fold.rs:141:9\n |\n141| let folded = self.fold_const(expr)?;\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n = note: value of type `ConstValue` has no in-memory representation\n\nthread 'rustc' panicked at compiler/rustc_middle/src/ty/consts.rs:88:22:\nassertion failed: !ty.has_infer()\nstack backtrace:\n 0: rust_begin_unwind\n 4: lumenc::opt::fold::ConstFolder::fold_binary\n 5: lumenc::opt::run_passes\n\nonly with our own const-folding pass enabled, and only when the input has a shift by a value we can't prove is in range", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "compiler's incremental builds are wrong about one in fifty times and it's terrifying:\n\n$ lumenc build\n Compiling app v0.4.1\n Finished in 2.1s\n$ ./target/app\nsegmentation fault\n\n$ lumenc build --no-incremental\n Compiling app v0.4.1\n Finished in 41.2s\n$ ./target/app\nok\n\nfingerprint debug output for the changed module:\n src/render.lm mtime=1753843201 size=8412 hash=9c1d0044 deps=[math, gfx]\n cached fingerprint: mtime=1753843201 size=8412 hash=9c1d0044 deps=[math]\n\nthe dependency list changed but the hash didn't, because the hash covers the source text and not the resolved imports", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "three services build the same \"is this listing visible\" condition and they disagree:\n\n# api/v3/listings_controller.rb\nscope.where(status: %w[live under_offer]).where(published_at: ..Time.current)\n\n# jobs/portal_feed_job.rb\nscope.where(status: \"live\").where.not(published_at: nil)\n\n# app/queries/saved_search_matcher.rb\nscope.where(\"status != 'withdrawn'\").where(\"published_at IS NOT NULL\")\n\nthe first includes under-offer listings, the second excludes them, and the third includes drafts that happen to have a published_at from a previous publish", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "pass manager has grown conditionals for every pass we've added. same output, better structure:\n\npub fn run_passes(module: &mut Module, opts: &Opts) {\n if opts.opt_level >= 1 { inline::run(module, opts.inline_threshold); }\n if opts.opt_level >= 1 && !opts.no_const_fold { fold::run(module); }\n if opts.opt_level >= 2 { \n loop_opt::run(module);\n if !opts.no_vectorize && module.target.has_simd() { vectorize::run(module); }\n }\n if opts.debug_assertions { assert_checks::run(module); }\n if opts.opt_level >= 2 && opts.lto { cross_module::run(module); }\n if opts.opt_level >= 1 { dce::run(module); }\n if opts.emit_ir { dump_ir(module); }\n if opts.opt_level >= 2 { fold::run(module); } // second fold, added later, nobody remembers why\n}", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "portal partner's feed specification, which we produce:\n\nnightly full feed plus a delta feed every 15 minutes\n full: gzipped NDJSON, one listing per line, uploaded to their SFTP by 05:00\n delta: same shape, only listings changed since the last delta, plus a `deleted` array of ids\n a listing that is withdrawn must appear in `deleted`, not merely be absent\n price changes must produce a delta entry, which today they do not because price lives in a separate table with its own timestamp\n every entry needs a stable `source_id` that survives a listing being unpublished and republished\n they process deltas in order and will reject a delta whose sequence number is not consecutive\n if we miss a delta window, the next one must include everything since the last successful one", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "one visibility scope for listings", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "is that transmute actually sound?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "incremental compilation is wrong about one build in fifty and the cause is that fingerprints hash source text but not the resolved dependency set, which the original RFC explicitly rejected as expensive. i want the fix designed properly — what goes into a fingerprint, how we invalidate the existing caches on upgrade, and how we'd detect a recurrence in CI rather than in a customer's production binary two customers have shipped a binary built this way, which is the part that keeps me up.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "i'd like an honest read of whether a plugin can crash the compiler with an out-of-range span, and if so the validation that stops it — with a test that used to crash i'd like enough detail that i can hand it to someone else to finish.", "purpose": "review", "secondary": "backendImpl", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "a prospect's security team has asked six pointed questions about what the agent collects, what happens when our endpoint is unreachable, and the blast radius of a bad eBPF program. answer each from the code and write it as a page we can publish, rather than an email that gets forwarded and misquoted they will forward whatever we write to their own security review, so it has to survive being read carefully.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "saved searches notify on listings that match neither the bounding box nor the property type, which suggests the percolator query is built from stale saved-search fields. diagnose it, then fix the builder", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "what happens to buffered events when the agent is restarted mid-upload", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "react native app crashes when returning from the camera on android 15 only:\n\nFATAL EXCEPTION: main\nProcess: com.lumen.estate, PID: 8812\njava.lang.RuntimeException: Unable to resume activity {com.lumen.estate/com.lumen.estate.MainActivity}: java.lang.IllegalStateException: Can not perform this action after onSaveInstanceState\n\tat android.app.ActivityThread.performResumeActivity(ActivityThread.java:5412)\n\tat androidx.fragment.app.FragmentManager.checkStateLoss(FragmentManager.java:1882)\n\tat com.lumen.estate.photos.PhotoPickerModule.onActivityResult(PhotoPickerModule.java:141)\n\nonly when the system killed our activity while the camera was open, which android 15 does far more aggressively", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "before this goes in, is the unsafe block justified or are we fooling ourselves?\n\npub fn intern(&self, s: &str) -> Symbol {\n if let Some(&sym) = self.map.borrow().get(s) {\n return sym;\n }\n let owned = s.to_owned();\n let leaked: &'static str = unsafe { std::mem::transmute::<&str, &'static str>(&owned) };\n std::mem::forget(owned);\n let sym = Symbol(self.strings.borrow().len() as u32);\n self.strings.borrow_mut().push(leaked);\n self.map.borrow_mut().insert(leaked, sym);\n sym\n}\n\nthe interner is per-compilation-session, sessions are dropped between builds in the language server, and the language server is long-lived", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "eBPF program's map handling, which i'd like a second opinion on before we ship it widely:\n\nSEC(\"kprobe/tcp_connect\")\nint BPF_KPROBE(tcp_connect, struct sock *sk) {\n struct conn_key key = {};\n key.pid = bpf_get_current_pid_tgid() >> 32;\n BPF_CORE_READ_INTO(&key.sport, sk, __sk_common.skc_num);\n BPF_CORE_READ_INTO(&key.daddr, sk, __sk_common.skc_daddr);\n\n struct conn_val val = {};\n val.ts = bpf_ktime_get_ns();\n bpf_map_update_elem(&connections, &key, &val, BPF_ANY);\n\n struct event *e = bpf_ringbuf_reserve(&events, sizeof(*e), 0);\n if (!e) return 0;\n e->pid = key.pid;\n bpf_ringbuf_submit(e, 0);\n return 0;\n}\n\nthe connections map is a hash with 65536 entries and nothing deletes from it except a userspace sweep every 30 seconds", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "por favor revisa la consulta de búsqueda antes de que la pongamos en producción:\n\ndef execute\n Listing.search(\n query: {\n bool: {\n must: [{ match: { description: params[:q] } }],\n filter: [\n { geo_bounding_box: { location: bbox_from(params) } },\n { range: { price_cents: { lte: params[:max_price] } } },\n { terms: { property_type: params[:types] } }\n ]\n }\n },\n size: params.fetch(:size, 50),\n sort: [{ _score: :desc }, { listed_at: :desc }]\n )\nend\n\nparams[:types] llega directamente del cliente sin validar, size no tiene límite superior, y el índice tiene 4 millones de anuncios", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "es"} -{"prompt": "photo pipeline, three lambdas that grew separately. worth a read before i extend it:\n\nupload-handler: validates content-type, writes to s3://raw/, publishes to SNS\nthumbnail-worker: sharp().resize(1200).jpeg({quality: 80}).toBuffer() → s3://thumbs/\nfloorplan-worker: detects floorplans by filename heuristic (\"plan\" in the name), applies OCR, writes JSON\n\nnone of them read EXIF; the thumbnail worker strips all metadata; the floorplan heuristic misfires on any listing whose address contains \"plan\"; and a failure in any of them leaves the listing in \"processing\" forever because the state is only advanced on success", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "mobile app's offline handling for saved listings, which i suspect is why favourites go missing:\n\nconst save = async (listing: Listing) => {\n const current = JSON.parse((await AsyncStorage.getItem('saved')) ?? '[]')\n const next = [...current, listing]\n await AsyncStorage.setItem('saved', JSON.stringify(next))\n try {\n await api.post('/saved', { listingId: listing.id })\n } catch {\n // will sync later\n }\n}\n\nthere is no \"sync later\"; the app also fetches the server list on launch and overwrites AsyncStorage with it", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "changelog for the agent, from the commits since 2.4:\n\n41c9e0b fix(ebpf): CO-RE relocation for struct sock on 6.11 kernels\n88f21c0 feat(maps): LRU hash for the connections map, evicting instead of filling\nc0aa774 perf(enrich): cache container lookups per cgroup id instead of per event\n2e91b45 fix(sample): sample_rate is now per host, not per process\naa30f19 feat(config): cpu_limit_percent enforced via cgroups where available\n9c1d004 chore: minimum kernel is now 5.10\n4410bb7 fix(ringbuf): drop oldest instead of blocking when the consumer is behind\nb77e910 feat(k8s): pod and namespace enrichment from the kubelet API\n\nour readers are platform engineers deploying this to fleets; two of these change behaviour they've built alerts around", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "CI for the compiler takes 40 minutes and this is the whole config:\n\njobs:\n test:\n strategy:\n matrix:\n os: [ubuntu-24.04, macos-15, windows-2022]\n steps:\n - uses: actions/checkout@v4\n - uses: dtolnay/rust-toolchain@1.84\n - run: cargo test --all-features\n - run: cargo test --release --all-features\n - run: ./scripts/run_ui_tests.sh\n - run: cargo bench --no-run\n\nno caching of any kind, the release test run duplicates the debug one for most tests, and the ui test script rebuilds the compiler from scratch", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "unsere React-Native-Screens holen ihre Daten jeweils selbst, mit drei verschiedenen Mustern:\n\n// ListingScreen.tsx\nuseEffect(() => { api.get(`/listings/${id}`).then(setListing) }, [id])\n\n// SavedScreen.tsx\nconst { data } = useQuery({ queryKey: ['saved'], queryFn: fetchSaved })\n\n// SearchScreen.tsx\nconst [state, dispatch] = useReducer(searchReducer, initial)\nuseEffect(() => { let cancelled = false; search(state.filters).then(r => !cancelled && dispatch({type:'ok', r})); return () => { cancelled = true } }, [state.filters])\n\ndrei Muster, drei Fehlerbehandlungen, und nur eines davon behandelt den Offline-Fall überhaupt", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "de"} -{"prompt": "design spec for the map search screen, react native, which is our most-used surface:\n\nMap search\n- Map fills the screen; a bottom sheet at three detents holds the result list, snapping to peek / half / full.\n- Clusters above 12 listings show a count; below that, individual pins priced in thousands (\"£625k\").\n- Panning refetches with a 400ms debounce and a \"Search this area\" button rather than automatic refetch — users hated automatic.\n- Selected pin lifts, turns accent, and scrolls the sheet to that listing without changing the detent.\n- Saved listings show a filled heart on the pin; toggling from the sheet updates the pin immediately and reconciles later.\n- Offline: last results and their photos are shown with a banner; the search button is disabled with an explanation.\n- Accessibility: every pin reachable by the list, which is the accessible path; the map itself is marked as decorative.\n- Must hold 60fps while panning with 300 pins on a mid-range android device from 2021.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "price arrows are colour-only", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "why is incremental sometimes wrong?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "two of the three compiler engineers leave in six weeks and the remaining list includes a soundness landmine, a correctness bug and a pile of ergonomics work. sequence it with the departures as the main constraint, and tell me plainly which item is the most dangerous thing to leave undocumented rather than merely undone the person joining in october has no context on any of this.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "listings stuck in processing generate about forty support calls a week and the fix is always the same re-upload. write the troubleshooting page support can follow, and separately tell me which of the six behaviours in my notes are product bugs that documentation would merely paper over support has no engineering access, so every step has to be something they can do themselves.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "fleet view has to stay usable when the control plane itself is degraded, which today means it shows a spinner forever. rebuild it to the spec with stale data marked by age, filters in the URL, and bulk actions that say how many hosts they will touch before they do it during an incident this screen is the only thing platform engineers trust, so stale-but-labelled beats empty.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "viewing booking service does eight things in one method and only the availability check needs to be transactional. split it, then document the new boundaries and what is guaranteed to have happened by the time the API returns this has come up in three separate reviews now and never gets done.", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "agents stopped loading three eBPF programs after a kernel upgrade despite CO-RE, which is exactly what CO-RE was meant to prevent. work out why the relocation failed, then fix it so the next kernel doesn't do this to us assume whoever picks this up next has no context at all. assume whoever picks it up next has no context beyond what you write.", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "compiler's error messages are inconsistent and i want a house style before we add fifty more. current examples:\n\nerror: type mismatch\nerror: expected `Int`, found `String`\nerror[E0412]: cannot find type `Foo` in this scope\nERROR: unresolved import `std::collectionz`\nerror: the trait bound `T: Display` is not satisfied\nwarning: unused variable x\nnote: `Bar` is defined here but not exported\n\ninconsistent: capitalisation, whether codes are used, whether the primary message names the file, whether we suggest a fix, and whether we use backticks around identifiers\n\nwrite the error message style guide, with rules for wording, structure, spans, notes and suggestions, and rewrite these seven as examples", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "compiler team's list, and one of them is leaving in six weeks:\n\n- incremental fingerprints must include the resolved dependency set, which is the correctness bug\n- error messages need a house style and a lint that enforces it\n- the interner's unsafe transmute is a landmine in the language server\n- plugin diagnostics can crash the compiler with an out-of-range span\n- the second const-fold pass exists for a reason nobody remembers and removing it changes output\n- ui tests take 20 of our 40 CI minutes and rebuild the compiler from scratch\n\nsequence these with the departure in mind, and say plainly which one is the highest risk to leave undone", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "pass manager as an ordered list", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "one cache layer in the agent", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "portal feed shows withdrawn listings for hours and misses price changes entirely, because price lives in a separate table with its own timestamp and the feed keys on the listing's updated_at. before we patch it i'd like a view on whether the feed should be event-driven rather than diff-driven, and what that means for partners who process deltas in strict sequence partners process deltas strictly in sequence and reject anything with a gap.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "en"} -{"prompt": "incremental fingerprint RFC rejected hashing the resolved dependency set as rarely different, which is exactly the case that has now miscompiled production code twice. read the RFC against the current implementation and tell me which of its other assumptions are similarly optimistic i'd rather find the rest of them now than after the next miscompile. flag anything you'd want to change before doing it rather than after.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "en"} -{"prompt": "three services each define what makes a listing visible and they disagree about under-offer, drafts with a stale published_at, and withdrawn listings. settle on one definition, apply it in all three, and give me the list of listings whose visibility changes so the content team can be warned before partners notice the portal feed is the one partners see, so it's the definition that matters most externally.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "i'd like to understand what the second const-fold pass changes, since removing it alters output", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "the agent has three caches with three lifetimes, one unbounded, one re-read from procfs on every event, and one that isn't really a cache. consolidate them behind one layer with explicit bounds and eviction, and keep the enrichment output identical for a recorded hour of events from a busy host a recorded hour from the four-hundred-container host is in the fixtures bucket for comparison.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "agent degrades after the kernel upgrade", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "our health endpoint reports the agent healthy while it's in procfs fallback with three programs unloaded", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "listing thing", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "agent's enrichment cache and the process resolver both key on things that churn:\n\n// enrich/cache.go\ntype Cache struct { m map[connKey]*Meta } // keyed by (pid, fd), never evicted\n\n// proc/resolver.go\nfunc (r *Resolver) containerFor(pid uint32) string {\n b, _ := os.ReadFile(fmt.Sprintf(\"/proc/%d/cgroup\", pid)) // on every event\n return parseCgroup(b)\n}\n\n// k8s/enricher.go\nfunc (e *Enricher) podFor(containerID string) *Pod {\n return e.byContainer[containerID] // refreshed every 30s from the kubelet\n}\n\nthree caches with three lifetimes, one of which is unbounded and one of which isn't a cache at all", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "agent stuff again", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "the listing gallery should preload the next two images while the current one is showing", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "our language server and compiler share a crate that assumes one compilation per process", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "is our percolator matcher using the saved search as stored or as it was when created", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "what guarantees does the delta feed make if we miss a fifteen-minute window entirely", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "a walkthrough of how a viewing reaches the agent's calendar would help before i touch sync", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "agent's sampling is per process at a fixed rate, so a host with five hundred processes is effectively unsampled, and when the ringbuffer fills the kernel silently overwrites exactly the events we most want. work through what adaptive sampling with per-category floors would require, including the awkward fact that customers alert on raw event counts today one customer alerts on events per host per minute and would notice adaptive sampling immediately.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "listing page fails seven accessibility items including a carousel that only responds to swipe. fix them, and write the accessibility statement the portal partner asked for", "purpose": "frontendImpl", "secondary": "writing", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "saved searches need an edit screen that shows what the search currently matches before saving", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "les photos des annonces arrivent parfois pivotées de 90 degrés, mais seulement depuis l'app iOS :\n\nfichier reçu : IMG_4471.HEIC, 4032x3024\nEXIF Orientation: 6 (rotate 90 CW)\npipeline de traitement :\n 1. upload direct vers S3 (pas de transformation)\n 2. lambda de vignettes : sharp().resize(1200).jpeg().toBuffer()\n 3. écriture de la vignette, 1200x900\n 4. l'app web affiche la vignette\n\nles vignettes générées perdent l'orientation EXIF et sharp n'est pas configuré avec rotate(); le web affiche donc l'image couchée alors que l'original est correct", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "fr"} -{"prompt": "booking-viewing flow double-books slots occasionally and the audit trail looks like this:\n\n11:02:14.101 POST /viewings agent=a_881 listing=88412 slot=2026-08-03T14:00Z → 201 viewing v_4471\n11:02:14.118 POST /viewings agent=a_902 listing=88412 slot=2026-08-03T14:00Z → 201 viewing v_4472\n11:02:14.140 slot_availability recalculated for listing 88412: 14:00 marked unavailable\n11:02:14.155 notification sent to vendor: 2 viewings booked at 14:00\n\nthe controller checks availability with a SELECT and then inserts, no unique index on (listing_id, slot), and availability is a materialised view refreshed after the fact", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "availability logic behind viewing bookings, which i inherited:\n\ndef available_slots(listing, from_date, to_date)\n slots = listing.vendor.availability_windows.flat_map { |w| w.slots_between(from_date, to_date) }\n booked = Viewing.where(listing: listing, starts_at: from_date..to_date).pluck(:starts_at)\n blocked = listing.blackouts.where(date: from_date..to_date).flat_map(&:slots)\n (slots - booked - blocked).sort\nend\n\ncalled from the API on every listing page view, from the notification job, and from the agent app's calendar sync; vendors edit their availability windows from a separate screen with no locking", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "RFC for our incremental compilation fingerprints. does it actually close the hole we hit?\n\n## Fingerprints\nEach module's fingerprint is the hash of its source text. A module is recompiled when its fingerprint changes or when any of its dependencies were recompiled.\n\n## Rationale\nSource text is cheap to hash and captures every change a user can make.\n\n## Known gaps\n- Changes to compiler flags are not captured; users are told to run a clean build.\n- The dependency graph is recorded from the previous build.\n\n## Rejected\nHashing the resolved dependency set was rejected as \"expensive and rarely different\".", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "query the agent's control plane runs every 30 seconds for every tenant:\n\nSELECT h.id, h.hostname, h.last_seen_at, h.agent_version,\n count(distinct c.id) FILTER (WHERE c.state = 'running') AS containers,\n (SELECT count(*) FROM events e WHERE e.host_id = h.id AND e.ts > now() - interval '5 minutes') AS recent_events,\n (SELECT max(ts) FROM events e2 WHERE e2.host_id = h.id) AS last_event\nFROM hosts h\nLEFT JOIN containers c ON c.host_id = h.id\nWHERE h.tenant_id = $1 AND h.deleted_at IS NULL\nGROUP BY h.id;\n\n40,000 hosts across tenants, events is 2.1 billion rows partitioned by day, and this runs per tenant per 30 seconds", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "support notes about listings stuck in processing, which need to become a real page:\n\n- a listing goes to \"processing\" when photos are uploaded and leaves it when all workers report success\n- if any worker fails, the listing stays in processing forever and the agent sees no error\n- the most common failure is a HEIC the thumbnail worker can't decode, about 40 a week\n- support fixes it by re-uploading the photo, which starts the pipeline again\n- there's a script that force-advances a listing, which two people know about\n- agents phone in because the listing isn't live and they have a viewing booked\n\nwrite the support-facing troubleshooting page, and separately note which of these are product bugs rather than documentation gaps", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "die Notizen aus der Störung von gestern, daraus soll die Kundenmitteilung werden:\n\n14:02 Kunden melden, dass in einer Region keine Suchergebnisse erscheinen\n14:18 bestätigt: alle Abfragen mit Kartenausschnitt schlagen fehl, Textsuche funktioniert\n14:35 Ursache gefunden: der neue Index vom 1. Juli hat kein geo_point-Mapping\n14:50 Index-Template war im Juni versehentlich gelöscht worden\n15:20 Reindexierung gestartet, 4,1 Millionen Anzeigen\n17:40 Reindexierung abgeschlossen, Suche wieder normal\n\nBetroffen war eine Region, dreieinhalb Stunden lang; keine Daten verloren, aber Makler konnten ihre eigenen Anzeigen nicht finden und haben teilweise doppelt eingestellt", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "de"} -{"prompt": "vendor's questions before they sign, which we should answer as documentation rather than an email:\n\n\"What data does the agent collect from our hosts, exactly? Does it read file contents or only metadata? Are command-line arguments captured, and if so can we redact them? What happens to the agent if your ingest endpoint is unreachable for a day — does it buffer, drop, or fill our disk? Can we run it in a mode that collects nothing until we've reviewed the schema? What is the blast radius if one of your eBPF programs has a bug on a production kernel?\"\n\nanswer each from the code and write it as a page we can publish", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "marketplace's public API, which three portal partners integrate against off a README from 2024:\n\nGET /api/v3/listings\n filters: bbox, min_price, max_price, min_beds, property_type[], status\n sort: price_asc | price_desc | listed_desc | relevance (default relevance, which needs `q`)\n pagination: cursor-based, `after` opaque, page size 50 fixed\n a listing under offer is returned with status=under_offer unless `status` excludes it\n withdrawn listings disappear entirely, which partners handle badly — they keep showing them\n the price on a listing can change without the listing changing its updated_at, because price lives in a separate table\n\nwrite the reference, and be explicit about the updated_at problem because it's why partners' caches go stale", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "runbook for a stuck ingest pipeline is a slack thread. what we actually do:\n\n- symptom is agents reporting fine but events not appearing for a tenant\n- first check is the per-tenant kafka lag dashboard; over 5 minutes of lag means the consumer is behind\n- if lag is flat and high, the enrichment stage is stuck on a slow k8s API; restarting the enricher clears it\n- if lag is climbing steadily, it's usually one tenant sending 100x their normal volume\n- `lumenctl tenant throttle --rate 5000` slows them without dropping, and we tell the account manager afterwards\n- never restart the ingest tier during business hours; it drops the ringbuffer contents on every agent connected to it\n\nwrite the runbook page, in the order someone paged at 3am would need it", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "我们的编译器诊断文档只有一页示例，第三方插件作者一直在猜。当前实际行为：\n\n- 诊断分为 error / warning / note 三级，note 不能单独出现，必须挂在前两者下面\n- 错误码格式是 `E0412`，但只有大约三分之一的诊断有码，其余没有，也没有规则说明什么时候该有\n- span 支持多段，但渲染时只显示第一段所在的文件，跨文件的诊断会丢失上下文\n- 建议（suggestion）分为 machine-applicable 和 maybe-incorrect，前者会被 `--fix` 自动应用\n- 插件返回的诊断不做校验，span 越界会导致编译器崩溃而不是报错\n- 同一位置的多条诊断按插件注册顺序输出，没有去重\n\n示例代码：\n\nDiagnostic::error(\"type mismatch\")\n .with_span(span, \"expected `Int`, found `String`\")\n .with_note(\"the function signature is defined here\")\n .emit();\n\n请写成给插件作者的诊断 API 文档，把错误码规则和 span 越界这两点写清楚", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "zh"} -{"prompt": "rubocop and the type checker on the rails app, gate goes on friday:\n\napp/queries/listing_search.rb:88:5: C: Metrics/MethodLength: Method has too many lines. [31/15]\napp/queries/listing_search.rb:41:9: W: Lint/UselessAssignment: Useless assignment to variable - `sort`\napp/models/listing.rb:212:11: C: Style/SafeNavigation: Use safe navigation (&.) instead of checking if an object exists\napp/services/viewings/book.rb:22:3: C: Style/Documentation: Missing top-level class documentation comment\n\nsorbet:\napp/services/viewings/book.rb:66: Expected `Time` but found `T.nilable(Time)` for argument `starts_at`\napp/models/listing.rb:141: Method `price_cents` does not exist on `T.nilable(Price)`\n\n4 offenses, 2 type errors, and the two type errors look like actual nil bugs", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "clippy on the compiler, mostly noise but check the last two:\n\nwarning: this `RefCell` is borrowed twice in the same expression\n --> src/intern.rs:41:9\nwarning: large enum variant\n --> src/ast.rs:88:1\n | enum Expr { Lit(i64), Call(Box), Block([Stmt; 64]) }\nwarning: this loop could be written as a `for` loop\n --> src/lex.rs:141:5\nwarning: casting `usize` to `u32` may truncate the value\n --> src/intern.rs:52:20\nwarning: `mem::forget` on a type with a `Drop` implementation\n --> src/intern.rs:49:5\n\n34 warnings total", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "index template that got deleted, restored from a backup. does this match what the search code expects?\n\nPUT _index_template/listings\n{\n \"index_patterns\": [\"listings-*\"],\n \"template\": {\n \"mappings\": {\n \"properties\": {\n \"location\": { \"type\": \"geo_point\" },\n \"price_cents\": { \"type\": \"long\" },\n \"beds\": { \"type\": \"short\" },\n \"property_type\": { \"type\": \"keyword\" },\n \"description\": { \"type\": \"text\", \"analyzer\": \"english\" },\n \"listed_at\": { \"type\": \"date\" }\n }\n },\n \"settings\": { \"number_of_shards\": 3, \"number_of_replicas\": 1 }\n }\n}\n\nthe search code also filters on `status` and sorts on `updated_at`, neither of which appears here", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"} -{"prompt": "npm audit on the mobile app before the store submission:\n\nreact-native 0.76.0 - 0.76.9\nHigh: Improper URI validation in the Linking module\nfix available via `npm audit fix --force`\nWill install react-native@0.79.2, which is a breaking change\n\n@react-native-async-storage/async-storage 1.21.0 - 1.23.1\nModerate: Data written without atomic replace, corruption possible on crash\nfix available via `npm audit fix`\n\nreact-native-image-picker 7.1.0 - 7.2.2\nModerate: Activity result handling can leak the file URI to other apps\nfix available via `npm audit fix`\n\nthe async-storage one is interesting given our saved-listings bug", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "os limites de alerta do ingest, acordam-nos por nada:\n\n- alert: IngestLag\n expr: kafka_consumergroup_lag{group=\"ingest\"} > 1000\n for: 1m\n labels: { severity: page }\n\n- alert: AgentDown\n expr: up{job=\"agent\"} == 0\n for: 0m\n labels: { severity: page }\n\n- alert: EnrichErrors\n expr: rate(enrich_errors_total[5m]) > 0\n for: 1m\n labels: { severity: page }\n\ncomportamento normal: o lag passa de 1000 em todas as manhãs às 9h durante cerca de dez minutos; há sempre alguns agentes offline num universo de 40 mil hosts; e o incidente real do mês passado (uma região inteira sem eventos durante duas horas) não gerou nenhum alerta", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "pt"} -{"prompt": "diagnostic emission code is duplicated across passes with slight differences:\n\n// in type check\nsess.emit_error(format!(\"type mismatch: expected {}, found {}\", a, b), span);\n\n// in the borrow checker\nsess.diagnostic(Level::Error, \"cannot borrow as mutable\")\n .span_label(span, \"second mutable borrow\")\n .emit();\n\n// in the const folder\neprintln!(\"error: {}\", msg); // yes, really\nsess.error_count.fetch_add(1, Ordering::Relaxed);\n\n// in the plugin bridge\nDiagnostic::error(msg).with_span(span, label).emit();\n\nfour ways to report an error, one of which bypasses the diagnostic system entirely and breaks --json output", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "viewing-booking service does everything in one method and the tests need a database and a stubbed calendar:\n\nclass Viewings::Book\n def call\n raise SlotUnavailable unless available?\n viewing = Viewing.create!(listing:, agent:, starts_at:, source:)\n CalendarSync.push(agent, viewing)\n VendorMailer.viewing_booked(viewing).deliver_later\n BuyerMailer.viewing_confirmed(viewing).deliver_later\n Sms.send(buyer.phone, confirmation_text(viewing)) if buyer.phone?\n listing.touch(:last_activity_at)\n Analytics.track(\"viewing_booked\", agent_id: agent.id, listing_id: listing.id)\n AvailabilityCache.invalidate(listing)\n viewing\n end\nend\n\nsame behaviour, but the availability check and the booking need to be atomic and the rest needs to be out of the request", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "quarter planning, and this is what i have to sequence:\n\n- the double-booking bug is small in volume but every instance is a furious vendor and an angry agent\n- portal partners are complaining that our feed shows withdrawn listings for hours\n- the agent's memory growth means one large customer caps us at 200 hosts per cluster\n- the compiler's incremental correctness bug has produced two miscompiles in production code this quarter\n- a new customer needs the agent on 5.4 kernels, which we dropped support for in 2.4\n- two engineers are leaving the compiler team and one is joining in october\n- there's a store submission deadline for the mobile app in three weeks", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "architecture ticket, thinking needed before code:\n\nOBS-410 — Agent event sampling and backpressure\nThe agent currently samples per process at a fixed rate and drops nothing until the ringbuffer fills, at which point the kernel side silently overwrites. On busy hosts this means we lose the events we most want. The proposal is adaptive sampling driven by observed volume with per-category floors, plus explicit backpressure signalling to the control plane. Concerns: sampling decisions in eBPF cost cycles per event; the control plane cannot push config faster than every 30 seconds; customers alert on event counts and adaptive sampling would make those alerts meaningless; and we have no way to tell a customer what we dropped.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "customer's security requirement for the agent, which sales has already half-agreed to:\n\n\"The agent shall not transmit file contents, command-line arguments or environment variables outside the host without explicit per-category opt-in. It shall operate in an audit-only mode in which it collects and displays locally but transmits nothing. The customer shall be able to review the exact schema of transmitted data. A failure of the agent shall not affect the host: no kernel panic, no CPU starvation, no disk exhaustion. Evidence of the last requirement shall include the results of fault injection testing.\"\n\nwe transmit command lines by default, have no local-only mode, no published schema, and have never done fault injection. i want the plan and an honest view of what we can claim by the deadline", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "spec for the agent fleet screen in our console, which platform engineers live in:\n\nFleet view\n- Table of hosts: hostname, agent version, kernel, last seen, events/sec, degraded reason. Virtualised to 40,000 rows.\n- Degraded hosts sort first by default; \"degraded\" needs a plain-language reason, not an error code.\n- Filters: version, kernel, tenant, degraded state; filters are in the URL so they can be shared in an incident.\n- Bulk actions: restart agent, change sample rate, collect diagnostics. Each shows how many hosts it will affect before confirming.\n- A version rollout view: percentage on each version over time, with the ability to pause a rollout.\n- Host detail: loaded programs with their status, map utilisation, recent config changes, and the last ten errors.\n- Everything must remain usable when the control plane is degraded — show stale data with its age rather than a spinner.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "accessibility findings on the listing detail page, from an audit a portal partner ran:\n\n1. The photo carousel is operable only by swipe; there are no next/previous controls and arrow keys do nothing.\n2. Photo alt text is the filename (\"IMG_4471.HEIC\") for every image.\n3. The floorplan opens in a lightbox that traps focus and has no close button reachable by keyboard.\n4. Price change history is conveyed by red and green arrows with no text.\n5. The \"book a viewing\" form's date picker is a custom control with no role and no keyboard support.\n6. Headings jump from h1 to h4 in the description section.\n7. The map embed has no accessible name and is included in the tab order with nothing to do.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "design tokens versus what the listing pages actually use:\n\ntokens:\n color.text.primary #101418 / #F2F5F7\n color.text.muted #5B6570 / #9AA6B2\n color.brand #0B6E4F\n color.price.up #B42318\n color.price.down #067647\n space 4/8/12/16/24/32/48, radius 6/10/16, shadow.sm/md/lg\n type: display 28/34, title 20/26, body 15/22, caption 13/18\n\nthe listing pages: nine hardcoded colours, three of which are the brand green at slightly different values; paddings of 5, 11, 13 and 22; two type sizes not in the scale; price direction shown only by colour; and a shadow defined inline in four components\n\nbring it onto the tokens and give price direction a non-colour indicator while you're in there", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "schema we agreed for agent config versioning, needs implementing in the control plane:\n\nCREATE TABLE agent_configs (\n id uuid PRIMARY KEY,\n tenant_id uuid NOT NULL,\n scope text NOT NULL CHECK (scope IN ('tenant','group','host')),\n scope_id text,\n body jsonb NOT NULL,\n version int NOT NULL,\n created_by text NOT NULL,\n created_at timestamptz NOT NULL DEFAULT now(),\n UNIQUE (tenant_id, scope, scope_id, version)\n);\n\nagents poll every 30 seconds with their current version; the effective config is host over group over tenant; a rollout can be paused, which means agents keep their current version rather than reverting; and an agent that receives a config it can't apply must report why and keep running on the previous one", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "sample_rate should be per host", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "async-storage bump before submission", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "cache cargo registry in CI", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "thumbnails need rotate() for EXIF", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "el filtro de precio no acepta decimales", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "es"} -{"prompt": "cap the search page size at 100", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "add `status` to the index template", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "process_tree off by default", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "IngestLag needs a 15 minute window", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "Release-Tests im CI weglassen", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "de"} -{"prompt": "unique index on (listing_id, slot)", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "the compiler's error output needs colour that survives being piped into a file", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "agent config is parsed in three places with different defaults for the same keys", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "our internal wiki page on the photo pipeline describes two lambdas and there are three, one of which advances the listing state and is therefore the one everyone needs to understand during an incident. write the page properly, covering each stage, what failure looks like, and which state transitions are irreversible tell me if any of that is a bad idea before doing it.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "pins should show price in thousands", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "\"search this area\" button on the map", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "degraded hosts should sort first", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "filters belong in the URL", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "photo alt text is the filename", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "間取り図のライトボックスが閉じられません", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "ja"} -{"prompt": "carousel has no keyboard controls", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "bottom sheet snaps to the wrong detent", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "stale fleet data looks live", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "pull the emails out of Viewings::Book", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "un seul modèle de récupération de données", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "fr"} -{"prompt": "`price_cents` naming, everywhere", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "extract the bbox parsing helper", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "inline `slots_between`, one caller", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "one diagnostic emission path", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "doc comments on the plugin diagnostic API", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "changelog for agent 2.5", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "nota para os parceiros sobre o feed", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "pt"} -{"prompt": "document what sample_rate really means", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "summarise the sampling proposal", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "PR body for the fingerprint fix", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "¿por qué el feed muestra anuncios retirados?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "es"} -{"prompt": "can two agents book the same slot?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "walk me through the photo pipeline", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "geo search fails in one region", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "favourites disappear after relaunch", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "warum belegt der Agent 2 GB RAM?", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "de"} -{"prompt": "endpoint for a host's loaded programs", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "press on", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "leaner", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "you know the priorities", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "lo del compilador, sigue", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "es"} -{"prompt": "clean as you go", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "same again", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "partner doc", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "anything small", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "cast an eye over it", "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": "more of that", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "mobile app's offline story is three different patterns and a hope, and the saved-listings bug is just the visible part. i want a position on what offline should mean for this app — which surfaces work, what happens to writes, how conflicts resolve — before anyone touches the storage layer again the store submission is in three weeks, so anything shipped now has to be small.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "compiler's diagnostics are inconsistent in seven visible ways and plugin authors are copying whichever example they found first. write the error message style guide — wording, capitalisation, when a code is required, how spans and notes are used, when to suggest a fix — with our current worst examples rewritten as illustrations the guide should be enforceable by a lint, so wording rules need to be mechanical where possible.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "customers deploy the agent across whole fleets from a sample config file with no documentation, which is how one of them ran unsampled for a month. write the configuration reference covering what each option really does, the ones that interact badly, and the three that mean something different from what their names suggest assume the reader is a platform engineer rolling this to forty thousand hosts.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "public listings API is documented by a README from 2024 and the thing partners get wrong every time is that a price change doesn't move updated_at. write the reference properly, with the caching implications spelled out, and a worked example of a partner keeping a mirror in sync three partners integrate against it today and a fourth starts next month.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "string interner leaks every string deliberately and transmutes a borrow to 'static, which is fine for a one-shot compiler and possibly catastrophic in a long-lived language server. work through whether the sessions really are isolated, what happens when one is dropped, and whether the language server can end up with a dangling symbol the language server runs for days in an editor, which is where this would show up.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "eBPF program updates a hash map on every connection and relies on a userspace sweep every thirty seconds to remove entries, which on a busy host cannot possibly keep up. read the program and the sweep together and tell me what happens once the map is full — silently dropped updates, or something worse on our busiest customer host that's about twelve thousand events a second.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "en"} -{"prompt": "pass manager is a wall of conditionals including a second const-fold pass nobody can explain, and removing it changes generated code. restructure it into an explicit ordered pipeline with each pass declaring its own preconditions, and keep the emitted binary identical for our benchmark suite before we discuss removing anything our benchmark suite is the only thing standing between us and silently changing generated code.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "two agents booked the same viewing slot seventeen milliseconds apart and our availability check is a select followed by an insert with no constraint behind it. work out how often this has happened historically before we add the index, because the vendor-facing consequences of the ones we've already sent are the actual problem vendors get an email per booking, so the ones already sent are what we actually have to handle.", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "map screen is our most-used surface and it currently refetches on every pan, drops frames with three hundred pins, and has no offline behaviour at all. build it to the new spec, keeping the sheet's three detents and making sure the accessible path through the list actually works the target device is a mid-range android from 2021, which is what most of our users have.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "before we change sampling i want the design written down — adaptive rates, per-category floors, what we tell customers about what we dropped — and then the drop accounting implemented, because we currently can't answer that question at all that's the whole of it, but shout if the context is thin.", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.9, "slice": "mixed", "lang": "en"} -{"prompt": "incremental correctness bug needs a proper fix and a regression test that would have caught it. design the fingerprint change with me first, including the cache invalidation on upgrade, then implement it we've been burned by guessing at this before, so evidence over instinct please.", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.9, "slice": "mixed", "lang": "en"} -{"prompt": "portal feed should probably be event-driven rather than diffing on updated_at, but that's a bigger change than this quarter allows. give me the target design, then implement the price-change events so partners at least stop showing stale prices i'd rather have the reasoning than a quick answer here. there's no rush on this week specifically, but it keeps costing us time.", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "unsere Offline-Strategie in der App ist dreimal unterschiedlich gebaut und verliert dabei Favoriten. Ich hätte gern zuerst ein Konzept, was offline überhaupt funktionieren soll, und danach die Umsetzung für die gespeicherten Anzeigen", "purpose": "planning", "secondary": "frontendImpl", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "de"} -{"prompt": "supporting 5.4 kernels again needs a decision and, if we say yes, a compatibility path that doesn't fork the codebase. work through the options, then prototype whichever one you'd recommend against a 5.4 test host happy to be told this is the wrong shape entirely. nobody has trusted this code for about a year, which is part of the problem.", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "agent's configuration reference needs writing and i suspect at least two options don't do what their names say. produce the reference, and give me the list of options whose behaviour we should change rather than document i've already spent an afternoon on it and got nowhere useful.", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "listings API reference has to exist before the fourth partner integrates, and while writing it please confirm whether withdrawn listings really do vanish from the feed rather than appearing as deleted", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "escribe la guía de despliegue del agente para clientes que lo instalan en toda su flota, y comprueba en el código si el límite de CPU se aplica de verdad o solo es orientativo", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "es"} -{"prompt": "ingest runbook should be a page rather than a slack thread, and the ingest tier restart that drops every connected agent's ringbuffer deserves a guard. write the runbook, then add the confirmation if the answer is that it's fine as it is, that's a useful answer too.", "purpose": "writing", "secondary": "quickFix", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "compiler reports errors four different ways, one of which bypasses the diagnostic system and breaks JSON output entirely. unify them, and tell me which existing tools would break if the JSON output suddenly contained diagnostics it never saw before it doesn't have to be elegant, it has to be defensible in a review.", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "react native screens fetch data three different ways with three error behaviours. bring them onto one pattern, and write the short note for the team explaining which one and why, because this is the third time we've had this conversation it's been like this long enough that nobody trusts it any more. the last person who touched this left, so there's nobody to ask.", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "photos come out rotated from iOS uploads and i think the thumbnail worker drops EXIF orientation. confirm it, then fix the pipeline and tell me how many existing thumbnails need regenerating", "purpose": "debugging", "secondary": "quickFix", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "fleet view needs a rollout pause control, and we should agree what pausing means for agents mid-download before it exists. decide that with me, then build it", "purpose": "frontendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "CI duplicates the debug test run in release mode and rebuilds the compiler for the UI tests. cut it down, and tell me what coverage we lose by doing so", "purpose": "quickFix", "secondary": "review", "mixed": true, "difficulty": 0.5, "slice": "mixed", "lang": "en"} -{"prompt": "config versioning for agents needs the effective-config resolution agreed before it's built — host over group over tenant, and what a paused rollout means. settle that, then implement", "purpose": "backendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "percolator index is rebuilt nightly from saved searches, so an edit doesn't take effect until the next day", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "rails app has three ways to express money and the mobile API returns two of them in the same payload", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "lexer and the language server's lexer are separate implementations that have drifted on string escapes", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "rename `Listing#status` to something that admits it's a state machine with six values and two of them unused", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "could you explain how a listing gets into \"processing\" and what takes it out again", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "why does the fleet query run per tenant every thirty seconds rather than once for everyone", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "someone should check whether our search endpoint can be made to scan every shard by a crafted filter", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "is it expected that the thumbnail worker strips all metadata including copyright", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "pouvez-vous m'expliquer comment le cache de disponibilité est invalidé après une réservation ?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "fr"} -{"prompt": "docs/search.md describes the geo filter as optional, which stopped being true two versions ago", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "a short note on why we're moving to an LRU map in the agent, for the decision log", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "rustdoc on our plugin API promises span validation that doesn't exist", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "write the customer note about dropping 5.4 kernel support, for the two customers still on it", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "listing URL includes the address, so a withdrawn listing is still findable by search engines", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "staging hosts run five containers and prod runs four hundred, with identical map sizes", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "floorplan detector fires on any listing whose address contains the word plan", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "how should we version the agent's wire protocol now that fleets run three versions at once", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "what's the right way to test a compiler optimisation pass when the failure mode is a wrong program", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "i want a position on whether saved searches should be percolated or evaluated on write", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "three partners want real-time listing updates rather than a fifteen-minute feed, what's our story", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "we need a plan for running the agent on hosts where we can't load eBPF at all", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "what should happen to a tenant's events when they exceed their contracted volume mid-month", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "an endpoint returning a listing's price history with the source of each change, for the detail page", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "delta feed needs a sequence number that survives a redeploy and a gap-recovery path", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "agents should buffer to disk with a size cap when ingest is unreachable, rather than dropping silently", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "viewing availability should be computed from a single source rather than three set operations at request time", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "host detail screen needs a map utilisation chart so we can see which map fills first", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "whatever gets us through the submission", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "next bit of the feed work", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "i'd like an honest read of whether our language server can end up holding a symbol from a dropped compilation session, given the interner leaks and transmutes, and if it can, the fix — ideally one that doesn't require rewriting every pass that holds a Symbol the sooner we know the size of it, the better.", "purpose": "review", "secondary": "refactor", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "the lexer exists twice, once in the compiler and once in the language server, and they have drifted on string escapes badly enough that the editor highlights code the compiler rejects. merge them onto one implementation, and tell me which existing editor behaviours change as a result i've spent an afternoon on it already and got nowhere useful.", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "agent configuration is parsed in three places with different defaults for the same keys, which is why a documented default is sometimes not the effective one. consolidate the parsing, then write down the resulting defaults so the reference we publish is generated rather than hand-maintained this has come up in three separate reviews now. the sooner we know roughly how big this is, the better for planning.", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "saved searches are percolated against an index rebuilt nightly, so an edit doesn't take effect for a day and users assume it's broken. decide with me whether to percolate live or evaluate on write, then implement whichever we land on for new saved searches first it doesn't have to be perfect, it has to be defensible.", "purpose": "backendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "our listing URLs embed the address, so a withdrawn property remains findable through search engines and vendors have complained about it twice this month. change the URL scheme for new listings, keep the old ones resolving with a redirect, and make sure withdrawn listings return the right status code rather than a soft 404 page that's the whole of it, but shout if the context is thin.", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} +{"prompt":"Gateway: Ticket OPS-50147: retire the legacy replay path for JunctionAmberFilterFlow\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 JunctionAmberFilterFlow 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":"Test Suite 'JunctionEchoRegistryFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[JunctionEchoRegistryFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/junction/config/staging.toml:144: error: -[JunctionEchoRegistryFlowTests 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 '-[JunctionEchoRegistryFlowTests 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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Bring JunctionEchoRegistryFlow'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":"debugging","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Renderer: # projects/junction/ml/pipeline/features.py\n[worker.junctionsummitproxyflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctionsummitproxyflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctionsummitproxyflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionSummitProxyFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50143\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/junction/ml/pipeline/features.py. 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":"Make JunctionOpalRouterStore keyboard navigable","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'JunctionCopperBridgeFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[JunctionCopperBridgeFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/junction/cmd/exporter/main.py:144: error: -[JunctionCopperBridgeFlowTests 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 '-[JunctionCopperBridgeFlowTests 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\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Bring JunctionCopperBridgeFlow'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":"JunctionDriftConsoleCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"# CI job 50144: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: Cloudflare Workers\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] JunctionMosaicGridFlowIntegration.replays_after_timeout ... ok\n[test] JunctionMosaicGridFlowIntegration.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 \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 JunctionMosaicGridFlow server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Collapse the JunctionFlintTimelineService wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"JunctionMosaicGridCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"diff --git a/projects/junction/web/components/FilterDrawer.vue b/projects/junction/web/components/FilterDrawer.vue\nindex 62d71aa..90f3c1e 100644\n--- a/projects/junction/web/components/FilterDrawer.vue\n+++ b/projects/junction/web/components/FilterDrawer.vue\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Consolidate JunctionPrismCacheFlow'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":"Summarize the JunctionTideWorkerService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Support wants the behavior in projects/junction/services/ledger/replay.go recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"JunctionOrbitSyncCoordinator: sort out the rough edge","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Outline a safer JunctionOpalRouterService cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-50120\n\n08:02 deploy JunctionOspreyJobFlow 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 JunctionOspreyJobFlow 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":"projects/junction/workers/thumbnail/consumer.ex 里的 JunctionEmberRelayService 最近在 Spring Boot 流程中出现间歇性问题。 请追踪 queue、scheduler 和取消路径，对比假设，先定位原因再提修改。\n\n约束：\n- 继续使用 Spring Boot\n- 保持兼容性和取消语义\n- 改动只限于 JunctionEmberRelayService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"Our support and SDK teams keep answering the same questions about JunctionHarborIndexService, but the current prose in projects/junction/crates/index/src/segment.rs only describes the happy path. 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- retain the existing CLI flags and exit codes\n- stay compatible with the existing Kafka deployment\n- keep the work scoped to JunctionHarborIndexService and its direct tests\n\nThis repository spans logistics, WebAssembly, MySQL; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Em projects/junction/ui/settings/PrivacyPane.tsx, o JunctionEmberRelayStore tem um problema intermitente no fluxo de Spring Boot. Finalize o layout responsivo, estados vazio e retry, foco por teclado, dark mode e reduced motion.\n\nRestrições:\n- continuar com Spring Boot\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao JunctionEmberRelayStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"pt"} +{"prompt":"Indexer: # projects/junction/workers/thumbnail/consumer.ex\n[worker.junctionslateeditorcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctionslateeditorcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctionslateeditorcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionSlateEditorCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50155\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/junction/workers/thumbnail/consumer.ex. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"pasted-context","lang":"en"} +{"prompt":"diff --git a/projects/junction/Sources/CLI/Commands/Doctor.swift b/projects/junction/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/junction/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/junction/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is JunctionDriftConsoleFlow'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":"Apparently: A copied hex color in JunctionAtlasSearchStore lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"The JunctionMosaicGridService 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":"Lately: projects/junction/cmd/exporter/main.py 里的 JunctionSummitProxyStore 最近在 Kotlin coroutines 流程中出现间歇性问题。 请完成 responsive layout、空状态、retry、键盘焦点、dark mode 和 reduced motion。\n\n约束：\n- 继续使用 Kotlin coroutines\n- 保持兼容性和取消语义\n- 改动只限于 JunctionSummitProxyStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"zh"} +{"prompt":"JunctionTideWorkerCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Ticket OPS-50125: retire the legacy replay path for JunctionMoonlitSDKFlow\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 JunctionMoonlitSDKFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"JunctionJuniperCLIFlow's staging timeout is already known to be wrong: change the single projects/junction/Sources/App/SessionStore.swift value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Centre la modale JunctionNovaPickerService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"fr"} +{"prompt":"Oddly: Test Suite 'JunctionVelaDrawerFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[JunctionVelaDrawerFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/junction/web/components/FilterDrawer.vue:144: error: -[JunctionVelaDrawerFlowTests 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 '-[JunctionVelaDrawerFlowTests 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\nFinish the visible JunctionVelaDrawerFlow 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":"Fresh release brief for JunctionRainfallDBCoordinator:\n- primary outcome: change JunctionRainfallDBCoordinator'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/junction/web/components/FilterDrawer.vue\n- platform constraint: GraphQL\n- known complication: memory growth during hour-long imports\n\nBoth results are required, but they should remain independently reviewable. Retain the existing cli flags and exit codes; 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.6,"slice":"mixed","lang":"en"} +{"prompt":"Sequence JunctionGarnetModalService's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"JunctionVelaDrawerCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Currently: The JunctionEchoRegistryService surface in projects/junction/config/staging.toml 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":"Production says JunctionCopperBridgeService is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Reconstruct the failing timeline from logs and tests, identify which invariant first breaks, and distinguish causal signals from effects or cleanup noise.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current Kotlin coroutines operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Please turn JunctionAmberFilterService'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":"JunctionAmberFilterCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"JunctionKiteSchedulerCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"JunctionFrostPanelStore's staging timeout is already known to be wrong: change the single projects/junction/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":"Check JunctionMoonlitSDKService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-50154\n\n08:02 deploy JunctionFrostPanelCoordinator 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 JunctionFrostPanelCoordinator 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":"Ist JunctionNovaPickerStore sicher?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"de"} +{"prompt":"Today: The behavior of JunctionWrenExportService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/junction/web/components/FilterDrawer.vue. 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- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current GraphQL operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"$ pnpm test --filter JunctionGarnetModalFlow\n RUN v3.2.4 /workspace/apps/console\n × JunctionGarnetModalFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=50124 phase=resume storedCursor=seg-0183\n session=50124 phase=fetch requestCursor=seg-0183 pageSize=200\n session=50124 phase=commit receivedCursor=seg-0184 itemCount=0\n session=50124 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nReconstruct the JunctionGarnetModalFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"# projects/junction/Sources/CLI/Commands/Doctor.swift\n[worker.junctionjuniperclicoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctionjuniperclicoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctionjuniperclicoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionJuniperCLICoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50158\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/junction/Sources/CLI/Commands/Doctor.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":"Ticket OPS-50129: retire the legacy replay path for JunctionMicaProfileFlow\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À partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Turn the material above into a concise JunctionMicaProfileFlow 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":"Read projects/junction/db/migrations/20260730_events.sql and tell me whether JunctionBasilRunnerStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"JunctionOpalRouterCoordinator: ship, then document","purpose":"backendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"UI ticket DES-50146: finish the compact JunctionIrisBatchFlow filter experience\n\nRoute: /catalog/search\nSource: projects/junction/internal/auth/refresh.go\nFramework: GraphQL\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring JunctionIrisBatchFlow'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":"Context: diff --git a/projects/junction/services/ledger/replay.go b/projects/junction/services/ledger/replay.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/junction/services/ledger/replay.go\n+++ b/projects/junction/services/ledger/replay.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit JunctionLumenChartFlow 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":"JunctionMarbleTokenCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Describe JunctionOspreyJobStore's error envelope","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"The behavior of JunctionTideWorkerStore is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/junction/packages/api/openapi.yaml. 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- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current Kafka operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Stream JunctionSableParserService's audit events","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"JunctionEmberRelayCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Is there a cleaner way to separate JunctionBeaconStoreService'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":"JunctionBirchMigratorCoordinator needs a paired pass: assess ownership and failure handling in projects/junction/pkg/cache/lease.rs, plus capture the contract and rollback note for consumers. Use projects/junction/pkg/cache/lease.rs as the source of truth, preserve the Kafka contract, and avoid unrelated cleanup.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Dedupe JunctionFlintTimelineStore's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"JunctionRavenSessionService é seguro?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"pt"} +{"prompt":"JunctionEchoRegistryCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Test Suite 'JunctionMapleQueueFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[JunctionMapleQueueFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/junction/app/src/main/SyncWorker.kt:144: error: -[JunctionMapleQueueFlowTests 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 '-[JunctionMapleQueueFlowTests 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 JunctionMapleQueueFlow'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":"$ pnpm test --filter JunctionTideWorkerFlow\n RUN v3.2.4 /workspace/apps/console\n × JunctionTideWorkerFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=50117 phase=resume storedCursor=seg-0183\n session=50117 phase=fetch requestCursor=seg-0183 pageSize=200\n session=50117 phase=commit receivedCursor=seg-0184 itemCount=0\n session=50117 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nDetermine why JunctionTideWorkerFlow 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":"Background: Incident timeline — INC-50114\n\n08:02 deploy JunctionAsterWebhookFlow 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 JunctionAsterWebhookFlow 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":"Question: Ticket OPS-50159: retire the legacy replay path for JunctionPineMetricsCoordinator\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 JunctionPineMetricsCoordinator 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":"Observation: projects/junction/ml/pipeline/features.py の JunctionSummitProxyService で、Kotlin coroutines の flow に断続的な問題が起きています。 consumer 向けに contract、error、retry、コピー可能な例を含む文書を書き、handler は変更しないでください。\n\n制約:\n- Kotlin coroutines を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は JunctionSummitProxyService のみ","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"ja"} +{"prompt":"Move JunctionEchoRegistryStore'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.5,"slice":"core","lang":"en"} +{"prompt":"Two asks around JunctionMoonlitSDKCoordinator: (1) finish JunctionMoonlitSDKCoordinator's responsive empty and retry states; (2) correct the known stale timeout beside it. Retain the existing cli flags and exit codes, and leave a clear boundary between the resulting artifacts or edits.","purpose":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Fresh release brief for JunctionAsterWebhookCoordinator:\n- primary outcome: separate JunctionAsterWebhookCoordinator's policy from transport without behavior changes\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/junction/db/migrations/20260730_events.sql\n- platform constraint: Cloudflare Workers\n- known complication: cancellation being swallowed at the repository boundary\n\nBoth results are required, but they should remain independently reviewable. Retain the existing cli flags and exit codes; 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":"refactor","secondary":"writing","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Check JunctionLumenChartStore's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Unifie les validateurs de JunctionRavenSessionStore","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"fr"} +{"prompt":"Ownership of JunctionFrostPanelService is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current Cloudflare Workers operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"What does JunctionBirchMigratorStore own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Milestones for replacing JunctionMicaProfileService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Two deliverables are holding up JunctionCedarPolicyCoordinator. First, separate JunctionCedarPolicyCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/junction/engine/render/atlas.cpp, which follows Spring Boot conventions and currently suffers from two validators with subtly different error strings. Retain the existing cli flags and exit codes.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"JunctionSummitProxyCoordinator: ship a sensible version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"JunctionFernSnapshotFlow 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":"Release verification found a single stale JunctionCedarPolicyService value; the cause, desired value, and affected assertion are already agreed. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current Spring Boot operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"The JunctionQuartzPlayerFlow surface in projects/junction/ml/pipeline/features.py is stable now; turn its edge cases into API documentation with one successful example and one cancellation example.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Constraint: Two deliverables are holding up JunctionCopperBridgeCoordinator. First, separate JunctionCopperBridgeCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/junction/ml/pipeline/features.py, which follows Kotlin coroutines conventions and currently suffers from stale cursors when a page is resumed. Retain the existing cli flags and exit codes.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"JunctionDeltaCanvasStore crashes after reconnect","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"JunctionDeltaCanvasCoordinator: sequence, then ship","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Decouple JunctionMoonlitSDKStore's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating a deadlock that appears only during shutdown in JunctionDriftConsoleService, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-50151: retire the legacy replay path for JunctionWrenExportCoordinator\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for JunctionWrenExportCoordinator, 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":"Request: Two asks around JunctionLumenChartCoordinator: (1) change JunctionLumenChartCoordinator's known staging timeout from 15 to 30 seconds; (2) give the existing implementation a read-only safety pass. Retain the existing cli flags and exit codes, and leave a clear boundary between the resulting artifacts or edits.","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"PM needs a concise migration note for JunctionIrisBatchStore, 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":"Is there a cleaner way to separate JunctionPineMetricsFlow'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":"JunctionHarborIndexCoordinator is blocking the next release because a misleading timeout name used in five packages. I need two concrete outcomes from a single pass: assess ownership and failure handling in projects/junction/pkg/cache/lease.rs, and capture the contract and rollback note for consumers. Use the existing Kafka conventions in projects/junction/pkg/cache/lease.rs; retain the existing CLI flags and exit codes. 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":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Goal: The data is already available in projects/junction/engine/render/atlas.cpp; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Symptom: The public surface of JunctionJuniperCLIService is frozen, but its internal ownership in projects/junction/Sources/App/SessionStore.swift is difficult to test and even harder to change safely. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside JunctionJuniperCLIService\n- retain the existing CLI flags and exit codes\n\nThe relevant code crosses logistics, WebAssembly, MySQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"JunctionWillowCodecCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Memory attributed to JunctionKiteSchedulerService rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"For JunctionRavenSessionCoordinator, finish JunctionRavenSessionCoordinator's responsive empty and retry states; once that is complete, capture the contract and rollback note for consumers. Work from projects/junction/config/staging.toml, stay with Kafka, and retain the existing CLI flags and exit codes. Keep the two outcomes separately reviewable.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"JunctionMicaProfileCoordinator needs a paired pass: change JunctionMicaProfileCoordinator's known staging timeout from 15 to 30 seconds, plus capture the contract and rollback note for consumers. Use projects/junction/app/src/main/SyncWorker.kt as the source of truth, preserve the Cloudflare Workers contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.3,"slice":"mixed","lang":"en"} +{"prompt":"Give JunctionLedgerGateStore'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.5,"slice":"core","lang":"en"} +{"prompt":"JunctionCloudReconcilerCoordinator is blocking the next release because a feature flag whose default differs between environments. I need two concrete outcomes from a single pass: find the unknown cause of a feature flag whose default differs between environments, and capture the contract and rollback note for consumers. Use the existing Spring Boot conventions in projects/junction/ui/settings/PrivacyPane.tsx; retain the existing CLI flags and exit codes. Keep the outcomes distinct so reviewers can see which evidence supports the assessment and which files or prose satisfy the requested change.\n\nConstraints:\n- preserve public wire values and tenant boundaries\n- cover cancellation and retry behavior\n- avoid generated code and unrelated cleanup\n- include a rollback trigger that an on-call engineer can measure\n\nThis is a fresh workstream for the release, so derive everything from the repository and the context here.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Introduce a durable deduplication key for JunctionFernSnapshotStore 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":"JunctionOspreyJobCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"# projects/junction/Sources/App/SessionStore.swift\n[worker.junctionorbitsyncflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctionorbitsyncflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctionorbitsyncflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionOrbitSyncFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50148\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 JunctionOrbitSyncFlow'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":"En projects/junction/web/components/FilterDrawer.vue, JunctionRainfallDBStore tiene un problema intermitente en el flujo de GraphQL. Lee el flujo actual y dime si ownership, cancelación y orden son seguros; solo necesito el análisis.\n\nRestricciones:\n- seguir con GraphQL\n- conservar compatibilidad y cancelación\n- limitar el cambio a JunctionRainfallDBStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"es"} +{"prompt":"Why is JunctionDeltaCanvasService stalling?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating a misleading timeout name used in five packages in JunctionCoralUploadStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Headsup: Two asks around JunctionFlintTimelineCoordinator: (1) lay out a staged migration for JunctionFlintTimelineCoordinator; (2) also add the visible loading and offline states. Retain the existing cli flags and exit codes, and leave a clear boundary between the resulting artifacts or edits.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Ticket OPS-50157: retire the legacy replay path for JunctionLedgerGateCoordinator\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for JunctionLedgerGateCoordinator, 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":"Since the last release, JunctionCraneWorkspaceStore has shown a misleading timeout name used in five packages; nobody on the team can reproduce it reliably on a laptop. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- retain the existing CLI flags and exit codes\n- stay compatible with the existing GraphQL deployment\n- keep the work scoped to JunctionCraneWorkspaceStore and its direct tests\n\nThis repository spans logistics, WebAssembly, MySQL; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Trace JunctionBirchMigratorService's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"JunctionAtlasSearchCoordinator: make the api less awkward","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"JunctionAcornWidgetStore 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":"# projects/junction/crates/index/src/segment.rs\n[worker.junctionharborindexflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctionharborindexflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctionharborindexflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionHarborIndexFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50112\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 JunctionHarborIndexFlow'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":"FYI: projects/junction/engine/render/atlas.cpp has grown through several launches, and JunctionCoralUploadService now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- retain the existing CLI flags and exit codes\n- stay compatible with the existing Spring Boot deployment\n- keep the work scoped to JunctionCoralUploadService and its direct tests\n\nThis repository spans logistics, WebAssembly, MySQL; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Meanwhile: # projects/junction/lib/codec/frame.cc\n[worker.junctioncinderauthflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctioncinderauthflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctioncinderauthflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionCinderAuthFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50130\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 JunctionCinderAuthFlow'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":"How does JunctionVelaDrawerStore propagate cancellation through the GraphQL boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"JunctionBasilRunnerCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"JunctionSableParserCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"A flaky failure around JunctionCloudReconcilerStore survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside JunctionCloudReconcilerStore\n- retain the existing CLI flags and exit codes\n\nThe relevant code crosses logistics, WebAssembly, MySQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Drop JunctionSpruceDaemonService's unused import","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"JunctionNimbusFormCoordinator needs a paired pass: change JunctionNimbusFormCoordinator's known staging timeout from 15 to 30 seconds, plus capture the contract and rollback note for consumers. Use projects/junction/infra/modules/edge/main.tf as the source of truth, preserve the GraphQL contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Architect a gradual ownership transfer for JunctionBeaconStoreStore across two teams, including module seams, temporary interfaces, observability, handoff criteria, and rollback responsibility. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Unify the JunctionCloudReconcilerService validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Locally: Ticket OPS-50127: retire the legacy replay path for JunctionRavenSessionFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for JunctionRavenSessionFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"Compare the old and new JunctionMapleQueueStore 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":"For JunctionCinderAuthCoordinator, change JunctionCinderAuthCoordinator's known staging timeout from 15 to 30 seconds; once that is complete, capture the contract and rollback note for consumers. Work from projects/junction/engine/render/atlas.cpp, stay with Spring Boot, and retain the existing CLI flags and exit codes. Keep the two outcomes separately reviewable.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"The public surface of JunctionSlateEditorService is frozen, but its internal ownership in projects/junction/ui/settings/PrivacyPane.tsx is difficult to test and even harder to change safely. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside JunctionSlateEditorService\n- retain the existing CLI flags and exit codes\n\nThe relevant code crosses logistics, WebAssembly, MySQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"What does JunctionGarnetModalStore own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"JunctionMarbleTokenService needs an idempotent replay endpoint backed by Kafka; accept a cursor, cap each page at 500 items, and return a stable continuation token.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"PM is preparing the JunctionHarborIndexStore rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside JunctionHarborIndexStore\n- retain the existing CLI flags and exit codes\n\nThe relevant code crosses logistics, WebAssembly, MySQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Sketch the JunctionMicaProfileStore migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"The JunctionOrbitSyncStore 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":"Production: projects/junction/web/components/FilterDrawer.vue の JunctionWrenExportFlow で、GraphQL の flow に断続的な問題が起きています。 段階、互換性、metrics、rollback、ownership を提案し、コード変更の前で止めてください。\n\n制約:\n- GraphQL を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は JunctionWrenExportFlow のみ","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"ja"} +{"prompt":"Staging: The destination for JunctionAcornWidgetService is broadly agreed; the missing piece is a reversible route from projects/junction/pkg/cache/lease.rs to that target. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside JunctionAcornWidgetService\n- retain the existing CLI flags and exit codes\n\nThe relevant code crosses logistics, WebAssembly, MySQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"JunctionAcornWidgetFlow's staging timeout is already known to be wrong: change the single projects/junction/pkg/cache/lease.rs value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"CI: For JunctionGarnetModalCoordinator, assess ownership and failure handling in projects/junction/src/sync/reconcile.ts; once that is complete, capture the contract and rollback note for consumers. Work from projects/junction/src/sync/reconcile.ts, stay with Cloudflare Workers, and retain the existing CLI flags and exit codes. Keep the two outcomes separately reviewable.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Incident timeline — INC-50150\n\n08:02 deploy JunctionCoralUploadCoordinator 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 JunctionCoralUploadCoordinator 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":"diff --git a/projects/junction/cmd/exporter/main.py b/projects/junction/cmd/exporter/main.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/junction/cmd/exporter/main.py\n+++ b/projects/junction/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\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Restructure JunctionQuartzPlayerCoordinator 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":"JunctionNovaPickerCoordinator: polish, then correct","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"diff --git a/projects/junction/workers/thumbnail/consumer.ex b/projects/junction/workers/thumbnail/consumer.ex\nindex 62d71aa..90f3c1e 100644\n--- a/projects/junction/workers/thumbnail/consumer.ex\n+++ b/projects/junction/workers/thumbnail/consumer.ex\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 JunctionEmberRelayFlow'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":"Ticket OPS-50111: retire the legacy replay path for JunctionRainfallDBFlow\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 JunctionRainfallDBFlow 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":"Give JunctionNimbusFormStore a README example","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Atlas: For JunctionSpruceDaemonCoordinator, separate JunctionSpruceDaemonCoordinator's policy from transport without behavior changes; once that is complete, correct the known stale timeout beside it. Work from projects/junction/ml/pipeline/features.py, stay with Kotlin coroutines, and retain the existing CLI flags and exit codes. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"En projects/junction/ml/pipeline/features.py, JunctionQuartzPlayerService tiene un problema intermitente en el flujo de Kotlin coroutines. Separa responsabilidades y elimina duplicación, conservando API, wire values, orden y comportamiento observable.\n\nRestricciones:\n- seguir con Kotlin coroutines\n- conservar compatibilidad y cancelación\n- limitar el cambio a JunctionQuartzPlayerService Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con Kotlin coroutines alrededor de JunctionQuartzPlayerService.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"es"} +{"prompt":"# CI job 50122: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: Kafka\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] JunctionSableParserFlowIntegration.replays_after_timeout ... ok\n[test] JunctionSableParserFlowIntegration.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 \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\nFind the source of this JunctionSableParserFlow 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":"Split projects/junction/web/components/FilterDrawer.vue by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Does JunctionSpruceDaemonStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Dedupe JunctionAsterWebhookService's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Unify the JunctionPrismCacheStore validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Beacon: The next client release depends on a new JunctionFernSnapshotService capability in projects/junction/internal/auth/refresh.go, with GraphQL already chosen by the platform group. Implement the endpoint and durable cursor, enforce tenant authorization and idempotency, emit useful spans, cap work per request, and include focused tests for retries, cancellation, and malformed cursors.\n\nConstraints:\n- retain the existing CLI flags and exit codes\n- stay compatible with the existing GraphQL deployment\n- keep the work scoped to JunctionFernSnapshotService and its direct tests\n\nThis repository spans logistics, WebAssembly, MySQL; use its existing conventions rather than importing a new abstraction.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"JunctionPrismCacheCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"thread 'tokio-runtime-worker' panicked at projects/junction/app/src/main/SyncWorker.kt:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: junctionnovapickerflow::scheduler::LeaseTask::flush\n at ./projects/junction/app/src/main/SyncWorker.kt:217:18\n 4: junctionnovapickerflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nFind the source of this JunctionNovaPickerFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Cinder: Unify the JunctionLumenChartService validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Correct the JunctionCraneWorkspaceService flag default","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Introduce a durable deduplication key for JunctionWillowCodecStore 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":"projects/junction/ml/pipeline/features.py has grown through several launches, and JunctionCopperBridgeStore now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- retain the existing CLI flags and exit codes\n- stay compatible with the existing Kotlin coroutines deployment\n- keep the work scoped to JunctionCopperBridgeStore and its direct tests\n\nThis repository spans logistics, WebAssembly, MySQL; use its existing conventions rather than importing a new abstraction.\n\nThe target structure is settled; carry out the behavior-preserving edits rather than writing another strategy.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'JunctionAtlasSearchFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[JunctionAtlasSearchFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/junction/ui/settings/PrivacyPane.tsx:144: error: -[JunctionAtlasSearchFlowTests 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 '-[JunctionAtlasSearchFlowTests 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，并明确说明证据和取舍。 Use the UI evidence to complete JunctionAtlasSearchFlow'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":"Please resist widening this one: JunctionPineMetricsStore works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside JunctionPineMetricsStore\n- retain the existing CLI flags and exit codes\n\nThe relevant code crosses logistics, WebAssembly, MySQL. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"On compact widths, JunctionKiteSchedulerStore'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.4,"slice":"core","lang":"en"} +{"prompt":"JunctionSlateEditorFlow returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/junction/ui/settings/PrivacyPane.tsx and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"How does JunctionAmberFilterStore propagate cancellation through the Kafka boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Compare JunctionCinderAuthService's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Animate the JunctionNimbusFormService drawer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-50116\n\n08:02 deploy JunctionCraneWorkspaceFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current JunctionCraneWorkspaceFlow 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":"UI ticket DES-50142: finish the compact JunctionMarbleTokenFlow filter experience\n\nRoute: /catalog/search\nSource: projects/junction/pkg/cache/lease.rs\nFramework: Kafka\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 JunctionMarbleTokenFlow'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":"Delta: diff --git a/projects/junction/infra/modules/edge/main.tf b/projects/junction/infra/modules/edge/main.tf\nindex 62d71aa..90f3c1e 100644\n--- a/projects/junction/infra/modules/edge/main.tf\n+++ b/projects/junction/infra/modules/edge/main.tf\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is JunctionFernSnapshotCoordinator'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/junction/crates/index/src/segment.rs\nfinal class JunctionAcornWidgetCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 JunctionAcornWidgetCoordinator; 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":"Before touching projects/junction/internal/auth/refresh.go, 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":"JunctionBeaconStoreCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"This should remain a deliberately small patch: JunctionCedarPolicyStore has one known configuration mistake in projects/junction/engine/render/atlas.cpp, not an open-ended failure investigation. 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- retain the existing CLI flags and exit codes\n- stay compatible with the existing Spring Boot deployment\n- keep the work scoped to JunctionCedarPolicyStore and its direct tests\n\nThis repository spans logistics, WebAssembly, MySQL; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Security flagged JunctionAsterWebhookStore for a read-only pass because its Cloudflare Workers boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current Cloudflare Workers operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL 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":"JunctionMapleQueueCoordinator: polish the last piece","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Read projects/junction/infra/modules/edge/main.tf and tell me whether JunctionWillowCodecService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"How does JunctionSlateEditorStore propagate cancellation through the Spring Boot boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'JunctionBeaconStoreFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[JunctionBeaconStoreFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/junction/apps/console/routes/usage.svelte:144: error: -[JunctionBeaconStoreFlowTests 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 '-[JunctionBeaconStoreFlowTests 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 JunctionBeaconStoreFlow'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":"Where did JunctionOspreyJobService's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Ember: Incident timeline — INC-50132\n\n08:02 deploy JunctionBirchMigratorFlow 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 JunctionBirchMigratorFlow 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":"UI ticket DES-50134: finish the compact JunctionBasilRunnerFlow filter experience\n\nRoute: /catalog/search\nSource: projects/junction/src/sync/reconcile.ts\nFramework: Cloudflare Workers\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring JunctionBasilRunnerFlow'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":"Ticket OPS-50133: retire the legacy replay path for JunctionSpruceDaemonFlow\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 JunctionSpruceDaemonFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Architect a gradual ownership transfer for JunctionMapleQueueService 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":"Translate the JunctionPrismCacheService setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Could the reasoning behind JunctionFrostPanelFlow's Cloudflare Workers choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Three teams extended JunctionJuniperCLIStore independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current Kotlin coroutines operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL monorepo, so keep ownership and handoff points understandable in a small review.\n\nThe target structure is settled; carry out the behavior-preserving edits rather than writing another strategy.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"$ pnpm test --filter JunctionCedarPolicyFlow\n RUN v3.2.4 /workspace/apps/console\n × JunctionCedarPolicyFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=50110 phase=resume storedCursor=seg-0183\n session=50110 phase=fetch requestCursor=seg-0183 pageSize=200\n session=50110 phase=commit receivedCursor=seg-0184 itemCount=0\n session=50110 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nFind the source of this JunctionCedarPolicyFlow 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":"Trace JunctionCinderAuthStore's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"The JunctionMarbleTokenStore 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":"Release engineering needs a JunctionDriftConsoleStore 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":"thread 'tokio-runtime-worker' panicked at projects/junction/internal/auth/refresh.go:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: junctionnimbusformflow::scheduler::LeaseTask::flush\n at ./projects/junction/internal/auth/refresh.go:217:18\n 4: junctionnimbusformflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nDetermine why JunctionNimbusFormFlow 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":"The behavior of JunctionLedgerGateService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/junction/packages/api/openapi.yaml. 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- touch generated artifacts only through their checked-in generator\n- retain the existing CLI flags and exit codes\n- retain the current Kafka operational envelope\n\nSeveral teams work in this logistics, WebAssembly, MySQL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-50140\n\n08:02 deploy JunctionKiteSchedulerFlow 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 JunctionKiteSchedulerFlow 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":"In projects/junction/services/ledger/replay.go hat JunctionRainfallDBService ein sporadisches Problem im GraphQL-Ablauf. Vervollständige Responsive Layout, Empty- und Retry-State, Tastaturfokus, Dark Mode und Reduced Motion.\n\nRandbedingungen:\n- GraphQL weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf JunctionRainfallDBService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um JunctionRainfallDBService mit GraphQL kompatibel.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"de"} +{"prompt":"JunctionCraneWorkspaceCoordinator: ship, then assess","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Release engineering needs a JunctionMosaicGridStore 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":"We need to move JunctionOrbitSyncService from the legacy store to Kotlin coroutines. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Frost: UI ticket DES-50128: finish the compact JunctionFlintTimelineFlow filter experience\n\nRoute: /catalog/search\nSource: projects/junction/Sources/App/SessionStore.swift\nFramework: Kotlin coroutines\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring JunctionFlintTimelineFlow'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":"Garnet: Incident timeline — INC-50118\n\n08:02 deploy JunctionOpalRouterFlow 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 JunctionOpalRouterFlow 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":"JunctionIrisBatchCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Harbor: # projects/junction/ml/pipeline/features.py\n[worker.junctiondeltacanvasflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.junctiondeltacanvasflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.junctiondeltacanvasflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.JunctionDeltaCanvasFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-50123\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/junction/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":"Iris: projects/junction/apps/console/routes/usage.svelte has grown through several launches, and JunctionPineMetricsService now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- retain the existing CLI flags and exit codes\n- stay compatible with the existing Cloudflare Workers deployment\n- keep the work scoped to JunctionPineMetricsService and its direct tests\n\nThis repository spans logistics, WebAssembly, MySQL; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Compare the old and new JunctionQuartzPlayerStore 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":"What sequence would let JunctionLedgerGateFlow adopt Kafka with dual reads but no dual writes? Include data validation, canary scope, and the decision that ends compatibility mode. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Two engineers disagree about whether JunctionAtlasSearchService's cache is authoritative. Walk the reads and writes in projects/junction/ui/settings/PrivacyPane.tsx and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-50115: retire the legacy replay path for JunctionCloudReconcilerFlow\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 JunctionCloudReconcilerFlow 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":"Split JunctionSableParserStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Juniper: The minimum supported Cloudflare Workers version in projects/junction/src/sync/reconcile.ts 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":"diff --git a/projects/junction/infra/modules/edge/main.tf b/projects/junction/infra/modules/edge/main.tf\nindex 62d71aa..90f3c1e 100644\n--- a/projects/junction/infra/modules/edge/main.tf\n+++ b/projects/junction/infra/modules/edge/main.tf\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nWire JunctionWillowCodecFlow'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.8,"slice":"pasted-context","lang":"en"} diff --git a/data/round2-11.jsonl b/data/round2-11.jsonl index 7477eb5..93457e6 100644 --- a/data/round2-11.jsonl +++ b/data/round2-11.jsonl @@ -1,200 +1,200 @@ -{"prompt": "courier locations stop updating for a subset of couriers every evening:\n\n[location] 18:41:02 batch received, 412 couriers\n[location] 18:41:02 written to redis, 412 keys\n[location] 18:46:02 batch received, 388 couriers\n[location] 18:51:02 batch received, 214 couriers\n[location] 18:56:02 batch received, 88 couriers\n[app] courier c_9021 location publisher: android doze mode entered\n[app] courier c_9021 location publisher: wakelock released by system\n\nthe android app publishes from a foreground service, but only while the courier is actively holding the phone; the numbers drop as couriers pocket their phones after pickup", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "our partner changelog needs an entry for the proof-of-delivery threshold becoming public", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "the courier app should show why an offer was rejected, rather than the offer simply vanishing", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "a chain's IT team asked five questions about opening-hours propagation and our honest answers are all worse than they expect. write the documentation that answers them accurately, including the beta API's real limitations, without either overselling it or making the product sound unfinished it doesn't have to be elegant, it has to be defensible in a review.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "courier screen", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "our health endpoint reports the dispatcher healthy while its zone has no couriers connected at all", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "the geometry kernel is wrapped in three adapter layers, each added because nobody wanted to touch the one below, and a simple call now crosses all three with a conversion at every boundary. collapse them to one adapter, keep the kernel's semantics exactly as they are, and tell me which conversions were silently lossy", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "gateway returns 503 for one upstream while envoy says the cluster is healthy:\n\nenvoy access log:\n[2026-07-29T11:02:14.881Z] \"POST /v1/orders HTTP/2\" 503 UF 0 91 30001 - \"-\" \"lumen-app/4.1\" \"8f2b1c40\" \"orders.internal\" \"10.4.2.71:8080\"\n\nresponse flags: UF = upstream connection failure\ncluster stats:\n upstream_cx_connect_timeout: 41882\n upstream_cx_active: 0\n upstream_rq_pending_overflow: 0\n health_check.attempt: 8412\n health_check.success: 8412\n membership_healthy: 4\n\nhealth checks pass on :8081 and traffic goes to :8080, which is a detail nobody remembered until today", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "flutter app shows stale order status for about a minute after delivery:\n\n[ws] connected wss://api.lumen.io/orders/88412/events\n[ws] event {\"type\":\"picked_up\",\"at\":\"18:52:11Z\"}\n[ws] event {\"type\":\"en_route\",\"at\":\"18:52:44Z\"}\n[ws] ping timeout, reconnecting (attempt 1)\n[ws] connected wss://api.lumen.io/orders/88412/events\n[ws] event {\"type\":\"en_route\",\"at\":\"18:52:44Z\"}\n[http] GET /orders/88412 → status: delivered, delivered_at: 18:58:02Z\n[ui] still showing \"on its way\"\n\non reconnect the socket replays from the last event it has rather than the current state, and the UI only updates from socket events", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "elixir cluster partitions during deploys and orders get double-assigned:\n\n11:02:14.101 [warn] :global name conflict for {:dispatcher, \"Z3\"}, resolving\n11:02:14.104 [info] node lumen@10.4.2.71 down\n11:02:14.118 [info] :global re-registering {:dispatcher, \"Z3\"} on lumen@10.4.2.72\n11:02:14.882 [warn] duplicate assignment detected for order 88412: c_9021 and c_9044\n11:02:15.114 [info] node lumen@10.4.2.71 up\n11:02:15.118 [warn] :global name conflict for {:dispatcher, \"Z3\"}, resolving\n\ndeploys are rolling, four nodes, and the dispatcher is a singleton per zone registered with :global", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "a bulk status endpoint for chains needs rate limits that accommodate 1,400 calls in a burst without letting anyone else do the same. decide the shape with me, then implement", "purpose": "backendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "couriers get assigned orders from closed restaurants during the dinner rush:\n\n[dispatch] 18:41:02.114 order 88412 ready_at=18:55 restaurant=r_4471 zone=Z3\n[dispatch] 18:41:02.118 candidate couriers: 12 within 2km\n[dispatch] 18:41:02.141 assigned to courier c_9021 (score 0.88, eta_to_pickup 6m)\n[dispatch] 18:41:02.882 courier c_9021 accepted\n[restaurant] 18:38:44.001 r_4471 status changed to closed (manual, staff)\n[dispatch] 18:41:12.004 order 88412 pickup failed: restaurant closed\n[dispatch] 18:41:12.009 order 88412 requeued, courier c_9021 released, compensation issued\n\nthe dispatcher reads restaurant state from a GenServer cache that refreshes every five minutes", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "CAD files saved on windows won't open on mac, one customer's whole team is blocked:\n\nreading assembly.cadx:\n header ok, version 4.1, units mm\n reading part 1/41: ok\n reading part 2/41: ok\n reading part 12/41: error: referenced file not found: C:\\Users\\dana\\Projects\\brackets\\M6.cadpart\n reading part 13/41: error: referenced file not found: ..\\..\\shared\\fasteners\\M6.cadpart\n\nwe store both an absolute and a relative path for each referenced part, prefer the absolute, and fall back to the relative resolved against the assembly's directory using the platform separator", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "design doc for our order state machine, written a year ago. does it match what we run?\n\n## States\nplaced → confirmed → preparing → ready → picked_up → en_route → delivered\nAny state can transition to cancelled before picked_up. After picked_up, only delivered or failed.\n\n## Guarantees\n- Transitions are recorded in an append-only log and are the source of truth.\n- Clients derive current state from the log, so replay is always safe.\n- The websocket delivers every transition at least once, in order.\n\n## Not covered\nRestaurant-initiated cancellation after pickup. Partial refunds. Multi-courier handoff.\n\nwe added handoff in March, cancellation after pickup exists in the admin tool, and the socket replays from the client's last event rather than the log head", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "gateway's retry policy, which i think is amplifying incidents rather than smoothing them:\n\nretry_policy:\n retry_on: 5xx,reset,connect-failure,refused-stream\n num_retries: 3\n per_try_timeout: 10s\n retry_back_off: { base_interval: 0.025s, max_interval: 0.25s }\n retriable_status_codes: [503]\nrequest_timeout: 30s\n\nthe upstreams behind this include a payment service that is not idempotent on POST, and during the last incident our own retries tripled the load on a service that was already failing\n\nlast incident, from the upstream's side:\n inbound rps before: 1,200\n inbound rps during the incident: 3,910\n upstream_rq_retry: 41,882 in ten minutes\n upstream_rq_retry_overflow: 0\n our own error rate at the edge: 61%\n\nthe payment service owner has asked, twice, that we stop retrying their POSTs", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "redis config versus what the docs recommend for our access pattern:\n\n# ours\nmaxmemory: 8gb\nmaxmemory-policy: noeviction\nappendonly: yes\nappendfsync: everysec\nsave: 900 1 300 10 60 10000\ntimeout: 0\ntcp-keepalive: 300\n\nwe store courier locations (ephemeral, 30s TTL), dispatch state (must not be lost), and a session cache (rebuildable)\n\nthe noeviction policy means that when we hit 8gb, writes fail and dispatch stops, which happened last friday\n\nfriday's numbers when it filled:\n used_memory: 8.00G / 8.00G\n evicted_keys: 0\n rejected_connections: 0\n errors: OOM command not allowed when used memory > 'maxmemory' (41,882 in six minutes)\n keyspace: courier:loc:* 6.1G, dispatch:inflight:* 1.2G, session:* 0.7G\n\ndispatch stopped for eleven minutes and nothing recovered it until someone flushed the location keys by hand", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "document class has become the place everything goes. same behaviour, better seams:\n\nclass Document : public QObject {\n // owns the geometry tree\n // owns the undo stack\n // owns the selection\n // handles save, autosave and recovery\n // holds the plugin-visible IDocument implementation\n // emits 22 signals, of which the UI connects 19\n // has a static registry of open documents used by the plugin host\n};\n\n2,400 lines, and every one of those responsibilities has needed changing this quarter\n\nfor scale, this quarter's changes touched:\n save/autosave path 6 commits\n undo stack ownership 4 commits\n selection model 3 commits\n plugin-visible IDocument 5 commits\n the static open-documents registry 2 commits\n\nand every one of those commits also had to touch at least one unrelated part of the same file", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "restaurant cache refresh to 30 seconds", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "route inspector needs a diff view", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "one availability check for couriers", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "is one_for_all right for the zone tree?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "i'd like an honest read of whether a slow offer loop can block a whole zone's dispatch, given three sequential twenty-second offers in the dispatcher process, and the fix if it can", "purpose": "review", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "what does the dispatcher do with an offer that's accepted after the window closes", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "flutter analyze before the store release:\n\ninfo • Avoid `print` calls in production code • lib/services/ws_client.dart:88:5 • avoid_print\nwarning • The value of the field '_reconnectTimer' isn't used • lib/services/ws_client.dart:22:9 • unused_field\ninfo • Use 'const' with the constructor to improve performance • lib/widgets/order_card.dart:41:12 • prefer_const_constructors\nwarning • Missing case clause for 'handoff' • lib/models/order_state.dart:66:5 • missing_enum_case_clause\ninfo • Don't use 'BuildContext's across async gaps • lib/screens/order_screen.dart:141:22 • use_build_context_synchronously\n\n5 issues, and the missing enum case is the handoff state we added in march", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"} -{"prompt": "gateway filters are copy-pasted per route with small differences:\n\n# routes/orders.yaml\nhttp_filters: [cors, jwt_auth, rate_limit, request_id, router]\n\n# routes/partners.yaml\nhttp_filters: [cors, jwt_auth, rate_limit, request_id, ext_authz, router]\n\n# routes/internal.yaml\nhttp_filters: [request_id, router]\n\n# routes/legacy.yaml\nhttp_filters: [cors, api_key_auth, rate_limit, router] # no request_id, which is why legacy traces are useless\n\nfour lists maintained by hand, and adding a filter means remembering all four files", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "elixir contexts have leaked into each other and the boundaries are gone:\n\nLumen.Orders.get_order/1 # used by Dispatch, Couriers, Admin, Billing\nLumen.Dispatch.assign/2 # calls Orders.update_state/2 directly\nLumen.Couriers.available?/1 # duplicated in Dispatch, as above\nLumen.Billing.charge/1 # called from Orders.deliver/1 inline\nLumen.Admin.force_reassign/2 # calls Dispatch internals via :sys.replace_state\n\nfive contexts, no boundaries, and the admin one reaches into a GenServer's state to fix production problems", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "modeller crashes when undoing a boolean operation on a large assembly:\n\nThread 1 \"cadmodeller\" received signal SIGSEGV, Segmentation fault.\n0x00007ffff7a2c118 in cad::geom::BRepShape::~BRepShape() at src/geom/brep.cpp:412\n412\t for (auto* face : faces_) delete face;\n(gdb) bt\n#0 cad::geom::BRepShape::~BRepShape\n#1 0x0000555555601a44 in cad::undo::BooleanCommand::undo() at src/undo/boolean.cpp:141\n#2 0x00005555556220c8 in cad::undo::UndoStack::undo() at src/undo/stack.cpp:88\n#3 0x00007ffff7b0a112 in QAction::triggered()\n(gdb) p faces_.size()\n$1 = 41882\n\nthe boolean result shares face pointers with its operands, and undo deletes the result while the operands are still live", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "nuestro gateway devuelve 429 a un cliente que está muy por debajo de su límite:\n\ncliente: partner_4471, límite contratado 1000 rpm\nmétricas del gateway:\n ratelimit_hits{descriptor=\"partner_4471\"} 412 rpm\n ratelimit_over_limit{descriptor=\"partner_4471\"} 188 rpm\n ratelimit_error{...} 0\n\nconfiguración:\n descriptors:\n - key: partner_id\n rate_limit: { unit: minute, requests_per_unit: 1000 }\n - key: partner_id\n value: partner_4471\n rate_limit: { unit: second, requests_per_unit: 5 }\n\nel segundo descriptor lo añadió alguien hace meses para una prueba de carga", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "es"} -{"prompt": "before this goes near production, is the supervision strategy right?\n\ndefmodule Lumen.Dispatch.ZoneSupervisor do\n use Supervisor\n\n def init(zone) do\n children = [\n {Lumen.Dispatch.Dispatcher, zone},\n {Lumen.Dispatch.CourierCache, zone},\n {Lumen.Dispatch.RestaurantCache, zone}\n ]\n Supervisor.init(children, strategy: :one_for_all, max_restarts: 3, max_seconds: 5)\n end\nend\n\nthe dispatcher holds in-flight assignments in its state, the caches are refreshed every five minutes from postgres, and a restart loses whatever the dispatcher was holding", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "undo implementation, which i inherited and which is the source of two crash clusters:\n\nclass BooleanCommand : public Command {\n BRepShape* result_;\n BRepShape* lhs_;\n BRepShape* rhs_;\npublic:\n void redo() override {\n result_ = geom::boolean_union(lhs_, rhs_); // shares face pointers with operands\n doc_->replace({lhs_, rhs_}, result_);\n }\n void undo() override {\n doc_->replace({result_}, {lhs_, rhs_});\n delete result_;\n }\n};\n\nthe undo stack holds a hundred of these, documents can be closed with the stack non-empty, and geom::boolean_union is documented as \"may reference input geometry\"", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "rate limit configuration we ship to customers, which i suspect nobody fully understands:\n\ndomain: lumen_api\ndescriptors:\n - key: partner_id\n rate_limit: { unit: minute, requests_per_unit: 1000 }\n - key: partner_id\n value: partner_4471\n rate_limit: { unit: second, requests_per_unit: 5 }\n - key: partner_id\n descriptors:\n - key: endpoint\n value: /v1/orders\n rate_limit: { unit: minute, requests_per_unit: 100 }\n\nwhen a request matches several descriptors, which apply? all of them, the most specific, or the first match? our documentation says one thing and the behaviour looks like another", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "file format's reference handling, which is why cross-platform assemblies break:\n\nstruct PartRef {\n std::string absolute_path; // as saved on the authoring machine\n std::string relative_path; // relative to the assembly file, native separators\n std::optional content_id; // added in 4.0, populated only for new refs\n};\n\nPartRef resolve(const PartRef& ref, const fs::path& assembly_dir) {\n if (fs::exists(ref.absolute_path)) return load(ref.absolute_path);\n auto rel = assembly_dir / ref.relative_path;\n if (fs::exists(rel)) return load(rel);\n throw NotFound(ref.absolute_path);\n}\n\ncontent_id exists and is never used in resolution; relative paths keep whatever separator the authoring platform used", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "changelog for the modeller's 4.2 release:\n\n41c9e0b fix(undo): boolean undo no longer frees geometry still referenced by operands\n88f21c0 feat(files): assemblies resolve references by content id before falling back to paths\nc0aa774 fix(autosave): autosave writes to a temporary file and renames, never truncates in place\n2e91b45 feat(perf): assembly load is now parallel, 41 parts in 2s instead of 14s\naa30f19 fix(ui): the measurement tool no longer snaps to hidden geometry\n9c1d004 chore: minimum macOS is 13, minimum Windows is 10 22H2\n4410bb7 feat(export): STEP export preserves assembly structure\nb77e910 fix(undo): the undo stack is cleared on document close rather than leaked\n\nour users are mechanical engineers; two of these are data-loss fixes and should be impossible to miss", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "three modules decide whether a courier is available and they disagree:\n\n# dispatch/assign.ex\ndefp available?(c), do: c.status == :online and c.current_assignment == nil\n\n# dispatch/stacking.ex\ndefp can_take_more?(c), do: c.status in [:online, :delivering] and length(c.assignments) < 2\n\n# admin/courier_view.ex\ndef available?(c), do: c.status == :online and c.last_seen_at > minutes_ago(2)\n\nstacking is the newest and the only one that considers the two-assignment limit; the admin view is what support looks at when a courier complains they're getting no work", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "opening-hours API the chain customer wants, currently a beta nobody supports:\n\nPUT /v1/restaurants/{id}/status { open: bool, reason?: string, until?: timestamp }\n must take effect in dispatch within 30 seconds, contractually\n a close with `until` reopens automatically; without it, the restaurant stays closed until reopened\n orders already accepted are unaffected, which the customer has agreed to but wants stated\n the caller may be the chain's own system, so authentication is a chain-scoped key covering many restaurants\n we must record who closed it and why, and expose that on GET for their own audit\n they will call this for 1,400 restaurants and expect bulk semantics — one call per restaurant is acceptable but rate limits must accommodate it", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "el mapa no centra en la recogida", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "es"} -{"prompt": "Autosave darf nicht in-place schreiben", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "de"} -{"prompt": "doc comments on the plugin interface", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "why is mTLS costing us 40ms?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "order as you see fit", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "we owe the restaurant chain a written explanation of why couriers kept arriving at locations they had closed, and their complaint is reputational rather than financial. write the incident report for a non-technical operations audience, honest about the five-minute cache, and clear about what changes and by when i've already spent an afternoon on it and got nowhere useful.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "assignments occasionally go to two couriers during a rolling deploy and the logs show :global resolving a name conflict at exactly that moment. work through what happens to the dispatcher's in-flight state when the registration moves, before we decide whether the answer is durability or a different registry if the answer is that it's fine as it is, that's a useful answer too.", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "staging has four upstreams and prod has forty-one, with the same connection pool settings", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "per-partner circuit breaking in the gateway, so one slow partner can't take the pool", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "CAD plugin API, which four customers write against with only a header file for documentation:\n\nclass IPlugin {\npublic:\n virtual const char* name() const = 0;\n virtual int apiVersion() const = 0; // must equal CAD_PLUGIN_API_VERSION\n virtual void onDocumentOpened(IDocument*) {}\n virtual void onSelectionChanged(const ISelection&) {}\n virtual bool onCommand(const char* id, ICommandContext&) { return false; }\n virtual void registerCommands(ICommandRegistry&) {}\n};\n\nthings only we know: onSelectionChanged is called on the UI thread and blocking it freezes the app; IDocument pointers are invalidated on close with no notification; onCommand returning true suppresses the built-in command of the same id, including our own; and apiVersion mismatches are silently ignored, the plugin simply never loads\n\nwrite the plugin developer guide", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "gateway's config in staging and prod, and staging never reproduces our timeouts:\n\n# staging\nconnect_timeout: 5s\nrequest_timeout: 30s\nretry: { num_retries: 3, per_try_timeout: 10s }\nhealth_check: { interval: 10s, unhealthy_threshold: 3, port: 8080 }\ncircuit_breakers: { max_connections: 1024, max_pending_requests: 1024 }\nupstreams: 4\n\n# prod\nconnect_timeout: 30s\nrequest_timeout: 30s\nretry: { num_retries: 3, per_try_timeout: 10s }\nhealth_check: { interval: 10s, unhealthy_threshold: 3, port: 8081 }\ncircuit_breakers: { max_connections: 1024, max_pending_requests: 1024 }\nupstreams: 41", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "design spec for the courier app's active delivery screen, flutter:\n\nActive delivery\n- Map fills the top two thirds, route to the next waypoint, courier position as a heading arrow; recentres on a 5 second idle.\n- Bottom card: address, customer name, order items collapsed to a count, and the primary action for the current stage (Arrived / Picked up / Delivered).\n- The primary action is a slide-to-confirm control, not a button, because accidental taps cost us orders.\n- Stacked deliveries show a second card behind the first with the next drop's ETA; swiping up reveals it.\n- Offline: the screen keeps working from cached data, actions queue with a visible \"will send when back online\" state, and the slide control still works.\n- Battery: the screen must not keep the display awake; navigation hand-off to the system maps app is a single tap.\n- Everything must be usable one-handed with gloves on, which means 56dp minimum targets and no long-press-only actions.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "redis policy to allkeys-lru for locations", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "one websocket client for all screens", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "document the 20 second offer window", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "courier API is used by our own flutter app and two partner fleets, and it's documented in a google doc that nobody has updated since the offer window changed. write the reference properly, with the silent drop of over-frequent location updates and the unpublished proof-of-delivery threshold stated plainly rather than discovered by integration partners the hard way", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "our gateway config lives in two repos owned by two teams and neither validates the other's assumptions", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "the offer window is twenty seconds in the dispatcher and twenty-five in the app, which makes legitimate late accepts look like client bugs and has generated a month of misdirected support tickets. align them, and write the short note for support explaining what the symptom actually was context if it helps: this has been open since before i joined the team.", "purpose": "quickFix", "secondary": "writing", "mixed": true, "difficulty": 0.45, "slice": "mixed", "lang": "en"} -{"prompt": "a walkthrough of how an order reaches a courier's phone would help before i touch the socket layer", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "courier scoring function has grown a term per incident, its weights were tuned by hand three times, and nothing about it is tested. restructure it so each term is separately testable and the weights live in configuration, keeping the ranking identical for a replayed evening of real assignments i'd like enough detail that i can hand it to someone else to finish.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "our internal page on the dispatch pipeline stops at \"the dispatcher assigns the order\" and everything after that — offers, acceptance, stacking, handoff — is folklore held by two people. write the page properly, following one order from placement to delivery and naming every service and queue it passes through nobody has trusted this code for about a year, which is part of the problem.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "the measurement tool snaps to hidden geometry, which two customers have described as actively dangerous because a measurement that looks right can be taken from a suppressed part. change the snapping to respect visibility, keep the existing snap priorities otherwise, and make sure suppressed parts stay excluded when they're temporarily shown", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "couriers sent to closed restaurants", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "gateway retries 503s and connect failures three times by default, including for POSTs to a payment service that is not idempotent, and this amplified both of our last two incidents. work through what a defensible retry policy looks like per route class, how we'd enforce idempotency where retries are allowed, and how we stop a well-meaning default from doing this again", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "elixir contexts have leaked into each other to the point where the admin tool reaches into a GenServer's state to fix production problems. i'd rather agree what the boundaries should be, and what each context owns, than keep adding functions wherever they're convenient — with a view on which violations are worth fixing first", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "route inspector is what we open during incidents and it currently shows the config as written rather than as effective, which has misled us twice. build the effective-config view with provenance per value, the request-id lookup, and inline flags for dangerous settings keep it concrete — file names and line numbers are more use than principles here.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "flutter app has three websocket clients with three reconnect strategies and none of them refetches state on reconnect. unify them, then document the reconnect contract so the next screen doesn't invent a fourth", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "restaurant portal ignores half our design tokens and removes focus styles on three components. bring it onto the tokens, and tell me which colour changes will be visible to restaurants who've used this daily for two years", "purpose": "frontendImpl", "secondary": "review", "mixed": true, "difficulty": 0.55, "slice": "mixed", "lang": "en"} -{"prompt": "i'd like to understand how the undo stack interacts with document close, because i suspect it leaks", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "is our health check actually checking the port that serves traffic", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "what guarantees does the location endpoint make about ordering when a phone uploads a backlog", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "a short note on why we're moving dispatcher state to postgres, for the decision log", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "modeller's autosave corrupts files when the app is killed mid-save:\n\nsave sequence from the log:\n 11:02:14.101 autosave started, target /Users/dana/proj/assembly.cadx\n 11:02:14.104 truncating existing file\n 11:02:14.882 wrote header + 12/41 parts\n \n\non next open:\n error: unexpected end of file at offset 8412114 (expected 41882002)\n no backup found; autosave overwrites in place and .bak is only written on explicit save\n\nthe customer lost four hours of work and is understandably furious", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "requests through the mesh get 40ms slower after we enabled mTLS, which is more than we expected:\n\nbefore:\n p50 8ms p95 22ms p99 41ms\nafter:\n p50 12ms p95 61ms p99 188ms\n\nenvoy stats:\n ssl.handshake: 41,882/min\n ssl.session_reused: 118/min\n upstream_cx_total: 41,882/min\n upstream_cx_http2_total: 0\n\nour sidecars are configured for HTTP/1.1 upstreams with no connection pooling changes, so every request appears to be establishing a new TLS session\n\nsidecar config, the relevant part:\n http_protocol_options: { explicit_http_config: { http_protocol_options: {} } }\n common_http_protocol_options: { idle_timeout: 1s }\n circuit_breakers: { max_connections: 1024 }\n transport_socket: { name: envoy.transport_sockets.tls }\n\nthe one second idle timeout was copied from an example config a year ago and nobody has questioned it since", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "bitte einmal drüberschauen, das läuft im Abendgeschäft:\n\ndef assign(order, couriers) do\n couriers\n |> Enum.filter(&available?/1)\n |> Enum.map(&{&1, score(&1, order)})\n |> Enum.sort_by(fn {_, s} -> -s end)\n |> Enum.take(3)\n |> Enum.reduce_while(nil, fn {courier, _}, _ ->\n case offer(courier, order, timeout: 20_000) do\n :accepted -> {:halt, courier}\n _ -> {:cont, nil}\n end\n end)\nend\n\nbis zu 20 Sekunden pro Kurier, drei Kuriere nacheinander, und der aufrufende Prozess ist der Dispatcher für die ganze Zone", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "de"} -{"prompt": "query behind our restaurant dashboard, which times out for chains:\n\nSELECT r.id, r.name,\n count(*) FILTER (WHERE o.state = 'delivered' AND o.placed_at > now() - interval '7 days') AS delivered_7d,\n avg(EXTRACT(epoch FROM (o.picked_up_at - o.ready_at))) FILTER (WHERE o.picked_up_at IS NOT NULL) AS avg_wait,\n (SELECT count(*) FROM order_issues i WHERE i.restaurant_id = r.id AND i.resolved_at IS NULL) AS open_issues,\n (SELECT avg(rating) FROM reviews rv WHERE rv.restaurant_id = r.id AND rv.created_at > now() - interval '30 days') AS rating\nFROM restaurants r\nLEFT JOIN orders o ON o.restaurant_id = r.id\nWHERE r.chain_id = $1\nGROUP BY r.id, r.name;\n\none chain has 1,400 restaurants and orders is 400M rows partitioned by month", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "support's notes on the assembly-won't-open problem, they need to become a customer-facing article:\n\n- happens when an assembly authored on windows is opened on mac or linux, or vice versa\n- the absolute path is tried first and obviously fails on the other platform\n- the relative path then fails too if it was saved with backslashes\n- workaround is opening each missing part manually once, which rewrites the reference\n- for a 40-part assembly that's twenty minutes of clicking\n- files saved by 4.0 or later have a content id we could use but don't\n- customers on mixed-platform teams hit this every time they share a file\n\nwrite the article, including the workaround, and separately tell me what the real fix looks like", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "courier-facing API, which the flutter app and two partner fleets use, documented in a google doc:\n\nPOST /v1/couriers/{id}/location { lat, lon, accuracy_m, heading, speed_kph, battery_pct, at }\n accepted at up to 1 Hz; anything faster is silently dropped, not rejected\n a location older than 60 seconds is ignored, which partners discover by having their history not appear\nPOST /v1/offers/{id}/respond { accept: bool, reason? }\n must be within the 20 second offer window; late responses get 409 and the offer is already gone\nGET /v1/couriers/{id}/assignments\n returns current and next assignment; \"next\" only exists during a stacked delivery\nPOST /v1/assignments/{id}/events { type: \"arrived\"|\"picked_up\"|\"delivered\", at, proof? }\n proof is required for delivered when the order is high value, and the threshold is not published\n\nwrite the reference; the silent drops and the unpublished threshold are what partners keep asking about", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "notes from the incident review, we owe the restaurants an explanation:\n\n18:41 couriers begin receiving orders from restaurants that had closed\n18:52 pattern identified: closures made in the last five minutes are not seen by dispatch\n19:04 restaurant cache refresh reduced from five minutes to thirty seconds as a stopgap\n19:20 issue stops recurring\n21:00 44 orders affected, all requeued or refunded, 12 couriers compensated for wasted trips\n\nroot cause: the dispatcher reads restaurant open/closed state from an in-memory cache refreshed on a timer, with no invalidation when a restaurant changes state\n\nthe restaurants' complaint is that they closed and we kept sending couriers, which made them look bad to customers", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "les notes de la réunion d'architecture, à transformer en document de décision :\n\n- la passerelle applique aujourd'hui quatre politiques différentes selon l'ancienneté de la route\n- personne ne sait laquelle s'applique quand plusieurs descripteurs correspondent\n- la documentation dit « le plus spécifique gagne », le code applique tous les descripteurs correspondants\n- les partenaires configurent leurs propres limites via un fichier YAML que nous appliquons sans validation\n- une limite mal écrite peut aujourd'hui bloquer un partenaire entier, ce qui est déjà arrivé deux fois\n- l'équipe propose un seul modèle explicite, avec validation au moment de l'écriture\n\nrédige la note de décision avec les options et une recommandation", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "fr"} -{"prompt": "operator's guide for the gateway is a single page from when we had one cluster. what's true now:\n\n- routes are defined in git, applied by a controller, and a bad route can be rolled back by reverting\n- rate limit descriptors live in a separate repo owned by the partnerships team, applied without validation\n- the mTLS rotation is automatic but the root has to be rotated manually every two years, and it's due in march\n- an upstream that fails health checks is ejected for 30 seconds, which is shorter than most of our deploys\n- retries are on by default for 503 and connect failures, including for non-idempotent POSTs\n- there is no per-partner circuit breaking; one slow partner can consume the whole connection pool\n\nwrite the operator's guide, and mark the four things here that are actually dangerous defaults", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "questions the restaurant chain's IT team sent before signing, which need a proper answer:\n\n\"How quickly does a change to our opening hours take effect in your dispatch system? If we close a location for an emergency, what is the worst case before couriers stop being sent? Do you have an API for this or is it only the portal? What happens to orders already accepted when we close? Can we see, after the fact, which orders were sent to a closed location and why?\"\n\nour honest answers are: up to five minutes, five minutes, portal only with an API in beta, they stay assigned, and no. write the response as documentation rather than an email, and don't oversell what the beta API does", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "内部向けのオンコール手順書がまだありません。現状、チームが実際にやっていることは次の通りです:\n\n- 最初に見るのはゾーン別のディスパッチ遅延ダッシュボード、5 分を超えたら異常\n- 遅延が特定ゾーンだけなら、そのゾーンの dispatcher プロセスを再起動する（進行中の割り当ては失われるが、20 秒以内に再割り当てされる）\n- 全ゾーンで遅延している場合は redis の接続数を確認する、上限に張り付いていることが多い\n- 「注文が届かない」という問い合わせは、まず websocket ではなく HTTP の状態を見る（websocket は再接続時に最新状態を返さない）\n- デプロイ中の :global 名前衝突は既知の問題で、二重割り当てが起きるが自動で解消される\n- 夜間に redis を再起動してはいけない。クーリエの位置情報がすべて消える\n\nこれをオンコール手順書としてまとめてください。優先順位は夜中に起こされた人が最初に必要とする順で\n\n参考までに、現在のダッシュボードとコマンドはこれだけです:\n\n dispatch_assign_seconds{zone=\"Z3\"} p95 = 6.2s (閾値 5s)\n redis_connected_clients = 9,812 / 10,000\n courier_location_batch_size{zone=\"Z3\"} = 88 (通常は 400 前後)\n\n # ゾーンの dispatcher を再起動する\n bin/lumen rpc 'Lumen.Dispatch.ZoneSupervisor.restart(\"Z3\")'\n # 進行中の割り当てを確認する\n bin/lumen rpc 'Lumen.Dispatch.Dispatcher.inflight(\"Z3\") |> length()'\n\nこれらのコマンドはどこにも書かれておらず、Slack の過去ログを検索して見つけるしかありません", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "ja"} -{"prompt": "credo and dialyzer on the elixir app, gate goes on next week:\n\n┃ [W] ↗ Function body is nested too deep (max_nesting: 2)\n┃ lib/lumen/dispatch/assign.ex:88 #{Lumen.Dispatch.assign/2}\n┃ [R] ↗ Function is too complex (CC is 14, max is 9)\n┃ lib/lumen/dispatch/score.ex:22\n┃ [W] ↗ There should be no unused aliases\n┃ lib/lumen/orders/state.ex:4\n\ndialyzer:\nlib/lumen/dispatch/assign.ex:141:no_return\nFunction offer/3 has no local return\nlib/lumen/orders/state.ex:66:pattern_match\nThe pattern can never match the type {:error, _}\n\n3 credo issues, 2 dialyzer findings, and the no_return one looks like it matters", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "clang-tidy on the modeller, and two of these are our crash clusters:\n\nsrc/undo/boolean.cpp:141:9: warning: 'delete' on a pointer that may be shared [cppcoreguidelines-owning-memory]\nsrc/geom/brep.cpp:412:5: warning: loop deleting raw pointers; consider a container of unique_ptr [modernize-loop-convert]\nsrc/io/save.cpp:88:13: warning: file is truncated before the write succeeds [bugprone-unsafe-file-handling]\nsrc/ui/measure.cpp:22:1: warning: function exceeds recommended size [readability-function-size]\nsrc/plugin/host.cpp:66:22: warning: virtual call in destructor [clang-analyzer-optin.cplusplus.VirtualCall]\n\n5 warnings, and save.cpp:88 is the autosave corruption we've been arguing about", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "dependabot on the elixir app, three open:\n\nphoenix 1.7.12 → 1.7.18 (patch series; changelog mentions a change to channel reconnect behaviour)\necto_sql 3.11.1 → 3.12.1 (minor; migration lock behaviour changed for multi-node deploys)\nfinch 0.18.0 → 0.19.0 (minor; default pool size per host changed from 50 to 10)\n\nour dispatcher runs on four nodes and does migrations on boot; the courier API is the heaviest user of finch", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "os alertas do dispatch acordam-nos por nada e falham no que importa:\n\n- alert: DispatchLatency\n expr: histogram_quantile(0.95, dispatch_assign_seconds_bucket) > 5\n for: 1m\n labels: { severity: page }\n\n- alert: CourierOffline\n expr: up{job=\"courier-api\"} == 0\n for: 0m\n labels: { severity: page }\n\n- alert: RedisMemory\n expr: redis_memory_used_bytes / redis_memory_max_bytes > 0.95\n for: 5m\n labels: { severity: ticket }\n\ncomportamento real: a latência passa de 5s em todas as noites às 19h durante o pico; o redis encheu na sexta-feira e o alerta era apenas um ticket, pelo que ninguém viu antes de o dispatch parar durante onze minutos", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "pt"} -{"prompt": "nuestro cliente de websocket en flutter está escrito tres veces, una por pantalla:\n\n// order_screen.dart\nfinal ws = WebSocketChannel.connect(uri); ws.stream.listen(_onEvent, onDone: _reconnect);\n\n// courier_screen.dart\nfinal ws = IOWebSocketChannel.connect(uri, pingInterval: Duration(seconds: 20));\nws.stream.listen(_onEvent, onError: (_) => _reconnectWithBackoff());\n\n// tracking_screen.dart\nStreamSubscription? _sub;\nvoid _connect() { _sub = channel.stream.listen(_onEvent); }\n// sin reconexión en absoluto\n\ntres estrategias de reconexión, dos de ellas sin backoff, y ninguna vuelve a pedir el estado actual al reconectar", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "es"} -{"prompt": "scoring function has grown a term per incident and nobody can explain the weights:\n\ndefp score(courier, order) do\n distance_score(courier, order) * 0.4 +\n acceptance_rate(courier) * 0.2 +\n idle_time(courier) * 0.15 +\n vehicle_fit(courier, order) * 0.1 +\n zone_affinity(courier, order) * 0.05 +\n batching_bonus(courier, order) * 0.05 +\n (if courier.new?, do: 0.05, else: 0.0) -\n (if recently_rejected?(courier, order.restaurant_id), do: 0.3, else: 0.0)\nend\n\nthe weights were tuned by hand in three separate incidents, the rejection penalty was added last week, and nothing is tested", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "architecture ticket, thinking before code:\n\nDISP-330 — Dispatcher state durability\nThe zone dispatcher is a GenServer holding in-flight assignments in memory, registered via :global, restarted by a one_for_all supervisor. A crash or a rolling deploy loses whatever it was holding, and during deploys :global name conflicts have produced duplicate assignments. The proposal is to move in-flight state into postgres with the GenServer as a cache, or to adopt a proper distributed process registry. Concerns: assignment decisions are latency sensitive (we have a 20 second offer window); postgres is already the bottleneck at dinner peak; and the team has no experience with the alternatives.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "compliance requirement for courier data, which legal has now put a date on:\n\n\"Location data of couriers may be retained only for the duration necessary to complete and account for a delivery, and in any case no longer than 90 days. Couriers must be able to obtain a copy of their location history and to have it erased after that period. Aggregated analytics derived from location data must not permit re-identification of an individual courier. Access by staff must be logged and justified.\"\n\nwe keep raw location points indefinitely in redis and postgres, our analytics tables are keyed by courier id, and access is a support tool with no logging. i want the plan in order of legal risk", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "spec for the gateway's route inspector in our console, which we use during incidents:\n\nRoute inspector\n- Left: route tree grouped by domain, with a health dot per route rolling up its upstreams.\n- Main: the effective configuration for the selected route — filters in order, timeouts, retries, rate limits — with each value showing where it came from (route, domain default, or global).\n- A diff view against the last applied revision, with the git commit and author.\n- Live traffic strip: requests per second, error rate and p99 for the last 15 minutes, updating every 5 seconds.\n- A \"why did this request fail\" box: paste a request id, get the matched route, the filters that ran, and which one returned the error.\n- Dangerous values (retries on non-idempotent methods, no circuit breaker) are flagged inline with an explanation.\n- Read-only for everyone except the two people who can apply changes, and applying goes through git, never directly.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "accessibility findings for the modeller's UI, from a government customer's procurement review:\n\n1. The ribbon is navigable only by mouse; keyboard focus skips from the menu bar to the viewport.\n2. Tool state (active/inactive) is conveyed by a subtle background tint failing contrast at 1.9:1.\n3. The measurement panel updates values without announcing them.\n4. Modal dialogs do not return focus to the invoking control on close.\n5. The viewport has no keyboard alternative for selection, which makes the whole product unusable without a mouse.\n6. Error toasts disappear after 3 seconds regardless of length or importance.\n7. High-contrast mode on Windows is ignored entirely; the app draws its own theme.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "schema we agreed for courier location retention, now it needs building:\n\nCREATE TABLE courier_pings (\n courier_id uuid NOT NULL,\n at timestamptz NOT NULL,\n point geography(Point, 4326) NOT NULL,\n accuracy_m real,\n assignment_id uuid,\n PRIMARY KEY (courier_id, at)\n) PARTITION BY RANGE (at);\n\npartitions are daily; anything older than 90 days must be dropped automatically; a courier's export must be servable within 24 hours of request; erasure must remove pings but keep the delivery record itself; and the analytics tables that currently key on courier_id need a plan of their own because they're derived from this", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "health check port should be 8080", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "drop the stale partner_4471 descriptor", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "tip screen says \"Thankyou\"", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "core", "lang": "en"} -{"prompt": "missing handoff case in the enum switch", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "no retries on POST /v1/payments", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "CAD team's list, with the enterprise renewals in mind:\n\n- autosave must never truncate in place; write-and-rename plus a real backup chain\n- undo must stop sharing ownership of geometry with live objects\n- cross-platform references need to resolve by content id, which we already store\n- the document class needs splitting before anyone can safely touch any of the above\n- plugin API needs documenting; four customers are guessing\n- assembly load is single-threaded and takes 14 seconds for a 41-part assembly\n\ntwo engineers, and one enterprise renewal decision in eight weeks", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "request_id filter missing on legacy routes", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "design tokens versus what the restaurant portal actually uses:\n\ntokens:\n color.surface #FFFFFF / #101317\n color.text.default #10151A / #E8EDF2\n color.accent #E8562A\n color.status.late #B42318\n color.status.ok #067647\n space 4/8/12/16/24/32, radius 6/10/14, focus 2px solid accent, offset 2px\n type: title 20/26, body 14/20, caption 12/16\n\nthe portal: seven hardcoded colours including two versions of the accent, focus styles removed on three interactive components, paddings of 5/7/13/18, and a late-order indicator that is colour-only\n\nbring it onto the tokens, restore focus styles, and give the late indicator a non-colour cue", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "RedisMemory should page, not ticket", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "connect timeout 30s in prod is too long", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "slide-to-confirm instead of a button", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "courier location retention has a legal deadline and no design. work through what we keep, for how long, and what erasure means for the analytics derived from it, then implement the partition drop job as the first concrete piece", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "our dispatch code reaches into the orders context in eleven places to update state directly, which is why the state machine's guarantees are aspirational rather than enforced. route those writes through one function that validates transitions, keep every current transition working exactly as it does, and give me the list of transitions that turn out to be invalid under the documented machine", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "the same \"is this order late\" calculation exists in four places and they disagree by minutes:\n\n# dispatch/lateness.ex\ndef late?(order), do: DateTime.diff(DateTime.utc_now(), order.promised_at) > 0\n\n# restaurant_portal/live/orders.ex\ndef late?(order), do: DateTime.diff(DateTime.utc_now(), order.ready_at) > 300\n\n# courier_app (dart)\nbool isLate(Order o) => DateTime.now().isAfter(o.promisedAt.add(Duration(minutes: 2)));\n\n# analytics/sql/late_orders.sql\nWHERE delivered_at > promised_at + interval '5 minutes'\n\nthe portal is what restaurants see and complain about, the analytics number is what we report to chains in their monthly review, and the two have never matched. i want one definition, applied everywhere, with the analytics figure as the reference because that's the number in contracts", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "stacked delivery card behind the first", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "56dp targets, couriers wear gloves", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "tool state tint fails contrast", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "エラーのトーストが3秒で消えます", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "ja"} -{"prompt": "late orders are red only", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"} -{"prompt": "ribbon can't be reached by keyboard", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "map keeps the screen awake", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "focus doesn't return after a dialog", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "filter lists from one template", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "pull save/recovery out of Document", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "un seul module pour le scoring", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "fr"} -{"prompt": "`ready_at` naming across contexts", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "extract the offer loop from assign", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "inline `zone_affinity`, one caller", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "context boundaries in the elixir app", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "changelog for modeller 4.2", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "nota para os restaurantes sobre o incidente", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "pt"} -{"prompt": "summarise the durability proposal", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "PR body for the autosave fix", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "which descriptor wins on a match?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "¿el undo libera geometría compartida?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "es"} -{"prompt": "can retries make an outage worse?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "walk me through offer acceptance", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "undo crashes on large assemblies", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "one upstream 503s while healthy", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "warum verdoppeln sich Zuweisungen beim Deploy?", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "de"} -{"prompt": "endpoint for a zone's dispatch backlog", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "dispatch thing", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "crack on", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "fewer pages tonight", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "lo del gateway, continúa", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "es"} -{"prompt": "that CAD thing again", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "straighten it out", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "as we discussed", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "doc for legal", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "nothing risky today", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "eyes on this one", "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": "pick something up", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "zone dispatcher holds in-flight assignments in memory, is registered with :global, and loses everything it was holding on a restart, which during rolling deploys has produced both dropped assignments and duplicated ones. i want the options for making that state durable worked through properly — postgres-backed with the process as a cache, a distributed registry, or something else — with the twenty second offer window and the dinner-peak database load as the constraints that actually bind", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "autosave truncating in place has now cost us two enterprise renewals and the fix is obviously write-and-rename, but the wider question is what our data-durability story should be — backup chains, crash recovery, what we promise a customer whose laptop dies mid-save. i'd like that written down as a position before we patch the one function everyone is angry about", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "couriers stop publishing location when their phone goes into doze, which is most of an evening shift, and our current answer is a foreground service that android increasingly ignores. i want the realistic options — platform APIs we're not using, batching with the geofence API, accepting lower resolution — with the impact on dispatch quality for each", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "document class in the modeller owns geometry, undo, selection, saving and the plugin surface, and every one of those has needed changing this quarter. before anyone splits it i'd like agreement on what the pieces are and in what order they move, because a half-finished split is worse than the current mess", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "en"} -{"prompt": "four customers write plugins against a header file and a hope, and the behaviours that bite them — UI-thread callbacks, invalidated document pointers, silently ignored version mismatches — are exactly the ones we've never written down. write the plugin developer guide covering the lifecycle, the threading rules and the failure modes the sooner we know roughly how big this is, the better for planning.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "gateway's operator guide describes a single cluster from three years ago, while today routes come from git, rate limits from a repo owned by another team with no validation, and four of our defaults are actively dangerous. write the current guide and mark those defaults clearly rather than burying them in a table this has come up in three separate reviews now and never gets done.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "nobody can tell me what the boolean undo actually frees, given that the union result shares face pointers with its operands and the geometry library documents itself as \"may reference input geometry\". read the command, the shape destructor and the library's ownership rules together and tell me exactly what is double-freed and when", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "rate limit configuration has three descriptors that can all match one request, our documentation says the most specific wins, and the observed behaviour suggests all of them apply. work out what the implementation really does, including the nested descriptor case, before i tell a partner their limit is what they think it is flag anything you'd want to change before doing it rather than after.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "order state machine's design doc promises an append-only log as the source of truth and a socket that delivers every transition in order, and i believe neither is true any more. go through the doc claim by claim against the code, including the handoff state we added in march there's no rush on this week specifically, but it keeps costing us time.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "three modules decide whether a courier is available and they disagree about stacked deliveries, staleness and the two-assignment limit, which is why support and dispatch tell couriers different things. consolidate onto one predicate, with the stacking rules as the reference behaviour, and list which couriers become newly eligible or ineligible as a result the last person who touched this left, so there's nobody to ask.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "gateway filter chains are maintained by hand in four route files and the legacy one is missing request_id, which is why legacy traces are useless. generate the chains from one declaration with per-route exceptions, keeping the applied configuration byte-identical for the three routes that are currently correct we've been burned by guessing at this before, so evidence over instinct please.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "active delivery screen has to work one-handed, with gloves, on a phone that's about to die, while the courier is walking. build it to the spec — slide to confirm, queued actions when offline, no screen wake-lock — and tell me which parts of the current screen actively fight those constraints", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "before we make dispatcher state durable i want the design agreed — what's authoritative, what the process caches, how a handover works mid-offer — and then the assignment write path implemented against it so we can measure the latency cost at peak a rough ordering matters more to me than a complete answer right now.", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.9, "slice": "mixed", "lang": "en"} -{"prompt": "opening-hours API needs to go from beta to something we'd sign a contract on, which is a design question about propagation guarantees before it's an implementation. settle the semantics with me, then build the write path and the dispatch invalidation this is the third time it's bitten us and i'd like it to be the last.", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "das Dokument-Objekt im Modeller macht alles gleichzeitig und blockiert jede weitere Änderung. Ich hätte gern zuerst einen Schnittplan, welche Verantwortlichkeiten wohin gehen, und danach die Herauslösung des Speicher- und Wiederherstellungsteils", "purpose": "planning", "secondary": "refactor", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "de"} -{"prompt": "retry policy needs a per-route-class design rather than one global default, and the payments route needs fixing today regardless. give me the design, then turn retries off for the non-idempotent routes as the immediate step", "purpose": "planning", "secondary": "quickFix", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "courier API reference has to exist before the second partner fleet integrates, and while writing it please confirm whether location updates faster than 1 Hz are really dropped silently rather than rejected", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "plugin guide needs writing and i expect it will surface at least two behaviours we should change rather than document — the silent version mismatch being the obvious one. write the guide, and give me that list separately", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "escribe el documento de decisión sobre los límites de tasa y comprueba en el código qué descriptor gana realmente cuando varios coinciden, porque la documentación y el comportamiento no coinciden", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "es"} -{"prompt": "on-call runbook for dispatch should be a page rather than folklore, and the redis restart that wipes every courier location deserves a guard rather than a warning. write the runbook, then add the confirmation prompt", "purpose": "writing", "secondary": "quickFix", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "elixir contexts need boundaries and the admin tool's :sys.replace_state call needs to stop existing. restructure the boundaries, and tell me what the admin tool actually needed that it couldn't get through a proper API", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "file references should resolve by content id before falling back to paths, which fixes cross-platform assemblies. make the change, and write the note for customers explaining why files saved before 4.0 still need the manual fix", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "mTLS added forty milliseconds at p50 and far more at p99, and the handshake count suggests we're not reusing connections at all. diagnose it properly, then fix the pooling configuration so we get the security without the latency", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "app shows stale order status for about a minute after delivery, which correlates with socket reconnects. confirm the mechanism, then change the reconnect path to reconcile against the current state rather than replaying from the client's last event", "purpose": "debugging", "secondary": "frontendImpl", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "redis filled up on friday and dispatch stopped, because our eviction policy is noeviction and we mix ephemeral locations with state we can't lose. work out what's actually in there, then split the workloads so a location flood can't take dispatch down whatever you find, write it somewhere the next person will actually look.", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "modeller fails a government customer's accessibility review on seven counts including a viewport with no keyboard selection at all. work through them, and write the remediation plan with dates that we can actually send", "purpose": "frontendImpl", "secondary": "writing", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "flutter app stores auth tokens in three places and refreshes them in two", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "rename the `Assignment` struct in dispatch, it means something different in billing", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "qt widgets subclass a base that reimplements half of QWidget's event handling", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "could you explain what happens to an accepted order when the restaurant closes afterwards", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "why does the courier app's location publisher stop when the screen locks", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "someone should check whether a partner can exceed their limit by spreading requests across endpoints", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "is it expected that a plugin returning true from onCommand suppresses our own built-in command", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "pouvez-vous m'expliquer comment le cache des restaurants est rafraîchi, et pourquoi toutes les cinq minutes ?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "fr"} -{"prompt": "docs/dispatch.md describes a two-stage assignment we replaced with scoring last year", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "header comments on IPlugin promise thread safety that the UI callbacks don't have", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "write the customer note about the minimum OS versions changing in 4.2", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "how should we shard dispatch when a city grows past what one zone process can handle", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "what's the right way to test dispatch, where the failure mode is a courier standing outside a closed door", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "i want a position on whether the modeller should move to a document format that supports partial loading", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "two partner fleets want to run their own dispatch and use us only for orders, what would that even mean", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "we need a plan for the modeller's plugin API now that four customers depend on undocumented behaviour", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "what should happen to in-flight orders when we take a zone offline for a deploy", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "an endpoint that returns why a specific order was assigned to a specific courier, for support", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "location endpoint should reject rather than silently drop updates faster than 1 Hz", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "restaurant dashboard needs a late-order strip that survives being watched on a wall screen all day", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "assembly tree should virtualise, a 41-part assembly currently renders every node eagerly", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "route inspector needs to work when the control plane is down, from the last known config", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "whatever keeps dinner service running", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "next piece of the gateway work", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "envoy filters reach us through static yaml, the control plane and one hand-edited bootstrap that predates both, which means the effective configuration is genuinely unknown. bring them onto one path, and produce the diff between what we thought was applied and what actually is i'm not attached to the current approach if there's an obviously better one.", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "i'd like an honest read on whether our append-only order event log can be trusted as a source of truth, given that the admin tool updates rows directly to fix data, and the fix if it can't — including what to do about the rows already edited i'd rather have the reasoning written down than a quick answer.", "purpose": "review", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "assignments need an idempotency key so that a retried offer response can't produce a second assignment, but the key's scope depends on whether we treat an offer or an order as the unit. decide that with me, then implement the write path and the conflict response tell me if this is the wrong shape entirely, i won't be offended.", "purpose": "backendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "the flutter app keeps auth tokens in secure storage, in a provider and in a module-level variable, refreshing them in two of the three, which is why couriers occasionally get logged out mid-shift. consolidate onto one owner with a single refresh path, and make sure a refresh that fails while the app is backgrounded doesn't silently sign someone out", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "our health endpoint reports the dispatcher as healthy when its zone has no couriers connected at all, which is exactly the state we most need to page on, and it also stays green when redis is refusing writes. make it check what actually matters, keep it cheap enough for a two-second interval, and tell me which existing alerts become redundant", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "staging runs four upstreams and production runs forty-one behind identical connection pool and circuit breaker settings, which is why load-related failures never appear before release. bring the staging numbers into a sensible relationship with production, and note which settings are genuinely per-upstream rather than global so we don't scale the wrong ones", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "a city has grown past what one zone process can handle at dinner peak and the obvious answer is more zones, except that our zones are geographic and couriers cross them constantly. i'd like the options for sharding dispatch worked through — smaller zones with handoff, sharding by order rather than geography, or splitting the process differently — with the cross-zone courier case as the thing that decides it", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "per-partner circuit breaking doesn't exist in our gateway, so one slow partner consumes the shared connection pool and everyone's requests queue behind theirs. add breakers scoped per partner with sensible defaults, expose the state so support can see who is tripped, and make sure a tripped breaker fails fast with a distinguishable status rather than a generic 503", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "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_51155'\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_51155'::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 KeystoneBirchMigratorCoordinator 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":"KeystoneSummitProxyCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Read projects/keystone/engine/render/atlas.cpp and tell me whether KeystoneDeltaCanvasService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating an empty state that flashes before cached data arrives in KeystoneLumenChartStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"// projects/keystone/ui/settings/PrivacyPane.tsx\nfinal class KeystoneFlintTimelineCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 KeystoneFlintTimelineCoordinator; 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":"KeystoneOspreyJobCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"KeystoneAsterWebhookCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"A flaky failure around KeystoneBasilRunnerService survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneBasilRunnerService\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":"planning","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"PM needs a concise migration note for KeystonePrismCacheStore, 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":"KeystoneDeltaCanvasCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Our support and SDK teams keep answering the same questions about KeystoneBirchMigratorService, but the current prose in projects/keystone/app/src/main/SyncWorker.kt only describes the happy path. 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- keep public behavior and serialized data unchanged\n- stay compatible with the existing gRPC deployment\n- keep the work scoped to KeystoneBirchMigratorService and its direct tests\n\nSeveral teams work in this collaboration, C++, Next.js monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Move KeystoneAmberFilterService behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"UI ticket DES-51159: finish the compact KeystoneWillowCodecCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/keystone/cmd/exporter/main.py\nFramework: FastAPI\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 KeystoneWillowCodecCoordinator'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":"KeystoneBirchMigratorStore returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/keystone/apps/console/routes/usage.svelte and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Could KeystoneFernSnapshotService migrate incrementally?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"projects/keystone/pkg/cache/lease.rs has grown through several launches, and KeystoneEmberRelayService now mixes policy, transport, persistence, and metrics in one place. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing Room deployment\n- keep the work scoped to KeystoneEmberRelayService and its direct tests\n\nSeveral teams work in this collaboration, C++, Next.js monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Two deliverables are holding up KeystoneMarbleTokenCoordinator. First, assess ownership and failure handling in projects/keystone/app/src/main/SyncWorker.kt. In the same workstream, capture the contract and rollback note for consumers. The relevant starting point is projects/keystone/app/src/main/SyncWorker.kt, which follows gRPC conventions and currently suffers from out-of-order events after consumer rebalancing. Keep public behavior and serialized data unchanged.\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":"review","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Stream KeystoneOrbitSyncService's audit events","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Extract KeystoneAcornWidgetService's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Kestrel: # projects/keystone/workers/thumbnail/consumer.ex\n[worker.keystoneorbitsyncflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystoneorbitsyncflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystoneorbitsyncflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneOrbitSyncFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51121\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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Make the one confirmed configuration correction in projects/keystone/workers/thumbnail/consumer.ex. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Lumen: # projects/keystone/crates/index/src/segment.rs\n[worker.keystonecloudreconcilerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystonecloudreconcilerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystonecloudreconcilerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneCloudReconcilerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51138\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 KeystoneCloudReconcilerFlow'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":"Please resist widening this one: KeystoneKiteSchedulerService works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneKiteSchedulerService\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Before we approve KeystoneCopperBridgeService, assess whether a deadlock that appears only during shutdown is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"How does KeystoneCinderAuthStore propagate cancellation through the Room boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Walk through KeystoneMarbleTokenService's usage.svelte","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Sequence KeystoneJuniperCLIService's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Document KeystoneCoralUploadStore's cancellation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Maple: Two asks around KeystoneQuartzPlayerCoordinator: (1) separate KeystoneQuartzPlayerCoordinator's policy from transport without behavior changes; (2) correct the known stale timeout beside it. Keep public behavior and serialized data unchanged, and leave a clear boundary between the resulting artifacts or edits.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Nimbus: The public surface of KeystoneFlintTimelineService is frozen, but its internal ownership in projects/keystone/workers/thumbnail/consumer.ex is difficult to test and even harder to change safely. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneFlintTimelineService\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Fresh release brief for KeystoneKiteSchedulerCoordinator:\n- primary outcome: produce a consumer guide for KeystoneKiteSchedulerCoordinator\n- companion outcome: give the existing implementation a read-only safety pass\n- repository entry point: projects/keystone/config/staging.toml\n- platform constraint: Room\n- known complication: a feature flag whose default differs between environments\n\nBoth results are required, but they should remain independently reviewable. Keep public behavior and serialized data unchanged; 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":"writing","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Summarize the KeystoneBeaconStoreStore changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"For KeystoneAcornWidgetCoordinator, change KeystoneAcornWidgetCoordinator's known staging timeout from 15 to 30 seconds; once that is complete, capture the contract and rollback note for consumers. Work from projects/keystone/apps/console/routes/usage.svelte, stay with gRPC, and keep public behavior and serialized data unchanged. Keep the two outcomes separately reviewable.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"KeystoneOpalRouterCoordinator: sort out the rough edge","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating a deadlock that appears only during shutdown in KeystoneRainfallDBStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"KeystoneBeaconStoreCoordinator: diagnose, then correct","purpose":"debugging","secondary":"quickFix","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Sketch the KeystoneLedgerGateService migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Opal: # projects/keystone/internal/auth/refresh.go\n[worker.keystonepinemetricsflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystonepinemetricsflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystonepinemetricsflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystonePineMetricsFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51132\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 KeystonePineMetricsFlow'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":"Prism: projects/keystone/apps/console/routes/usage.svelte 里的 KeystoneHarborIndexService 最近在 gRPC 流程中出现间歇性问题。 原因已经明确：只把 staging timeout 从 15 秒改成 30 秒，并调整对应 assertion。\n\n约束：\n- 继续使用 gRPC\n- 保持兼容性和取消语义\n- 改动只限于 KeystoneHarborIndexService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"zh"} +{"prompt":"What is the safest way to split projects/keystone/web/components/FilterDrawer.vue into independently owned modules while KeystoneGarnetModalService's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Milestones for replacing KeystoneAtlasSearchStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"KeystoneIrisBatchCoordinator: polish, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Ticket OPS-51120: retire the legacy replay path for KeystoneAmberFilterFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for KeystoneAmberFilterFlow, 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":"For KeystoneSlateEditorCoordinator, produce a consumer guide for KeystoneSlateEditorCoordinator; once that is complete, give the existing implementation a read-only safety pass. Work from projects/keystone/crates/index/src/segment.rs, stay with Room, and keep public behavior and serialized data unchanged. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Sketch the KeystoneVelaDrawerService migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Add a bounded KeystoneRavenSessionStore export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-51143: finish the compact KeystoneOspreyJobFlow filter experience\n\nRoute: /catalog/search\nSource: projects/keystone/config/staging.toml\nFramework: Room\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 KeystoneOspreyJobFlow 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":"Before touching projects/keystone/Sources/CLI/Commands/Doctor.swift, 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":"Ticket OPS-51110: retire the legacy replay path for KeystoneEchoRegistryFlow\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 KeystoneEchoRegistryFlow 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":"Animate the KeystoneCedarPolicyService drawer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"KeystoneFrostPanelCoordinator needs a paired pass: assess ownership and failure handling in projects/keystone/services/ledger/replay.go, plus capture the contract and rollback note for consumers. Use projects/keystone/services/ledger/replay.go as the source of truth, preserve the Swift 6 contract, and avoid unrelated cleanup.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Memory attributed to KeystoneCopperBridgeStore rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-51131\n\n08:02 deploy KeystoneJuniperCLIFlow 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 KeystoneJuniperCLIFlow 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":"Quartz: // projects/keystone/internal/auth/refresh.go\nfinal class KeystoneMapleQueueFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 KeystoneMapleQueueFlow; 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":"KeystoneCoralUploadCoordinator: restructure, then correct","purpose":"refactor","secondary":"backendImpl","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Security flagged KeystoneKiteSchedulerStore for a read-only pass because its Room boundary mixes tenant data, retries, and cancellation in subtle ways. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current Room operational envelope\n\nThe relevant code crosses collaboration, C++, Next.js. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"KeystoneAtlasSearchService leaks tasks on shutdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Split projects/keystone/cmd/exporter/main.py by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Is KeystoneAmberFilterStore safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"KeystoneMoonlitSDKCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"# projects/keystone/internal/auth/refresh.go\n[worker.keystonemicaprofilecoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystonemicaprofilecoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystonemicaprofilecoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneMicaProfileCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51152\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/keystone/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":"Raven: Ticket OPS-51116: retire the legacy replay path for KeystoneSummitProxyFlow\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 KeystoneSummitProxyFlow 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":"KeystoneWillowCodecFlow returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/keystone/ml/pipeline/features.py and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"On compact widths, KeystoneMicaProfileStore'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":"Sable: Ticket OPS-51156: retire the legacy replay path for KeystoneSpruceDaemonCoordinator\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\nWire KeystoneSpruceDaemonCoordinator'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.8,"slice":"pasted-context","lang":"en"} +{"prompt":"One contained cleanup in projects/keystone/workers/thumbnail/consumer.ex: remove the obsolete KeystoneOpalRouterService import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-51135: finish the compact KeystoneHarborIndexFlow filter experience\n\nRoute: /catalog/search\nSource: projects/keystone/apps/console/routes/usage.svelte\nFramework: gRPC\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 KeystoneHarborIndexFlow'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":"Move KeystoneGarnetModalStore's clock and ID generation behind the existing environment type so tests no longer reach global state; outputs and scheduling order must stay identical. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/keystone/engine/render/atlas.cpp b/projects/keystone/engine/render/atlas.cpp\nindex 62d71aa..90f3c1e 100644\n--- a/projects/keystone/engine/render/atlas.cpp\n+++ b/projects/keystone/engine/render/atlas.cpp\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure KeystoneDeltaCanvasFlow 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":"The behavior of KeystoneWillowCodecService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/keystone/ml/pipeline/features.py. 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- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current FastAPI operational envelope\n\nThe relevant code crosses collaboration, C++, Next.js. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Bring KeystoneFlintTimelineStore'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.5,"slice":"core","lang":"en"} +{"prompt":"The destination for KeystoneLumenChartService is broadly agreed; the missing piece is a reversible route from projects/keystone/Sources/CLI/Commands/Doctor.swift to that target. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneLumenChartService\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"KeystoneCopperBridgeCoordinator: ship a sensible version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"KeystoneSableParserCoordinator: handle the lingering thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Tide: The destination for KeystoneEmberRelayStore is broadly agreed; the missing piece is a reversible route from projects/keystone/crates/index/src/segment.rs to that target. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneEmberRelayStore\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Two asks around KeystonePineMetricsCoordinator: (1) finish KeystonePineMetricsCoordinator's responsive empty and retry states; (2) capture the contract and rollback note for consumers. Keep public behavior and serialized data unchanged, and leave a clear boundary between the resulting artifacts or edits.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Test Suite 'KeystoneMoonlitSDKFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[KeystoneMoonlitSDKFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/keystone/pkg/cache/lease.rs:144: error: -[KeystoneMoonlitSDKFlowTests 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 '-[KeystoneMoonlitSDKFlowTests 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 KeystoneMoonlitSDKFlow's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Documente le contrat KeystoneFrostPanelStore","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"fr"} +{"prompt":"What sequence would let KeystoneSableParserService adopt gRPC with dual reads but no dual writes? Include data validation, canary scope, and the decision that ends compatibility mode.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Walk through KeystoneFernSnapshotStore's main.py","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Does KeystoneQuartzPlayerService preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Teach KeystoneCinderAuthFlow to verify signed continuation tokens, reject cross-tenant cursors, and rotate keys without invalidating tokens issued during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Memory attributed to KeystoneLumenChartFlow rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"// projects/keystone/web/components/FilterDrawer.vue\nfinal class KeystoneFrostPanelFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 KeystoneFrostPanelFlow 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":"Three teams extended KeystoneEchoRegistryStore independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current gRPC operational envelope\n\nThe relevant code crosses collaboration, C++, Next.js. Prefer evidence from the repository and make any assumption explicit.\n\nThe individual edits look tiny, but the semantic cleanup spans the repository and must preserve behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Three teams extended KeystoneSpruceDaemonService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current OpenTelemetry operational envelope\n\nThe relevant code crosses collaboration, C++, Next.js. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"KeystoneRainfallDBService's staging timeout is already known to be wrong: change the single projects/keystone/Sources/App/SessionStore.swift value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"KeystoneSlateEditorService flakes under UTC","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"2026-07-30T08:14:11.409Z level=info service=keystonemosaicgridflow pod=keystonemosaicgridflow-7cf8 request_id=51117 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=keystonemosaicgridflow request_id=51117 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=keystonemosaicgridflow request_id=51117 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=keystonemosaicgridflow request_id=51117 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=keystonemosaicgridflow request_id=51117 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=keystonemosaicgridflow request_id=51117 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=keystonemosaicgridflow request_id=51117 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=keystonemosaicgridflow request_id=51117 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nReconstruct the KeystoneMosaicGridFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"KeystoneNovaPickerCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-51119\n\n08:02 deploy KeystoneIrisBatchFlow 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 KeystoneIrisBatchFlow 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":"Umbra: // projects/keystone/ui/settings/PrivacyPane.tsx\nfinal class KeystoneDriftConsoleFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 KeystoneDriftConsoleFlow'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":"Zentriere das KeystoneIrisBatchStore-Modal","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"de"} +{"prompt":"KeystonePrismCacheCoordinator: give it a nicer flow","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Vela: # projects/keystone/services/ledger/replay.go\n[worker.keystonebasilrunnercoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystonebasilrunnercoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystonebasilrunnercoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneBasilRunnerCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51157\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/keystone/services/ledger/replay.go. 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":"Willow: # projects/keystone/app/src/main/SyncWorker.kt\n[worker.keystoneacornwidgetflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystoneacornwidgetflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystoneacornwidgetflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneAcornWidgetFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51125\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/keystone/app/src/main/SyncWorker.kt and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"KeystoneAtlasSearchCoordinator: diagnose, then assess","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Fresh release brief for KeystoneEchoRegistryCoordinator:\n- primary outcome: separate KeystoneEchoRegistryCoordinator's policy from transport without behavior changes\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/keystone/src/sync/reconcile.ts\n- platform constraint: gRPC\n- known complication: a misleading timeout name used in five packages\n\nBoth results are required, but they should remain independently reviewable. Keep public behavior and serialized data unchanged; 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":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"UI ticket DES-51149: finish the compact KeystoneNimbusFormFlow filter experience\n\nRoute: /catalog/search\nSource: projects/keystone/ml/pipeline/features.py\nFramework: FastAPI\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 KeystoneNimbusFormFlow 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":"How does KeystoneSableParserStore propagate cancellation through the gRPC boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Two asks around KeystoneFernSnapshotCoordinator: (1) find the unknown cause of a feature flag whose default differs between environments; (2) capture the contract and rollback note for consumers. Keep public behavior and serialized data unchanged, and leave a clear boundary between the resulting artifacts or edits.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"A flaky failure around KeystoneVelaDrawerStore survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneVelaDrawerStore\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Add a bounded KeystoneCloudReconcilerService export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Ownership of KeystoneRavenSessionService is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current gRPC operational envelope\n\nThe relevant code crosses collaboration, C++, Next.js. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Support wants the behavior in projects/keystone/ml/pipeline/features.py recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Style KeystonePineMetricsStore's offline state","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Documente o contrato de KeystoneFrostPanelService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"pt"} +{"prompt":"Ticket OPS-51154: retire the legacy replay path for KeystoneLumenChartCoordinator\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 KeystoneLumenChartCoordinator behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Xylem: UI ticket DES-51133: finish the compact KeystoneCedarPolicyFlow filter experience\n\nRoute: /catalog/search\nSource: projects/keystone/packages/api/openapi.yaml\nFramework: Room\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring KeystoneCedarPolicyFlow'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":"KeystoneNovaPickerStore has four wrappers that only translate the same error enum. Collapse them into one adapter and preserve every public case, message, and metric label. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"KeystoneCedarPolicyCoordinator needs a paired pass: separate KeystoneCedarPolicyCoordinator's policy from transport without behavior changes, plus give the existing implementation a read-only safety pass. Use projects/keystone/config/staging.toml as the source of truth, preserve the Room contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Center the KeystoneSlateEditorStore modal","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Yarrow: UI ticket DES-51141: finish the compact KeystoneOpalRouterFlow filter experience\n\nRoute: /catalog/search\nSource: projects/keystone/workers/thumbnail/consumer.ex\nFramework: OpenTelemetry\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 KeystoneOpalRouterFlow'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":"KeystoneSpruceDaemonFlow needs an idempotent replay endpoint backed by OpenTelemetry; accept a cursor, cap each page at 500 items, and return a stable continuation token.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Could the reasoning behind KeystoneTideWorkerStore's gRPC choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"KeystoneOrbitSyncCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"KeystoneNimbusFormCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"KeystoneOrbitSyncStore's PrivacyPane.tsx needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"// projects/keystone/lib/codec/frame.cc\nfinal class KeystoneCopperBridgeFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 KeystoneCopperBridgeFlow; 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":"Security flagged KeystoneSummitProxyStore for a read-only pass because its OpenTelemetry boundary mixes tenant data, retries, and cancellation in subtle ways. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current OpenTelemetry operational envelope\n\nThe relevant code crosses collaboration, C++, Next.js. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-51118: retire the legacy replay path for KeystoneAtlasSearchFlow\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 KeystoneAtlasSearchFlow 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":"Introduce a durable deduplication key for KeystoneNovaPickerService 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":"KeystoneCoralUploadService's staging.toml needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"The KeystoneMicaProfileFlow 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":"Match KeystoneLedgerGateStore's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/keystone/Sources/CLI/Commands/Doctor.swift b/projects/keystone/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/keystone/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/keystone/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate KeystonePrismCacheFlow'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":"KeystoneRavenSessionFlow's staging timeout is already known to be wrong: change the single projects/keystone/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":"KeystoneHarborIndexCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"PM needs a concise migration note for KeystoneTideWorkerService, 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":"KeystoneLedgerGateCoordinator needs a paired pass: separate KeystoneLedgerGateCoordinator's policy from transport without behavior changes, plus give the existing implementation a read-only safety pass. Use projects/keystone/src/sync/reconcile.ts as the source of truth, preserve the gRPC contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"In projects/keystone/ui/settings/PrivacyPane.tsx hat KeystoneDriftConsoleService ein sporadisches Problem im OpenTelemetry-Ablauf. Die Ursache ist klar: Ändere nur das Staging-Timeout von 15 auf 30 Sekunden und passe die Assertion an.\n\nRandbedingungen:\n- OpenTelemetry weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf KeystoneDriftConsoleService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um KeystoneDriftConsoleService mit OpenTelemetry kompatibel.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"de"} +{"prompt":"The data is already available in projects/keystone/lib/codec/frame.cc; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Zephyr: # projects/keystone/src/sync/reconcile.ts\n[worker.keystonetideworkerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystonetideworkerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystonetideworkerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneTideWorkerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51140\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/keystone/src/sync/reconcile.ts and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Checkout: The KeystoneEmberRelayFlow 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":"KeystoneAmberFilterCoordinator: restructure, then correct","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Is KeystoneBeaconStoreService safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"For KeystoneJuniperCLICoordinator, produce a consumer guide for KeystoneJuniperCLICoordinator; once that is complete, give the existing implementation a read-only safety pass. Work from projects/keystone/workers/thumbnail/consumer.ex, stay with OpenTelemetry, and keep public behavior and serialized data unchanged. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"En projects/keystone/workers/thumbnail/consumer.ex, KeystoneDriftConsoleStore tiene un problema intermitente en el flujo de OpenTelemetry. Sigue queue, scheduler y cancelación, compara hipótesis y encuentra la causa antes de proponer cambios.\n\nRestricciones:\n- seguir con OpenTelemetry\n- conservar compatibilidad y cancelación\n- limitar el cambio a KeystoneDriftConsoleStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con OpenTelemetry alrededor de KeystoneDriftConsoleStore.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"es"} +{"prompt":"projects/keystone/packages/api/openapi.yaml 里的 KeystoneOspreyJobStore 最近在 Room 流程中出现间歇性问题。 请拆分职责并去掉重复，同时保持 API、wire value、顺序和可观察行为不变。\n\n约束：\n- 继续使用 Room\n- 保持兼容性和取消语义\n- 改动只限于 KeystoneOspreyJobStore","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"Where did KeystoneCedarPolicyStore's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Pin KeystoneMosaicGridService's Swift dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-51115\n\n08:02 deploy KeystoneMarbleTokenFlow 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\nFind the source of this KeystoneMarbleTokenFlow symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Split projects/keystone/web/components/FilterDrawer.vue by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"thread 'tokio-runtime-worker' panicked at projects/keystone/packages/api/openapi.yaml:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: keystonecinderauthcoordinator::scheduler::LeaseTask::flush\n at ./projects/keystone/packages/api/openapi.yaml:217:18\n 4: keystonecinderauthcoordinator::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Reconstruct the KeystoneCinderAuthCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Exporter: # projects/keystone/Sources/CLI/Commands/Doctor.swift\n[worker.keystonewrenexportflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystonewrenexportflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystonewrenexportflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneWrenExportFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51124\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/keystone/Sources/CLI/Commands/Doctor.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":"Does KeystoneMoonlitSDKStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Scheduler: // projects/keystone/cmd/exporter/main.py\nfinal class KeystoneCraneWorkspaceFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 KeystoneCraneWorkspaceFlow 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":"Dashboard: projects/keystone/infra/modules/edge/main.tf has grown through several launches, and KeystoneMapleQueueStore now mixes policy, transport, persistence, and metrics in one place. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing Swift 6 deployment\n- keep the work scoped to KeystoneMapleQueueStore and its direct tests\n\nSeveral teams work in this collaboration, C++, Next.js monorepo, so keep ownership and handoff points understandable in a small review.\n\nThe individual edits look tiny, but the semantic cleanup spans the repository and must preserve behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/keystone/crates/index/src/segment.rs b/projects/keystone/crates/index/src/segment.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/keystone/crates/index/src/segment.rs\n+++ b/projects/keystone/crates/index/src/segment.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure KeystoneEmberRelayCoordinator 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Worker: diff --git a/projects/keystone/pkg/cache/lease.rs b/projects/keystone/pkg/cache/lease.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/keystone/pkg/cache/lease.rs\n+++ b/projects/keystone/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\nRestructure KeystoneSlateEditorFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Introduce a durable deduplication key for KeystoneDeltaCanvasStore events and enforce it in both the database migration and the ingestion path.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Simulator: The KeystoneBasilRunnerFlow empty state in projects/keystone/web/components/FilterDrawer.vue needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Two deliverables are holding up KeystoneMapleQueueCoordinator. First, produce a consumer guide for KeystoneMapleQueueCoordinator. In the same workstream, correct the known stale timeout beside it. The relevant starting point is projects/keystone/infra/modules/edge/main.tf, which follows Swift 6 conventions and currently suffers from cancellation being swallowed at the repository boundary. Keep public behavior and serialized data unchanged.\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":"writing","secondary":"quickFix","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"PM needs a concise migration note for KeystoneCloudReconcilerStore, 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":"We expect KeystoneWillowCodecStore to outgrow its current FastAPI arrangement next quarter, but changing everything at once would be risky. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing FastAPI deployment\n- keep the work scoped to KeystoneWillowCodecStore and its direct tests\n\nSeveral teams work in this collaboration, C++, Next.js monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Check KeystonePineMetricsService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"KeystoneTideWorkerCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-51123\n\n08:02 deploy KeystoneCoralUploadFlow 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 KeystoneCoralUploadFlow, 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":"Ticket OPS-51126: retire the legacy replay path for KeystoneQuartzPlayerFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for KeystoneQuartzPlayerFlow, 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":"KeystoneGarnetModalCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Runbook: Ticket OPS-51114: retire the legacy replay path for KeystoneVelaDrawerFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for KeystoneVelaDrawerFlow, 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":"Compare the old and new KeystoneCraneWorkspaceService adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"How should KeystoneSummitProxyService be decomposed?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Give KeystoneAsterWebhookService'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":"KeystoneRainfallDBCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Trace: Incident timeline — INC-51113\n\n08:02 deploy KeystoneKiteSchedulerFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Turn the material above into a concise KeystoneKiteSchedulerFlow 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":"Test Suite 'KeystoneRainfallDBFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[KeystoneRainfallDBFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/keystone/Sources/App/SessionStore.swift:144: error: -[KeystoneRainfallDBFlowTests 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 '-[KeystoneRainfallDBFlowTests 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\nFinish the visible KeystoneRainfallDBFlow 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":"Profiler: PM is preparing the KeystoneEchoRegistryService rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneEchoRegistryService\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Assess the KeystoneAcornWidgetStore diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"projects/keystone/workers/thumbnail/consumer.ex の KeystoneFlintTimelineFlow で、OpenTelemetry の flow に断続的な問題が起きています。 原因は判明済みです。staging timeout だけを 15 秒から 30 秒へ変え、対応する assertion を直してください。\n\n制約:\n- OpenTelemetry を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は KeystoneFlintTimelineFlow のみ","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"ja"} +{"prompt":"Console: diff --git a/projects/keystone/db/migrations/20260730_events.sql b/projects/keystone/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/keystone/db/migrations/20260730_events.sql\n+++ b/projects/keystone/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit KeystoneLedgerGateFlow 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":"How does KeystoneCraneWorkspaceStore propagate cancellation through the FastAPI boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Workspace: // projects/keystone/app/src/main/SyncWorker.kt\nfinal class KeystoneSableParserFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Split KeystoneSableParserFlow 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":"The KeystoneMoonlitSDKService 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":"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_51122'\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_51122'::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\nDeliver the KeystoneBeaconStoreFlow server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"KeystoneWrenExportCoordinator needs a paired pass: assess ownership and failure handling in projects/keystone/Sources/App/SessionStore.swift, plus capture the contract and rollback note for consumers. Use projects/keystone/Sources/App/SessionStore.swift as the source of truth, preserve the FastAPI contract, and avoid unrelated cleanup.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"En projects/keystone/config/staging.toml, KeystoneCinderAuthService tiene un problema intermitente en el flujo de Room. Redacta una guía para consumidores con contrato, errores, retry y un ejemplo copiable; no cambies el handler.\n\nRestricciones:\n- seguir con Room\n- conservar compatibilidad y cancelación\n- limitar el cambio a KeystoneCinderAuthService Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con Room alrededor de KeystoneCinderAuthService.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"es"} +{"prompt":"Repository: # projects/keystone/ml/pipeline/features.py\n[worker.keystonefernsnapshotflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.keystonefernsnapshotflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.keystonefernsnapshotflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.KeystoneFernSnapshotFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-51129\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Align KeystoneFernSnapshotFlow'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":"Pipeline: Incident timeline — INC-51137\n\n08:02 deploy KeystoneAsterWebhookFlow 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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Turn the material above into a concise KeystoneAsterWebhookFlow release note and operator runbook section. State impact, detection, rollback, and the client-visible contract; do not modify code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"} +{"prompt":"KeystoneDriftConsoleCoordinator is blocking the next release because stale cursors when a page is resumed. I need two concrete outcomes from a single pass: change KeystoneDriftConsoleCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing OpenTelemetry conventions in projects/keystone/workers/thumbnail/consumer.ex; keep public behavior and serialized data unchanged. 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.5,"slice":"mixed","lang":"en"} +{"prompt":"Gateway: The behavior of KeystoneMapleQueueService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/keystone/internal/auth/refresh.go. 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- touch generated artifacts only through their checked-in generator\n- keep public behavior and serialized data unchanged\n- retain the current Swift 6 operational envelope\n\nThe relevant code crosses collaboration, C++, Next.js. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"This should remain a deliberately small patch: KeystoneMarbleTokenStore has one known configuration mistake in projects/keystone/app/src/main/SyncWorker.kt, not an open-ended failure investigation. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing gRPC deployment\n- keep the work scoped to KeystoneMarbleTokenStore and its direct tests\n\nSeveral teams work in this collaboration, C++, Next.js monorepo, so keep ownership and handoff points understandable in a small review.\n\nThe cause and exact value change are already known, so keep this as a contained correction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Renderer: Incident timeline — INC-51150\n\n08:02 deploy KeystoneRavenSessionCoordinator 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nReconstruct the KeystoneRavenSessionCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Does KeystoneWrenExportStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Pin KeystoneJuniperCLIStore's OpenTelemetry dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Give KeystoneOpalRouterStore'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.5,"slice":"core","lang":"en"} +{"prompt":"Em projects/keystone/app/src/main/SyncWorker.kt, o KeystoneHarborIndexStore tem um problema intermitente no fluxo de gRPC. Leia o fluxo atual e avalie ownership, cancelamento e ordem; preciso apenas da análise.\n\nRestrições:\n- continuar com gRPC\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao KeystoneHarborIndexStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"pt"} +{"prompt":"Split projects/keystone/app/src/main/SyncWorker.kt by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched. Although each edit is small, the semantic rename spans the whole repository.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Check KeystoneWrenExportService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"// projects/keystone/web/components/FilterDrawer.vue\nfinal class KeystoneGarnetModalFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 KeystoneGarnetModalFlow'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":"Translate the KeystoneQuartzPlayerStore setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current KeystoneMosaicGridStore design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside KeystoneMosaicGridStore\n- keep public behavior and serialized data unchanged\n\nThis repository spans collaboration, C++, Next.js; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"KeystoneCloudReconcilerCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Ticket OPS-51142: retire the legacy replay path for KeystoneNovaPickerFlow\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 KeystoneNovaPickerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"What sequence would let KeystoneBasilRunnerStore adopt Swift 6 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.8,"slice":"core","lang":"en"} +{"prompt":"We expect KeystoneMicaProfileService to outgrow its current Swift 6 arrangement next quarter, but changing everything at once would be risky. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- keep public behavior and serialized data unchanged\n- stay compatible with the existing Swift 6 deployment\n- keep the work scoped to KeystoneMicaProfileService and its direct tests\n\nSeveral teams work in this collaboration, C++, Next.js monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"KeystoneVelaDrawerCoordinator is blocking the next release because a deadlock that appears only during shutdown. I need two concrete outcomes from a single pass: change KeystoneVelaDrawerCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing FastAPI conventions in projects/keystone/Sources/CLI/Commands/Doctor.swift; keep public behavior and serialized data unchanged. 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.5,"slice":"mixed","lang":"en"} +{"prompt":"Centre la modale KeystoneIrisBatchService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"fr"} +{"prompt":"KeystoneCraneWorkspaceCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Indexer: projects/keystone/config/staging.toml の KeystoneOspreyJobService で、Room の flow に断続的な問題が起きています。 段階、互換性、metrics、rollback、ownership を提案し、コード変更の前で止めてください。\n\n制約:\n- Room を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は KeystoneOspreyJobService のみ","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"ja"} +{"prompt":"KeystoneMosaicGridCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} diff --git a/data/round2-12.jsonl b/data/round2-12.jsonl index 9f098c7..10e0fdd 100644 --- a/data/round2-12.jsonl +++ b/data/round2-12.jsonl @@ -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();\n r.material.color = hoverColor; // instantiates the material\n}\n\nvoid OnHoverExit(GameObject go) {\n var r = go.GetComponent();\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().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 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:dmarc@lumen.io; 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: notifications@mail.lumen.io", "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] = [:]\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] = [:]\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 \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] = [:]\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] = [:]\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] = [:]\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 \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] = [:]\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] = [:]\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] = [:]\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"} diff --git a/data/round2-13.jsonl b/data/round2-13.jsonl index 572b521..3d958a5 100644 --- a/data/round2-13.jsonl +++ b/data/round2-13.jsonl @@ -1,200 +1,200 @@ -{"prompt": "hub firmware updates brick about one device in two hundred:\n\nOTA log from a failed device (recovered over serial):\n [ota] downloading 4.2.1, 8,412,004 bytes\n [ota] verifying signature... ok\n [ota] writing slot B, 8,412,004 bytes\n [ota] write complete, crc ok\n [ota] setting boot flag to B\n [ota] rebooting\n [boot] slot B invalid magic, falling back to slot A\n [boot] slot A invalid magic\n [boot] no valid image, entering recovery\n\nthe boot flag write and the slot B write are on the same flash sector, and the erase before writing the flag wipes the last 4KB of the image", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "our prompt and schema for clause extraction, which i'd like a second opinion on:\n\nSCHEMA = {\n \"type\": \"object\",\n \"required\": [\"clauses\", \"governing_law\", \"termination_notice_days\"],\n \"properties\": {\n \"clauses\": {\"type\": \"array\", \"items\": {\"type\": \"object\", \"required\": [\"type\", \"text\", \"page\"]}},\n \"governing_law\": {\"type\": \"string\"},\n \"termination_notice_days\": {\"type\": \"integer\"}\n }\n}\n\nEXTRACT_PROMPT = \"Extract all clauses from the following contract. Return JSON matching the schema.\\n\\n{text}\"\n\ntermination_notice_days became required on monday; plenty of contracts don't state one; and the validator's repair loop is what runs when the model omits it", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "the hub's state handling is spread across three tasks with shared atomics:\n\nstatic LINK_DOWN: AtomicBool\nstatic MQTT_CONNECTED: AtomicBool\nstatic LAST_PUBLISH_OK: AtomicU64\nstatic OTA_IN_PROGRESS: AtomicBool\n\n// net task sets LINK_DOWN\n// mqtt task reads LINK_DOWN, sets MQTT_CONNECTED and LAST_PUBLISH_OK\n// ota task reads MQTT_CONNECTED, sets OTA_IN_PROGRESS\n// the watchdog reads all four and decides whether to reboot\n\nfour booleans encoding a state machine nobody has written down, and the watchdog's reboot decision is the most safety-relevant code we have\n\nfor reference, the watchdog:\n\nfn watchdog(state: &State) {\n let link = LINK_DOWN.load(Ordering::Relaxed);\n let mqtt = MQTT_CONNECTED.load(Ordering::Relaxed);\n let last = LAST_PUBLISH_OK.load(Ordering::Relaxed);\n let ota = OTA_IN_PROGRESS.load(Ordering::Relaxed);\n if !ota && !link && !mqtt && now_secs() - last > 900 {\n log::error!(\"watchdog: rebooting, no successful publish for 15 minutes\");\n reboot();\n }\n}\n\nnote that a hub deadlocked in publish has MQTT_CONNECTED true and LINK_DOWN false, so the watchdog never fires — which is exactly the field failure we're seeing", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "device events through one handler table", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "matchmaking queues stall for one region at peak and i can't see why from the metrics:\n\nmatchmaker_queue_depth{region=\"eu-west\"} 41,882\nmatchmaker_matches_created{region=\"eu-west\"} 0/s (normally 120/s)\nmatchmaker_ticket_age_p99{region=\"eu-west\"} 412s\nmatchmaker_pool_scan_duration{region=\"eu-west\"} 8.4s (normally 40ms)\nmatchmaker_backfill_active{region=\"eu-west\"} 1,204\n\nother regions are healthy with the same build. the scan is O(n²) over the pool and eu-west is our biggest region, but this only started last week", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "our device integration API, which three hardware partners build against from a PDF we wrote in 2024:\n\nMQTT topics:\n hub/{hub_id}/state hub → cloud, retained, QoS 1, at most every 30s\n hub/{hub_id}/event hub → cloud, not retained, QoS 1\n hub/{hub_id}/cmd cloud → hub, QoS 1, hub must ack on .../cmd/ack within 5s\n hub/{hub_id}/ota cloud → hub, QoS 1, payload is a signed manifest\n\nthings partners get wrong: state is retained so a stale state survives a hub being offline for days; commands are not idempotent and a redelivery after a missed ack will run twice; the ack topic is per-command not per-hub; and QoS 1 means duplicates are expected rather than exceptional\n\nwrite the integration reference for partners", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "the extraction team's list, with finance watching the model bill:\n\n- stop sending the full document in repair prompts; send the failing section\n- make termination_notice_days optional, or teach the model to return null with a reason\n- measure cost per customer per stage, which we currently cannot do at all\n- version prompts and record which version produced which result\n- add a circuit breaker so a rate limit doesn't back up the whole queue\n- evaluate whether the layout model is still needed now that OCR quality improved\n\ntwo engineers, and the bill is the thing leadership is looking at", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "device state lives in the hub's memory, a retained MQTT message and postgres, and all three disagree often enough that support checks all three by habit. work through what a single authoritative store would mean for offline reconciliation, for the automation engine's read latency, and for the three hardware partners who read retained messages today", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "hub firmware encodes its state machine as four static atomics read by four tasks, including the watchdog that decides whether to reboot a device in someone's home. before we touch any of it i'd like agreement on what the states actually are and how they're represented, because the current arrangement is why the deadlock is so hard to reason about", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "en"} -{"prompt": "what counts as a counter reset?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "extraction quality halved overnight for one customer with no code change, and the only thing that changed on their side was a new scanner. work through the pipeline stage by stage — OCR confidence, layout, chunk sizes — and tell me where the quality is actually lost rather than where it first becomes visible i'd like enough detail that i can hand it to someone else to finish.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "matchmaking again", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "clause extraction quality collapsed for one customer overnight, same model, same prompts:\n\nrun 8f2b1c (yesterday): 412 documents, mean clauses extracted 41.2, human agreement 0.91\nrun 91cc40 (today): 409 documents, mean clauses extracted 12.8, human agreement 0.44\n\npipeline stages:\n pdf → ocr (tesseract 5.3) → layout (our model) → chunker → extractor (LLM) → validator\n\nocr confidence mean: 0.94 → 0.62\nchunker: mean chunk length 1,800 chars → 410 chars\nextractor: prompt unchanged, temperature 0, same model version\n\nthe customer started uploading scans from a new office scanner on monday", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "three places compute a device's \"is online\" state and they disagree:\n\n// api/devices.rs\nfn online(d: &Device) -> bool { d.last_seen_at > Utc::now() - Duration::minutes(5) }\n\n// automation/engine.rs\nfn online(d: &Device) -> bool { d.mqtt_session_present && d.last_state_at.is_some() }\n\n// mobile app (kotlin)\nfun isOnline(d: Device) = d.lastSeenAt.isAfter(Instant.now().minusSeconds(120))\n\nthe automation engine's version is the one that decides whether a rule runs, the app's is what the user sees, and support has learned to check all three", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "queue timer is announced every second", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "is the boot flag on its own sector?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "a legal customer's security team asked six specific questions about document handling and our honest answers are mostly uncomfortable. answer each from the code and the contracts, write it as a publishable page, and mark clearly where the answer is \"not today\" rather than dressing it up flag anything you'd want to change before doing it rather than after.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "extraction pipeline module does orchestration, retries, cost accounting and prompt assembly in seven hundred lines. split it, then document which piece owns retries because that's the question every incident starts with", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "what does the automation engine do when a device is offline at evaluation time", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "hubs stop reporting after a few days in the field and only ever recover with a power cycle:\n\n[2026-07-29T02:14:02Z WARN lumen_hub::mqtt] publish timed out after 30s, topic=hub/8f2b/state\n[2026-07-29T02:14:32Z WARN lumen_hub::mqtt] publish timed out after 30s, topic=hub/8f2b/state\n[2026-07-29T02:15:02Z ERROR lumen_hub::mqtt] outgoing queue full (1024), dropping message\n[2026-07-29T02:15:02Z INFO lumen_hub::net] link down (wlan0)\n[2026-07-29T02:15:04Z INFO lumen_hub::net] link up (wlan0), ip 192.168.1.44\n[2026-07-29T02:15:04Z INFO lumen_hub::mqtt] reconnect scheduled in 1s\n[2026-07-29T02:15:05Z INFO lumen_hub::mqtt] connecting to mqtts://ingest.lumen.io:8883\n\n\nthe reconnect task takes the client mutex and the publish path is still holding it waiting on the old socket", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "document uploads fail for exactly one customer and only for large files:\n\nPOST /v1/documents (multipart, 84MB pdf)\n → 413 Request Entity Too Large after 41s\n\nnginx: client_max_body_size 100m\ningress: proxy-body-size: 100m\napp: MAX_UPLOAD_BYTES = 104857600\ncdn: max request body 50MB (not configurable on our plan)\n\nthis customer's uploads go through the CDN because they're on our EU endpoint; everyone else hits the origin directly\n\ntimings from the failing request, captured at the CDN:\n request started 11:02:14.101\n bytes received 52,428,800 of 88,080,384\n connection closed by edge 11:02:55.882\n status returned to client 413\n\nand from our origin: no request logged at all, so nothing reached nginx\n\nthe customer is on the EU endpoint because of a data residency clause added to their contract in march; everyone else resolves straight to the origin load balancer", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "players report being matched with wildly different skill levels, here's a sample match:\n\nmatch m_88412, mode=ranked_5v5, region=na-east, created 11:02:14\n team A skill: 1204, 1188, 1211, 1197, 1206 (mean 1201)\n team B skill: 1198, 1210, 1189, 2410, 1205 (mean 1442)\n ticket ages at match time: 8s, 11s, 9s, 412s, 10s\n\nour relaxation schedule widens the skill window by 100 every 30 seconds with no cap, and the 412-second ticket had a window of ±1400 by the time it matched", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "could you look at the reconnect logic before i sign off on it? the mutex worries me:\n\npub async fn publish(&self, topic: &str, payload: &[u8]) -> Result<()> {\n let mut client = self.client.lock().await;\n client.publish(topic, QoS::AtLeastOnce, false, payload).await\n}\n\nasync fn reconnect_task(state: Arc) {\n loop {\n if state.link_down.load(Ordering::Relaxed) {\n let mut client = state.client.lock().await;\n *client = MqttClient::connect(&state.opts).await?;\n state.link_down.store(false, Ordering::Relaxed);\n }\n sleep(Duration::from_secs(1)).await;\n }\n}\n\npublish has a 30 second timeout on the network call but no timeout on acquiring the lock", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "changelog for the hub firmware 4.2.2, which is the recovery release:\n\n41c9e0b fix(ota): boot flag moved to its own flash sector\n88f21c0 fix(ota): image tail verified after the flag write, not before\nc0aa774 fix(mqtt): publish no longer holds the client lock across a network timeout\n2e91b45 feat(energy): counter resets are detected and reported explicitly\naa30f19 fix(net): reconnect backoff is now exponential with jitter, capped at 5 minutes\n9c1d004 chore: bootloader minimum version is now 2.1\n4410bb7 feat(recovery): a hub with no valid image now exposes a recovery access point\nb77e910 fix(time): hub clock is validated against the server before signing telemetry\n\nour readers are partner hardware teams and our own support staff; two of these are the fix for bricked devices and one requires a bootloader update first", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "design spec for the home app's automation editor, which is where users spend their time:\n\nAutomation editor (mobile, portrait)\n- Trigger, conditions and actions as three stacked sections, each a list with an add row at the bottom.\n- Adding a trigger opens a sheet of device categories, then devices, then the trigger for that device — three taps maximum to a common case.\n- A condition that can never be true (a sensor that doesn't report the attribute) is flagged inline at edit time, not on save.\n- Actions show the device's current state next to them, greyed if the device is offline, with the last-seen time on tap.\n- Saving an automation that references an offline device warns but does not block, because devices come back.\n- A test run button executes the actions immediately and shows per-action success or failure, which is the single most requested feature.\n- Everything must be operable one-handed and legible in a dark room at minimum brightness.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "review panes desync on zoom", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "one online check for devices", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "prompts out of the pipeline module", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "why did extraction quality drop overnight?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "energy totals jump backwards", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "eu-west queues stall at peak", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "automation screen", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "next thing on the board", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "model bill tripled because a schema change made a rarely-produced field required and the repair loop resends the whole document five times. beyond the immediate fix i want a position on how we control model cost structurally — per-stage budgets, circuit breakers, cost attribution per customer — because this will happen again with a different field", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "we owe thirty-eight households an explanation for why their heating controller stopped working overnight and needs replacing. write the customer notification — plain language, no blame-shifting to the update process, clear about the replacement and the timeline — and a separate internal write-up for the hardware team that doesn't spare us", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "internal documentation on model calls doesn't exist, and every engineer rediscovers the retry behaviour, the cost accounting gaps and the fact that a rate limit backs up the whole queue. write the guide for internal developers covering how a call is made, what happens on failure, and what it costs this has come up in three separate reviews now and never gets done.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "nobody can tell me whether the publish path can deadlock against the reconnect task, or whether the symptom is something else entirely — hubs go quiet and only a power cycle helps. read both paths and the lock discipline around the client and tell me exactly what sequence produces a hub that keeps running but never publishes again there's no rush on this week specifically, but it keeps costing us time.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "partner cloud-to-cloud integration lands in october and their protocol has no sequence numbers and no completion callbacks. design how we reconcile out-of-order state and asynchronous commands, then build the webhook receiver against it", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "hub's four state atomics should become one state machine. do the conversion, and tell me whether the watchdog's reboot decision changes for any state it currently sees", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "i'd like an honest read of whether a device's energy counter reset can be distinguished from a genuine drop, and if it can, the ingestion change that stops zeroing someone's daily total", "purpose": "review", "secondary": "backendImpl", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "an 84MB upload fails for one customer with a 413 after forty seconds, and there are five different size limits in the path. find which one it is, then switch that route to the presigned upload path we already have", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "go services each define their own Ticket type and convert at every boundary", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "ingest path should detect and record counter resets rather than clamping the difference to zero", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "clause list needs a confidence indicator", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "queue panel clips at 125% text", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "three hardware partners integrate against our MQTT contract from a PDF written in 2024, and the behaviours they get wrong — retained state surviving an offline hub, non-idempotent commands, duplicates under QoS 1 — are the ones we never wrote down. write the integration reference properly, with those three as prominent sections rather than footnotes", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "is our match quality metric measuring anything once the window is uncapped", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "a walkthrough of how a command reaches a device would help before i touch the ack path", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "smart plugs report energy readings that jump backwards, which corrupts the daily totals:\n\ndevice plug_4471, cumulative energy Wh:\n 10:00 128,441\n 10:15 128,502\n 10:30 128,560\n 10:45 61,204 ← jump backwards\n 11:00 61,290\n 11:15 61,344\n\nfirmware notes: the counter is a u32 of deciwatt-hours stored in flash, written every 15 minutes, and the device reboots on OTA or brownout\nour ingestion computes daily total as last_reading - first_reading of the day", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "die Automationen feuern doppelt, seit wir die Regel-Engine neu ausgerollt haben:\n\n2026-07-29T18:00:00.114Z rule r_4471 triggered (schedule 18:00) → action: turn_on lamp_881\n2026-07-29T18:00:00.118Z rule r_4471 triggered (schedule 18:00) → action: turn_on lamp_881\n2026-07-29T18:00:00.412Z device lamp_881 state=on\n2026-07-29T18:00:00.418Z device lamp_881 state=on\n\nzwei Instanzen der Engine laufen seit dem Rolling-Update, beide lesen denselben Zeitplan aus Postgres und es gibt keine Sperre; die alte Instanz sollte nach 30 Sekunden beendet werden, hängt aber an einer offenen MQTT-Verbindung", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "de"} -{"prompt": "hub fleet runbook should be a page rather than tribal knowledge, and the broker restart that disconnects four hundred thousand devices deserves a confirmation prompt. write the runbook, then add the guard", "purpose": "writing", "secondary": "quickFix", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "our on-call runbook for the hub fleet is two lines. what the team actually does:\n\n- \"hubs offline\" is almost always the ingest broker, not the hubs; check broker connection count first\n- a broker restart disconnects 400,000 hubs which then reconnect within 60 seconds — do not do this at peak\n- individual hubs stuck offline are usually the publish deadlock; a remote reboot command won't reach them\n- the OTA rollout must be paused before any broker work, otherwise devices update mid-disconnect\n- `hubctl fleet pause-ota` is the command, and it takes about two minutes to take effect\n- if energy readings stop for a region, check the ingest partition lag before assuming devices are down\n\nwrite the runbook page, in the order a person paged at 3am would need it", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "the legal customer's data requirements, which now block a renewal:\n\n\"Documents must be processable within our tenancy, with no document content transmitted to a third-party model provider. Where a provider is used, content must not be retained beyond the request and must not be used for training, evidenced contractually. Partial extraction results must not be persisted if extraction fails. Employee access to document content must be logged with a reason and reviewable by us. Deletion must propagate to all derived artefacts including embeddings and logs within 30 days.\"\n\nwe send full documents to a provider, persist partial results, log document text in our own application logs, and have never traced embeddings on deletion. i want the plan by contractual risk", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "device event handling is a match with a branch per device type, inline debounce logic in two of them, and a silent catch-all that hid a new device type for a month. restructure it into a handler per type with shared debounce and validation, and make an unknown type a loud failure rather than a shrug", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "matchmaking in eu-west stalls at every peak because a live event left the relaxation cap and backfill timeout disabled, but the deeper problem is that our pool scan is quadratic and nobody noticed until the region grew. i want a view on the algorithm itself, not just the config, with the party-matching path's bucketing as the obvious starting point", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "en"} -{"prompt": "our matchmaker config across regions, and only eu-west stalls:\n\n# na-east\npool_scan_interval: 500ms\nmax_pool_size: 20000\nbackfill_timeout: 60s\nrelaxation_step: 100\nrelaxation_cap: 800\nscan_workers: 8\n\n# eu-west\npool_scan_interval: 500ms\nmax_pool_size: 100000\nbackfill_timeout: 0 # disabled last week for a live event\nrelaxation_step: 100\nrelaxation_cap: 0 # uncapped, also from the live event\nscan_workers: 8\n\nand the two regions' shapes at peak:\n\n na-east pool 18,400 scan 42ms matches 118/s backfills active 41\n eu-west pool 96,200 scan 8,400ms matches 0/s backfills active 1,204\n ap-south pool 11,900 scan 31ms matches 74/s backfills active 22\n\nthe eu-west values were set for a live event three weeks ago and the ticket to revert them is still open", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "the partner hardware spec we have to implement on the cloud side:\n\nthe partner's devices speak their own protocol to their own cloud, and we integrate cloud-to-cloud:\n POST /partner/v1/webhook they call us on every state change, HMAC-SHA256 signed, at most 50/s per account\n GET /partner/v1/devices we poll for the device list every 6 hours; it is not paginated and returns up to 40k devices\n POST /partner/v1/command we send commands; they respond 202 and deliver asynchronously with no completion callback\n their state changes can arrive out of order and they do not include a sequence number, only a timestamp with second precision\n a device removed on their side simply stops appearing in the device list\n they rate limit us to 10 requests per second and will not raise it", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "device state ownership needs deciding and the reconciliation path needs building either way. work through the model with me, then implement the reconnect reconciliation so hubs returning after days stop overwriting newer cloud state", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "hub fleet spans four firmware versions and we've never deprecated one", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "what guarantees does the matchmaker make that a ticket eventually matches at all", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "extraction service has three HTTP clients with three timeout and retry policies, and the one used for model calls is the one with no timeout at all. consolidate them, and tell me which current behaviour each caller was relying on before i sign off on a single policy this is the third time it's bitten us and i'd like it to be the last.", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "matchmaking operator guide is one command, while the real knowledge — that queue depth is the wrong signal, that killing a backfill is safe, that restarting drops every ticket — lives in two people's heads. write the guide ordered by what someone paged during a peak needs first it doesn't have to be elegant, it has to be defensible in a review.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "so our extraction pipeline's cost tripled with no change in volume:\n\nweek 29: 412k documents, 8.1M model calls, $12,400\nweek 30: 409k documents, 24.8M model calls, $38,100\n\ncall breakdown by stage:\n classifier 409k → 409k\n extractor 2.4M → 2.4M\n validator 5.3M → 22.0M\n\nthe validator retries on a schema mismatch, up to 5 times, and we changed the schema on monday to add a required field the model rarely produces", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "session tokens for the mobile app expire early for some users and they get logged out mid-automation:\n\ntoken issued: 2026-07-29T09:00:00Z, exp 2026-08-28T09:00:00Z (30d)\nrejected at: 2026-07-29T14:12:44Z with \"token expired\"\n\nauth service log:\n jwt validation failed: token used before issued (iat 1753837200, now 1753818764)\n node: auth-7d9c4f8b6-x2plq\n\nntp status on that node: offset -18436 seconds, last sync 41 days ago\n\nthree of our twelve auth nodes have drifted, and the app retries against a random node until one accepts", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "ok so our validator's retry loop, which apparently tripled the bill:\n\ndef validate(doc, extracted, schema, attempts=5):\n for i in range(attempts):\n try:\n return Schema(schema).validate(extracted)\n except ValidationError as e:\n extracted = call_model(\n REPAIR_PROMPT.format(errors=e.messages, text=doc.text, previous=extracted)\n )\n log.warning(\"validation failed after %d attempts\", attempts)\n return extracted\n\nthe repair prompt includes the full document text, the schema now has a required field the model rarely produces, and there's no check for whether the repair actually changed anything", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "here's the matchmaking relaxation schedule, which i inherited and don't trust:\n\nfunc (t *Ticket) SkillWindow(now time.Time) int {\n age := now.Sub(t.CreatedAt)\n steps := int(age.Seconds()) / 30\n return baseWindow + steps*100\n}\n\nfunc (m *Matchmaker) scan(pool []*Ticket) []Match {\n for i := range pool {\n for j := i + 1; j < len(pool); j++ {\n if compatible(pool[i], pool[j], time.Now()) { ... }\n }\n }\n}\n\nno cap on the window, the scan is quadratic in pool size, and compatible() calls SkillWindow for both tickets on every comparison", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "por favor, revisa el manejo del contador de energía antes de que lo desplieguemos:\n\nfn daily_total(readings: &[Reading]) -> u64 {\n let first = readings.first().map(|r| r.wh).unwrap_or(0);\n let last = readings.last().map(|r| r.wh).unwrap_or(0);\n last.saturating_sub(first)\n}\n\nel contador es un u32 en el firmware, se reinicia a cero tras un OTA o un corte de corriente, y el dispositivo puede enviar lecturas fuera de orden tras una reconexión; saturating_sub devuelve cero cuando hay un reinicio, así que el consumo de ese día simplemente desaparece", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "es"} -{"prompt": "honestly the OTA design doc, written before we had the field failures. does it still hold?\n\n## Update flow\nThe hub downloads the image to slot B, verifies the signature, writes the boot flag and reboots. If slot B fails to boot, the bootloader falls back to slot A.\n\n## Assumptions\n- Slot A always holds a known-good image.\n- The boot flag can be written independently of the slots.\n- A failed update costs a reboot, not a device.\n\n## Not covered\nPower loss during the flag write. Devices whose slot A has itself been updated in place. Recovery without physical access.\n\nwe now know the flag shares a flash sector with the tail of slot B, and about one device in two hundred does not come back", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "right, the query behind our device history screen, which is slow for anyone with more than fifty devices:\n\nSELECT d.id, d.name, d.kind, d.last_seen_at,\n (SELECT state FROM device_states s WHERE s.device_id = d.id ORDER BY s.at DESC LIMIT 1) AS current_state,\n (SELECT count(*) FROM device_events e WHERE e.device_id = d.id AND e.at > now() - interval '24 hours') AS events_24h,\n (SELECT sum(wh) FROM energy_readings r WHERE r.device_id = d.id AND r.at::date = current_date) AS energy_today\nFROM devices d\nWHERE d.home_id = $1\nORDER BY d.name;\n\ndevice_states is 4.1 billion rows, device_events 8.8 billion, energy_readings 12 billion, all partitioned by day", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "quick one — the backfill logic in matchmaking, which i think is why the pool never drains:\n\nfunc (m *Matchmaker) backfill(match *Match) {\n for len(match.Players) < match.Mode.Size {\n ticket := m.pool.FindBest(match) // scans the whole pool\n if ticket == nil {\n time.Sleep(500 * time.Millisecond)\n continue // no timeout, no give-up\n }\n match.Add(ticket)\n m.pool.Remove(ticket)\n }\n}\n\nbackfills hold a slot in the match and are counted as active; there are 1,204 of them in eu-west right now and each one scans the pool twice a second", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "support's notes on the energy dashboard complaints, which need to become a help article:\n\n- daily totals occasionally show zero or a wildly wrong number\n- this happens when a plug reboots, because the cumulative counter restarts at zero\n- our daily total is last minus first, so a reboot mid-day either zeroes it or produces a negative we clamp to zero\n- the plug's own counter also wraps at about 4.2 million Wh, which affects a handful of long-running devices\n- customers see this as \"the app forgot my electricity usage\" and some have asked for refunds\n- the underlying readings are all still there; only the daily aggregation is wrong\n\nwrite the help article, and separately tell me which of these is a data problem and which is a presentation problem", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "incident notes from the bricked hubs, and we owe affected customers an explanation:\n\n09:02 first reports of hubs not coming back after the 4.2.1 update\n10:15 confirmed: 41 devices out of 8,400 updated overnight are unresponsive\n11:40 cause identified: the boot flag shares a flash sector with the tail of slot B\n12:00 OTA rollout paused for all remaining devices\n14:30 recovery requires physical access and a serial cable, which customers do not have\n16:00 decision: replace affected units, 41 devices across 38 customers\n\nthe customers are consumers, the hub controls their heating, and several were without it overnight\n\nwrite the customer notification and a separate internal write-up for the hardware team", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "as notas da revisão da pipeline de extração, para transformar em documento de decisão:\n\n- o validador repete até cinco vezes quando o esquema não valida, e cada repetição envia o documento inteiro\n- a alteração de segunda-feira tornou obrigatório um campo que a maioria dos contratos não tem\n- o custo semanal triplicou sem aumento de volume\n- opções: tornar o campo opcional, deixar o validador desistir mais cedo, ou enviar apenas o excerto relevante na repetição\n- a equipa jurídica quer o campo obrigatório porque alimenta um relatório\n- ninguém mede a taxa de sucesso das repetições, portanto não sabemos se ajudam\n\nescreve a nota de decisão com as opções, os custos estimados e uma recomendação", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "pt"} -{"prompt": "fyi the questions our legal customer's security team sent, which need answering as a document:\n\n\"Which parts of a document are sent to the model provider, and is any of it retained by them? Can we run in a mode where documents never leave our tenancy? What happens to a document if extraction fails partway — is a partial result stored? Who at your company can read the contents of an uploaded document, and is that access logged? If we delete a document, is it removed from your model provider's logs as well? Do you use customer documents to improve any model?\"\n\nanswer each from the code and our contracts, and write it as a page we can publish rather than a mail thread", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "heads up: the matchmaking service's operator guide is a single command. reality:\n\n- queue depth over 10,000 in one region means the scan is falling behind, not that players are queueing\n- `mmctl pool stats ` shows the pool size and scan duration, which is the actual signal\n- backfills are counted as active matches and can starve the pool; `mmctl backfill list` shows them\n- killing a backfill returns its players to the pool, which is safe and is usually the fix\n- restarting the matchmaker drops every ticket, which players experience as being kicked from the queue\n- the relaxation schedule has no cap, so a stuck ticket eventually matches with anyone, which is worse than not matching\n\nwrite the operator guide, ordered by what someone paged during a peak would need", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "社内向けに、モデル呼び出しの運用ドキュメントがありません。現状はこうです:\n\n- 抽出は 1 文書につき最大 3 回モデルを呼ぶ（分類・抽出・検証）\n- 検証が失敗すると最大 5 回まで修復プロンプトを送る。修復プロンプトには文書全文が含まれる\n- タイムアウトは 120 秒、リトライは 3 回、指数バックオフなし\n- レート制限に当たった場合は 429 をそのまま上位に返しており、キュー全体が詰まる\n- コストの計測はバッチ単位でしかできず、顧客別・ステージ別の内訳が出せない\n- プロンプトはコードに直接埋め込まれていて、変更履歴はコミットログにしかない\n\n例:\n\nresp = client.messages.create(model=MODEL, max_tokens=4096,\n messages=[{\"role\": \"user\", \"content\": prompt}])\n\nこれを社内の開発者向けドキュメントとしてまとめてください。特にリトライとコストの扱いを明確に\n\n実際のコストの内訳（先週）:\n classifier 409,000 calls $1,100\n extractor 2,400,000 calls $9,800\n validator 22,000,000 calls $27,200\n\n retry_on_429_total = 41,882\n timeout_total = 1,204\n repair_attempts_p99 = 5 (上限)\n\nこの内訳は手作業で集計したもので、ダッシュボードには存在しません", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "ja"} -{"prompt": "clippy on the hub firmware, and one of these is the deadlock:\n\nwarning: this `MutexGuard` is held across an `await` point\n --> src/mqtt.rs:88:9\n |\n88 | let mut client = self.client.lock().await;\n = help: consider using an async-aware lock or restructuring\nwarning: large enum variant\n --> src/proto.rs:41:1\nwarning: casting `u32` to `u16` may truncate\n --> src/energy.rs:141:22\nwarning: this loop never actually loops\n --> src/ota.rs:22:5\nwarning: `saturating_sub` on values that may legitimately decrease\n --> src/energy.rs:66:20\n\n5 warnings, and mqtt.rs:88 is exactly where hubs wedge", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "ruff and mypy on the extraction service, gate goes on next sprint:\n\nservices/extract/validator.py:41: error: Argument \"schema\" has incompatible type \"dict[str, Any]\"; expected \"Schema\" [arg-type]\nservices/extract/validator.py:88: warning: B008 Do not perform function call in argument defaults\nservices/extract/pipeline.py:141: error: Missing return statement [return]\nservices/extract/prompts.py:22: warning: E501 line too long (412 > 100)\nservices/extract/client.py:66: error: Call to untyped function \"call_model\" in typed context [no-untyped-call]\n\n3 errors, 2 warnings, and the missing return is in the path that handles a rate limit", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "small thing but the CDN and origin limits for uploads, one of these is why an 84MB file fails:\n\ncdn (eu endpoint): max request body 50MB\nnginx: client_max_body_size 100m\ningress annotation: nginx.ingress.kubernetes.io/proxy-body-size: 100m\napp: MAX_UPLOAD_BYTES = 104857600\ns3 presign (unused): part size 8MB, unlimited total\n\nthe presigned upload path exists in the code, is tested, and is not used by the web client\n\nand the sizes we actually see:\n p50 upload 1.2 MB\n p95 upload 18 MB\n p99 upload 62 MB\n largest last month 340 MB (rejected)\n\nabout 4% of uploads from that one customer are over the CDN's 50MB limit, and they are the contracts with scanned exhibits attached, which are the ones the customer cares most about", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "not urgent, but the hub's kubernetes ingest deployment, which we restarted during peak by accident:\n\nreplicas: 6\nstrategy:\n type: RollingUpdate\n rollingUpdate: { maxSurge: 1, maxUnavailable: 1 }\nterminationGracePeriodSeconds: 30\nreadinessProbe: { httpGet: { path: /healthz, port: 8080 }, periodSeconds: 5 }\nlifecycle:\n preStop: { exec: { command: [\"sleep\", \"5\"] } }\n\neach pod holds about 70,000 MQTT connections, hubs reconnect immediately with a one second backoff, and a rolling update currently drops a sixth of the fleet at a time", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "pasted-context", "lang": "en"} -{"prompt": "les seuils d'alerte du parc de hubs, on nous réveille pour rien :\n\n- alert: HubsOffline\n expr: sum(hub_connected == 0) > 1000\n for: 1m\n labels: { severity: page }\n\n- alert: IngestLag\n expr: kafka_consumergroup_lag{group=\"telemetry\"} > 100000\n for: 5m\n labels: { severity: page }\n\n- alert: OtaFailures\n expr: increase(ota_failed_total[1h]) > 10\n for: 0m\n labels: { severity: ticket }\n\nen réalité : mille hubs hors ligne c'est du bruit sur quatre cent mille appareils ; le lag dépasse 100 000 à chaque redémarrage du broker ; et les 41 appareils briqués n'ont produit qu'un ticket, vu le lendemain matin", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "fr"} -{"prompt": "dependabot on the extraction service, and one is a CVE:\n\npydantic 2.7.1 → 2.9.2 (minor; validation error message format changed, our repair prompt parses it)\nanthropic 0.34.0 → 0.40.0 (minor; streaming API changes, we don't stream)\npillow 10.3.0 → 10.4.0 (CVE-2026-10118, buffer overflow in TIFF decoding)\npytesseract 0.3.10 → 0.3.13 (minor)\n\nwe pass scanned TIFFs through pillow before OCR, and our repair prompt includes the raw pydantic error text", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "this pipeline module does orchestration, retries, cost accounting and prompt assembly in one file:\n\nclass ExtractionPipeline:\n def run(self, doc):\n # ocr, with its own retry loop\n # layout model call, with a different retry loop\n # chunking, with the chunk size hardcoded per document type\n # extraction call, with prompt assembled inline from three f-strings\n # validation with the repair loop\n # cost accounting by summing token counts into a module-level dict\n # audit row written at the end, or not at all if anything raised\n\n700 lines, one test that mocks the model client and asserts on the final output", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "unsere Prompt-Bausteine liegen an vier Stellen im Code:\n\n# prompts.py\nEXTRACT_PROMPT = \"Extract all clauses...\"\n\n# pipeline.py\nprompt = f\"{EXTRACT_PROMPT}\\n\\nDocument type: {doc.kind}\\n{text}\" # zusätzlicher Kontext inline\n\n# validator.py\nREPAIR_PROMPT = \"The following JSON failed validation...\" # eigene Formatierung\n\n# experiments/ab_test.py\nPROMPT_V2 = \"...\" # läuft für 10% der Kunden\n\nvier Varianten, keine Versionierung, und niemand kann sagen, welcher Prompt ein bestimmtes Ergebnis erzeugt hat", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "de"} -{"prompt": "quarter planning input, needs sequencing:\n\n- 41 bricked hubs are a product recall problem and the fix needs a bootloader update first\n- the publish deadlock takes hubs offline until a power cycle and affects maybe 2% of the fleet monthly\n- extraction costs tripled and finance has noticed\n- eu-west matchmaking stalls at every peak since the live event config was left in place\n- the legal customer's security questionnaire is blocking a renewal worth a fifth of that product's revenue\n- one firmware engineer, one platform engineer, and the game backend team is two people\n- there's a hardware partner integration due in october that assumes our MQTT contract doesn't change", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "architecture ticket, and i want the thinking before anyone starts:\n\nIOT-540 — Device state ownership\nDevice state currently lives in three places: the hub's memory, a retained MQTT message, and our postgres. They disagree routinely and support has learned to check all three. The proposal is a single authoritative state store with the retained message as a cache. Concerns: hubs go offline for days and must reconcile on reconnect; the automation engine reads state on every rule evaluation and cannot tolerate a database round trip; retained messages are what partner integrations read; and any change to the MQTT contract affects three hardware partners with their own release cycles.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "spec for the document review screen, which lawyers use for hours at a time:\n\nReview screen\n- Document pane on the left with the original scan, extracted clauses highlighted in place, and page thumbnails.\n- Clause list on the right, grouped by type, each showing a confidence indicator and the page it came from.\n- Clicking a clause scrolls both panes; the highlight must survive zoom and rotation.\n- Low-confidence extractions are marked with a shape as well as a colour and sort to the top of their group.\n- Editing a clause's text or type is inline, saves optimistically, and records who changed what.\n- A \"nothing extracted for this section\" state exists and must be visible rather than an absence.\n- Keyboard: j/k moves between clauses, e edits, a accepts, r rejects — lawyers ask for this specifically.\n- Must remain usable at 200% zoom for accessibility, which the current fixed two-pane layout does not.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "accessibility findings for the game's in-client store and queue UI, from a platform certification review:\n\n1. The queue timer is announced continuously by the screen reader, making the client unusable while queueing.\n2. Match-found accept is a 10 second timed action with no way to extend it, which fails the platform's timing requirement.\n3. Store prices are conveyed with strikethrough only for discounts, with no text alternative.\n4. Controller focus is lost when a modal closes, landing on the first element of the page rather than the invoking control.\n5. The rank badge conveys tier by colour alone.\n6. Text scaling above 125% clips the queue panel.\n7. No captions for the voice announcements in the match-found flow.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "design tokens versus what the home app's device screens actually use:\n\ntokens:\n color.surface #FFFFFF / #0D1117\n color.text #0D1117 / #E6EDF3\n color.muted #6E7781\n color.on #1A7F37\n color.off #6E7781\n color.warn #9A6700\n space 4/8/12/16/24, radius 8/12/20, touch target 44dp minimum\n type: title 20/26, body 15/22, caption 13/18\n\nthe device screens: six hardcoded colours including two greens, touch targets of 32dp on the toggle rows, an offline state shown only by reduced opacity, and three type sizes not in the scale\n\nbring it onto the tokens, fix the touch targets, and give offline a proper indicator", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "relaxation cap back to 800 in eu-west", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "pillow CVE bump before friday", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"} -{"prompt": "onboarding email says \"you're hub\"", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "core", "lang": "en"} -{"prompt": "backfill timeout back to 60 seconds", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "pause the OTA rollout now", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "la app muestra vatios en vez de kilovatios", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "es"} -{"prompt": "maxUnavailable 1 drops 70k connections", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "make termination_notice_days optional", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "ntp is 41 days stale on three auth nodes", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "OtaFailures should page immediately", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "Upload über presigned URLs statt Proxy", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "de"} -{"prompt": "hub telemetry is signed using the device's own clock, which on a hub that boots without network is whatever it was when it last had one, so the signature is valid and the timestamp is nonsense. work out how far back this goes in the stored data, then move to server-assigned time with the device clock kept only as a hint", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "our matchmaking pool is scanned three different ways depending on the code path:\n\n// scan.go — the main loop, quadratic over the whole pool\nfor i := range pool { for j := i+1; j < len(pool); j++ { ... } }\n\n// backfill.go — FindBest, linear scan per call, called twice a second per backfill\nfunc (p *Pool) FindBest(m *Match) *Ticket { for _, t := range p.tickets { ... } }\n\n// party.go — party matching, builds a map by skill bucket then scans buckets\nbuckets := map[int][]*Ticket{}\n\nonly the party path uses buckets; the other two ignore them entirely and rebuild nothing", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "the schema we agreed for prompt versioning, now it needs building:\n\nCREATE TABLE prompt_versions (\n id uuid PRIMARY KEY,\n name text NOT NULL,\n version int NOT NULL,\n template text NOT NULL,\n schema jsonb,\n model text NOT NULL,\n params jsonb NOT NULL,\n created_by text NOT NULL,\n created_at timestamptz NOT NULL DEFAULT now(),\n UNIQUE (name, version)\n);\n\nevery model call records the prompt_version id it used; versions are immutable once referenced; an A/B experiment references two versions and the assignment must be recorded per document; and we need to answer \"which prompt produced this extraction\" for any result in the last two years", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "device screens ignore the tokens and use 32dp touch targets on the toggles. bring them onto the tokens and fix the targets, and tell me whether the row height change breaks the compact layout on small phones", "purpose": "frontendImpl", "secondary": "review", "mixed": true, "difficulty": 0.55, "slice": "mixed", "lang": "en"} -{"prompt": "missing return in the rate limit path", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "test run button on the automation editor", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "toggle rows are 32dp, should be 44", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "rank badge is colour-only", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "j and k through the clause list", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "オフラインの機器が薄い色でしか分かりません", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "ja"} -{"prompt": "controller focus lost after a modal", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "skill buckets for every scan path", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "une seule machine à états pour le hub", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "fr"} -{"prompt": "`last_seen_at` naming everywhere", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "extract the repair loop from validate", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "inline `compatible`, one caller left", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "one retry policy for model calls", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "doc comments on the MQTT topic contract", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "changelog for firmware 4.2.2", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "nota aos clientes sobre os hubs afetados", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "pt"} -{"prompt": "document the retained-state gotcha", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "summarise the state-ownership proposal", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "PR body for the deadlock fix", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "can a backfill starve the pool?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "¿el validador reintenta con el documento entero?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "es"} -{"prompt": "walk me through the OTA flow", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "hubs wedge until power cycled", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "warum feuern die Automationen doppelt?", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "de"} -{"prompt": "endpoint for a document's extraction lineage", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "carry on with that", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "cheaper, ideally", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "you choose what matters", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "lo de la extracción, continúa", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "es"} -{"prompt": "tidy where you can", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "like the last one", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "security answers", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "low risk only today", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "take a look please", "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": "forty-one hubs are bricked in customers' homes and the fix needs a bootloader update that itself has to go over the air, which is exactly the mechanism that failed. i want the recovery plan worked through properly — how we ship a bootloader safely, what we do for the devices already dead, and what we change so a partial flash write can never take a device out again", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "legal customer's renewal is blocked on data handling we don't currently do: no third-party model provider, no persisted partial results, no document text in logs, and deletion propagating to embeddings. i'd like the options with honest costs, including the one where we run a model in our own tenancy and what that does to quality and latency", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "OTA design doc assumes the boot flag can be written independently of the slots and that a failed update costs a reboot rather than a device, both of which we now know are false. read it against the flash layout and the bootloader and tell me which of its other assumptions are similarly wrong the last person who touched this left, so there's nobody to ask.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "en"} -{"prompt": "matchmaking pool is scanned three ways — quadratic in the main loop, linear per backfill, bucketed only in the party path — and the bucketing is the one that works. bring all three onto the bucketed structure, keep match quality measurably the same on a replayed peak, and make the scan cost sublinear in pool size", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "prompts live in four places including an experiment file that runs for a tenth of our customers, and nobody can say which prompt produced a given result. consolidate them into one versioned location, record the version on every call, and keep the experiment running throughout the migration we've been burned by guessing at this before, so evidence over instinct please.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "automation editor is where users spend their time and it currently lets you build automations that can never fire, then tells you nothing. build it to the spec — inline impossible-condition warnings, device state next to actions, and the test run button people keep asking for if the answer is that it's fine as it is, that's a useful answer too.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "review screen is a fixed two-pane layout that breaks at 200% zoom, which fails the accessibility requirement in a public sector tender. rebuild it to the spec with the keyboard navigation lawyers asked for, and make sure the clause highlighting survives zoom and rotation keep it concrete — file names and line numbers are more use than principles here.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "before we change the OTA flow i want the failure modes written down — power loss at each step, a corrupted slot, a bootloader that itself needs updating — and then the flag relocation implemented against that analysis this has come up in three separate reviews now and never gets done.", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.9, "slice": "mixed", "lang": "en"} -{"prompt": "model cost control needs a design — budgets per stage, a circuit breaker, attribution per customer — and the repair loop needs fixing this week regardless. give me the design, then change the repair prompt to send only the failing section", "purpose": "planning", "secondary": "quickFix", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "unser Matchmaking skaliert nicht mehr und die Konfiguration aus dem Live-Event steht immer noch. Ich hätte gern zuerst ein Konzept für die Poolstruktur und danach die Umstellung des Haupt-Scans auf Buckets", "purpose": "planning", "secondary": "refactor", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "de"} -{"prompt": "MQTT integration reference has to exist before the october partner starts, and while writing it please confirm whether a redelivered command really does execute twice, because two partners have asked and we've given different answers", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "model-call guide needs writing and i expect it will surface things we should fix rather than document — the 429 propagation especially. write the guide, and give me that list separately", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "our device event handling has grown a branch per device type:\n\nmatch event.kind {\n \"plug.energy\" => { /* 40 lines, includes counter reset detection */ }\n \"plug.state\" => { /* 20 lines */ }\n \"thermostat.temp\" => { /* 30 lines, has its own smoothing */ }\n \"thermostat.setpoint\" => { /* 25 lines */ }\n \"sensor.motion\" => { /* 15 lines, debounce logic inline */ }\n \"sensor.contact\" => { /* 15 lines, different debounce */ }\n \"lock.state\" => { /* 35 lines, includes an audit write nothing else does */ }\n _ => { /* silently ignored, which is how we missed a new device type for a month */ }\n}", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "the hub thing", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "escribe la guía del operador para el matchmaking y comprueba en el código si matar un backfill devuelve realmente a los jugadores a la cola, porque el runbook lo afirma y nadie lo ha verificado", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "es"} -{"prompt": "three online checks for devices should become one, and i'd like to know which of the three the automation engine should actually be using before we standardise on it. check that, then unify", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "tokens are being rejected as \"used before issued\" on three auth nodes whose clocks have drifted by five hours. confirm that's the whole story, then fix the nodes and make the validator tolerate a small skew rather than failing outright a rough ordering matters more to me than a complete answer right now.", "purpose": "debugging", "secondary": "quickFix", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "players are being matched against wildly stronger opponents and the relaxation window is my suspect, but i want it confirmed against real tickets. diagnose it, then cap the window at whatever the analysis supports", "purpose": "debugging", "secondary": "quickFix", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "store and queue UI fails platform certification on seven counts including a timed accept with no extension. fix what we can before submission, and write the certification response for the rest", "purpose": "frontendImpl", "secondary": "writing", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "prompt versioning needs the immutability rules agreed before it's built — what happens when someone edits a referenced version, and how experiments map to versions. settle that, then implement the table and the recording", "purpose": "backendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "rename `Ticket.Skill`, it's a rating in one place and a percentile in another", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "could you explain what happens to a retained state message when a hub is factory reset", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "i'd like to understand how a document that fails extraction halfway is stored, if at all", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "why does the layout model still run now that OCR quality has improved", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "someone should check whether document text ends up in our application logs", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "is it expected that a hub keeps executing automations while disconnected from the cloud", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "pouvez-vous m'expliquer comment le compteur d'énergie gère un redémarrage du boîtier ?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "fr"} -{"prompt": "docs/ota.md describes a rollback that the bootloader doesn't actually implement", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "a short note on why prompts are moving into the database, for the decision log", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "partner changelog needs an entry for the command ack topic changing shape", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "rustdoc on publish() promises a 30 second bound that the lock acquisition ignores", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "write the customer note about energy totals being recalculated for the affected days", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "health endpoint reports the matchmaker healthy while it has created no matches for ten minutes", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "staging has one hub and prod has four hundred thousand, with the same broker connection limits", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "how should we handle a hardware partner whose devices we can't update ourselves", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "what's the right way to evaluate an extraction change when the ground truth is a lawyer's judgement", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "i want a position on whether automations should run on the hub or in the cloud", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "two customers want an on-premise deployment of the document pipeline, what would that require", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "we need a plan for supporting a second matchmaking mode with completely different team sizes", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "what should happen to a queued player when their region's matchmaker restarts", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "an endpoint that returns a hub's last twenty state transitions, for support", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "per-customer cost attribution for model calls, since finance can only see the total", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "commands need an idempotency key so a redelivery after a missed ack doesn't run twice", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "device list needs a filter for offline devices, which is what people open the app to check", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "clause list should let a reviewer accept a whole group at once, with undo", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "queue screen should show estimated wait time rather than a spinner that lies", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "energy chart should mark counter resets rather than drawing a cliff", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "whatever unblocks the renewal", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "next bit of the firmware work", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "mobile app and the hub disagree about what \"away mode\" means — one treats it as a mode, the other as a flag that other automations can clear — and users notice when heating comes back on. settle the semantics, then make both sides agree, and tell me which behaviour existing automations depend on whatever you find, write it somewhere the next person will actually look.", "purpose": "refactor", "secondary": "planning", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "python services load secrets three different ways and one of them logs the loaded values at debug level, which is on in staging. fix that today, then unify the loading so it can't happen again", "purpose": "quickFix", "secondary": "refactor", "mixed": true, "difficulty": 0.55, "slice": "mixed", "lang": "en"} -{"prompt": "extraction queue has no dead letter, so a document that fails five times is retried forever and one bad scan has been cycling since tuesday. add the dead letter, and decide with me first what a human is supposed to do with the documents that land in it i'm not attached to the current approach if there's an obviously better one.", "purpose": "backendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "internal page on the hub's state machine doesn't exist, which is why every firmware bug report starts with three people describing the states differently. write it from the code — the four atomics, who sets what, and what the watchdog does with each combination — as the reference for the rework context if it helps: this has been open since before i joined the team.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "hub reports its firmware version only on connect, so a device that failed an update and rolled back looks like it's still on the old version forever, which is how we undercounted the bricked devices. report the running version on every state message, and backfill what we can from the OTA logs i'd rather have the reasoning written down than a quick answer.", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "go services each define their own Ticket type and convert at every boundary, which is why the matchmaker and the party service disagree about whether skill is a rating or a percentile. define it once in a shared package, convert only at the edges where we talk to clients, and prove that a replayed peak produces identical matches", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "validator's repair loop, the OCR retry and the model client's own retry are three nested layers of retrying that nobody designed together, and a single bad document can therefore produce seventy-five model calls. flatten them into one retry policy with an overall budget per document, keeping the successful-path behaviour exactly as it is", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "chunk sizes are hardcoded per document type in the pipeline, the layout model has its own idea of section boundaries, and the extractor gets whichever wins. pull chunking into one place with the document type as a parameter, and keep the extraction output identical for a sample of a thousand documents across all types tell me if this is the wrong shape entirely, i won't be offended.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "hub's flash layout, the bootloader's expectations and the OTA writer's assumptions live in three files that have to agree and don't. bring the layout into one definition both the bootloader and the application build from, and make a mismatch a compile error rather than a bricked device nobody has trusted this code for about a year, which is part of the problem.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "nobody can tell me what our match quality metric actually measures once the relaxation window is uncapped, because it compares against the window rather than against the players' skills. read the metric and the matcher together and tell me whether the number we report weekly means anything at all assume whoever picks it up next has no context beyond what you write.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "eu-west matchmaker still runs the live-event configuration from three weeks ago — no relaxation cap, no backfill timeout, a pool five times the size of any other region. put the standard values back, and tell me which of the three actually mattered so we know what the event genuinely needed the sooner we know roughly how big this is, the better for planning.", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "ingest deployment does a rolling update with maxUnavailable of one, which drops seventy thousand MQTT connections at a time and produces a reconnect storm that looks exactly like an outage. change the rollout to something the fleet can absorb, and tell me what the safe reconnect rate actually is i've already spent an afternoon on it and got nowhere useful.", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} +{"prompt":"diff --git a/projects/meridian/Sources/CLI/Commands/Doctor.swift b/projects/meridian/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/meridian/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate MeridianTideWorkerFlow'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":"projects/meridian/workers/thumbnail/consumer.ex 里的 MeridianGarnetModalStore 最近在 SQLite 流程中出现间歇性问题。 原因已经明确：只把 staging timeout 从 15 秒改成 30 秒，并调整对应 assertion。\n\n约束：\n- 继续使用 SQLite\n- 保持兼容性和取消语义\n- 改动只限于 MeridianGarnetModalStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"zh"} +{"prompt":"Quartz: // projects/meridian/apps/console/routes/usage.svelte\nfinal class MeridianFlintTimelineFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianFlintTimelineFlow 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":"Three teams extended MeridianVelaDrawerService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current PostgreSQL 17 operational envelope\n\nSeveral teams work in this geospatial, Deno, iPadOS 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":"MeridianDeltaCanvasService's staging timeout is already known to be wrong: change the single projects/meridian/db/migrations/20260730_events.sql value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Raven: // projects/meridian/app/src/main/SyncWorker.kt\nfinal class MeridianOrbitSyncFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianOrbitSyncFlow 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":"MeridianCopperBridgeCoordinator needs a paired pass: change MeridianCopperBridgeCoordinator's known staging timeout from 15 to 30 seconds, plus capture the contract and rollback note for consumers. Use projects/meridian/db/migrations/20260730_events.sql as the source of truth, preserve the WebGPU contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Sable: // projects/meridian/infra/modules/edge/main.tf\nfinal class MeridianCloudReconcilerFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianCloudReconcilerFlow; 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":"Compare the old and new MeridianDriftConsoleFlow 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":"Compare the old and new MeridianSableParserService 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":"Tide: // projects/meridian/packages/api/openapi.yaml\nfinal class MeridianFernSnapshotFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianFernSnapshotFlow 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":"Since the last release, MeridianEchoRegistryService has shown an accessibility label that reads the internal enum; nobody on the team can reproduce it reliably on a laptop. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- do not introduce another runtime dependency\n- stay compatible with the existing NATS JetStream deployment\n- keep the work scoped to MeridianEchoRegistryService and its direct tests\n\nThis repository spans geospatial, Deno, iPadOS; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Rename MeridianAtlasSearchService's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Center the MeridianBeaconStoreStore modal","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Bring MeridianOspreyJobStore'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.5,"slice":"core","lang":"en"} +{"prompt":"Move MeridianOpalRouterStore'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":"MeridianDeltaCanvasCoordinator: ship a sensible version","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Walk through MeridianAcornWidgetService's features.py","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Match MeridianPineMetricsStore's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"MeridianNovaPickerCoordinator: polish the last piece","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Umbra: Incident timeline — INC-53159\n\n08:02 deploy MeridianKiteSchedulerCoordinator 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 MeridianKiteSchedulerCoordinator migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"MeridianRainfallDBService crashes after reconnect","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Vela: projects/meridian/Sources/App/SessionStore.swift has grown through several launches, and MeridianAmberFilterStore now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- do not introduce another runtime dependency\n- stay compatible with the existing NATS JetStream deployment\n- keep the work scoped to MeridianAmberFilterStore and its direct tests\n\nThis repository spans geospatial, Deno, iPadOS; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-53146: retire the legacy replay path for MeridianRavenSessionFlow\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 MeridianRavenSessionFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Ownership of MeridianMapleQueueStore is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current SQLite operational envelope\n\nSeveral teams work in this geospatial, Deno, iPadOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Willow: # projects/meridian/internal/auth/refresh.go\n[worker.meridianmoonlitsdkflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.meridianmoonlitsdkflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.meridianmoonlitsdkflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.MeridianMoonlitSDKFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-53144\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/meridian/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":"Memory attributed to MeridianPrismCacheService rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"This should remain a deliberately small patch: MeridianMosaicGridStore has one known configuration mistake in projects/meridian/ui/settings/PrivacyPane.tsx, not an open-ended failure investigation. 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- do not introduce another runtime dependency\n- stay compatible with the existing SQLite deployment\n- keep the work scoped to MeridianMosaicGridStore and its direct tests\n\nThis repository spans geospatial, Deno, iPadOS; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Bring MeridianBasilRunnerStore'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":"Xylem: Ticket OPS-53140: retire the legacy replay path for MeridianPrismCacheFlow\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 MeridianPrismCacheFlow 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":"MeridianCedarPolicyCoordinator needs a paired pass: finish MeridianCedarPolicyCoordinator's responsive empty and retry states, plus give the existing implementation a read-only safety pass. Use projects/meridian/web/components/FilterDrawer.vue as the source of truth, preserve the Tokio contract, and avoid unrelated cleanup.","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"What is the safest way to split projects/meridian/app/src/main/SyncWorker.kt into independently owned modules while MeridianFlintTimelineStore's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"MeridianMicaProfileCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Support wants the behavior in projects/meridian/packages/api/openapi.yaml recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary. The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Pin MeridianCedarPolicyStore's Tokio dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"PM needs a concise migration note for MeridianEmberRelayStore, 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":"Move MeridianNimbusFormService'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":"Security flagged MeridianAtlasSearchStore for a read-only pass because its Tokio boundary mixes tenant data, retries, and cancellation in subtle ways. 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- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current Tokio operational envelope\n\nSeveral teams work in this geospatial, Deno, iPadOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"MeridianRavenSessionCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"MeridianCinderAuthStore returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/meridian/web/components/FilterDrawer.vue and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"The MeridianOpalRouterService surface in projects/meridian/app/src/main/SyncWorker.kt 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":"Read projects/meridian/internal/auth/refresh.go and tell me whether MeridianCloudReconcilerStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/meridian/internal/auth/refresh.go b/projects/meridian/internal/auth/refresh.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/internal/auth/refresh.go\n+++ b/projects/meridian/internal/auth/refresh.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate MeridianSlateEditorFlow'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":"Yarrow: Bring MeridianFlintTimelineService'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":"Zephyr: diff --git a/projects/meridian/lib/codec/frame.cc b/projects/meridian/lib/codec/frame.cc\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/lib/codec/frame.cc\n+++ b/projects/meridian/lib/codec/frame.cc\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\nAdd the bounded MeridianPineMetricsFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Checkout: diff --git a/projects/meridian/src/sync/reconcile.ts b/projects/meridian/src/sync/reconcile.ts\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/src/sync/reconcile.ts\n+++ b/projects/meridian/src/sync/reconcile.ts\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure MeridianCopperBridgeFlow 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":"Draft MeridianAmberFilterService's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Two asks around MeridianFernSnapshotCoordinator: (1) find the unknown cause of a feature flag whose default differs between environments; (2) give the existing implementation a read-only safety pass. Do not introduce another runtime dependency, and leave a clear boundary between the resulting artifacts or edits.","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Polish the MeridianBeaconStoreService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"MeridianCoralUploadService est-il sûr ?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"fr"} +{"prompt":"MeridianMosaicGridService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. 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- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current SQLite operational envelope\n\nSeveral teams work in this geospatial, Deno, iPadOS 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":"MeridianAmberFilterCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Ticket OPS-53150: retire the legacy replay path for MeridianLumenChartCoordinator\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 MeridianLumenChartCoordinator 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":"PM needs a concise migration note for MeridianMapleQueueFlow, including the user impact, rollback trigger, and the one configuration key operators must change. The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"The MeridianLumenChartStore 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":"We expect MeridianLumenChartService to outgrow its current PostgreSQL 17 arrangement next quarter, but changing everything at once would be risky. 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- do not introduce another runtime dependency\n- stay compatible with the existing PostgreSQL 17 deployment\n- keep the work scoped to MeridianLumenChartService and its direct tests\n\nThis repository spans geospatial, Deno, iPadOS; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"MeridianIrisBatchCoordinator is blocking the next release because timestamps rendered one day ahead near UTC midnight. I need two concrete outcomes from a single pass: change MeridianIrisBatchCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing PostgreSQL 17 conventions in projects/meridian/packages/api/openapi.yaml; do not introduce another runtime dependency. 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":"MeridianRavenSessionStore's staging timeout is already known to be wrong: change the single projects/meridian/Sources/CLI/Commands/Doctor.swift value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"MeridianSableParserCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"# CI job 53133: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: SQLite\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] MeridianAsterWebhookFlowIntegration.replays_after_timeout ... ok\n[test] MeridianAsterWebhookFlowIntegration.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 \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\nReconstruct the MeridianAsterWebhookFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating duplicate retries after a network handoff in MeridianEmberRelayFlow, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Assess the MeridianOrbitSyncService diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"$ pnpm test --filter MeridianAcornWidgetFlow\n RUN v3.2.4 /workspace/apps/console\n × MeridianAcornWidgetFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=53121 phase=resume storedCursor=seg-0183\n session=53121 phase=fetch requestCursor=seg-0183 pageSize=200\n session=53121 phase=commit receivedCursor=seg-0184 itemCount=0\n session=53121 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Reconstruct the MeridianAcornWidgetFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"MeridianBeaconStoreCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Center the MeridianLedgerGateStore modal","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Exporter: The API work is done; what remains for MeridianKiteSchedulerStore is the visible interaction layer across loading, offline, empty, and success cases. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside MeridianKiteSchedulerStore\n- do not introduce another runtime dependency\n\nThe relevant code crosses geospatial, Deno, iPadOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Fresh release brief for MeridianAtlasSearchCoordinator:\n- primary outcome: change MeridianAtlasSearchCoordinator'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/meridian/internal/auth/refresh.go\n- platform constraint: Tokio\n- known complication: lost focus when the drawer animation finishes\n\nBoth results are required, but they should remain independently reviewable. Do not introduce another runtime dependency; 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.4,"slice":"mixed","lang":"en"} +{"prompt":"Scheduler: Ticket OPS-53114: retire the legacy replay path for MeridianAtlasSearchFlow\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 MeridianAtlasSearchFlow 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":"MeridianNimbusFormCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Two asks around MeridianPineMetricsCoordinator: (1) lay out a staged migration for MeridianPineMetricsCoordinator; (2) also add the visible loading and offline states. Do not introduce another runtime dependency, and leave a clear boundary between the resulting artifacts or edits.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"MeridianWrenExportCoordinator: restructure, then document","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Clarify MeridianPineMetricsService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"MeridianMoonlitSDKCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"projects/meridian/ui/settings/PrivacyPane.tsx の MeridianGarnetModalService で、SQLite の flow に断続的な問題が起きています。 consumer 向けに contract、error、retry、コピー可能な例を含む文書を書き、handler は変更しないでください。\n\n制約:\n- SQLite を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は MeridianGarnetModalService のみ","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"ja"} +{"prompt":"Dashboard: The minimum supported SQLite version in projects/meridian/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":"Translate the MeridianSlateEditorStore setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Worker: The data is already available in projects/meridian/infra/modules/edge/main.tf; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"# projects/meridian/services/ledger/replay.go\n[worker.meridiancedarpolicyflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.meridiancedarpolicyflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.meridiancedarpolicyflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.MeridianCedarPolicyFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-53129\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. The intended correction is already known: change only the stale 15-second setting to 30 seconds in projects/meridian/services/ledger/replay.go and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"pasted-context","lang":"en"} +{"prompt":"Animate the MeridianFrostPanelService drawer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"# CI job 53112: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: WebGPU\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] MeridianSummitProxyFlowIntegration.replays_after_timeout ... ok\n[test] MeridianSummitProxyFlowIntegration.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 \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\nReconstruct the MeridianSummitProxyFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Before touching projects/meridian/src/sync/reconcile.ts, 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.9,"slice":"core","lang":"en"} +{"prompt":"Could MeridianMicaProfileStore show the active SQLite sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"I inherited MeridianSummitProxyService and need a careful read of projects/meridian/src/sync/reconcile.ts before I can sign off on the next release. 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- do not introduce another runtime dependency\n- stay compatible with the existing WebGPU deployment\n- keep the work scoped to MeridianSummitProxyService and its direct tests\n\nThis repository spans geospatial, Deno, iPadOS; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"MeridianCinderAuthCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Where did MeridianFernSnapshotService's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"MeridianTideWorkerCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Simulator: # projects/meridian/Sources/CLI/Commands/Doctor.swift\n[worker.meridianechoregistrycoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.meridianechoregistrycoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.meridianechoregistrycoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.MeridianEchoRegistryCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-53156\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/meridian/Sources/CLI/Commands/Doctor.swift and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Runbook: # projects/meridian/cmd/exporter/main.py\n[worker.meridianharborindexflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.meridianharborindexflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.meridianharborindexflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.MeridianHarborIndexFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-53131\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/meridian/cmd/exporter/main.py. 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":"MeridianCoralUploadCoordinator: correct, then assess","purpose":"backendImpl","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Trace: projects/meridian/ml/pipeline/features.py の MeridianBirchMigratorFlow で、NATS JetStream の flow に断続的な問題が起きています。 段階、互換性、metrics、rollback、ownership を提案し、コード変更の前で止めてください。\n\n制約:\n- NATS JetStream を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は MeridianBirchMigratorFlow のみ","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"ja"} +{"prompt":"Read projects/meridian/crates/index/src/segment.rs and tell me whether MeridianPrismCacheStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"MeridianCraneWorkspaceCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Ticket: projects/meridian/config/staging.toml 里的 MeridianCraneWorkspaceService 最近在 PostgreSQL 17 流程中出现间歇性问题。 请拆分职责并去掉重复，同时保持 API、wire value、顺序和可观察行为不变。\n\n约束：\n- 继续使用 PostgreSQL 17\n- 保持兼容性和取消语义\n- 改动只限于 MeridianCraneWorkspaceService","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"Check MeridianWrenExportStore's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/meridian/lib/codec/frame.cc b/projects/meridian/lib/codec/frame.cc\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/lib/codec/frame.cc\n+++ b/projects/meridian/lib/codec/frame.cc\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 MeridianMicaProfileFlow'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":"Incident timeline — INC-53127\n\n08:02 deploy MeridianJuniperCLIFlow 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 MeridianJuniperCLIFlow 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":"diff --git a/projects/meridian/Sources/CLI/Commands/Doctor.swift b/projects/meridian/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/meridian/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit MeridianAmberFilterFlow 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":"Compare the old and new MeridianNimbusFormStore 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":"Profiler: // projects/meridian/services/ledger/replay.go\nfinal class MeridianCinderAuthFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianCinderAuthFlow; 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":"Incident timeline — INC-53141\n\n08:02 deploy MeridianSableParserFlow 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 MeridianSableParserFlow 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":"Em projects/meridian/packages/api/openapi.yaml, o MeridianCraneWorkspaceStore tem um problema intermitente no fluxo de PostgreSQL 17. A causa já é conhecida: mude apenas o timeout de staging de 15 para 30 segundos e ajuste a assertion.\n\nRestrições:\n- continuar com PostgreSQL 17\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao MeridianCraneWorkspaceStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"pt"} +{"prompt":"SDK consumers are ready for durable continuation tokens, so the remaining work lives in MeridianSummitProxyStore's API, storage, and worker layers. Add signed cursor parsing, bounded pagination, key rotation, tenant checks, and a resumable background path with metrics for lag, retries, and terminal failures.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside MeridianSummitProxyStore\n- do not introduce another runtime dependency\n\nThe relevant code crosses geospatial, Deno, iPadOS. Prefer evidence from the repository and make any assumption explicit.\n\nThe contract notes are context; the requested outcome is the working server path.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"En projects/meridian/ui/settings/PrivacyPane.tsx, MeridianBasilRunnerService tiene un problema intermitente en el flujo de SQLite. La causa ya está clara: cambia solo el timeout de staging de 15 a 30 segundos y ajusta su assertion.\n\nRestricciones:\n- seguir con SQLite\n- conservar compatibilidad y cancelación\n- limitar el cambio a MeridianBasilRunnerService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"es"} +{"prompt":"Wire a MeridianKiteSchedulerFlow background task in projects/meridian/services/ledger/replay.go that expires abandoned sessions, records an OpenTelemetry span, and yields cleanly when shutdown begins.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"MeridianSpruceDaemonFlow occasionally exhibits an accessibility label that reads the internal enum, but only after a reconnect. Follow the data and cancellation paths in projects/meridian/db/migrations/20260730_events.sql and identify the cause before changing anything.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-53154: retire the legacy replay path for MeridianEmberRelayCoordinator\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 MeridianEmberRelayCoordinator 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":"Two deliverables are holding up MeridianMosaicGridCoordinator. First, assess ownership and failure handling in projects/meridian/ui/settings/PrivacyPane.tsx. In the same workstream, capture the contract and rollback note for consumers. The relevant starting point is projects/meridian/ui/settings/PrivacyPane.tsx, which follows SQLite conventions and currently suffers from a flaky snapshot caused by locale-dependent sorting. Do not introduce another runtime dependency.\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":"review","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Pin MeridianIrisBatchService's PostgreSQL dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Lay out a two-milestone strategy for eliminating duplicate retries after a network handoff in MeridianEchoRegistryStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Any races in MeridianLedgerGateService?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Console: // projects/meridian/packages/api/openapi.yaml\nfinal class MeridianNimbusFormFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Consolidate MeridianNimbusFormFlow'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":"The behavior of MeridianBirchMigratorService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/meridian/ml/pipeline/features.py. 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- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current NATS JetStream operational envelope\n\nSeveral teams work in this geospatial, Deno, iPadOS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"The MeridianCinderAuthService surface in projects/meridian/services/ledger/replay.go 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":"For MeridianSlateEditorCoordinator, lay out a staged migration for MeridianSlateEditorCoordinator; once that is complete, consolidate the duplicated normalization paths without changing behavior. Work from projects/meridian/infra/modules/edge/main.tf, stay with Tokio, and do not introduce another runtime dependency. Keep the two outcomes separately reviewable.","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Workspace: Incident timeline — INC-53137\n\n08:02 deploy MeridianOpalRouterFlow 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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Capture the MeridianOpalRouterFlow 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":"A flaky failure around MeridianSpruceDaemonService survived three attempted fixes, so I want the evidence and invariants traced before another patch lands. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside MeridianSpruceDaemonService\n- do not introduce another runtime dependency\n\nThe relevant code crosses geospatial, Deno, iPadOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"For MeridianJuniperCLICoordinator, produce a consumer guide for MeridianJuniperCLICoordinator; once that is complete, give the existing implementation a read-only safety pass. Work from projects/meridian/app/src/main/SyncWorker.kt, stay with WebGPU, and do not introduce another runtime dependency. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Por que MeridianJuniperCLIService trava?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"pt"} +{"prompt":"Repository: # projects/meridian/config/staging.toml\n[worker.meridianirisbatchflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.meridianirisbatchflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.meridianirisbatchflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.MeridianIrisBatchFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-53115\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 MeridianIrisBatchFlow'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":"PM is preparing the MeridianMapleQueueService rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside MeridianMapleQueueService\n- do not introduce another runtime dependency\n\nThe relevant code crosses geospatial, Deno, iPadOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"Pipeline: Ticket OPS-53120: retire the legacy replay path for MeridianWrenExportFlow\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 MeridianWrenExportFlow 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":"Three teams extended MeridianDriftConsoleService independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current WebGPU operational envelope\n\nSeveral teams work in this geospatial, Deno, iPadOS 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":"Gateway: diff --git a/projects/meridian/db/migrations/20260730_events.sql b/projects/meridian/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/db/migrations/20260730_events.sql\n+++ b/projects/meridian/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit MeridianQuartzPlayerFlow 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":"Renderer: The name pendingAck means two different things across MeridianDeltaCanvasStore's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"MeridianLedgerGateCoordinator needs a paired pass: separate MeridianLedgerGateCoordinator's policy from transport without behavior changes, plus capture the contract and rollback note for consumers. Use projects/meridian/Sources/CLI/Commands/Doctor.swift as the source of truth, preserve the NATS JetStream contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Indexer: Incident timeline — INC-53123\n\n08:02 deploy MeridianFrostPanelFlow 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 MeridianFrostPanelFlow 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":"UI ticket DES-53139: finish the compact MeridianOspreyJobFlow filter experience\n\nRoute: /catalog/search\nSource: projects/meridian/web/components/FilterDrawer.vue\nFramework: Tokio\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nUse the UI evidence to complete MeridianOspreyJobFlow'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":"Apparently: diff --git a/projects/meridian/crates/index/src/segment.rs b/projects/meridian/crates/index/src/segment.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/crates/index/src/segment.rs\n+++ b/projects/meridian/crates/index/src/segment.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit MeridianVelaDrawerFlow 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":"Lately: The public surface of MeridianIrisBatchStore is frozen, but its internal ownership in projects/meridian/packages/api/openapi.yaml is difficult to test and even harder to change safely. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside MeridianIrisBatchStore\n- do not introduce another runtime dependency\n\nThe relevant code crosses geospatial, Deno, iPadOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Oddly: For MeridianAsterWebhookCoordinator, lay out a staged migration for MeridianAsterWebhookCoordinator; once that is complete, consolidate the duplicated normalization paths without changing behavior. Work from projects/meridian/ui/settings/PrivacyPane.tsx, stay with SQLite, and do not introduce another runtime dependency. Keep the two outcomes separately reviewable.","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Add a bounded MeridianRavenSessionService export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Does MeridianLumenChartFlow enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"MeridianCloudReconcilerService 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":"Responsive layout for MeridianFernSnapshotStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Currently: Incident timeline — INC-53153\n\n08:02 deploy MeridianBasilRunnerCoordinator 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Turn the material above into a concise MeridianBasilRunnerCoordinator 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":"Two asks around MeridianHarborIndexCoordinator: (1) finish MeridianHarborIndexCoordinator's responsive empty and retry states; (2) correct the known stale timeout beside it. Do not introduce another runtime dependency, and leave a clear boundary between the resulting artifacts or edits.","purpose":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Today: The MeridianBasilRunnerFlow surface in projects/meridian/ui/settings/PrivacyPane.tsx is stable now; turn its edge cases into API documentation with one successful example and one cancellation example. The deliverable is prose for consumers; do not alter the handler.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"projects/meridian/services/ledger/replay.go has grown through several launches, and MeridianKiteSchedulerService now mixes policy, transport, persistence, and metrics in one place. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- do not introduce another runtime dependency\n- stay compatible with the existing Tokio deployment\n- keep the work scoped to MeridianKiteSchedulerService and its direct tests\n\nThis repository spans geospatial, Deno, iPadOS; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"MeridianEmberRelayService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. 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- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current Tokio operational envelope\n\nSeveral teams work in this geospatial, Deno, iPadOS 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":"A previously stable test around MeridianTideWorkerStore 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":"Context: Incident timeline — INC-53113\n\n08:02 deploy MeridianMosaicGridFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Map a safe route from the current MeridianMosaicGridFlow 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":"Background: The behavior of MeridianOrbitSyncStore is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/meridian/apps/console/routes/usage.svelte. 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- touch generated artifacts only through their checked-in generator\n- do not introduce another runtime dependency\n- retain the current WebGPU operational envelope\n\nSeveral teams work in this geospatial, Deno, iPadOS monorepo, so keep ownership and handoff points understandable in a small review.\n\nThe server contract is the subject, but the requested output is documentation rather than handler code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Ticket OPS-53152: retire the legacy replay path for MeridianSpruceDaemonCoordinator\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 MeridianSpruceDaemonCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"MeridianPrismCacheCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"2026-07-30T08:14:11.409Z level=info service=meridiandriftconsolecoordinator pod=meridiandriftconsolecoordinator-7cf8 request_id=53157 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=meridiandriftconsolecoordinator request_id=53157 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=meridiandriftconsolecoordinator request_id=53157 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=meridiandriftconsolecoordinator request_id=53157 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=meridiandriftconsolecoordinator request_id=53157 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=meridiandriftconsolecoordinator request_id=53157 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=meridiandriftconsolecoordinator request_id=53157 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=meridiandriftconsolecoordinator request_id=53157 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nReconstruct the MeridianDriftConsoleCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"MeridianSummitProxyCoordinator is blocking the next release because an empty state that flashes before cached data arrives. I need two concrete outcomes from a single pass: change MeridianSummitProxyCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing WebGPU conventions in projects/meridian/db/migrations/20260730_events.sql; do not introduce another runtime dependency. 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.7,"slice":"mixed","lang":"en"} +{"prompt":"MeridianGarnetModalCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Move MeridianDriftConsoleStore'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":"Read projects/meridian/lib/codec/frame.cc and tell me whether MeridianMicaProfileService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Question: Ticket OPS-53126: retire the legacy replay path for MeridianLedgerGateFlow\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 MeridianLedgerGateFlow 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":"MeridianOpalRouterCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Match MeridianQuartzPlayerService's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Queue MeridianHarborIndexService's expired sessions","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"MeridianAcornWidgetCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Observation: Ticket OPS-53138: retire the legacy replay path for MeridianNovaPickerFlow\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 MeridianNovaPickerFlow 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":"Fresh release brief for MeridianMarbleTokenCoordinator:\n- primary outcome: assess ownership and failure handling in projects/meridian/ml/pipeline/features.py\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/meridian/ml/pipeline/features.py\n- platform constraint: NATS JetStream\n- known complication: out-of-order events after consumer rebalancing\n\nBoth results are required, but they should remain independently reviewable. Do not introduce another runtime dependency; 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":"Document MeridianAcornWidgetStore's cancellation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Before touching projects/meridian/Sources/App/SessionStore.swift, 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":"MeridianBirchMigratorStore'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":"MeridianCloudReconcilerCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Enforce MeridianSlateEditorService's idempotency key","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"MeridianOrbitSyncCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"One contained cleanup in projects/meridian/config/staging.toml: remove the obsolete MeridianWillowCodecStore import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Draft MeridianRainfallDBStore's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"MeridianFrostPanelCoordinator: restructure, then document","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"diff --git a/projects/meridian/engine/render/atlas.cpp b/projects/meridian/engine/render/atlas.cpp\nindex 62d71aa..90f3c1e 100644\n--- a/projects/meridian/engine/render/atlas.cpp\n+++ b/projects/meridian/engine/render/atlas.cpp\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 MeridianMapleQueueCoordinator 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":"What is the safest way to split projects/meridian/cmd/exporter/main.py into independently owned modules while MeridianSableParserStore's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"Two deliverables are holding up MeridianVelaDrawerCoordinator. First, lay out a staged migration for MeridianVelaDrawerCoordinator. In the same workstream, also add the visible loading and offline states. The relevant starting point is projects/meridian/pkg/cache/lease.rs, which follows PostgreSQL 17 conventions and currently suffers from a deadlock that appears only during shutdown. Do not introduce another runtime dependency.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Store MeridianCopperBridgeStore's delivery receipts","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Assess the MeridianAsterWebhookService diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-53142: retire the legacy replay path for MeridianDeltaCanvasFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for MeridianDeltaCanvasFlow, 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":"Could MeridianMoonlitSDKService show the active Tokio sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"MeridianQuartzPlayerCoordinator: restructure, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Give MeridianCedarPolicyService a loading skeleton","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-53111\n\n08:02 deploy MeridianMarbleTokenFlow 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 MeridianMarbleTokenFlow 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":"Is MeridianWrenExportService safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-53151\n\n08:02 deploy MeridianBirchMigratorCoordinator 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 MeridianBirchMigratorCoordinator, 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":"thread 'tokio-runtime-worker' panicked at projects/meridian/crates/index/src/segment.rs:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: meridianrainfalldbflow::scheduler::LeaseTask::flush\n at ./projects/meridian/crates/index/src/segment.rs:217:18\n 4: meridianrainfalldbflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nReconstruct the MeridianRainfallDBFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Where did MeridianFrostPanelStore's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Test Suite 'MeridianBeaconStoreFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[MeridianBeaconStoreFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/meridian/engine/render/atlas.cpp:144: error: -[MeridianBeaconStoreFlowTests 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 '-[MeridianBeaconStoreFlowTests 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 MeridianBeaconStoreFlow'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":"En projects/meridian/ml/pipeline/features.py, MeridianMarbleTokenStore tiene un problema intermitente en el flujo de NATS JetStream. La causa ya está clara: cambia solo el timeout de staging de 15 a 30 segundos y ajusta su assertion.\n\nRestricciones:\n- seguir con NATS JetStream\n- conservar compatibilidad y cancelación\n- limitar el cambio a MeridianMarbleTokenStore","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"es"} +{"prompt":"Before we approve MeridianNovaPickerService, 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.3,"slice":"core","lang":"en"} +{"prompt":"For MeridianRainfallDBCoordinator, lay out a staged migration for MeridianRainfallDBCoordinator; once that is complete, consolidate the duplicated normalization paths without changing behavior. Work from projects/meridian/pkg/cache/lease.rs, stay with PostgreSQL 17, and do not introduce another runtime dependency. Keep the two outcomes separately reviewable.","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.8,"slice":"mixed","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_53135'\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_53135'::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\nDeliver the MeridianCraneWorkspaceFlow server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Documente le contrat MeridianJuniperCLIStore","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"fr"} +{"prompt":"MeridianFlintTimelineCoordinator: sort out the rough edge","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"// projects/meridian/ui/settings/PrivacyPane.tsx\nfinal class MeridianGarnetModalFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianGarnetModalFlow; 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":"Map MeridianQuartzPlayerStore's ownership split","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Warum hängt MeridianCoralUploadStore?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"de"} +{"prompt":"Our support and SDK teams keep answering the same questions about MeridianVelaDrawerStore, but the current prose in projects/meridian/pkg/cache/lease.rs only describes the happy path. 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- do not introduce another runtime dependency\n- stay compatible with the existing PostgreSQL 17 deployment\n- keep the work scoped to MeridianVelaDrawerStore and its direct tests\n\nThis repository spans geospatial, Deno, iPadOS; use its existing conventions rather than importing a new abstraction.\n\nThe server contract is the subject, but the requested output is documentation rather than handler code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Compare MeridianAsterWebhookStore's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Remove MeridianHarborIndexStore's stray comma","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"MeridianOspreyJobCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"SDK consumers are ready for durable continuation tokens, so the remaining work lives in MeridianWillowCodecService's API, storage, and worker layers. Add signed cursor parsing, bounded pagination, key rotation, tenant checks, and a resumable background path with metrics for lag, retries, and terminal failures.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside MeridianWillowCodecService\n- do not introduce another runtime dependency\n\nThe relevant code crosses geospatial, Deno, iPadOS. Prefer evidence from the repository and make any assumption explicit.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"In projects/meridian/cmd/exporter/main.py hat MeridianMarbleTokenService ein sporadisches Problem im NATS JetStream-Ablauf. Trenne Verantwortlichkeiten und entferne Duplikate, ohne API, Wire-Werte, Reihenfolge oder sichtbares Verhalten zu ändern.\n\nRandbedingungen:\n- NATS JetStream weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf MeridianMarbleTokenService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um MeridianMarbleTokenService mit NATS JetStream kompatibel.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"de"} +{"prompt":"MeridianOspreyJobService's metric is misspelled as succesful_total in one declaration. Correct that literal and its exact test expectation, without renaming anything else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"MeridianCopperBridgeService leaks tasks on shutdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"// projects/meridian/config/staging.toml\nfinal class MeridianWillowCodecCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianWillowCodecCoordinator; 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":"On compact widths, MeridianTideWorkerService'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.4,"slice":"core","lang":"en"} +{"prompt":"Constraint: // projects/meridian/web/components/FilterDrawer.vue\nfinal class MeridianCoralUploadFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 MeridianCoralUploadFlow; 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"} diff --git a/data/round2-14.jsonl b/data/round2-14.jsonl index d2090b8..bce07c1 100644 --- a/data/round2-14.jsonl +++ b/data/round2-14.jsonl @@ -1,200 +1,200 @@ -{"prompt": "our checkpoint restart produces wrong results but only for jobs restarted after more than 48 hours:\n\ncheckpoint written at step 412000, size 8.1 TB\nrestart at step 412000, continues to step 500000\nvalidation against a continuous run: max relative difference 4.1e-3 (tolerance 1e-9)\n\nthe checkpoint stores the state arrays and the RNG seed but not the RNG stream position, and the thermostat's random forces resume from the seed rather than from where they were\n\nthe relevant part of the checkpoint code:\n\n ! checkpoint.f90\n write(unit) step, n_atoms\n write(unit) positions, velocities\n write(unit) rng_seed\n ! rng_pos declared, never written <- compiler warns about it, we've ignored that for years\n\n ! thermostat.f90, on restart\n call random_seed(put=rng_seed) ! stream restarts from the beginning\n\nvalidation runs so far:\n restart after 6h max rel diff 2.1e-11 (looks fine)\n restart after 24h max rel diff 8.8e-6\n restart after 48h max rel diff 4.1e-3\n\nthe two papers under discussion both used runs restarted at least twice", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "the checkpoint writer and reader have drifted apart across three format versions:\n\n! checkpoint.f90 — writer\nwrite(unit) step, n_atoms, positions, velocities, seed\n\n! checkpoint.f90 — reader, with version sniffing\nread(unit) step, n_atoms\nif (n_atoms > 0 .and. n_atoms < HUGE_N) then\n read(unit) positions, velocities, seed ! v2\nelse\n rewind(unit); read(unit) step, positions, velocities ! v1, no seed\nend if\n\nversion detection by whether a field looks plausible, no magic number, no version field, and v3 adds the RNG position we need for correct restarts", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "HRIS special cases into configuration", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "a real checkpoint format with a version field", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "job adverts stopped syncing to one job board and their support says they see nothing:\n\nPOST https://partner.jobboard.example/v2/postings\n → 200 OK {\"accepted\": true, \"id\": \"jb_88412\"}\n\nour sync log:\n posted 412 adverts, 412 accepted, 0 errors\n\ntheir side:\n \"we have received 0 postings from your account since 21 July\"\n\nwe changed the partner API key on 21 July; the old key still returns 200 with an accepted body but their system discards the postings, which their docs describe in a footnote as \"deprecated key behaviour\"", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "our receipt rendering path, which is why the cheap tills fall over:\n\nfun renderToBitmap(receipt: Receipt): Bitmap {\n val height = receipt.lines.size * LINE_HEIGHT_PX // 203dpi, ~34px per line\n val bmp = Bitmap.createBitmap(WIDTH_PX, height, Bitmap.Config.ARGB_8888)\n val canvas = Canvas(bmp)\n receipt.lines.forEachIndexed { i, line -> canvas.drawText(line, 0f, (i * LINE_HEIGHT_PX).toFloat(), paint) }\n return bmp\n}\n\nARGB_8888 at 576 pixels wide, a 60-line receipt is about 4.7MB, a 500-line stocktake report is 40MB, and the printer takes a monochrome bitmap anyway", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "the HRIS field mapping lives in YAML with per-customer special cases in code:\n\n# mappings/acme.yaml\nfirst_name: givenName\nstart_date: startDate # format: YYYY-MM-DD\n\n# mappings/globex.yaml\nfirst_name: fname\nstart_date: start # format: DD/MM/YYYY <- handled by an if in the pusher\n\n// pusher.ts\nif (customer === 'globex') payload.start = formatUk(offer.startDate)\nif (customer === 'initech') payload.employee_id = padLeft(offer.id, 8)\nif (customer === 'umbrella') delete payload.middle_name\n\nnine customers, four with code special cases, and adding a tenth means a deploy", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "a migration archived forty thousand applications at one customer because their talent pool records had never been touched since creation, and unarchiving them is a click each in the product. i want the recovery planned properly — how we identify exactly which records we archived, how we put them back without a script that could touch anyone else's data, and what we change so a migration can't do this again", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "HRIS integration guide was written for one customer and is now used for nine, four of whom have special cases living in if-statements. write the guide that reflects reality, and separately list every special case that should be configuration so we can stop deploying to onboard a customer keep it concrete — file names and line numbers are more use than principles here.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "offline banner with today's total", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "what makes an application \"active\"?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "simulation is one four-thousand-line module and only one person can work on it, which is now the binding constraint on everything else in the group's list. before splitting it i'd like agreement on the seams — I/O, decomposition, physics, output — and on how we prove the split changed nothing, given our only test is a stored trajectory", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "en"} -{"prompt": "job adverts stopped reaching a job board three weeks ago while their API kept returning 200 with an accepted body, which our sync treats as success. work out what we should have been checking, and whether any other partner integration has the same shape of silent failure nobody has trusted this code for about a year, which is part of the problem.", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "interview scheduling emails go out with the wrong timezone for about one candidate in twenty:\n\ninterview i_4471\n scheduled_at (db, timestamptz): 2026-08-03 14:00:00+00\n interviewer timezone: Europe/Berlin\n candidate timezone: America/New_York (from their profile)\n email to candidate said: 3 August, 14:00 (your local time)\n actual time in New York: 10:00\n\nthe template formats with the interviewer's timezone but labels it as the candidate's, and only candidates whose profile timezone differs from the interviewer's notice", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "an MPI job hangs at the same point every time on more than 512 ranks:\n\n[rank 0] entering collective: MPI_Allreduce (comm=MPI_COMM_WORLD, count=4194304, MPI_DOUBLE)\n[rank 1] entering collective: MPI_Allreduce\n...\n[rank 511] entering collective: MPI_Allreduce\n[rank 512] entering collective: MPI_Bcast (comm=MPI_COMM_WORLD, count=1, MPI_INT)\n[rank 513] entering collective: MPI_Bcast\n...\n\n\nranks 512 and above take a different branch that broadcasts a convergence flag before the reduction, and the branch depends on a value computed from the local domain size", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "stock counts drift in stores that use the handheld scanners, about 0.3% of lines a week:\n\nscan event sku=SKU-4471 qty=1 device=hh_881 at=11:02:14.114 synced_at=11:02:19\nscan event sku=SKU-4471 qty=1 device=hh_881 at=11:02:14.118 synced_at=11:02:19\nstock movement sku=SKU-4471 delta=-1 source=scan at=11:02:19\nstock movement sku=SKU-4471 delta=-1 source=scan at=11:02:19\n\nthe scanner debounces a double trigger in firmware at 200ms, these are 4ms apart, and each scan gets a device-local id that the backend uses for idempotency — but the id is a counter that resets when the handheld is docked", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "three places decide whether an application is \"active\" and they disagree:\n\n// api/pipeline.ts\nconst active = (a: Application) => !['rejected', 'withdrawn', 'archived'].includes(a.stage)\n\n// jobs/nurture.ts\nconst active = (a: Application) => a.stage === 'pool' || a.stage === 'applied'\n\n-- reports/active_candidates.sql\nWHERE a.stage NOT IN ('rejected', 'withdrawn') AND a.archived_at IS NULL\n\nthe report includes archived-by-migration records that have archived_at set but stage still 'pool' for some rows, because the migration set both and an earlier one set only stage", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "careers page says \"Sorry, no jobs founds\"", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "core", "lang": "en"} -{"prompt": "payment buttons need to be 72dp", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "pipeline filters should live in the URL", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "is the scan idempotency key unique enough?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "checkpoint restarts are silently wrong for long jobs because the RNG stream position isn't saved, and two published papers used runs that were restarted. i need the plan: how we determine which results are affected, what we tell the group and the journals if any are, and how the format changes so this class of error is impossible rather than merely fixed", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.95, "slice": "core", "lang": "en"} -{"prompt": "offline card payments are now contractual with limits, automatic retransmission and same-day manager reporting, none of which we have. work through what that means for the till, the backend and the store manager's tooling, and be explicit about which parts need the payment vendor's cooperation rather than just ours we've been burned by guessing at this before, so evidence over instinct please.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "simulation module split needs the seams agreed before anyone moves a line, and then the I/O layer extracted first because it's the least entangled. do both, and keep the stored-trajectory test passing at every step", "purpose": "planning", "secondary": "refactor", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "what does the till do with an offline voucher that is declined the next morning", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "por favor, revisa la consulta que alimenta el panel de reclutamiento antes de que la subamos:\n\nSELECT j.id, j.title,\n count(a.*) FILTER (WHERE a.stage = 'applied') AS applied,\n count(a.*) FILTER (WHERE a.stage = 'interview') AS interviewing,\n (SELECT count(*) FROM interviews i WHERE i.job_id = j.id AND i.starts_at > now()) AS upcoming,\n (SELECT avg(EXTRACT(epoch FROM (a2.hired_at - a2.created_at))/86400)\n FROM applications a2 WHERE a2.job_id = j.id AND a2.hired_at IS NOT NULL) AS avg_days_to_hire\nFROM jobs j\nLEFT JOIN applications a ON a.job_id = j.id\nWHERE j.tenant_id = $1 AND j.status = 'open'\nGROUP BY j.id, j.title;\n\nel inquilino más grande tiene 4.100 vacantes abiertas y 8,2 millones de candidaturas", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "es"} -{"prompt": "changelog for the POS release, which stores will read on their tills:\n\n41c9e0b fix(print): receipts render in bands rather than one bitmap, fixing crashes on 1GB tills\n88f21c0 fix(payments): terminal client retries once on a read timeout before falling back to offline\nc0aa774 feat(offline): offline vouchers now carry a reference the till can reconcile automatically\n2e91b45 fix(scan): scan idempotency now uses a device-persistent id rather than a resetting counter\naa30f19 feat(stock): stocktake reports print in landscape on the wide printers\n9c1d004 chore: minimum android is now 11\n4410bb7 fix(ui): the numeric keypad no longer accepts a leading zero on quantities\nb77e910 feat(returns): returns without a receipt require a manager PIN\n\nour readers are store managers, not engineers; two of these change what staff do at the till", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "unsere Mandantenprüfung ist an vierzehn Stellen unterschiedlich implementiert:\n\n// api/jobs.ts\nwhere: { tenantId: session.tenantId }\n\n// api/applications.ts\nwhere: { job: { tenantId: session.tenantId } }\n\n// api/reports.ts\nconst rows = await prisma.$queryRaw`SELECT ... WHERE tenant_id = ${session.tenantId}`\n\n// jobs/nurture.ts\n// keine Prüfung – der Job läuft für alle Mandanten und filtert nach Stage\n\nvierzehn Stellen, drei Muster, und eine Stelle ohne Prüfung; ich hätte gern eine Durchsetzung, die man nicht vergessen kann", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "de"} -{"prompt": "design spec for the recruiter pipeline board, which recruiters have open all day:\n\nPipeline board\n- Columns per stage, cards per candidate, virtualised — the largest tenant has 4,000 candidates in one job.\n- Card shows name, current stage age, source, and a flag if an interview is scheduled within 24 hours.\n- Drag between columns moves the stage optimistically, with a toast that can undo for ten seconds.\n- Bulk select with shift-click, then a bulk action bar; every bulk action states how many candidates it affects.\n- Filters: source, stage age, interviewer, tag. Filters live in the URL so recruiters can share a view.\n- Keyboard: arrow keys move between cards, enter opens, m moves stage via a menu — recruiters asked for this.\n- An archived candidate must be visibly distinct rather than absent, because \"where did they go\" is our top support question.\n- Everything must stay responsive with 4,000 cards and a websocket delivering updates from other recruiters.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "terminal read timeout to 10s with one retry", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "stage needs an indicator besides colour", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "apply modal traps focus with no escape", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "one active-application predicate", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "doc comments on the public jobs API", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "why does the 512-rank job hang?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "en"} -{"prompt": "applications lost at the morning spike", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "till screen", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "tenant scoping is done by hand in fourteen places with three patterns and one omission, and we have no test that would catch a fifteenth. i want a position on enforcement — row-level security, a repository layer, or something else — that survives our transaction-scoped pooler and the reports that use raw SQL", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "boundary", "lang": "en"} -{"prompt": "nobody can tell me whether a restarted run can differ from a continuous one in a way that matters, and two papers depend on the answer. read the checkpoint writer, the reader and the thermostat's use of the RNG, and tell me exactly what diverges and by how much on a realistic run whatever you find, write it somewhere the next person will actually look.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "scan idempotency key is device id plus a device-local counter that resets when the handheld is docked, held in a one-hour cache, across four hundred devices. work out how often two different scans can collide on that key, and whether the stock drift we see is consistent with that rate i'm not attached to the current approach if there's an obviously better one.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "en"} -{"prompt": "before we touch the checkpoint format i want the failure modes written down — restart on a different rank count, a changed thermostat, a truncated file — and then the versioned header implemented against that analysis", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "i'd like an honest read of whether our OpenMP reduction can produce different totals for the same input on the same machine, and if it can, the change that makes it deterministic without costing more than a few percent", "purpose": "review", "secondary": "refactor", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "recruiter app ignores the tokens and uses stage colour as the only stage indicator. bring it onto the tokens with a non-colour indicator, and tell me whether the card height changes enough to affect how many fit on a laptop screen", "purpose": "frontendImpl", "secondary": "review", "mixed": true, "difficulty": 0.55, "slice": "mixed", "lang": "en"} -{"prompt": "ATS background jobs each construct their own prisma client, which is a meaningful share of the connections at 09:00. share one, and tell me which jobs were relying on their own transaction isolation before i approve it", "purpose": "quickFix", "secondary": "review", "mixed": true, "difficulty": 0.5, "slice": "mixed", "lang": "en"} -{"prompt": "payment vendors behind one interface", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "stock drifts on handheld scans", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "an HPC customer's security team asked six questions about credentials, shared filesystems, telemetry and job isolation, and our honest answers include a couple of \"not currently\". write the document from the code, mark those clearly, and give each one a remediation note rather than leaving it hanging this is the third time it's bitten us and i'd like it to be the last.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "checkpoint design note assumes restarts happen on the same rank count and that the RNG is reseeded from the step, neither of which is true today. read it against the code and tell me which of its other assumptions have quietly stopped holding as our jobs got longer context if it helps: this has been open since before i joined the team.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "en"} -{"prompt": "three payment vendors have three client shapes, three error taxonomies and three copies of the offline voucher logic with slightly different conditions. put them behind one interface with one offline policy, keeping each vendor's on-the-wire behaviour exactly as it is, and make the differences visible in configuration rather than in branches", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "pipeline board is what recruiters have open all day and it currently renders four thousand cards eagerly and loses their filters on refresh. rebuild it to the spec — virtualised, filters in the URL, keyboard navigation, archived candidates visible rather than absent — without changing the drag interaction people are used to assume whoever picks it up next has no context beyond what you write.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "our careers-site API, which twelve customers embed in their own sites from a README:\n\nGET /v1/public/jobs?tenant=&location=&department=&remote=\n returns open jobs only; a job closed while a candidate is on the page 404s on apply\n ordering is by posted_at desc with no tie-break, so equal timestamps reorder between requests\n the description field is HTML we sanitise on write, not on read, and old records predate the sanitiser\nPOST /v1/public/applications\n multipart with a CV up to 10MB; larger uploads fail with a generic 400\n duplicate applications to the same job are accepted silently and appear twice to the recruiter\n the response is 201 with an application id that is not shown to the candidate anywhere\n\nwrite the reference for customers embedding this, and be explicit about the duplicate behaviour", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "the simulation group's list, with a paper deadline in eight weeks:\n\n- fix the checkpoint RNG position, which may invalidate results in the last two papers\n- decide on -ffast-math, which costs 18% if we remove it\n- fixed-order reduction, which costs 4% and a kernel rewrite\n- the 512-rank hang, which blocks the largest runs entirely\n- split the 4,000-line module so more than one person can work on it\n- job scripts that don't waste 88% of each node\n\none Fortran engineer, and the deadline is real but the correctness questions are older", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "HRIS field mapping is YAML plus four customer names hardcoded in the pusher, so onboarding a tenth customer means a deploy. move the special cases into the mapping format itself, keep every current customer's payload byte-identical, and add the test that proves it for each tell me if this is the wrong shape entirely, i won't be offended.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "a 512-rank job hangs at the same collective every time and the branch that broadcasts a convergence flag looks like the culprit. confirm it, then restructure the collectives so all ranks agree on what they're calling", "purpose": "debugging", "secondary": "refactor", "mixed": true, "difficulty": 0.9, "slice": "mixed", "lang": "en"} -{"prompt": "job list widget should degrade to plain server-rendered HTML when scripts are blocked", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "our runbook for the 09:00 application spike is \"watch the dashboard\". what the team actually does:\n\n- job adverts go out by email at 09:00 and the apply endpoint takes ten times its normal load for about twenty minutes\n- the first symptom is connection pool exhaustion, which shows as 500s on apply and nothing else\n- scaling the app up makes it worse, because each instance takes ten more connections\n- the actual mitigation is scaling down to 20 instances, which nobody believes until they try it\n- pgbouncer exists in staging and has never been enabled in production\n- if applications are lost rather than delayed, they are recoverable from the email bounce log, painfully\n\nwrite the runbook, and mark clearly that scaling up is the wrong instinct", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "the retailer's requirements for offline payments, which are now contractual:\n\n\"The point of sale shall continue to accept card payments when the payment terminal is temporarily unreachable, subject to a configurable per-store limit on the total value of offline transactions. Offline transactions shall be transmitted for authorisation within 15 minutes of connectivity being restored, without staff intervention. Declined offline transactions shall be reported to the store manager the same day. The system shall not permit offline acceptance for transactions above a configurable value.\"\n\nwe have no limits, no automatic retransmission except on restart, and no manager-facing report. i want the plan by contractual exposure", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "a walkthrough of how a scan becomes a stock movement would help before i touch idempotency", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "HRIS integration guide needs writing and i expect it will surface behaviours we should change rather than document — the silent failure after three retries especially. write the guide, and give me that list", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "careers widget documentation has to exist for the customers embedding it, and while writing it please confirm whether duplicate applications really are accepted silently, because support believes they're rejected", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "offline payments runbook for store managers should exist, and the till should stop printing vouchers past a sensible daily limit. write the runbook, then add the limit with a configurable default", "purpose": "writing", "secondary": "quickFix", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "interview emails show the wrong local time for candidates in other timezones, which looks like the formatter using the interviewer's zone. confirm that, then fix it and work out how many past emails were wrong so we can decide whether to apologise i've already spent an afternoon on it and got nowhere useful.", "purpose": "debugging", "secondary": "writing", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "is our job efficiency really 12%, or is the accounting measuring something else", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "what guarantees does the apply endpoint make once it has returned a 201 to the candidate", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "simulation writes trajectory output through three routines depending on format, and two of them buffer differently so a killed job loses a different amount of data. unify them behind one writer, and tell me which format's flush behaviour we should adopt given jobs are killed by the scheduler routinely this has come up in three separate reviews now and never gets done.", "purpose": "refactor", "secondary": "planning", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "job adverts should be verified by reading the posting back rather than trusting a 200, and we should decide first what we do when the read-back disagrees — retry, alert, or mark the advert failed. settle that, then implement flag anything you'd want to change before doing it rather than after.", "purpose": "backendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "candidate applications vanish between the form and the database, maybe five a day:\n\nPrismaClientUnknownRequestError: \nInvalid `prisma.application.create()` invocation:\nError occurred during query execution:\nConnectorError(ConnectorError { user_facing_error: None, kind: QueryError(PostgresError { code: \"53300\", message: \"remaining connection slots are reserved for non-replication superuser connections\" }) })\n at Ai.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:6412)\n at async POST (/app/app/api/apply/route.ts:88:22)\n\nconnection pool: 10 per instance, 40 instances behind the autoscaler, postgres max_connections 100\nthe apply endpoint is the only one that spikes, because job ads go out by email at 09:00", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "so our simulation gives different answers on the new cluster and i can't tell which is right:\n\n old cluster (gcc 11, -O2, AVX2): total energy = -1042.884112 Ha\n new cluster (gcc 14, -O3, AVX512): total energy = -1042.884109 Ha\n reference (published): total energy = -1042.884110 Ha\n\ncompiler flags on the new cluster: -O3 -march=native -ffast-math -funroll-loops\ncompiler flags on the old cluster: -O2 -march=haswell\n\nthe kernel sums a 4-million-element array of pair interactions in a plain loop, and the reduction order differs between the two builds", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "tills stop taking card payments in one store every afternoon, always around the same time:\n\n14:02:11.114 [pos-04] payment start amount=1240 currency=GBP\n14:02:11.882 [pos-04] terminal connect 192.168.10.44:9100\n14:02:41.902 [pos-04] terminal read timeout after 30s\n14:02:41.905 [pos-04] payment failed, offline voucher printed\n14:02:44.001 [pos-04] terminal connect 192.168.10.44:9100\n14:03:14.020 [pos-04] terminal read timeout after 30s\n\nstore wifi shows a channel change at 14:00 daily, which is when the bakery ovens come on, and the terminals are on wifi while the tills are wired", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "seit dem letzten Deploy verschwinden Bewerbungen aus dem Talent-Pool, aber nur bei einem Kunden:\n\nSELECT count(*) FROM applications WHERE tenant_id = 'acme' AND stage = 'pool';\n vor dem Deploy: 41.882\n nach dem Deploy: 1.204\n\nMigration aus dem Deploy:\n UPDATE applications SET stage = 'archived'\n WHERE stage = 'pool' AND updated_at < now() - interval '180 days';\n\nbei diesem Kunden werden Bewerbungen im Pool nicht angefasst, solange niemand sie öffnet, also ist updated_at das Erstellungsdatum; bei allen anderen Kunden läuft ein Nurturing-Job, der die Datensätze regelmäßig berührt", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "de"} -{"prompt": "ok so the POS app crashes on a specific till model when printing a receipt with more than about forty lines:\n\nFATAL EXCEPTION: main\nProcess: io.lumenpos.till, PID: 4412\njava.lang.OutOfMemoryError: Failed to allocate a 41943040 byte allocation with 12582912 free bytes\n\tat android.graphics.Bitmap.nativeCreate(Native Method)\n\tat io.lumenpos.print.ReceiptRenderer.renderToBitmap(ReceiptRenderer.kt:141)\n\tat io.lumenpos.print.PrintJob.execute(PrintJob.kt:88)\n\nwe render the whole receipt into one bitmap at 203dpi before sending it to the printer, and these tills have 1GB of RAM", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "could you look at the pooling before i sign this off? the 09:00 spike is what worries me:\n\nexport const prisma = new PrismaClient({\n datasources: { db: { url: process.env.DATABASE_URL } },\n})\n\n// route.ts\nexport async function POST(req: Request) {\n const body = await req.json()\n const application = await prisma.application.create({ data: { ...body } })\n await sendConfirmationEmail(application) // awaited, 400-800ms\n await notifyRecruiters(application) // awaited, fans out to up to 12 recipients\n return Response.json({ id: application.id })\n}\n\nforty instances, ten connections each, postgres allows a hundred, and the two awaits hold the request open for over a second", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "honestly the reduction kernel, which is where our numbers differ between clusters:\n\nsubroutine pair_energy(n, r, q, energy)\n integer, intent(in) :: n\n real(8), intent(in) :: r(3,n), q(n)\n real(8), intent(out) :: energy\n integer :: i, j\n energy = 0.0d0\n !$omp parallel do reduction(+:energy) private(j)\n do i = 1, n\n do j = i+1, n\n energy = energy + q(i)*q(j)/norm2(r(:,i) - r(:,j))\n end do\n end do\nend subroutine\n\nbuilt with -ffast-math on the new cluster, thread count differs between runs, and the result is quoted to ten significant figures in our papers", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "right, the idempotency handling for handheld scans, which i think is behind the stock drift:\n\n@PostMapping(\"/v1/scans\")\npublic ResponseEntity scan(@RequestBody ScanBatch batch) {\n for (Scan s : batch.scans()) {\n String key = s.deviceId() + \":\" + s.localId();\n if (seen.putIfAbsent(key, Boolean.TRUE) == null) {\n stock.apply(s.sku(), -s.qty(), \"scan\");\n }\n }\n return ResponseEntity.accepted().build();\n}\n\n`seen` is a Caffeine cache with a one hour expiry, localId is a device counter that resets on docking, and there are 400 handhelds across the estate", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "quick one — the checkpoint format's design note, written when jobs ran for eight hours rather than three weeks:\n\n## Checkpoint contents\nState arrays, the current step, the input parameters and the RNG seed. Written every 10,000 steps to the parallel filesystem.\n\n## Assumptions\n- A restart continues a run that would otherwise have been identical.\n- The RNG is reseeded deterministically from the seed and the step.\n- Checkpoints are read back on the same number of ranks.\n\n## Not covered\nRestarting on a different rank count. Changing the thermostat between restarts. Reproducibility across compilers.\n\nwe now restart on different rank counts routinely, and the RNG is not reseeded from the step at all", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "fyi the migration that archived a customer's talent pool, which i'd like reviewed before we write the recovery:\n\n-- 20260722_archive_stale_pool.sql\nUPDATE applications\n SET stage = 'archived', archived_at = now()\n WHERE stage = 'pool'\n AND updated_at < now() - interval '180 days';\n\n-- rollback (as written in the migration file)\n-- none\n\napplications has no history table; archived_at is the only trace; and updated_at means \"last touched by anything\", which for one tenant is the creation date because they don't run the nurturing job", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "heads up: the job scheduler script we hand to researchers, which i suspect is why jobs sit in the queue:\n\n#!/bin/bash\n#SBATCH --nodes=64\n#SBATCH --ntasks-per-node=8\n#SBATCH --cpus-per-task=16\n#SBATCH --time=24:00:00\n#SBATCH --exclusive\n#SBATCH --mem=0\n\nexport OMP_NUM_THREADS=16\nexport OMP_PLACES=cores\nsrun ./simulate input.dat\n\nthe cluster has 128 cores per node, our job asks for 8 tasks × 16 threads = 128, exclusive plus mem=0 takes the whole node, and the queue's backfill window is four hours", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "support's notes on the archived applications, which we need to turn into a customer explanation:\n\n- a migration archived applications in the talent pool that hadn't been updated in 180 days\n- for most customers a nurturing job touches these records, so almost nothing was archived\n- for one customer the nurturing job is disabled, so updated_at was the creation date and 40,000 records were archived\n- the records are not deleted; they're in the archived stage and can be moved back\n- moving them back individually is a click each; there is no bulk unarchive in the product\n- we can do it with a script, but archived_at is the only evidence of which records we touched\n\nwrite the customer explanation and the internal note about what we're doing to restore them", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "incident notes from the till outage, and the retailer wants a written explanation:\n\n14:02 store 44 reports card payments failing on all six tills\n14:20 other stores unaffected; store 44's terminals are on wifi, tills are wired\n14:35 store wifi logs show a channel change at 14:00, coinciding with the bakery ovens starting\n15:10 terminals moved to the wired network as a workaround, payments resume\n16:00 root cause: the terminals lose association during the channel change and our client has a 30 second read timeout with no retry\n17:30 during the outage, staff used offline vouchers for 412 transactions, of which 8 were later declined\n\nthe retailer's question is why a wifi hiccup takes down payments at all when the tills are wired", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "as notas da reunião sobre reprodutibilidade, para transformar em documento de decisão:\n\n- os resultados diferem entre o cluster antigo e o novo na décima casa decimal\n- a causa provável é -ffast-math combinada com uma redução OpenMP cuja ordem varia com o número de threads\n- publicámos valores com dez algarismos significativos em dois artigos\n- opções: fixar a ordem da redução, remover -ffast-math, ou passar a publicar com incerteza declarada\n- remover -ffast-math custa cerca de 18% de desempenho segundo o teste que fizemos\n- a ordem fixa custa cerca de 4% e obriga a reescrever o kernel\n\nescreve a nota de decisão com as opções, o custo de cada uma e uma recomendação para o grupo", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "pt"} -{"prompt": "small thing but the questions our new HPC customer's IT security team sent, which need answering as a document:\n\n\"What data does the job submission tool send to your servers, and can it operate fully offline? Where are user credentials stored on shared login nodes? Does your software write anything to a world-readable location? Can a user's job read another user's checkpoint data on the shared filesystem? How do you handle a job that exceeds its allocation — is it killed, and by whom? What telemetry do you collect from academic sites and can it be disabled?\"\n\nour honest answers are mixed at best; write the document from the code, and mark clearly which answers are \"not currently\" rather than presenting them as design decisions", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "社内向けに、レジ端末のオフライン運用手順が文書化されていません。現状は次の通りです:\n\n- カード端末が 30 秒応答しない場合、レジはオフラインバウチャーを印刷する（リトライはしない）\n- オフラインバウチャーは後で一括送信されるが、与信が通らない場合は店舗の損失になる\n- 一日あたりのオフライン上限は設定されておらず、先週は 412 件が積み上がった\n- レジ側のログはローカルにしか残らず、7 日で上書きされる\n- 店舗マネージャーはオフライン件数を確認する画面を持っていない\n- 復旧後の再送はレジの再起動時にのみ行われる\n\n設定例:\n\nterminal:\n read_timeout_ms: 30000\n retries: 0\n offline_voucher_limit: null\n\n店舗マネージャー向けの手順書として、また社内の開発者向けの注意点として、それぞれまとめてください\n\n先週のオフライン件数（店舗別、上位）:\n store 44 412 件 合計 £18,204 後日否認 8 件\n store 12 88 件 合計 £3,110 後日否認 1 件\n store 07 41 件 合計 £1,204 後日否認 0 件\n\n関連する設定とログ:\n\n terminal:\n read_timeout_ms: 30000\n retries: 0\n offline_voucher_limit: null\n resubmit_on: [\"app_start\"]\n\n 14:02:41 [pos-04] terminal read timeout after 30s\n 14:02:41 [pos-04] payment failed, offline voucher printed\n\n店舗マネージャーはこの数字をどこからも見られません", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "ja"} -{"prompt": "not urgent, but the ATS's integration guide for HR systems, written for one customer and now used by nine:\n\nwe push hires to the customer's HRIS on offer acceptance:\n POST {customer_endpoint}/employees with our own field names, mapped per customer in a YAML file\n retries: 3, then a support ticket is created and someone re-runs it by hand\n the mapping file lives in our repo, so a new field for one customer is a deploy\n four customers require a custom date format and two require a custom ID scheme\n nobody has documented which customer needs what; the YAML comments are the only record\n a failed push leaves the offer accepted in our system with no indication that the HRIS is out of sync\n\nwrite the integration guide, and separately list what should be configuration rather than code", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "eslint and tsc on the ATS, gate goes on next sprint:\n\napp/api/apply/route.ts:88:22 - error TS2345: Argument of type 'unknown' is not assignable to parameter of type 'ApplicationCreateInput'\napp/lib/mail.ts:41:9 - warning: Promise returned in function argument where a void return was expected @typescript-eslint/no-misused-promises\napp/lib/tenant.ts:141:3 - error TS2532: Object is possibly 'undefined'\napp/components/PipelineBoard.tsx:212:5 - warning: React Hook useEffect has a missing dependency: 'tenantId'\napp/lib/dates.ts:22:11 - error TS2769: No overload matches this call (formatInTimeZone)\n\n3 errors, 2 warnings, and dates.ts is the file behind the timezone emails", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "compiler warnings from the simulation build, which we've been ignoring for years:\n\nsrc/pair.f90:141:22: warning: 'energy' may be used uninitialized [-Wmaybe-uninitialized]\nsrc/io.f90:88:5: warning: array 'buf' is used uninitialized [-Wuninitialized]\nsrc/thermostat.f90:41:9: warning: comparison of real values with == [-Wfloat-equal]\nsrc/checkpoint.f90:212:13: warning: unused variable 'rng_pos' [-Wunused-variable]\nsrc/main.f90:22:1: warning: obsolescent feature: COMMON block\n\n41 warnings total; checkpoint.f90's unused rng_pos is exactly the variable our restart bug is about", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "genuinely puzzled by this: the till app's config across store types, and only the small stores crash:\n\n# flagship stores\nprint:\n render_mode: banded\n band_height_px: 512\n bitmap_config: ALPHA_8\ndevice: { ram_mb: 4096, android: 13 }\n\n# small stores\nprint:\n render_mode: single\n band_height_px: null\n bitmap_config: ARGB_8888\ndevice: { ram_mb: 1024, android: 11 }\n\nbanded rendering was added for the flagship rollout and never enabled anywhere else\n\nand the crash rate per store type over the last month:\n\n flagship (4GB, android 13, banded) 0 crashes / 41,882 receipts\n standard (2GB, android 12, single) 14 crashes / 88,214 receipts\n small (1GB, android 11, single) 412 crashes / 21,004 receipts\n\nevery crash is the same OutOfMemoryError in renderToBitmap, and the receipts that trigger it are stocktake reports and long promotional receipts", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"} -{"prompt": "slurm accounting for our group this month, and we're being asked why utilisation is low:\n\nJobID Nodes Elapsed CPUTime TotalCPU Efficiency\n881204 64 23:58:12 1536:00 184:12 11.9%\n881207 64 23:59:02 1536:00 201:44 13.1%\n881209 32 04:12:44 134:48 128:02 94.9%\n881211 64 23:58:44 1536:00 190:22 12.4%\n\nthe 64-node jobs request 8 tasks per node with 16 threads each on 128-core nodes, and the three long ones all hit the wall clock rather than converging", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "pasted-context", "lang": "en"} -{"prompt": "dependabot on the ATS, four open and one blocks the store submission:\n\nnext 15.1.0 → 15.4.2 (patch series; middleware behaviour changed for rewrites)\n@prisma/client 5.19 → 6.2 (major; connection pool defaults changed, `connection_limit` now per-process)\ndate-fns-tz 2.0.0 → 3.2.0 (major; formatInTimeZone signature changed)\nnodemailer 6.9.13 → 6.10.1 (patch)\n\nthe date-fns-tz major is the library our timezone bug is in, and the prisma major changes exactly the pooling behaviour we're fighting", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "pasted-context", "lang": "en"} -{"prompt": "les seuils d'alerte de la plateforme de recrutement, on nous réveille pour rien :\n\n- alert: ApplyErrorRate\n expr: rate(http_requests_total{route=\"/api/apply\",code=~\"5..\"}[5m]) > 0\n for: 1m\n labels: { severity: page }\n\n- alert: DbConnections\n expr: pg_stat_activity_count > 90\n for: 5m\n labels: { severity: ticket }\n\n- alert: SyncFailures\n expr: increase(partner_sync_failed_total[1h]) > 0\n for: 0m\n labels: { severity: ticket }\n\nen pratique : le taux d'erreur dépasse zéro tous les matins à 9h ; la saturation des connexions n'est qu'un ticket alors que c'est la cause ; et la synchronisation vers un job board renvoyait 200 tout en jetant nos annonces, donc aucune alerte n'a été déclenchée pendant trois semaines", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "pasted-context", "lang": "fr"} -{"prompt": "this module does I/O, domain decomposition and the physics in one file, and every change touches all three:\n\nmodule simulate\n ! reads input.dat, including three formats we've supported over the years\n ! decides the domain decomposition from the rank count\n ! allocates the state arrays\n ! runs the integrator, calling the pair kernel and the thermostat\n ! writes checkpoints and trajectory output\n ! handles MPI setup and teardown\nend module\n\n4,000 lines of Fortran, one test that runs a tiny system and compares against a stored trajectory", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "quarter planning input, needs sequencing:\n\n- 40,000 applications were archived by a migration at one customer and unarchiving them is manual\n- the 09:00 spike takes the apply endpoint down most mornings and scaling up makes it worse\n- our simulation results differ between clusters in the tenth significant figure, and we publish ten\n- the POS crash on small tills affects 300 stores and the workaround is telling staff to print shorter receipts\n- checkpoint restarts are silently wrong for long jobs, which may affect published work\n- one Fortran engineer, two platform engineers, and the POS team is three people\n- there's an HPC customer procurement in october with a security questionnaire we can't currently pass", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "architecture ticket, i want the thinking before code:\n\nATS-410 — Tenant isolation enforcement\nTenant scoping is applied by hand in fourteen places with three different patterns and at least one omission. The proposal is row-level security in postgres with the tenant set per connection, so a missing filter fails closed. Concerns: our connection pooler is transaction-scoped and the tenant would have to be set per transaction; some background jobs legitimately run across tenants; raw queries in reports bypass the ORM entirely; and we have no test that would catch a missing filter today, so we cannot prove the change is safe or that it was needed.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "spec for the till's payment screen, which cashiers use hundreds of times a day:\n\nPayment screen\n- Amount due in the largest type on the screen, unmissable from a metre away.\n- Payment method buttons at least 72dp tall, arranged so the most common method is under the thumb.\n- While waiting on the terminal: a progress state that names what is happening (\"waiting for card\", \"authorising\") rather than a generic spinner, with the elapsed seconds visible.\n- On timeout: an explicit choice — retry, or take the payment offline — never an automatic silent fallback.\n- Offline mode shows a persistent banner with the count and total value of offline transactions taken today.\n- Errors from the terminal are shown in the words the cashier needs (\"ask for another card\"), with the vendor code available on a long press for support.\n- The screen must be operable with gloves and must never require a precise tap.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "accessibility findings for the careers site widget, which our customers embed and are legally responsible for:\n\n1. The job list is a div soup with no list semantics and no headings, so screen reader users cannot navigate it.\n2. The filter controls are custom dropdowns with no keyboard support and no announced state.\n3. The apply form's file input is hidden behind a styled button with no label association.\n4. Required field errors appear only as red borders.\n5. The widget sets its own font size in px, overriding the host page's user scaling.\n6. Focus is trapped in the apply modal with no escape key handling.\n7. Colour contrast on the \"apply now\" button fails at 3.2:1 against our default background, which most customers keep.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "design tokens versus what the recruiter app actually uses:\n\ntokens:\n color.surface #FFFFFF / #0F1216\n color.text #0F1216 / #E8EDF3\n color.muted #626C76\n color.stage.new #0B62D6\n color.stage.offer #1A7F37\n color.stage.reject #B42318\n space 4/8/12/16/24/32, radius 6/10, focus 2px offset 2\n type: title 18/24, body 14/20, caption 12/16\n\nthe recruiter app: eight hardcoded colours including three blues, stage colour used as the only stage indicator on cards, focus removed on the card press target, paddings of 5/9/13/17, and a card title at 15px which is in no scale\n\nbring it onto the tokens and give stage a non-colour indicator on the card", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"} -{"prompt": "banded rendering on the small tills", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "date-fns-tz major, before the timezone fix", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "enable pgbouncer in production", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "rotate the job board API key", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"} -{"prompt": "el correo de entrevista sale sin zona horaria", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "es"} -{"prompt": "our database connection settings versus what postgres allows:\n\napp instances (autoscaler): min 10, max 60\nprisma connection_limit: 10 (default, not set explicitly)\npostgres max_connections: 100\npostgres superuser_reserved_connections: 3\npgbouncer: deployed in staging only, transaction pooling\n\nat 09:00 the autoscaler goes to 40+ instances within two minutes because the apply endpoint's latency rises, which is itself caused by connection contention\n\nand what 09:00 looks like from the database side:\n\n 08:58 connections 41 apply p95 180ms instances 12\n 09:00 connections 96 apply p95 2.4s instances 18\n 09:02 connections 100 apply p95 timeout instances 41\n 09:06 connections 100 apply 500s 38% instances 60 (autoscaler ceiling)\n 09:22 connections 44 apply p95 210ms instances 14\n\npg_stat_activity during the spike is almost entirely idle-in-transaction, which is the two awaited emails inside the request", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "the HRIS integration spec from our largest customer, which we implement:\n\nPOST /api/v2/employees\n auth: OAuth2 client credentials, token valid 15 minutes, their token endpoint rate limits to 1/minute\n body: their field names, dates as YYYY-MM-DD, employee id assigned by them and returned in the response\n a duplicate push for the same offer must be idempotent on our `external_ref`, which they store but do not index\n they respond 202 and process asynchronously; failures arrive by email to a shared mailbox, not by callback\n a rejected employee record leaves the offer accepted on our side with no automatic reconciliation\n they have a nightly maintenance window during which everything returns 503\n we push about 400 hires a month, in bursts on the first of the month", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "HRIS pusher should reconcile nightly rather than leaving an offer accepted and unsynced", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "a short note on why the apply endpoint is moving to a queue, for the decision log", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "drop -ffast-math from the release build", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "DbConnections should page, not ticket", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "cap prisma connections per instance", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "OMP_NUM_THREADS passt nicht zur Knotengröße", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "de"} -{"prompt": "uninitialised `energy` in pair.f90", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "archived candidates should be visible, not absent", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "求人ウィジェットの文字サイズが固定です", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "ja"} -{"prompt": "required errors are red borders only", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "terminal errors show vendor codes to cashiers", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "board drops frames past 2000 cards", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "split the 4000-line simulate module", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "un seul contrôle de locataire, partout", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "fr"} -{"prompt": "`stage` naming across the API", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "extract the offline voucher logic", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "inline `padLeft`, one caller", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "changelog for the POS release", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "nota aos clientes sobre as candidaturas arquivadas", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "pt"} -{"prompt": "document the duplicate application behaviour", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "summarise the tenant isolation proposal", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "PR body for the checkpoint fix", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "can a restart change published results?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "¿por qué el 09:00 tumba el endpoint de solicitudes?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "es"} -{"prompt": "walk me through the offer-to-HRIS push", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "card payments fail every afternoon in one store", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "warum unterscheiden sich die Ergebnisse je Cluster?", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "de"} -{"prompt": "endpoint for a store's offline transactions", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "carry it on", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "less flaky", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "pick the order yourself", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "lo del cluster, continúa", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "es"} -{"prompt": "scanners again", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "clean it as you go", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "same shape as last time", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "security answers for procurement", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "nothing that needs a deploy", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "give it a read", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "どれから着手するかはお任せします", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "ja"} -{"prompt": "next on the list", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "09:00 application spike takes down the apply endpoint most mornings and every instinct the team has — scaling up, raising the pool size — makes it worse. i'd like the actual capacity model worked out, including whether pgbouncer solves it or just moves the queue, and what the endpoint should do when it genuinely can't accept an application", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "twelve customers embed our careers widget in their own sites and are legally responsible for its accessibility, which is currently poor enough to be a problem for them. write the integration documentation, including the accessibility characteristics they're inheriting and what they can configure, without pretending the widget is in better shape than it is 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.7, "slice": "core", "lang": "en"} -{"prompt": "retailer wants a written explanation of why a wifi channel change in one store stopped card payments on wired tills, which is a fair question. write the incident report for their operations team — the terminal association, our timeout, the offline vouchers and the eight that were later declined — without hiding behind the word \"connectivity\"", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "runbook for the morning spike should say plainly that scaling up is the wrong instinct, because three separate people have made it worse that way. write it in the order someone would need at 09:05, with the connection maths spelled out so the advice is believable rather than folklore a rough ordering matters more to me than a complete answer right now.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "checkpoint format is detected by whether a field looks plausible, with no magic number and no version, and we now need to add the RNG position. give it a proper header with a version, keep reading both existing formats, and make an unrecognised file a clear error rather than a plausible misinterpretation i'd rather have the reasoning written down than a quick answer.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "payment screen currently falls back to offline silently on a timeout, which is how a store took four hundred vouchers without noticing. rebuild it to the spec — named progress states, an explicit choice on timeout, a persistent offline banner — and keep every tap target usable with gloves the sooner we know roughly how big this is, the better for planning.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "tenant isolation needs an approach decided and one concrete step taken. work through the options with me, then implement the repository-level scoping for the reports module, which is where the raw queries live", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "morning spike needs a capacity model and it needs the apply endpoint to stop dropping applications tomorrow. give me the model, then make the endpoint enqueue rather than write synchronously so a full pool delays rather than loses", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "our till's payment flow has three implementations depending on terminal vendor:\n\n// VendorA.kt — synchronous socket, 30s timeout, no retry\n// VendorB.kt — vendor SDK with callbacks, retries internally 3 times, reports only final failure\n// VendorC.kt — HTTP to a local bridge, 10s timeout, retries once, returns a different error taxonomy\n\nthe till's payment screen handles all three with a when(vendor) block in the view model, and offline voucher logic is duplicated in each branch with slightly different conditions", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "the schema we agreed for offline transactions, now it needs building on the till and the backend:\n\nCREATE TABLE offline_transactions (\n id uuid PRIMARY KEY,\n store_id uuid NOT NULL,\n till_id text NOT NULL,\n amount_cents bigint NOT NULL,\n currency char(3) NOT NULL,\n taken_at timestamptz NOT NULL,\n submitted_at timestamptz,\n outcome text CHECK (outcome IN ('approved','declined','expired')),\n card_ref text NOT NULL\n);\n\nthe till holds these locally until connectivity returns, submits within 15 minutes without staff action, enforces a per-store value limit and a per-transaction cap, and the store manager needs a same-day view of anything declined", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "unsere Offline-Zahlungen brauchen erst ein Konzept mit Limits und automatischer Nachübertragung und danach die Umsetzung der Limits auf der Kasse, weil das der vertraglich heikelste Teil ist", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "de"} -{"prompt": "escribe la guía del operador para el pico de las 09:00 y comprueba en el código si escalar instancias realmente empeora la situación, porque quiero poder demostrarlo y no solo afirmarlo", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "es"} -{"prompt": "active-application predicate exists three times and the report includes records the product hides. unify them, then document what each stage means, because \"archived\" apparently means two different things depending on which migration set it", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "receipt rendering should be banded everywhere rather than only on the flagship tills. make the change, and confirm from the store inventory how many devices are actually on the old configuration before we call it fixed", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.55, "slice": "mixed", "lang": "en"} -{"prompt": "fourteen tenant checks should become one mechanism, and i'd like to know first which of the fourteen is actually wrong rather than merely different. audit them, then unify", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "applications are lost rather than delayed during the morning spike, which the team assumes is the connection pool. verify that assumption end to end, then make the failure mode a delay rather than a loss", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "careers widget fails seven accessibility items and our customers carry the legal risk. fix them, and write the statement customers can put on their own accessibility pages", "purpose": "frontendImpl", "secondary": "writing", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "offline transaction limits need the semantics agreed — per store, per till, per day, and what happens at the boundary mid-transaction. decide that with me, then implement on both sides", "purpose": "backendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "i'd like to understand how the autoscaler decides to add instances during the spike", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "why does the nurturing job touch every pool record, and what does it actually change", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "is it expected that a job advert can be accepted by the board and then silently discarded", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "pouvez-vous m'expliquer comment le point de restauration gère un redémarrage sur un nombre de rangs différent ?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "fr"} -{"prompt": "docs/checkpoints.md claims restarts are bit-for-bit reproducible, which they are not", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "partner changelog needs an entry for the job board key rotation and what it broke", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "doc comment on renderToBitmap claims it streams, which it very much does not", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "write the note to affected candidates whose interview email showed the wrong time", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "health endpoint reports the sync healthy while the job board has discarded everything for three weeks", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "apply endpoint awaits two emails before responding, which holds a connection for over a second", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "staging runs one app instance and prod runs forty, with the same per-instance connection limit", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "how should we handle a customer who wants their ATS data in their own region", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "what's the right way to validate a simulation change when the reference is a published number", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "i want a position on whether the till should hold stock state locally or always ask the backend", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "three customers want single sign-on into the recruiter app with different providers", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "we need a plan for running the simulation on GPUs, which the next cluster procurement assumes", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "boundary", "lang": "en"} -{"prompt": "stores run four android versions and we've never dropped one", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "what should happen to a candidate's data when a customer leaves us", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "an endpoint that returns an application's full stage history with who moved it and when", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "pipeline board needs a bulk action bar that states how many candidates it will affect", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "simulation's progress output should be parseable rather than a wall of formatted text", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "whatever we can ship before the audit", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "rest of the till work", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "email templates format dates with the server's locale and timezone rather than the recipient's, which is the same class of bug as the interview emails but affects every template we send. centralise the formatting with the recipient's zone as the input, and tell me which templates change appearance for which recipients before we ship it", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "till keeps two receipt models, one for the printer and one for the customer copy, synchronised by hand and already divergent on discount lines. merge them, and confirm from the last month's receipts whether any customer copy has actually shown a different total from the printed one it doesn't have to be elegant, it has to be defensible in a review.", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "internal page on the apply pipeline stops at \"the form posts to the API\", and everything after — the two awaited emails, the recruiter fan-out, the connection cost of each — is why nobody understands the morning spike. write the page properly, following one application from the form to the recruiter's inbox", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"} -{"prompt": "job scripts we hand researchers request eight tasks of sixteen threads on 128-core nodes and then take the whole node exclusively, which is most of our reported 12% efficiency. fix the templates, and add a comment explaining the arithmetic so the next person doesn't quietly restore the old numbers there's no rush on this week specifically, but it keeps costing us time.", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "nobody has been able to tell me what happens to an offer when the HRIS push fails all three attempts — whether the ticket that gets created is actually worked, whether the offer shows any sign of being unsynced, and how the customer finds out. trace it end to end and tell me how many offers are currently in that state", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "recruiter reports module builds its queries with raw SQL and a tenant id interpolated by hand, and one of them takes the tenant from a query parameter rather than the session. read the module and tell me whether a recruiter can reach another tenant's data today, with the specific request that would do it if so", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "simulation reads input files three different ways and two of them treat comment characters differently, which means the same input file can produce two different runs depending on which path parses it. unify the reader, and check whether any of our stored regression inputs relies on the lenient behaviour the last person who touched this left, so there's nobody to ask.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "`Application.stage` is a pipeline stage in the API, a lifecycle state in the database and something in between in the reports, which is why archived means two different things. give the concepts separate names and migrate the data, keeping the API's field names unchanged for the customers embedding our widget i'd like enough detail that i can hand it to someone else to finish.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "scan idempotency needs a device-persistent identifier rather than a counter that resets when a handheld is docked, which means the handhelds need a stable id we can trust across firmware updates and battery swaps. design that with the constraint that four hundred devices are already in stores, then implement the backend side we've been burned by guessing at this before, so evidence over instinct please.", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "a manager screen showing today's offline transactions and their outcomes is now contractual, and it has to work on the till itself because that's the only device a store manager has. build it against the offline transaction table, including the declined ones from previous days that nobody has acknowledged if the answer is that it's fine as it is, that's a useful answer too.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "stock levels", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "one receipt model, not two", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "ATS has three ways of resolving the current tenant — a session field, a header the reports module trusts, and a query parameter one legacy endpoint still accepts — and new code copies whichever it finds first. reduce it to one resolution path with the others explicitly rejected, and keep every current client working while we migrate them", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "till's stock cache, the backend's stock table and the handheld's local queue are three views of the same number that reconcile only overnight, which is why staff trust none of them. bring them onto one model with explicit staleness, keeping the till usable while offline, and tell me what changes about the numbers staff see during the day", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "interview scheduling logic exists in the API and again in the calendar sync worker, and they disagree about what happens when an interviewer declines after the candidate has confirmed. consolidate them, with the API's behaviour as the reference, and list every scheduled interview whose state would differ under the unified logic", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "before i approve the offline limits work, i'd like to understand what the till currently does when a card is declined for an offline voucher taken three days ago — whether the customer is contacted, whether the store absorbs it, and whether anything in the product records that it happened at all", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "HRIS pusher should reconcile nightly rather than leaving an offer accepted on our side and absent from the customer's system with nothing to indicate the divergence. build the reconciliation against their employee list endpoint, handle their nightly maintenance window, and make a persistent divergence visible to the recruiter rather than only to us", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} +{"prompt":"Compare the old and new NorthstarCopperBridgeFlow adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Please resist widening this one: NorthstarHarborIndexService works, but staging still carries a setting that production corrected last month. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarHarborIndexService\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Spell NorthstarBirchMigratorStore's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Request: Incident timeline — INC-54138\n\n08:02 deploy NorthstarIrisBatchFlow 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 NorthstarIrisBatchFlow 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":"Match NorthstarMicaProfileService's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"UI ticket DES-54110: finish the compact NorthstarOpalRouterFlow filter experience\n\nRoute: /catalog/search\nSource: projects/northstar/internal/auth/refresh.go\nFramework: Spring Boot\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 NorthstarOpalRouterFlow 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":"Goal: # projects/northstar/workers/thumbnail/consumer.ex\n[worker.northstaramberfilterflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.northstaramberfilterflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.northstaramberfilterflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.NorthstarAmberFilterFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-54139\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/northstar/workers/thumbnail/consumer.ex. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"pasted-context","lang":"en"} +{"prompt":"diff --git a/projects/northstar/src/sync/reconcile.ts b/projects/northstar/src/sync/reconcile.ts\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/src/sync/reconcile.ts\n+++ b/projects/northstar/src/sync/reconcile.ts\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 NorthstarCraneWorkspaceCoordinator'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":"UI ticket DES-54148: finish the compact NorthstarFernSnapshotFlow filter experience\n\nRoute: /catalog/search\nSource: projects/northstar/db/migrations/20260730_events.sql\nFramework: Kotlin coroutines\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring NorthstarFernSnapshotFlow'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":"PM is preparing the NorthstarMoonlitSDKStore rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarMoonlitSDKStore\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Give NorthstarKiteSchedulerService a README example","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"The NorthstarFrostPanelStore 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":"A previously stable test around NorthstarMosaicGridService 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":"Symptom: Incident timeline — INC-54126\n\n08:02 deploy NorthstarBasilRunnerFlow 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 NorthstarBasilRunnerFlow 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":"Milestones for replacing NorthstarMapleQueueStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"NorthstarMarbleTokenService needs an idempotent replay endpoint backed by Cloudflare Workers; accept a cursor, cap each page at 500 items, and return a stable continuation token.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"NorthstarCoralUploadStore 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":"NorthstarMoonlitSDKCoordinator: diagnose, then document","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"NorthstarQuartzPlayerCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"# CI job 54132: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: Kafka\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] NorthstarKiteSchedulerFlowIntegration.replays_after_timeout ... ok\n[test] NorthstarKiteSchedulerFlowIntegration.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 \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\nReconstruct the NorthstarKiteSchedulerFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Headsup: // projects/northstar/Sources/CLI/Commands/Doctor.swift\nfinal class NorthstarCinderAuthFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 NorthstarCinderAuthFlow 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":"Bring NorthstarAtlasSearchStore'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":"In projects/northstar/packages/api/openapi.yaml hat NorthstarNovaPickerService ein sporadisches Problem im GraphQL-Ablauf. Verfasse eine Consumer-Doku mit Vertrag, Fehlern, Retry und einem kopierbaren Beispiel; ändere keinen Handler.\n\nRandbedingungen:\n- GraphQL weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf NorthstarNovaPickerService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um NorthstarNovaPickerService mit GraphQL kompatibel.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"de"} +{"prompt":"NorthstarTideWorkerFlow returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/northstar/ui/settings/PrivacyPane.tsx and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Match NorthstarEchoRegistryService's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Two deliverables are holding up NorthstarOspreyJobCoordinator. First, assess ownership and failure handling in projects/northstar/Sources/CLI/Commands/Doctor.swift. In the same workstream, capture the contract and rollback note for consumers. The relevant starting point is projects/northstar/Sources/CLI/Commands/Doctor.swift, which follows Kafka conventions and currently suffers from lost focus when the drawer animation finishes. Make rollback possible without deleting user data.\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":"review","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"FYI: # projects/northstar/src/sync/reconcile.ts\n[worker.northstarnimbusformflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.northstarnimbusformflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.northstarnimbusformflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.NorthstarNimbusFormFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-54118\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/northstar/src/sync/reconcile.ts. 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":"NorthstarLumenChartCoordinator: diagnose, then document","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"The NorthstarCedarPolicyFlow 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":"NorthstarFlintTimelineCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Before we approve NorthstarOrbitSyncStore, assess whether a misleading timeout name used in five packages is an actual correctness risk or merely confusing structure. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"We expect NorthstarDeltaCanvasStore to outgrow its current Spring Boot arrangement next quarter, but changing everything at once would be risky. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- make rollback possible without deleting user data\n- stay compatible with the existing Spring Boot deployment\n- keep the work scoped to NorthstarDeltaCanvasStore and its direct tests\n\nSeveral teams work in this developer tools, Java, WebGL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Does NorthstarEchoRegistryStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-54116\n\n08:02 deploy NorthstarGarnetModalFlow 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 NorthstarGarnetModalFlow 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":"I inherited NorthstarCopperBridgeService and need a careful read of projects/northstar/web/components/FilterDrawer.vue before I can sign off on the next release. 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- make rollback possible without deleting user data\n- stay compatible with the existing Spring Boot deployment\n- keep the work scoped to NorthstarCopperBridgeService and its direct tests\n\nSeveral teams work in this developer tools, Java, WebGL 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":"diff --git a/projects/northstar/pkg/cache/lease.rs b/projects/northstar/pkg/cache/lease.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/pkg/cache/lease.rs\n+++ b/projects/northstar/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\nRead the artifact above as a skeptical reviewer. Is NorthstarFrostPanelFlow'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":"Give NorthstarBirchMigratorService a README example","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Pin NorthstarWillowCodecStore's Kotlin dependency","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Meanwhile: diff --git a/projects/northstar/config/staging.toml b/projects/northstar/config/staging.toml\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/config/staging.toml\n+++ b/projects/northstar/config/staging.toml\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 NorthstarBeaconStoreFlow'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":"Ownership of NorthstarPrismCacheStore is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Kotlin coroutines operational envelope\n\nThe relevant code crosses developer tools, Java, WebGL. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"NorthstarOrbitSyncService occasionally exhibits two validators with subtly different error strings, but only after a reconnect. Follow the data and cancellation paths in projects/northstar/infra/modules/edge/main.tf and identify the cause before changing anything.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"En projects/northstar/config/staging.toml, NorthstarNovaPickerStore tiene un problema intermitente en el flujo de GraphQL. Propón fases, compatibilidad, métricas, rollback y ownership; detente antes de tocar código.\n\nRestricciones:\n- seguir con GraphQL\n- conservar compatibilidad y cancelación\n- limitar el cambio a NorthstarNovaPickerStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con GraphQL alrededor de NorthstarNovaPickerStore.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"es"} +{"prompt":"Locally: The NorthstarQuartzPlayerStore surface in projects/northstar/services/ledger/replay.go 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":"NorthstarAtlasSearchService's metric is misspelled as succesful_total in one declaration. Correct that literal and its exact test expectation, without renaming anything else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Production: The API work is done; what remains for NorthstarPineMetricsService is the visible interaction layer across loading, offline, empty, and success cases. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarPineMetricsService\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Staging: The NorthstarSlateEditorService empty state in projects/northstar/ml/pipeline/features.py needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-54114\n\n08:02 deploy NorthstarSableParserFlow 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 NorthstarSableParserFlow 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":"Is NorthstarVelaDrawerStore safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"CI: The NorthstarAmberFilterStore surface in projects/northstar/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":"Investigate the NorthstarBasilRunnerService hang","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Atlas: Incident timeline — INC-54130\n\n08:02 deploy NorthstarDriftConsoleFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current NorthstarDriftConsoleFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current NorthstarOpalRouterService design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarOpalRouterService\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"What does NorthstarFlintTimelineStore own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-54121: retire the legacy replay path for NorthstarMicaProfileFlow\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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Capture the NorthstarMicaProfileFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"NorthstarNimbusFormCoordinator: correct, then assess","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Beacon: The minimum supported Cloudflare Workers version in projects/northstar/engine/render/atlas.cpp 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":"NorthstarAmberFilterCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"diff --git a/projects/northstar/packages/api/openapi.yaml b/projects/northstar/packages/api/openapi.yaml\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/packages/api/openapi.yaml\n+++ b/projects/northstar/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\nRestructure NorthstarMapleQueueFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"NorthstarSlateEditorCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Test Suite 'NorthstarPineMetricsCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[NorthstarPineMetricsCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/northstar/packages/api/openapi.yaml:144: error: -[NorthstarPineMetricsCoordinatorTests 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 '-[NorthstarPineMetricsCoordinatorTests 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 NorthstarPineMetricsCoordinator's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"What sequence would let NorthstarAmberFilterService adopt Cloudflare Workers 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.8,"slice":"core","lang":"en"} +{"prompt":"Set NorthstarLumenChartStore's port to 8081","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"For NorthstarWillowCodecCoordinator, separate NorthstarWillowCodecCoordinator's policy from transport without behavior changes; once that is complete, capture the contract and rollback note for consumers. Work from projects/northstar/src/sync/reconcile.ts, stay with Kotlin coroutines, and make rollback possible without deleting user data. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Cinder: Incident timeline — INC-54152\n\n08:02 deploy NorthstarCedarPolicyCoordinator 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 NorthstarCedarPolicyCoordinator 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":"Delta: diff --git a/projects/northstar/infra/modules/edge/main.tf b/projects/northstar/infra/modules/edge/main.tf\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/infra/modules/edge/main.tf\n+++ b/projects/northstar/infra/modules/edge/main.tf\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is NorthstarOrbitSyncFlow'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":"Documente o contrato de NorthstarEmberRelayService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"pt"} +{"prompt":"NorthstarMapleQueueService leaks tasks on shutdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"The name pendingAck means two different things across NorthstarHarborIndexStore's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Design handed over a final pass for NorthstarTideWorkerStore, and the basic data flow in projects/northstar/workers/thumbnail/consumer.ex already works. 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- make rollback possible without deleting user data\n- stay compatible with the existing Cloudflare Workers deployment\n- keep the work scoped to NorthstarTideWorkerStore and its direct tests\n\nSeveral teams work in this developer tools, Java, WebGL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Move NorthstarVelaDrawerService behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"NorthstarCinderAuthCoordinator: diagnose, then correct","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"NorthstarSlateEditorStore's metric is misspelled as succesful_total in one declaration. Correct that literal and its exact test expectation, without renaming anything else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Ember: What is the safest way to split projects/northstar/apps/console/routes/usage.svelte into independently owned modules while NorthstarRainfallDBStore's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"} +{"prompt":"NorthstarSableParserCoordinator is blocking the next release because an accessibility label that reads the internal enum. I need two concrete outcomes from a single pass: change NorthstarSableParserCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing Cloudflare Workers conventions in projects/northstar/engine/render/atlas.cpp; make rollback possible without deleting user data. 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":"Security flagged NorthstarGarnetModalStore for a read-only pass because its GraphQL boundary mixes tenant data, retries, and cancellation in subtle ways. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current GraphQL operational envelope\n\nThe relevant code crosses developer tools, Java, WebGL. Prefer evidence from the repository and make any assumption explicit.\n\nNothing is reported broken, so judge and explain current behavior without inventing a failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-54129: retire the legacy replay path for NorthstarEchoRegistryFlow\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À partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Assess NorthstarEchoRegistryFlow for durability, tenant isolation, races, and misleading observability. Separate blockers from questions and do not produce a patch.","purpose":"planning","secondary":"review","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"Corrige le timeout de NorthstarEmberRelayStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"fr"} +{"prompt":"// projects/northstar/services/ledger/replay.go\nfinal class NorthstarDeltaCanvasFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 NorthstarDeltaCanvasFlow; 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":"NorthstarEmberRelayCoordinator needs a paired pass: assess ownership and failure handling in projects/northstar/cmd/exporter/main.py, plus capture the contract and rollback note for consumers. Use projects/northstar/cmd/exporter/main.py as the source of truth, preserve the Kafka contract, and avoid unrelated cleanup.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"We expect NorthstarCraneWorkspaceService to outgrow its current Kotlin coroutines arrangement next quarter, but changing everything at once would be risky. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- make rollback possible without deleting user data\n- stay compatible with the existing Kotlin coroutines deployment\n- keep the work scoped to NorthstarCraneWorkspaceService and its direct tests\n\nSeveral teams work in this developer tools, Java, WebGL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"projects/northstar/services/ledger/replay.go 里的 NorthstarSummitProxyService 最近在 Spring Boot 流程中出现间歇性问题。 请实现幂等 endpoint，包含持久 cursor、tenant 鉴权、spans 和 retry 测试。\n\n约束：\n- 继续使用 Spring Boot\n- 保持兼容性和取消语义\n- 改动只限于 NorthstarSummitProxyService","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"NorthstarVelaDrawerCoordinator needs a paired pass: separate NorthstarVelaDrawerCoordinator's policy from transport without behavior changes, plus give the existing implementation a read-only safety pass. Use projects/northstar/app/src/main/SyncWorker.kt as the source of truth, preserve the Kotlin coroutines contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Document NorthstarSableParserService's cancellation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Frost: Ticket OPS-54111: retire the legacy replay path for NorthstarNovaPickerFlow\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 NorthstarNovaPickerFlow 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":"Garnet: projects/northstar/app/src/main/SyncWorker.kt の NorthstarWrenExportService で、Kotlin coroutines の flow に断続的な問題が起きています。 責務を分離して重複をなくし、API、wire value、順序、観測可能な動作は変えないでください。\n\n制約:\n- Kotlin coroutines を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は NorthstarWrenExportService のみ","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"ja"} +{"prompt":"Persist NorthstarQuartzPlayerService delivery attempts in projects/northstar/web/components/FilterDrawer.vue, 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":"diff --git a/projects/northstar/app/src/main/SyncWorker.kt b/projects/northstar/app/src/main/SyncWorker.kt\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/app/src/main/SyncWorker.kt\n+++ b/projects/northstar/app/src/main/SyncWorker.kt\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure NorthstarWrenExportFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Flip NorthstarMicaProfileStore's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fresh release brief for NorthstarPrismCacheCoordinator:\n- primary outcome: produce a consumer guide for NorthstarPrismCacheCoordinator\n- companion outcome: give the existing implementation a read-only safety pass\n- repository entry point: projects/northstar/app/src/main/SyncWorker.kt\n- platform constraint: Kotlin coroutines\n- known complication: timestamps rendered one day ahead near UTC midnight\n\nBoth results are required, but they should remain independently reviewable. Make rollback possible without deleting user data; 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":"writing","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Move NorthstarMoonlitSDKService behind one protocol","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Harbor: Ticket OPS-54159: retire the legacy replay path for NorthstarTideWorkerCoordinator\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for NorthstarTideWorkerCoordinator, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"The name pendingAck means two different things across NorthstarMarbleTokenStore's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Iris: projects/northstar/lib/codec/frame.cc now contains NorthstarAcornWidgetStore'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":"This should remain a deliberately small patch: NorthstarCedarPolicyService has one known configuration mistake in projects/northstar/Sources/CLI/Commands/Doctor.swift, not an open-ended failure investigation. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- make rollback possible without deleting user data\n- stay compatible with the existing Kafka deployment\n- keep the work scoped to NorthstarCedarPolicyService and its direct tests\n\nSeveral teams work in this developer tools, Java, WebGL monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Juniper: diff --git a/projects/northstar/db/migrations/20260730_events.sql b/projects/northstar/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/db/migrations/20260730_events.sql\n+++ b/projects/northstar/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is NorthstarWillowCodecFlow'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":"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_54145'\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_54145'::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\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Find the source of this NorthstarQuartzPlayerFlow symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Kestrel: The public surface of NorthstarCloudReconcilerService is frozen, but its internal ownership in projects/northstar/ml/pipeline/features.py is difficult to test and even harder to change safely. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarCloudReconcilerService\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Animate the NorthstarCinderAuthService drawer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"NorthstarMarbleTokenCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"NorthstarTideWorkerService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Cloudflare Workers operational envelope\n\nThe relevant code crosses developer tools, Java, WebGL. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Lumen: Ticket OPS-54157: retire the legacy replay path for NorthstarCloudReconcilerCoordinator\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 NorthstarCloudReconcilerCoordinator 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":"Maple: What sequence would let NorthstarCloudReconcilerStore adopt Kafka 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.8,"slice":"core","lang":"en"} +{"prompt":"Nimbus: # projects/northstar/apps/console/routes/usage.svelte\n[worker.northstarveladrawerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.northstarveladrawerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.northstarveladrawerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.NorthstarVelaDrawerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-54133\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/northstar/apps/console/routes/usage.svelte. 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":"UI ticket DES-54154: finish the compact NorthstarHarborIndexCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/northstar/lib/codec/frame.cc\nFramework: Cloudflare Workers\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring NorthstarHarborIndexCoordinator'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":"NorthstarIrisBatchStore's staging timeout is already known to be wrong: change the single projects/northstar/db/migrations/20260730_events.sql value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-54134\n\n08:02 deploy NorthstarMarbleTokenFlow 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 NorthstarMarbleTokenFlow 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":"Ticket OPS-54119: retire the legacy replay path for NorthstarRavenSessionFlow\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 NorthstarRavenSessionFlow 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":"NorthstarIrisBatchCoordinator: smooth out this interaction","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"NorthstarSummitProxyCoordinator: ship a sensible version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Opal: projects/northstar/Sources/CLI/Commands/Doctor.swift has grown through several launches, and NorthstarOspreyJobStore now mixes policy, transport, persistence, and metrics in one place. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- make rollback possible without deleting user data\n- stay compatible with the existing Kafka deployment\n- keep the work scoped to NorthstarOspreyJobStore and its direct tests\n\nSeveral teams work in this developer tools, Java, WebGL 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":"Prism: projects/northstar/apps/console/routes/usage.svelte 里的 NorthstarWrenExportStore 最近在 Kotlin coroutines 流程中出现间歇性问题。 请完成 responsive layout、空状态、retry、键盘焦点、dark mode 和 reduced motion。\n\n约束：\n- 继续使用 Kotlin coroutines\n- 保持兼容性和取消语义\n- 改动只限于 NorthstarWrenExportStore","purpose":"frontendImpl","secondary":"debugging","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"zh"} +{"prompt":"Clarify NorthstarSpruceDaemonStore's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Quartz: The NorthstarBeaconStoreService surface in projects/northstar/config/staging.toml 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":"diff --git a/projects/northstar/cmd/exporter/main.py b/projects/northstar/cmd/exporter/main.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/cmd/exporter/main.py\n+++ b/projects/northstar/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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Deliver the NorthstarAtlasSearchFlow server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"Raven: projects/northstar/config/staging.toml の NorthstarPineMetricsFlow で、GraphQL の flow に断続的な問題が起きています。 現在の flow を読み、ownership、cancel、順序が安全か評価してください。分析だけで十分です。\n\n制約:\n- GraphQL を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は NorthstarPineMetricsFlow のみ","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"} +{"prompt":"Sable: The first NorthstarPineMetricsStore request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"For NorthstarSpruceDaemonCoordinator, assess ownership and failure handling in projects/northstar/services/ledger/replay.go; once that is complete, capture the contract and rollback note for consumers. Work from projects/northstar/services/ledger/replay.go, stay with Spring Boot, and make rollback possible without deleting user data. Keep the two outcomes separately reviewable.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Draft NorthstarDeltaCanvasService's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Two asks around NorthstarEchoRegistryCoordinator: (1) finish NorthstarEchoRegistryCoordinator's responsive empty and retry states; (2) capture the contract and rollback note for consumers. Make rollback possible without deleting user data, and leave a clear boundary between the resulting artifacts or edits.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Test Suite 'NorthstarLedgerGateFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[NorthstarLedgerGateFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/northstar/ui/settings/PrivacyPane.tsx:144: error: -[NorthstarLedgerGateFlowTests 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 '-[NorthstarLedgerGateFlowTests 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\nFinish the visible NorthstarLedgerGateFlow 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":"The minimum supported Kotlin coroutines version in projects/northstar/src/sync/reconcile.ts 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":"Is there a cleaner way to separate NorthstarCloudReconcilerFlow'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":"NorthstarAtlasSearchCoordinator: make the api less awkward","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Introduce a durable deduplication key for NorthstarCraneWorkspaceFlow 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":"Tide: The API work is done; what remains for NorthstarCraneWorkspaceStore is the visible interaction layer across loading, offline, empty, and success cases. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarCraneWorkspaceStore\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Split NorthstarFlintTimelineService without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Before we approve NorthstarFernSnapshotService, assess whether an empty state that flashes before cached data arrives is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Fresh release brief for NorthstarOpalRouterCoordinator:\n- primary outcome: lay out a staged migration for NorthstarOpalRouterCoordinator\n- companion outcome: then implement the bounded durable-cursor handler\n- repository entry point: projects/northstar/infra/modules/edge/main.tf\n- platform constraint: Spring Boot\n- known complication: an empty state that flashes before cached data arrives\n\nBoth results are required, but they should remain independently reviewable. Make rollback possible without deleting user data; retain serialization and authorization boundaries; cover cancellation, idempotent retries, and rollback; and avoid drive-by cleanup. Use the code as the source of truth, call out assumptions, and state how an on-call engineer can tell that either part is unsafe to ship.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"NorthstarRainfallDBFlow returns one extra item only when the page boundary lands on a deleted record. Reconstruct the cursor transitions in projects/northstar/app/src/main/SyncWorker.kt and find where the invariant breaks.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"projects/northstar/infra/modules/edge/main.tf now contains NorthstarJuniperCLIFlow'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":"NorthstarRavenSessionService est-il sûr ?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"fr"} +{"prompt":"Ticket OPS-54153: retire the legacy replay path for NorthstarRainfallDBCoordinator\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 を維持し、根拠と判断を明確にしてください。 Assess NorthstarRainfallDBCoordinator 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":"Responsive layout for NorthstarKiteSchedulerStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Find NorthstarDriftConsoleService's duplicate retry source","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Umbra: Ticket OPS-54127: retire the legacy replay path for NorthstarEmberRelayFlow\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 NorthstarEmberRelayFlow 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":"NorthstarFrostPanelCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"PM is preparing the NorthstarPrismCacheService rollout and needs prose that works for both application developers and the operators who will carry the pager. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarPrismCacheService\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Split projects/northstar/workers/thumbnail/consumer.ex by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"projects/northstar/pkg/cache/lease.rs now contains NorthstarFrostPanelService'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.4,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-54136\n\n08:02 deploy NorthstarMosaicGridFlow 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 NorthstarMosaicGridFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Introduce a durable deduplication key for NorthstarCoralUploadService 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":"Sequence NorthstarNimbusFormStore's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Move NorthstarBeaconStoreStore'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":"Vela: Ticket OPS-54123: retire the legacy replay path for NorthstarLumenChartFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for NorthstarLumenChartFlow, 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":"Test Suite 'NorthstarPrismCacheFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[NorthstarPrismCacheFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/northstar/apps/console/routes/usage.svelte:144: error: -[NorthstarPrismCacheFlowTests 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 '-[NorthstarPrismCacheFlowTests 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\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Finish the visible NorthstarPrismCacheFlow state described above: responsive layout, correct selection restoration, keyboard focus, accessible labels, dark mode, and reduced-motion behavior.","purpose":"debugging","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Walk through NorthstarBasilRunnerStore's segment.rs","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/northstar/web/components/FilterDrawer.vue b/projects/northstar/web/components/FilterDrawer.vue\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/web/components/FilterDrawer.vue\n+++ b/projects/northstar/web/components/FilterDrawer.vue\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure NorthstarSpruceDaemonFlow 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":"NorthstarAcornWidgetCoordinator: handle the lingering thing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"For NorthstarMapleQueueCoordinator, produce a consumer guide for NorthstarMapleQueueCoordinator; once that is complete, give the existing implementation a read-only safety pass. Work from projects/northstar/config/staging.toml, stay with GraphQL, and make rollback possible without deleting user data. Keep the two outcomes separately reviewable.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"NorthstarGarnetModalCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Ownership of NorthstarJuniperCLIService is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Spring Boot operational envelope\n\nThe relevant code crosses developer tools, Java, WebGL. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"On compact widths, NorthstarCedarPolicyStore'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":"Two asks around NorthstarBasilRunnerCoordinator: (1) separate NorthstarBasilRunnerCoordinator's policy from transport without behavior changes; (2) correct the known stale timeout beside it. Make rollback possible without deleting user data, and leave a clear boundary between the resulting artifacts or edits.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"NorthstarFernSnapshotCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Design the NorthstarGarnetModalService rollback","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Willow: Two deliverables are holding up NorthstarDeltaCanvasCoordinator. First, produce a consumer guide for NorthstarDeltaCanvasCoordinator. In the same workstream, correct the known stale timeout beside it. The relevant starting point is projects/northstar/web/components/FilterDrawer.vue, which follows Spring Boot conventions and currently suffers from lease renewal code copied across three workers. Make rollback possible without deleting user data.\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":"writing","secondary":"quickFix","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"NorthstarJuniperCLIStore 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":"Give NorthstarWillowCodecService a loading skeleton","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"NorthstarMosaicGridCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"NorthstarOrbitSyncCoordinator: sort out the rough edge","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"NorthstarWrenExportCoordinator: give it a nicer flow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"The minimum supported GraphQL version in projects/northstar/pkg/cache/lease.rs 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":"Read projects/northstar/pkg/cache/lease.rs and tell me whether NorthstarAsterWebhookFlow can acknowledge work before its durable write completes; this is a read-only safety pass. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"NorthstarBeaconStoreCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Xylem: # projects/northstar/services/ledger/replay.go\n[worker.northstarsummitproxyflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.northstarsummitproxyflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.northstarsummitproxyflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.NorthstarSummitProxyFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-54135\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 NorthstarSummitProxyFlow'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":"Spell NorthstarNimbusFormService's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"NorthstarLedgerGateCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Yarrow: # projects/northstar/services/ledger/replay.go\n[worker.northstarcopperbridgecoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.northstarcopperbridgecoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.northstarcopperbridgecoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.NorthstarCopperBridgeCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-54155\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/northstar/services/ledger/replay.go and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Zephyr: The behavior of NorthstarOpalRouterStore is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/northstar/infra/modules/edge/main.tf. 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- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Spring Boot operational envelope\n\nThe relevant code crosses developer tools, Java, WebGL. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"En projects/northstar/app/src/main/SyncWorker.kt, NorthstarRainfallDBService tiene un problema intermitente en el flujo de Kotlin coroutines. Separa responsabilidades y elimina duplicación, conservando API, wire values, orden y comportamiento observable.\n\nRestricciones:\n- seguir con Kotlin coroutines\n- conservar compatibilidad y cancelación\n- limitar el cambio a NorthstarRainfallDBService","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"es"} +{"prompt":"Checkout: // projects/northstar/engine/render/atlas.cpp\nfinal class NorthstarAcornWidgetFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 NorthstarAcornWidgetFlow'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":"Nobody is asking for code changes yet; we first need to understand whether the current NorthstarSableParserStore design actually guarantees what its callers assume. 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- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside NorthstarSableParserStore\n- make rollback possible without deleting user data\n\nThis repository spans developer tools, Java, WebGL; use its existing conventions rather than importing a new abstraction.\n\nNothing is reported broken, so judge and explain current behavior without inventing a failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Remove NorthstarDriftConsoleStore's stray comma","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"NorthstarMicaProfileCoordinator: ship, then assess","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Add a bounded NorthstarHarborIndexFlow export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Two engineers disagree about whether NorthstarCopperBridgeStore's cache is authoritative. Walk the reads and writes in projects/northstar/services/ledger/replay.go and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Exporter: // projects/northstar/Sources/App/SessionStore.swift\nfinal class NorthstarOspreyJobFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 NorthstarOspreyJobFlow 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":"Scheduler: Two asks around NorthstarKiteSchedulerCoordinator: (1) assess ownership and failure handling in projects/northstar/Sources/CLI/Commands/Doctor.swift; (2) capture the contract and rollback note for consumers. Make rollback possible without deleting user data, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"Dashboard: # projects/northstar/cmd/exporter/main.py\n[worker.northstarmoonlitsdkflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.northstarmoonlitsdkflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.northstarmoonlitsdkflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.NorthstarMoonlitSDKFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-54117\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 NorthstarMoonlitSDKFlow'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":"Where did NorthstarCinderAuthStore's cursor drift?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Release engineering needs a NorthstarAsterWebhookStore 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":"diff --git a/projects/northstar/ml/pipeline/features.py b/projects/northstar/ml/pipeline/features.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/northstar/ml/pipeline/features.py\n+++ b/projects/northstar/ml/pipeline/features.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 NorthstarSlateEditorFlow'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":"NorthstarRavenSessionCoordinator: ship, then correct","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","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_54124'\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_54124'::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\nFind the source of this NorthstarBirchMigratorFlow symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"} +{"prompt":"NorthstarAsterWebhookService is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current GraphQL operational envelope\n\nThe relevant code crosses developer tools, Java, WebGL. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"NorthstarCoralUploadCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"NorthstarDriftConsoleCoordinator needs a paired pass: produce a consumer guide for NorthstarDriftConsoleCoordinator, plus correct the known stale timeout beside it. Use projects/northstar/infra/modules/edge/main.tf as the source of truth, preserve the Spring Boot contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"quickFix","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"NorthstarNovaPickerCoordinator is blocking the next release because a flaky snapshot caused by locale-dependent sorting. I need two concrete outcomes from a single pass: separate NorthstarNovaPickerCoordinator's policy from transport without behavior changes, and correct the known stale timeout beside it. Use the existing GraphQL conventions in projects/northstar/config/staging.toml; make rollback possible without deleting user data. 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":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Support wants the behavior in projects/northstar/ui/settings/PrivacyPane.tsx recast as a troubleshooting page: symptoms first, then checks, recovery, and an escalation boundary.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"Before touching projects/northstar/src/sync/reconcile.ts, 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":"Map NorthstarLumenChartService's ownership split","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"The behavior of NorthstarOspreyJobService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/northstar/Sources/App/SessionStore.swift. 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- touch generated artifacts only through their checked-in generator\n- make rollback possible without deleting user data\n- retain the current Kafka operational envelope\n\nThe relevant code crosses developer tools, Java, WebGL. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Em projects/northstar/web/components/FilterDrawer.vue, o NorthstarSummitProxyStore tem um problema intermitente no fluxo de Spring Boot. Leia o fluxo atual e avalie ownership, cancelamento e ordem; preciso apenas da análise.\n\nRestrições:\n- continuar com Spring Boot\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao NorthstarSummitProxyStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"pt"} +{"prompt":"Incident timeline — INC-54142\n\n08:02 deploy NorthstarCoralUploadFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current NorthstarCoralUploadFlow 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":"$ pnpm test --filter NorthstarFlintTimelineFlow\n RUN v3.2.4 /workspace/apps/console\n × NorthstarFlintTimelineFlow > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=54120 phase=resume storedCursor=seg-0183\n session=54120 phase=fetch requestCursor=seg-0183 pageSize=200\n session=54120 phase=commit receivedCursor=seg-0184 itemCount=0\n session=54120 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\nReconstruct the NorthstarFlintTimelineFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Any races in NorthstarSpruceDaemonService?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"2026-07-30T08:14:11.409Z level=info service=northstarasterwebhookcoordinator pod=northstarasterwebhookcoordinator-7cf8 request_id=54156 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=northstarasterwebhookcoordinator request_id=54156 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=northstarasterwebhookcoordinator request_id=54156 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=northstarasterwebhookcoordinator request_id=54156 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=northstarasterwebhookcoordinator request_id=54156 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=northstarasterwebhookcoordinator request_id=54156 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=northstarasterwebhookcoordinator request_id=54156 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=northstarasterwebhookcoordinator request_id=54156 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nReconstruct the NorthstarAsterWebhookCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"NorthstarBirchMigratorCoordinator needs a paired pass: finish NorthstarBirchMigratorCoordinator's responsive empty and retry states, plus correct the known stale timeout beside it. Use projects/northstar/lib/codec/frame.cc as the source of truth, preserve the Cloudflare Workers contract, and avoid unrelated cleanup.","purpose":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Warum hängt NorthstarRavenSessionStore?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"de"} +{"prompt":"Incident timeline — INC-54150\n\n08:02 deploy NorthstarJuniperCLICoordinator 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 NorthstarJuniperCLICoordinator, 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"} diff --git a/data/round2-15.jsonl b/data/round2-15.jsonl index 7eee5c6..de2943a 100644 --- a/data/round2-15.jsonl +++ b/data/round2-15.jsonl @@ -1,200 +1,200 @@ -{"prompt": "the cache key logic is spread across the config parser, the request handler and a per-customer override table:\n\n// config/parse.rs — builds a CacheKeySpec from the customer's yaml\n// handler/key.rs — builds the actual key, ignoring two fields of the spec\n// overrides.rs — a per-customer hashmap applied after the key is built, in production only\n\nthe overrides table has 41 entries, four of which contradict the customer's own config, and nobody knows who added them or why", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "our cache key configuration, which one customer's Vary header just multiplied by every user agent on the internet:\n\ncache_key:\n include: [scheme, host, path, query]\n vary: from_origin # we honour whatever the origin sends\n ignore_query_params: [utm_source, utm_medium, fbclid]\n normalize_accept_encoding: true\n\nthere is no cap on the number of variants per key, no warning when a Vary header would explode the key space, and a customer can do this with a one-line change on their side at any time\n\nwhat the key space did over the incident:\n distinct cache keys for /assets/app.js, before: 3\n after: 41,882 and climbing\n cache fill rate: 1.2 GB/min\n evictions: 8,400/s (previously ~0)\n\nand the customer's diff, in full:\n - Vary: Accept-Encoding\n + Vary: Accept-Encoding, User-Agent", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "field app deletes a queued photo when an upload returns any 4xx, which is how a customer lost the photographic evidence behind a variation claim. beyond the immediate fix, i want a position on what our offline guarantees actually are — what we promise never to lose, what the user is shown, and how we prove it after the fact — because the enterprise contract signing in november asks for exactly that", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "a customer whose payments API was unresolvable for two hours wants to know how an automated key roll can take a zone off the internet. write the incident report for their architecture team — the overlap arithmetic, why nothing caught it, and what changes — without retreating into DNSSEC jargon they'll have to look up whatever you find, write it somewhere the next person will actually look.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "the data team's list, with the recommender incident fresh:\n\n- output validation on the nightly job: row counts, distribution checks, comparison against yesterday\n- stop overwriting the table, write to a new partition and swap\n- the (user_id, context_id) grouping needs a different shape entirely, it doesn't fit in memory\n- the licensing filter should be somewhere legal can read it rather than inline in a 900-line object\n- adaptive query execution is off because someone turned it off in 2023\n- run time has crept from 70 minutes to three hours and nobody owns that\n\nthree engineers, and the nightly job feeds the 06:00 home screen", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "one anycast POP answers queries with the wrong zone data for about ninety seconds after each deploy:\n\n2026-07-29T11:02:14Z pop=fra1 zone=example.com serial=2026072901 source=cache age=0\n2026-07-29T11:02:14Z pop=fra1 zone=example.com serial=2026072814 source=disk age=86400\n2026-07-29T11:02:15Z pop=fra1 answered A example.com -> 203.0.113.9 (old target)\n2026-07-29T11:03:44Z pop=fra1 zone=example.com serial=2026072901 source=xfr age=0\n2026-07-29T11:03:45Z pop=fra1 answered A example.com -> 198.51.100.4 (correct)\n\nthe process starts serving from the on-disk snapshot before the zone transfer completes, and the snapshot can be a day old", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "edge cache hit rate collapsed for one customer overnight with no config change on our side:\n\n before: hit 94.1%, origin rps 1,204\n after: hit 41.2%, origin rps 18,882\n\nsample request/response:\n GET /assets/app.js\n Cache-Control: public, max-age=31536000\n Vary: Accept-Encoding, User-Agent\n ETag: W/\"a11c3f2-8814\"\n\nthe customer added User-Agent to Vary in a deploy yesterday, which multiplies cache entries by every UA string we see", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "our edge configuration API, which customers automate against from a README and a support engineer's memory:\n\nPUT /v1/zones/{zone}/config\n body: cache rules, origin settings, header transforms, WAF toggles\n applies globally within about 90 seconds, but a POP that restarts during that window may serve the previous config for its startup period\n a config that fails validation on one POP is still applied on the others; there is no atomic rollout\n the response is 202 with a deployment id, and GET on it reports \"complete\" once the last POP acknowledges — which is not the same as the config being live\n rate limited to 10 changes per zone per hour, undocumented, and returns 429 with no retry-after\n\nwrite the reference documentation, including the honest description of what \"complete\" means", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "field app's offline behaviour is described in the sales deck as \"works fully offline\" and the reality is three queues with three failure modes and no visibility. write the honest documentation for site staff and their IT departments, covering what is queued, what happens when an upload is rejected, and what conflicts do to their data", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "a customer's architecture review asked five questions about POP health, config rollback, transfer authentication, key rollover approval and self-service recovery. answer each from the code and the runbooks, and mark clearly the ones where the honest answer is that a human notices rather than a mechanism catching it context if it helps: this has been open since before i joined the team.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "zone view should sort by staleness", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "nightly job again", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "one definition of downloaded", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "edge configuration API is automated against by customers who discovered its behaviour by experiment, including the undocumented rate limit and the fact that \"deployment complete\" doesn't mean the config is live everywhere. write the reference documentation, with those two stated plainly rather than left to be discovered again i'm not attached to the current approach if there's an obviously better one.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "before this goes to production, is the sync conflict handling defensible?\n\nFuture sync() async {\n final local = await db.dirtyTasks();\n for (final t in local) {\n final remote = await api.getTask(t.id);\n if (remote == null) { await api.createTask(t); continue; }\n if (t.updatedAt.isAfter(remote.updatedAt)) {\n await api.updateTask(t); // whole record\n } else {\n await db.replaceTask(remote); // discards local edits silently\n }\n }\n}\n\nupdatedAt comes from the device clock, tablets on site are routinely minutes out, and a task record includes a free-text notes field several people edit", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "three parts of the app decide what \"downloaded\" means and they disagree:\n\n// LibraryView.swift\nlet isDownloaded = FileManager.default.fileExists(atPath: track.localURL.path)\n\n// DownloadManager.swift\nfunc isDownloaded(_ t: Track) -> Bool { store.state(for: t.id) == .complete }\n\n// SyncService.swift\nlet downloaded = try db.query(\"SELECT 1 FROM downloads WHERE track_id = ? AND expires_at > ?\", t.id, now)\n\nthe file can exist while the download record says failed, the record can say complete after the file was evicted by the OS, and the expiry is only checked in one of the three", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "cache key logic in one place", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "what makes a zone \"current\"?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "is our idempotency key store fail-open?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "POP answers queries from a disk snapshot that can be a day old, and the health probe considers it healthy the moment it answers anything. work through what readiness should mean for us — zone currency, per-zone or per-POP, and what we do about zones that are never current by any strict definition — knowing the load balancer's probe is a TCP check we don't control", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "recommender is one nine-hundred-line object that legal has to read for the licensing filter and the data team has to change weekly for everything else. before splitting it i'd like agreement on the boundaries and on what evidence we need that the split changed no recommendations, given the output is inherently noisy this is the third time it's bitten us and i'd like it to be the last.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "en"} -{"prompt": "nobody can tell me whether our idempotency store is fail-open, and the daily report duplication suggests it is. read the key store, the failover behaviour and the handler together, and tell me what happens to a request whose key lookup returns nil during a redis failover rather than an error i'd rather have the reasoning written down than a quick answer.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "i'd like an honest read on whether our shuffle can be fixed without changing what users think shuffle means, and then the implementation — a proper shuffled order per session with skips remembered", "purpose": "review", "secondary": "frontendImpl", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "nightly recommender wrote half the usual rows and reported success, and the table it overwrites is the one the home screen reads at six in the morning. i want the validation story designed — what checks, where they run, what happens when one fails at four in the morning — rather than someone adding a row count assert and calling it done", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "zone timeline needs serial changes, transfers and config applies on one axis", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "recommendations went stale for a third of users and the pipeline says it succeeded:\n\n25/07/29 02:14:02 INFO DAGScheduler: Job 41 finished: saveAsTable at Recommender.scala:212, took 4118.882 s\n25/07/29 02:14:02 WARN TaskSetManager: Lost task 88 in stage 12.0: FetchFailed(BlockManagerId(41, ip-10-4-2-71), shuffleId=3)\n25/07/29 02:14:02 INFO DAGScheduler: Resubmitting stage 12 (retry 1)\n25/07/29 03:22:11 INFO DAGScheduler: Job 42 finished: saveAsTable, took 4088.114 s\n25/07/29 03:22:12 INFO Recommender: wrote 41,882,004 rows to recs.user_daily\n\nyesterday's run wrote 62 million rows; the table is overwritten, not appended, and the job exits zero either way", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "site photos taken offline disappear when the app comes back online, maybe one in fifty:\n\n[sync] 08:12:04 queued photo p_4471 (site 88, task 412) 4.1MB\n[sync] 08:12:04 queued photo p_4472 (site 88, task 412) 3.8MB\n[sync] 11:44:19 connectivity restored, draining queue (2 items)\n[sync] 11:44:20 uploading p_4471... 201 created\n[sync] 11:44:21 uploading p_4472... 413 payload too large\n[sync] 11:44:21 removing p_4472 from queue (non-retryable)\n[sync] 11:44:21 queue empty\n\nthe 413 comes from a gateway limit of 4MB that nobody documented, and non-retryable means we delete the local file", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "DNSSEC validation started failing for one zone and only from some resolvers:\n\ndig +dnssec example.com @8.8.8.8 → SERVFAIL\ndig +dnssec example.com @1.1.1.1 → SERVFAIL\ndig +dnssec example.com @our-pop-fra1 → NOERROR, AD not set\n\nzone signing:\n ZSK rolled 2026-07-28T02:00Z (prepublish, 24h overlap configured)\n DS record at the parent: still the pre-roll KSK digest\n RRSIG expiry on the SOA: 2026-07-29T02:00Z\n\nthe overlap was configured as 24 hours and the roll happened 26 hours before the old signatures expired", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "changelog for the mobile app release, which our users will read in the store listing:\n\n41c9e0b fix(shuffle): shuffle now plays every track before repeating\n88f21c0 fix(player): resuming from the lock screen keeps your position and track\nc0aa774 feat(offline): downloads survive an app update\n2e91b45 fix(sync): queued photos are no longer deleted when an upload is rejected\naa30f19 perf(library): library loads in under a second with 10,000 saved tracks\n9c1d004 chore: minimum iOS is now 17\n4410bb7 feat(player): crossfade between tracks, off by default\nb77e910 fix(a11y): the player controls are reachable with VoiceOver\n\nour readers are listeners, not engineers; two of these are the complaints we see most in reviews", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "unsere Offline-Warteschlange ist an drei Stellen implementiert:\n\n// TaskQueue.dart — eigene SQLite-Tabelle, FIFO, kein Retry-Limit\n// PhotoQueue.dart — Dateisystem plus JSON-Index, löscht bei 4xx\n// ReportQueue.dart — SharedPreferences, hält nur den letzten Bericht\n\ndrei Warteschlangen mit drei Fehlerbehandlungen, keine gemeinsame Sicht auf „was ist noch nicht gesendet\", und der Nutzer sieht keine davon\n\ngewünscht ist eine Warteschlange mit einheitlicher Semantik, ohne dass die App offline schlechter wird als heute\n\nZahlen aus dem letzten Monat:\n Aufgaben in der Warteschlange (Median pro Gerät): 14\n Fotos in der Warteschlange (Median pro Gerät): 31\n Berichte: 1 (nur der letzte wird gehalten)\n Einträge, die nach einem 4xx gelöscht wurden: 312\n Einträge, die der Nutzer je gesehen hat: 0\n\nund der relevante Code:\n\n if (e.statusCode >= 400 && e.statusCode < 500) {\n await _queue.remove(item);\n await File(item.path).delete();\n }", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "de"} -{"prompt": "design spec for the field app's sync status screen, which currently doesn't exist:\n\nSync status\n- A persistent indicator in the app bar: synced, syncing with a count, offline with a count, or attention needed.\n- The screen itself lists pending items grouped by type — tasks, photos, reports — with size and age.\n- An item that failed shows why in plain language and what the user can do, never a status code alone.\n- Photos that cannot be uploaded because of size offer to resize and retry rather than being discarded.\n- A conflict shows both versions side by side with the author and time of each, and requires an explicit choice.\n- Nothing is ever deleted from the queue without the user seeing it; \"discard\" is an action, not a consequence.\n- Must be usable in gloves, in sunlight, on a cracked screen, which is the actual condition of most site tablets.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "el botón de descarga no muestra progreso", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "es"} -{"prompt": "task list targets are 36dp outdoors", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "track titles clip at large type", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "licensing filter out of the recommender", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "doc comments on the edge config API", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "player screen", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "offline sync loses concurrent edits silently and a customer is threatening not to renew over it, which makes the conflict model a commercial question rather than a technical preference. lay out the options — server clocks, per-field versioning, a CRDT for the notes field — with the team's lack of CRDT experience and a full working day offline as the constraints", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"} -{"prompt": "we need a plan for POPs in regions where we cannot ship our own hardware", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "cache key configuration honours whatever Vary the origin sends with no cap on variants, which let one customer's one-line change multiply our key space by every user agent on the internet. read the key construction and the override table and tell me what other single-line customer changes could do something similar nobody has trusted this code for about a year, which is part of the problem.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "before we change the sync model i want the conflict semantics written down — what's a conflict, who wins, what the user sees, what we keep for the audit trail — and then the per-field versioning implemented against it, starting with the notes field that people actually fight over", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.9, "slice": "mixed", "lang": "en"} -{"prompt": "POP readiness needs a definition and a first implementation. work through what \"current\" means per zone class with me, then wire a readiness endpoint the load balancer can use, keeping enough capacity during rolling deploys", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.9, "slice": "mixed", "lang": "en"} -{"prompt": "three definitions of \"downloaded\" should become one, and i'd like to know which of the three the library screen should have been using before we standardise. check that against what users report, then unify", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "is the overwrite mode leaving the recs table empty while the job runs", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "what guarantees does the nightly job make about the table between the truncate and the write", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "recommender should write to a new partition and swap rather than overwriting in place", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "nobody can tell me what happens to a queued daily report when the user logs out on site before it syncs — whether it survives, whether it uploads under the next user, or whether it quietly disappears. trace it through the queue, the auth layer and the local database, and tell me which of those three it actually is", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "i'd like to understand what our POP actually does with a query for a zone it has never successfully transferred — whether it serves the snapshot, refuses, or falls through to another POP — because the answer decides whether readiness is a real problem or a cosmetic one", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "playlist shuffle repeats the same tracks far more than users expect, and they're right:\n\nsample of one user's session, 40-track playlist, shuffle on:\n positions played: 12, 4, 12, 31, 4, 12, 7, 31, 12\n distinct tracks in first 9 plays: 5\n\nour shuffle picks a random index per track with a seed derived from the playlist id and the day, and skips are not remembered, so pressing next re-rolls from the same seed and lands on the same handful", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "so the field app's task list shows different data to two users on the same site:\n\nuser A (foreman, online since 06:00): 41 tasks, last sync 11:02\nuser B (engineer, offline 07:00-11:30): 38 tasks, last sync 11:31\ntasks created by user A at 09:14 and 09:41 are missing for user B\ntask edited by user B offline at 10:02 overwrote user A's 09:41 edit on sync\n\nour sync is last-write-wins on the whole task record, using the device clock, and user B's tablet is 4 minutes fast", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "the enterprise construction customer's requirements, which arrived with a signing date:\n\n\"Field data captured offline must not be lost or silently overwritten under any circumstance, including device clock error and concurrent editing. The application must show the user what is pending upload. Data must be retained in the customer's region. Site photographs are contractual evidence and must be retained for six years with an audit trail of any modification. The supplier must demonstrate recovery from a device lost mid-project with no data loss beyond what was captured on that device since its last sync.\"\n\nwe currently fail four of those five. i want the plan by contractual exposure, not by engineering preference", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "our runbook for a stale-serving POP is \"restart it\", which is what caused the last incident. reality:\n\n- symptom is one POP answering with an old serial after a deploy or a restart\n- `edgectl zone status --pop fra1` shows the serial and the source (disk, xfr or cache)\n- draining the POP is safe and takes about 30 seconds to take effect at the load balancer\n- restarting it without draining first means it serves the disk snapshot again, which is the original problem\n- the disk snapshot is refreshed hourly, so a POP that has been down for a day has a day-old zone\n- forcing a transfer with `edgectl zone xfr --pop fra1` takes 60-120s for the large zones\n\nwrite the runbook, ordered by what someone paged would need first", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "field app has three offline queues with three storage mechanisms and three failure behaviours, only one of which retries. unify them behind one queue with one semantics, keep the app working offline for a full day exactly as it does now, and make sure a migration doesn't drop anything already queued on a device assume whoever picks it up next has no context beyond what you write.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "a third of users got yesterday's recommendations and the job reported success, having written 41 million rows where the previous night wrote 62 million. work out how a partial write becomes a success before we add any checks, because the answer determines whether the fix is validation or the write path itself", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "the label's delivery spec, which we ingest from:\n\ndaily DDEX feed over SFTP, one batch per label per day\n each batch is a zip of XML messages plus audio files, up to 40GB\n a message can update or withdraw a previously delivered release, referenced by its DDEX party and release id\n withdrawals must take effect within 24 hours, contractually, including removing tracks from playlists and recommendations\n territory rights are per track per territory with start and end dates, and can change retroactively\n a malformed message in a batch must not block the rest of the batch\n the label sends corrections as full re-deliveries, so idempotency is on (party, release_id, message_timestamp)\n\nbuild the ingestion; the withdrawal path is the one legal cares about", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "one offline queue, three item kinds", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "edge console is the thing we open during an incident and it currently shows a spinner when the control plane is unreachable, which is exactly when we need it. rebuild the zone view to the spec, rendering from cache with an age indicator, and make a POP on the wrong serial impossible to miss", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "our spark configuration versus the shape of the new grouping key:\n\nspark.sql.shuffle.partitions: 200\nspark.executor.memory: 16g\nspark.executor.cores: 4\nspark.executor.instances: 40\nspark.sql.autoBroadcastJoinThreshold: 10m\nspark.sql.adaptive.enabled: false\n\ndistinct (user_id): 41 million\ndistinct (user_id, context_id): 1.6 billion\noutput rows: about 200 per key, collected into a list before slicing\n\nand what the stage looked like when it failed:\n\n Stage 12: 200 tasks, 188 succeeded, 12 failed with OOM\n shuffle read per task: p50 412 MB, max 8.1 GB\n spill (memory): 2.4 TB total\n spill (disk): 1.1 TB total\n peak execution memory per task: 14.2 GB against a 16g executor\n\nthe skew is real: the largest (user_id, context_id) key has 4.1 million events, and the median has eleven", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "pasted-context", "lang": "en"} -{"prompt": "field app ignores the tokens and uses 36dp targets with 14px body text, on tablets used outdoors in gloves. bring it onto the tokens, and tell me how much less fits on screen once the type and targets are right", "purpose": "frontendImpl", "secondary": "review", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"} -{"prompt": "a customer's cache hit rate fell from 94% to 41% after they added User-Agent to Vary, and our origin took the difference. confirm that's the whole story, then add the guard rail that warns or caps before it happens again", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "`Zone.current` means \"loaded from somewhere\" in the resolver and \"matches the primary's serial\" in the admin module, which is precisely the ambiguity behind the stale-serving incident. give the two concepts different names throughout, and make the resolver's check the stricter one wherever that doesn't cost us availability", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "nightly recommender needs an output contract before it needs more checks. define what a valid run means — row counts, key coverage, comparison against yesterday — then implement the swap-a-partition write so a bad run can't overwrite a good one", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "one track model across the services", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "edge config API reference needs writing, and while you're in there confirm whether a validation failure on one POP really does leave the config applied on the others, because our support team has been telling customers otherwise", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "seit dem Update spielt die App nach dem Sperrbildschirm den falschen Titel weiter:\n\n[player] 18:41:02 now playing track=t_4471 position=124.4s queue_index=3\n[player] 18:44:11 app entered background\n[player] 18:44:12 remote command center: nowPlayingInfo updated (track=t_4471)\n[player] 19:02:44 remote command: play\n[player] 19:02:44 resuming queue_index=3 position=0.0s track=t_4488\n\nder Queue-Index wird beim Reaktivieren neu aufgelöst, und die Queue wurde zwischenzeitlich vom Server neu gemischt; die Position geht dabei ebenfalls verloren", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "de"} -{"prompt": "ok so our spark job's memory profile changed after the schema evolution and now it fails at the same stage:\n\n25/07/29 04:11:02 ERROR Executor: Exception in task 412.0 in stage 12.0\njava.lang.OutOfMemoryError: GC overhead limit exceeded\n\tat org.apache.spark.sql.catalyst.expressions.codegen.BufferHolder.grow(BufferHolder.java:71)\n\tat org.apache.spark.sql.execution.aggregate.HashAggregateExec$$anon$1.processInputs\n\nexecutor memory 16g, 4 cores, spark.sql.shuffle.partitions 200\nthe grouping key was (user_id) and is now (user_id, context_id), which multiplies the distinct key count by about forty", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "honestly the construction app's daily report submits twice when the site has patchy signal:\n\n11:02:14 POST /v1/reports (idempotency-key: local-4471) → timeout after 30s\n11:02:44 POST /v1/reports (idempotency-key: local-4471) → 201 created id=r_88412\n11:03:14 POST /v1/reports (idempotency-key: local-4471) → 201 created id=r_88413\n\nserver side:\n idempotency keys are stored per user with a 10 minute TTL in redis\n the first request completed on the server at 11:02:47, after the client had already timed out\n redis was failing over between 11:02:40 and 11:02:50, and lookups during a failover return nil rather than an error", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "right, our shuffle implementation, which users describe as broken and i suspect is worse than that:\n\ndef nextTrack(playlist: Playlist, user: User): Track = {\n val seed = playlist.id.hashCode ^ LocalDate.now().hashCode\n val rng = new scala.util.Random(seed)\n val idx = rng.nextInt(playlist.tracks.size)\n playlist.tracks(idx)\n}\n\ncalled once per skip and once per track end, no memory of what has been played, and the seed is stable for the whole day so the same sequence recurs every session", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "quick one — the zone loading path at POP startup, which is why we serve stale answers after a deploy:\n\nfn start(&self) -> Result<()> {\n let snapshot = self.disk.load_latest()?; // may be up to 24h old\n self.serve(snapshot); // start answering immediately\n tokio::spawn(async move {\n let zone = self.primary.axfr().await?; // can take 60-120s for large zones\n self.serve(zone);\n Ok::<_, Error>(())\n });\n Ok(())\n}\n\nhealth checks pass as soon as we answer anything, the load balancer adds us immediately, and there is no readiness signal tied to the transfer completing", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "por favor, revisa el trabajo de spark antes de que lo dejemos correr esta noche:\n\nval recs = events\n .filter($\"ts\" > lit(cutoff))\n .groupBy($\"user_id\", $\"context_id\")\n .agg(collect_list(struct($\"track_id\", $\"score\")).as(\"items\"))\n .withColumn(\"items\", slice(sort_array($\"items\", false), 1, 200))\n\nrecs.write.mode(\"overwrite\").saveAsTable(\"recs.user_daily\")\n\ncollect_list acumula en memoria por clave, la cardinalidad de (user_id, context_id) es unos 1.600 millones, y el modo overwrite borra la tabla antes de escribir", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "es"} -{"prompt": "fyi the idempotency design note for the field API, written before we had offline devices:\n\n## Idempotency\nClients send an Idempotency-Key header. The server stores the key with the response for ten minutes and replays the stored response on a repeat.\n\n## Assumptions\n- A client retry happens within ten minutes.\n- The key store is available; a failed lookup means the key is new.\n- Keys are unique per user.\n\n## Not covered\nClients that queue for hours offline. Key store failover. Two devices submitting the same queued item.\n\nour field app queues for up to a working day, and a nil lookup during a redis failover is treated as \"new\"", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"} -{"prompt": "heads up: the query behind our artist dashboard, which times out for anyone in the top thousand:\n\nSELECT t.id, t.title,\n sum(p.count) AS plays,\n count(distinct p.user_id) AS listeners,\n (SELECT sum(count) FROM plays_daily p2 WHERE p2.track_id = t.id AND p2.day > current_date - 28) AS plays_28d,\n (SELECT count(*) FROM playlist_tracks pt WHERE pt.track_id = t.id) AS in_playlists\nFROM tracks t\nJOIN plays_daily p ON p.track_id = t.id\nWHERE t.artist_id = $1 AND p.day > current_date - 365\nGROUP BY t.id, t.title\nORDER BY plays DESC;\n\nplays_daily is 41 billion rows partitioned by day, playlist_tracks is 12 billion, and a top artist has 4,000 tracks", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "small thing but the photo upload path in the field app, which is deleting people's evidence:\n\nFuture _drain() async {\n for (final item in await _queue.items()) {\n try {\n await _api.upload(item);\n await _queue.remove(item);\n await File(item.path).delete();\n } on ApiException catch (e) {\n if (e.statusCode >= 400 && e.statusCode < 500) {\n await _queue.remove(item); // \"non-retryable\"\n await File(item.path).delete(); // and the local copy goes too\n }\n }\n }\n}\n\na 413 from an undocumented gateway limit lands squarely in that branch, and site photos are the evidence for variation claims worth thousands", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "support's notes on the missing site photos, which need to become a customer explanation:\n\n- photos taken offline are queued locally and uploaded when the device reconnects\n- an upload rejected with a 4xx is treated as permanently failed and the local copy is deleted\n- a gateway limit of 4MB, which we never documented, rejects photos from newer phones\n- affected users see the photo in the app until the sync runs, then it disappears with no message\n- we can recover nothing; the local file is gone\n- about 300 photos across 40 sites in the last month, some attached to variation claims\n\nwrite the customer notification and the internal note, and be clear that the data is not recoverable", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "incident notes from the DNSSEC failure, and we owe the customer a report:\n\n02:00 ZSK roll executed by the scheduled job\n04:11 first SERVFAIL reports from users on validating resolvers\n04:40 on-call confirms the old RRSIGs expired 26 hours after the roll, overlap configured as 24\n05:02 emergency re-sign with the previous key, published\n05:20 propagation to all POPs complete\n06:15 validating resolvers recover as their caches expire\n08:00 impact assessed: the zone was unresolvable for validating resolvers for about two hours, roughly 40% of their traffic\n\nthe customer runs a payments API on that zone and wants to know why an automated key roll can take a zone off the internet", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "as notas da reunião sobre a sincronização offline, para transformar em documento de decisão:\n\n- o modelo atual é last-write-wins sobre o registo inteiro, com o relógio do dispositivo\n- os tablets em obra estão frequentemente vários minutos desacertados\n- edições concorrentes ao campo de notas perdem-se sem qualquer aviso\n- opções: relógio do servidor, versões por campo, ou CRDT para o campo de texto\n- a equipa não tem experiência com CRDTs e a app tem de continuar a funcionar offline durante um dia inteiro\n- os clientes já perderam registos e um deles ameaça não renovar\n\nescreve a nota de decisão com as opções, o esforço estimado e uma recomendação", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "pt"} -{"prompt": "not urgent, but the questions from a customer's architecture review, which need answering as a document:\n\n\"What happens to our traffic if one of your POPs is unhealthy but still announcing? How do you roll back a configuration change that is already live in some locations? Is a zone transfer authenticated, and what prevents a compromised POP from serving forged answers? What is your DNSSEC key rollover procedure and who approves it? If we misconfigure something catastrophically, what is the fastest path to reverting, and can we do it without your support team?\"\n\nanswer each from the code and the runbooks, and mark clearly where the answer is \"a human notices\" rather than a mechanism", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "社内向けに、レコメンドのバッチ運用ドキュメントがありません。現状は次の通りです:\n\n- 毎晩 02:00 に Spark ジョブが起動し、recs.user_daily を overwrite モードで書き換える\n- 途中でステージが失敗しても再試行され、最終的に成功すれば終了コードは 0 になる\n- 書き込み行数の下限チェックがないため、半分の行数でも「成功」として扱われる\n- 前日のテーブルは overwrite で消えるため、ロールバックできない\n- 実行時間は通常 70 分、遅い日は 3 時間、02:00 開始で 06:00 の配信に間に合わないことがある\n- 監視は Airflow のタスク成否のみで、出力の妥当性は誰も見ていない\n\n設定:\n\n spark.sql.shuffle.partitions = 200\n executor.memory = 16g\n executor.cores = 4\n\n社内向けの運用ドキュメントとしてまとめてください。特に「成功」の定義が曖昧な点を明確に\n\n直近 7 日の実行結果:\n\n 日付 行数 実行時間 終了コード\n 07-23 62,104,882 72 min 0\n 07-24 61,882,004 74 min 0\n 07-25 62,001,118 70 min 0\n 07-26 61,904,412 118 min 0\n 07-27 62,114,008 81 min 0\n 07-28 62,088,441 77 min 0\n 07-29 41,882,004 187 min 0 <- 誰も気づかなかった\n\n spark.sql.adaptive.enabled = false (2023 年に誰かが無効化)", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "ja"} -{"prompt": "genuinely puzzled by this: the field app's offline documentation, which is currently a paragraph in the sales deck:\n\nwhat actually happens offline:\n tasks, photos and daily reports are queued locally with no size limit\n the queue drains in order when connectivity returns, oldest first\n a 4xx response deletes the queued item and its local file\n conflicts resolve last-write-wins by device clock, silently\n downloads of drawings expire after 30 days and re-download on next connection\n the queue is not visible to the user; there is no \"3 items pending\" indicator anywhere\n\nwrite the documentation for site staff and their IT departments, honestly, because they plan their day around what this app can do without signal", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"} -{"prompt": "scalafix and scalac warnings on the recommender, gate goes on next sprint:\n\n[warn] Recommender.scala:88:22: match may not be exhaustive. It would fail on: Context.Unknown\n[warn] Recommender.scala:141:9: discarded non-Unit value\n[warn] Features.scala:41:13: method collectList in class Dataset is deprecated\n[warn] Shuffle.scala:22:5: parameter value seed in method nextTrack is never used\n[warn] Pipeline.scala:212:7: local val cutoff is never used\n\n5 warnings, and Shuffle.scala's unused seed parameter is interesting given users say shuffle is broken", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "clippy and cargo audit on the edge server:\n\nwarning: this async block may hold a lock across an await\n --> src/zone/store.rs:141:9\nwarning: large future (8.2 KB) may cause stack overflow when boxed\n --> src/resolver/handler.rs:88:1\nwarning: `unwrap` on a `None` value is possible here\n --> src/dnssec/keys.rs:41:22\n\ncargo audit:\n Crate: ring 0.17.7\n Advisory: RUSTSEC-2026-0044 (panic on malformed signature input)\n Solution: upgrade to >=0.17.12\n\nthe ring advisory is in the code path that validates DNSSEC signatures on inbound transfers", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "pasted-context", "lang": "en"} -{"prompt": "for context, the gateway limits versus what our own app sends:\n\ngateway:\n client_max_body_size: 4m # undocumented, set in 2023\napp (flutter):\n photo quality: 90, max dimension 4032 # about 3-8MB per photo on recent phones\n no client-side resize\napi docs:\n \"photos may be up to 25MB\"\nCDN in front of the gateway:\n max body 100MB\n\nthe 4MB limit is the effective one and nothing in the product tells anyone about it\n\nand the numbers from the last month:\n photos queued: 41,882\n photos rejected with 413: 312\n photos rejected and deleted locally: 312\n average size of a rejected photo: 6.4 MB\n sites affected: 40\n\nnothing in the app, the docs or the API response mentions four megabytes anywhere", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"} -{"prompt": "background: the DNSSEC signing config, and one number is why a zone went dark:\n\nsigning:\n algorithm: ECDSAP256SHA256\n zsk_rollover: prepublish\n zsk_lifetime_days: 30\n zsk_overlap_hours: 24\n rrsig_validity_hours: 26\n rrsig_refresh_hours: 20\n ksk_rollover: manual\n\nthe overlap is shorter than the signature validity, so signatures made with the outgoing key can outlive the period during which we publish it\n\nthe timeline the numbers produce:\n T+0h ZSK roll, new key published, old key still published\n T+24h old key unpublished (overlap expires)\n T+26h signatures made with the old key expire\n\nso for two hours there are live signatures whose key is no longer published, and every validating resolver returns SERVFAIL for the whole zone during that window", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"} -{"prompt": "worth a look — the iOS player's audio session setup, which i think is behind the lock screen bug:\n\ntry AVAudioSession.sharedInstance().setCategory(.playback, mode: .default, options: [])\ntry AVAudioSession.sharedInstance().setActive(true)\n\nMPRemoteCommandCenter.shared().playCommand.addTarget { [weak self] _ in\n self?.player.play() // resolves the queue index freshly\n return .success\n}\n\nMPNowPlayingInfoCenter.default().nowPlayingInfo = [\n MPMediaItemPropertyTitle: track.title,\n MPNowPlayingInfoPropertyElapsedPlaybackTime: player.currentTime\n]\n\nnowPlayingInfo is set once when playback starts and never updated, and the queue can be reordered by the server while the app is backgrounded", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "pasted-context", "lang": "en"} -{"prompt": "les seuils d'alerte de la plateforme edge, on nous réveille pour rien :\n\n- alert: PopUnhealthy\n expr: up{job=\"pop\"} == 0\n for: 1m\n labels: { severity: page }\n\n- alert: CacheHitRate\n expr: cache_hit_ratio < 0.8\n for: 15m\n labels: { severity: ticket }\n\n- alert: ZoneSerialMismatch\n expr: count(count by (serial) (zone_serial)) > 1\n for: 0m\n labels: { severity: ticket }\n\nen réalité : un POP est toujours en maintenance quelque part ; la chute du taux de cache d'un client a doublé la charge origine sans réveiller personne ; et la divergence de serial après chaque déploiement produit un ticket que tout le monde ignore, y compris le jour où elle a duré deux heures", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "pasted-context", "lang": "fr"} -{"prompt": "this pipeline object does feature building, model scoring, filtering and writing in one class:\n\nobject Recommender {\n def run(spark: SparkSession, cutoff: Timestamp): Unit = {\n // reads three source tables with different freshness expectations\n // builds features inline, with the window sizes as literals\n // scores with a model loaded from a hardcoded S3 path\n // applies business filters: explicit content, regional licensing, artist blocks\n // collects per user, slices to 200, writes with overwrite\n // no row count check, no comparison against yesterday, exits zero on any completed run\n }\n}\n\n900 lines, and the licensing filter is the part legal asks about", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "quarter planning input, and it needs sequencing:\n\n- the field app deletes site photos on a 4xx, which has already cost a customer a variation claim\n- offline sync loses concurrent edits silently and a customer is threatening not to renew\n- a DNSSEC roll took a customer's zone off the internet for two hours\n- the recommender wrote half the usual rows and nobody noticed for a day\n- shuffle is the top complaint in app store reviews and has been for a year\n- one Rust engineer on the edge platform, two on the field app, and the data team is three\n- there's an enterprise construction customer signing in november whose security review starts next month", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "architecture ticket, thinking before code:\n\nEDGE-220 — Readiness and zone freshness\nA POP currently answers as soon as any zone is loaded from its on-disk snapshot, which can be a day old, and the health probe reports healthy at that point. The proposal is a readiness signal tied to zone currency, so a POP does not receive traffic until its zones are current. Concerns: a POP with a very large zone takes two minutes to transfer and we would lose capacity during rolling deploys; \"current\" is ambiguous for zones that change every few seconds; some customers' zones are never current by that definition; and the load balancer's health check is a simple TCP probe we do not control.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"} -{"prompt": "spec for the edge console's zone view, which we open during incidents:\n\nZone view\n- Per-POP table: serial being served, source (disk, transfer, cache), age, query rate, error rate. Sorted by staleness.\n- A POP serving a serial other than the current one is unmistakable — not a colour alone, and with the age in words.\n- Deployment strip: the last five config deployments with their status per POP, and which one a given POP is running.\n- One-click drain and undrain per POP, with a confirmation that states how much traffic will move and where.\n- A zone-level timeline of serial changes, transfers and config applies on one axis, because correlating those is the whole job.\n- The view must render from cached data with an age indicator when the control plane is unreachable, which is exactly when we need it.\n- Everything must be legible on a phone at 3am.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "accessibility findings for the music app's player, from an app store review and our own audit:\n\n1. The play/pause button's accessible label does not change with state.\n2. The scrubber is a custom control with no adjustable trait, so VoiceOver users cannot seek at all.\n3. Track changes are not announced, so a blind user cannot tell what is playing without navigating to the label.\n4. The queue reorder handles have no accessibility actions; reordering requires a drag.\n5. Album art has no alt text, not even the album name.\n6. The mini player and the full player expose duplicate elements to VoiceOver, doubling every swipe.\n7. Dynamic Type above the default clips track titles rather than truncating them, hiding the artist entirely.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "design tokens versus what the field app actually uses:\n\ntokens:\n color.surface #FFFFFF / #12151A\n color.text #12151A / #E9EDF2\n color.muted #5C6672\n color.status.ok #1A7F37\n color.status.warn #9A6700\n color.status.err #B42318\n space 4/8/12/16/24/32, radius 8/12, touch target 48dp (site gloves)\n type: title 20/28, body 16/24, caption 14/20\n\nthe field app: nine hardcoded colours, touch targets of 36dp on the task list, body text at 14px which is unreadable in sunlight, and status shown by colour alone on a screen people use outdoors\n\nbring it onto the tokens, fix the targets and the type sizes, and give status a non-colour indicator", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"} -{"prompt": "gateway body limit to 25MB", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "ring bump for the DNSSEC path", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "store listing still says \"Beta\"", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "core", "lang": "en"} -{"prompt": "turn adaptive query execution back on", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "ZSK overlap longer than signature validity", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "client-side resize before photo upload", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "row count floor on the nightly job", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"} -{"prompt": "CacheHitRate should page, not ticket", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "cap Vary variants per cache key", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "the schema we agreed for the offline queue, now it needs building on both sides:\n\nCREATE TABLE pending_items (\n id uuid PRIMARY KEY,\n device_id text NOT NULL,\n user_id uuid NOT NULL,\n kind text NOT NULL CHECK (kind IN ('task','photo','report')),\n payload jsonb NOT NULL,\n local_path text,\n created_at timestamptz NOT NULL,\n attempts int NOT NULL DEFAULT 0,\n last_error text,\n state text NOT NULL CHECK (state IN ('pending','sent','failed','conflict'))\n);\n\nnothing leaves the queue without the user seeing it; a 4xx moves an item to failed with a human-readable reason rather than deleting it; a conflict is a first-class state; and the queue survives an app update and a device restore", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"} -{"prompt": "our POP has three code paths that decide whether to answer a query:\n\n// resolver/handler.rs\nif zone.is_loaded() { answer(zone) } else { servfail() }\n\n// health/probe.rs\nfn healthy(&self) -> bool { self.zones.any_loaded() } // any zone at all\n\n// admin/status.rs\nfn status(&self) -> Status { if self.zones.all_current() { Ready } else { Degraded } }\n\nthe resolver answers from whatever is loaded, the health probe reports healthy if any zone is loaded, and only the admin status knows whether the data is current — and nothing acts on it", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"} -{"prompt": "field app has two HTTP clients, one with token refresh and one without, and the photo uploader uses the one without — which means a long offline period ends with an upload that 401s and gets treated as permanently failed. move everything onto the refreshing client, and check what else uses the wrong one", "purpose": "refactor", "secondary": "debugging", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "a walkthrough of how a play event becomes a recommendation would help before i touch features", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "the sync thing", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "nowPlayingInfo wird nie aktualisiert", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "de"} -{"prompt": "unused seed parameter in nextTrack", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "pending count in the app bar", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "conflicts need a side-by-side view", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "scrubber needs the adjustable trait", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"} -{"prompt": "曲が変わっても読み上げられません", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "ja"} -{"prompt": "album art has no alt text", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "mini player duplicates VoiceOver elements", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "une seule notion de « zone à jour »", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "fr"} -{"prompt": "`serial` naming across the POP code", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "extract the queue drain from the sync service", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "inline `isDownloaded`, one caller now", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"} -{"prompt": "changelog for the mobile release", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"} -{"prompt": "nota aos clientes sobre as fotos perdidas", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "pt"} -{"prompt": "document what \"deployment complete\" means", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"} -{"prompt": "summarise the readiness proposal", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "PR body for the shuffle rewrite", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"} -{"prompt": "can a 4xx delete a site photo?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "¿el job puede escribir la mitad de las filas?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "es"} -{"prompt": "walk me through the zone transfer path", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "why does shuffle repeat so much?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "site photos disappear after sync", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "recommendations are a day stale", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "one POP serves yesterday's zone", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "warum verliert die App Offline-Änderungen?", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "de"} -{"prompt": "press ahead", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "more reliable", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "your judgement on the order", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"} -{"prompt": "lo del POP, sigue", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "es"} -{"prompt": "leave it tidier than you found it", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"} -{"prompt": "same as we did before", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "doc for the review", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "nothing that touches prod", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"} -{"prompt": "second opinion please", "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": "whatever's next", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"} -{"prompt": "DNSSEC key roll took a customer's zone off the internet for two hours because the publication overlap was shorter than the signature validity. beyond fixing the number, i want a position on how key material changes are reviewed and rolled out at all, given this one was fully automated and nobody looked at it until resolvers started failing", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "boundary", "lang": "en"} -{"prompt": "runbook for a stale POP currently says restart it, which is precisely what makes it serve the old snapshot again. write the real procedure — drain first, check the source, force a transfer, wait — in the order someone paged at three in the morning would need, and say why the obvious action is wrong", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "idempotency design note assumes retries happen within ten minutes and that a failed lookup means a new key, both of which are false for a field app that queues for a working day. read it against the implementation and tell me which other assumptions have quietly stopped holding tell me if this is the wrong shape entirely, i won't be offended.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "en"} -{"prompt": "track model exists three times with different field sets and hand-written conversions in six places, three of them lossy for multi-artist tracks. converge on one model with explicit conversions at the service boundaries, and prove that the mobile API's payloads are byte-identical for a sample covering the lossy cases the sooner we know roughly how big this is, the better for planning.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "cache key construction is split across a config parser, a request handler that ignores two fields of the parsed spec, and a production-only override table with forty-one entries nobody can explain. bring it into one place, work out which overrides are still load-bearing, and keep every customer's effective cache key unchanged unless we decide otherwise deliberately", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "sync status screen doesn't exist, which is why site staff discover a failed upload days later when someone asks for the photo. build it to the spec — pending items by type, plain-language failures, resize-and-retry for oversized photos, conflicts with an explicit choice — and make sure nothing leaves the queue invisibly", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "unsere Offline-Warteschlangen sollen zusammengeführt werden, aber vorher hätte ich gern ein Konzept, was garantiert nicht verloren gehen darf und was der Nutzer davon sieht. Danach die Umsetzung für die Foto-Warteschlange, weil dort bereits Daten verloren gingen", "purpose": "planning", "secondary": "refactor", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "de"} -{"prompt": "DDEX ingestion needs the withdrawal semantics agreed before anything is built — what removing a release means for playlists, caches and recommendations within 24 hours. decide that with me, then implement the ingest and the withdrawal path", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.9, "slice": "mixed", "lang": "en"} -{"prompt": "offline documentation has to exist before the enterprise security review, and writing it will surface things we should fix rather than describe — the silent deletion especially. write it, and give me that list separately", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "escribe la documentación del proceso de recomendaciones para el equipo de datos y comprueba en el código si el modo overwrite deja realmente la tabla vacía durante la escritura, porque eso explicaría los informes de la mañana", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "es"} -{"prompt": "our track model exists three times with different field sets:\n\n// api/TrackDto.scala — 41 fields, what the mobile app receives\n// domain/Track.scala — 22 fields, what the recommender uses\n// storage/TrackRow.scala — 38 fields, what the database has\n\nconversions are hand-written in six places, three of them lossy in ways that only show up for tracks with multiple artists, and the licensing fields exist in two of the three\n\nthe conversions, for reference:\n\n TrackDto.fromDomain(t: Track): TrackDto // drops secondary artists\n Track.fromRow(r: TrackRow): Track // drops licensing fields entirely\n TrackRow.fromDto(d: TrackDto): TrackRow // used only by the admin importer\n TrackDto.fromRow(r: TrackRow): TrackDto // the mobile read path, keeps licensing\n Track.fromDto(d: TrackDto): Track // used by the recommender's backfill\n TrackRow.fromDomain(t: Track): TrackRow // drops everything the domain doesn't model\n\nsix conversions, three lossy, and the licensing fields survive only two of the six paths", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"} -{"prompt": "stale-POP runbook should be a page rather than a wrong one-liner, and the restart command should refuse to run on an undrained POP. write the runbook, then add the guard", "purpose": "writing", "secondary": "quickFix", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "licensing filter should live somewhere legal can read it rather than inline in a nine-hundred-line object. extract it, then document the rules it encodes so the next licensing question doesn't require an engineer", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "POP's three notions of health should collapse into one. do that, and tell me whether any of the current callers depended on the loose definition — the admin status page especially", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "daily reports submit twice on patchy signal and the idempotency store looks fail-open during a failover. confirm the mechanism, then make the store fail closed and give the client a longer key lifetime for offline queues", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"} -{"prompt": "lock screen resumes the wrong track because the queue index is re-resolved after the server reshuffles. diagnose it properly, then make the player resume by track identity and position rather than by index", "purpose": "debugging", "secondary": "frontendImpl", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "player fails seven accessibility items including a scrubber blind users cannot operate at all. fix them, and write the accessibility section for the store listing, which we've never had", "purpose": "frontendImpl", "secondary": "writing", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"} -{"prompt": "pending-items table needs its state machine agreed before it's built — what conflict means, what happens to a failed item the user ignores for a week. settle that, then implement both sides", "purpose": "backendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"} -{"prompt": "is it expected that a config change is live on some POPs and not others for ninety seconds", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "pouvez-vous m'expliquer comment la file d'attente hors ligne gère une mise à jour de l'application ?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "fr"} -{"prompt": "docs/sync.md claims conflicts are surfaced to the user, which has never been true", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "a short note on why we're moving to partition-swap writes, 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 photo size limit becoming documented and enforced", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"} -{"prompt": "scaladoc on Recommender.run promises idempotency that the overwrite write mode doesn't provide", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "write the note to sites whose photos we lost, including what we can and cannot recover", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "health endpoint reports a POP healthy while it serves a zone from a day-old snapshot", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"} -{"prompt": "how should we handle a customer zone that changes faster than we can transfer it", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "i want a position on whether the field app should sync through a queue or a proper replicated store", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"} -{"prompt": "two labels want realtime delivery rather than a daily batch, what would that mean for ingestion", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "construction customers run four app versions and sites go months without updating", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "what should happen to a site's data when the project finishes and the contract ends", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"} -{"prompt": "task list should show which items are pending upload rather than looking synced", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "artist dashboard should load progressively rather than waiting for the slowest query", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"} -{"prompt": "whatever the security review needs first", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "pick up the queue work", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"} -{"prompt": "POP metrics are labelled by pop and zone, which for our largest customer alone is four million series and most of our monitoring bill. rework the labelling so per-zone detail is available on demand rather than always, and tell me which dashboards and alerts break when the high-cardinality labels go", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "recommender reads three source tables with different freshness guarantees and treats them all as current, which is probably why the cold-start features look wrong on mondays. make the freshness explicit at the read, and tell me which features are actually affected before we change any behaviour", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "iOS and Android players implement the queue independently and disagree about repeat-one, which users notice when they switch devices mid-session. decide which behaviour is correct with me first, since it's a product question, then align both clients", "purpose": "planning", "secondary": "frontendImpl", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"} -{"prompt": "photo uploads should be chunked so a large file on a site connection can resume rather than restarting, and we should agree the chunk size and the resume semantics before either side is built. settle that, then implement the server side", "purpose": "backendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"} -{"prompt": "internal page on the recommendation pipeline stops at \"the nightly job writes the table\", which is why nobody knew a partial write was possible. write the page properly — the three source tables, the grouping, the filters, the write mode, and what \"success\" currently means — as the reference for the validation work", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} -{"prompt": "nightly job exits zero whether it writes sixty-two million rows or forty-one, and the table it overwrites is what the morning home screen reads. add a floor and a comparison against the previous run, fail loudly below it, and make sure the failure is visible to someone before six in the morning rather than after", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "three retry helpers exist in the scala codebase and the recommender uses none of them, having its own loop that retries a failed stage without checking whether the previous attempt left rows behind. consolidate onto one helper with explicit idempotency expectations, and tell me which callers were relying on the differences", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"} -{"prompt": "field app's drawing cache expires after thirty days and re-downloads on the next connection, including drawings that haven't changed, which on a site connection costs an hour and a lot of goodwill. make expiry depend on the drawing's version rather than the calendar, keeping offline availability exactly as it is", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "staging environment has one POP and production has forty-one, with the same zone transfer timeout and the same snapshot refresh interval, which is why the stale-serving behaviour has never once appeared before a release. bring the staging numbers into a defensible relationship with production and note which of them are genuinely per-POP", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"} -{"prompt": "app's photo quality setting produces files above the gateway's undocumented limit on any phone bought in the last three years, which is the actual cause of the deleted-evidence incident. lower the default, resize on the client before upload, and make sure existing queued photos are resized rather than rejected when the app updates", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"} -{"prompt": "support needs an endpoint that returns a device's pending queue as the server understands it — what has arrived, what is duplicated, what was rejected and why — because today the only way to answer \"where did my photo go\" is to ask the customer to read their own screen back to us over the phone", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "drawing cache and the offline queue both decide independently when local storage is under pressure, and on a 64GB tablet halfway through a project they fight: the cache evicts drawings the queue is about to attach, and the queue's photos push the cache below its own floor. give storage one owner with an explicit budget per kind of data, and keep a full working day offline possible on the smallest device we support", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "edge config validation runs in three places — the console's form, the API on write, and each POP on apply — and they disagree enough that a config can pass the first two and be rejected by half the fleet. bring them onto one validator compiled into all three, and tell me which currently-live configs would fail it", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"} -{"prompt": "before the enterprise security review i want a read on whether a compromised POP could serve forged answers for any customer zone, given that transfers are authenticated by source address and the signing keys live on the primaries. tell me what an attacker with one POP could actually do", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "en"} -{"prompt": "console's zone view refuses to render at all when the control plane is unreachable, which is the exact circumstance in which we open it. serve it from the last known state with a visible age, keep the drain controls working against the POPs directly, and make it obvious which parts of the page are stale", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "shuffle rewrite needs the product behaviour settled before the code: whether a shuffled order persists across sessions, what a skip means for the rest of the order, and whether adding a track reshuffles. decide that with me, then implement it in the shared player logic", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"} -{"prompt": "zone transfers are authenticated by source address, which is how they were set up when we had three POPs in one datacentre and is now indefensible. move to TSIG or mutual TLS per POP, roll it out without a flag day across forty-one locations, and make an unauthenticated transfer attempt something we alert on rather than something we allow", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"} -{"prompt": "nobody has been able to tell me how a withdrawn release actually leaves the product — whether it disappears from playlists immediately, waits for the nightly recommender, or lingers in the mobile app's local cache until eviction. trace it through ingestion, playlists, recommendations and the client caches, and tell me where the 24-hour contractual window is actually at risk", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"} -{"prompt": "label ingestion accepts a batch as a unit, so one malformed message means the whole day's deliveries from that label sit unprocessed until someone notices. i want to know exactly how failures are currently isolated, if at all, and what a single bad message can hold up in the worst case we've actually seen", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"} -{"prompt": "library screen shows a track as downloaded when the file exists, regardless of whether the download record says it completed or the licence has since expired, which is why people find silent tracks on a plane. show the state honestly — complete, partial, expired — and make the offline case the one we design for rather than the exception", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "an endpoint that returns, for one zone, the serial each POP is currently serving along with where it came from and how old it is, so the console and the runbook stop depending on someone SSHing into a POP to find out. it has to answer while the control plane is degraded, which is when it matters", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"} -{"prompt": "i'd like to understand what the mobile client does with a track whose licence expired while the device was offline — whether it refuses to play, plays anyway, or removes it silently — because the answer determines whether our territory rights handling is a client problem or a server one", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"} -{"prompt": "the queue screen shows tracks with no indication of which are downloaded, which is the single thing people want to know before a flight, and the download state we do show elsewhere is unreliable anyway. show it honestly on the queue, including partial and expired, and make the offline case the default assumption rather than an edge case", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"} -{"prompt": "we need a per-zone deployment status endpoint that reports, per POP, which config revision is live rather than which one was acknowledged, since those are not the same thing and our console currently shows the second while claiming the first. it has to work when the control plane is degraded and be cheap enough for the console to poll", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"} +{"prompt":"Is there a cleaner way to separate OvertureWillowCodecStore'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":"OvertureCopperBridgeCoordinator needs a paired pass: lay out a staged migration for OvertureCopperBridgeCoordinator, plus consolidate the duplicated normalization paths without changing behavior. Use projects/overture/Sources/App/SessionStore.swift as the source of truth, preserve the Room contract, and avoid unrelated cleanup.","purpose":"planning","secondary":"refactor","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Bring OvertureSableParserService'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.5,"slice":"core","lang":"en"} +{"prompt":"En projects/overture/services/ledger/replay.go, OvertureIrisBatchStore tiene un problema intermitente en el flujo de OpenTelemetry. Termina el layout responsive, estados vacío y retry, foco por teclado, dark mode y reduced motion.\n\nRestricciones:\n- seguir con OpenTelemetry\n- conservar compatibilidad y cancelación\n- limitar el cambio a OvertureIrisBatchStore","purpose":"frontendImpl","secondary":"debugging","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"es"} +{"prompt":"Worker: Incident timeline — INC-55117\n\n08:02 deploy OvertureAcornWidgetFlow 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 OvertureAcornWidgetFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"SDK consumers are ready for durable continuation tokens, so the remaining work lives in OvertureMosaicGridService's API, storage, and worker layers. Wire the schema, repository, handler, and worker so duplicate deliveries return the original result and shutdown never acknowledges uncommitted work.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside OvertureMosaicGridService\n- preserve cancellation and back-pressure semantics\n\nSeveral teams work in this IoT fleet, Ruby, SolidJS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"OvertureMoonlitSDKCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Please resist widening this one: OvertureOrbitSyncStore works, but staging still carries a setting that production corrected last month. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside OvertureOrbitSyncStore\n- preserve cancellation and back-pressure semantics\n\nSeveral teams work in this IoT fleet, Ruby, SolidJS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"OvertureAcornWidgetCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Security flagged OvertureCoralUploadStore for a read-only pass because its gRPC 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- preserve cancellation and back-pressure semantics\n- retain the current gRPC operational envelope\n\nThis repository spans IoT fleet, Ruby, SolidJS; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Two asks around OvertureCloudReconcilerCoordinator: (1) assess ownership and failure handling in projects/overture/lib/codec/frame.cc; (2) capture the contract and rollback note for consumers. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"This should remain a deliberately small patch: OvertureMarbleTokenService has one known configuration mistake in projects/overture/config/staging.toml, 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- preserve cancellation and back-pressure semantics\n- stay compatible with the existing Swift 6 deployment\n- keep the work scoped to OvertureMarbleTokenService and its direct tests\n\nThe relevant code crosses IoT fleet, Ruby, SolidJS. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"OvertureMicaProfileCoordinator: polish the last piece","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"The data is already available in projects/overture/engine/render/atlas.cpp; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Before we approve OvertureDeltaCanvasStore, assess whether a misleading timeout name used in five packages is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"boundary","lang":"en"} +{"prompt":"Our support and SDK teams keep answering the same questions about OvertureBeaconStoreStore, but the current prose in projects/overture/src/sync/reconcile.ts 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- preserve cancellation and back-pressure semantics\n- stay compatible with the existing FastAPI deployment\n- keep the work scoped to OvertureBeaconStoreStore and its direct tests\n\nThe relevant code crosses IoT fleet, Ruby, SolidJS. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"en"} +{"prompt":"We expect OvertureMapleQueueService to outgrow its current FastAPI 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- preserve cancellation and back-pressure semantics\n- stay compatible with the existing FastAPI deployment\n- keep the work scoped to OvertureMapleQueueService and its direct tests\n\nThe relevant code crosses IoT fleet, Ruby, SolidJS. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Simulator: The OvertureEmberRelayFlow 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":"OvertureNimbusFormCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"Ticket OPS-55152: retire the legacy replay path for OvertureEchoRegistryCoordinator\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 OvertureEchoRegistryCoordinator 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/overture/ui/settings/PrivacyPane.tsx 里的 OvertureOspreyJobService 最近在 gRPC 流程中出现间歇性问题。 原因已经明确：只把 staging timeout 从 15 秒改成 30 秒，并调整对应 assertion。\n\n约束：\n- 继续使用 gRPC\n- 保持兼容性和取消语义\n- 改动只限于 OvertureOspreyJobService","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"zh"} +{"prompt":"For OvertureRainfallDBCoordinator, change OvertureRainfallDBCoordinator's known staging timeout from 15 to 30 seconds; once that is complete, give the existing implementation a read-only safety pass. Work from projects/overture/internal/auth/refresh.go, stay with OpenTelemetry, and preserve cancellation and back-pressure semantics. Keep the two outcomes separately reviewable.","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Runbook: Two asks around OverturePineMetricsCoordinator: (1) lay out a staged migration for OverturePineMetricsCoordinator; (2) then implement the bounded durable-cursor handler. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"// projects/overture/app/src/main/SyncWorker.kt\nfinal class OvertureBasilRunnerFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 OvertureBasilRunnerFlow'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":"Ticket OPS-55132: retire the legacy replay path for OvertureTideWorkerFlow\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 OvertureTideWorkerFlow 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":"Could the reasoning behind OvertureLumenChartService's OpenTelemetry choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"OvertureQuartzPlayerCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Split OvertureCedarPolicyStore without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Two asks around OvertureHarborIndexCoordinator: (1) separate OvertureHarborIndexCoordinator's policy from transport without behavior changes; (2) capture the contract and rollback note for consumers. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Cadre la migration de OvertureHarborIndexStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"fr"} +{"prompt":"Could OvertureVelaDrawerFlow show the active OpenTelemetry sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Center the OvertureTideWorkerStore modal","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"} +{"prompt":"Read projects/overture/engine/render/atlas.cpp and tell me whether OvertureEmberRelayStore can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Architect a gradual ownership transfer for OvertureCinderAuthStore across two teams, including module seams, temporary interfaces, observability, handoff criteria, and rollback responsibility. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Investigate the OvertureCedarPolicyService hang","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Trace: Incident timeline — INC-55135\n\n08:02 deploy OvertureOspreyJobFlow 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 OvertureOspreyJobFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"What does OvertureFernSnapshotService own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"We need to move OvertureSpruceDaemonStore from the legacy store to Room. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Diff: The OvertureBasilRunnerStore surface in projects/overture/apps/console/routes/usage.svelte 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":"Bump OvertureRainfallDBService's timeout to 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Fresh release brief for OvertureAmberFilterCoordinator:\n- primary outcome: separate OvertureAmberFilterCoordinator's policy from transport without behavior changes\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/overture/crates/index/src/segment.rs\n- platform constraint: Swift 6\n- known complication: an accessibility label that reads the internal enum\n\nBoth results are required, but they should remain independently reviewable. Preserve cancellation and back-pressure semantics; 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":"refactor","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Check OvertureQuartzPlayerStore's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"One contained cleanup in projects/overture/packages/api/openapi.yaml: remove the obsolete OvertureMarbleTokenStore import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Profiler: Two asks around OvertureOpalRouterCoordinator: (1) assess ownership and failure handling in projects/overture/cmd/exporter/main.py; (2) capture the contract and rollback note for consumers. Preserve cancellation and back-pressure semantics, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"} +{"prompt":"OvertureAtlasSearchCoordinator is blocking the next release because lost focus when the drawer animation finishes. I need two concrete outcomes from a single pass: lay out a staged migration for OvertureAtlasSearchCoordinator, and consolidate the duplicated normalization paths without changing behavior. Use the existing gRPC conventions in projects/overture/lib/codec/frame.cc; preserve cancellation and back-pressure semantics. 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":"En projects/overture/cmd/exporter/main.py, OvertureDriftConsoleService tiene un problema intermitente en el flujo de Room. Añade el endpoint idempotente con cursor durable, autorización tenant, spans y tests de retry.\n\nRestricciones:\n- seguir con Room\n- conservar compatibilidad y cancelación\n- limitar el cambio a OvertureDriftConsoleService Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con Room alrededor de OvertureDriftConsoleService.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"es"} +{"prompt":"In projects/overture/web/components/FilterDrawer.vue hat OvertureIrisBatchService ein sporadisches Problem im OpenTelemetry-Ablauf. Trenne Verantwortlichkeiten und entferne Duplikate, ohne API, Wire-Werte, Reihenfolge oder sichtbares Verhalten zu ändern.\n\nRandbedingungen:\n- OpenTelemetry weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf OvertureIrisBatchService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um OvertureIrisBatchService mit OpenTelemetry kompatibel.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"de"} +{"prompt":"Test Suite 'OvertureLedgerGateFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[OvertureLedgerGateFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/overture/crates/index/src/segment.rs:144: error: -[OvertureLedgerGateFlowTests 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 '-[OvertureLedgerGateFlowTests 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\nReconstruct the OvertureLedgerGateFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Test Suite 'OvertureVelaDrawerCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[OvertureVelaDrawerCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/overture/internal/auth/refresh.go:144: error: -[OvertureVelaDrawerCoordinatorTests 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 '-[OvertureVelaDrawerCoordinatorTests 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 OvertureVelaDrawerCoordinator'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-55113\n\n08:02 deploy OvertureOrbitSyncFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. From this evidence, draft consumer-facing migration guidance for OvertureOrbitSyncFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"} +{"prompt":"Any races in OvertureLedgerGateStore?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"thread 'tokio-runtime-worker' panicked at projects/overture/Sources/CLI/Commands/Doctor.swift:217:18:\ncalled `Result::unwrap()` on an `Err` value: SendError { .. }\n\nstack backtrace:\n 0: std::panicking::begin_panic_handler\n 1: core::panicking::panic_fmt\n 2: core::result::unwrap_failed\n 3: overturecopperbridgeflow::scheduler::LeaseTask::flush\n at ./projects/overture/Sources/CLI/Commands/Doctor.swift:217:18\n 4: overturecopperbridgeflow::scheduler::LeaseTask::shutdown\n at ./src/scheduler/lease.rs:301:14\n 5: tokio::runtime::task::core::Core::poll\n 6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task\n 7: tokio::runtime::context::runtime::enter_runtime\n\nnote: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.\nruntime metrics: active_tasks=3 queued_tasks=0 open_channels=0 shutdown_reason=SIGTERM grace_ms=10000\nThe panic is only visible during rolling deploys. Requests have already drained, the sender is intentionally dropped by the coordinator, and the process exits successfully despite the panic hook writing this trace.\n\nReconstruct the OvertureCopperBridgeFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"The minimum supported OpenTelemetry version in projects/overture/internal/auth/refresh.go 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":"OvertureJuniperCLICoordinator: sequence, then polish","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"On compact widths, OvertureVelaDrawerStore'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":"How does OvertureSableParserStore propagate cancellation through the Swift 6 boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"For OvertureTideWorkerCoordinator, find the unknown cause of two validators with subtly different error strings; once that is complete, give the existing implementation a read-only safety pass. Work from projects/overture/crates/index/src/segment.rs, stay with Swift 6, and preserve cancellation and back-pressure semantics. Keep the two outcomes separately reviewable.","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Milestones for replacing OvertureTideWorkerService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"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_55158'\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_55158'::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\nReconstruct the OvertureSummitProxyCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"OvertureOspreyJobCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"diff --git a/projects/overture/src/sync/reconcile.ts b/projects/overture/src/sync/reconcile.ts\nindex 62d71aa..90f3c1e 100644\n--- a/projects/overture/src/sync/reconcile.ts\n+++ b/projects/overture/src/sync/reconcile.ts\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure OverturePineMetricsFlow 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":"2026-07-30T08:14:11.409Z level=info service=overtureslateeditorflow pod=overtureslateeditorflow-7cf8 request_id=55120 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=overtureslateeditorflow request_id=55120 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=overtureslateeditorflow request_id=55120 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=overtureslateeditorflow request_id=55120 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=overtureslateeditorflow request_id=55120 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=overtureslateeditorflow request_id=55120 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=overtureslateeditorflow request_id=55120 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=overtureslateeditorflow request_id=55120 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nFind the source of this OvertureSlateEditorFlow 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":"Our support and SDK teams keep answering the same questions about OvertureAtlasSearchService, but the current prose in projects/overture/engine/render/atlas.cpp 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- preserve cancellation and back-pressure semantics\n- stay compatible with the existing gRPC deployment\n- keep the work scoped to OvertureAtlasSearchService and its direct tests\n\nThe relevant code crosses IoT fleet, Ruby, SolidJS. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"OvertureMicaProfileService needs an idempotent replay endpoint backed by FastAPI; accept a cursor, cap each page at 500 items, and return a stable continuation token.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Console: Could the reasoning behind OvertureEchoRegistryStore's Swift 6 choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Unify the OvertureQuartzPlayerService validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Assess the OvertureFernSnapshotStore diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Workspace: Ticket OPS-55131: retire the legacy replay path for OvertureCraneWorkspaceFlow\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 OvertureCraneWorkspaceFlow 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":"core","lang":"en"} +{"prompt":"Three teams extended OvertureMosaicGridStore independently, leaving parallel adapters and normalization branches that are supposed to behave identically. Separate those responsibilities into focused units, remove the duplicated normalization branches, and keep public types, wire values, log fields, timing, and test-observable behavior exactly the same.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current FastAPI operational envelope\n\nThis repository spans IoT fleet, Ruby, SolidJS; use its existing conventions rather than importing a new abstraction.\n\nThe target structure is settled; carry out the behavior-preserving edits rather than writing another strategy.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Em projects/overture/workers/thumbnail/consumer.ex, o OvertureOspreyJobStore tem um problema intermitente no fluxo de gRPC. Separe responsabilidades e remova duplicação sem mudar API, wire values, ordem ou comportamento observável.\n\nRestrições:\n- continuar com gRPC\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao OvertureOspreyJobStore","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"pt"} +{"prompt":"Cadre la migration de OvertureFrostPanelService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"fr"} +{"prompt":"Production says OvertureKiteSchedulerService is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current gRPC operational envelope\n\nThis repository spans IoT fleet, Ruby, SolidJS; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current OvertureEmberRelayService 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 OvertureEmberRelayService\n- preserve cancellation and back-pressure semantics\n\nSeveral teams work in this IoT fleet, Ruby, SolidJS 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":"OvertureSlateEditorCoordinator: assess, then document","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Draft OvertureBeaconStoreService's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-55145: finish the compact OvertureCinderAuthFlow filter experience\n\nRoute: /catalog/search\nSource: projects/overture/workers/thumbnail/consumer.ex\nFramework: gRPC\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\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Finish the visible OvertureCinderAuthFlow 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":"Repository: diff --git a/projects/overture/pkg/cache/lease.rs b/projects/overture/pkg/cache/lease.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/overture/pkg/cache/lease.rs\n+++ b/projects/overture/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\nRead the artifact above as a skeptical reviewer. Is OvertureAmberFilterFlow'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":"OvertureWrenExportCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"UI ticket DES-55151: finish the compact OvertureWillowCodecCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/overture/web/components/FilterDrawer.vue\nFramework: OpenTelemetry\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 OvertureWillowCodecCoordinator 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 the reasoning behind OvertureMoonlitSDKService's gRPC choices be captured as an ADR for engineers joining the project next quarter?","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"The behavior of OvertureSummitProxyService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/overture/Sources/CLI/Commands/Doctor.swift. 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- preserve cancellation and back-pressure semantics\n- retain the current Room operational envelope\n\nThis repository spans IoT fleet, Ruby, SolidJS; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Incident timeline — INC-55146\n\n08:02 deploy OvertureLumenChartFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nReconstruct the OvertureLumenChartFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Two engineers disagree about whether OvertureBirchMigratorService's cache is authoritative. Walk the reads and writes in projects/overture/config/staging.toml and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Pipeline: Incident timeline — INC-55111\n\n08:02 deploy OvertureIrisBatchFlow 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\nFind the source of this OvertureIrisBatchFlow symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"projects/overture/Sources/App/SessionStore.swift has grown through several launches, and OvertureSummitProxyStore now mixes policy, transport, persistence, and metrics in one place. Rename the overloaded state, extract the pure conversion work, and make dependencies explicit while preserving ABI, serialization, metrics, and failure messages.\n\nConstraints:\n- preserve cancellation and back-pressure semantics\n- stay compatible with the existing Room deployment\n- keep the work scoped to OvertureSummitProxyStore and its direct tests\n\nThe relevant code crosses IoT fleet, Ruby, SolidJS. Prefer evidence from the repository and make any assumption explicit.\n\nThe target structure is settled; carry out the behavior-preserving edits rather than writing another strategy.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Gateway: Incident timeline — INC-55115\n\n08:02 deploy OvertureCoralUploadFlow 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 OvertureCoralUploadFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"// projects/overture/engine/render/atlas.cpp\nfinal class OvertureAtlasSearchFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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\nWire OvertureAtlasSearchFlow'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.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Ticket OPS-55116: retire the legacy replay path for OvertureWrenExportFlow\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 OvertureWrenExportFlow 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.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Release engineering needs a OvertureSpruceDaemonService 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":"OvertureFlintTimelineCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Responsive layout for OvertureAcornWidgetService","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Renderer: projects/overture/Sources/App/SessionStore.swift now contains OvertureDeltaCanvasService'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":"OvertureDriftConsoleStore'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":"OvertureRavenSessionService 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":"OvertureBasilRunnerCoordinator: check the suspicious part","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Indexer: The OvertureMicaProfileStore 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":"Please resist widening this one: OvertureVelaDrawerService works, but staging still carries a setting that production corrected last month. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside OvertureVelaDrawerService\n- preserve cancellation and back-pressure semantics\n\nSeveral teams work in this IoT fleet, Ruby, SolidJS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"} +{"prompt":"OvertureGarnetModalCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Rename OvertureSlateEditorService's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"OvertureBirchMigratorCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"} +{"prompt":"Apparently: // projects/overture/apps/console/routes/usage.svelte\nfinal class OvertureGarnetModalFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 OvertureGarnetModalFlow 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":"Please turn OvertureKiteSchedulerStore'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":"OvertureNimbusFormService'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":"SDK consumers are ready for durable continuation tokens, so the remaining work lives in OvertureAmberFilterService's API, storage, and worker layers. Wire the schema, repository, handler, and worker so duplicate deliveries return the original result and shutdown never acknowledges uncommitted work.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside OvertureAmberFilterService\n- preserve cancellation and back-pressure semantics\n\nSeveral teams work in this IoT fleet, Ruby, SolidJS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Teach OvertureMarbleTokenFlow to verify signed continuation tokens, reject cross-tenant cursors, and rotate keys without invalidating tokens issued during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"The data is already available in projects/overture/src/sync/reconcile.ts; render it as a sortable table with a compact mobile card fallback, visible focus, and honest loading placeholders.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Lately: // projects/overture/cmd/exporter/main.py\nfinal class OvertureJuniperCLIFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 OvertureJuniperCLIFlow; 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":"Spell OvertureOpalRouterService's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"OvertureAmberFilterStore is functionally complete on desktop, but compact widths and assistive technologies still expose unfinished states. Finish the responsive layout, empty and retry states, keyboard order, VoiceOver labels, dark appearance, and reduced-motion transition while preserving the existing data-loading code.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current Swift 6 operational envelope\n\nThis repository spans IoT fleet, Ruby, SolidJS; use its existing conventions rather than importing a new abstraction.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"OvertureCinderAuthCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-55153\n\n08:02 deploy OvertureDriftConsoleCoordinator 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Capture the OvertureDriftConsoleCoordinator decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"} +{"prompt":"Oddly: # projects/overture/apps/console/routes/usage.svelte\n[worker.overturemosaicgridcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.overturemosaicgridcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.overturemosaicgridcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.OvertureMosaicGridCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-55159\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/overture/apps/console/routes/usage.svelte. 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":"OvertureCraneWorkspaceCoordinator needs a paired pass: finish OvertureCraneWorkspaceCoordinator's responsive empty and retry states, plus capture the contract and rollback note for consumers. Use projects/overture/services/ledger/replay.go as the source of truth, preserve the OpenTelemetry contract, and avoid unrelated cleanup.","purpose":"frontendImpl","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"OvertureNovaPickerCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Add a bounded OvertureMapleQueueStore export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-55140: retire the legacy replay path for OvertureMoonlitSDKFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for OvertureMoonlitSDKFlow, 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":"Currently: Please turn OvertureMosaicGridFlow'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":"Today: projects/overture/ml/pipeline/features.py 里的 OvertureFlintTimelineStore 最近在 Room 流程中出现间歇性问题。 请给出阶段、兼容层、指标、rollback 和 ownership，先不要修改代码。\n\n约束：\n- 继续使用 Room\n- 保持兼容性和取消语义\n- 改动只限于 OvertureFlintTimelineStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"} +{"prompt":"Collapse the OvertureCraneWorkspaceService wrappers","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Design the OvertureJuniperCLIService rollback","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Polish the OverturePineMetricsService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"OvertureSableParserCoordinator: handle the lingering thing","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Before touching projects/overture/Sources/CLI/Commands/Doctor.swift, propose how to retire its legacy format while old clients remain active for ninety days and operators retain a reversible escape hatch. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"This should remain a deliberately small patch: OvertureAcornWidgetStore has one known configuration mistake in projects/overture/config/staging.toml, 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- preserve cancellation and back-pressure semantics\n- stay compatible with the existing Swift 6 deployment\n- keep the work scoped to OvertureAcornWidgetStore and its direct tests\n\nThe relevant code crosses IoT fleet, Ruby, SolidJS. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"Trace OvertureOpalRouterStore's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Context: Incident timeline — INC-55143\n\n08:02 deploy OvertureFlintTimelineFlow 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 OvertureFlintTimelineFlow 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":"Background: Incident timeline — INC-55121\n\n08:02 deploy OvertureFernSnapshotFlow 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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Turn the material above into a concise OvertureFernSnapshotFlow 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":"Question: Incident timeline — INC-55157\n\n08:02 deploy OvertureMarbleTokenCoordinator 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 OvertureMarbleTokenCoordinator 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":"Assess the OvertureCoralUploadService diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'OvertureNovaPickerFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[OvertureNovaPickerFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/overture/db/migrations/20260730_events.sql:144: error: -[OvertureNovaPickerFlowTests 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 '-[OvertureNovaPickerFlowTests 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 OvertureNovaPickerFlow'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":"Does OvertureLumenChartStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Summarize the OvertureCopperBridgeService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Does OvertureCopperBridgeStore preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Any races in OvertureCloudReconcilerStore?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"Test Suite 'OvertureEmberRelayCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[OvertureEmberRelayCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/overture/engine/render/atlas.cpp:144: error: -[OvertureEmberRelayCoordinatorTests 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 '-[OvertureEmberRelayCoordinatorTests 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 OvertureEmberRelayCoordinator's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Draft OvertureCloudReconcilerService's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"What sequence would let OvertureBirchMigratorStore adopt Swift 6 with dual reads but no dual writes? Include data validation, canary scope, and the decision that ends compatibility mode. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"OvertureFrostPanelCoordinator: diagnose, then document","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"Clarify OverturePineMetricsStore's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"OvertureFernSnapshotCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"} +{"prompt":"Before touching projects/overture/crates/index/src/segment.rs, propose how to retire its legacy format while old clients remain active for ninety days and operators retain a reversible escape hatch. Stop at the restructuring strategy rather than editing files.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"} +{"prompt":"Compare OvertureCraneWorkspaceStore's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Polish the OvertureWrenExportService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"projects/overture/infra/modules/edge/main.tf now contains OverturePrismCacheStore'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":"# projects/overture/ml/pipeline/features.py\n[worker.overtureopalrouterflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.overtureopalrouterflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.overtureopalrouterflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.OvertureOpalRouterFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-55133\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/overture/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":"Observation: # projects/overture/packages/api/openapi.yaml\n[worker.overturesableparserflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.overturesableparserflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.overturesableparserflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.OvertureSableParserFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-55137\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Align OvertureSableParserFlow'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":"Constraint: // projects/overture/config/staging.toml\nfinal class OvertureBirchMigratorFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 OvertureBirchMigratorFlow 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":"# CI job 55114: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: FastAPI\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] OvertureBeaconStoreFlowIntegration.replays_after_timeout ... ok\n[test] OvertureBeaconStoreFlowIntegration.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 \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\nAdd the bounded OvertureBeaconStoreFlow replay flow described here, including authorization, key rotation, cancellation, lag metrics, and tests for malformed and cross-tenant cursors.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"} +{"prompt":"One contained cleanup in projects/overture/workers/thumbnail/consumer.ex: remove the obsolete OvertureKiteSchedulerFlow import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"Bring OvertureNimbusFormStore'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":"Request: projects/overture/src/sync/reconcile.ts now contains OvertureMapleQueueFlow'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.4,"slice":"core","lang":"en"} +{"prompt":"OvertureOrbitSyncCoordinator is blocking the next release because lease renewal code copied across three workers. I need two concrete outcomes from a single pass: produce a consumer guide for OvertureOrbitSyncCoordinator, and give the existing implementation a read-only safety pass. Use the existing Room conventions in projects/overture/cmd/exporter/main.py; preserve cancellation and back-pressure semantics. Keep the outcomes distinct so reviewers can see which evidence supports the assessment and which files or prose satisfy the requested change.\n\nConstraints:\n- preserve public wire values and tenant boundaries\n- cover cancellation and retry behavior\n- avoid generated code and unrelated cleanup\n- include a rollback trigger that an on-call engineer can measure\n\nThis is a fresh workstream for the release, so derive everything from the repository and the context here.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"Goal: // projects/overture/workers/thumbnail/consumer.ex\nfinal class OvertureCedarPolicyFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task] = [:]\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 OvertureCedarPolicyFlow'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":"OverturePrismCacheCoordinator: give it a nicer flow","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"OvertureRavenSessionCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"} +{"prompt":"Incident timeline — INC-55119\n\n08:02 deploy OvertureFrostPanelFlow 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 OvertureFrostPanelFlow, 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":"Bring OvertureBasilRunnerService'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":"Two deliverables are holding up OvertureIrisBatchCoordinator. First, find the unknown cause of timestamps rendered one day ahead near UTC midnight. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/overture/services/ledger/replay.go, which follows OpenTelemetry conventions and currently suffers from timestamps rendered one day ahead near UTC midnight. Preserve cancellation and back-pressure semantics.\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":"Symptom: # projects/overture/Sources/App/SessionStore.swift\n[worker.overturequartzplayerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.overturequartzplayerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.overturequartzplayerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.OvertureQuartzPlayerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-55118\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/overture/Sources/App/SessionStore.swift and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"Please resist widening this one: OvertureWrenExportStore works, but staging still carries a setting that production corrected last month. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside OvertureWrenExportStore\n- preserve cancellation and back-pressure semantics\n\nSeveral teams work in this IoT fleet, Ruby, SolidJS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"# CI job 55154: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: FastAPI\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] OvertureMapleQueueCoordinatorIntegration.replays_after_timeout ... ok\n[test] OvertureMapleQueueCoordinatorIntegration.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 \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 OvertureMapleQueueCoordinator 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":"OvertureLedgerGateCoordinator: diagnose, then document","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"This should remain a deliberately small patch: OvertureOrbitSyncService has one known configuration mistake in projects/overture/ml/pipeline/features.py, not an open-ended failure investigation. Correct the known literal and the test that intentionally mirrors it; the final diff should stay local enough for an on-call engineer to verify at a glance.\n\nConstraints:\n- preserve cancellation and back-pressure semantics\n- stay compatible with the existing Room deployment\n- keep the work scoped to OvertureOrbitSyncService and its direct tests\n\nThe relevant code crosses IoT fleet, Ruby, SolidJS. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"} +{"prompt":"PM is preparing the OvertureAtlasSearchStore 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 OvertureAtlasSearchStore\n- preserve cancellation and back-pressure semantics\n\nSeveral teams work in this IoT fleet, Ruby, SolidJS monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/overture/infra/modules/edge/main.tf b/projects/overture/infra/modules/edge/main.tf\nindex 62d71aa..90f3c1e 100644\n--- a/projects/overture/infra/modules/edge/main.tf\n+++ b/projects/overture/infra/modules/edge/main.tf\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit OvertureRainfallDBFlow 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":"Headsup: projects/overture/cmd/exporter/main.py の OvertureFlintTimelineService で、Room の flow に断続的な問題が起きています。 現在の flow を読み、ownership、cancel、順序が安全か評価してください。分析だけで十分です。\n\n制約:\n- Room を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は OvertureFlintTimelineService のみ","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"boundary","lang":"ja"} +{"prompt":"Production says OvertureEchoRegistryService is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- preserve cancellation and back-pressure semantics\n- retain the current Swift 6 operational envelope\n\nThis repository spans IoT fleet, Ruby, SolidJS; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Why does OvertureGarnetModalService's FastAPI worker stop making progress while its health endpoint remains green? Gather evidence from the scheduler and queue code and narrow the failure mode.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"} +{"prompt":"UI ticket DES-55127: finish the compact OvertureHarborIndexFlow filter experience\n\nRoute: /catalog/search\nSource: projects/overture/config/staging.toml\nFramework: Swift 6\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 OvertureHarborIndexFlow 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":"Ticket OPS-55136: retire the legacy replay path for OverturePrismCacheFlow\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 OverturePrismCacheFlow 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":"OvertureCedarPolicyCoordinator needs a paired pass: change OvertureCedarPolicyCoordinator's known staging timeout from 15 to 30 seconds, plus capture the contract and rollback note for consumers. Use projects/overture/ui/settings/PrivacyPane.tsx as the source of truth, preserve the gRPC contract, and avoid unrelated cleanup.","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"} +{"prompt":"FYI: Does OvertureLedgerGateService preserve ordering?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Responsive layout for OvertureJuniperCLIStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"} +{"prompt":"OvertureSpruceDaemonCoordinator: ship a sensible version","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"} +{"prompt":"Meanwhile: # projects/overture/engine/render/atlas.cpp\n[worker.overturecloudreconcilerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.overturecloudreconcilerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.overturecloudreconcilerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.OvertureCloudReconcilerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-55130\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/overture/engine/render/atlas.cpp and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"} +{"prompt":"2026-07-30T08:14:11.409Z level=info service=overturekiteschedulercoordinator pod=overturekiteschedulercoordinator-7cf8 request_id=55155 msg=\"lease acquired\" partition=12 epoch=884\n2026-07-30T08:14:11.417Z level=debug service=overturekiteschedulercoordinator request_id=55155 msg=\"batch loaded\" rows=250 cursor=01JZ7M\n2026-07-30T08:14:11.590Z level=warn service=overturekiteschedulercoordinator request_id=55155 msg=\"heartbeat delayed\" elapsed_ms=3012 deadline_ms=3000\n2026-07-30T08:14:11.593Z level=info service=overturekiteschedulercoordinator request_id=55155 msg=\"lease renewed\" partition=12 epoch=885\n2026-07-30T08:14:11.598Z level=error service=overturekiteschedulercoordinator request_id=55155 msg=\"commit rejected\" expected_epoch=884 actual_epoch=885\n2026-07-30T08:14:11.601Z level=info service=overturekiteschedulercoordinator request_id=55155 msg=\"retry scheduled\" attempt=1 delay_ms=0\n2026-07-30T08:14:11.617Z level=warn service=overturekiteschedulercoordinator request_id=55155 msg=\"duplicate key ignored\" event_id=ev_29af\n2026-07-30T08:14:11.620Z level=info service=overturekiteschedulercoordinator request_id=55155 msg=\"batch acknowledged\" rows=250\n\nDeployment is Kubernetes 1.34 with four replicas. The warning begins after a consumer rebalance and stops after the pod is restarted. Queue depth remains flat, CPU is 28%, and the readiness probe never fails.\n\nReconstruct the OvertureKiteSchedulerCoordinator failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"} +{"prompt":"Locally: Test Suite 'OvertureAsterWebhookFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[OvertureAsterWebhookFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/overture/app/src/main/SyncWorker.kt:144: error: -[OvertureAsterWebhookFlowTests 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 '-[OvertureAsterWebhookFlowTests 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. Find the source of this OvertureAsterWebhookFlow 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":"A previously stable test around OvertureNovaPickerService now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"diff --git a/projects/overture/Sources/CLI/Commands/Doctor.swift b/projects/overture/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/overture/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/overture/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure OvertureSpruceDaemonFlow 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":"Two engineers disagree about whether OvertureGarnetModalStore's cache is authoritative. Walk the reads and writes in projects/overture/app/src/main/SyncWorker.kt and settle that question from the code.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"} +{"prompt":"Split projects/overture/cmd/exporter/main.py by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"} +{"prompt":"Extract OvertureAsterWebhookService's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Rename OvertureRainfallDBStore's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"boundary","lang":"en"} +{"prompt":"I inherited OvertureWillowCodecService and need a careful read of projects/overture/services/ledger/replay.go 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- preserve cancellation and back-pressure semantics\n- stay compatible with the existing OpenTelemetry deployment\n- keep the work scoped to OvertureWillowCodecService and its direct tests\n\nThe relevant code crosses IoT fleet, Ruby, SolidJS. Prefer evidence from the repository and make any assumption explicit.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"} +{"prompt":"Ticket OPS-55138: retire the legacy replay path for OvertureDeltaCanvasFlow\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 OvertureDeltaCanvasFlow 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":"Production: Ticket OPS-55142: retire the legacy replay path for OvertureRavenSessionFlow\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 OvertureRavenSessionFlow 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":"Staging: Two deliverables are holding up OvertureBeaconStoreCoordinator. First, separate OvertureBeaconStoreCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/overture/src/sync/reconcile.ts, which follows FastAPI conventions and currently suffers from duplicate retries after a network handoff. Preserve cancellation and back-pressure semantics.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"} +{"prompt":"OvertureLumenChartCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Remove OvertureAsterWebhookStore's stray comma","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"} +{"prompt":"For OvertureAsterWebhookCoordinator, separate OvertureAsterWebhookCoordinator's policy from transport without behavior changes; once that is complete, give the existing implementation a read-only safety pass. Work from projects/overture/apps/console/routes/usage.svelte, stay with FastAPI, and preserve cancellation and back-pressure semantics. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"} +{"prompt":"Is there a cleaner way to separate OvertureCinderAuthService'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":"OvertureDeltaCanvasCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"} +{"prompt":"Atlas: projects/overture/services/ledger/replay.go の OvertureWillowCodecFlow で、OpenTelemetry の flow に断続的な問題が起きています。 責務を分離して重複をなくし、API、wire value、順序、観測可能な動作は変えないでください。\n\n制約:\n- OpenTelemetry を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は OvertureWillowCodecFlow のみ","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"ja"} +{"prompt":"PM needs a concise migration note for OvertureRavenSessionStore, 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: Ticket OPS-55144: retire the legacy replay path for OvertureMicaProfileFlow\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 OvertureMicaProfileFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Incident timeline — INC-55141\n\n08:02 deploy OvertureNimbusFormFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current OvertureNimbusFormFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"} +{"prompt":"Documente o contrato de OvertureHarborIndexService","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"pt"} +{"prompt":"Fresh release brief for OvertureCoralUploadCoordinator:\n- primary outcome: change OvertureCoralUploadCoordinator'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/overture/workers/thumbnail/consumer.ex\n- platform constraint: gRPC\n- known complication: a query plan that changes after statistics refresh\n\nBoth results are required, but they should remain independently reviewable. Preserve cancellation and back-pressure semantics; 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.6,"slice":"mixed","lang":"en"} +{"prompt":"Draft OvertureSlateEditorStore's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"} +{"prompt":"Zentriere das OvertureFrostPanelStore-Modal","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"de"}